Summary: | No input possible if hald not running | ||
---|---|---|---|
Product: | xorg | Reporter: | Stefan Dirsch <sndirsch> |
Component: | Server/General | Assignee: | Xorg Project Team <xorg-team> |
Status: | RESOLVED NOTABUG | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | normal | ||
Priority: | medium | CC: | eich, mat, peter.hutterer |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Stefan Dirsch
2009-06-19 08:19:17 UTC
no. you can start up hald after X has started already. HAL is default configuration, if you need something other than the default you need an xorg.conf. Sure, hald should be running, if you don't want to use a xorg.conf. But if it's not - for which reasons whatsoever? What's the purpose of starting X at all without any input possibility? It's just confusing IMHO. X could also wait until hald is available. What about keeping this as enhancement? you can start X before starting HAL, which - IIRC - shaves about a second or so off boot time. we actually had a startup dependency on HAL until not too long ago and removed it for this very reason. This is news to me. Last time I tried this, this was just not possible. Could this be a new feature of upcoming xorg-server 1.7? You're right. I've been stupid. # sudo /etc/init.d/haldaemon stop # X X.Org X Server 1.6.1 [...] (EE) config/hal: couldn't initialise context: (null) ((null)) # sudo /etc/init.d/haldaemon start (II) config/hal: Adding input device Logitech USB Receiver (II) LoadModule: "evdev" [...] So indeed X can be started before hald. Good to know this. :-) Sorry for wasting your time, Peter. |
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.