> It only seems to occur when using the HAL-configured keyboard. BETTER WORKAROUND: Try to edit the /etc/X11/wdm/Xreset_0 file and add the command /bin/kill -n 15 `cat /tmp/.X0-lock` note the backticks for shell expansion. an explanation follows.
It looks like an issue with Xorg and (possibly) HAL. The problem is that you get an XKB error after sending Xorg a SIGHUP, which is what wdm does by default to reset the X server. The specific error is: XKB: no components provided for device Virtual core Keyboard What's needed is some other signal. I've found SIGTERM works (15). NOTE you CANNOT set DisplayManager*reset 15 in wdm-config because it doesn't work. _Another_ bug in this program prevents some of the config options from having any effect. If you're good at scripting and happen to run multiple xservers, you can edit Xreset to check the display number and have it SIGTERM the correct Xserver. Adam Glover -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
