Gerry: your bug doesn't present duplicate GIDs, but the problem here is not about them. Be GIDs duplicate or not, the real issue is that the launcher program is not owned by the 'messagebus' group. The fact that it's using a GID used by another group is a coincidence that doesn't change anything (just messes things a bit more).
But please - this bug is serious, but the fact that you ran into it doesn't mean everybody is experiencing it at all. Nobody is assuming users are able to fix it by running terminal commands, but please explain us how to fix it, and we surely will! ;-) This bug must come from some program changing by mistake the GID for the messagebus group. But this kind of bug is very hard to tackle, since it affects a limited parts of users (only a handful of reporters so far), and we don't know what's the common denominator to all of them. If you want to help, you have to find what's in common to all these cases. So: - what's the first Ubuntu version reporters have installed, and how/when did they upgrade until Lucid? - is there something noteworthy that isn't standard on their systems - whose nature is hard to guess beforehand? A hint: as Scott said, "This really looks like something removed the messagebus group and caused it to be recreated with a new gid." Another solution would be to force changing the owner group of the launcher when installing package, which wouldn't be too hard. ** Changed in: dbus (Ubuntu) Importance: Medium => High ** Summary changed: - fails to run lib/dbus-1.0/dbus-daemon-launch-helper + Fails to run lib/dbus-1.0/dbus-daemon-launch-helper: not owned by the messagebus group -- Fails to run lib/dbus-1.0/dbus-daemon-launch-helper: not owned by the messagebus group 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
