Bugzilla Bug 140666

I do use hal and ivman to automatically perform some actions (like mounting
removable devices). Everything was OK till I upgrade from hal-0.5.5.1-r3 to
0.5.7-r1.

Downgrading to 0.5.5.1-r3 was the solution for me.

This is my emerge --info:
Gentoo Base System version 1.6.15
Portage 2.1-r1 (default-linux/x86/2006.0, gcc-3.4.6, glibc-2.3.6-r4,
2.6.16-gentoo-r13 i686)
=================================================================
System uname: 2.6.16-gentoo-r13 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz
app-admin/eselect-compiler: [Not Present]
dev-lang/python:     2.4.3-r1
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     [Not Present]
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2
sys-devel/binutils:  2.16.1-r3
sys-devel/gcc-config: 1.3.13-r3
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/X11/xkb"
CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo"
CXXFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks fixpackages metadata-transfer noinfo sandbox
sfperms strict"
GENTOO_MIRRORS="http://www.die.unipd.it/pub/Linux/distributions/gentoo-sources/
http://gentoo.ngi.it"
LDFLAGS="-Wl,-O1 -Wl,--sort-common"
LINGUAS="C"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress
--force --whole-file --delete --delete-after --stats --timeout=180
--exclude='/distfiles' --exclude='/local' --exclude='/packages'"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 X a52 alsa apache2 avi bitmap-fonts bzip2 cdr cli crypt cups curl dbus
dlloader dri dv dvd dvdr emboss encode foomaticdb fortran gif gstreamer gtk
gtk2 hal imagemagick imlib ipv6 isdnlog jpeg lcms libg++ libwww live mad mikmod
mmx mng mp3 mpeg ncurses nptl nptlonly nsplugin opengl pam pcre pda pdflib perl
png pppd python qt4 quicktime readline real reflection scanner sdl session
spell spl sse ssl tiff truetype truetype-fonts type1-fonts udev usb v4l v4l2
win32codecs xml xorg xv zlib elibc_glibc input_devices_keyboard
input_devices_evdev input_devices_mouse kernel_linux linguas_C userland_GNU
video_cards_mga"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL,
PORTAGE_RSYNC_EXTRA_OPTS

Created an attachment (id=91916) [details]
lshal output for both hal-0.5.5.1-r3 and hal-0.5.7-r1

Please find attached the lshal output for both 0.5.5.1-r3 and 0.5.7-r1 hal
versions. The output has been produced after plugging the same USB memory
stick.

If you analyze the section related to the volume uid 446E_1041 you can see many
differences. For example in the 0.5.5.1-r3 case we have:
 volume.policy.should_mount = true  (bool)
this is missing in the lshal output produced with 0.5.7-r1 hal version.

same problem for me here - the removable media applet of kde does not show any
removable media devices after upgrading to hal-0.5.7-r1

I'm also experiencing the same problem with hal-0.5.7-r3 on amd64.

It seems as though this was a problem with KDE media's manager and not with
hal.  After upgrading to KDE 3.5.4, this problem went away for me.

don't know if this will solve your problems or not, but while watching my boot
messages I noticed that 90-hal.rules was creating an error message from udevd.
It seems that 90-hal.rules has action="remove" instead of action=="remove".
adding in the second "=" sign got rid of the error message. Haven't tried
adding or removing any media yet but I will try that later.

HAL 0.5.7 removed functionality (the volume.policy and storage.policy) keys
that are used by a bunch of mounters. apparently the mounters and DEs need to
provide this info or PolicyKit does. However PolicyKit doesn't work until 0.5.8
and is still a very unstable very immature app.

Unfortunately it's looking more and more and more like I might removed 0.5.7.1
from Portage or patch the living day lights out of it.

Problem with KDE should be fixed in KDE 3.5.5. They were doing something wrong
over there.

Robert: The file in question has a == for me.


Can someone test this with KDE 3.5.5?

(In reply to comment #8)
>
> Can someone test this with KDE 3.5.5?
> 

Works with the following at least:

pena betelgeuse # emerge -pv hal dbus

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R   ] sys-apps/hal-0.5.7.1-r2  USE="acpi crypt dmi -debug -doc
-pcmcia (-selinux)" 0 kB
[ebuild     U ] sys-apps/dbus-1.0.2 [0.62-r2] USE="-X -debug -doc (-selinux)
(-gtk%) (-mono%) (-python%) (-qt3%*) (-qt4%)" 1,368 kB

Done.