Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I don't know if this is the right place to post this but here goes anyway.
ASUS Pro50n Laptop
Distro: Arch Linux
I've recently installed Arch linux with the gnome desktop environment, and everything is working fine apart from HAL and DBUS. I'm not sure why this problem is happening and I have no idea about any settings for HAL and DBUS all I know is what it says in the wiki.
The problem I have is that HAL and DBUS fail to start. I have tried /etc/rc.d/hal start and get the message BUSY.. then FAIL. I have tried /etc/rc.d/dbus start and get exactly the same. I have tried restart and that also fails.
*EDIT* I have just tried /etc/rc.d/dbus start again without changing a thing and dbus has started successfully but HAL still fails.
The further problem, which I think is related to HAL not starting... possibly... Is that I can't watch DVD's / anything in the DVD drive. I can see it in Places >Computer as "CD/DVD Drive: 3_MEN_IN_ANOTHER_BOAT" but when I click to load it or if I open Totem and try and load it all I get is the error: Unable to mount location: Not Authorized. Is this related to HAL or is this a completely different issue?
*EDIT* fixed the HAL problem, reinstalled xf86-input-evdev package and it seemed to fix the problem. However I am still having a problem with watching DVD's can anyone help with this?
**EDIT** Fixed this problem, it was related to consolekit. I am still using console login with startx, and for some reason consolekit doesn't automatically start with the gnome-session. When using GDM, however, it does. The solution is to add "exec ck-launch-session gnome-session" to your ~/.xinitrc file and viola! it auto-mounts and allows access to auto-mounted devices straight away.
Last edited by Colonel-1990; 01-21-2010 at 09:24 AM.