retitle 793519 after upgrade to 1.9.18, reloading bus config does not work until system is rebooted forwarded 793519 https://bugs.freedesktop.org/show_bug.cgi?id=89280#c30
On 24/07/15 20:33, 積丹尼 Dan Jacobson wrote: > Installing new version of config file /etc/dbus-1/session.conf ... > Installing new version of config file /etc/dbus-1/system.conf ... > A reboot is required to replace the running dbus-daemon. > Please reboot the system when convenient. > Error org.freedesktop.DBus.Error.Failed: Configuration file needs one or more > <listen> elements giving addresses This is a known and unavoidable consequence of the change to how bus setup works in 1.9.18; the stub configuration file in /etc/dbus-1 as installed by 1.9.18 is not a valid configuration file for whatever you were upgrading from (assuming << 1.9.18). For those not using development-branch releases, the only time this is encountered would be on upgrade from 1.8 (jessie) to 1.10 (stretch, soon). The maintainer script already advised you to reboot when convenient, so I don't consider it to be a major issue that the bus configuration can't be reloaded (e.g. to allow a newly installed D-Bus system service to work) until you have done so. However, it's good to have a bug documenting this. I don't think this can be made to work better while still achieving the goal that basic bus setup moves to /usr and dbus-daemon can be run without error with an empty /etc, without at least one of these bad effects: * breaking upgrades on systems where the sysadmin has edited /etc/dbus-1/system.conf (which Debian policy says they may, but comments in the file say they should not) * potentially leaving system.conf in a state where changes in subsequent dbus upgrades do not take effect (which could result in security vulnerabilities remaining unfixed) * setting up a cyclic <include> loop between /etc and /usr Suggestions welcome, but please read the various config files and https://bugs.freedesktop.org/show_bug.cgi?id=89280 first, to get the context and rule out things we already considered. Any dbus upgrade in which we added new syntax <foo/> for system.conf, and used <foo/> in the new system.conf, would have the same problem. S -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
