Bug 304205 – net-wireless/bluez breaks dbus if hal is not installed

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description A. Craig West 2010-02-10 02:34:02 UTC]

When bluez is installed, the ebuild patches the file dbus-1/system.d/bluetooth.conf with a reference to the group plugdev. Unfortunately, if hal has not been installed on the system, the plugdev group does not exist, so dbus will not start up.

[Comment 1 Gustavo F. Padovan 2010-02-13 23:20:47 UTC]

Should we add dependence on hal when plugdev USE is enabled?

[Comment 2 Gustavo F. Padovan 2010-02-13 23:24:08 UTC]

hum..it's not plugdev use. It's !consolekit. Then we should depend on hal.

[Comment 3 A. Craig West 2010-02-14 01:52:09 UTC]

Do we actually depend on hal in that case, or just the plugdev user? If it is the user we need, we could add it ourselves. My use case is an embedded device, where I am trying to avoid a proliferation of dependencies...

[Comment 4 Pacho Ramos 2010-02-14 13:57:36 UTC]

I don't know if it would require hal or not :-(, but I will CC Fabio as he will probably know it much better than me since he suggested the change some time ago (bug 283744)

Thanks Fabio

[Comment 5 Fabio Erculiani (RETIRED) 2010-02-14 18:05:08 UTC]

Thanks Pacho,
looking at net-wireless/bluez source code, there's no hal reference in configure.ac. But still, "plugdev" is generally used for these kind of things in Gentoo-land. Why not just creating "plugdev" group (enewgroup) in dbus ebuild when required?

[Comment 6 Pacho Ramos 2010-02-14 18:54:45 UTC]

(In reply to comment #5)
> in dbus
> ebuild when required?
> 

I guess you meant bluez ebuild instead ;-)

Yes, I will then let bluez ebuild create plugdev group when USE="-consolekit"

Thanks 

[Comment 7 Pacho Ramos 2010-02-15 18:05:27 UTC]

Fixed in 4.61

[Comment 8 niogic 2010-02-16 08:42:35 UTC]

*** Bug 305319 has been marked as a duplicate of this bug. ***