Update seems to have stopped Xorg talking to mouse and keyboard in Multiseat

Bug #335802 reported by Obrouni
2
Affects Status Importance Assigned to Milestone
multiseat
Invalid
Undecided
Unassigned
nvidia-graphics-drivers-180 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I'm using fully up to date Jaunty (28/2/09) configured with MDM (http://wiki.c3sl.ufpr.br/multiseat/index.php/Mdm)

A update this week, between Monday and about Wednesday/Thursday seems to have made the underlying X server Display:0 stop receiving input events from the mouse and the keyboard.

The nested Xephyr sessions (Displays :1 to :4) running on top of Display:0 still work fine. This proves that the keyboards and mice are still being detected and passing events through to the Xephyr sessions correctly.

This regression or change in behaviour was first noticed by the fact that xorg goes into power saving due to inactivity and then cannot be woken up. Its also seen by the fact you can't change VT's anymore and keyboard LED's don't work.

What do I expect to happen
The underlying Xserver Display:0 receives events from the keyboards and mice so it can still turn the keyboard LED's on and off. It will also not go into power saving if it detects activity on any of the attached keyboards and mice.

What actually happens
The underlying Xserver Display:0 appears as if no keyboard and mice events are being generated, even though they can be seen to be working in Xephyr sessions running on top of it.

Revision history for this message
Bryce Harrington (bryce) wrote :

Not enough information to troubleshoot. See http://wiki.ubuntu.com/X/Reporting for instructions on reporting X issues and https://wiki.ubuntu.com/X/Troubleshooting/HalBreaksKeyboardAndMouse and please provide additional details.

Changed in xorg:
status: New → Incomplete
Revision history for this message
Obrouni (nick-fisk) wrote :

Thanks for those links,

I have done a bit of investigating, the behaviour seems to be linked to this message I am getting in the xorg log:-

[ 0.145343] (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 0.145349] (WW) Disabling Keyboard
[ 0.145355] (WW) Disabling Mouse

For a test I set AllowEmptyInput to FALSE, this re-enabled the keyboard mouse and LED's. However.....

A bug I previously logged and then found fixed with Jaunty regarding the LED's being linked is now a problem again:-

https://bugs.launchpad.net/ubuntu/+bug/300974

Also it seemed that every time I did a ctrl-c the whole X server reset/crashed, so I have reverted the setting for the moment and I am using a panel applet to inform users of the led status.

Revision history for this message
Obrouni (nick-fisk) wrote :

My xorg.conf attached.

Bryce Harrington (bryce)
Changed in multiseat:
status: New → Invalid
Bryce Harrington (bryce)
Changed in xorg (Ubuntu):
status: Incomplete → New
Revision history for this message
Bryce Harrington (bryce) wrote :

Hi nick-fisk,

Thanks for including the attached files. Could you also include your /var/log/Xorg.0.log (or Xorg.0.log.old) from after reproducing the issue?

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-xorglog
Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: New → Incomplete
Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automated message]

In Jaunty (9.04), we have just updated to the latest
nvidia-graphics-drivers-180 package from nVidia, version 180.44.

This package provides fixes for a large number of bugs, and we need your
assistance in testing if it fixes the issue you reported.

To do this, please do the following:

 a. Update to the 180.44 version of -nvidia using your favorite update
     method

 b. Attempt to reproduce your bug

 c. If your bug still remains, please simply reply to this email
     indicating so.

 d. If your bug is now solved, you can help us by setting your bug
     report to Fix Released:
     * In launchpad, go to your bug report
     * Click on the downward pointing arrow under Status
     * Set the Status field to 'Fix Released'
     * Comment on the change, such as, 'Verified fixed in 180.44'
     * Click 'Save Changes'

 e. If the original problem is solved but there are now other problems,
     please close the original bug and open new ones for those issues.

Thank you!

For details on the changes in this version of -nvidia, please see:

   http://www.nvidia.com/object/linux_display_ia32_180.44.html

Revision history for this message
Obrouni (nick-fisk) wrote :

Sorry for the delay, I have only managed to upgrade our multiseat internet cafe box to jaunty release this weekend. It appears now that this problem does not exist anymore, the keyboard led's work and the displays don't go into power saving whilst they are being used.

Bryce Harrington (bryce)
Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.