You are not logged in.
- Topics: Active | Unanswered
#26 2023-05-13 06:06:05
- seth
- Member
- Registered: 2012-09-03
- Posts: 51,335
Re: [SOLVED] Gnome Login screen blank after upgrade to gnome
How was the "there's no login panel" bug fixed?
Or is it just the delay?
May 12 18:32:51 peelz systemd-logind[343]: New session 1 of user gdm.
…
May 12 18:32:56 peelz NetworkManager[350]: <info> [1683930776.0577] manager: NetworkManager state is now CONNECTED_GLOBAL
…
May 12 18:33:18 peelz gnome-session-c[473]: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
…
May 12 18:33:18 peelz at-spi-bus-laun[482]: g_dbus_method_invocation_return_dbus_error: assertion 'error_message != NULL' failed
May 12 18:33:21 peelz systemd-timesyncd[319]: Contacted time server [2620:83:8000:ffd1:1::e]:123 (2.arch.pool.ntp.org).
May 12 18:33:21 peelz systemd-timesyncd[319]: Initial clock synchronization to Fri 2023-05-12 18:33:21.623460 EDT.
May 12 18:33:21 peelz systemd[1]: systemd-hostnamed.service: Deactivated successfully.
May 12 18:33:44 peelz gnome-shell[519]: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
May 12 18:33:44 peelz gnome-shell[519]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
…
>>> May 12 18:33:45 peelz org.gnome.Shell.desktop[519]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm/.config/mutter/sessions/1068ef60dbe8699974168393079844657400000004680000.ms”: No such file or directory
…
May 12 18:33:45 peelz at-spi-bus-laun[482]: g_dbus_method_invocation_return_dbus_error: assertion 'error_message != NULL' failed
May 12 18:33:45 peelz at-spi-bus-laun[482]: g_dbus_method_invocation_return_dbus_error: assertion 'error_message != NULL' failed
May 12 18:33:45 peelz at-spi-bus-laun[482]: g_dbus_method_invocation_return_dbus_error: assertion 'error_message != NULL' failed
May 12 18:33:45 peelz at-spi-bus-laun[482]: g_dbus_method_invocation_return_dbus_error: assertion 'error_message != NULL' failed
May 12 18:33:45 peelz at-spi-bus-laun[482]: g_dbus_method_invocation_return_dbus_error: assertion 'error_message != NULL' failed
…
May 12 18:33:46 peelz gnome-shell[519]: Registering session with GDM
May 12 18:34:10 peelz gsd-media-keys[664]: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
May 12 18:34:10 peelz gsd-power[661]: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
May 12 18:34:10 peelz gsd-color[655]: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
May 12 18:34:10 peelz gsd-wacom[672]: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
May 12 18:34:10 peelz gsd-keyboard[669]: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
May 12 18:34:10 peelz gnome-session-binary[468]: Entering running state
May 12 18:34:10 peelz gsd-media-keys[664]: Failed to grab accelerator for keybinding settings:rotate-video-lock
May 12 18:34:10 peelz gsd-media-keys[664]: Failed to grab accelerator for keybinding settings:hibernate
May 12 18:34:10 peelz gsd-media-keys[664]: Failed to grab accelerator for keybinding settings:playback-repeat
May 12 18:34:10 peelz gsd-media-keys[664]: Failed to grab accelerator for keybinding settings:playback-random
May 12 18:34:10 peelz /usr/lib/gdm-x-session[467]: dbus-daemon[467]: [session uid=120 pid=467] Activating service name='org.gnome.ScreenSaver' requested by ':1.33' (uid=120 pid=661 comm="/usr/lib/gsd-power")
May 12 18:34:10 peelz /usr/lib/gdm-x-session[467]: dbus-daemon[467]: [session uid=120 pid=467] Successfully activated service 'org.gnome.ScreenSaver'
May 12 18:34:40 peelz systemd[1]: systemd-localed.service: Deactivated successfully.
May 12 18:34:40 peelz systemd[1]: systemd-hostnamed.service: Deactivated successfully.
May 12 18:34:45 peelz geoclue[614]: Service not used for 60 seconds. Shutting down..
May 12 18:34:45 peelz systemd[1]: geoclue.service: Deactivated successfully.
>>>
May 12 18:36:16 peelz gdm-password][903]: gkr-pam: unable to locate daemon control file
May 12 18:36:16 peelz gdm-password][903]: gkr-pam: stashed password to try later in open session
May 12 18:36:16 peelz gdm-password][903]: pam_unix(gdm-password:session): session opened for user banana(uid=1000) by (uid=0)There's still a lot of AT-SPI failures (gone with update or NO_AT_BRIDGE=1 ?) which cover teh time from 18~:32:55 to ~18:34:10 and then there's a 91s delay where absolutely nothing happens between geoclue deactivating and your login.
Which gap is the critical one?
Online
#27 2023-05-13 19:39:40
- SploitStacks
- Member
- From: Virginia, USA
- Registered: 2018-02-10
- Posts: 23
Re: [SOLVED] Gnome Login screen blank after upgrade to gnome
How was the "there's no login panel" bug fixed?
That was corrected when I removed fprintd from my system a few posts up:
I also have a ThinkPad and experimented with the fingerprint sensor a while ago and determined it wasn't worth the headache to me. I removed all packages related to fprintd and that appears to have fixed the issue.
There's still a lot of AT-SPI failures (gone with update or NO_AT_BRIDGE=1 ?) which cover teh time from 18~:32:55 to ~18:34:10 and then there's a 91s delay where absolutely nothing happens between geoclue deactivating and your login.
Which gap is the critical one?
It was probably the first one, but either way it seems to not matter any more because after a system upgrade, at-spi2-core had a new version (2.48.2-1) and the 90 second lag is gone now.
❯ paru -Qikk at-spi2-core
[sudo] password for banana:
Name : at-spi2-core
Version : 2.48.2-1
Description : Protocol definitions and daemon for D-Bus at-spi
Architecture : x86_64
URL : https://gitlab.gnome.org/GNOME/at-spi2-core
Licenses : GPL2
Groups : None
Provides : at-spi2-atk=2.48.2-1 atk=2.48.2-1 libatk-1.0.so=0-64 libatk-bridge-2.0.so=0-64 libatspi.so=0-64
Depends On : dbus glib2 gsettings-desktop-schemas libx11 libxml2 libxtst systemd
Optional Deps : dbus-broker: Alternative bus implementation [installed]
Required By : atkmm gtk2 gtk3 minecraft-launcher python-atspi webkit2gtk webkit2gtk-4.1 webkit2gtk-5.0 webkitgtk-6.0
Optional For : None
Conflicts With : at-spi2-atk<=2.38.0-2 atk<=2.38.0-2
Replaces : at-spi2-atk<=2.38.0-2 atk<=2.38.0-2
Installed Size : 3.84 MiB
Packager : Jan Alexander Steffens (heftig) <heftig@archlinux.org>
Build Date : Thu May 11 13:46:07 2023
Install Date : Sat May 13 15:25:25 2023
Install Reason : Installed as a dependency for another package
Install Script : No
Validated By : SignatureI now have no issues, much thanks for the assistance, in summary for anyone else who reads this post:
systemd-homed -> solved by removing all lines containing "pam_systemd_home.so" in /etc/pam.d/system-auth
missing login panel in gdm -> solved by removing fprintd from system
90 second lag on gdm login screen starting -> stopped occurring when at-spi2-core was upgraded to version 2.48.2-1
Offline
#28 2023-05-13 22:32:16
- 2ManyDogs
- Forum Fellow
- Registered: 2012-01-15
- Posts: 4,645
Re: [SOLVED] Gnome Login screen blank after upgrade to gnome
The original two issues I posted for have been but this systemd crash hasn't, so yep I guess I'll remove the solved tag.
The thread is still marked solved.
Offline
#29 2023-05-13 23:00:18
- sp00kins
- Member
- Registered: 2023-05-13
- Posts: 5
Re: [SOLVED] Gnome Login screen blank after upgrade to gnome
The thread is still marked solved.
The thread is solved according to the OP:
I now have no issues, much thanks for the assistance, in summary for anyone else who reads this post:
systemd-homed -> solved by removing all lines containing "pam_systemd_home.so" in /etc/pam.d/system-authmissing login panel in gdm -> solved by removing fprintd from system
90 second lag on gdm login screen starting -> stopped occurring when at-spi2-core was upgraded to version 2.48.2-1
Offline