Summary: | sys-apps/dbus-1.2.24 : dbus access issue with users in plugdev group | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Serge FELIX <nopublegrave> |
Component: | [OLD] Core system | Assignee: | Freedesktop bugs <freedesktop-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Serge FELIX
2010-04-13 12:34:01 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). 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. 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)) 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 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? (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 |