Kubuntu Hangs on Shutdown (remote ssh still works)

[jbentham]

It seems that one of the recent updates is causing my laptop and desktop to hang on shutdown (running 2.6.24-24-generic on both).

Here are the symptoms and what I have tried so far:
- the mouse is still active, but screen is black
- Ctl-Alt-Del does not work
- SSH from another computer works and I can execute a shutdown from there
- from an SSH session, /var/log/syslog shows the following at the end (it may or may not be related):
>>
Oct 8 11:00:45 alet-winlin-01 avahi-daemon[5727]: Invalid query packet.
Oct 8 11:00:46 alet-winlin-01 last message repeated 2 times
<<
- I have not made any hardware or software changes; only updates

I am not sure what else to look for in solving this.

Any ideas on what the problem is or how to fix it?

[rb0171610]

Re: Kubuntu Hangs on Shutdown (remote ssh still works)

Try this:

1. Hit CTRL+ Alt + F2 to get to a TTY. (hit CTRL+ALT+F7 at any time to return to your desktop)
2. Login with your username and password
3. Type
sudo reboot -v
OR
sudo halt -v

The -v switch will make your reboot command (hopefully) more verbose. Take note of any terminal messages for an indication of what is causing the system to hang at shutdown.

[jbentham]

Re: Kubuntu Hangs on Shutdown (remote ssh still works)

Thanks for your reply, rb171610. I had forgotten the key sequence to pull up a tty (no need to ssh from my iPhone now).

I executed shutdown as you suggested; I didn't see anything out of the ordinary on the terminal session, so I copied the syslog output (see attached).

The key times are as follows:
- 10:13, executed a shutdown from the KDE menu where it subsequently hung the system (black screen with an active mouse)
- 10:16, hit Ctrl-Alt-F2 to get a tty, logged in and checked the time
- 10:18, executed shutdown -vh 0

To make it easier to read, I edited the syslog to only include times from the most recent boot to the shutdown.

I mentioned before that the avahi daemon seemed to be hanging, but after a closer look, could it be the NetworkManager at 10:18:38?

Any suggestions on what might be the problem?