You are not logged in.
Pages: 1
Topic closed
Hi guys!
I switched from gentoo to arch linux... I was bored from this distro!
I install arch linux, i put kdemod with dbus and hal, but hal don't want to start!!!
and I get this message
hald --daemon=no --verbose=yes
02:57:46.818 [i] hald.c:634: hal 0.5.10
02:57:46.819 [i] hald.c:699: Will not daemonize
02:57:46.819 [i] hald_dbus.c:5284: local server is listening at unix:abstract=/var/run/hald/dbus-lgrDa6MBue,guid=0e91a334c4271e39dea4b900473a561a
02:57:46.823 [i] hald_runner.c:301: Runner has pid 7651
02:57:46.824 [W] ci-tracker.c:299: Could not get uid for connection: org.freedesktop.DBus.Error.NameHasNoOwner Could not get UID of name 'org.freedesktop.DBus': no such name
02:57:46.824 [E] hald_dbus.c:4944: Cannot get caller info for org.freedesktop.DBus
Runner started - allowed paths are '/usr/lib/hal:/usr/lib/hal/scripts:/usr/bin'
02:57:46.826 [i] hald_runner.c:182: runner connection is 0x657300
02:57:46.830 [W] osspec.c:326: Unable to open /proc/mdstat: No such file or directory
02:57:46.833 [i] mmap_cache.c:282: cache mtime is 1194782851
Error binding udev_event socket: Address already in use
What does it mean???
Thank
Andrea
Sorry for my english
Last edited by nemodex (2007-11-15 08:53:25)
Offline
"Error binding udev_event socket: Address already in use"
it could have started already.
Offline
check /etc/group if your user is a member of hal and dbus
Last edited by xdeusx (2007-11-14 16:14:23)
Offline
check /etc/group if your user is a member of hal and dbus
Yes I've checked, my user is a member of the group...
But I've resolved the problem... I've reinstall arch linux!!:D
I've found, on google, /proc/mdstat is something about raid... But on my pc I don't have any raid device!!
And Now hal start at boot!!
Thanks
Andrea
Offline
I was having a similar problem, with the "Error binding udev_event socket: Address already in use" error, and then realized I'd simply put "hal" twice in the DAEMONS section of rc.conf. Deleting the second instance solved the problem.
Offline
check /etc/group if your user is a member of hal and dbus
I don't know..I don't think that is very good practice, or at least, not very recommendable.
Non-root user probably should have no reason to be in hal nor dbus groups. Storage, optical and power should be fine...(?)
OP: Rather than reinstalling the OS, you might try reinstalling hal if there's a next time. :)
Offline
Offline
Pages: 1
Topic closed