You are not logged in.
Pages: 1
When I installed Arch on my computer about half a year ago, the shutdown process from GNOME is quick. However, I discovered recently that after I hit the 'shutdown' button in GNOME it took a few seconds before desktop exits. I looked into it today by using journalctl and discovered a 5-second delay caused by inhibitor lock. The output is like this:
...(I believe that I pressed the shutdown button before here)
Jan 02 20:40:06 john-pc colord[483]: Automatic remove of icc-860bdce758c2d718868b91de369c98fa from xrandr-BOE
Jan 02 20:40:06 john-pc colord[483]: Profile removed: icc-860bdce758c2d718868b91de369c98fa
Jan 02 20:40:06 john-pc colord[483]: device removed: xrandr-BOE
Jan 02 20:40:11 john-pc systemd-logind[376]: Delay lock is active but inhibitor timeout is reached.
Jan 02 20:40:11 john-pc systemd-logind[376]: System is powering down.
...(The actual shutdown process happens here)
After this delay(between the third and fourth line) actual shutdown happens normally, which only takes about 3 seconds. So I believe that the delay is caused by a misconfigured inhibitor delay lock. After consulting the inhibitors I only find one delay inhibitor related to shutdown:
Who: Telepathy (UID 1000/dingbur, PID 679/mission-control)
What: shutdown:sleep
Why: Disconnecting IM accounts before suspend/shutdown...
Mode: delay
Is it the reason for the delay in shutdown and how can I resolve the problem?
Offline
I'm running into the same issue and also triaged the problem to mission-control-5 (telepathy).
https://bugs.freedesktop.org/show_bug.cgi?id=68758
The only workaround so far is to send a "kill" to mission control (e.g: kill 679) right before the shutdown/sleep.
Offline
An interesting thing I just discovered is that it is somehow related to Gnome. I tried LightDM + Cinnamon, it seems OK. However, if I change one of the thing (DM or Desktop Shell) to that of GNOME's (i.e. gdm or Gnome Shell), the problem will occur.
Offline
I'm running into the same issue and also triaged the problem to mission-control-5 (telepathy).
https://bugs.freedesktop.org/show_bug.cgi?id=68758
The only workaround so far is to send a "kill" to mission control (e.g: kill 679) right before the shutdown/sleep.
Yeah, you're right. Downgrading telepathy-mission-control to 5.14.1-1 also eliminates the problem. I think it is a bug in gnome-shell and gdm in which mission-control is perhaps improperly used and the problematic inhibitor is taken unintentionally due to the upgrade. I'll file a bug report to GNOME.
EDIT: Bug #721605 has been submitted to gnome-shell.
Last edited by jdbrown (2014-01-06 05:17:26)
Offline
Ok cool. I'm going to try downgrading too. Could you please post the bug id in this thread? Thanks
Offline
Offline
Dude awesome. Thanks for reporting and getting this resolved.
Offline
Pages: 1