starting from udev-126 hal doesn't recognise anymore my keyboard and touchpad and Xorg (which on my system depends on hal's aid for autoconfiguration) is unusable. However it recognise my USB mouse if I unplug end re-plug it, so it seems something is broken WRT coldplug of input devices. re-emerging udev-125-r2 fixes the problem for me. Reproducible: Always
(In reply to comment #0) > starting from udev-126 hal doesn't recognise anymore my keyboard and touchpad > and Xorg (which on my system depends on hal's aid for autoconfiguration) is > unusable. However it recognise my USB mouse if I unplug end re-plug it, so it > seems something is broken WRT coldplug of input devices. > > re-emerging udev-125-r2 fixes the problem for me. > > Reproducible: Always > Forgot to say that the culprit seems to be in hald-addon-input non being started on my system with >=udev-126
Found the following in syslog after setting HAL to be verbose: Sep 3 15:22:35 mother hald[4973]: 15:22:35.057 [E] coldplug.c:166: Couldn't invoke /usr/bin/udevinfo Sep 3 15:22:35 mother hald[4973]: 15:22:35.057 [E] coldplug.c:569: Unable to get sysfs to dev map udevinfo was a symlink to udevadm and seems to be missing with udev-127. Recreating the symlink fixed the problem here (although probably HAL needs to adjusted).
(In reply to comment #2) > (although probably HAL needs to be adjusted). > Looks like it already is in GIT: http://gitweb.freedesktop.org/?p=hal.git;a=commit;h=f6af40c1e7ea54e69eb2d259d91dd212065d5f6e
*** Bug 236599 has been marked as a duplicate of this bug. ***
Same problem here. In addition to my mouse and keyboard my eth0 device isn't started and configured by NetworkManager, too. Downgrading to 125-r2 works, so let's wait for a new hal version...
solution hier https://bugs.gentoo.org/show_bug.cgi?id=236599
udevinfo has been deprecated for a long time. hal needs to move to using 'udevadm info', as per the patch in the HAL Git tree.
Shouldn't we mask new udev for now/add blockers for this one? Breaking both mouse and network capabilities (when using NetworkManager) at the same time is not so nice for the user...
(In reply to comment #3) > Looks like it already is in GIT: > http://gitweb.freedesktop.org/?p=hal.git;a=commit;h=f6af40c1e7ea54e6 Confirmed: The following patch applies all right and solves the issue: http://gitweb.freedesktop.org/?p=hal.git;a=commitdiff_plain;h=f6af40c1e7ea54e6 Can we please get a revbump of hal which includes this patch? And proper runtime dependencies as well, I'd say, so that new udev blocks old hal.
fixed with hal-0.5.11-r2. thanks to compnerd!
*** Bug 236764 has been marked as a duplicate of this bug. ***
My 'hald' works well only with 'root' rights. on starting [my_host~]# sudo -u haldaemon hald --verbose=yes gives in syslog such messages: ............................ coldplug.c:166: Couldn't invoke /sbin/udevadm coldplug.c:569: Unable to get sysfs to dev map ............................ and typing: [my_host~]# sudo -u haldaemon /sbin/udevadm sudo: unable to execute /sbin/udevadm: Permission denied It's seems to be not HAL error but only permissions problem. I don't now how to tune '/sbin' and/or haldaemon goup permission to resolve this problem :-(
*** Bug 249527 has been marked as a duplicate of this bug. ***
