You are not logged in.

#1 2005-04-04 10:11:30

wabi
Member
Registered: 2005-04-04
Posts: 72

ivman hal dbus problem

I tried automount and this with the packages from current and extra

when starting ivman I get this:

libhal.c 644 : Error connecting to system bus: Failed to connect to socket /var/lib/dbus/system_bus_socket: Connection refused

** (process:3869): WARNING **: manager.c/656: Failed to initialize HAL!

if I start hal it seems to start but later does not have a process so I think it stops again:
12:08:17.822 [I] hald.c:394: hal 0.4.7
12:08:17.823 [I] hald.c:396: Will daemonize
12:08:17.823 [I] hald.c:406: Becoming a daemon

ps ax|grep hal shows me nothing

finally dbus:
dbus gets started at boottime and has this lines when I ps for it:

3746 tty1     S      0:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session
3747 ?        Ss     0:00 dbus-daemon-1 --fork --print-pid 8 --print-address 6

so somehow some kind of dbus is running but hal can't connect to it so ivman wont start.
I could not find any information about this problem.

any help appreciated
thanks
wabi

Offline

#2 2005-04-04 10:43:28

bauerber
Member
Registered: 2004-12-20
Posts: 40

Re: ivman hal dbus problem

Hi,
did you use the correct starting order (dbus, hal, ivman)?
there is a quite good howto, only i cannot find it at the moment...

greez

bernhard

[Edit]
Sorry, didn't thoroughly read the last few lines, you are starting them in correct order...
<smacks forehead>

Offline

#3 2005-04-04 11:39:27

T-Dawg
Forum Fellow
From: Charlotte, NC
Registered: 2005-01-29
Posts: 2,736

Re: ivman hal dbus problem

strange, I got similar errors when I started those daemons out of order, but it looks like you have them right. The only thing I can think of right now without knowing a little more about what you did would be  to not  prefix dbus and hal daemons with a @, make sure you are using udev not devFS, and use the 2.6 kernel.

Offline

#4 2005-04-04 12:30:03

wabi
Member
Registered: 2005-04-04
Posts: 72

Re: ivman hal dbus problem

yes I saw the howto and I got the correct order and I even use udev and 2.6 and there is no prefix for these daemons in the rc.conf but somehow they won't or better dbus and hal don't want to (is ther any possibility to get more information out of hal? I just don't know why it crashes after it daemonizes)

Offline

#5 2005-04-04 13:12:11

bauerber
Member
Registered: 2004-12-20
Posts: 40

Re: ivman hal dbus problem

Another thing:

which components did you install to get hal and dbus running?

pacman -S hal hal-device-manager dbus???

Somehow I have the impression we're overlooking something...

greez

bernhard

Offline

#6 2005-04-04 13:34:42

wabi
Member
Registered: 2005-04-04
Posts: 72

Re: ivman hal dbus problem

do I need hal-device-manager? it didn't install with the ivman so I didn't know it was needed. I will install it but I don't think it accutally is the source of the problem.
I have installed terminal so I got exo and with that dbus. hal I added seperatly and then ivman.

In /var/log/messages I get frequent messages like this:
hal.hotplug[3836]: DEVPATH is not set

perhaps this is something but I only find things about wlan related with this.

Offline

#7 2005-04-04 13:45:08

bauerber
Member
Registered: 2004-12-20
Posts: 40

Re: ivman hal dbus problem

I'm only asking 'cause the hal-device-manager was listed in a german wiki I found at http://laber-land.berlios.de/wiki/index.php/Automount.
The Wiki there describes installation of gnome-volume-manager, but that also makes use of dbus and hal...

good luck

bernhard

Offline

#8 2005-04-04 15:11:04

T-Dawg
Forum Fellow
From: Charlotte, NC
Registered: 2005-01-29
Posts: 2,736

Re: ivman hal dbus problem

I never installed hal-device-manager, Just dbus and hal.

hal.hotplug[3836]: DEVPATH is not set

I get the same messages, but everything works fine for me.

Offline

#9 2005-04-05 17:47:32

mic64
Member
Registered: 2005-03-03
Posts: 173

Re: ivman hal dbus problem

Hi

I got some other problem hal related
It was running since weeks without problems..automounting usb, cd etc.
since the latest update, where hal and dbus was updated some very very strange things happen.

After fresh start I had normally 77 processes running, mounting was ok etc.
Now...after a restart I got 150 processes running increasing every few seconds.
After a minute or so I got 280. 200 are hal and hotlug.hal related.
and the Hard Drive and CPU is always showing actibities. never happened before.

...and  automounting isn´t working anymore too.

What is this? 

tia
mic

Offline

Board footer

Powered by FluxBB