Comment 15 for bug 395302

> Seinding HUP to gdm does not terminate it.

OK, you're right, I tried it :)

> It rather sounds like d-bus crashed during the upgrade

Seems you are right again:

martin /var/log # zgrep dbus syslog.1
Oct 14 19:57:29 martin dbus-daemon: Reloaded configuration
[...]
Oct 14 20:05:20 martin dbus-daemon: Reloaded configuration
Oct 14 20:11:52 martin avahi-daemon[32252]: dbus_bus_get_private(): Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[...]
Oct 14 20:11:52 martin init: dbus main process ended, respawning
Oct 14 20:12:38 martin init: dbus main process ended, respawning
Oct 14 20:12:50 martin init: dbus main process ended, respawning
Oct 14 20:12:50 martin init: dbus main process (5278) killed by KILL signal
Oct 14 20:12:50 martin init: dbus main process ended, respawning
Oct 14 20:12:50 martin init: dbus main process (5352) terminated with status 1
Oct 14 20:12:50 martin init: dbus main process ended, respawning
Oct 14 20:12:50 martin init: Unable to connect to the system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused

I'll attach the complete syslog and apt/term.log.

> Can you reproduce this somehow?

I have no idea how. I tried to run a few dbus related postinsts, but that caused nothing.

> Can you please check afterwards with "status dbus" and "status hal" whether they are running or stopped?

When it happens again, I'll try to login via ssh, and post the results.