Ubuntu
dbus package

Error upgrading from gutsy: “Element <standard_system_servicedirs> not allowed”

Bug #174148 reported by Anders Kaseorg
60
Affects Status Importance Assigned to Milestone
dbus (Ubuntu)
Won't Fix
Undecided
Unassigned
Nominated for Hardy by Anders Kaseorg

Bug Description

Binary package hint: dbus

I got this error when upgrading from a previous version of dbus.

Setting up dbus (1.1.2-1ubuntu1) ...
Installing new version of config file /etc/dbus-1/system.conf ...
Installing new version of config file /etc/init.d/dbus ...
The user `messagebus' already exists. Exiting.
 * Reloading system message bus config...
Error org.freedesktop.DBus.Error.Failed: Element <standard_system_servicedirs> not allowed inside <busconfig> in configuration file
invoke-rc.d: initscript dbus, action "reload" failed.

$ sudo /etc/init.d/dbus reload
 * Reloading system message bus config...
Error org.freedesktop.DBus.Error.Failed: Element <standard_system_servicedirs> not allowed inside <busconfig> in configuration file

My conffiles have not been modified from the defaults (according to md5sums from `dpkg-query -f '${Conffiles}\n' -W dbus`).

See original description
Revision history for this message
Stefan Fleiter (stefan-fleiter) wrote :

Same here since dbus 1.1.2-1ubuntu1 from hardy.

Changed in dbus:
status: New → Confirmed
Revision history for this message
Anders Kaseorg (andersk) wrote :

This might just be an upgrade problem, since dbus started fine after the next reboot. I’m guessing that dbus reload causes the old version of dbus to choke trying to read the new config file.

Revision history for this message
Loïc Minier (lool) wrote :

Yes, I confirm, /etc/init.d/dbus reload was failing, but restart worked; I think the dbus maintainer scripts should be changed to restart dbus for the upgrade of /etc/dbus-1/system.conf.

Revision history for this message
hackel (hackel) wrote :

I just got this again (8 Mar) upon upgrading feisty to hardy.

Revision history for this message
Olly Betts (ojwb) wrote :

Just noticed this upgrading from gutsy to hardy beta.

Anders Kaseorg (andersk)
description: updated
Revision history for this message
David N. Arnold (darnold) wrote :

This is still a problem. I got it upgrading today.

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Hardy is long-since out of the door, so we missed this one :-/

Changed in dbus (Ubuntu):
status: Confirmed → Won't Fix
Revision history for this message
Free Ekanayaka (free.ekanayaka) wrote :

Just to add one more voice, I confirm this issue is affecting Dapper->Hardy upgrades.

Note that Dapper is still a supported release, I'm wondering if there is some way this can be fixed with a dbus SRU target to dapper, hardy or both.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.