Bug 2007742 - Selecting Xorg doesn't work as when you login you still end up with Wayland
Summary: Selecting Xorg doesn't work as when you login you still end up with Wayland
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: 35
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: https://ask.fedoraproject.org/t/we-ar...
Depends On:
Blocks: F35FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2021-09-24 18:06 UTC by Peter Robinson
Modified: 2021-12-03 01:07 UTC (History)
15 users (show)

Fixed In Version: gdm-41.0-2.fc35
Clone Of:
: 2009044 (view as bug list)
Environment:
Last Closed: 2021-10-01 00:15:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
session x11 sucsses second time login (419.52 KB, image/png)
2021-09-27 17:10 UTC, Geraldo Simião
no flags Details
X11 session failed to login at first time (481.56 KB, image/png)
2021-09-27 17:11 UTC, Geraldo Simião
no flags Details
journalctl -b0 from 2 subseq. logins into X with debug=on in /etc/gdm/custom.conf (1.03 MB, text/plain)
2021-09-28 20:50 UTC, Ronald Warsow
no flags Details


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME gdm merge_requests 159 0 None None None 2021-09-29 15:11:54 UTC

Description Peter Robinson 2021-09-24 18:06:40 UTC
I'm still stuck with Xorg due to screen share not working with some of the various video conferencing apps.

I upgraded to F-35 today and upon logging in I realised I was running Wayland. I logged out, selected the Xorg option and logged in and it was still Wayland.

mutter-41.0-2.fc35.x86_64
gdm-41.0-1.fc35.x86_64
gnome-shell-41.0-1.fc35.x86_64
gnome-control-center-41.0-1.fc35.x86_64
gnome-session-40.1.1-2.fc35.x86_64
gnome-session-wayland-session-40.1.1-2.fc35.x86_64
gnome-session-xsession-40.1.1-2.fc35.x86_64

Comment 1 Peter Robinson 2021-09-24 18:08:02 UTC
Hardware is a Lenovo Carbon X1 gen 6

Comment 2 Fedora Blocker Bugs Application 2021-09-24 18:08:14 UTC
Proposed as a Blocker for 35-final by Fedora user pbrobinson using the blocker tracking app because:

 Xorg should be a working option for Workstation

Comment 3 Paul Whalen 2021-09-24 18:40:12 UTC
Confirmed this on AArch64 as well. It works in Beta but once upgraded it will no longer honour the Xorg selection at log in.

Comment 4 František Zatloukal 2021-09-27 09:35:40 UTC
I was able to get into X11 by logging in, logging out and then selecting the X11 session again.

Comment 5 Peter Robinson 2021-09-27 12:15:05 UTC
(In reply to František Zatloukal from comment #4)
> I was able to get into X11 by logging in, logging out and then selecting the
> X11 session again.

Doesn't work for me, I've tried a number of times, and it should work the first time as expected.

Comment 6 Adam Williamson 2021-09-27 16:06:45 UTC
+7 in https://pagure.io/fedora-qa/blocker-review/issue/481 , marking accepted. For a criterion I'd say we can probably count it as covered by Beta criterion "Shutting down, rebooting, logging in and logging out must work using standard console commands and the mechanisms offered (if any) by all release-blocking desktops." - in this instance, "logging in" isn't exactly working as intended. The footnote defines it as "Logging in must transfer the user from the login screen/prompt to their working environment", which is slightly vague.

Comment 7 Geraldo Simião 2021-09-27 17:07:44 UTC
(In reply to František Zatloukal from comment #4)
> I was able to get into X11 by logging in, logging out and then selecting the
> X11 session again.

Yes, here too. I tested with an F35 beta 1.2 iso and other iso too. First login only on Wayland, but second time I can log into a X11 sesssion.

Comment 8 Geraldo Simião 2021-09-27 17:10:31 UTC
Created attachment 1826720 [details]
session x11 sucsses second time login

Comment 9 Geraldo Simião 2021-09-27 17:11:45 UTC
Created attachment 1826721 [details]
X11 session failed to login at first time

Comment 10 Ray Strode [halfline] 2021-09-27 18:29:37 UTC
so i just did a fresh f35 install and can't reproduce.

Can someone set Enable=true in the [debug] section of /etc/gdm/custom.conf, reboot, reproduce, and then attach the full, unfiltered output of 

journalctl -b

?

Comment 11 Ray Strode [halfline] 2021-09-27 18:30:29 UTC
when this happens, do you guys have a file called /run/gdm/custom.conf ? if so, can you attach that file ?

Comment 12 Peter Robinson 2021-09-27 18:45:33 UTC
(In reply to Ray Strode [halfline] from comment #11)
> when this happens, do you guys have a file called /run/gdm/custom.conf ? if
> so, can you attach that file ?

No file called that on my current session, will retry and get debug once I've finished calls and meetings

Comment 13 Ray Strode [halfline] 2021-09-28 13:22:02 UTC
Geraldo and Paul if you could post logs too that'd be great!

Comment 14 Ronald Warsow 2021-09-28 20:36:55 UTC
I've new installed last week and now it's full updated (Intel Skylake and i915)

I see the following:
I'm in general able to log in to X when I choose to do so by explicit choose X under the the "wheel" in the login screen
But when I log out and login again I get wayland *even* when X is highlighted (but not clicked)

To get X again I explicitly need to click X

Comment 15 Ronald Warsow 2021-09-28 20:50:33 UTC
Created attachment 1827182 [details]
journalctl -b0 from 2 subseq. logins into X with debug=on in /etc/gdm/custom.conf

as declared in comment 14 
1. a login with exclicit set X, 
2. a log out and 
3. a login without clicking X again (but controlled it's highlighted) 

=> leads to wayland

Comment 16 Ronald Warsow 2021-09-28 20:55:44 UTC
(In reply to Ray Strode [halfline] from comment #11)
> when this happens, do you guys have a file called /run/gdm/custom.conf ? if
> so, can you attach that file ?

no and no ! ;-) 

- with debug=on in /etc/gdm/custom.conf -

ls -lRa /run/gdm/

/run/gdm/:
total 4
drwx--x--x.  3 root gdm    80 28. Sep 22:39 .
drwxr-xr-x. 48 root root 1220 28. Sep 22:39 ..
-rw-r--r--.  1 root root    5 28. Sep 22:39 gdm.pid
drwx------.  2 gdm  gdm    40 28. Sep 22:39 greeter

/run/gdm/greeter:
total 0
drwx------. 2 gdm  gdm 40 28. Sep 22:39 .
drwx--x--x. 3 root gdm 80 28. Sep 22:39 .

Comment 18 Fedora Update System 2021-09-29 15:18:18 UTC
FEDORA-2021-bfcc9cd095 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-bfcc9cd095

Comment 19 Fedora Update System 2021-09-30 01:43:37 UTC
FEDORA-2021-bfcc9cd095 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-bfcc9cd095`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-bfcc9cd095

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 20 František Zatloukal 2021-09-30 06:55:37 UTC
Thanks for the fix, gdm-41.0-2.fc35 fixes the issue.

Comment 21 Ronald Warsow 2021-09-30 08:28:17 UTC
dito here, gdm-41.0-2.fc35 fixes the issue.
thanks

Comment 22 Geraldo Simião 2021-09-30 19:45:57 UTC
Confirmed here too, with gdm-41.0-2.fc35. All is working as expected.

Comment 23 Fedora Update System 2021-10-01 00:15:01 UTC
FEDORA-2021-bfcc9cd095 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.


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