Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1695690 - gnome-terminal fails to start with Error calling StartServiceByName: Timeout was reached
Summary: gnome-terminal fails to start with Error calling StartServiceByName: Timeout ...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gnome-terminal
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Debarshi Ray
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-03 15:33 UTC by Christophe de Dinechin
Modified: 2019-04-03 15:33 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)

Description Christophe de Dinechin 2019-04-03 15:33:02 UTC
Description of problem:

Running gnome-terminal from within a tightvnc-server session fails with the message:

# Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached

The problem occurs with X11 over `ssh -Y` and within a gnome-session running on a tightvnc-server instance.

Version-Release number of selected component (if applicable):
gnome-terminal.x86_64               3.28.2-3.el8               @beaker-AppStream

How reproducible: Always (no workaround found so far)

Steps to Reproduce:
1. Provisioned a machine with RHEL-8.0.0-20190326.n.0 in Beaker
2. yum module install virt
3. yum group install Workstation
4. yum install tigervnc tigervnc-server xterm
5. vncserver -geometry 1600x1200
6. DISPLAY=:1 gnome-session

Actual results:

In the gnome-session (and outside), gnome-terminal fails to start with above message


Expected results:

gnome-terminal starts correctly


Additional info:

Apparently not a problem with the distro itself, since gnome-terminal works fine in a guest installed on that host from the same image.

xterm works (but is remarkably slow)


Note You need to log in before you can comment on or make changes to this bug.