well, because this became a big issue for me and my users i googled a
lot and finally got this solved...
the segfault issue was caused by a previos mod to hald.conf trying to
solve the original issue, after comparing between the bad an sane system
i've managed to found the problem
and after looking to the policy problem i've added this to
/etc/dbus-1/system.d/hal.conf
<!-- 01-08-2006 modification in order to KDE users can mount -->
<policy group="plugdev">
<allow send_interface="org.freedesktop.Hal.Device.Volume"/>
<allow send_interface="org.freedesktop.Hal.Device.Volume.Crypto"/>
</policy>
so is working again right now...
the info needed was founded here:
http://www.mail-archive.com/debian-kde@lists.debian.org/msg25907.html
and this
http://www.nabble.com/Bug-347233:-dbus-1-on-sarge-segfaults-if-a
-unpriviliged-user-run-%22lshal%22-t880937.html
something i believe is important:
the sane system is my home laptop, and standalone system.
the other two systems with the issue are using ldap as auth backend for
the users.
from the last link it seems to be some issue here with a different auth
backend system.
in fact at the laptop system the hal.conf mod is not needed but at the
ldap system is needed... (just modify one of them, 'til monday i can get
to the other one.. to double check)
--
security policy error with hald after latest updates
https://launchpad.net/bugs/58165
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
