Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 314983 - sys-apps/dbus-1.2.24 : dbus access issue with users in plugdev group
Summary: sys-apps/dbus-1.2.24 : dbus access issue with users in plugdev group
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Freedesktop bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-13 12:34 UTC by Serge FELIX
Modified: 2010-04-15 16:58 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Serge FELIX 2010-04-13 12:34:01 UTC
Since my last upgrade (dbus-1.2.3 to 1.2.24), some programs (thunar, xfdesktop) can't talk with dbus system.
My user is in plugdev group.


Reproducible: Always

Steps to Reproduce:
1. emerge dbus-1.2.24
2. put your user in plugdev group
3. try to open thunar (or other files manager like pcmanfm), xfdesktop ...

Actual Results:  
dbus-daemon: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.15" (uid=29102 pid=12606 comm="thunar) interface="org.freedesktop.Hal.Manager" member="FindDeviceByCapability" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=8013 comm="/usr/sbin/hald))


Old environment : sys-apps/hal-0.5.13-r2 sys-apps/dbus-1.2.3-r1
New environment : sys-apps/hal-0.5.13-r2 sys-apps/dbus-1.2.24
xfce 4.6.1

workaround 1 :
specify my user in /etc/dbus-1/system.d/hal.conf like that :
  <!-- Gentoo specific rules to allow 'plugdev' group to access Volumes and Power Management -->
++  <policy user="myuser">
--  <policy group="plugdev">

workaround 2 :
emerge sys-apps/dbus-1.2.24 but keep 1.2.3 config files
Comment 1 Rafał Mużyło 2010-04-13 19:17:10 UTC
Workaround 3: fix those programs to work with new dbus policy.

Probably bug 267621 will give you a hint.

Report back, if that's the problem (with full list of programs
affected).
Comment 2 Daniel Gryniewicz (RETIRED) gentoo-dev 2010-04-14 11:28:53 UTC
We need to know which dbus paths failed (syslog should tell you).  Then the packages that own those paths need to be updated to allow correct permissions.
Comment 3 Serge FELIX 2010-04-14 13:56:26 UTC
I did multiple tests, the problem seems to be with my ldap authentification via pam.
When I disable ldap pam configuration and log in  with a local user, the system acts normaly :
- with plugdev group : no problem
- without plugdev : dbus hal service message error

When I enable ldap authentification and log in with a ldap user, I see this messages in syslog (with or without pludev group) :

Apr 14 10:44:33 tc-test dbus-daemon: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.4" (uid=29102 pid=6566 comm="xfdesktop) interface="org.freedesktop.Hal.Manager" member="FindDeviceByCapability" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=5276 comm="/usr/sbin/hald))
Apr 14 10:44:34 tc-test dbus-daemon: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.7" (uid=29102 pid=6579 comm="xfdesktop) interface="org.freedesktop.Hal.Manager" member="FindDeviceByCapability" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=5276 comm="/usr/sbin/hald))
Apr 14 10:44:34 tc-test dbus-daemon: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.8" (uid=29102 pid=6581 comm="xfdesktop) interface="org.freedesktop.Hal.Manager" member="FindDeviceByCapability" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=5276 comm="/usr/sbin/hald))
Apr 14 10:44:34 tc-test dbus-daemon: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.9" (uid=29102 pid=6583 comm="xfdesktop) interface="org.freedesktop.Hal.Manager" member="FindDeviceByCapability" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=5276 comm="/usr/sbin/hald))
Apr 14 10:49:29 tc-test dbus-daemon: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.10" (uid=29102 pid=6590 comm="thunar) interface="org.freedesktop.Hal.Manager" member="FindDeviceByCapability" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=5276 comm="/usr/sbin/hald))
Apr 14 10:50:17 tc-test dbus-daemon: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.11" (uid=29102 pid=6597 comm="pcmanfm) interface="org.freedesktop.Hal.Manager" member="FindDeviceByCapability" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=5276 comm="/usr/sbin/hald))
Apr 14 10:50:48 tc-test dbus-daemon: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.13" (uid=29102 pid=6558 comm="/usr/bin/xfce4-session) interface="org.freedesktop.Hal.Device.SystemPowerManagement" member="ThisMethodMustNotExistInHal" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=5276 comm="/usr/sbin/hald))
Comment 4 Serge FELIX 2010-04-15 15:12:33 UTC
My problem is an incompatibility between pam_group and dbus that my recent upgrade has unearthed.
More info here : http://lists.freedesktop.org/archives/dbus/2008-January/009173.html

Sorry and thanks for help
Comment 5 Steev Klimaszewski (RETIRED) gentoo-dev 2010-04-15 15:51:00 UTC
Is the issue actually fixed though?  Reading through the thread, I didn't see anything, but out of curiosity, what did you do to fix it, is it something that we can tell users so that when they run into this issue they don't have to go looking for a 2 year old conversation on a mailing list?
Comment 6 Serge FELIX 2010-04-15 16:58:01 UTC
(In reply to comment #5)
> Is the issue actually fixed though?  Reading through the thread, I didn't see
> anything, but out of curiosity, what did you do to fix it, is it something that
> we can tell users so that when they run into this issue they don't have to go
> looking for a 2 year old conversation on a mailing list?
> 

I didn't take any decisions for this time.
In my case, a possible workaround, is to change the plugdev group by the group of the user in /etc/dbus-1/hal.conf
The group of the user is stored in ldap but not set by pam_group. Dbus can read it.

I'll looking if some better solutions already exist. This problem is not so recent, it would be strange that nobody has solved it.
I report it here if I find any solution