GDM freeze in lockscreen

andrea993 · 2016-02-06 14:36:27

For two days when gnome goes in lock screen (after 5min of inactivity) often gdm stops responding, and I can't re-login in my session. I've tried to use Xorg in gdm instead of Wayland, but it does not fix. Next I've enabled the gdm debug. In gdm I can only move the mouse cursor but the PC stop responding to click and keyboard.

This is the journalctl log from same miunutes before the lockscreen and there are 2 my attempts to login in, where the log say:
GsmSystemd: received logind signal: SessionNew
GsmSystemd: ignoring SessionNew signal

https://arin.ga/LyG4uf

I've already try to reinstall gnome and xorg.

thanks a lot

EDIT: A work-around seem to be login with Wayland at system boot, but I would like to use Xorg

Last edited by andrea993 (2016-02-06 16:49:54)

wudu · 2016-02-06 15:04:40

Hi,
I have the same problem with lightdm. I still can hit "switch user" button in that situation and then reenter. Not sure if this is possible for GDM. Of course the problem itself remains but I can still unlock this way...

Hope this works for you as well.

andrea993 · 2016-02-06 15:07:21

No in GDM it is not possible because there is the spash image and I cant scroll it up with mouse or keyboard

MagicFish1990 · 2016-02-07 23:01:40

I have exactly the same issue.

birnard · 2016-02-09 04:19:30

I believe I have the same issue. Cannot unlock after suspend. Use GDM and Gnome 3 splash screen does not respond. I've been sudo rebooting from another tty.

adolchristin · 2016-02-09 14:24:49

One more here with the same issue, I've tried disabling wayland from gdm but I still have the issue.

birnard · 2016-02-12 04:15:03

I'm a real novice about troubleshooting, but looking at some logs these are my thoughts:

I checked pacman.log and gdm and libgdm have not been updated since 2015-11-19, so it might not be a gdm bug directly that is causing my problem.

I ran

systemctl status gdm.service

.

● gdm.service - GNOME Display Manager
   Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2016-02-11 06:16:42 EST; 10h ago
 Main PID: 504 (gdm)
    Tasks: 3 (limit: 512)
   CGroup: /system.slice/gdm.service
           └─504 /usr/bin/gdm

Feb 11 06:16:42 brianarch systemd[1]: Started GNOME Display Manager.
Feb 11 06:16:42 brianarch gdm[504]: GdmDisplay: display lasted 0.256315 seconds
Feb 11 06:16:42 brianarch gdm[504]: Child process -532 was already dead.
Feb 11 06:16:42 brianarch gdm[504]: Child process 521 was already dead.
Feb 11 06:16:42 brianarch gdm[504]: Unable to kill session worker process
Feb 11 06:16:51 brianarch gdm-password][746]: pam_unix(gdm-password:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=  user=brian
Feb 11 06:16:56 brianarch gdm-password][791]: pam_unix(gdm-password:auth): conversation failed
Feb 11 06:16:56 brianarch gdm-password][791]: pam_unix(gdm-password:auth): auth could not identify password for [brian]
Feb 11 06:16:56 brianarch gdm-password][791]: gkr-pam: no password is available for user
Feb 11 06:17:04 brianarch gdm-password][795]: pam_unix(gdm-password:session): session opened for user brian by (uid=0)

So I thought something was interfering with the credentials lookup at the lockscreen. After some googling and poking around I (almost) randomly noticed that /etc/shadow and /etc/gshadow had permissions 000. That seemed weird and I saw this post:
http://bbs.archlinux.org/viewtopic.php?id=193783

So following that post I changed permissions to 600. This is really a shot in the dark, but since I haven't found any other solutions I'll just keep trying until something works. I'll report back if it locks up again.

P.S. The lockscreen initially would only get stuck sometimes. For example if I set the power settings to screenoff in 60 seconds then unlocked, it would still work. But if I left my computer on for 2 hours unattended it would usually get stuck when I tried to unlock. So it might take a bit before I'm sure it is fixed.

------------------------------------
EDIT:

Okay, still locking up. I can create a new thread if that is better, but I didn't know if I should considering it might be the same issue as others are having.
Here is the bottom of my journalctl log.

Feb 12 02:03:04 brianarch gnome-session[764]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2a00005 specified for 0x2a0010c (TeXstudio).
Feb 12 02:05:19 brianarch dbus[456]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Feb 12 02:05:19 brianarch systemd[1]: Starting Hostname Service...
Feb 12 02:05:19 brianarch dbus[456]: [system] Successfully activated service 'org.freedesktop.hostname1'
Feb 12 02:05:19 brianarch systemd[1]: Started Hostname Service.
Feb 12 02:06:11 brianarch dbus[456]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Feb 12 02:06:11 brianarch systemd[1]: Starting Hostname Service...
Feb 12 02:06:11 brianarch dbus[456]: [system] Successfully activated service 'org.freedesktop.hostname1'
Feb 12 02:06:11 brianarch systemd[1]: Started Hostname Service.
Feb 12 02:06:39 brianarch dbus-daemon[775]: Activating service name='org.gnome.evince.Daemon'
Feb 12 02:06:39 brianarch dbus-daemon[775]: Successfully activated service 'org.gnome.evince.Daemon'
Feb 12 02:07:05 brianarch dbus[456]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Feb 12 02:07:05 brianarch systemd[1]: Starting Hostname Service...
Feb 12 02:07:05 brianarch dbus[456]: [system] Successfully activated service 'org.freedesktop.hostname1'
Feb 12 02:07:05 brianarch systemd[1]: Started Hostname Service.
Feb 12 02:07:17 brianarch dbus-daemon[775]: Activating service name='org.gnome.evince.Daemon'
Feb 12 02:07:17 brianarch dbus-daemon[775]: Successfully activated service 'org.gnome.evince.Daemon'
Feb 12 02:14:53 brianarch gnome-session[764]: (gnome-shell:842): Clutter-CRITICAL **: clutter_layout_manager_get_child_meta: assertion 'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed
Feb 12 02:14:53 brianarch gnome-session[764]: (gnome-shell:842): GLib-GObject-CRITICAL **: g_object_set: assertion 'G_IS_OBJECT (object)' failed
Feb 12 02:14:53 brianarch gnome-session[764]: (gnome-shell:842): GLib-GObject-CRITICAL **: g_object_set: assertion 'G_IS_OBJECT (object)' failed
Feb 12 02:14:53 brianarch gnome-session[764]: (gnome-shell:842): St-CRITICAL **: st_widget_get_theme_node called on the widget [0x34993c0 ShellGenericContainer "dash"] which is not in the stage.
Feb 12 02:14:53 brianarch gnome-session[764]: (gnome-shell:842): Clutter-CRITICAL **: clutter_layout_manager_get_child_meta: assertion 'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed
Feb 12 02:14:53 brianarch gnome-session[764]: (gnome-shell:842): GLib-GObject-CRITICAL **: g_object_set: assertion 'G_IS_OBJECT (object)' failed
Feb 12 02:14:53 brianarch gnome-session[764]: (gnome-shell:842): GLib-GObject-CRITICAL **: g_object_set: assertion 'G_IS_OBJECT (object)' failed
Feb 12 02:14:53 brianarch gnome-session[764]: (gnome-shell:842): St-CRITICAL **: st_widget_get_theme_node called on the widget [0x3e78cc0 ShellGenericContainer "dash"] which is not in the stage.
Feb 12 04:34:08 brianarch /usr/lib/gdm/gdm-x-session[757]: (WW) RADEON(0): radeon_dri2_flip_event_handler: Pageflip completion event has impossible msc 52226805 < target_msc 52226806
Feb 12 04:35:02 brianarch /usr/lib/gdm/gdm-x-session[757]: (II) AIGLX: Suspending AIGLX clients for VT switch
Feb 12 04:35:02 brianarch /usr/lib/gdm/gdm-x-session[757]: (II) systemd-logind: got pause for 13:67
Feb 12 04:35:02 brianarch /usr/lib/gdm/gdm-x-session[757]: (II) systemd-logind: got pause for 13:68
Feb 12 04:35:02 brianarch systemd[1]: Started Getty on tty3.
Feb 12 04:35:02 brianarch /usr/lib/gdm/gdm-x-session[757]: (II) systemd-logind: got pause for 13:69
Feb 12 04:35:02 brianarch /usr/lib/gdm/gdm-x-session[757]: (II) systemd-logind: got pause for 13:66
Feb 12 04:35:02 brianarch /usr/lib/gdm/gdm-x-session[757]: (II) systemd-logind: got pause for 13:64
Feb 12 04:35:02 brianarch /usr/lib/gdm/gdm-x-session[757]: (II) systemd-logind: got pause for 226:0
Feb 12 04:35:02 brianarch /usr/lib/gdm/gdm-x-session[757]: (II) systemd-logind: got pause for 13:70
Feb 12 04:35:02 brianarch /usr/lib/gdm/gdm-x-session[757]: (II) systemd-logind: got pause for 13:65
Feb 12 04:35:13 brianarch login[6189]: pam_unix(login:session): session opened for user brian by LOGIN(uid=0)
Feb 12 04:35:13 brianarch systemd-logind[466]: New session c4 of user brian.
Feb 12 04:35:13 brianarch systemd[1]: Started Session c4 of user brian.
Feb 12 04:35:13 brianarch login[6189]: LOGIN ON tty3 BY brian
Feb 12 04:38:05 brianarch sudo[6326]:    brian : TTY=tty3 ; PWD=/home/brian ; USER=root ; COMMAND=/usr/bin/journalctl -e
Feb 12 04:38:05 brianarch sudo[6326]: pam_unix(sudo:session): session opened for user root by brian(uid=0)
Feb 12 04:39:39 brianarch sudo[6326]: pam_unix(sudo:session): session closed for user root
Feb 12 04:40:18 brianarch sudo[6348]:    brian : TTY=tty3 ; PWD=/home/brian ; USER=root ; COMMAND=/usr/bin/journalctl -e
Feb 12 04:40:18 brianarch sudo[6348]: pam_unix(sudo:session): session opened for user root by brian(uid=0)

Last edited by birnard (2016-02-12 09:47:48)

quoj · 2016-02-14 16:03:45

I am having the same issue as the posters above -- freeze at lock screen (after inactivity). This happens either all the time or almost all the time. My last full system upgrade was Feb 12. I'll perform a system upgrade now and see if this persists.

paulo_cv · 2016-02-18 16:48:18

Same issue with system up to date. The only way to recover my desktop is to restart gdm (systemctl restart gdm) which obviously kills the X session and closes all open applications which might result in loss of work.

RinCat · 2016-02-23 17:57:33

Any update?
I still encountered this problem.

birnard · 2016-02-23 21:42:17

I'm still having issue, just avoiding using the lock screen for now.

Shot in the dark, is everyone using radeon? Seems OP and me both have (WW) RADEON(0): radeon_dri2_flip_event_handler: Pageflip completion event has impossible msc ....

mmarzantowicz · 2016-02-23 23:29:28

birnard wrote:

I'm still having issue, just avoiding using the lock screen for now.
Shot in the dark, is everyone using radeon? Seems OP and me both have (WW) RADEON(0): radeon_dri2_flip_event_handler: Pageflip completion event has impossible msc ....

I have the same issue (gdm freezes) on Radeon HD 5770 but not on Intel Poulsbo so it might be related to graphics card.

jwb · 2016-02-24 16:19:27

Same here on Radeon HD 6400 Series.

RinCat · 2016-02-25 04:22:49

birnard wrote:

I'm still having issue, just avoiding using the lock screen for now.
Shot in the dark, is everyone using radeon? Seems OP and me both have (WW) RADEON(0): radeon_dri2_flip_event_handler: Pageflip completion event has impossible msc ....

But I have Intel + Nvidia...

thor77 · 2016-02-29 12:05:10

Same issue here with Radeon HD 7800 Series.

You can get back to your session without loosing any work by following these steps:
Switch to a different tty

Strg+Alt+3/4/5

Search for the PID of gnome-shell

ps x | grep gnome-shell

Kill it

kill -9 <PID>

and now switch back to your gdm-tty (probably 1 or 2).
After some time the lockscreen will appear again and you're able to unlock your screen.

didierg · 2016-02-29 15:52:10

birnard wrote:

I'm still having issue, just avoiding using the lock screen for now.
Shot in the dark, is everyone using radeon? Seems OP and me both have (WW) RADEON(0): radeon_dri2_flip_event_handler: Pageflip completion event has impossible msc ....

Apologizes, I am not an Archilinux user but a Fedora one...

I have exactly the same behavior with same message using gnome-shell and a Radeon R9 270X.

thor77 · 2016-02-29 18:05:35

Is anyone also using a patched version of gdm?
I'm using gdm-plymouth.
@didierg you are probably also using Plymouth (preinstalled on Fedora for boot-screen-stuff) => patched version

jwb · 2016-02-29 19:53:20

And now, a few reboots and some (seemingly unrelated) package updates later, the problem seems gone--I can't reproduce it. Anybody else have it mysteriously clear up?

jwb · 2016-02-29 20:27:05

jwb wrote:

And now, a few reboots and some (seemingly unrelated) package updates later, the problem seems gone--I can't reproduce it. Anybody else have it mysteriously clear up?

Ah, never mind. And the 'kill -9' for gnome-shell isn't working either--gnome-shell restarts, but doesn't seem to actually be running--no desktop background, mouse-clicks ignored, etc. Let's just say, it worked a couple of times, and now again it's not.

RinCat · 2016-03-03 06:07:14

Hi all, I've got the log with debug flag, but I'm not found where is the issue. gdm seems ok, so the issue is in gnome-shell?

Mar 03 00:36:25 gdm[678]: GdmManager: trying to open reauthentication channel for user USERNAME-ABC
Mar 03 00:36:25 gdm[678]: GdmSession: Creating D-Bus server for worker for session
Mar 03 00:36:25 gdm[678]: GdmSession: D-Bus server for workers listening on unix:abstract=/tmp/dbus-Lqh83Jke
Mar 03 00:36:25 gdm[678]: GdmSession: Creating D-Bus server for greeters and such
Mar 03 00:36:25 gdm[678]: GdmSession: D-Bus server for greeters listening on unix:abstract=/tmp/dbus-pyXYoKcB
Mar 03 00:36:25 gdm[678]: GdmSession: Setting display device: (null)
Mar 03 00:36:25 gdm[678]: GdmSession: Disposing session
Mar 03 00:36:25 gdm[678]: GdmSession: Closing session
Mar 03 00:36:25 gdm[678]: GdmSession: Stopping all conversations
Mar 03 00:36:25 gdm[678]: GdmDBusServer: new connection 0x184dc30
Mar 03 00:36:25 gdm[678]: GdmSession: Handling new connection from outside
Mar 03 00:36:25 gdm[678]: GdmManager: client connected to reauthentication server
Mar 03 00:36:25 gdm[678]: GdmSession: starting conversation gdm-password
Mar 03 00:36:25 gdm[678]: GdmSessionWorkerJob: Starting worker...
Mar 03 00:36:25 gdm[678]: GdmSessionWorkerJob: Running session_worker_job process: gdm-session-worker [pam/gdm-password] /usr/lib/gdm/gdm-session-worker
Mar 03 00:36:25 gdm[678]: GdmSessionWorkerJob: : SessionWorkerJob on pid 32437
Mar 03 00:36:25 gdm-password][32437]: Enabling debugging
Mar 03 00:36:25 gdm-password][32437]: GdmSessionWorker: connecting to address: unix:abstract=/tmp/dbus-Lqh83Jke
Mar 03 00:36:25 gdm[678]: GdmDBusServer: new connection 0x7f07cc0098c0
Mar 03 00:36:25 gdm[678]: GdmSession: Handling new connection from worker
Mar 03 00:36:25 gdm[678]: GdmSession: Authenticating new connection
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: calling 'ListCachedUsers'
Mar 03 00:36:25 gdm-password][32437]: AccountsService: Failed to identify the current session: No such device or address
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: seat unloaded, so trying to set loaded property
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: Listing cached users, so not setting loaded property
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: Listing cached users, so not setting loaded property
Mar 03 00:36:25 gdm[678]: GdmSession: worker connection is 0x7f07cc0098c0
Mar 03 00:36:25 gdm[678]: GdmSession: Emitting conversation-started signal
Mar 03 00:36:25 gdm[678]: GdmManager: reauthentication service 'gdm-password' started
Mar 03 00:36:25 gdm[678]: GdmSession: Setting user: 'USERNAME-ABC'
Mar 03 00:36:25 gdm[678]: GdmSession: Beginning setup for user USERNAME-ABC
Mar 03 00:36:25 gdm[678]: GdmSession: Conversation started
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: ListCachedUsers finished, will set loaded property after list is fully loaded
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: tracking new user with object path /org/freedesktop/Accounts/User1000
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: tracking new user with object path /org/freedesktop/Accounts/User1001
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: unrefing manager owned by finished ListCachedUsers call
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: trying to track new user with username USERNAME-ABC
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: finding user 'USERNAME-ABC' state 1
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: waiting for user manager to load before finding user 'USERNAME-ABC'
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: user USERNAME-ABC is now loaded
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: user USERNAME-ABC was not yet known, adding it
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: tracking user 'USERNAME-ABC'
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: not yet loaded, so not emitting user-added signal
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: not all users loaded yet
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: no pending users, trying to set loaded property
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: Seat wouldn't load, so giving up on it and setting loaded property
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: user manager now loaded, proceeding with fetch user request for user 'USERNAME-ABC'
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: finding user 'USERNAME-ABC' state 2
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: Looking for user 'USERNAME-ABC' in accounts service
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: Found object path of user 'USERNAME-ABC': /org/freedesktop/Accounts/User1000
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: finding user 'USERNAME-ABC' state 3
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: user 'USERNAME-ABC' fetched
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: finished handling request for user 'USERNAME-ABC'
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: unrefing manager owned by fetch user request
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: user USERNAME-ABC is now loaded
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: sessions changed (user USERNAME-ABC) num=0
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: no pending users, trying to set loaded property
Mar 03 00:36:25 gdm-password][32437]: AccountsService: ActUserManager: already loaded, so not setting loaded property
Mar 03 00:36:25 gdm-password][32437]: GdmSessionSettings: saved session is gnome
Mar 03 00:36:25 gdm-password][32437]: GdmSessionWorker: Saved session is gnome
Mar 03 00:36:25 gdm-password][32437]: GdmSessionSettings: saved language is en_US.UTF-8
Mar 03 00:36:25 gdm-password][32437]: GdmSessionWorker: Saved language is en_US.UTF-8
Mar 03 00:36:25 gdm-password][32437]: GdmSessionWorker: queuing setup for user: USERNAME-ABC
Mar 03 00:36:25 gdm-password][32437]: GdmSessionWorker: attempting to change state to SETUP_COMPLETE
Mar 03 00:36:25 gdm-password][32437]: GdmSessionWorker: initializing PAM; service=gdm-password username=USERNAME-ABC seat=seat0
Mar 03 00:36:25 gdm[678]: GdmSession: getting session command for file 'gnome.desktop'
Mar 03 00:36:25 gdm[678]: GdmSession: getting session command for file 'gnome.desktop'
Mar 03 00:36:25 gdm-password][32437]: GdmSessionWorker: Set PAM environment variable: 'XDG_SEAT=seat0'
Mar 03 00:36:25 gdm-password][32437]: GdmSessionWorker: state SETUP_COMPLETE
Mar 03 00:36:25 gdm-password][32437]: GdmSessionWorker: attempting to change state to AUTHENTICATED
Mar 03 00:36:25 gdm-password][32437]: GdmSessionWorker: authenticating user USERNAME-ABC
Mar 03 00:36:25 gdm-password][32437]: GdmSessionWorker: 1 new messages received from PAM
Mar 03 00:36:25 gdm-password][32437]: GdmSessionWorker: username is 'USERNAME-ABC'
Mar 03 00:36:25 gdm-password][32437]: GdmSessionWorker: old-username='USERNAME-ABC' new-username='USERNAME-ABC'
Mar 03 00:36:25 gdm-password][32437]: GdmSessionWorker: received pam message of type 1 with payload 'Password: '
Mar 03 00:36:26 gdm-password][32437]: GdmSessionWorker: trying to get updated username
Mar 03 00:36:26 gdm-password][32437]: GdmSessionWorker: PAM conversation returning 0: Success
Mar 03 00:36:26 gdm-password][32437]: GdmSessionWorker: state AUTHENTICATED
Mar 03 00:36:26 gdm-password][32437]: GdmSessionWorker: trying to get updated username
Mar 03 00:36:26 gdm-password][32437]: GdmSessionWorker: username is 'USERNAME-ABC'
Mar 03 00:36:26 gdm-password][32437]: GdmSessionWorker: old-username='USERNAME-ABC' new-username='USERNAME-ABC'
Mar 03 00:36:26 gdm-password][32437]: GdmSessionWorker: attempting to change state to AUTHORIZED
Mar 03 00:36:26 gdm-password][32437]: GdmSessionWorker: determining if authenticated user (password required:0) is authorized to session
Mar 03 00:36:26 gdm-password][32437]: GdmSessionWorker: state AUTHORIZED
Mar 03 00:36:26 gdm-password][32437]: GdmSessionWorker: attempting to change state to ACCREDITED
Mar 03 00:36:26 gdm-password][32437]: GdmSessionWorker: Set PAM environment variable: 'LOGNAME=USERNAME-ABC'
Mar 03 00:36:26 gdm-password][32437]: GdmSessionWorker: Set PAM environment variable: 'USER=USERNAME-ABC'
Mar 03 00:36:26 gdm-password][32437]: GdmSessionWorker: Set PAM environment variable: 'USERNAME=USERNAME-ABC'
Mar 03 00:36:26 gdm-password][32437]: GdmSessionWorker: Set PAM environment variable: 'HOME=/home/USERNAME-ABC'
Mar 03 00:36:26 gdm-password][32437]: GdmSessionWorker: Set PAM environment variable: 'SHELL=/bin/zsh'
Mar 03 00:36:26 gdm-password][32437]: GdmSessionWorker: Set PAM environment variable: 'PATH=/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin'
Mar 03 00:36:26 gdm-password][32437]: GdmSessionWorker: state ACCREDITED
Mar 03 00:36:26 gdm[678]: GdmManager: reauthenticated user in unmanaged session 'c2' with service 'gdm-password'
Mar 03 00:36:26 gdm[678]: Unlocking session c2
Mar 03 00:36:26 gdm[678]: GdmSession: Closing session
Mar 03 00:36:26 gdm[678]: GdmSession: Stopping all conversations
Mar 03 00:36:26 gdm[678]: GdmSessionWorkerJob: Stopping job pid:32437
Mar 03 00:36:26 gdm[678]: GdmCommon: sending signal 15 to process 32437
Mar 03 00:36:26 gdm[678]: GdmSessionWorkerJob: Waiting on process 32437
Mar 03 00:36:26 gdm-password][32437]: Worker finished
Mar 03 00:36:26 gdm[678]: GdmCommon: process (pid:32437) done (status:0)
Mar 03 00:36:26 gdm[678]: GdmSessionWorkerJob: SessionWorkerJob died
Mar 03 00:36:26 gdm[678]: GdmSession: Disposing session
Mar 03 00:36:26 gdm[678]: GdmSession: Closing session
Mar 03 00:36:26 gdm[678]: GdmSession: Stopping all conversations
Mar 03 00:36:39 /usr/lib/gdm/gdm-x-session[1205]: (II) AIGLX: Suspending AIGLX clients for VT switch
Mar 03 00:36:39 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got pause for 13:66
Mar 03 00:36:39 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got pause for 13:80
Mar 03 00:36:39 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got pause for 13:65
Mar 03 00:36:39 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got pause for 13:70
Mar 03 00:36:39 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got pause for 226:0
Mar 03 00:36:39 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got pause for 13:67
Mar 03 00:36:39 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got pause for 13:79
Mar 03 00:36:39 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got pause for 13:69
Mar 03 00:36:39 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got pause for 13:78
Mar 03 00:36:39 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got pause for 13:68
Mar 03 00:36:39 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got pause for 13:71
Mar 03 00:36:39 /usr/lib/gdm/gdm-wayland-session[815]: gnome-session-binary[818]: DEBUG(+): emitting SessionIsActive
Mar 03 00:36:39 gnome-session-binary[818]: DEBUG(+): emitting SessionIsActive
Mar 03 00:36:39 /usr/lib/gdm/gdm-wayland-session[815]: gnome-session-binary[818]: DEBUG(+): GsmPresence: setting idle: 0
Mar 03 00:36:39 /usr/lib/gdm/gdm-wayland-session[815]: gnome-session-binary[818]: DEBUG(+): Updating systemd idle status: 0
Mar 03 00:36:39 gnome-session-binary[818]: DEBUG(+): GsmPresence: setting idle: 0
Mar 03 00:36:39 /usr/lib/gdm/gdm-wayland-session[815]: gnome-session-binary[818]: DEBUG(+): GsmPresence: setting non-idle status 0
Mar 03 00:36:39 gnome-session-binary[818]: DEBUG(+): Updating systemd idle status: 0
Mar 03 00:36:39 gnome-session-binary[818]: DEBUG(+): GsmPresence: setting non-idle status 0
Mar 03 00:36:40 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got resume for 13:66
Mar 03 00:36:40 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got resume for 13:80
Mar 03 00:36:40 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got resume for 13:65
Mar 03 00:36:40 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got resume for 13:70
Mar 03 00:36:40 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got resume for 226:0
Mar 03 00:36:40 /usr/lib/gdm/gdm-x-session[1205]: (II) AIGLX: Resuming AIGLX clients after VT switch
Mar 03 00:36:40 /usr/lib/gdm/gdm-x-session[1205]: (II) intel(0): switch to mode 1920x1080@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none
Mar 03 00:36:40 /usr/lib/gdm/gdm-wayland-session[815]: gnome-session-binary[818]: DEBUG(+): emitting SessionIsActive
Mar 03 00:36:40 gnome-session-binary[818]: DEBUG(+): emitting SessionIsActive
Mar 03 00:36:40 /usr/lib/gdm/gdm-x-session[1205]: (**) Option "Device" "/dev/input/event16"
Mar 03 00:36:40 /usr/lib/gdm/gdm-x-session[1205]: (--) synaptics: ETPS/2 Elantech Touchpad: touchpad found
Mar 03 00:36:40 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got resume for 13:67
Mar 03 00:36:40 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got resume for 13:79
Mar 03 00:36:40 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got resume for 13:69
Mar 03 00:36:40 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got resume for 13:78
Mar 03 00:36:40 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got resume for 13:68
Mar 03 00:36:40 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got resume for 13:71
Mar 03 00:36:44 /usr/lib/gdm/gdm-x-session[1205]: (II) AIGLX: Suspending AIGLX clients for VT switch
Mar 03 00:36:44 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got pause for 13:66
Mar 03 00:36:44 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got pause for 13:80
Mar 03 00:36:44 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got pause for 13:65
Mar 03 00:36:44 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got pause for 13:70
Mar 03 00:36:44 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got pause for 226:0
Mar 03 00:36:44 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got pause for 13:67
Mar 03 00:36:44 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got pause for 13:79
Mar 03 00:36:44 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got pause for 13:69
Mar 03 00:36:44 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got pause for 13:78
Mar 03 00:36:44 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got pause for 13:68
Mar 03 00:36:44 /usr/lib/gdm/gdm-x-session[1205]: (II) systemd-logind: got pause for 13:71
Mar 03 00:36:44 /usr/lib/gdm/gdm-wayland-session[815]: gnome-session-binary[818]: DEBUG(+): emitting SessionIsActive
Mar 03 00:36:44 gnome-session-binary[818]: DEBUG(+): emitting SessionIsActive

paulo_cv · 2016-03-09 16:17:06

Still having the issue, also a Radeon user (Oland PRO [Radeon R7 240/340]). I had to switch to i3 in the meantime which isn't bad at all but I would like to be able to use gnome :@

birnard · 2016-03-22 09:45:28

For a while I disabled the lockscreen, but now I switched to the catalyst drivers. I re-enabled gnome-lockscreen and it has not locked up yet. (Fingers crossed.) I'd like to use Mesa, but another benefit of the proprietary is it fixed some issues I had on some steam games.

edit:

RinCat wrote:

Hi all, I've got the log with debug flag, but I'm not found where is the issue. gdm seems ok, so the issue is in gnome-shell?

Oh and I forgot to say, I think you are spot on RinCat. Maybe the thread title has confused people. I personally, in my neophyte ignorance, didn't completely separate them in my mind since both greet me with a password prompt.

Last edited by birnard (2016-03-23 08:07:21)

duo8 · 2016-03-23 04:56:57

Same issue here for 2 months now.
Also use AMD card (HD7750).

velle_frak · 2016-03-23 08:35:42

I'm having the issue as well since 2 months.

I have a

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670]

I wonder if this is related to

https://bugzilla.redhat.com/show_bug.cgi?id=1318439

Maybe kernel 4.4.6 will solve this problem.

jwb · 2016-03-23 14:27:37

birnard wrote:

For a while I disabled the lockscreen, but now I switched to the catalyst drivers. I re-enabled gnome-lockscreen and it has not locked up yet. (Fingers crossed.) I'd like to use Mesa, but another benefit of the proprietary is it fixed some issues I had on some steam games.

I tried catalyst, too, but after sitting overnight the same problem showed up again.

Arch Linux

#1 2016-02-06 14:36:27

GDM freeze in lockscreen

#2 2016-02-06 15:04:40

Re: GDM freeze in lockscreen

#3 2016-02-06 15:07:21

Re: GDM freeze in lockscreen

#4 2016-02-07 23:01:40

Re: GDM freeze in lockscreen

#5 2016-02-09 04:19:30

Re: GDM freeze in lockscreen

#6 2016-02-09 14:24:49

Re: GDM freeze in lockscreen

#7 2016-02-12 04:15:03

Re: GDM freeze in lockscreen

#8 2016-02-14 16:03:45

Re: GDM freeze in lockscreen

#9 2016-02-18 16:48:18

Re: GDM freeze in lockscreen

#10 2016-02-23 17:57:33

Re: GDM freeze in lockscreen

#11 2016-02-23 21:42:17

Re: GDM freeze in lockscreen

#12 2016-02-23 23:29:28

Re: GDM freeze in lockscreen

#13 2016-02-24 16:19:27

Re: GDM freeze in lockscreen

#14 2016-02-25 04:22:49

Re: GDM freeze in lockscreen

#15 2016-02-29 12:05:10

Re: GDM freeze in lockscreen

#16 2016-02-29 15:52:10

Re: GDM freeze in lockscreen

#17 2016-02-29 18:05:35

Re: GDM freeze in lockscreen

#18 2016-02-29 19:53:20

Re: GDM freeze in lockscreen

#19 2016-02-29 20:27:05

Re: GDM freeze in lockscreen

#20 2016-03-03 06:07:14

Re: GDM freeze in lockscreen

#21 2016-03-09 16:17:06

Re: GDM freeze in lockscreen

#22 2016-03-22 09:45:28

Re: GDM freeze in lockscreen

#23 2016-03-23 04:56:57

Re: GDM freeze in lockscreen

#24 2016-03-23 08:35:42

Re: GDM freeze in lockscreen

#25 2016-03-23 14:27:37

Re: GDM freeze in lockscreen

Board footer