I think it's something wrong in the dbus setup package. I have had the same issue as the OP - the dbus executable file has permissions set up improperly. I also have most of the system groups < 1000 exported out from a common NIS server. ( need common administrators across various computers, admin and adm being one of those groups < 1000 ). Unfortuantely, this also pushes out the messagebus group across to the various computers ( again, it's a system group < 1000 ).
This screws up whatever sets up the permissions in the dbus package, leaving the file with permissions pointing to the REMOTE dbus group instead of the local group, giving us this sort of broken permissions. Fixes? Either rewrite the dbus setup thing to change ownership to the right GID, or put the admin, adm groups > 1000, because in a networked environment with a need for common administrators, they really OUGHT not to be system/computer groups. -- fails to run lib/dbus-1.0/dbus-daemon-launch-helper https://bugs.launchpad.net/bugs/295405 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
