Public bug reported:
dbus 1.6.18-0ubuntu4.3 for Ubuntu 14.04 installs a /etc/init.d/dbus
script that checks for /usr/bin/dbus-daemon instead of /bin/dbus-daemon
.
Evidently this is not a critical failure as something still starts a
system dbus on my system:
5 102 2423 1 1 0 41004 3304 - Ss ? 3:07
dbus-daemon --system --fork
Who, I haven't figured out yet. The usual suspect systemd seems to be
innocent here, because AFAICT it's supposed to start the daemon with a
different set of options:
ExecStart=//bin/dbus-daemon --system --address=systemd: --nofork
--nopidfile --systemd-activation
This makes it a little bit tricky to figure out how to relaunch the system dbus
daemon...
** Affects: dbus (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1624285
Title:
/etc/init.d/dbus checks for dbus-daemon in wrong location
Status in dbus package in Ubuntu:
New
Bug description:
dbus 1.6.18-0ubuntu4.3 for Ubuntu 14.04 installs a /etc/init.d/dbus
script that checks for /usr/bin/dbus-daemon instead of /bin/dbus-
daemon .
Evidently this is not a critical failure as something still starts a
system dbus on my system:
5 102 2423 1 1 0 41004 3304 - Ss ? 3:07
dbus-daemon --system --fork
Who, I haven't figured out yet. The usual suspect systemd seems to be
innocent here, because AFAICT it's supposed to start the daemon with a
different set of options:
ExecStart=//bin/dbus-daemon --system --address=systemd: --nofork
--nopidfile --systemd-activation
This makes it a little bit tricky to figure out how to relaunch the system
dbus daemon...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1624285/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
