7

I have no idea how to start debugging this. My laptop is a Dell XPS 13, model 9333. The behaviour started when I upgraded to 15.04 (from 14.10), and to Gnome 3.16 (from 3.14). Unfortunately I'm not sure which upgrade caused it, because I did them both at the same time.

What happens is pretty straight forward. I hit shutdown, the shutdown process does its thing until the screen goes blank, but the laptop remains powered on (the little light at the front of the laptop, and the keyboard backlight, stay powered on).

When this happens my laptop does disconnect from Wi-Fi. Nothing appears to happen when I try to switch to other TTY (ctrl alt F1,2,3,4...) - perhaps something is happening and I'm not seeing it because the screen is off, I don't know. The machine DOES appear to disable it's wi-fi when I use the fn+wifi toggle button (because on my next boot the laptop is in "airplane mode").

The only way to power my laptop down when this happens is to hold the power button. After powering down like this I have sometimes (not always) had the next boot run a filesystem check and then dump me into an emergency console, where reviewing the logs in journalctl -xb tell me I need to run e2fsck on sda9 before I can boot - so I do that e2fsck /dev/sda9 -y and then reboot, and everything works fine.

Does anybody have any ideas how to start debugging this issue? Are there any logs I can check, and anything in particular to look for to identify why the laptop is not powering off?

Any help would be greatly appreciated.

Thanks, Rob

(edit) Looks like this must be a gnome 3.16 problem. Shutting down after logging into Unity works fine, but shutting down from the Gnome lock screen or from logging in to Gnome consistently fails. Any idea how to debug this further?

(edit 2) More info. Running sudo shutdown -h now fails when ran via a terminal window in Gnome. Running sudo shutdown -h now via tty1 (when logged in to gnome or when the gnome lock screen is open, on tty7 (i think)) results in a successful shutdown. Running sudo shutdown -h now via unity results in a successful shutdown. The problem is clearly confined to Gnome 3.16 then. :\

  • Same here! +1 I am using an Vostro 5470, Gnome 3.16 on Vivid, I did a fresh install. – fanl Apr 30 '15 at 21:56
  • Can you look at your shutdown messages behind the splash screen. Is 'Reached target Shutdown" the last message you see before it hangs? – xtrchessreal Mar 8 '16 at 19:31
1

I have upgraded to Gnome 3.16.1 and I am no longer having this problem. I'm guessing it was fixed by this change:

========================================
  gtk+
========================================

Overview of changes in GTK+ 3.16.2
==================================

* Bug fixes:
 [...]
 747689 [...]
        GtkApplication: Prevent more crashes around shutdown            
 [...]

from https://www.mirrorservice.org/sites/ftp.gnome.org/pub/GNOME/core/3.16/3.16.1/NEWS

protected by Community May 5 '15 at 19:13

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.