There is an openQA test - it's trying to test whether any desktop notifications show up during a live session - which does the following: 1. Boot a Workstation live image to runlevel 3 (multiuser.target) 2. Log in as root to a console and Do Some Stuff (fiddle with package repos a bit, and set the system clock to 6:00am, for REASONS) 3. Run 'systemctl isolate graphical.target' After this, what *should* happen is that we get to a graphical desktop as liveuser, because autologin should kick in just like it does when booting direct to the graphical environment as usual. And up until recently, that is what happened. However, since Fedora-Rawhide-20200326.n.0 (Rawhide) and Fedora-32-20200330.n.1 (F32), that's not what happens any more: instead, we wind up at the GDM login screen. The only relevant thing I can see that changed in both those two composes is gnome-shell: it went from 3.36.0-3.{fc32,fc33} to 3.36.0-4.{fc32,fc33} in those exact composes. systemd didn't change in both, nothing else I could think of to check did - only gnome-shell. The difference between 3.36.0-3 and 3.36.0-4 is just this patch: https://src.fedoraproject.org/rpms/gnome-shell/blob/c41301197e0aa2bccd2bb951bfedca8fbe2247de/f/0001-data-ensure-systemd-environment-is-sanitized-when-sh.patch neither halfline nor myself can figure out offhand why this would be breaking things, but it does *seem* to be the case. This isn't a super urgent bug as it's a fairly unusual thing to do and I *can* patch the test to work around it (assuming that logging in from the GDM screen actually works - I didn't try that yet), but I figured I'd file it. I'm attaching the /var/log tarball from running this test with GDM debugging enabled, you can read the journal file in var/log/journal with journalctl --file.
Created attachment 1676734 [details] /var/log tarball with gdm debugging enabled
Bonus weird thing about this bug: I tweaked openQA to just hit enter when it sees GDM (on this path) to try and get to a desktop. This doesn't work (it blinks briefly and goes back to GDM)...unless I *also* drop a custom.conf to set GDM to debugging mode, while we're logged into the console at runlevel 3, before we do the 'systemctl isolate graphical.target'. If I also have the test do that, hitting enter *does* get us to a desktop.
gdm-3.34.1-3.fc3{2,3} fixes this, but there's no update for F32. So it's fixed in Rawhide, still an issue on F32. I'll maybe try and put in a workaround for the F32 Final RC tests...
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.