FS#65780 - [gnome-shell] failure on logging in to my GNOME desktop
Attached to Project:
Arch Linux
Opened by Bart Willems (hersenbeuker) - Wednesday, 11 March 2020, 10:20 GMT
Last edited by freswa (frederik) - Sunday, 13 September 2020, 15:51 GMT
Opened by Bart Willems (hersenbeuker) - Wednesday, 11 March 2020, 10:20 GMT
Last edited by freswa (frederik) - Sunday, 13 September 2020, 15:51 GMT
|
Details
Description:
After running a full system update, I can't login to my GNOME desktop anymore. Logging in on wayland just brings me back to GDM, whilst Xorg shows me an error screen without details. I created an additional account on my system and that one can login without issues. Additional info: It appears that I'm not the only one with the issue: https://www.reddit.com/r/archlinux/comments/fgikow/new_gnomeshell_indirectly_depends_on_python2/ Running "journalctl -u gdm" gives me the following log entries: * gdm-password: gkr-pam: unable to locate daemon control file * gdm: GdmDisplay: Session never registered, failing * gdm: Tried to look up non-existent conversation gdm-launch-environment * gdm: Freeing conversation 'gdm-launch-environment' with active job It might be related to this issue: https://bugzilla.redhat.com/show_bug.cgi?id=1796544 Steps to reproduce: * have an existing gnome 3.34 system * run a system update * try to login with an existing account |
This task depends upon
Can we just close this or do we want to reassign the issue to the gnome-shell maintainer (heftig)?
So reassigning might be better.
For me, dash-to-dock (https://extensions.gnome.org/extension/307/dash-to-dock/) was blocking everything.
Removing it was enough to fix it.
I opened a bug upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/2456
Rolling back to March 04 was the only solution that worked for me.