Ever since upgrading to Fedora 34 (from 33) I’ve noticed that the system is much slower to wake from sleep/suspend.
What happens:
When waking the computer from suspend, the screen remains black until I press a key. Sometimes I need to press a key multiple times before the gdm shows up.
I’ve also noticed that, sometimes, I am unable to reach the password prompt via keyboard and have to click anywhere to make it available.
What was expected:
Snappy response when waking from sleep and no unnecessary keystrokes/inputs
What I tried:
I tried deactivating GNOME shell extensions, but nothing changed
I see slack.desktop making lots of network requests—I wonder if that contributes some to the delay.
There’s this too:
gnome-shell[6200]: Usage of object.actor is deprecated for AuthPrompt
get@resource:///org/gnome/shell/ui/environment.js:317:29
_initEntryRow@resource:///org/gnome/shell/gdm/authPrompt.js:176:9
_init@resource:///org/gnome/shell/gdm/authPrompt.js:93:14
_ensureAuthPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:678:28
_showPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:717:14
vfunc_key_press_event@resource:///org/gnome/shell/ui/unlockDialog.js:617:14
which may be related to the the key press not bringing up the login/password screen,
and there are a few of these that look related to the keyring issue:
goa-daemon[6470]: secret_password_lookup_sync() returned NULL
goa-daemon[6470]: secret_password_lookup_sync() returned NULL
goa-daemon[6470]: secret_password_lookup_sync() returned NULL
goa-daemon[6470]: secret_password_lookup_sync() returned NULL
Just as a test, could you create a new user and see how suspend/resume works there? That’ll help us decide if its a system level issue or a user specific one.
That suggests it’s something specific to the account then. I guess comparing the suspend/resume logs when using the two users would be a start? That may tell us what components are running/behaving differently?
Oddly it seems the problem may have propagated to the new user as I’m encountering the same issue again: i.e screen remains black after resume, need to press a key to activate display.