Starting using baselayout-2, openrc and xorg-server-1.5 with fdi rules for keyboard (and mouse). If problem occurs and an hard reboot is needed, on next start, dbus will hang on /var/run/dbus.pid existing file and won't start. Hald hangs cause dbus is not started and don't start too. But xdm initscript start without taking care about that and user is facing a cool & nice login screen without possibility to log in ... Of course impossible to switch on a tty (no keyboard ...) to remove the dbus.pid file and restart dbus/hald/xdm initscripts. Reproducible: Always Steps to Reproduce: 1. hard reboot the system and restart 2. 3. Actual Results: HID unusable when they're configured through fdi's file ... Expected Results: When dbus initscript find "dbus.pid" file remove it and start OR include hard dependency on dbus/hald in xdm initscript.
Yea, I noticed this too and was going to file a bug report. x11 team: should xdm init script "need hald" ?
NAK, Xorg just needs dbus to be running. HAL can come up on its own whenever it wants and Xorg will pick up input devices at this point. We _could_ add the dbus dep in the init script, but again, X doesn't need it per se... Maybe "after dbus" ? Thanks
Well, the problem is that if dbus doesn't come up[1], you can't even get back to the normal console because none of the keyboard works (ctrl + alt + f1) this is a real pita because unless you have ssh access you need a live cd* to get back into the host and "reset" it to a sane state. [1]: If dbus doesn't come up, then hald won't come up. This makes xorg not have any input devices but it still comes up. Since hald already has "need dbus" in it, we need a way for xorg to *NOT* start if dbus (or hald) fails to start. * - Or some other equally annoying way to remove the dbus pid file.
@darkside : if you entered in "Interactive mode" at init, you can "don't start" xorg then remove pid files then restart dbus/hald/xdm initscript. That's why I don't put this bug as "critical" in first intention. But it is really a pita to stay in front of your "cool themed desktop manager" and couldn't do *nothing* but push shutdown front computer switch (only if acpi is correctly configured and running) ... Anycase, what is the problem to remove the pid files at init start is it exists ???
(In reply to comment #4) > @darkside : if you entered in "Interactive mode" at init, you can "don't start" > xorg then remove pid files then restart dbus/hald/xdm initscript. I'm aware. See the "*" of my previous comment. Annoying and you shouldn't have to go into interactive mode to get to "don't start xdm"
This is fixed by new xdm init script. AFAIK it can require HAL based on user configuration or based on DM system used.
