Ubuntu
dbus package

HAL and gnome-volume-manger do not work for LDAP users

Bug #139098 reported by Timothy Allen
6
Affects Status Importance Assigned to Milestone
dbus (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: dbus

Running Feisty, all users login via LDAP. Network Manager provides connectivity.

Users are not able to make use of any devices from gnome-volume-manager. Running "lshal" returned a NoReply error from dbus for all users. (root and local users are able to use lshal without problems.) The bug was the same on 5 similarly-configured machines.

The correct groups are set in /etc/security/group.conf, LDAP users were added to the plugindev group in /etc/group, with no result.

I reviewed Debian bug#377689, Ubuntu bugs #75602 and #58165, and many other similar threads; none of these fixed the problem in any way (including various changes to /etc/dbus-1/system.d/hal.conf).

The fix I finally found was to purge network-manager (relying on /etc/network/interfaces instead), and move /etc/rc2.d/S12dbus to S29dbus, and S13gdm to S30gdm (I'm not yet certain whether moving both files was necessary).

After this, LDAP users were able see and mount removable devices without trouble, and 'lshal' reported the correct results.

I'm not sure if this bug belongs to HAL, Network Manager, PAM or some kind of LDAP package, or DBus, but since most elements of the eventual fix involved D-Bus, I'm reporting it here.

Revision history for this message
bgrupe (bgrupe) wrote :

This bug seems to be (accidently?) fixed in hardy. I got the same problem you had in gutsy and dist-upgrading to hardy fixed the issue. Please report if it still doesn't work for you in hardy.

Changed in dbus:
status: New → Fix Released
Revision history for this message
Timothy Allen (tim-treehouse) wrote :

I have recently upgraded all the originally-affected computers to hardy, with a fresh install. The problem still exists, and now also affects gnome-power-manager. (Typically the system has a 1-minute delay before displaying the shutdown dialogue.)

I fixed it by moving /etc/rc2.d/S12dbus to /etc/rc2.d/S22dbus.

Changed in dbus:
status: Fix Released → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.