X.org will stop responding to mouse clicks on Ibex with Xinerama. Occurs frequently, Fatal Error.

[SteveA]

This bug is a duplicate of bug 296167. I'm just reporting it again because it is miscategorized. It is being shown as an nvidia bug, but it also happens with mga and ati drivers.

I personally have multiple machines with mga dual head that have this problem.

Description of problem:
  The mouse will move normally, but mouse clicks are not registered.

Reproducing:
  I can consistently reproduce the bug within about 30 seconds by opening firefox full screen on the two moniters then going back and forth between the two, click to change focus. There must be some kind of timing issue, because it is easier to reproduce when firefox is doing something relatively processer intensive. (It isn't a firefox issue, since I have had the problem occur with other apps - gphpedit and gnome terminal)

Getting mouse clicks back:
  I can get mouse clicks back by logging out (ctrl-alt-bckspce) and back in, or by taking a non maximized window and using keyboard hotkeys move it from one moniter to another (and sometimes back again). This is as described in a comment on bug 296167.

I would be happy to provide any needed logs, but my situation matches many of the ones already posted in bug 296167. I have a new Intrepid desktop install on an LTSP server with multiple clients with matrox dual head graphics cards. I have changed the kernel on the server to the server kernel (since I have 8G of ram there), and I have installed updated mga drivers to make xinerama work at all with mga in intrepid (as described in bug 292214).

Ubuntu bug reporting documentaion:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu.
 lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10
2) The version of the package you are using, via 'apt-cache policy packagename' or by checking in Synaptic.
  I don't know which package it is. It isn't the mga driver since others are reporting it with nvidia and ati, so I'll give you xorg and xinerama
apt-cache policy xorg
xorg:
  Installed: 1:7.4~5ubuntu3
  Candidate: 1:7.4~5ubuntu3
  Version table:
 *** 1:7.4~5ubuntu3 0
        500 http://us.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

apt-cache policy libxinerama1
libxinerama1:
  Installed: 2:1.0.3-2
  Candidate: 2:1.0.3-2
  Version table:
 *** 2:1.0.3-2 0
        500 http://us.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

3) What you expected to happen
mouse working
4) What happened instead
mouse stops clicking

[Bryce Harrington (bryce)]

[This is an automated message]

Hi steve-encoremusic,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

Please attach the output of `lspci -vvnn` too.

[Bill Childers (bchilders)]

I am also experiencing this issue - along with a fairly large population of my company. We run dual head desktops, with Nvidia video chipsets, in Xinerama mode, and everyone who's upgraded to Intrepid has seen it.
The problem description posted by the prior poster matches exactly, except he is running mga while we're on nvidia.

I am attaching lscpi -vvnn output along with my Xorg.0.log file (ironic, the system exhibited this bug while creating this report).

[Bill Childers (bchilders)]

Adding xorg.0.log.

[Bill Childers (bchilders)]

Adding xorg.conf

[Bill Childers (bchilders)]

OK, got a really goofy workaround. When the bug exhibits itself, pushing ALT-F7 and clicking a couple of times restores the mouse's ability to click. Sounds crack-fueled, but it works.

[Bill Childers (bchilders)]

Workaround refined: Alt-F7, then you have to move the window to the other display entirely, and then click. That seems to work 100% reliably at the moment.

[Bill Childers (bchilders)]

Can we get an update, please?

[Bill Childers (bchilders)]

Did further research and this bug is a dupe of 296167 - and the people on that bug have some good work arounds.
https://bugs.launchpad.net/ubuntu/+bug/296167