On 23/11/15 20:11, Brent S. Elmer Ph.D. wrote:
> My system may have been in an odd state due to this bug causing the
> 1.10.4-1 upgrade to perpetuate the circular dependency. How do I get
> my system to a good state again?
Before doing anything to try to solve it, please show me the output of:
ls -la /etc/dbus-1/
Ideally, what you want (with uninteresting date/ownership/size columns
removed to avoid linewrapping) is something like this:
drwxr-xr-x [...] .
drwxr-xr-x [...] ..
lrwxrwxrwx [...] session.conf -> /usr/share/dbus-1/session.conf
drwxr-xr-x [...] session.d
lrwxrwxrwx [...] system.conf -> /usr/share/dbus-1/system.conf
drwxr-xr-x [...] system.d
*.dpkg-{dist,old,new} files are also OK. *.dpkg-bak are OK but only if
they are real files, not if they are symlinks into /usr/share/dbus-1/;
if in doubt, rename them out of the way.
If /etc/dbus-1/s*.conf.bak is a symlink into /usr/share/dbus-1/, delete
that symlink.
For completeness, also check that /usr/share/dbus-1/session.conf and
/usr/share/dbus-1/system.conf are real files, not symlinks. If not, move
them out of the way, then reinstall dbus (something like "sudo dpkg -i
/var/cache/apt/archives/dbus_1.10.4-1_*.deb" should work).
Having reached a stable state, "sudo service dbus reload" should work.
Please substitute your favourite way of running things as root if that
isn't sudo.
I'm reluctant to add any additional workarounds in the dbus package to
try to sort out your system automatically, because the bad situation
could only be hit by downgrading (which is unsupported anyway), and the
more special-case code I add to the maintainer scripts, the more likely
it is that I'll accidentally cause some regression for someone else.
S
