HAL Failed to start

malubankudi · 2008-11-22 21:54:34

[mike@Kudi ~]$ hald --verbose=yes --daemon=no
14:31:13.455 [i] hald.c:669: hal 0.5.11
14:31:13.456 [i] hald.c:734: Will not daemonize
14:31:13.457 [i] hald_dbus.c:5381: local server is listening at unix:abstract=/var/run/hald/dbus-btUDI3dZBN,guid=1e6f821928a6b034d90581d349285e01
14:31:13.482 [E] ck-tracker.c:367: Error doing GetSeats on ConsoleKit: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files
14:31:13.482 [E] ck-tracker.c:792: Could not get seats and sessions
14:31:13.482 [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'
14:31:13.551 [i] hald_runner.c:301: Runner has pid 5058
14:31:13.554 [i] hald_runner.c:182: runner connection is 0x9a261d8
14:31:13.559 [W] osspec.c:373: Unable to open /proc/mdstat: No such file or directory
14:31:13.561 [D] util_helper.c:124: drop_privileges: could not set group id

Any ideas?

kazuo · 2008-11-22 23:06:41

hal dont need root privileges?

sudo hald --verbose=yes --daemon=no

Last edited by kazuo (2008-11-22 23:07:16)

malubankudi · 2008-11-22 23:49:13

kazuo wrote:

hal dont need root privileges?
sudo hald --verbose=yes --daemon=no

...i saw someone else do that that had a problem like mine...dont rely know what it means

malubankudi · 2008-11-22 23:59:08

when i: sudo hald --verbose=yes --daemon=yes HAL start up with no errors at all. Its just the start up script that doesnt work...

Nezmer · 2008-11-23 13:15:05

malubankudi wrote:

when i: sudo hald --verbose=yes --daemon=yes HAL start up with no errors at all. Its just the start up script that doesnt work...

Did you add yourself to the 'hal' group ?

JGC · 2008-11-23 13:36:03

Adding users to the hal group should not be done.
As for the error message: scripts in /etc/rc.d/ should be run as root. It's not a bug when these things fail when starting as normal user.

malubankudi · 2008-11-23 18:45:26

JGC wrote:

Adding users to the hal group should not be done.
As for the error message: scripts in /etc/rc.d/ should be run as root. It's not a bug when these things fail when starting as normal user.

i am in root while running the script

brazzmonkey · 2008-12-25 00:12:58

i'm having similar issues:

/etc/rc.d/hal start
:: Starting Hardware Abstraction Layer                                                                                                 [FAIL]

hald --daemon=no --verbose=yes
01:09:46.817 [i] hald.c:669: hal 0.5.11
01:09:46.817 [i] hald.c:734: Will not daemonize
01:09:46.817 [i] hald_dbus.c:5381: local server is listening at unix:abstract=/var/run/hald/dbus-ZYPitKzScp,guid=73c2efe9be17930a0134b2ed4952cf4a
01:09:46.820 [E] ck-tracker.c:367: Error doing GetSeats on ConsoleKit: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files
01:09:46.820 [E] ck-tracker.c:792: Could not get seats and sessions
01:09:46.820 [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'
01:09:46.822 [i] hald_runner.c:301: Runner has pid 3134
01:09:46.822 [i] hald_runner.c:182: runner connection is 0x834b150
01:09:46.827 [W] osspec.c:373: Unable to open /proc/mdstat: No such file or directory
01:09:46.829 [i] mmap_cache.c:274: cache mtime is 1229286958
Error binding udev_event socket: Address already in use

olovram · 2009-07-03 15:55:20

bump,
I've got this problem

toasty_ghosty · 2009-07-03 17:25:50

I too have this issue. Using Fluxbox right now as I can't use KDE because of this...:(

2_Thumbs_Up · 2009-07-03 18:04:04

I encountered the same problem after updating to the newest kernel (I updated a bunch of other packages simultaneously though and maybe it was another update that caused the problem). Suddenly, my mouse wasn't working in X and it turned out that the hal startup script in rc.d didn't work. Unfortunately I don't know how I got it to work again. All I did was messing some with my rc.conf and reinstalling a few packages, and on the next reboot it was working flawlessly again. Hope this helps in finding the issue.

toasty_ghosty · 2009-07-04 06:38:50

I've been working on this all day and have found some odd stuff out:

1) If I do not use HAL, and simply use my Xorg config, but start HAL once using Fluxbox, it will start.
2) KDE won't start - related?
3) If I add HAL to a daemon that starts before anything Xorg related (like it should be) and everything else recommended by the HAL guide, it doesn't start.
4) This is making me mad.

bash-32# hald --verbose=yes --daemon=yes HAL start
02:36:59.686 [i] hald.c:680: hal 0.5.12
02:36:59.686 [i] hald.c:681: using child timeout 250s
02:36:59.686 [i] hald.c:690: Will daemonize
02:36:59.686 [i] hald.c:691: Becoming a daemon
bash-3.2# /etc/rc.d/hal start
:: Starting Hardware Abstraction Layer [FAIL]

-Ghosty

BTW, everything is updated on my rig - this is a fresh install. And I would really like to get this sorted before the new laptop comes.

Dregath · 2009-07-07 17:19:31

I'm getting this exact same error as well, been working on it all night and no luck!

toad · 2009-07-07 17:42:44

The following helped me some time ago:

edit rc.conf and put the hal daemon (without backgrounding!) right after syslog-ng and reboot - did it come up?

Dregath · 2009-07-07 19:12:14

Hold that thought, I've just wiped my HDD for a fresh install of Windows 7 and so I can allocate more space for Linux. I'll get back to you as soon as I've got Arch back up and running.

Lastebil · 2009-07-08 03:20:35

I just had this issue, and placed hal after syslog-ng. This solved the issue. Thanks for that, it didn't happen on the other 2 boxes I just upgraded; very strange that this one had the issue.

Now, my question:

syslog-ng hal network netfs crond sshd ntp alsa

Those are all the items I have starting on this box as daemons. I can't imagine WHY any of those would cause issues with another daemon. Can anyone suggest why this is happening? Alsa, perhaps? I just added alsa at the end there, actually, to restore volume levels; seems very odd it might cause the issue.

permagreen · 2009-10-22 07:17:24

Hey, I'm having the same problem, except the solution above isn't working for me. When I run

hald --daemon=no --verbose=yes

I get something that looks like this:

hald_dbus.c:(some number):dbus_bus_get(): Failed to connect to socket /var/run/dbus/system_bus_socket: no such file or directory

Before this happened one of my filesystems got corrupted somehow (not sure how that happened) and I had never used fsck to repair a file system before, so I'm willing to admit that in my haste to get my computer working again, I inadvertantly deleted something fairly important.

Any help would be greatly appreciated,

Last edited by permagreen (2009-10-22 07:21:43)

cb474 · 2010-02-04 10:08:48

I was having a similar error, with the "Error binding udev_event socket: Address already in use" error, and then discovered I'd put "hal" in the DAEMONS section of rc.conf twice. Deleting the second instance solved the problem.

There's enough different places in the installation guides that talk about putting "hal" in rc.conf that it's easy to just mindlessly do it a second time.

Misfit138 · 2010-02-04 15:12:30

Zombie.

http://wiki.archlinux.org/index.php/For … Bumping.27

Arch Linux

#1 2008-11-22 21:54:34

HAL Failed to start

#2 2008-11-22 23:06:41

Re: HAL Failed to start

#3 2008-11-22 23:49:13

Re: HAL Failed to start

#4 2008-11-22 23:59:08

Re: HAL Failed to start

#5 2008-11-23 13:15:05

Re: HAL Failed to start

#6 2008-11-23 13:36:03

Re: HAL Failed to start

#7 2008-11-23 18:45:26

Re: HAL Failed to start

#8 2008-12-25 00:12:58

Re: HAL Failed to start

#9 2009-07-03 15:55:20

Re: HAL Failed to start

#10 2009-07-03 17:25:50

Re: HAL Failed to start

#11 2009-07-03 18:04:04

Re: HAL Failed to start

#12 2009-07-04 06:38:50

Re: HAL Failed to start

#13 2009-07-07 17:19:31

Re: HAL Failed to start

#14 2009-07-07 17:42:44

Re: HAL Failed to start

#15 2009-07-07 19:12:14

Re: HAL Failed to start

#16 2009-07-08 03:20:35

Re: HAL Failed to start

#17 2009-10-22 07:17:24

Re: HAL Failed to start

#18 2010-02-04 10:08:48

Re: HAL Failed to start

#19 2010-02-04 15:12:30

Re: HAL Failed to start

Board footer