dbus does not start again if not cleanly shutdown before

[Stefan Fleiter]

Binary package hint: dbus

if /var/run/dbus/pid exists, f.e. after dbus crashed,
it won't get started again until the pid file is manually removed.

The first bug ist that upstart does not recognize that dbus is not running
anymore.
Is this a bug in upstart or in dbus.conf?

The pid file should be removed if dbus is not running any more,
so dbus can be started again.
That is the second bug.

ProblemType: Bug
Architecture: amd64
Date: Sun Jan 17 19:04:10 2010
DistroRelease: Ubuntu 10.04
NonfreeKernelModules: nvidia
Package: dbus 1.2.16-2ubuntu2
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
SourcePackage: dbus
Tags: lucid
Uname: Linux 2.6.32-10-generic x86_64

[Daniel Hahler (blueyed)]

As far as I can see, upstart should have restarted dbus (there's "respawn" in the config).

Regarding the pid file, this cannot get removed if there's an unexpected crash.
Why wasn't dbus not starting before the file had been removed?

Well, "stop dbus" does not appear to stop dbus completely (the pid is gone, but 3 dbus-daemon processes still running).

I can confirm though, that with a file /var/run/dbus/pid in place (even if empty), dbus won't properly startup again, after having pkill'ed dbus-daemon, using "start dbus".
Removing the pid file made it start better, but the system is still borked, e.g. dbus-monitor cannot connect - that's another issue though probably (and maybe cannot get fixed at all).