Bug 1871389

Summary: GNOME Terminal and GNOME apps won't launch from X11 session
Product: [Fedora] Fedora Reporter: Artem <ego.cordatus>
Component: gnome-sessionAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 33CC: awilliam, caillon+fedoraproject, debarshir, giallu, gnome-sig, john.j5live, klember, kparal, mclasen, rhughes, robatino, rstrode, sandmann
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: AcceptedBlocker
Fixed In Version: gnome-shell-3.37.90-2.fc33 gnome-shell-3.37.90-2.fc34 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-24 23:23:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1766775    
Attachments:
Description Flags
journal
none
rpm-qa none

Description Artem 2020-08-23 02:04:03 UTC
Description of problem:
GNOME Terminal and GNOME apps won't launch after upgrade from f32 to f33. Fedora Workstation edition.


Version-Release number of selected component (if applicable):
gnome-terminal-3.36.1.1-4.fc33


How reproducible:
Try to launch gnome-terminal (or any gnome app) in Xorg session from any non-gnome-terminal. mate-terminal for example:

$ gnome-terminal


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


Expected results:
App successfully launched.


Additional info:
This happens only in Xorg session. No issue on Wayland session.

Comment 1 Kamil Páral 2020-08-24 12:41:09 UTC
I can confirm this issue. This is not just about upgraded systems, even clean F33 installs show the same problem. In my VM logs, I see:

Aug 24 14:26:13 f32 gsd-color[1785]: Unable to init server: Could not connect: Connection refused
Aug 24 14:26:13 f32 gsd-color[1785]: Cannot open display:
Aug 24 14:26:13 f32 gsd-keyboard[1799]: Unable to init server: Could not connect: Connection refused
Aug 24 14:26:13 f32 gsd-keyboard[1799]: Cannot open display:
Aug 24 14:26:13 f32 gsd-power[1805]: Unable to init server: Could not connect: Connection refused
Aug 24 14:26:13 f32 gsd-power[1805]: Cannot open display:
...
Aug 24 14:26:40 f32 systemd[1423]: Starting GNOME Terminal Server...
Aug 24 14:26:40 f32 gnome-terminal-server[2268]: Unable to init server: Could not connect: Connection refused
Aug 24 14:26:40 f32 gnome-terminal-server[2268]: Failed to parse arguments: Cannot open display:
Aug 24 14:26:40 f32 systemd[1423]: gnome-terminal-server.service: Main process exited, code=exited, status=10/n/a
Aug 24 14:26:40 f32 systemd[1423]: gnome-terminal-server.service: Failed with result 'exit-code'.
Aug 24 14:26:40 f32 systemd[1423]: Failed to start GNOME Terminal Server.
...

Comment 2 Kamil Páral 2020-08-24 12:46:35 UTC
Created attachment 1712353 [details]
journal

Comment 3 Kamil Páral 2020-08-24 12:46:40 UTC
Created attachment 1712354 [details]
rpm-qa

Comment 4 Kalev Lember 2020-08-24 15:08:48 UTC
This should be already fixed in gnome-shell-3.37.90-2.fc33. Can you guys verify the fix, please?

Comment 5 Adam Williamson 2020-08-24 21:50:45 UTC
Discussed at 2020-08-24 blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2020-08-24/f33-blocker-review.2020-08-24-16.07.html . Accepted as a blocker as a violation of "It must be possible to run the default web browser and a terminal application from all release-blocking desktop environments" when GNOME is run on Xorg (which is the default config for some systems).

Comment 6 Artem 2020-08-24 23:16:45 UTC
(In reply to Kalev Lember from comment #4)
> This should be already fixed in gnome-shell-3.37.90-2.fc33. Can you guys
> verify the fix, please?

@Kalev, seems like 'gnome-shell-3.37.90-2.fc33' fixed this issue. Thanks a lot for patching it. Also fix should be in next upstream gnome-shell 3.37.91 version.

Comment 7 Adam Williamson 2020-08-24 23:23:10 UTC
if you verify the fix, we can close the bug, as the update got in just under the freeze wire so it's already "stable". Thanks!