[solved] hal and dbus wont work

osc~ · 2007-12-28 03:48:29

dbus and hal wont work.
i would like to automount my camera or memorystick

sudo /etc/rc.d/dbus restart
:: Stopping D-BUS system messagebus                                      [BUSY]
 /etc/rc.d/dbus: line 24: kill: (8854) - Processo inexistente
                                                                                              [FAIL] 
:: Starting D-BUS system messagebus                                       [BUSY]
 Failed to start message bus: The pid file "/var/run/dbus.pid" exists,
 if the message bus is not running, remove this file
                                                                                              [FAIL] 
sudo /etc/rc.d/hal restart
:: Stopping Hardware Abstraction Layer                                     [FAIL] 
:: Starting Hardware Abstraction Layer                                      [BUSY]

this is the daemons in the rc.conf

DAEMONS=(syslog-ng network samba hal sonypid hplip ptal-init cups netfs crond alsa sshd fam ipw3945d stbd)

cheers:)

Last edited by osc~ (2008-01-25 13:20:12)

luca · 2007-12-28 07:35:26

Hi osc~,
if exists try to remove the pid file

/var/run/dbus.pid

and start dbus again.
Also what is the version of dbus and hal in your system?

Last edited by luca (2007-12-28 07:36:00)

onearm · 2007-12-28 08:35:32

I have the same problem but removing /var/run/dbus.pid doesn't resolve it. Btw, what's strange is that even if dbus says "fail" at boot it is running nonetheless

ps aux | grep dbus
dbus      7489  0.0  0.0   2252   932 ?        Ss   09:17   0:00 /usr/bin/dbus-daemon --system
root      9235  0.0  0.0   3712   856 pts/2    S+   09:34   0:00 grep dbus

osc~ · 2007-12-28 17:13:34

ps aux | grep dbus
dbus      7567  0.0  0.0   2388  1024 ?        Ss   14:49   0:00 /usr/bin/dbus-daemon --system
root      7683  0.0  0.1   2256  1208 ?        S    14:49   0:00 dbus-daemon --session --print-address --nofork

true it is running.
is this a bug in arch?

nevertheless, when i insert a memory stick or a digital cam; they dont automount.
what must i do?

hdoria · 2007-12-28 20:09:09

Maybe some other daemon called dbus on system startup?
Did you tried to add your user to the "camera" group?

gpasswd -a user camera

osc~ · 2008-01-17 16:56:45

to me it all seems ok. but still i cant manage to automount a usb flash memory or a camera or a memory stick.
here goes some info that might help:

groups
sys adm lp wheel locate games dbus hal network video audio optical storage scanner camera power users gdm stb-admin adesklets

id noise
uid=1000(noise) gid=100(users) grupos=100(users),3(sys),4(adm),7(lp),10(wheel),50(games),90(network),91(video),92(audio),93(optical),95(storage),
98(power),21(locate),81(dbus),82(hal),101(gdm),97(camera),96(scanner),102(stb-admin),107(adesklets)

DAEMONS=(syslog-ng dbus hal network netfs samba sonypid @hplip @ptal-init @cups !crond @alsa @sshd ipw3945d fam @stbd)

thanks

osc~ · 2008-01-20 00:13:19

could anybody give me a hand with this one. i am stuck. everything seems ok, but it still wont auto mount.

Last edited by osc~ (2008-01-20 00:21:25)

freakcode · 2008-01-20 00:22:43

osc~:

To automount your camera on connecting it, you need to (I know you already have some steps, but just to list it all):

1 - Have HAL and dbus properly instaled and up to date
2 - Have "hal" daemon entry on rc.conf (no need to start dbus, hal starts dbus by itself)
3 - Add your user to the groups: dbus, storage, camera. Use:

gpasswd -a <user> <group>

as root
4 - If you use GNOME, start the following process via the GNOME Session Preferences on every login:

gnome-volume-manager --sm-disable

This will do the trick.

osc~ · 2008-01-20 00:27:51

steps 1,2,3 are ok.
if i type:

noise ~  $  /etc/rc.d/hal start
:: Starting Hardware Abstraction Layer                                   [FAIL] 
noise ~  $  /etc/rc.d/dbus start
:: Starting D-BUS system messagebus                                      [BUSY] Failed to start message bus: The pid file "/var/run/dbus.pid" exists, if the message bus is not running, remove this file
                                                                         [FAIL]

i get these errors even though at startup they manage to load.

freakcode · 2008-01-20 00:35:54

To start/stop daemons after boot you need to be logged as root, and doesn't look like you're:

noise ~ $ /etc/rc.d/hal start
...

Last edited by freakcode (2008-01-20 00:39:10)

osc~ · 2008-01-20 00:40:53

i actually had tried it as root as well, but ended up posting as normal user.

root /home/noise  #  /etc/rc.d/hal start
:: Starting Hardware Abstraction Layer                                   [FAIL] 
root /home/noise  #  /etc/rc.d/dbus start
:: Starting D-BUS system messagebus                                      [BUSY] Failed to start message bus: The pid file "/var/run/dbus.pid" exists, if the message bus is not running, remove this file
                                                                         [FAIL]

man what a problem.

Last edited by osc~ (2008-01-20 00:41:26)

freakcode · 2008-01-20 02:24:20

"hal start" will NEVER work if HAL is already running. Use "hal restart" instead.

Anyway, if HAL is already running, you shouldnt need to do anything else than the above instructions to get the camera automounting working.

Last edited by freakcode (2008-01-20 02:27:10)

Pudge · 2008-01-20 04:10:51

osc~ wrote:

dbus and hal wont work.
i would like to automount my camera or memorystick
this is the daemons in the rc.conf
DAEMONS=(syslog-ng network samba hal sonypid hplip ptal-init cups netfs crond alsa sshd fam ipw3945d stbd)
cheers:)

When Arch boots up, the Daemons are started in the order they are listed in the /etc/rc.conf file. If some Daemons are dependent on others, then the order is important. For example, fam should be started before hal, and you have it the opposite. Plus, portmap isn't even listed in your rc.conf and I THINK (emphasis on think) portmap is necessary for automount. Other examples are, network needs to be started before firestarter, and netfs needs to be started before sshd. Here is a listing of my DAEMONS line in my /etc/rc.conf file. Try rearranging the order of startup and add portmap to the list.

DAEMONS=(syslog-ng network firestarter netfs sshd crond portmap fam dbus hal !avahi-daemon samba cups stbd alsa)

HTH

Pudge

Last edited by Pudge (2008-01-20 04:15:59)

Zer0 · 2008-01-20 19:38:37

What info does dmesg show after you plug in your devices?

osc~ · 2008-01-21 01:53:22

hi
i changed my daemons as you recommended.

DAEMONS=(syslog-ng network netfs @sshd crond portmap fam dbus hal samba sonypid @hplip @ptal-init @cups  @alsa  ipw3945d  @stbd)

but still nothing.

Pudge wrote:

osc~ wrote:
dbus and hal wont work.
i would like to automount my camera or memorystick
this is the daemons in the rc.conf
DAEMONS=(syslog-ng network samba hal sonypid hplip ptal-init cups netfs crond alsa sshd fam ipw3945d stbd)
cheers:)
When Arch boots up, the Daemons are started in the order they are listed in the /etc/rc.conf file. If some Daemons are dependent on others, then the order is important. For example, fam should be started before hal, and you have it the opposite. Plus, portmap isn't even listed in your rc.conf and I THINK (emphasis on think) portmap is necessary for automount. Other examples are, network needs to be started before firestarter, and netfs needs to be started before sshd. Here is a listing of my DAEMONS line in my /etc/rc.conf file. Try rearranging the order of startup and add portmap to the list.
DAEMONS=(syslog-ng network firestarter netfs sshd crond portmap fam dbus hal !avahi-daemon samba cups stbd alsa)
HTH
Pudge

osc~ · 2008-01-21 01:54:31

here is the dmesg part.

sd 4:0:0:0: [sdb] 1942528 512-byte hardware sectors (995 MB)
sd 4:0:0:0: [sdb] Write Protect is off
sd 4:0:0:0: [sdb] Mode Sense: 87 00 00 00
sd 4:0:0:0: [sdb] Assuming drive cache: write through
sd 4:0:0:0: [sdb] 1942528 512-byte hardware sectors (995 MB)
sd 4:0:0:0: [sdb] Write Protect is off
sd 4:0:0:0: [sdb] Mode Sense: 87 00 00 00
sd 4:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1

Zer0 wrote:

What info does dmesg show after you plug in your devices?

osc~ · 2008-01-23 03:48:33

freakcode wrote:

"hal start" will NEVER work if HAL is already running. Use "hal restart" instead.
Anyway, if HAL is already running, you shouldnt need to do anything else than the above instructions to get the camera automounting working.

i did sudo /etc/rc.d/hal restart and it started fine.
so then i rebooted my computer.
but still i cant automount anything.
cheers

dw · 2008-01-23 05:42:58

osc~ wrote:

freakcode wrote:
"hal start" will NEVER work if HAL is already running. Use "hal restart" instead.
Anyway, if HAL is already running, you shouldnt need to do anything else than the above instructions to get the camera automounting working.
i did sudo /etc/rc.d/hal restart and it started fine.
so then i rebooted my computer.
but still i cant automount anything.
cheers

hi osc~.

i experienced exactly the same problem on my girlfriend's laptop. as it turned out, i once installed gparted which created some hal-specific file in /usr/share/.... which prevented removable devices from being mounted by gnome. i hope this information is helpful for you.

cheers...

osc~ · 2008-01-23 16:57:40

hey dw
thanks for the help, but i cant really know how it could help.
what did you do to solve the problem?

dw wrote:

osc~ wrote:
freakcode wrote:
"hal start" will NEVER work if HAL is already running. Use "hal restart" instead.
Anyway, if HAL is already running, you shouldnt need to do anything else than the above instructions to get the camera automounting working.
i did sudo /etc/rc.d/hal restart and it started fine.
so then i rebooted my computer.
but still i cant automount anything.
cheers
hi osc~.
i experienced exactly the same problem on my girlfriend's laptop. as it turned out, i once installed gparted which created some hal-specific file in /usr/share/.... which prevented removable devices from being mounted by gnome. i hope this information is helpful for you.
cheers...

dw · 2008-01-23 17:51:46

hey.

i just uninstalled gparted (which is probably not necessary) and deleted the file /usr/share/hal/fdi/policy/gparted-disable-automount.fdi. after a reboot, automounting worked fine again in gnome. i really hope this information is helpful for you to get automounting working again

cheers

clarence · 2008-01-25 01:12:09

I just did some quick experiments...

/usr/share/hal/fdi/policy/gparted-disable-automount.fdi
is created by gparted when it starts up. when gparted crashes it does not get removed.

simply starting gparted again and then exiting gparted cleanly is enough to remove it and get my system working correctly. no reboot was needed on my system.

Taylor · 2008-01-25 02:34:11

As far as I know, dbus doesn't need to be included in the DAEMONS list anymore I believe. If you have added your user to the groups listed in previous posts, you need to logout to take effect. HAL needs to be in list though.

dw · 2008-01-25 05:08:03

clarence wrote:

I just did some quick experiments...
/usr/share/hal/fdi/policy/gparted-disable-automount.fdi
is created by gparted when it starts up. when gparted crashes it does not get removed.
simply starting gparted again and then exiting gparted cleanly is enough to remove it and get my system working correctly. no reboot was needed on my system.

thx clarence. nice to know that...

Crooksey · 2008-01-25 09:43:13

If this isnt sloved yet, i reccomend.

pacman -Syu #fix any file erros

Then remove dbus from rc.conf, I dont have it within my rc.conf and hal works fine.

Or failing that, remove all deamons from rc.conf that arent essintal, start your computer, then try starting HAL manually.

osc~ · 2008-01-25 13:19:41

yes, finally!!!!!
thanks a lot dw and clarence.
it was the problem with gparted that caused this.
i just started gparted and then closed it. and it worked. now everything automounts.
cheers!!!

Arch Linux

#1 2007-12-28 03:48:29

[solved] hal and dbus wont work

#2 2007-12-28 07:35:26

Re: [solved] hal and dbus wont work

#3 2007-12-28 08:35:32

Re: [solved] hal and dbus wont work

#4 2007-12-28 17:13:34

Re: [solved] hal and dbus wont work

#5 2007-12-28 20:09:09

Re: [solved] hal and dbus wont work

#6 2008-01-17 16:56:45

Re: [solved] hal and dbus wont work

#7 2008-01-20 00:13:19

Re: [solved] hal and dbus wont work

#8 2008-01-20 00:22:43

Re: [solved] hal and dbus wont work

#9 2008-01-20 00:27:51

Re: [solved] hal and dbus wont work

#10 2008-01-20 00:35:54

Re: [solved] hal and dbus wont work

#11 2008-01-20 00:40:53

Re: [solved] hal and dbus wont work

#12 2008-01-20 02:24:20

Re: [solved] hal and dbus wont work

#13 2008-01-20 04:10:51

Re: [solved] hal and dbus wont work

#14 2008-01-20 19:38:37

Re: [solved] hal and dbus wont work

#15 2008-01-21 01:53:22

Re: [solved] hal and dbus wont work

#16 2008-01-21 01:54:31

Re: [solved] hal and dbus wont work

#17 2008-01-23 03:48:33

Re: [solved] hal and dbus wont work

#18 2008-01-23 05:42:58

Re: [solved] hal and dbus wont work

#19 2008-01-23 16:57:40

Re: [solved] hal and dbus wont work

#20 2008-01-23 17:51:46

Re: [solved] hal and dbus wont work

#21 2008-01-25 01:12:09

Re: [solved] hal and dbus wont work

#22 2008-01-25 02:34:11

Re: [solved] hal and dbus wont work

#23 2008-01-25 05:08:03

Re: [solved] hal and dbus wont work

#24 2008-01-25 09:43:13

Re: [solved] hal and dbus wont work

#25 2008-01-25 13:19:41

Re: [solved] hal and dbus wont work

Board footer