You are not logged in.

#1 2009-02-07 11:56:51

joeda
Member
Registered: 2008-09-14
Posts: 32

HAL-Daemon refuses to start

Hello everbody,

I don't really know what to say.

bash-3.2# /etc/rc.d/hal start
:: Starting Hardware Abstraction Layer                                                                                                              [FAIL] 
bash-3.2#

Any logfiles that can help? Anything? Anybody?

joe

Offline

#2 2009-02-07 12:15:39

kgas
Member
From: Qatar
Registered: 2008-11-08
Posts: 718

Re: HAL-Daemon refuses to start

Offline

#3 2009-02-07 12:53:56

joeda
Member
Registered: 2008-09-14
Posts: 32

Re: HAL-Daemon refuses to start

Thanks for your reply,

bash-3.2# hald --daemon=no --verbose=yes
13:39:13.286 [i] hald.c:669: hal 0.5.11
13:39:13.286 [i] hald.c:734: Will not daemonize
13:39:13.287 [i] hald_dbus.c:5381: local server is listening at unix:abstract=/var/run/hald/dbus-QKIh8chC5h,guid=8ecef3ec88f01f1fca5aa2cd498d80f1
13:39:13.288 [i] ck-tracker.c:387: got seat '/org/freedesktop/ConsoleKit/Seat1'
13:39:13.288 [i] ck-tracker.c:317: got session '/org/freedesktop/ConsoleKit/Session1' for seat '/org/freedesktop/ConsoleKit/Seat1'
13:39:13.289 [E] ck-tracker.c:261: Invalid GetUnixUser reply from CK
13:39:13.289 [E] ck-tracker.c:323: Could not get information for session '/org/freedesktop/ConsoleKit/Session1'
13:39:13.289 [E] ck-tracker.c:401: Could not get sessions for seat '/org/freedesktop/ConsoleKit/Seat1'
13:39:13.289 [E] ck-tracker.c:792: Could not get seats and sessions
13:39:13.289 [W] hald_dbus.c:5806: Could not initialize seats and sessions from ConsoleKit
Runner started - allowed paths are '/usr/lib/hal:/usr/lib/hal/scripts:/usr/bin'
13:39:13.290 [i] hald_runner.c:301: Runner has pid 2949
13:39:13.290 [i] hald_runner.c:182: runner connection is 0x84636d0
13:39:13.293 [W] osspec.c:373: Unable to open /proc/mdstat: No such file or directory
13:39:13.293 [i] mmap_cache.c:274: cache mtime is 1234008237
Error binding udev_event socket: Address already in use
bash-3.2#

/etc/groups:

root::0:root
bin::1:root,bin,daemon
daemon::2:root,bin,daemon
sys::3:root,bin
adm::4:root,daemon
tty::5:
disk::6:root
lp::7:daemon
mem::8:
kmem::9:
wheel::10:root
ftp::11:
mail::12:
uucp:x:14:
log::19:root
smmsp::25:
games::50:
network:x:90:
video:x:91:
audio::92:jo,mpd
optical::93:hal,jo
floppy:x:94:hal
storage:x:95:hal,jo
power:x:98:jo
nobody::99:
users::100:
locate:x:21:
http:x:33:
scanner:x:96:jo
dbus:x:81:jo
hal:x:82:jo
avahi:x:84:
camera:x:97:
mpd:x:45:
gdm:x:101:
policykit:x:102:
lpadmin:x:103:jo

I just rebooted, but it doesn't seem to help. Are there any configs or other stuff that could have to do with it?
I'm sure it isn't running, but it's in the DAEMONS in rc.conf to start at booting. Shouldn't there bo a log or so?

joe

Offline

#4 2009-04-11 22:50:49

vampiro
Member
From: Russia
Registered: 2009-04-11
Posts: 3

Re: HAL-Daemon refuses to start

wtf?! same problem after system upgrade. hal fails while boot process. hald --daemon=no --verbose=yes says "could not initialise PolicyKit context". People with no problems, post your policykit confs please.

Offline

#5 2009-04-11 22:57:41

vampiro
Member
From: Russia
Registered: 2009-04-11
Posts: 3

Re: HAL-Daemon refuses to start

2 joeda
did you solve the problem?

Offline

#6 2009-04-16 03:17:45

Knute
Member
From: Minot, ND
Registered: 2009-03-17
Posts: 604

Re: HAL-Daemon refuses to start

Hey Jo, do you have any raid devices on your system?

If not, go into /etc/mkinitcpio.conf and put an exclaimation point in front of raid in your hooks section, then if you run mkinitcpio it will rebuild the image for you.  If you read that other thread it mentioned about the /proc/mdstat, and that, if I were to guess, when that other person reinstalled, they didn't have any raid modules load. hehehe...

HTH


Knute

Offline

Board footer

Powered by FluxBB