I have just suffered this problem: 1. I run "startx" 2. X started with no xorg.conf file at all (great!) but, on my system, only "evdev" input driver is installed, and it needs hal to be running for being able to work 3. As I forgot to start hald, I lost mouse and keyboard being unable to make anything! (yes, I also should be started openssh daemon...) I think that X should fail to start when only a hal-based input driver is available and hald is not running to prevent this situation. Thanks a lot
sorry, this is a configuration issue on your side. X will allow hald to be started later and then hook onto it. This is beneficial at e.g. boot-time as it allows for parallel startup. also, fwiw, evdev is just like any other input driver and blissfully unaware of HAL
Umm, ok, I didn't know that hald would be started after X (in parallel boot setups) Thanks for the info
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.