Unfortunately the fix mentioned does not always work, at least on 8.04 I tried to apply the fix: run "sudo /etc/init.d/dbus restart" then re- run services-admin and re-enable dbus
on running gksudo services-admin I get ** (services-admin:6299) CRITICAL **: The permission of the setuid helper is not correct And... once again teh fatal.. the configuration could not be loaded. Once dbus is stopped, for whatever reason, the network and other items needed to upgrade or get repairs become innaccessible/unusable. Essentially, stopping this servcie is immediately unrecoverable and will force me to apply a complete re-installation of Ubuntu. Why not just mark it with "Click here to waste three hours hunting obscure configuration defects and then enjoy a full re-install, kiss your data goodbye" I have tried to follow the debate and direction being attempted here and frankly it seems like a poorly thought out hack being forced in during migration to 8.10. At the very least stopping dbus should come with a warning that the user will probably have to perform a re-install to get a usable system again. This is extremely poor design and needs a decent fix asap... I love where Ubuntu is going, but this kind of "screw the user mantrap" really sucks. Steve -- Too easy to accidentally kill dbus from Services settings and lock yourself out of services https://bugs.launchpad.net/bugs/112102 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
