Bug 22833

Summary:	X should fail to start if hal is not started and evdev if the only available input driver
Product:	xorg	Reporter:	Pacho Ramos <pachoramos1>
Component:	Server/General	Assignee:	Xorg Project Team <xorg-team>
Status:	RESOLVED WONTFIX	QA Contact:	Xorg Project Team <xorg-team>
Severity:	normal
Priority:	medium
Version:	7.4 (2008.09)
Hardware:	Other
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Pacho Ramos 2009-07-18 04:14:38 UTC

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

Comment 1 Peter Hutterer 2009-07-19 03:00:11 UTC

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

Comment 2 Pacho Ramos 2009-07-19 06:59:03 UTC

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.