After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 785359 - Unable to unlock after screen lock, often crashes and forced to restart manually
Unable to unlock after screen lock, often crashes and forced to restart manually
Status: RESOLVED OBSOLETE
Product: gdm
Classification: Core
Component: general
3.24.x
Other Linux
: Normal blocker
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2017-07-24 17:41 UTC by Inactive account
Modified: 2018-05-24 11:38 UTC
See Also:
GNOME target: ---
GNOME version: 3.23/3.24



Description Inactive account 2017-07-24 17:41:13 UTC
As of about a week or so ago, and not even after doing a package upgrade, I have noticed that when my machine suspends, that when I pull the shield up instead of "Unlock", the button says "Next", and no matter how many times I type the correct password it won't let me in.

In a lot of cases I also find that immediately, or after I have pressed enter or at some random point, the screen will either freeze or go black and force me to manually do a restart. In most cases I am also unable to switch to another TTY. And each time something like this is in the logs in regards to gnome-shell:

Jul 23 17:16:50 <computerName> NetworkManager[304]: <info> [1500826610.0777] manager: sleep requested (sleeping: no enabled: yes)
Jul 23 17:16:50 <computerName> NetworkManager[304]: <info> [1500826610.0778] manager: sleeping...
Jul 23 17:16:50 <computerName> gnome-software-service.desktop[1090]: 16:16:50:0148 GsPluginShellExtensions no app for changed alternate-tab@gnome-shell-extensi
Jul 23 17:16:50 <computerName> gnome-software-service.desktop[1090]: 16:16:50:0150 GsPluginShellExtensions no app for changed drive-menu@gnome-shell-extensions
Jul 23 17:16:50 <computerName> org.gnome.Shell.desktop[505]: Window manager warning: Failed to set power save mode for output LVDS-1: Permission denied
Jul 23 17:16:50 <computerName> wpa_supplicant[467]: nl80211: deinit ifname=wlp2s0b1 disabled_11b_rates=0
Jul 23 17:16:50 <computerName> NetworkManager[304]: <info> [1500826610.0780] device (wlp2s0b1): state change: unavailable -> unmanaged (reason 'sleeping', int
Jul 23 17:16:50 <computerName> gnome-software-service.desktop[1090]: 16:16:50:0160 GsPluginShellExtensions no app for changed activities-config@nls1729
Jul 23 17:16:50 <computerName> gnome-software-service.desktop[1090]: 16:16:50:0182 GsPluginShellExtensions no app for changed dash-to-dock@micxgx.gmail.com
Jul 23 17:16:50 <computerName> NetworkManager[304]: <info> [1500826610.0783] device (wlp2s0b1): set-hw-addr: reset MAC address to 68:94:23:F4:00:CD (unmanage)
Jul 23 17:16:50 <computerName> NetworkManager[304]: <info> [1500826610.0790] manager: NetworkManager state is now ASLEEP
Jul 23 17:16:50 <computerName> gnome-shell[505]: Screen lock is locked down, not locking
Jul 23 17:16:50 <computerName> gnome-shell[776]: JS ERROR: Error getting systemd inhibitor: Gio.IOErrorEnum: GDBus.Error:org.freedesktop.login1.OperationInProg
LoginManagerSystemd<.inhibit/<@resource:///org/gnome/shell/misc/loginManager.js:170:48
Jul 23 17:16:50 <computerName> systemd[1]: Reached target Sleep.
Jul 23 17:16:50 <computerName> systemd[1]: Starting Suspend...
Jul 23 17:16:50 <computerName> systemd-sleep[1513]: Suspending system...

When the issue first started it only blocked me from unlocking the machine, now it has the freezing and black screen business, and actually it's getting worse, more often than not now it just freezes when I move the mouse to try and open the shield, other times it doesn't even get to showing me anything on the screen and just stays black. On other times the little light indicating the caps locks will be flashing like mad even though I'm not doing anything relating to that.

This is a real menace and is really hampering with usability as it happens every time now even though it didn't in previous days, not all the time anyway. But now it does, this used to only include when it went to sleep because of the timeout, now it's also if I just close my laptop lid of my Lenovo B590. I have also found that when it goes crazy in this state, even when it hasn't crashed and just doesn't let me unlock it, if I close the lid or use the keyboard shortcut that normally works to make it go to sleep, nothing happens. On rare occasions I find that when I lift the shield the button says "Unlock" and if I race against time and I type in my password fast enough it may allow me to unlock, however, after a few seconds me typing my password the shield appears again and when I lift it back I'm back to the situation with the "Next" button.

My Arch system is kept up-to-date and I am running gnome-shell version 3.24.3.

Nobody else I know experiences this issue, although I don't know anyone else running Arch. So in case it has anything to do with implementation or anything in the distro I have also filed a report downstream: https://bugs.archlinux.org/task/54914
Comment 1 Inactive account 2017-07-26 15:24:56 UTC
The downstream bug was changed from gnome-shell to gdm so I thought I would also do so here. Hope that is right.
Comment 2 Inactive account 2017-07-26 15:33:31 UTC
I have tried doing a fresh install but the issue remains.
Comment 3 Hussam Al-Tayeb 2017-08-24 10:09:20 UTC
I reported something similar yesterday. Are you by any chance using auto-login?
If so, it may be bug 786656.
Comment 4 GNOME Infrastructure Team 2018-05-24 11:38:01 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gdm/issues/324.