This bug affects my multiseat system with Karmic. I am using just gdm and due to the latest gdm doesn't support multiseat I had to downgrade to gdm 2.20. When my X is starting, there are some error messages in the xorg.log which do not affect any functionality as far as I can say
(II) config/hal: Adding input device Logitech 2.4GHz Cordless Desktop
(EE) config/hal: NewInputDeviceRequest failed (8)
(II) config/hal: Adding input device UVC Camera (046d:0990)
(EE) config/hal: NewInputDeviceRequest failed (8)
(II) config/hal: Adding input device Logitech 2.4GHz Cordless Desktop
(EE) config/hal: NewInputDeviceRequest failed (8)
(II) config/hal: Adding input device Power Button
(EE) config/hal: NewInputDeviceRequest failed (8)
(II) config/hal: Adding input device Microsoft Microsoft Wireless Optical Desktop® 1.00
(EE) config/hal: NewInputDeviceRequest failed (8)
(II) config/hal: Adding input device Microsoft Microsoft Wireless Optical Desktop® 1.00
(EE) config/hal: NewInputDeviceRequest failed (8)
(II) config/hal: Adding input device Logitech 2.4GHz Cordless Desktop
(EE) config/hal: NewInputDeviceRequest failed (8)
(II) config/hal: Adding input device Sleep Button
(EE) config/hal: NewInputDeviceRequest failed (8)
(II) config/hal: Adding input device Logitech 2.4GHz Cordless Desktop
(EE) config/hal: NewInputDeviceRequest failed (8)
(II) config/hal: Adding input device Power Button
(EE) config/hal: NewInputDeviceRequest failed (8)
(II) config/hal: Adding input device Macintosh mouse button emulation
(EE) config/hal: NewInputDeviceRequest failed (8)
The failsage-X, particulary the failsafeXInit script detects these messages it attempts to start the failsafe X even though the original X session is working just fine. Then I get problem that the failsafe X runs into conflict with the original X session and I get message
There already appears to be an X server running on display :0.....
Since I cannot figure out how to get rid of the error messages in my xorg log I have to disable failsafe X as described in comment #32.
This bug affects my multiseat system with Karmic. I am using just gdm and due to the latest gdm doesn't support multiseat I had to downgrade to gdm 2.20. When my X is starting, there are some error messages in the xorg.log which do not affect any functionality as far as I can say
(II) config/hal: Adding input device Logitech 2.4GHz Cordless Desktop equest failed (8) equest failed (8) equest failed (8) equest failed (8) equest failed (8) equest failed (8) equest failed (8) equest failed (8) equest failed (8) equest failed (8) equest failed (8)
(EE) config/hal: NewInputDeviceR
(II) config/hal: Adding input device UVC Camera (046d:0990)
(EE) config/hal: NewInputDeviceR
(II) config/hal: Adding input device Logitech 2.4GHz Cordless Desktop
(EE) config/hal: NewInputDeviceR
(II) config/hal: Adding input device Power Button
(EE) config/hal: NewInputDeviceR
(II) config/hal: Adding input device Microsoft Microsoft Wireless Optical Desktop® 1.00
(EE) config/hal: NewInputDeviceR
(II) config/hal: Adding input device Microsoft Microsoft Wireless Optical Desktop® 1.00
(EE) config/hal: NewInputDeviceR
(II) config/hal: Adding input device Logitech 2.4GHz Cordless Desktop
(EE) config/hal: NewInputDeviceR
(II) config/hal: Adding input device Sleep Button
(EE) config/hal: NewInputDeviceR
(II) config/hal: Adding input device Logitech 2.4GHz Cordless Desktop
(EE) config/hal: NewInputDeviceR
(II) config/hal: Adding input device Power Button
(EE) config/hal: NewInputDeviceR
(II) config/hal: Adding input device Macintosh mouse button emulation
(EE) config/hal: NewInputDeviceR
The failsage-X, particulary the failsafeXInit script detects these messages it attempts to start the failsafe X even though the original X session is working just fine. Then I get problem that the failsafe X runs into conflict with the original X session and I get message
There already appears to be an X server running on display :0.....
Since I cannot figure out how to get rid of the error messages in my xorg log I have to disable failsafe X as described in comment #32.