after upgrading from 0.5.12_rc1-r7, there is a config update that removes the following lines in the file /etc/dbus-1/system.d/hal.conf: <policy user="root"> <allow own="org.freedesktop.Hal"/> <allow send_destination="org.freedesktop.Hal" send_interface="org.freedesktop.Hal.Device"/> <allow send_destination="org.freedesktop.Hal" send_interface="org.freedesktop.Hal.Manager"/> <allow send_destination="org.freedesktop.Hal" send_interface="org.freedesktop.Hal.Device.KillSwitch"/> <allow send_destination="org.freedesktop.Hal" send_interface="org.freedesktop.Hal.Device.Leds"/> <allow send_destination="org.freedesktop.Hal" send_interface="org.freedesktop.Hal.Device.Storage"/> <allow send_destination="org.freedesktop.Hal" send_interface="org.freedesktop.Hal.Device.Storage.Removable"/> <allow send_destination="org.freedesktop.Hal" send_interface="org.freedesktop.Hal.Device.SystemPowerManagement"/> <allow send_destination="org.freedesktop.Hal" send_interface="org.freedesktop.Hal.Device.Volume"/> <allow send_destination="org.freedesktop.Hal" send_interface="org.freedesktop.Hal.Device.Volume.Crypto"/> <allow send_destination="org.freedesktop.Hal" send_interface="org.freedesktop.Hal.Device.WakeOnLan"/> </policy> removing them, renders all input offline. reinstalling 0.5.12_rc1-r7 renders te input back, also, installing 0.5.13 and rejecting the suggested config renders the input working again. Reproducible: Always
Created attachment 198783 [details] diff from etc-update This is the diff I got from etc-update from updating HAL. I skipped the update, and kept the config file as is, and my input devices kept working. If that helps any.
+ 22 Jul 2009; Samuli Suominen <ssuominen@gentoo.org> package.mask: + Mask latest HAL since it renders all input devices unusable.
(In reply to comment #1) > Created an attachment (id=198783) [edit] > diff from etc-update > > This is the diff I got from etc-update from updating HAL. I skipped the update, > and kept the config file as is, and my input devices kept working. > > If that helps any. > that is exacly what I've did.
Hmm, I was about to file a bug on 0.5.13. My X server does not start after the upgrade with the following FATAL message: FATAL: Module fbcon not found. I think this is the same bug.
I can confirm this as well. This version of hal (well, not this version but the config it provides) makes my X dirty like zebra. So I masked it out, re-emerged and it's clean like aardvark. [root@nexus]-[22:04:40]-[~] # cat /etc/portage/package.mask/hal =sys-apps/hal-0.5.13
(In reply to comment #4) > Hmm, I was about to file a bug on 0.5.13. My X server does not start after the > upgrade with the following FATAL message: > FATAL: Module fbcon not found. > I think this is the same bug. Probably unrelated. File a new bug report. Thanks
*** Bug 278631 has been marked as a duplicate of this bug. ***
That will teach me to actually test on my !policykit box. Fixed in 0.5.13-r1.
Related: bug #278760 about segfaults in Xorg due to broken hal config.
*** Bug 278838 has been marked as a duplicate of this bug. ***