Arch Linux

ammon

Member

Registered: 2008-12-11

Posts: 413

[Solved] Sudden HAL problems

Damn! Hal again.

It was fine just few hours ago. I did NOT updated machine latley. I did not changed any conf file or so.
Now it wont start, and most of apps wont fuction as they should cuz of it.

This is what dmesg says:

hald[3992]: segfault at 0 ip 0000000000411790 sp 00007fff4ab60f10 error 4 in hald[400000+56000]

Tried reinstall it, reinstalled dbus, rebooted machine... even did chmod +x on /etc/rc.d/hal

My deamons list from rc.conf:

DAEMONS=(syslog-ng @dbus @hal @stbd @gdm @laptop-mode @cpufreq @networkmanager @alsa @pulseaudio @bluetooth)

Pls help! My system is quite useless now.

Last edited by ammon (2009-09-15 11:52:33)

flamelab

Member

From: Athens, Hellas (Greece)

Registered: 2007-12-26

Posts: 2,160

Re: [Solved] Sudden HAL problems

Steps:

1)Remove dbus entry, it is started by hal automatically
2)Install acpid
3)Remove the "@" before HAL.

Last edited by flamelab (2009-09-14 09:50:32)

bernarcher

Forum Fellow

From: Germany

Registered: 2009-02-17

Posts: 2,281

Re: [Solved] Sudden HAL problems

No idea about the actual error. But you should never background hal. It must have finished its work before others can use the system. And you need not eyplicitely start the dbus daemon. Thus you'd better use:

DAEMONS=(syslog-ng hal @stbd @gdm @laptop-mode @cpufreq @networkmanager @alsa @pulseaudio @bluetooth)

Edit:
flamelab, you are too fast for me.

Last edited by bernarcher (2009-09-14 09:53:46)

---

To know or not to know ...
... the questions remain forever.

ammon

Member

Registered: 2008-12-11

Posts: 413

Re: [Solved] Sudden HAL problems

Thanks guys. I really hoped it would be that simple.
But no. I still does not work. I know that dbus is autostarted by hal, but sometimes it does not, so I placed dbus first. Strange, now without dbus entry dbus is started but hal is still at  [FAIL]. 
I used Hal with @ for over a year now. Never had problems. Never.

That is why I am so shocked with this. It works like a charm for a long time. And next stratup is epic fail.

Any ideas? Can I help you to think of something? c/p some log or so?

P.S.
flamelab - I installed acpid, but why do I need it? I does make no diffirence now when it is installed.

Army

Member

Registered: 2007-12-07

Posts: 1,784

Re: [Solved] Sudden HAL problems

I had this problem once, I solved it by reinstalling hal, which re-executed the install script, which solved my problem, whatever it actually was ;-) You might give it a try.

ammon

Member

Registered: 2008-12-11

Posts: 413

Re: [Solved] Sudden HAL problems

Ok....

sudo pacman -Rd hal
sudo rm -r /etc/hal

sudo pacman -S hal
sudo reboot

Damn, it works now.
I cant belive it... Damn hal, cant wait devkit to replace it.
It cost me so much nerves.

Thanks! Thank you all!
Sve najbolje!

Mr.Elendig

#archlinux@freenode channel op

From: The intertubes

Registered: 2004-11-07

Posts: 4,092

Re: [Solved] Sudden HAL problems

Steps:

1)Remove dbus entry, it is started by hal automatically
2)Install acpid
3)Remove the "@" before HAL.

That's just silly. Starting dbus explicitly makes it easier to spot problems. Countless people have been complaining on #archlinux about hal being broken, when the real problem was that udev didn't start.

There is nothing wrong wtih starting dbus explicitly before hal.

But, dbus should probably not be @'ed when it's started explicitly before hal

---

Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest

bernarcher

Forum Fellow

From: Germany

Registered: 2009-02-17

Posts: 2,281

Re: [Solved] Sudden HAL problems

That's just silly. Starting dbus explicitly makes it easier to spot problems.

It seems to be not that easy.

I had dbus started before hal in the DAEMONS array for some time. But then I experienced spurious lock-ups during the boot sequence. After removing dbus, these are completely gone. I assume timing issues when hal tries to find out about dbus a bit too soon.

But, dbus should probably not be @'ed when it's started explicitly before hal

Of course! Hal checks whether there is a running dbus already. If not, it tries to start it on his own.

Last edited by bernarcher (2009-09-14 20:05:51)

---

To know or not to know ...
... the questions remain forever.

flamelab

Member

From: Athens, Hellas (Greece)

Registered: 2007-12-26

Posts: 2,160

Re: [Solved] Sudden HAL problems

Steps:

1)Remove dbus entry, it is started by hal automatically
2)Install acpid
3)Remove the "@" before HAL.

That's just silly. Starting dbus explicitly makes it easier to spot problems. Countless people have been complaining on #archlinux about hal being broken, when the real problem was that udev didn't start.

There is nothing wrong wtih starting dbus explicitly before hal.

But, dbus should probably not be @'ed when it's started explicitly before hal

Hey, that was rude. As you can say that not starting dbus before hal is silly, I can say the same thing for starting dbus before hal.