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

Reported by Pascal R on 2008-11-10
268
This bug affects 21 people
Affects Status Importance Assigned to Milestone
X.Org X server
Fix Released
Critical
Ubuntu
Undecided
Unassigned
Intrepid
Undecided
Unassigned
xorg-server (Fedora)
Fix Released
Unknown
xorg-server (Ubuntu)
High
Unassigned
Intrepid
High
Unassigned

Bug Description

[Problem]
When using Xinerama (such as with multiple video cards), if using an animated cursor, after some time X will stop responding to mouse events. All mouse events are being sent to the root window instead of client applications.

[SRU]
Confirmed fix is released upstream in xserver 1.6.0 and present in Jaunty (as of xserver 1.6.0)

Impact: Severe regression for users of -nvidia and other drivers which still rely on Xinerama, resulting in mouse cursor (and thus much of the GUI) becoming unusable. No reliable workaround known.

Fix: Avoid calling UpdateSpriteForScreen() if the Xinerama extension is loaded

Patch: https://bugs.freedesktop.org/attachment.cgi?id=22373

Test Case: Configure a Xinerama multi-head (3+) layout using -nvidia. Configure the mouse to use an animated cursor; this is optional but makes it easier to reproduce the problem. Move windows around, from one screen to another until the bug is triggered (may take a few tries). Mouse clicking will become disabled, while keyboard and mouse movement continues to work correctly.

Regression Potential: The fix is extremely trivial and highly tied to Xinerama. The net effect is to prevent code from being executed rather than enable it. For non-Xinerama users, there is no chance for regression. For Xinerama users, give the huge number that have reported this as an issue, this bug probably affects all users; furthermore we already have numerous confirmations of the fix and zero reports of side effects. So I think the chance of regression is close to nil.

[Original Report]
After upgrading to Ibex a problem has appeared where after some activity (10-15 minutes), X will suddenly stop responding to any mouse events - the cursor is still there and will move around, but windows won't change focus and clicking the mouse buttons have no effect (in both the focused and unfocused windows). Keyboard still works fine and I can Alt-Tab between windows. Mouse still moves the cursor normally, just will not click anything.

I have a four-monitor Xinerama setup running the latest NVidia drivers on two 8600GT Graphics cards. This setup worked perfectly in Hardy.

Problem is present in 2.6.27-7 & 2.6.24-19, Nvidia Drivers 177 & 173.

Tried with two different wired optical mouses (logitech and microsoft) and problem is present in both.

Once the problem occurs, the only way to get the mouse buttons working again is to Ctl-Alt-Backspace to restart X. Mouse will work fine for a period of time after that.

Strangely - if I have xev running, it won't respond to any events if the mouse is over the window, but if the cursor is at the same height as the window one screen over to the right, it will show events.

I don't think I see anything in dmesg / syslog / Xorg.conf.

amd64 arch w/ 8 GB Ram.

This is driving me absolutely crazy as my computer is pretty much unusable.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 8.10
NonfreeKernelModules: nvidia
Package: xorg 1:7.4~5ubuntu3
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/User Name/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/User Name/bin
 LANG=en_US.UTF-8
ProcVersion: Linux version 2.6.27-7-generic (buildd@crested) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11) ) #1 SMP Tue Nov 4 19:33:06 UTC 2008

SourcePackage: xorg
Uname: Linux 2.6.27-7-generic x86_64
Xrandr:

xkbcomp:

[lspci]
00:00.0 Host bridge [0600]: nVidia Corporation C55 Host Bridge [10de:03a1] (rev a2)
     Subsystem: nVidia Corporation Device [10de:c55e]
01:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 8600 GTS [10de:0400] (rev a1)
     Subsystem: eVga.com. Corp. Device [3842:c773]
03:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 8600 GTS [10de:0400] (rev a1)
     Subsystem: eVga.com. Corp. Device [3842:c773]

Pascal R (pascal-cykod) wrote :
Tim Cole (timothy-j-cole) wrote :

I experienced this same issue also using Xinerama but with only a dual head setup.
I swaped to using a Twinview configuration and have not seen the bug since.
Not sure if Twinview allows greater than 2 monitors, but thought id comment anyway to highlight the Xinerama issue.

Pascal R (pascal-cykod) wrote :

I tried switching to a TwinView configuration but unfortunately I can't get it to work correctly in terms of positioning & maximizing windows (which is more painful than it sounds - everything appears, by default between 2 monitors including notifications and popups)

Thinking it might be MetaCity related I tried installing kubuntu to see if that fixes the problem but the same issues happen.

I've found that if I click carefully with my mouse (wait for windows and web pages to load completely before trying to interact with them, try not to use the mouse as much as possible) I can mostly avoid causing the problem for a couple hours of work time, but inevitably eventually something will happen that triggers the bug.

On the upside I'm polishing up on all my keyboard shortcuts...

Luc (luc-santeramo) wrote :

Hi,

I have the same problem.

Configuration differencies :
Architecture: i686
LANG=fr_FR.UTF-8
VGA compatible controller: nVidia Corporation G86M [GeForce 8400M GT]
2 monitors
And I don't use any 3D effects.

The problem mainly appears when I use ALT+TAB and quickly click on the selected app. But it's not always the case...

I'll try to remove all compiz packages, then try Twinview, then I'll send you a feedback.

Zach (zivester) wrote :

Seen this problem all over the ubuntu forums, and all over launchpad..

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-mouse/+bug/290406
https://bugs.launchpad.net/ubuntu/+bug/296118

I also have the same problem, and as I reported in the forums, I have the same problem no matter what type of mouse I use (all USB)... (one wired, one wireless, and one bluetooth). Happens in Gnome, and also in XFCE if I remember correctly. This is happening on both my work and home computer.

AMD64 + 2GB + nvidia 177 + xinerama (two cards, two monitors).
AMD64 + 2GB + nvidia 177 + xinerama (one card, two monitors).

After a random amount of time (minutes, hours, sometimes a day...) , Mouse only moves, no focus or clicking works. Computer runs find otherwise. Ctrl + Alt + F1 to Ctrl + Alt + F7 does nothing... only Ctrl + Alt + Bksp or Ctrl + Alt + Del gets me back with a working mouse.

Pascal R (pascal-cykod) wrote :

Hi Zach,

That sounds like the same problem, I've searched all over the the forums and the Internet in general for anyone with a work around and can't come up with anything.

Seeing as it really seems to be somehow triggered by window focus changes, I switched from focus-follows-mouse to click-to-focus and that seems to have helped some, as the problem didn't trigger for over an hour, but it didn't solve the problem.

ThomasAdam (thomas-adam22) wrote :

Hmm -- I see from the dependencies file that XCB is in use. I wonder if the problem lies in there, somewhere?

-- Thomas Adam

Zach (zivester) wrote :

If there is anything I can post from my configuration then let me know... this is my first time using launchpad, and so I am unfamiliar with the process. Also if there is anything I should do if I see the problem again, also please let me know.

Luc (luc-santeramo) wrote :

I have removed all compiz packages, and the problem is still present.
All my tests have been done with click-to-focus, using a touchpad or cordless mouse.

Walter White (walterjwhite) wrote :

I am having this issue on a db90000 with xinerama. I haven't been able to get compiz functioning with this setup for whatever reason. Normally it's just go into Appearance -> Effects -> and then check one of those settings, but it is not allowing me to set those complaining the Composite extension is not available I believe. My refresh rate also appears to be a bit slow - when typing text or scrolling in Firefox, the page refreshes really slowly.

Zach (zivester) wrote :

I also meant to add in my earlier post, that I have done both an upgrade AND a fresh install and these problems still exist. So it is my belief that it has nothing to do with an upgrade at all.

rooijan (rrossouw) wrote :

Exact same issue here. Lose ability to use mouse clicks. Moving mouse still works. Keyboard works.

- Ubuntu 8.10 amd64....
- Linux U810 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:06 UTC 2008 x86_64 GNU/Linux
- Xinerama two monitors running on two NVidia's (NV34 [GeForce FX 5500])
- Compiz disabled

Note to self learn more gnome shortcuts.

Ibex + Xinerama seems to be common to everyone affected. I updated the name of the bug to reflect that. Maybe this will trigger someone to take a look..

Bryce Harrington (bryce) on 2008-11-14
Changed in xorg:
status: New → Confirmed
1 comments hidden view all 205 comments
Travis Hegner (thegner) wrote :

I am also suffering from the same bug.

thegner@it-thegner:~$ uname -a
Linux it-thegner 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:06 UTC 2008 x86_64 GNU/Linux

Ubuntu 8.10 amd64
3.0 Ghz quad core
8 Gb RAM

I am running three monitors on two nvidia cards (8800 GT / 8600 GT), with xinerama.

I found on a post somewhere to try (sorry no link handy):

Section "ServerFlags"
    Option "AutoAddDevices" "false"
EndSection

This has significantly reduced the number of times that it happens, but it still happens 1-3 times per day.

As with everyone else, the only fix is a full reboot, or an X restart (ctrl-alt-backspace).

Another oddity that I've noticed with this bug, I am still able to alt-tab between apps, and ctrl-alt-arrow, to switch workspaces, but the little notification window that pops up with those actions is seems to be 'stuck' on one monitor, where normally it is on whichever monitor the cursor is on.

As someone else mentioned above with the mouse events on the wrong monitor: I have noticed that the cursor will still change (i.e. to the text beam), but not where it's supposed to, if i have gedit running on my center monitor, the cursor will change on the right monitor in the area that would be the text area if gedit were running on the right monitor. Likewise for a nautilus window on the left monitor, the cursor will change to a text beam on the center monitor in what would be the path space of the nautilus folder. Sorry for the mouth-full on that one, I hope you followed it OK.

I have also disabled my screen saver because others out there have attributed similar problems to gnome-screensaver, but I haven't seen any difference since then.

I'm not sure what else I should provide. If I can be of any help with information of symptoms, let me know.

rooijan (rrossouw) wrote :

I just want to confirm that for me going back to Twinview worked. Mouse is fine for more than a day. Working with the bug was not acceptable.

Zach (zivester) wrote :

OK, so my computer has just fallen victim to this as we speak... now what should I capture and post here?

Remember that I don't have use of a mouse, so explicit instructions(as I'm new to this) are appreciated...

And oh ya, the sooner the better so I can go ahead and restart ;)

Zach (zivester) wrote :

Wish I could edit comments... but I've been noticing that I get this problem a lot whenever I'm using VLC... maybe this has something to do with it? Don't know if this is the reason, but it definitely triggers it some of the time.

Zach (zivester) wrote :

Well too late for me, after 30 minutes whole computer locked up. Caps Lock and Scroll Lock blinking.

Travis Hegner (thegner) wrote :

I have also noticed that using either rdesktop, or vmware workstation seems to trigger it. I also installed the frets on fire game, and simply opening that application and closing it again triggers the bug ever single time. I don't notice the same cursor changing anomaly that described before when triggering the bug that way, but every other symptom is the same.

I also adjusted the screen res for frets on fire to match the screen res of the os, and the bug still triggers. I have not tried windowed mode yet.

Pascal R (pascal-cykod) wrote :

As a followup, switching to a TwinView setup only works if Xinerama stays off completely - If I turn on TwinView on each of the two cards and turn in Xinerama the problem will still appear.

If I leave Xinerama off - and so end up with two X screens each of which is spread over two monitors, the mouse will work, it's just not terribly functional the there are two task bars, each of which is spread over two screens and windows can't move between the two screens.

On the upside, it's way faster. And by way faster, I mean I that Firefox in Linux on par with it's Windows version (same machine booted into XP) whereas before something like Google Maps was a exercise in frustration and pain. I'd anticipated that Xinerama was slowing down performance but I had no idea how much...

Travis Hegner (thegner) wrote :

I've struggled with twinview as well before upgrading to 3 monitors. It will do it's own xinerama type implementation, but I've noticed that the nvidia-settings does not turn off xinerama in the xorg.conf if it has already been set. This is usually only a problem if you merge settings when saving your xorg.conf.

Double check your xorg.conf and make sure you don't still have xinerama enabled, then reboot. That may prevent the task bar from spanning across two monitors.

on a side note, I read that 8.10 was supposed to be implementing some new Xrandr features, that were supposed to allow those of us with multiple displays to can xinerama, but I have yet to figure out how to make that work, or if it's possible with the proprietary nvidia drivers.

I have the same issue as described and I feel that this bug in terms of Importance should move to high Importance.
This renders Ubuntu 8.10 in terms of Productivity to Null.

I have Dual Video Cards; Geforce 8500 - with the Restricted Nvidia Drivers 177 Installed.
I have configured my 3 LG 23" LCD Monitors with Twin View / Xinerama

- Heavy user of Gnome-RDP since Terminal Server Client does not seem to have Clipboard Support
- In essence it seems that this bug will happen when RDP Sessions or VNC Sessions are opened for a long period of time.

I experience this problem approximately 2-3 Times a day, and sometimes more. All keyboard functions still seem to function. Login off my Session with CTR-ALT-DEL and using the keyboard arrow keys to log-off then login back in will allow my mouse to have click functionalities again.

When this bug comes to life, I am able to see my mouse cursor moving, but cannot click on anything. All keyboard keys such as combinations of ALT-Tab and etc... functions.

I have a Logitech Laser Mouse MX Something.

Re-Installed Intrepid as well, fresh Installation with all updates. Ubuntu 8.10 / x_64

Hardware:

- Quad Core Intel Q6600
- 8GB of Memory
- 3x LG Monitors 23"
- 2x Nvidia Geforce 8500 PCI Express Video Cards

Travis Hegner (thegner) wrote :

MetraDynamix,

Try adding this section to your xorg.conf:

Section "ServerFlags"
    Option "AutoAddDevices" "false"
EndSection

This did not completely eliminate the bug, but it reduced it's frequency by at least half or better. It also fixed some strange keyboard issues I was experiencing with vmware workstation.

Nelson (nrescobar+lp) wrote :

I have the same issue. The main difference is that I'm using a Matrox G550 with xinerama instead of nvidia as everyone else here seems to be using. I've been running into the problem on average about once a day. Restarting X fixes the problem. I had been running Hardy for 6 months with no problem on the exact same setup.

After reading this ticket yesterday, I opened an xev on each of my two heads. After loosing the ability to click and change focus I experimented with those two xev windows. It seems that when I move the mouse around the screen0, the xev on screen1 starts showing events. Before the problem, moving the mouse in the xev window produced coordinates around 2080,600. After the mouse problem started, hovering on the xev window didn't produce events, but moving around screen 0 at location 800,600 did produce events and the events had the coordinates 800,600. In other words the events seemed to be coming from a location exactly one screen width ( in my case 1280 ) away from where they were supposed to be.

Also, I noticed that the cursor changed from the usual pointer to the text entry cursor on screen0 corresponding to the placement of windows on screen1, again exactly one screen away.

Just for full disclosure, the xorg mga driver in intrepid is broken and needs a patch to get xinerama working in the first place. See bug 292214 for details. But after finding this ticket, I think my mga issues are independent of this mouse issue.

Hops (drhops) wrote :

I have this problem as well using nvidia 177 + xinerama. I'm trying out the twinview fix (kdesudo nvidia-settings => display configuration => configuration => configure => change from xinerama to twinview) with no problems so far. Using twinview, performance is much better and kde4 transparency + desktop effects are now enabled. Thanks for the suggestion!

Throwing another "me too".

x86_64, Ibex, Xinerama (2 screens, 2 Nvidia NVS 290 cards), using the 177.80 nvidia drivers.

This bug has basically chased me off my desktop and back to my laptop. This thing needs attention, and quick.

A quick observation:

After the session has been running for a little while, dragging a window from one screen to the other seems to be a precursor to things failing shortly afterwards.

Anywhere between a few minutes and a few hours, the mouse buttons stop responding. The mouse itself keeps moving and remains visible.

The trigger is when moving the mouse between two xinerama screens.
No messages about this are logged in Xorg.0.log, messages, or any other log file.
In this state xev does not see any mouse events.

When X is restarted the mouse buttons are recognized again.
Another recovery is running a synergy server locally and connecting to it with the client. Note that this only works when running synergyc from the konsole in one of the xinerama screens. Doing the exact same thing in the other screen has no effect.

OS: Gentoo
xorg-7.4; xorg-server-1.5.2

The bug was first reported by Eric Stein. See also: https://bugs.gentoo.org/show_bug.cgi?id=243496 for more details.

Another me too. For me, at most it happens once a day. Nvidia and Xinerama. I've switched to twinview as Hops mentioned above (sudo nvidia-settings => display configuration => configuration => configure => change from xinerama to twinview)
It seems to work the same as Xinerama except that compiz now works and it does seem snappier.

Travis Hegner (thegner) wrote :

Just to make sure everyone is clear. The Twinview option is only viable to those with 2 or less monitors. Twinview does not functionally support 3 or more monitors, so this is still an issue for anyone that is required to use xinerama for this reason.

Robstarusa (rob-naseca) wrote :

I have this problem with 2 NVS 285 cards & 4 monitors + xinerama. I have to ctl-alt-backspace to fix it -- about 5-7 times per day. It is REALLY annoying.

Also, to make this ALWAYS happen, start Applications -> Internet -> terminal server client and leave your focus on the "computer" field.

Changing your focus to "password" or "username" field prevents the problem from happening in this instance.

Robstarusa (rob-naseca) wrote :

Whoops, to clarify my previous post...to always make this happen,

Go to Applications -> Internet -> terminal server client. Click the right arrow next to "Computer" select the computer and press "ENTER".

You will/should see a ghost menu while your rdp session opens behind it.

Nelson (nrescobar+lp) wrote :

After having run into this problem twice within 15 minutes I noticed exactly what I was doing when it happened, and tried repeating it. In both cases, I was moving out of a firefox window on my Screen0 to a window on Screen1.

After a little experimentation, now I can pretty much cause the mouse to quite working withing 30 seconds of trying. Open up two firefox windows and put one each screen, leaving a small gap of background between the firefox window and the edge of the screen. Now flick your mouse between both firefox windows (I have focus following the mouse). For me, within 20 flicks the mouse stops working and starts misbehaving.

I've also gotten it to start misbehaving with two emacs windows, but firefox seems the best choice for reproducing it quickly for me. Someone else should give the above method a try and confirm it reproduces the problem in a short time. Having a quick way of reproducing the problem might help this bug along.

xianthax (xianthax) wrote :

confirmed and killing my productivity...

this may be helpful in tracking it down.

system specs:

Ubuntu 8.10
Intel Q6600 @ 3.2Ghz
Asus P5E WS Pro Mainboard
8GB ram
2 x Nvidia 8600GTS (177.80 drivers)

Screen setup: 3 screens, each a separate x session all merged with xinerama, arranged from left to right as: GPU0(screen0), GPU1(Screen0), GPU1(screen1). All normal orientation and all 1680 x 1050 screens.

Always appears to happen when the mouse is moving across the GPU boundary. And here is the interesting bit that may help solve this. I often run 1 application on each screen but not maximized to the screen, there is a one inch gap or so around the edges of each application window on each screen. The apps that are on GPU1S0 (middle) and GPU1S1(right) have custom cursor icons, when the mouse bugs out, if i move the mouse to GPU0S0 (left) and put it in the area where the windows are on the other screens, the cursor icon changes and moving it around more subtly i can get the various cursor from the apps that are running on the other 2 screens (2 instances of the same app so i can't tell which screen X thinks the mouse is really on). Clicking anywhere has no effect, despite attempts to click on the left screen to create action on one of the others.

Testing: To test this hypothesis i setup 3 instances of xev, one on each screen roughly the same size and in the same place. I trigger the bug (waving mouse back and forth quickly across the gpu boundary seems to be 100% effective at causing this in a short amount of time, thus i recommend everyone avoid doing this when you don't want to reboot X).

results: movement on GPU0S0 (left) in the area of the xev window on GPU1S0 (center) triggers events on the xev on GPU1S0 (center), indicating that X thinks the mouse is one screen to the right of where it is displayed, presses and releases are also recorded although they have no effect on running applications (probably because the coordinates sent to the app are out of bounds). Mouse movement / events anywhere on GPU1S0 or GPU1S1 cause no xev events on any screen indicating its not simply an off by 1 screen issue.

this and everything else we've seen indicates to me this is a problem in handing off cursor control from 1 gpu to the the other gpu.

I'm out of time tonight but i will try disabling hardware acceleration of the cursor to see if it has any effect on this. I could also rearrange my screens to further test the GPU boundary theory.

cheers,

x

JPHein (jp-jphein) wrote :

I also have this problem.
Ubuntu 8.10 64-bit (updated today)
Nividia 177
Xinerama w/ 4 Screens

Reproduce bug:
1. Open Firefox (with a bunch of Restored tabs including one with flash content)
2. Move Firefox window to different monitor.
3. Right click on the Firefox entry in the "Window List" and select "Move"
4. Left click anywhere. (The mouse clicks stop working)

The keyboard still works fine and the mouse cursor still moves around.
One time I opened a terminal with keyboard shortcuts and ran "sudo /etc/init.d/hal restart" and it fixed the problem. The next time I tried that it didn't work.

Nelson: I tried to reproduce the bug using your steps, but It did not manifest itself for me.

I attached the Xorg.0.log from the buggy session.
I did add Option "AutoAddDevices" "false" to my xorg.conf "ServerFlags" area, but it didn't seem to help.

Matt Cockayne (matt-cockayne) wrote :

Same problem here for me

I get the problem mainly following a long period of inactivity.

 Has anyone heard of a fix for this other than going to twinview.

Also I am able to duplicate this bug instantly by using VirtualBox. My mouse is fine until I focus on the VM. the moment i try and change focus back I lose my mouse. Not sure if thats relevant in any way to this bug or if its an issue with VirtualBox, or even just an issue with my setup.

Setup
 Intrepid
 AMD 64 3500+
 Nvidia 6200 (PCIE) & Nvidia 6150 (int) Cards
 177 driver
 Xinerama

How much pressure do we need to exert to get the Importance uprated. its not impossible for me to work with it but its really a pain to resolve when it occurs. I think it definitely deserves to be higher than "Undecided"

Seconded on the importance issue. The only way to resolve the problem that I've found so far is to CTRL-ALT-DEL and kill my entire session. Because not all my apps have decent keyboard shortcuts, they can't all be quit cleanly, resulting in lost work.

Regardless of lost work, it's a major waste of time & effort to restart X just to get back to where you are.

On Sat, Nov 22, 2008 at 06:50:16PM -0800, <email address hidden> wrote:
> Anywhere between a few minutes and a few hours, the mouse buttons stop
> responding. The mouse itself keeps moving and remains visible.

> The trigger is when moving the mouse between two xinerama screens.

just a guess, could it be that the button events are delivered to the wrong
screen? If you have a full-screen xev on the other screen when it happens,
does it show the button events.

Good suggestion, but thats not it unfortunately.

Running xev in both screens. Neither reports any events when moving or clicking the mouse buttons onto the xev area.

Bryce Harrington (bryce) on 2008-12-05
Changed in xorg:
status: New → Confirmed
Bryce Harrington (bryce) on 2008-12-05
Changed in xorg:
status: Confirmed → Invalid
Changed in nvidia-graphics-drivers-177:
status: Confirmed → Invalid
mtopro (matt-mtopro) on 2008-12-28
Changed in xorg:
status: Invalid → Confirmed
Changed in xorg:
importance: Undecided → High
125 comments hidden view all 205 comments
Tom Davidson (tomdavidson) wrote :

ditto. Nvidia card, dual displays... the mouse issue. switch to twinview from xinerama and no problems yet. would rather use xinerama.

trouble shooting mouse files (as described here: https://wiki.ubuntu.com/DebuggingMouseDetection) attached should they be helpful...

messinwu (lynn-konz) wrote :

Okay, I don't think we need anymore "Hey, I have this problem too!" posts. This bug has been fixed. You need to upgrade your Xorg Server and associated files. At least that's what I did with my Fedora 10 system. Bug is gone, working perfectly with two Nvidia dual-head cards with 180.22 drivers and four monitors in Xinerama. Thank you to all who have contributed.

Tom Davidson (tomdavidson) wrote :

messinwu: sorry. Im a bit green... I thought one of the big advantages of such a large open source community was the diversity in testing and reporting of the user experience. It took me a few min to gather the info as directed on the wiki page... I didnt do it for my own self satisfaction - I truly thought this type of participation was/could be helpful.

Its not as though all of these "this problem too" posters filed separate bug reports. I think we just wanted to help in any way we can. It was from several of these such post that I found my workaround via twin veiw, otherwise i was going back to 8.04.... Thanks for the help everyone.

What version of Xorg ?
Using UBUNTU, still have bug with latest updates.

messinwu wrote:
> Okay, I don't think we need anymore "Hey, I have this problem too!"
> posts. This bug has been fixed. You need to upgrade your Xorg Server
> and associated files. At least that's what I did with my Fedora 10
> system. Bug is gone, working perfectly with two Nvidia dual-head cards
> with 180.22 drivers and four monitors in Xinerama. Thank you to all who
> have contributed.
>
>

chimaster (spike-queenstown) wrote :

messinwu, I'm still buggin too. Can you please validate your "fixed" with references to versions that you are using include Xorg. Bearing in mind of course that Ubuntu might not be using the same versions / patches / time frames as Fedora.

P.S. Me Too, and this problem sucks. The more the better, if it wasn't for so many me too's then we'd all probably still be saying this is an Nvidia specific issue and not related to Xinerama or Xorg.

messinwu (lynn-konz) wrote :

The latest patch is probably not in the Ubuntu updates yet. You have to patch your Xorg server, as suggested in Post #130 of this thread. Unfortunately, I have Fedora 10 and not Ubuntu, so my upgrade was simpler because they already had .rpm's made for the new Xorg that I installed with yum. If someone else has done this with Ubuntu already, please chime in and help those folks out. I'm guessing you just download the patched source code and compile it and install it as root... ?

messinwu (lynn-konz) wrote :

X -version

X.Org X Server 1.5.3
Release Date: 5 November 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.18-92.1.18.el5 i686
Current Operating System: Linux localhost.localdomain 2.6.27.12-170.2.5.fc10.i686 #1 SMP Wed Jan 21 02:09:37 EST 2009 i686
Build Date: 29 January 2009 08:40:04PM
Build ID: xorg-x11-server 1.5.3-10.fc10
 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.

I got the latest rpm's from the link from post #35 of the following thread:
https://bugzilla.redhat.com/show_bug.cgi?id=473825#c35

If you follow that thread, the specific cause of the problem was identified and fixed with the latest patch. A simple 'yum update' will not do it, I had to download and manually install the 'i386' rpm's from the link above.

Pushed as 9fe9b6e4ef669b192ee349e3290db5d2aeea273c and nominated for 1.6.
Thanks for testing.

Thanks for fixing it Peter

I tested the fix against Ubuntu Intrepid and it works great. System stable, thanks so much Peter!

Bryce Harrington (bryce) wrote :

Can someone extract the fedora patch? Perhaps this is a dupe of 41301, of which a patch was just uploaded to jaunty.

Changed in xorg:
status: Confirmed → Triaged
Changed in xorg-server:
status: Unknown → Fix Committed

Is there any ETA for when this fix is going to get into the normal Ubuntu update channels? Patching/recompiling X isn't really an option for some of us.

Reuben Firmin (reubenf) wrote :

FWIW, I switched to Twinview and (obviously) the problem hasn't reoccurred. I had an aversion to Twinview in the past (based on instability last time I tried it, years ago, I think) but it's stable (and, bonus, gives me full KDE4 bling, which xinerama was somehow blocking.)

dan_linder (dan-linder) wrote :

Unfortunately "TwinView" doesn't work for those of us with three+ monitors ("TripletView" anyone?).

Dan

(Or am I missing something with TwinView to make it work with my two NVidia cards -- GeForce 8600 GT, and older GeForce2 MX/MX 400? I'm using the NVidia driver for the 8600, and the opensource "nv" driver for the 400 IIRC...)

mati (mati-wroc) wrote :

> Unfortunately "TwinView" doesn't work for those of us with three+ monitors ("TripletView" anyone?).
Or just one monitor...

This should classify for a SRU, in my humble opinion.

Bryce Harrington (bryce) wrote :

> Is there any ETA for when this fix is going to get into the normal Ubuntu update channels?

No ETA until there is a patch identified and tested in Jaunty. So if anyone is anxious to see this fixed, you can help by extracting the patch from the fedora package (I poked around but didn't spot it offhand.)

> This should classify for a SRU, in my humble opinion.

If you'd like to see it as an SRU, you can lay the groundwork by updating the description of this bug and fill in the information specified in the procedure https://wiki.ubuntu.com/StableReleaseUpdates . If this is done, and a regression-free patch is identified and validated on Jaunty, I wouldn't be opposed to putting in an SRU on it.

Albert Damen (albrt) wrote :

This seems to be http://bugs.freedesktop.org/show_bug.cgi?id=18668
Both this LP bug and the Redhat bug are referenced in that bug.
Fix was pushed as 9fe9b6e4ef669b192ee349e3290db5d2aeea273c and nominated for 1.6
Steven Harms reports the fix works on Intrepid.

Changed in xorg-server:
status: Fix Committed → Fix Released
m0sia (m0sia) wrote :

I patched xorg-server with patch from http://bugs.freedesktop.org/show_bug.cgi?id=18668

You can find updated xorg packages in my PPA, while ubuntu developers update official package.
https://launchpad.net/~m0sia/+archive/ppa

Gareth Brown (gaz-gbmail) wrote :

After patching xserver with the patch from http://bugs.freedesktop.org/show_bug.cgi?id=18668 we have had no further problems.

We are using TwinView across 3 monitors (2 GPUs). xorg.conf attached.

Changed in xorg-server:
status: Unknown → Fix Released

I can confirm that the patch fixes the bug on my machine. Updated xorg via m0sias PPA - Thanks m0sia.

Also fixes it here at work, Quad Display Nvidia.

On Fri, Feb 27, 2009 at 6:49 AM, Kris Willis <email address hidden>wrote:

> I can confirm that the patch fixes the bug on my machine. Updated xorg
> via m0sias PPA - Thanks m0sia.
>
>

Bryce Harrington (bryce) wrote :

For Jaunty, this fix is confirmed present in the 1.6.0 code currently queued in the ubuntu xserver git tree, which should be uploaded some time this week.

Changed in xorg-server:
status: Triaged → Fix Committed
Bryce Harrington (bryce) on 2009-03-04
description: updated
Bryce Harrington (bryce) on 2009-03-04
description: updated
description: updated
Changed in xorg-server:
importance: Undecided → High
status: New → In Progress
chimaster (spike-queenstown) wrote :

Confirm. Fix works. 3 Screens. System (X) up for 4 days. not a single freeze. Yay. Thanks everyone for your input and to whichever guru made the pain stop. :-)

Bryce Harrington (bryce) wrote :

Uploaded to intrepid-proposed, updated description for an SRU, and subscribed SRU team. After reviewing the patch and based on all of the testing feedback I think this is very appropriate for an SRU so give it my ack.

Changed in xorg-server:
status: In Progress → Fix Committed
Bryce Harrington (bryce) on 2009-03-05
description: updated
Brian Murray (brian-murray) wrote :

I'm closing the Ubuntu task since the bug report is affecting the right package now and doesn't belong in the no package section.

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xorg-server - 2:1.6.0-0ubuntu1

---------------
xorg-server (2:1.6.0-0ubuntu1) jaunty; urgency=low

  [ Bryce Harrington ]
  * New upstream release
    - Fixes segfault during X startup for drivers with RANDR < 1.2
      (LP: #319210)
    - Fixes EDID for monitors that incorrectly report aspect ratio instead
      of resolution (LP: #311485)
    - Fixes issue where X stops responding to mouse clicks after some time
      if using Xinerama. (LP: #296167)
  * Add 162_null_crtc_in_rotation.patch: Fixes crash when two displays on
    separate cards are attached. X doesn't work with multiple cards yet,
    but crashing is not an appropriate way to handle such a situation.
    (LP: #139990)

  [ Timo Aaltonen ]
  * 159_xinerama_focus.patch,
    161_force_paired_kbd_device.patch:
    - Dropped, applied upstream

 -- Bryce Harrington <email address hidden> Fri, 06 Mar 2009 14:44:31 -0800

Changed in xorg-server:
status: Fix Committed → Fix Released
Martin Pitt (pitti) wrote :

Accepted xorg-server into intrepid-proposed; please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

mtopro (matt-mtopro) wrote :

Well the fix works great for me after a reboot. Thanks for all the support everyone!

I will report back if other issues develop, but all seams well. : )

mtopro (matt-mtopro) wrote :

Another comment that may help other GUI users test, you can enable the fix through System>Administration>Synaptic Package Manager. Then go to Settings>Repositories and under the 'Updates' tab check the box under Pre-released updates. Close out of that box and Synaptic, then do a System>Administration>Update Manager. 'Check' for new updates and you will get a list of the active updates. Uncheck all of them except the xorg-server and the xorg-common. After that updates, go back into the Synaptic Package Manager and uncheck the box for Pre-released updates. You're all set. Reboot and you should hopefully have a fix.

Download full text (5.1 KiB)

thank you :)

On Tue, 2009-03-10 at 21:20 +0000, mtopro wrote:
> Another comment that may help other GUI users test, you can enable the
> fix through System>Administration>Synaptic Package Manager. Then go to
> Settings>Repositories and under the 'Updates' tab check the box under
> Pre-released updates. Close out of that box and Synaptic, then do a
> System>Administration>Update Manager. 'Check' for new updates and you
> will get a list of the active updates. Uncheck all of them except the
> xorg-server and the xorg-common. After that updates, go back into the
> Synaptic Package Manager and uncheck the box for Pre-released updates.
> You're all set. Reboot and you should hopefully have a fix.
>
> --
> X.org will stop responding to mouse clicks on Ibex with Xinerama. Occurs frequently, Fatal Error.
> https://bugs.launchpad.net/bugs/296167
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in X.Org X server: Fix Released
> Status in Ubuntu: Invalid
> Status in “xorg-server” source package in Ubuntu: Fix Released
> Status in The Intrepid Ibex: Invalid
> Status in xorg-server in Ubuntu Intrepid: Fix Committed
> Status in “xorg-server” source package in Fedora: Fix Released
>
> Bug description:
> [Problem]
> When using Xinerama (such as with multiple video cards), if using an animated cursor, after some time X will stop responding to mouse events. All mouse events are being sent to the root window instead of client applications.
>
> [SRU]
> Confirmed fix is released upstream in xserver 1.6.0 and present in Jaunty (as of xserver 1.6.0)
>
> Impact: Severe regression for users of -nvidia and other drivers which still rely on Xinerama, resulting in mouse cursor (and thus much of the GUI) becoming unusable. No reliable workaround known.
>
> Fix: Avoid calling UpdateSpriteForScreen() if the Xinerama extension is loaded
>
> Patch: https://bugs.freedesktop.org/attachment.cgi?id=22373
>
> Test Case: Configure a Xinerama multi-head (3+) layout using -nvidia. Configure the mouse to use an animated cursor; this is optional but makes it easier to reproduce the problem. Move windows around, from one screen to another until the bug is triggered (may take a few tries). Mouse clicking will become disabled, while keyboard and mouse movement continues to work correctly.
>
> Regression Potential: The fix is extremely trivial and highly tied to Xinerama. The net effect is to prevent code from being executed rather than enable it. For non-Xinerama users, there is no chance for regression. For Xinerama users, give the huge number that have reported this as an issue, this bug probably affects all users; furthermore we already have numerous confirmations of the fix and zero reports of side effects. So I think the chance of regression is close to nil.
>
> [Original Report]
> After upgrading to Ibex a problem has appeared where after some activity (10-15 minutes), X will suddenly stop responding to any mouse events - the cursor is still there and will move around, but windows won't change focus and clicking the mouse buttons have no effect (in both the focused and unfocused windows). Key...

Read more...

mati (mati-wroc) wrote :

Be also sure to use the main repositories. I used the the ones in my country, but they still didn't contain the update.

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xorg-server - 2:1.5.2-2ubuntu3.1

---------------
xorg-server (2:1.5.2-2ubuntu3.1) intrepid-proposed; urgency=low

  * 163_no_updatespriteforscreen_if_xinerama.patch: Fixes issue where
    mouse stops responding if using Xinerama.
    (LP: #296167)

 -- Bryce Harrington <email address hidden> Tue, 03 Mar 2009 17:49:38 -0800

Changed in xorg-server:
status: Fix Committed → Fix Released
BlackenedSky (caffeine-lord) wrote :

I have reason to believe this issue has worked its way back in for Jaunty: see bug #374417

Agreeing with BlackenedSky - I'm seeing this as well in Jaunty (desktop upgraded from 8.10 to 9.04). Same workaround as described above (dragging window across screen border & back) works, suggesting the bug has resurfaced.

Philipp Sprunger (pspr) wrote :

I have this problem in 9.04 Jaunty and also in Karmic 9.10...

Roy Jamison (xteejx) wrote :

@Philipp Spunger: In Karmic can you run "apport-collect -p xorg 296167" without quotes and let it grab all the information for the report. Then we can reset this to confirmed. Thank you.

Changed in xorg-server (Ubuntu):
status: Fix Released → Confirmed
status: Confirmed → Incomplete
Bryce Harrington (bryce) wrote :

Report new issues with these symptoms as new bugs please. Use 'ubuntu-bug xorg'. This bug report is for an issue believed fixed and in any case is stale with too many comments.

Changed in xorg-server (Ubuntu):
status: Incomplete → Fix Released
Roy Jamison (xteejx) wrote :

Sorry about that Bryce, but thanks for a push in the right direction :)

*** Bug 20389 has been marked as a duplicate of this bug. ***

Changed in xorg-server:
importance: Unknown → Critical
Changed in xorg-server:
importance: Critical → Unknown
Changed in xorg-server:
importance: Unknown → Critical

LinkedIn
------------

Bug,

I'd like to add you to my professional network on LinkedIn.

- Michael

Michael Joyner
Programmer at NewsRx
Greater Atlanta Area

Confirm that you know Michael Joyner:
https://www.linkedin.com/e/-7mly8z-hr9ijsis-6i/isd/19867556319/ccrPNB5w/?hs=false&tok=3wLo7WFrY1US41

--
You are receiving Invitation to Connect emails. Click to unsubscribe:
http://www.linkedin.com/e/-7mly8z-hr9ijsis-6i/k3UsWeJkUvaCotwfHZFfSUMk1qzhI-F_m9bD6Iu/goo/296167%40bugs%2Elaunchpad%2Enet/20061/I6410444033_1/?hs=false&tok=2c-5GA1PY1US41

(c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.

Displaying first 40 and last 40 comments. View all 205 comments or add a comment.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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