You are not logged in.
Hi All,
when lock my screen (or go into suspend), I cannont unlock my laptop ocasionally. I enter my password and hit enter then gdm does not take anymore input.
The log looks as follows (PC going to sleep at 9:33 and waking up again at 9:36):
-- Logs begin at Sa 2015-01-24 11:58:41 CET, end at Sa 2015-05-30 09:37:44 CEST. --
Mai 30 09:37:44 wolf /usr/lib/gdm/gdm-x-session[890]: (II) systemd-logind: got pause for 13:66
Mai 30 09:37:44 wolf /usr/lib/gdm/gdm-x-session[890]: (II) systemd-logind: got pause for 13:79
Mai 30 09:37:44 wolf /usr/lib/gdm/gdm-x-session[890]: (II) systemd-logind: got pause for 13:70
Mai 30 09:37:44 wolf /usr/lib/gdm/gdm-x-session[890]: (II) systemd-logind: got pause for 226:0
Mai 30 09:37:44 wolf /usr/lib/gdm/gdm-x-session[890]: (II) systemd-logind: got pause for 13:78
Mai 30 09:37:44 wolf /usr/lib/gdm/gdm-x-session[890]: (II) systemd-logind: got pause for 13:65
Mai 30 09:37:44 wolf /usr/lib/gdm/gdm-x-session[890]: (II) systemd-logind: got pause for 13:68
Mai 30 09:37:44 wolf /usr/lib/gdm/gdm-x-session[890]: (II) systemd-logind: got pause for 13:67
Mai 30 09:37:44 wolf /usr/lib/gdm/gdm-x-session[890]: (II) systemd-logind: got pause for 13:71
Mai 30 09:37:44 wolf /usr/lib/gdm/gdm-x-session[890]: (II) AIGLX: Suspending AIGLX clients for VT switch
Mai 30 09:36:10 wolf chromium.desktop[1663]: libpng warning: iCCP: cHRM chunk does not match sRGB
Mai 30 09:36:10 wolf chromium.desktop[1663]: libpng warning: iCCP: known incorrect sRGB profile
Mai 30 09:36:10 wolf chromium.desktop[1663]: libpng warning: iCCP: cHRM chunk does not match sRGB
Mai 30 09:36:10 wolf chromium.desktop[1663]: libpng warning: iCCP: known incorrect sRGB profile
Mai 30 09:33:46 wolf chromium.desktop[1663]: [1663:2889:0530/093346:ERROR:cert_verify_proc_nss.cc(886)] CERT_PKIXVerifyCert for 192.168.0.168 failed err=-8179
Mai 30 09:33:18 wolf gnome-session[899]: ** (gnome-shell:1030): CRITICAL **: nma_mobile_providers_database_lookup_cdma_sid: assertion 'sid > 0' failed
Mai 30 09:33:15 wolf org.gnome.evolution.dataserver.Calendar7[897]: (evolution-calendar-factory-subprocess:1358): e-cal-backend-caldav-WARNING **: Server did not response with SOUP_STATUS_MULTI_STATUS, but with code 500 (Internal Server Error)
Mai 30 09:33:14 wolf org.gnome.evolution.dataserver.Calendar7[897]: (evolution-calendar-factory-subprocess:1358): e-cal-backend-caldav-WARNING **: Server did not response with SOUP_STATUS_MULTI_STATUS, but with code 500 (Internal Server Error)
Mai 30 09:33:14 wolf org.gnome.evolution.dataserver.Calendar7[897]: (evolution-calendar-factory-subprocess:1358): e-cal-backend-caldav-WARNING **: Server did not response with SOUP_STATUS_MULTI_STATUS, but with code 500 (Internal Server Error)
Mai 30 09:33:14 wolf org.gnome.evolution.dataserver.Calendar7[897]: (evolution-calendar-factory-subprocess:1358): e-cal-backend-caldav-WARNING **: Server did not response with SOUP_STATUS_MULTI_STATUS, but with code 500 (Internal Server Error)
Mai 30 09:33:13 wolf chromium.desktop[1663]: libpng warning: iCCP: known incorrect sRGB profile
Mai 30 09:33:13 wolf chromium.desktop[1663]: libpng warning: iCCP: known incorrect sRGB profileSome times, unlocking works as expected. I cannot make any sense in when it happens. Does anybody have an idea, what could be the case?
Cheers,
Phylu
Offline
Can you switch to a different console using Ctrl-Alt-F2 (Or F3, F4 ....)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Yes. On tty1 I have the gdm login screen. The frozen session is on tty2. On tty3 (and further) I get my terminals and can login there.
Offline
Do you need any other information?
Offline
Sorry, I somehow missed your first response
IT appears that the computer does come out of sleep. I don't use gdm (or any other display manager) so I don't have many suggestions.
The log is not very interesting. Is that a user mode log?, or did you run that with root privileges or who is a member of either systemd-journal or wheel groups?
What happens if you don't have Chromium running?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
No problem.
Here is a log, created with root permissions: http://pastebin.com/tiaa9cnR (the other one was only a user log.)
Unfortunately, I hat Chromium running again. I need to remember closing it, when sending the laptop to sleep the next time.
Offline
I managed to trace it down to autofs. When I disable autofs, the problem disappears.
Here are my autofs config files: http://pastebin.com/qKS5Dx4b
Offline