Bug 2009045

+++ This bug was initially created as a clone of Bug #2009044 +++

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

--- Additional comment from Peter Robinson on 2021-09-24 14:08:02 EDT ---

Hardware is a Lenovo Carbon X1 gen 6

--- Additional comment from Fedora Blocker Bugs Application on 2021-09-24 14:08:14 EDT ---

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

--- Additional comment from Paul Whalen on 2021-09-24 14:40:12 EDT ---

Confirmed this on AArch64 as well. It works in Beta but once upgraded it will no longer honour the Xorg selection at log in.

--- Additional comment from František Zatloukal on 2021-09-27 05:35:40 EDT ---

I was able to get into X11 by logging in, logging out and then selecting the X11 session again.

--- Additional comment from Peter Robinson on 2021-09-27 08:15:05 EDT ---

(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.

--- Additional comment from Adam Williamson on 2021-09-27 12:06:45 EDT ---

+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.

--- Additional comment from Geraldo Simião on 2021-09-27 13:07:44 EDT ---

(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.

--- Additional comment from Geraldo Simião on 2021-09-27 13:10:31 EDT ---



--- Additional comment from Geraldo Simião on 2021-09-27 13:11:45 EDT ---



--- Additional comment from Ray Strode [halfline] on 2021-09-27 14:29:37 EDT ---

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

?

--- Additional comment from Ray Strode [halfline] on 2021-09-27 14:30:29 EDT ---

when this happens, do you guys have a file called /run/gdm/custom.conf ? if so, can you attach that file ?

--- Additional comment from Peter Robinson on 2021-09-27 14:45:33 EDT ---

(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

--- Additional comment from Ray Strode [halfline] on 2021-09-28 09:22:02 EDT ---

Geraldo and Paul if you could post logs too that'd be great!

--- Additional comment from Ronald Warsow on 2021-09-28 16:36:55 EDT ---

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

--- Additional comment from Ronald Warsow on 2021-09-28 16:50:33 EDT ---

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

--- Additional comment from Ronald Warsow on 2021-09-28 16:55:44 EDT ---

(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 .

--- Additional comment from Ray Strode [halfline] on 2021-09-29 11:10:16 EDT ---

Thanks for the reproducer and logs, I believe I've found the issue. I'm doing a build now.

--- Additional comment from Fedora Update System on 2021-09-29 11:18:18 EDT ---

FEDORA-2021-bfcc9cd095 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-bfcc9cd095