You are not logged in.
im running arch x64, and kdemod fully updated on my hp tx2000 laptop, i booted this morning (did a big pacman -Syyu last night) and got this message on my boot messages:
:: Starting D-BUS system messagebus
Failed to start message bus: Failed to bind socket "/var/run/dbus/system_bus_socket": Address already in use
my system sames to work fine, although the keyboard didnt work at all after the first boot up (never happened before) so i hard resetted it and it works fine now.
what can i do to fix this, any ideas what it means?
thanks[
Last edited by originalsurfmex (2009-07-14 22:03:55)
Offline
post DAEMONS list from rc.conf
Give what you have. To someone, it may be better than you dare to think.
Offline
Try to see if D-bus i arleady running
Try to restart D-bus
Shell Scripter | C/C++/Python/Java Coder | ZSH
Offline
modules and daemons from rc.conf:
MODULES=(forcedeth !snd-pcm-oss snd-hda-intel fuse wl vhba loop)
DAEMONS=(@syslog-ng @hal @fam !network @netfs @wicd @crond cdemud alsa cups kdm)
...i also restarted dbus as suggested, although i dont understand why:
$ sudo /etc/rc.d/dbus restart
:: Stopping D-BUS system messagebus [DONE]
:: Starting D-BUS system messagebus [DONE]
restarting dbus crashed my printer applet, songbird and a coupla programs, but thats about it...it was already running cuz hal is in my daemons.
Offline
try not to fork hal.
DAEMONS=(@syslog-ng hal @fam !network @netfs @wicd @crond cdemud alsa cups kdm)
Give what you have. To someone, it may be better than you dare to think.
Offline
awesome! thanks a lot, i removed the @ symbol from in front of hal and its all good now...
that should probably be written down somewhere, my keyboard eventually became frozen and the only way to fix things was to enter my rc.conf from my arch32 on another partition...
Offline