This is with Fedora-Workstation-Live-x86_64-36-20220413.n.0.iso and some previous versions. When I boot it in a virtual machine, I'm greeted with login prompt for the Live System User in gdm. Clicking the user logs it properly. When I install it, do the all setup and restart the machine, then I'm booted into gdm, where I select my user, enter my password and upon successful login the session closes shortly after the login, thus I'm back in gdm. When I pick the user again and enter the password again and confirm it again, then the session sticks, even though I'm on the desktop, not in the overview mode. This is not the main problem, the main problem is the request to login twice to be able to use the Workstation. I'm using virtual manager with QXL video driver. I do not know whether it has any impact on the matter.
Created attachment 1872416 [details] journalctl -xe This is an output of the `journalctl -xe` in a state when I booted the Live image and the system is waiting in the gdm prompt. If you want anything else, give me the commands and I'll provide it. Suspicious things in the log, from my point of view: Apr 14 04:24:22 localhost-live gnome-session-binary[1911]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 14 04:24:22 localhost-live gnome-session-binary[1911]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 14 04:24:22 localhost-live org.gnome.Shell.desktop[1937]: MESA-LOADER: failed to open qxl: /usr/lib64/dri/qxl_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib64/dri, suffix _dri) Apr 14 04:24:22 localhost-live org.gnome.Shell.desktop[1937]: failed to load driver: qxl An interesting thing about the later: nothing provides /usr/lib64/dri/qxl_dri.so, according to `dnf install /usr/lib64/dri/qxl_dri.so`, neither with `dnf provides */qxl_dri.so*`. Maybe it's expected, I do not know.
Hmm, maybe it's not gnome-shell, or not directly. When I boot an installed f36 machine and, instead of picking my user and enter password for it in the gdm, I switch to a text terminal (Ctrl+Alt+F4 or such), then before I manage to enter the credentials I'm back in gdm. From that I guess the gdm restarted for some reason, even without logging into the gnome-shell. It's a pure speculation though.
I think you're seeing bug 2071394. You can try the included gnome-shell build which should fix it. Also, don't use QXL, use Virtio. We have several issues with QXL which we seem unable to fix, see bug 2063156 and bug 2071226. The default in virt-manager was changes to virtio because of this.
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. 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 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.