PS/2 Logitech MX310 clicks stop working sporadically

This happens to me on my Acer Travelmate Laptop. Any info on how to provide debug info would be welcome.

I use the Alt-Tab to re-enable mouse clicks. This problem usually happens when I am in gedit, and open the :"Save file as" dialog. I cannot click "Cancel or "Save". The cursor momentarily changes to a "+" sign when I click the buttons.

discussion from IRC some time ago:

"<ploum> For a few weeks, I experience a random mouse-click freeze in dapper
<ploum> The click is not responding on my mouse anymore
<ploum> and the workaround is to type a shortcut key (for exemple switch desktop key) and that's all
<seb128> check the mouse cable? :)
...
<seb128> do you have the click event to xev when that happens?
...
<ploum> seb128: it's very difficult because it must happen with a xev already openend ! (as the keystroke solve the problem)
<seb128> ploum: run an xev on every desktop until that happens next time :p
...
<ploum> seb128: YEAH ! I was able to reproduce my bug with xev !
<ploum> (alt+F2 doesn't deblock my mouse)
<ploum> and no xev event for the mouse click"

in case somebody was tempted to reassign it to GTK :p

Even better.. if xev reports no data from the kernel.. guess who is at fault?

Fabio > not sure anymore that xev doesn't report anything. It's just that xev has not the focus and there's no way it can have it. So it won't report anything.

And if it was the kernel, why will a given shortcut re-enable the mouse ?

I am having the same problem. It usually occurs when my T41 wakes up from suspend to ram and network manager connects to my wireless network. When it shows the signal strength icon in the taskbar, the mouse is useless. All I managed to do is Ctrl-Alt-Backspace. I'll have to try to switch the desktop instead, next time it happens. This problem occurs intermittently.

Maybe it is a problem with Network Manager?

I'm using v0.5.1 together with gnome and I get this problem sometimes.

Just after I have typed my password and I see the signal strenght mouse clicks have no effect.

Today I tried to logout using killall x-session-manager. I then logged into Enlightenment DR17 (alpha) and mouse clicks worked with no problems what so ever.

This really sounds like an xorg focus issue.

After the latest kernel update (to version 2.6.15-26.47) this issue seems to have disappeared. Is anybody else still having this problem?

I am using -27 and I got this issue today.

So it is still not fixed.

I'm having same kind of problem where mouse clicks are not responding. Only way is to switch workspaces, but that doesn't always help.

Best solution so far has been right clicking on the zone where the mouse was when it stopped responding. This problem is more frequent all the time

I've been able to reproduce this bug on a whole fresh edgy on another computer (a laptop HP Compaq nc6120). I had it several times this week.

So it's not related to the hardware (happens with the touchpad as well), not with the graphic driver (nvidia on my desktop, intel on the laptop).

It's still not fixed with Feisty Beta amd64. I first experienced it with the Herd 5 live CD. When the Beta came out I installed with the Alternate CD, but it still happened. Then I downloaded the Beta live CD and it still happens. My keyboard continues to work and, as others have noted, switching desktops resolves the problem for a while. I tried Ctrl-Alt-Bkspc, but that hung the computer.

The computer has an Abit NF-M2S motherboard with AMD-64/2 at 4600 and the mouse and keyboard are a Logitech Cordless Desktop EX110 (combo mouse and keyboard).

I can also add some additional experience. This is a brand new box I put together for myself, so I have been trying various 64-bit distros. I have the same exact problem with OpenSUSE 10.2, Fedora Core 6, Simply Mepis 6.5 rc2 and Mandriva-free-20007 (all 64-bit versions). But I did not have the problem with Gentoo 2006.1. I noted that Gentoo used KDE and also used Vesa, where the others used the nv drivers for the onboard nVidia GeForce 6100.

At this point the computer is running Fedora 7 test2, using the nv driver and Gnome 2.18.0, and kernel 2.6.20-1. The problem has completely disappeared. So if y'all want to find out what fixed it, look at what is different between Feisty Beta amd64 and Fedora 7 test2 amd64.

I had this issue on Dapper and still have it on Edgy with my Dell D600 laptop. I can get the mouse back by Ctrl-Alt F1 and then Alt F7 to get back to X. It sure is annoying!

I have a dell laptop with ati rage mobility P/M agp2x. The mouse freeze few seconds each time I open a window. It hapen to me now with edgy and happened wih 5.10 release. I am not sure if xorg is the cause. Ati rage have problems with new xorg drivers. I've heard that wih xfree86 work fine but it can not be instaled in the new kernels. Since a long time I want migrate to ubuntu (I use mandriva2006 because is the only distro that works in my machine) and the only problem I have is this.

Same problem here (edgy, feisty)
Ctrl Alt F1 -> Ctrl Alt F7 makes mouse buttons to work with the current window (1 time).
Very annoying.
The only solution I found is rebooting the system to get it working for a while.
Can't test xev, since I can't focus the window. The window behind xev test window won't lose the focus. (Alt tab not helping)

Bug Importance rated medium??
I'd rate it critical.

On Sun, 22 Apr 2007 16:14:32 -0000
Héctor <email address hidden> dijo:

> Same problem here (edgy, feisty)
> Ctrl Alt F1 -> Ctrl Alt F7 makes mouse buttons to work with the current window (1 time).
> Very annoying.
> The only solution I found is rebooting the system to get it working for a while.
> Can't test xev, since I can't focus the window. The window behind xev test window won't lose the focus. (Alt tab not helping)
>
>
> Bug Importance rated medium??
> I'd rate it critical.

First, it's rated medium because it doesn't affect very many of us. Another reason it's not rated higher is because there is a workaround. The workaround is to edit the /boot/grub/menu.lst file. Add "noapic acpi=off" to the end of the root line. You can do this while booting just by hitting e when the boot menu appears. Then select the root line and hit e again. Go to the end of the line and add the command. Hit return to save the edit and then b to continue the boot process.

Editing it during boot makes the command happen on booting, but only for that session. If it solves the problem you can add it to the end of the line by editing the /boot/grub/menu.lst file. From a command line enter "sudo gedit /boot/grub/menu.lst." When Gedit comes up add the command to the end of the line and save the file. Now it will be permanent.

First, it's rated medium because it doesn't affect very many of us. Another reason it's not rated higher is because there is a workaround. The workaround is to edit the /boot/grub/menu.lst file. Add "noapic acpi=off" to the end of the root line. You can do this while booting just by hitting e when the boot menu appears. Then select the root line and hit e again. Go to the end of the line and add the command. Hit return to save the edit and then b to continue the boot process.

Editing it during boot makes the command happen on booting, but only for that session. If it solves the problem you can add it to the end of the line by editing the /boot/grub/menu.lst file. From a command line enter "sudo gedit /boot/grub/menu.lst." When Gedit comes up add the command to the end of the line and save the file. Now it will be permanent.

The above fix worked for me on Fedora 7, Debian Etch and Ubuntu Feisty, all 64-bit. I have since discarded the others and now use just Ubuntu Feisty amd64.

Hi John,

It looks like those kernel arguments may make it so my laptop won't
sleep, and maybe some other side effects. Is that true?

Thanks,

Rob

On Sun, 2007-04-22 at 16:41 +0000, John Jason Jordan wrote:
> First, it's rated medium because it doesn't affect very many of us.
> Another reason it's not rated higher is because there is a workaround.
> The workaround is to edit the /boot/grub/menu.lst file. Add "noapic
> acpi=off" to the end of the root line. You can do this while booting
> just by hitting e when the boot menu appears. Then select the root line
> and hit e again. Go to the end of the line and add the command. Hit
> return to save the edit and then b to continue the boot process.
>
> Editing it during boot makes the command happen on booting, but only for
> that session. If it solves the problem you can add it to the end of the
> line by editing the /boot/grub/menu.lst file. From a command line enter
> "sudo gedit /boot/grub/menu.lst." When Gedit comes up add the command to
> the end of the line and save the file. Now it will be permanent.
>
> The above fix worked for me on Fedora 7, Debian Etch and Ubuntu Feisty,
> all 64-bit. I have since discarded the others and now use just Ubuntu
> Feisty amd64.
>
--
Rob Frohne, Ph.D., P.E.
E.F. Cross School of Engineering
Walla Walla College
100 SW 4th Street
College Place, WA 99324
(509) 527-2075
http://www.wwc.edu/~frohro/

Rob Frohne said:

I>t looks like those kernel arguments may make it so my laptop won't
>sleep, and maybe some other side effects. Is that true?

I don't know. I had the problem only on a brand new desktop computer I built for myself over spring break. I tried (all amd64 versions) CentOS, Mepis, Mandriva, OpenSUSE, Fedora 7 test2, Ubuntu Feisty Beta, and Debian Etch (final). Every single one of them displayed the same problem. Sometimes I could fix it by holding the cursor over a window and doing Alt-Tab, sometimes I had to log off and back in again. Eventually I discovered the "noapic pci=off" command and that solved it for all of them. The computer is currently running Ubuntu Feisty final and I still had to go in and add the command.

The computer has an Abit NF-M2S motherboard that has onboard nVidia chipset for everything except the gigabit ethernet which is Realtek. The video is nVidia GeForce 6100 and the rest is nforce 405. But who know which part is the culprit? All I can say is try it on your laptop and see what happens.

I tried that boot option "noapic acpi=off"
It seems to solve the problem, but now I can only switch windows by clicking on their titlebars.
At least I can use my mouse btw.

Same problem here. In addition to this I have problems where my gnome locks-up while dragging something. The mouse icon is then stuck like that and won't do anything until I switch to a virtual console and kill nautilus.
On my own computer I have this in my kernel messages:
[ 0.000000] Nvidia board detected. Ignoring ACPI timer override.
[ 0.000000] If you got timer trouble try acpi_use_timer_override

When I use that, it seems to fix this problem but it causes my wine games to crash randomly. Good trade off.

Bug is gone for me, no buggy focus/mouse anymore.
It seems the last kernel update solved the problem.
No boot options required.

Closing this bug since it has stopped recurring for both me and Héctor, who left us a comment saying as much.
If this is still an issue for the rest of those subscribed to the bug, please reopen the bug.

Thank you.

Still happening for me in Feisty 64.
Linux cappy-chan 2.6.20-16-generic #2 SMP Thu Jun 7 19:00:28 UTC 2007 x86_64 GNU/Linux

Problem is gone! I don't know why it took longer for mine to be fixed - maybe they were a little bit slower on the 64-bit kernel. It's been fixed at least a week for me.

Also, my much worse freezing problem also went away: https://bugs.launchpad.net/ubuntu/+bug/114365

Hurrah! Thank you so much ^^

Re my comment of April 23:
.....................
I don't know. I had the problem only on a brand new desktop computer I built for myself over spring break. I tried (all amd64 versions) CentOS, Mepis, Mandriva, OpenSUSE, Fedora 7 test2, Ubuntu Feisty Beta, and Debian Etch (final). Every single one of them displayed the same problem. Sometimes I could fix it by holding the cursor over a window and doing Alt-Tab, sometimes I had to log off and back in again. Eventually I discovered the "noapic pci=off" command and that solved it for all of them. The computer is currently running Ubuntu Feisty final and I still had to go in and add the command.

The computer has an Abit NF-M2S motherboard that has onboard nVidia chipset for everything except the gigabit ethernet which is Realtek. The video is nVidia GeForce 6100 and the rest is nforce 405. But who know which part is the culprit? All I can say is try it on your laptop and see what happens.
.......................

The problem disappeared for me, and without needing the "noapic pci=off" boot option. What made it disappear was returning the Abit NF-M2S motherboard and replacing it with an Asus M2NPV-VM motherboard. The Asus cost me about $12 more, but it has four SATA connectors, nVidia nforce 430, nVidia GeForce 6150, an eSATA connector, built-in firewire, and the gigabit ethernet is also nVidia. The added features are well worth the extra price, and it also solved all the problems I had been having with the SATA controller on the Abit board. Conclusions: 1) Abit is evil and, 2) if you have the option to swap motherboards, it's probably worth the time and effort to do so, compared to the effort you're spending on dealing with this bug.

This is currently happening for me on Intrepid Ibex.
I am using the "noapci apci=off" option.

Kernel version 2.6.27

Thanks

Kal

the no kernel option does not work for me.
the alt tab does not work for me, I have a dual monitor, with TwinView and monitor rotation.

I will try crtl - alt f1 -> alt f7 next time it happens.

What is the last good kernel known to have fixed this problem?

I haven't tried the "noapci apci=off" option yet, but I turned on the "ctrl shows me where my pointer is" option and even though the pointer was moving about the screen, X thought it was in the top left-most corner.

Same here, kernel 2.6.27.7 , tried the noapic acpi=off option but with no luck. The system will stop responding to mouse clicks randomly while working.
I can't reproduce the random freezing but mouse clicks always go away after returning from the idle state.

Same kernel too. Tried with the noapic acpi=off, rebooted last night, came in this morning and the mouse was no longer working (and by this I mean pointer moves around screen, but no mouse clicks work and focus follows pointer wasn't).

My problem appears to be related to my dual monitor.

Or at least I have never seen it when I was not using the dual monitor, and generally see it at least once during the course of a day when I am using the dual monitor.

My monitor is using Twin View, with Monitor Rotation.

crtl - alt f1 -> alt f7 does not work.
But killing the Xserver does work.

This problem started when I upgraded to intrepid ibex

I have started seeing this problem since upgrading from Hardy to Ibex. The cursor moves around on screen, but clicks are not recognized and the focus does not follow the cursor as it should. It happens several times a day for me. Switching to a text console does not help; only killing the X server fixes it.

I am also using a dual monitor setup with Xinerama, and one screen rotated 90 degrees. (Can't use Twinview because it won't let you rotate only one of two screens). I have an NVidia Quadro FX 3500. I had the same hardware with Hardy, but it didn't have this problem.

I never had this problem until upgrading to 8.10, and SO FAR, it has only happened when I have dual monitors running. When I run dual monitors, I'm running Xinerama. When I go with both, it's happening a few times per day. When go with just the lappy screen, it has not occurred yet.

One other difference, when I use only one monitor, I don't have any mouse attached - only the touchpad.

Only resetting X server fixes it, that I can find.

I'm running the same hardware that I had with Hardy, and I now have this problem with Ibex.

My GPU is an nVidia 8800GTS, I'm running two 4:3 monitors in 'separate X screen' mode with the Xinerama extension.

I'm not sure if it helps, but I see <"Xlib: extension "RANDR" missing on display ":0.0".> a lot whenever I run GUI programs from the command line...

I have also been experiencing this problem since moving to Intrepid, but not at first. I noticed it first one or two weeks ago, but it is now a daily occurrence. Alt-Tab does not fix it. Only Ctrl-Alt-Backspace restores the mouse click.

I am running 32-bit Intrepid on a Dell Latitude D820 notebook computer and have only noticed the problem when I am connected to a docking station and using Xinerama. I also see the RANDR error message that Tris pointed out.

It looks like it might just be Xinerama, when I disable xinerama, I no long see this behavior.

I cant actually figure out how to use the other monitor though.

I can see the mouse, but when I right/left click nothing happens.
I cant actually figure out how to start an application on that screen or move anything over.

There is no KDE toolbar at the bottom either.

Is there some setup config that I am missing?

Sorry, I am not using twin view.
I am using the "Seperate X Screen" option, because I use monitor rotation.

Reopening.

I can confirm this is happening again. The only app I can think which would be doing that is flash - I had at least one page with flash open every time in firefox when it happened (and it happened a good dozen of times), and I see other reporters using opera/epiphany at the time it happens.

Switching tty does not fix it.
Switching desktop does not fix it.
Restarting X seems to be the only way to fix it, although suggestions would be good on something less "annoying".

Keyboard input is still perfectly fine.
Mouse pointer still follows in X - the cursor is there and moving, sometimes changing when hovering a text area and so on. In an application replacing the cursor (tested with a few games under Wine), the cursor will be present where it died in the application and never move - the X cursor will be duplicate and not replaced when hovering the app.
Keyboard input works perfectly.

Dual monitor 1680x1050, nVidia 9800GTX+ proprietary 180.11 drivers. Xinerama enabled.
Xlib: extension "RANDR" missing on display ":0.0". also appears when starting GUI apps, although I don't think that's related.

A second usb mouse is connected, and behaves exactly like the first one.

Attaching Xorg.0.log

Ever since I disconnected my second monitor, I have not encountered this problem - not even once. (And since suspend to RAM doesn't work when I have that monitor connected, I've just dumped the second monitor altogether. Sigh. But at least my mouse and suspend work.)

This is the same for me; this bug ONLY turn on when my second screen is plug on my computer.

I'm having exactly same problem. Once in a while mouse buttons stop working, the pointer moves and keyboard still works. I'm also having dual-screen configuration with Xinerama and two Radeon graphics cards.

I also noted another bug with might be related. I use synergy to share my keyboard and mouse with a laptop which has also Ubuntu 8.10 as does the synergy-server (with those two screens on xinerama). When I move my mouse to the laptop and move it back to the synergy server screen the mouse buttons won't work anymore, exactly like described above. And there is two options to get the buttons to work: a) restart X with ctrl+alt+backspace b) kill the synergy-client on laptop. What's the most curious is that even if the mouse buttons stop working randomly without synergy even running the option b helps (of course you have to start synergy and move mouse to the laptop's screen in that case).

I tried doing some googling to figure out a way to trouble shoot this bug. I'd like to figure out where the problem is..i.e. X, the kernel, or something else. This bug is very annoying and in my case prevents me from running virtual machines.

Anyone have any ideas of how we can go about trouble shooting this problem?

The problem is almost certainly to do with Xinerama. I changed my dual monitor setup from Xinerama to MergedFB and the problem has completely gone away.

I do not use Xinerama nor do I use multiple displays and I have the
issue. It may be a bit more complex than that.

On Mon, Jan 5, 2009 at 1:40 AM, Gavin van Lelyveld
<email address hidden> wrote:
> The problem is almost certainly to do with Xinerama. I changed my dual
> monitor setup from Xinerama to MergedFB and the problem has completely
> gone away.
>
> --
> Mouse clicks stop working sporadically
> https://bugs.launchpad.net/bugs/41301
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

If it helps, here is the behavior I am seeing:

1. Problem is sporadic. Sometimes it happens frequently (and is extremely annoying), other times it happens rarely.

2. When it happens, it appears that some X window (I say "some" to mean "any" as far as I can tell) that has just interacted with the mouse (and perhaps performed some kind of a grab) doesn't release the grab. In other words, if I right-click on some other screen location that is above a different widget, and the last thing to have grabbed the mouse has a context menu, I'll get the context menu for that last item instead of the mouse events being passed to the item I'm trying to click.

3. Sometimes, furiously left and right clicking, Alt+Tabbing, etc. appears to clear the error. Other times, I have to hunt down the widget that has the cursor and click it with alternating buttons to try and reset the mouse grab state.

It's been years since I've done anything with Xlib, but if I had the time to try and find this bug, I'd start looking for reasons why random grabs aren't being released.

Just another confirmation, I have the problem too and have been reporting it elsewhere for over 2 months. It's caused by Xinerama, turn off Xinerama and you can run multi-screen setups fine for months with no lockup. Turn it on and you're pushed to survive more than a few hours.

Note; switch user - which appears to restart X, does not fix the problem (!)

Hi All, It seems that I have the same problem, it just started recently and im actually quite stumped as in why it just started.

I tried doing ctrl alt backspace but that just makes things worse, nothing works after that and i get a total system freeze.

I tried also doing alt f7 and that doesnt work either - i dont get into the tty i just see a frozen screen. Only solution for me is do a shutdown -r now in a terminal.

here is something i found in my logs, it looks like it may be trying to reconfigure the mouse. Sorry im not 100% sure as im new to linux and my interpretation may be wrong.

p.s i also tried sudo /etc/init.d/gdm restart when the mouse freezes, this also causes gnome to quit but leaves me sitting there with my background.

Thanks in advance for your time and patience.

Hopefully this will be of benefit to the thread - I had this behavior occur once yesterday and twice today and I seem to have found a way to reproduce it.

My environment info:

Intrepid (8.10), 2.6.27-9, SMP, x86_64
VMWare Server 1.0.8 (build 126538)
Logitech LX7 mouse using 'Driver "mouse"' in my X config
Nvidia drivers - 177.82
Two displays, using TwinView with Xinerama

Steps to reproduce:

From my Ubuntu host, I fire up a Windows 2000 guest virtual machine in VMWare. I have the VMWare Console program running, maximized, on my left display. With my mouse focus inside the Windows VM, I click and drag my mouse (to, say, highlight some text or whatever) within the VM but I drag all the way to the right edge of the VM's screen, such that if my mouse wasn't focused within the VM, the cursor would move onto the right display. Then, let go of the mouse button (which has being held down during the drag / text-selection.)

After doing this, I can move my mouse around but the mouse won't move beyond the boundaries of the VMWare Console window. Now I can hit ctrl-alt to release the cursor from the VM (to return it back to the host) and I can ctrl-tab to another window. Once I do this, I can finally move the cursor to the right display, but mouse clicks (left, right, middle) all go unrecognized, including if I have xev running, bring it to the foreground, position the cursor over it and try clicking.

After all this, as is mentioned above, restarting X with ctrl-alt-delete seems to be the only way to restore clicking capabilities.

Today I encountered this yet again, and in the middle of closing down everything prior to yet another ctrl-alt-delete to restart X I decided to see restarting my window manager would make any difference.

The good news (relatively good, anyway) is that it did. I fired up a terminal and did:
 metacity --replace

and my mouse was back in the business of clicking on things.

I'd still consider this bug quite serious and in need of a proper fix, but at least I now have a less painful workaround than a full out restart of X every time it occurs. Hopefully this helps others suffering from this as well.

krouskop wrote:
> The good news (relatively good, anyway) is that it did. I fired up a terminal and did:
> metacity --replace

That has never worked for me.
 --Justin

This problem just occurred for me and metacity --replace did not fix anything

This is the most aggravating bug I have ever experienced, I have to restart X almost three times a day - can somebody please figure out what's wrong???!?!

In my case switching user makes the mouse work click again.
(Ctrl-Alt-Del, switch user)

On Wed, Jan 14, 2009 at 9:55 AM, Henri Cook
<email address hidden> wrote:
> This problem just occurred for me and metacity --replace did not fix
> anything
>
> This is the most aggravating bug I have ever experienced, I have to
> restart X almost three times a day - can somebody please figure out
> what's wrong???!?!
>
> --
> Mouse clicks stop working sporadically
> https://bugs.launchpad.net/bugs/41301
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

Yesterday "metacity --replace" did in fact restore my mouse's clicking capability. Today the bug happened again for me though, and "metacity --replace" didn't help anything - I still had to restart X to get my mouse clicking back.

Seeing some users saying that Switch User fixes mouse clicking for them, if I go through the steps I earlier identified (https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/41301/comments/52) to repro this bug, and get into a no-mouse-click state, and then do [Ctrl-Alt-Del -> Switch User] I get the following behavior:

1. On the user login screen that comes up, my mouse can click just fine. (I can click the "Options" pop up menu, for instance.)
2. But, when I immediately log back in as "myself" (the user for which I was logged in as before doing switch user), once I log back in, mouse clicks do NOT work again.

I'll also echo Henri Cook's feeling that this is probably the most aggravating bug I too have ever experienced.

The switch between desktops did not fix this bug for me today unfortunately. Which is really odd. I'm on a three screen nvidia/xinerama setup. When the error occurs the pointer disappears when travelling over the left half of my centre screen, but is visible everywhere else outside this (I can move 'through' this area) - it's like something's been reset.

This problem still makes me have to restart on a daily basis, if not more regularly than that and I desperately need a solution

Same here with Henri. Three monitor setup with nvidia/xinerama.
Metacity --replace doesn't work and switching users doesn't work also. (clicking works If I login with a different user but when I come back clicks are gone).

Logging out or restarting X is the only solution to get my clicks back.
It's the most irritating bug i've ever encountered.

I'm having this same problem too. I have a two monitor setup with nvidia/xinerama.

Resetting X11 seems to work for me also. It usually happens when I'm in VirtualBox & it's focused in a window & I happen to click outside of the screen.

This is my x11 log file.

Hopefully someone will fix this bug. I can say with certainty that I cannot continue to use Ubuntu if this bug is not fixed.

I also tried the metacity thing & I added the noacpi line to my menu.lst file. Still no cookie.

Same happened here. I've used krouskop workarround to 'solve' but restart X isn't a solution.

By far the worst bug I ever seen.

Same here. This is happening since I set up dual screen in xinerama to run windows xp on a virtual box.
The bug is just a massive pain.

I reinstalled Hardy a week ago and I haven't seen this bug since then.

The problem started happening when I set up a dual screen in xinerama.
I have a nvidia GeForce 8400mG chipset. I was using the proprietary nvidia drivers version 177. I installed the version 180.11 and since then I haven't encountered the problem again.
So the new version of the nvidia drivers seems to have fixed the problem.

sorry it actually happened again......
so updating the drivers dont fix the problem.

I also have this problem on my 8.04 64 bit system, I have tried downgrading all xorg stuff to the base versions but it didn't help. Nor did upgrading my NVidia drivers to the latest available version.

I noticed this appear sometime around December 2008, so I imagine some update back then was the source as I did not recall it before that period.

If - as a previous poster has said - reinstalling Hardy fixes it, I can only assume that some configuration somewhere was changed by an update that has now being fixed/deleted, but the update changes were never rolled back (but all the current updates are ok).

Still happening here. Only way I can fix it is to Ctrl + Alt + Backspace. Happens about 3-4 times a day.

openSUSE 11.1 x86_64
Mac Pro Tower with 2 video cards / 3 monitors on Xinerama
Logitech MX1000
VirtualBox 2.0.6

I found bug 18668 in the bugs.freedesktop.org bugzilla that might be
related to this. http://bugs.freedesktop.org/show_bug.cgi?id=18668

There’s an interesting workaround in comment #9
(http://bugs.freedesktop.org/show_bug.cgi?id=18668#c9) that can be
used to both cause the bug *and* work around it:

    alt-tab to a window (firefox is the one i usually use)
    alt-space to bring up the window options menu (metacity)
    select move (this binds the cursor to the center of the window)
    use the arrow keys to move the window to another X session window
    move the mouse
    the bug should now be gone

(You can cause the bug by selecting move, then moving across a
xinerama boundary.)
 —Justin

Thank the Linux gods, I can move my mouse again!

I can confirm this issue, and the solution posted above. (I can duplicate the bug that way as well.)

Intrepid 6.10 running kernel 2.6.27-9-server.
nVidia 8400gs / Proprietary binary blob 177.82.
Dual monitors, separate X screens, one rotated, Xinerama.

I can reproduce and work around the bug with the sequence described above.

I found another way to reproduce it: With synergy running on my box , whenever I move the mouse cursor away clicks are gone.

At least I don't have to restart X all the time.

I have done a fresh Ubuntu 8.04 64bit install and managed to trigger off the problem in it, I have subsequently done another fresh install which does not yet have the problem.

In file comparisons between the "ok" install and the bad one I haven't found too much that is obvious, but I would like to ask those with this bug if they have the following in their /etc/modules file:

lp
rtc
sbp2

My "ok" system does not have them, but my bad system does.

I have the lp and sbp2 lines in my /etc/modules file.

My /etc/modules has

fuse
lp
rtc

The bug can be reproduced here when I change the focus between vbox and host. If I grab the mouse like 4 times is a row the bug is triggrered.

I can confirm this on Ubuntu 8.10 x86_64 running 2.6.27-11 also.

Using Xinerama and synergy, and focus follows mouse.

This should fix this

This is the debdiff for Jaunty

Patch committed to xorg-server git tree for Jaunty, thanks for chasing this down Steven.

How do I apply this patch for Inteprid ? Should I have to download xorg-server deb, patch and reinstall the package?

This bug was fixed in the package xorg-server - 2:1.5.99.902-0ubuntu2

---------------
xorg-server (2:1.5.99.902-0ubuntu2) jaunty; urgency=low

  [Bryce Harrington]
  * Add 157_check_null_modes.patch: Catch null pointer dereference in
    video mode selection, which can cause xserver crash when using SDL
    applications with qemu/kvm.
    (LP: #300310)
  * Add 158_raise_maxclients.patch to raise max number of clients from 256
    to 512. Trade-off is that this reduces client resources available to
    1,048,576 total resources (which should still be ample).
    (LP: #260138)

  [Steven Harms]
  * 159_xinerama_focus.patch: Resolves xinerama focus issues
    with multiple screens
    (LP: #41301)

 -- Bryce Harrington <email address hidden> Wed, 04 Feb 2009 22:33:28 -0800

I echo Rodolfo's question: How do I apply this patch for Intrepid?
More importantly, what needs to happen to make an SRU (Stable Release Update) request for this bug to be fixed on older Ubuntu releases?
Until then, I guess I'll try Justin's suggestion:
http://bugs.freedesktop.org/show_bug.cgi?id=18668#c9
<quote from Mark>
To "reset" the bug without rebooting the x server you can do the following:

alt-tab to a window (firefox is the one i usually use)
alt-space to bring up the window options menu (metacity)
select move (this binds the cursor to the center of the window)
use the arrow keys to move the window to another X session window
move the mouse
the bug should now be gone
</quote>

... 'cuz "metacity --replace" doesn't fix anything for me.

If we can find someone to help with the SRU, the first debdiff I provided will apply to the current intrepid package. If you don't want to wait, I have AMD64 packages at http://www.sharms.org/ubuntu/intrepid

I still have this problem, but as far as I am aware I am not using Xinerama.

At least, there is no mention of Xinerama in my xorg.conf. Does this mean I
am not using Xinerama, or is it possible I am using it without realising it?

Is it possible there are causes of this problem other than Xinerama?

I don't use Xinerama and also have experienced the problem, so it seems to be a Nvidia issue (at least, many posts I've seen seem to have Nvidia hardware) that is triggered off by more than just Xinerama.

I have Intel hardware and do not use Xinerama. Yet I experience this
or I should explain: I experience it occasionally when I logout/lock
my screen or switch user...

On Thu, Feb 12, 2009 at 7:57 PM, David Clayton <email address hidden> wrote:
> I don't use Xinerama and also have experienced the problem, so it seems
> to be a Nvidia issue (at least, many posts I've seen seem to have
> Nvidia hardware) that is triggered off by more than just Xinerama.
>
> --
> Mouse clicks stop working sporadically
> https://bugs.launchpad.net/bugs/41301
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

Nick2000 wrote:
> I have Intel hardware and do not use Xinerama. Yet I experience this
> or I should explain: I experience it occasionally when I logout/lock
> my screen or switch user...

That's a known problem with grabs and gnome-screensaver. You should search for
bugs against your screensaver and report them there.
 --Justin

The patch I added specifically addresses Xinerama -- if your not using Xinerama you need to find a different bug report as this issue is not the same one.

The 64bit DEB's linked above (http://www.sharms.org/ubuntu/intrepid/) worked for me.

Thanks for fixing it - well done.

After applying the debdiff and restarting X, GL screensavers no longer work, they produce the following error (I tested this with glmatrix and glplanet):

glWhateverScreensaver: couldn't create GL context for visual 0x3e
xscreensaver: glWhateverScreensaver exited abnormally (code1)

I downloaded xscreensaver source and installed it that way, but still the same error. Can anyone else reproduce this problem? Any ideas? Thanks.

Reinstalling Nvidia binary drivers, fixes the screensaver issue.

I' ve just had a very similar problem with two Compaq nc 8430 laptops -- one had some fan problems so I' ve transferred the disk to other to continue working. I use Ubuntu 8.04. On the new laptop (same as the old one) I had several times this problem -- the mouse pointer moves, either with the touchpad or with a external USB mouse (tried two different ones), but sometimes clicking on the mouse or trackpad did nothing, as described by others in this thread. Frantic alt-tab or changing the active desktop sometimes worked, sometimes not.

I removed /etc/X11/xorg.conf in hopes the system would recreate it, and suddenly everything came back to normal (except I still don't have a /etc/X11/xorg.conf).

I have no idea how or why it worked, but it is working right now. Any clues?

I have the same problem I get constant messages in /var/log/messages

Aug 11 07:47:25 cryptonite kernel: [56108.792815] psmouse.c: bad data from KBC - timeout
Aug 11 07:51:51 cryptonite kernel: [56374.595857] psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte 1
Aug 11 07:51:51 cryptonite kernel: [56374.596956] psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte 1
Aug 11 07:51:51 cryptonite kernel: [56374.598022] psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte 1
Aug 11 07:51:51 cryptonite kernel: [56374.599108] psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte 1
Aug 11 07:51:51 cryptonite kernel: [56374.608842] psmouse.c: GlidePoint at isa0060/serio1/input0 - driver resynched.

How I have managed to deal with it is to make sure I open a terminal window on one of my desktops and just unloading and reloading the driver, which get's everything working right again. It's a lot better then reloading X or rebooting. It happens mostly in
Firefox, but I have noticed it in other apps as well. It would be nice if there was an update from ubuntu since there seems to be a lot of people having the same problem.

modprobe -r psmouse
modprobe psmouse

Platform info:

Sony Vaio VGN-SZ340P
Linux cryptonite 2.6.28-15-generic #48-Ubuntu SMP Wed Jul 29 08:54:56 UTC 2009 i686 GNU/

I have similar equipment to Mike C and the same bug.
Sony Vaio SZ240P
Linux jordan-vaio 2.6.28-16-generic #55-Ubuntu SMP Tue Oct 20 19:48:24 UTC 2009 i686 GNU/Linux

I have been using Ubuntu since 5.04, and have only seen this bug with 9.04. Oddly I did not see it for a while after installing 9.04, but rather it only starting in the last month or so. Too bad I didn't keep track of which kernel.

Same Problem for me to...

Nov 14 22:27:42 Tecra kernel: [ 9742.823905] psmouse.c: DualPoint TouchPad at isa0060/serio4/input0 lost sync at byte 1
Nov 14 22:27:42 Tecra kernel: [ 9742.824965] psmouse.c: DualPoint TouchPad at isa0060/serio4/input0 lost sync at byte 1
Nov 14 22:27:42 Tecra kernel: [ 9742.828181] psmouse.c: DualPoint TouchPad at isa0060/serio4/input0 - driver resynched.
Nov 14 22:27:42 Tecra kernel: [ 9742.850536] psmouse.c: DualPoint TouchPad at isa0060/serio4/input0 lost sync at byte 6
Nov 14 22:27:42 Tecra kernel: [ 9742.851602] psmouse.c: DualPoint TouchPad at isa0060/serio4/input0 lost sync at byte 1
Nov 14 22:27:42 Tecra kernel: [ 9742.870885] psmouse.c: DualPoint TouchPad at isa0060/serio4/input0 - driver resynched.
Nov 14 22:27:42 Tecra kernel: [ 9742.871932] psmouse.c: DualPoint TouchPad at isa0060/serio4/input0 lost sync at byte 1
Nov 14 22:27:42 Tecra kernel: [ 9742.894724] psmouse.c: DualPoint TouchPad at isa0060/serio4/input0 - driver resynched.
Nov 14 22:27:44 Tecra kernel: [ 9745.046092] psmouse.c: DualPoint TouchPad at isa0060/serio4/input0 lost sync at byte 3
Nov 14 22:27:44 Tecra kernel: [ 9745.047281] psmouse.c: DualPoint TouchPad at isa0060/serio4/input0 lost sync at byte 1
Nov 14 22:27:44 Tecra kernel: [ 9745.050331] psmouse.c: DualPoint TouchPad at isa0060/serio4/input0 - driver resynched.

Paluskas workaround won't do it for me.

Nobody rebuilt the XServer in 9.10?

This is a really arcane bug, as most people will write it off as a hardware. I first thought it was a wireless mouse issue (started by changing batteries) it's only after observing it for a while, you can put the pieces together. I think I finally made the connection a week ago ... http://ubuntuforums.org/showthread.php?t=1335101

---
hi guys,

I've posted with an experience with 9.04 which I originally thought was a mouse driver issue. However a recent incident has caused me to suspect a misdiagnosis which may be why I have't gotten any answers.

The problem is intermittent (the worst kind) and revolves around the mouse. My system is dual-boot with XP, and XP works flawlessly, so we can eliminate the mouse hardware. However, it's a Labtec USB wireless (with keyboard).

The problem manifests itself by mouse clicks not working. Initial thoughts are the clicks are being ignored, as the pointer moves around the screen. However, a more detailed inspection of the situation reveals that it's not that the mouse clicks are being ignored. It's that the system appears to have "trapped" the mouse focus, as moving the mouse over buttons no longer causes a highlight. In firefox (for example) hyperlinks no longer cause the cursor to change to a hand.

The problem seems application independent ... happens in Nautilus, Firefox, NXClient (that ones a killer as it gets trapped in the NXClient window, and you cannot break out of it).

When the problem happens Alt-Tab also stops working, so you can't switch windows.

At first I suspected (obviously) a mouse/USB problem. However, on Friday, my Linux-expert brother had caused to VNC into the machine, and the problem happened to him. Which pretty much lets the hardware of the hook.

At his suggestion, I switched from GNOME to KDE, but the problem still happened, which narrows things down to the X-Server ?

(Notice the question mark - I'm a Windows programmer, so the intricacies of Linux/X-Server/Desktop environments is all a bit of a dark science to me).

Moving on from here, I have noticed one set of circumstances which appear to guarentee the fault happening, and which may explain the intermittent nature of the fault.

It seems to happen when the mouse focus passes into a list control (NOT a drop down list). I noticed this after opening the LogFile Viewer, and realised that the mouse focus was getting stick in the LH pane, which lists the available log files. Once it is stuck in there, it won't allow clicking anywhere. However, interestingly enough, if I hover the mouse over the right hand side (the contents of the logfile) I can hold the mouse button down and highlight text - so clearly the system is "getting" the mouse click. However moving the mouse to the "Close" button and clicking does nothing - no highlight, no click.

For those of you that know the "Blueman" app (for bluetooth) I also noticed it here ... when I click the icon the app comes up, and works fine, except if I click in the list of plug-ins. Then the mouse gets trapped ....

So there you have it ... This problem is occuring on two 9.04 installs, one an upgrade, and one a fresh install. The fresh install is my sons "mess-around" copy, so yesterda...

I agree with Jethro_UK, this is really a showstopper for using ubuntu as a desktop replacement. I can see the exact same problem as he does, but I have some reservations about somethings:

In my experience, using a xterm session, mount appears to be responsive and I can't make mouse button events disappear as they are so easily doing when on a gnome desktop.

I can also say that I previously used Gentoo with a KDE desktop and there a very similar problem occurred whereby mouse click events would completely stop. After quite some frustration I found that the only way to resolve that (save logging out/in again) was to alt-ctrl to console terminal and then back to windows and then use alt-next to flip windows. Then mouse clicks started registering again.

Initially I have to say that my experience on Gentoo was the worst, but at least there it was something you could work yourself out of, here now on Ubuntu the issue that the desktop feels sluggish and unresponsive. A bit like having to deal with someone who is deaf or can't understand what you are saying. Needless to say, if you have any streak of impatience in you then this is not going to make you hang around for long.

So, is there any commonality between KDE/Gnome which could explain this behaviour, which I feel cannot be seen on a straight "window manager less" environment. I'm going to swap over to window manager less for a while to see if the behaviour reappears. Could it be a specific application. I use amarok, could that be it?

sorry typo, mount = mouse in 2nd paragraph.

I also agree with Jethro_UK & TaxAlien, this is really a showstopper...

As far as I know Steven Harms did a bugfix in Feb 2009 (!!!) [See comment #78] but nobody took it into rep and did a rebuild?
What do I have to do? Rebuid the whole Xorg myself? how can I do that?

Bryce - Any idea if the current Xorg builds include Peters patch mi: don't call UpdateSpriteForScreen if we have Xinerama enabled. #18668(http://bugs.freedesktop.org/show_bug.cgi?id=18668) in newer distros?

I think we included this in intrepid, but I am not sure upstream included it yet?

To see if there's a Ubuntu working version, I've installed all versions, from Karmic 9.10, Jaunty 9.04, Intrepid 8.10, down to Hardy 8.04: all suffer the same problem.

All were clean installs with all updates applied. My machine is a Packard-Bell laptop.

This has only just started happening for me, usually but not exclusively while in Firefox (3.5.7).

I'm using one monitor, on Kubuntu 9.10, desktop AMD 64-bit, nVidia GeForce 6100, nvidia-glx-185, everything up-to-date, USB mouse which works perfectly with my laptop.

Having this problem for the last days even though my setup hasn't changed for over a year. Using Ubuntu 9.10 64-bit running awesome. Using a Logitech MX300 (ancient, but similar to one in report). My setup at work with external monitor and different mouse hasn't shown the issue yet.

Occasionally losing focus and no responding mouse buttons for seemingly any application or all except one (firefox, pidgin, virtualbox, what I happen to be using at the time). When triggered, the touchpad buttons can't be used either.

I never could get the mentioned workarounds to work, but that could be because I use awesome.

workaround 1: trash your Hardware
workaround 2: reinstall winXP

...A systemrestart every 20 minutes since over one year isn't really sexy

Affects me on a clean 9.10 32 bit. Built with mini.iso and only added gnome-core gdm and xorg.

Hardware is Dell Mini 9 with synaptics. Error also affects bluetooth mouse connected once in a while.

CTRL-ALT-D fixes it for a few seconds until you need to press a button again.

Logout and relogin RIGHT after boot keeps it away for sometimes as long as 20 mins.

My other system Dell Latitude 630 also with a synaptics pad but with an upgraded 64bit full Karmic doesent show this weird error.

Think it is the same as +bug/375905

I am on Ubuntu 9.10 64 bit with Dell Precision T3500 and experiencing the same issue. Mouse cursor is there but I cant click on anything.

What helps is pressing Alt + F4 to close the active window and then the mouse go back to normal. (Not always)

Also note that when mouse stops responding the Alt + Tab combination doesnt work along with Ctrl + Alt + Down (Compiz cube). Ctrl + Alt + Arrows does work and i cant switch to a different desktop although the mouse doesnt work there either.

After a couple of minutes everything goes back to normal. Weird....

Okay, it would seem that this but has decided to hit me too.

I have never before experienced it, but ever since the last ubuntu update before 14. March, 2010 (I think it was a also new kernel image) I am suddenly getting these weird mouse problems that others have described. I can move the mouse cursor, but any mouse clicks (left or right) are mostly ignored. If I unplug and replug my usb mouse, nothing happens and the problem persists. Since I use a laptop, I am getting the same on the touchpad, so its definitely not a hardware problem. It's almost as if there was some invisible window blocking all the mouse clicks from reaching the proper windows underneath. I found out that right-clicking usually helps when menus pop up. That's when the problem normally goes away for a while. I have no idea how to reproduce it though it seems to happen randomly.

At one point I managed to run the update manager, which warned me that something is stealing focus and that somebody may be doing something malicious. Another weird example is when the firefox window was fully responsive, but everything else was dead. In third case I managed to get the bottom bar in gnome to work, but everything else was frozen.

I mostly run a gnome terminal and firefox when the bug hits. Keyboard is responsive though alt+tab doesn't work. I can do an Alt+F2 to run an xterm to gain some control and killall some unresponsive apps. On most windows I couldn't click the little X to close the window, but I could still use the other two controls to minimize and maximize it. Sometimes even those don't work and you can't click and drag the window around.

~$uname -a
Linux lprime 2.6.31-20-generic #57-Ubuntu SMP Mon Feb 8 09:05:19 UTC 2010 i686 GNU/Linux

I recently started running into the same problem. In terms of differences from what was posted before:

 - I was using the FGLRX driver. I've uninstalled it -- I'll post back if that solves my problem.

 - alt-tab does work

 - visual effects are set to "none"

 - logging in and logging out may or may not fix the problem

 - Some app (I'm not sure which) gave a warning "GtkMenu failed to grab the pointer"

As Bryan I've also recently experienced the same problem. I'm running Ubuntu 9.10, upgraded from 8.10 via 9.04. I have not experienced the problem on the previous versions, but have seen it on and off for a few days now.

The mouse-click symptoms are pretty much the same as described. I can move the pointer, but the mouse does not react to links, does not highlight icons, nor show help-text when held above time/date or other symbols. In addition:
- Alt+tab does not work
- Alt+space does not work
- Ctrl+tab does work
- Ctrl+Alt+arrow does shift workspace
- Ctrl+Alt+backspace works, and usually solves the problem (but is annoying)
- Alt+F1 will highlight the Applications-menu-text, but the menu fails to show
- Alt+F2 does work
- Right-clicking will occationally solve the problem
- Clicking my processor-log-item, opening my system settings usually triggers the bug
- When the bug is "active" update manger says "failed to grab the pointer"

I started having this problem like 6 months ago when I was using Xubuntu 9.10. Short of restarting the Xserver nothing would fix it. I tried removing all my configuration files and starting clean but it still came back so i gave up on Xfce thinking it was the problem and installed Kubuntu 10.04 and I have it happening regularly in KDE even on the first boot. It seems like the problem might be related to the window managers because it seems like dragging or un/maximizing the windows with a double click sometimes triggers it.

I use google chrome with gmail open most of the time, and a logitech mx laser mouse. but I have plugged in other mice when experiencing the symptoms and they didn't work either. FWIW I am using an nvidia 6600 video card with the nvidia proprietary drivers and a twinview dual monitor setup too. Is there any other trouble shooting info I can post? It happens pretty regularly for me.

Problem persists in 10.04 Beta.

I can confirm that removal of the FGLRX driver appears to have fixed the problem for me.

Now confirmed on Ubuntu 10.04 and Kubuntu 10.04. So it is probably independent of KDE/Gnome. Switching users also helps in my case, but only for a few seconds. One of the most annoying bugs ever.

I had this happen again this morning and had a chance to try out some of the suggested workarounds in this thread an so I thought I would also add that NONE of them work for me! When I bring up the windows options menu it doesn't get focus so I can never select "Move". Using KDE I can do kwin --replace and it works for like 2 seconds before it all breaks again. Also it does not seem to be Xinerama specific or Nvidia specific because I have had it happen on my other machine that is neither dual monitor nor an nvidia card. This bug is getting really irritating and starting make me question Ubuntu's stability which is something I used to be a huge advocate for.

I am on this bug's list because it used to be an issue when my system used Nvidia video, but a while back I had to replace my MB which now has an ATI chip and guess what?, no problems like this since.

It would be interesting to have all the particular hardware setups that are still experiencing this collated.

I'll have this occur at least once a week, it's rather annoying. None of the workarounds help for me, I have to log out and log back in. My system is all Intel hardware except for the video card with is an nvidia GeForce 7600 GS (and I'm using the proprietary nvidia driver). I'm going to go see if I can find an old ATI card to see if that helps.

I'm not sure (I don't completely understand the bug-tracking system), but I think the status of this bug is currently "invalid" (for Linux) or "fix-released" (for xorg-server), and consequently no-one is likely to try to fix it. Since the released fix from last year only works for some people and doesn't fix the general case, would it be appropriate to re-open the bug?

Currently restarting X-server just after login usually fixes the bug for me.

I have an Nvidia GeForce 7300 GT, using the proprietary driver.

This problem is actual for me for a long time.

The workaround I'm using (every single day) is executing:

sudo modprobe -r psmouse && sudo modprobe psmouse

in my terminal. Sometimes, I have to repeat these commands for a few times in a row...

This have happened to me a lot recently, I'm gonna try the workarounds next time it happens and see if any of them work. I'm running 10.04 and I've got an intel chip btw.

It just happened again, but this time I tried Dmitry V Shurupov's workaround. It didn't work (I'm not using a PS/2 mouse), but what did work was removing and re-inserting the driver for my wireless keyboard/mouse (hid_logitech). I only had to do it once and sure enough everything was back to normal.

Still experiencing this problem after upgrading to Kubuntu 10.04 "Lucid Lynx" LTS.

dmesg shows the same messages when it happens:

[17441.032652] psmouse.c: GlidePoint at isa0060/serio4/input0 lost sync at byte 6
[17441.033811] psmouse.c: GlidePoint at isa0060/serio4/input0 lost sync at byte 1
[17441.037508] psmouse.c: GlidePoint at isa0060/serio4/input0 - driver resynched.
[17441.038701] psmouse.c: GlidePoint at isa0060/serio4/input0 lost sync at byte 1
[17441.050488] psmouse.c: GlidePoint at isa0060/serio4/input0 - driver resynched.
[17465.590702] input: PS/2 Mouse as /devices/platform/i8042/serio4/input/input10
[17465.607269] input: AlpsPS/2 ALPS GlidePoint as /devices/platform/i8042/serio4/input/input11

[This is an automatic notification.]

Hi Lionel,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 41301

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 41301 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

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

I am currently running 10.04 stable. I got hit by this bug in the last couple of weeks. Don't know how. I have been applying regular updates. This all started when I enabled nis/autofs - which in our environment causes it to remap /usr/local. So I diligently moved /usr/local to /usr/local1. All applications worked. Was able to login etc. However the mouse stopped working. After fidgeting with it for a while I have figured out running the mouse in left-handed mouse mode works - but not right-handed.

All right, more info. I reinstalled my machine from scratch with Lucid, and from the very beginning the bug appeared. Restarting the X server once it manifested seemed to solve the problem, but it was getting a bit tiresome.

Then I switched from my Logitech LX7 USB wireless mouse to a regular PS2 wired mouse, and the bug failed to appear at boot. It definitely looks as though the USB mouse was the trigger for the bug for me. But I really like my mouse, so I still hope this gets solved.

I am also with wireless logitech mouse with usb receiver.

On 28 June 2010 22:10, Kristian Spilhaug <email address hidden> wrote:

> All right, more info. I reinstalled my machine from scratch with Lucid,
> and from the very beginning the bug appeared. Restarting the X server
> once it manifested seemed to solve the problem, but it was getting a bit
> tiresome.
>
> Then I switched from my Logitech LX7 USB wireless mouse to a regular PS2
> wired mouse, and the bug failed to appear at boot. It definitely looks
> as though the USB mouse was the trigger for the bug for me. But I really
> like my mouse, so I still hope this gets solved.
>
> --
> Mouse clicks stop working sporadically
> https://bugs.launchpad.net/bugs/41301
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in “linux” package in Ubuntu: Confirmed
> Status in “xorg-server” package in Ubuntu: Incomplete
>
> Bug description:
> This bug is a long standing one for me in Dapper but it becomes more and
> more frequent in recent Dapper beta.
>
> Unfortunatly, there's no way I can reproduce it.
>
>
> Symptoms : the mouse buttons (all of them) stop working without any reason.
> Seems to happen mainly when surfing with Epiphany but not only.
>
>
> In fact, it's just like my mouse was in another dimension. I use "focus
> follow pointer" and it doesn't work anymore. I can see my cursor and moving
> it : the system just ignore it. No more click, no more focus following
> pointer.
>
> Also, the keyboard keeps working perfectly. By using shortcut keys, I can
> continue working normally.
>
> The workaround to have the mouse again is hopefully very simple : use the
> change desktop shortcut. The alt-tab shortcut is also working. Yes, it's
> strange, but they are the only two shortcuts I've found that bypass this bug
> ! Strange isn't it ?
>
> My mouse is a PS/2 Logitech MX310. The workaround seems to be the proof
> that it's not an hardware failure.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/41301/+subscribe
>

Another user of a Logitech USB mouse (MediaPlay) here. I've found that running `modprobe -r usbhid && modprobe usbhid` works as a temporary fix.

I've also noticed that the mouse focus is, at least in some cases, "stuck" on a particular window. For example, if I double-click on the focused window (when this bug is active) there will be no perceivable effect on that window. However, sometimes the response to that mouse action (e.g. text selection) will be apparent on another window when I switch back to it with ALT-TAB.

Like DJ I'm running a (mostly) regularly updated 10.04 and have started experiencing this problem within the past month or so. After restarting X it will often take a long time for this to start happening (days, weeks) but once it starts it will keep happening quite often. I'm finding that using the `modprobe` workaround will only be effective for about an hour or so.

I can confirm this bug too .......

Start: Few weeks after an upgrade from karmic to lucid. After it start never left. Upgrade from lucid to maverick "current" did not change anything. It occur with tow logitech mouse, but not with my crappy 5$ targus mouse !

My solution:

- boot without the logitech mouse one time
- shutdown
- restart with the logitech mouse connected on an another usb port.

You have one hour, on day, or one week of life without this problem lol.

more seriously: I forget where, maybe in /var, there a temporary file describe mouse logical access path (?) ... If i remove it with root account there's no need to reboot or unplug the mouse ...

Anyone can tell where the file is ? Can we make a rule to delete this file @ computer shutdown process ?

Regards

Hardware: intel P55 - nvidia 8800gt - MOUSE logitech cordless click plus (radio) / lx6 (bleutooth)
Software: linux-image-2.6.35-15-generic-pae - xserver-xorg-core 1.8.99.905-1ubuntu2 - nvidia-current 256.44-0ubuntu1

Having the same issue in Maverick for several days:

Left mouse button often "stucks" in a clicked state, in while focused in Nautilus, Empathy, Chromium, GIMP, etc. Moving the mouse results in dragging the window (if ALT was pressed) or highlighting bunches of text. Clicking the mouse button doesn't help.

I use another workaround: unplug my (A4tech wired) mouse, click the left button on the touchpad, replug the mouse back. Everything works for several minutes, then starts going crazy again.

Running xev results in the following weirdness:

* Presses and releases are registered.
* When the bug occurs, LEFT button clicks are never registered, right and middle button is okay.
* Unplugging the mouse and clicking inside xev with the touchpad produces ONE ButtonRelease event.
* Everything returns back to normal, until the bug occurs again.

By the way, downgrading to xserver-xorg-input-evdev 1:2.3.2-6build1 solved the problem for me.

Hi all,

@ Артём Попов,

"By the way, downgrading to xserver-xorg-input-evdev 1:2.3.2-6build1 solved the problem for me."

I was searching for this package but all results are for maverick version .... (1:2.3.2-6build1)
am i right ?

What package work with lucid ?

Regards

Yes, I'm on Maverick. Don't know any working Lucid version. There's supposedly a different bug, because I'm having this problem with a specific Ubuntu patch, introduced after the 2.3.2-6build1 version.

Ok, i've maverick on my desktop too. xserver-xorg-input-evdev 1:2.3.2-6ubuntu1 is installed on.

But what difference between xserver-xorg-input-evdev 1:2.3.2-6ubuntu1 and xserver-xorg-input-evdev 2.3.2-6build1 ?

http://www.ubuntuupdates.org/packages/show/217988

I can *almost* reproduce the loss of mouse's left-click with the history panel in Eclipse,
a (java-)SWT application that uses GTK widgets.

Steps to Reproduce:
1. Go to a java project with its files handled by in CVS,
2. right-click on a in-CVS file with at least 2 revisions stored, "Team | Show History ", the "History" view should appear,
3. in "History" view select 2 older revisions, either using Shift+Left_Click or Ctrl_Right_Click,
4. thats it!
If you are "lucky", mouse's left_click ceases to work. I have to logout/login to restore it (i have not tried yet plug/unplug mouse *with* left_button pressed).

SYSTEM CONFIGURATION:
---------------------
Linux hostname 2.6.34-gentoo-r1 #1 SMP Wed Jul 21 12:55:02 EEST 2010 i686 Intel(R) Core(TM)2 Duo CPU E4400 @ 2.00GHz GenuineIntel GNU/Linux

[I] x11-base/xorg-server
     Installed versions: 1.7.6(04:01:10 μμ 27/04/2010)(dmx hal nptl sdl xorg -debug -ipv6 -kdrive -minimal -tslib)
     Homepage: http://xorg.freedesktop.org/
     Description: X.Org X servers

[I] x11-base/xorg-drivers
     Installed versions: 1.7(11:02:36 πμ 21/07/2010)(input_devices_evdev input_devices_keyboard input_devices_mouse video_cards_fbdev video_cards_radeon video_cards_vesa -input_devices_acecad -input_devices_aiptek -input_devices_fpit -input_devices_joystick -input_devices_penmount -input_devices_synaptics -input_devices_tslib -input_devices_virtualbox -input_devices_vmmouse -input_devices_void -input_devices_wacom -video_cards_apm -video_cards_ark -video_cards_ast -video_cards_chips -video_cards_cirrus -video_cards_dummy -video_cards_epson -video_cards_fglrx -video_cards_geode -video_cards_glint -video_cards_i128 -video_cards_i740 -video_cards_impact -video_cards_intel -video_cards_mach64 -video_cards_mga -video_cards_neomagic -video_cards_newport -video_cards_nouveau -video_cards_nv -video_cards_nvidia -video_cards_r128 -video_cards_radeonhd -video_cards_rendition -video_cards_s3 -video_cards_s3virge -video_cards_savage -video_cards_siliconmotion -video_cards_sis -video_cards_sisusb -video_cards_sunbw2 -video_cards_suncg14 -video_cards_suncg3 -video_cards_suncg6 -video_cards_sunffb -video_cards_sunleo -video_cards_suntcx -video_cards_tdfx -video_cards_tga -video_cards_trident -video_cards_tseng -video_cards_v4l -video_cards_via -video_cards_virtualbox -video_cards_vmware -video_cards_voodoo -video_cards_xgi)

Section "InputDevice"
        Identifier "Mouse0"
        Driver "evdev"
        Option "Name" "Microsofrt USB Laser Mouse"
        Option "Emulate3Buttons" "no"
EndSection

Nothing unusual in /etc/hal/fdi/policy/10-xinput-configuration.fdi

java -version
java version "1.6.0_20"
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) Server VM (build 16.3-b01, mixed mode)

Eclipse 3.5, Galileo

Can be reproduced on maverick by using a sound volume key on keyboard.

Indicator me fall in a graphic bug when left click doesn't work.

Description:
The name of user appear tow time in the panel. One time in it normal place and on the "power button" of session notification applet.

This bug can appear in other circumstance, but often when the left click not respond.

I can confirm comment #137 by Marcos Vinícius. The problem did not affect me before I updated to Maverik.

Also, I noticed that "xdotool click 1" (xdotool is a X11 macro processor) does not work either. So the problem must lie somewhere within XOrg.

Same problem here.

I did a fresh installation of maverick 64-bits and the left click of the mouse get stuck randomly and makes it unusable. I have to unplug it to get the touchpad work and if I plug it again the problem gets back and the left button is stuck.

This don't happen on terminal console with gmp so definitively it is a xorg problem.

I downgraded to xserver-xorg-input-evdev_2.3.2-6build1_amd64.deb as suggested and the problem is fixed. I have the usb mouse working as expected now.

https://launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/1:2.3.2-6build1/+build/1911099

This bug has been effecting me for a very long time, over a number of different versions of Ubuntu (currently running 10.04.1)

Something has changed recently however.

When I initially encountered the problem, which was about a year ago it occurred quite frequently. I found a workaround which for some reason made it occur less often. That is have the system automagically log in to my guest account, then I log out and log in as me. (In this instance the guest account was effected by the bug, but I immediately logged out and thus was not a problem).

Using this work around I've only had the problem on rare occasions over the last ~6 months+ (tbh I can't really recall the time frame, but it's been a long time). When it did occur I just logged out and back in and the problem was usually (but not always) resolved. Sometimes I had to resort to alt-F1 a terminal login as root and reboot.

However sometime over the last week or two I've performed an update which has changed things dramatically. My workaround no longer works and the problem occurs with a far greater frequency.

I can usually right click the last component I used (the one that has stolen the focus) bring up a context menu and the problem is resolved temporarily. Once it starts though it keeps re-occurring until I reboot.

I note that as I type this the bug is currently in effect and that I notice nothing unusual in Bubble Monitor running in my panel; ie CPU, swap and memory use all appear normal and not under any strain.

I have the same left mouse click stop working problem. However, this only occurs on my laptop that has a touch pad. Left clicking does not stop working on the touch pad by itself (no external mouse attached) and in tandem. Even when the external mouse looses its click, the touch pad does not. When the external mouse does loose its click, I just unplug it then plug it back in. I've never had the problem on my desktop machine (no touch pad, just an external USB mouse.)

I can confirm what Ken wrote. With Ubuntu 10.04 my left click stops only
with the external wireless logitech USB mouse. The touch pad continues to
function. My Laptop is Dell XPS m1530

On 2 November 2010 12:12, Ken Pratt <email address hidden> wrote:

> I have the same left mouse click stop working problem. However, this
> only occurs on my laptop that has a touch pad. Left clicking does not
> stop working on the touch pad by itself (no external mouse attached) and
> in tandem. Even when the external mouse looses its click, the touch pad
> does not. When the external mouse does loose its click, I just unplug
> it then plug it back in. I've never had the problem on my desktop
> machine (no touch pad, just an external USB mouse.)
>
> --
> Mouse clicks stop working sporadically
> https://bugs.launchpad.net/bugs/41301
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (55739).
>
> Status in “linux” package in Ubuntu: Confirmed
> Status in “xorg-server” package in Ubuntu: Confirmed
> Status in “xserver-xorg-input-evdev” package in Ubuntu: Confirmed
>
> Bug description:
> This bug is a long standing one for me in Dapper but it becomes more and
> more frequent in recent Dapper beta.
>
> Unfortunatly, there's no way I can reproduce it.
>
>
> Symptoms : the mouse buttons (all of them) stop working without any reason.
> Seems to happen mainly when surfing with Epiphany but not only.
>
>
> In fact, it's just like my mouse was in another dimension. I use "focus
> follow pointer" and it doesn't work anymore. I can see my cursor and moving
> it : the system just ignore it. No more click, no more focus following
> pointer.
>
> Also, the keyboard keeps working perfectly. By using shortcut keys, I can
> continue working normally.
>
> The workaround to have the mouse again is hopefully very simple : use the
> change desktop shortcut. The alt-tab shortcut is also working. Yes, it's
> strange, but they are the only two shortcuts I've found that bypass this bug
> ! Strange isn't it ?
>
> My mouse is a PS/2 Logitech MX310. The workaround seems to be the proof
> that it's not an hardware failure.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/41301/+subscribe
>

I just noticed: When I trigger the bug using a keyboard-hotkey (as described above) while having the pointer above a xev window, xev registers a Button-1-Down (and down only!) Event. I'll attach xev's output starting from the moment I pressed Volume-Up on my keyboard.

In the hope of getting the importance of this bug raised I'd like to add that this bug is now stopping me from updating using the update manager.

When it tries to open the authentication dialog box I get an alert window "Cannot grab Mouse". The only thing I can do then is close it with Alt-F4. Update manager then goes back and refreshes the package list and no update occurs.

I had a similar problem last week (maybe the same?). I bought a new mouse 3 weeks ago (logitech usb and wired) that worked nice since then.

Tried with a different login : same problem.
Removed the nvidia proprietary driver, and used the nouveau driver : same problem (+ some refresh problems during scrolling)
Pluging and unpluging the mouse didn't solve the problem. The computer was almost unusable without keyboard navigation skills (which isn't the case for everybody at home).

Note : in Rhythmbox, when the problem occured and the mouse focus was grabed in the list of songs, I saw sometimes the color of the selected song switching to grey during 1 or 2 seconds without doing anything.

With another mouse : same problem
Booting from a USB disk with maverick 32bits (instead of AMD64) : same problem.

Then I remembered there was some parameters in the BIOS concerning USB mouse and keyboard support. My previous mouse was a PS2 one, and my keyboard is still a PS2 one. So these parameters were disabled in the BIOS.

For completness and because some actions may have had an influence in the result (maybe some cold reboot or disabling/re-enabling USB could have correctly reseted the hardware), here are the details of what I did :
1 - I first enabled only the mouse parameter (since my keyboard is PS2) and did a warm reboot. The problem seemed to disappear. But few hours later my wife had once the problem.
2 - I completly shut down the computer to do a cold boot.
3 - I disabled USB in the BIOS and rebooted until login (so no mouse, just PS2 keyboard),
4 - then rebooted into the BIOS, only enabled USB 1.1, enabled both mouse and keyboard USB support, rebooted and played a while to check everything was okay in a session,
5 - then rebooted into the BIOS, re-enabled USB2, rebooted and since then I don't have anymore problems with the mouse.

I don't know why the new mouse worked few weeks with these parameters disabled???

Hope this can help.
PS : Same bug seems to be related in 375905

The problem seems to disappear after upgrading to Natty. Weird.

I just would like to confirm once more this bug. I have an intel board, a logitech mouse using a freshly installed kubuntu 10.4 LTS.
If the bug is active, i have no xev events, xdotool does not seems to help. But the restarting of the Linux kernel usbhid module with : "modprobe -r usbhid && modprobe usbhid" does the trick.

If I can provide any other files about my xorg or kernel let me know.

I have this problem too on ubuntu 10.04. I am using awesome as window manager and it seems to occur when switching between desktops with the mouse. I had also the impression that it occurs when using firefox, especially when opening flash content.

Luckily, the bug vanished completely after upgrading to ubuntu 10.10 :-D.

My friend has this weird problem too. Mouse clicks stop working randomly without any apparent reason, while he can still move the pointer. Keyboard works, but Alt-Tab stops working too, so that it becomes impossible to switch between windows. Looks like a problem with window manager, but this happens both with metacity and compiz. If I connect to his desktop via VNC, I cannot click anything either, Alt-Tab doesn't work for me too. Xev doesn't show any mouse events, event mouse movement over the window. If the mouse is re-plugged, everything starts working again.

Using 64-bit Ubuntu 10.04 and latest (260.19.21) NVIDIA driver installed by hand (just becuase GeForce GTX 460 isn't supported by any driver available in Ubuntu repos). Otherwise the system is untouched.

I can confirm this bug in xubuntu 10.10.
It occured on my old Medion md 9800 notebook.
After fighting with it for a week i noticed, that it only happened when my external mouse was plugged in.
Unplugging the external mouse solved this problem for me! Let me know if you need more information.

A friend of mime who had a similar problem, but the mouse button behaved like if was always clicked at random, told me that unpluging and repluging the mouse worked. I will try this and also test a cable mouse.

I just noticed that this bug does no longer affect me. At least pressing the volume keys on my keyboard does not trigger the bug anymore. [ c.f. comment #139 ]

Hello,

Unfortunately I have to take back my comment #149. After my upgrade to ubuntu 10.10 this bug did not occur at all for maybe 2 weeks. Everything worked perfectly! But then it re-occured out of nothing. This is really strange, since if haven't changed anything on my system. I even haven't done any update since the upgrade.
I am using Awesome and have to live now with the following "work-around": After the mouse gets inresponsible I press ModKey-Ctrl-R to restart Awesome which gives me back control over the mouse. But usually only for one mouse click. So for the next mouse action i have to restart Awesome again. And so on ... this is getting really annoying

For the record: I am using Ubuntu 10.10 on a Laptop with external Monitor. The two monitors (Laptop and external) are managed by Xinerama.

Alex.

I also have this problem on 10.04 (and 9.10, when I was using that).

The problem *only* occurs when I use a Java based application called Aptana (v2 or v3), which is based on Eclipse. Usually it occurs when I am using a tree navigation pane and either double or single click on an item. Mouse left click will then stop working. Keyboard and mouse middle/right clicks still work. Problem occurs fairly frequently.

I tried the alt-tab and alt-ctrl-1>7 suggestion, unplugging my mouse and "modprobe -r usbhid && modprobe usbhid" to no effect. I always have to reboot.

Currently trying the suggestion to add "noapic acpi=off" to my menu.lst entry.

Mouse is a Logitech Cordless Trackman.
Video is NVIDIA GeForce 8400 GS, currently using non-free driver 195.36.24 and TwinView.
Java is currently sun-java6.
Flash is Adobe's.
Not using Compiz.

Had an issue very similar to what is described above.

- mouse would either stop working or become "trapped" within a certain element of a window.
- mouse would move around screen fine, but clicks would only effect wherever it was "trapped"
- alt + tab would sometimes fix problem
- occurred in Ubuntu 9.10 and persisted through upgrade to 10.4
- happened for me at EVERY login, though sometimes I could open a window or two before it began
- unplug then replug mouse in would sometimes be a temp fix, but the issue would come up again quickly

One thing I noticed that was pretty common among posts is that many people were using a Logitech mouse, I was too: Logitech MX518 USB mouse.

Switched mouse out for basic HP PS/2 mouse connected through PS/2 to USB converter and issue cleared up COMPLETELY. New mouse works fine.

Another Note, the Logitech MX518 that was giving me the issue with Ubuntu works fine with Windows XP.

I'm having the same problem on my laptop. It's an Acer Aspire 5745-7247. When I use an external Logitech mouse (model M-BZ96C), there is no problem at all, but when I use Acer's built-in touch pad, the problem begins immediately (so it's VERY easy to reproduce). I generally have to resort to using only the keyboard to close things down, and then I have to reboot.

Since I can reproduce this problem consistently, I'd be happy to lend a hand. To start, if it helps, below is some info about the laptop, which is running Ubuntu 10.04 LTS. I'd be great to get this problem fixed, so please let me know how I can help.

lspci:
------
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 18)
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18)
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05)
00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 05)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05)
00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05)
01:00.0 Ethernet controller: Atheros Communications AR8151 v1.0 Gigabit Ethernet (rev c0)
02:00.0 Network controller: Atheros Communications Inc. AR9287 Wireless Network Adapter (rev 01)
3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 05)
3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 05)
3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 05)
3f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 05)
3f:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 05)
3f:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 05)

lsmod:
------
Module Size Used by
aes_i586 7268 3
aes_generic 26863 1 aes_i586
binfmt_misc 6587 1
ppdev 5259 0
dm_crypt 11331 0
nfsd 238967 13
exportfs 3437 1 nfsd
nfs 265078 0
lockd 64849 2 nfsd,nfs
nfs_acl 2245 2 nfsd,nfs
auth_rpcgss 33767 2 nfsd,nfs
joydev 8740 0
snd_hda_codec_intelhdmi 11622 1
snd_hda_codec_realtek 203344 1
arc4 ...

-- See this for comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/673201/comments/18

Hi,

I have an HP elitebook 8530p crap, and I had the same problem
(the X server thought that one button was pressed, but not released),
and it has turned out that an 'rmmod psmouse' "solves" the problem.

So I backlisted the psmouse module:

cat /etc/modprobe.d/faszom.conf
#options psmouse proto=imps
blacklist psmouse

I suppose that you can play with the "options psmouse proto=imps", but it doesn't work for me.
It's easier to buy an usb mice, and forget the touchpad.

So I think this bug is related to some kernel bug/regression somewhere in the psmouse/synaptic code.

Or buggy hardware.
(The problem cames out _maybe_ often, if the laptop's temperature is higher, but it's just a feeling.)

>The workaround is to edit the /boot/grub/menu.lst file. Add "noapic acpi=off" to the end of the >root line. You can do this while booting just by hitting e when the boot menu appears. Then >select the root line and hit e again. Go to the end of the line and add the command. Hit return to >save the edit and then b to continue the boot process.

This workaround does not work for me.

I got the same problem that my mouse clicks became useless after compiling an e-mail in Thunderbird. It looks like it happened when clicking on the Stardict application which was at the back of the compose window, and then before it could get focus, quickly clicked on the compose window again. After closing all windows (applications) one-by-one with the menu shortcut keys, the main menu reacted again on mouse clicks. After opening a Gnome Terminal window, the mouse clicks and even keystrokes are disabled again. Then, when killing the Terminal session from a tty terminal, the keyboard works again, but no mouse clicks on the window menus or statusbar have any effect.

I used the touchpad.

dmesg:

[ 5344.877418] psmouse.c: GlidePoint at isa0060/serio4/input0 lost sync at byte 6
[ 5344.878461] psmouse.c: GlidePoint at isa0060/serio4/input0 lost sync at byte 1
[ 5344.881717] psmouse.c: GlidePoint at isa0060/serio4/input0 - driver resynched.
[ 5344.882753] psmouse.c: GlidePoint at isa0060/serio4/input0 lost sync at byte 1
[ 5344.894432] psmouse.c: GlidePoint at isa0060/serio4/input0 - driver resynched.

after removing and reloading the psmouse kernel module:

[ 5372.345756] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
... 6 times

Ubuntu Lucid on a Compaq Presario V3000

Does this bug seem to be vanished with Natty? Haven't noticed anything of that since upgrading to 11.04 in April.

I had the same problem with Fedora 12 linux running a laptop Acer Aspire 5100 (and occurs with fedora 14 and 15). The external USB mouse has the same bug described here, while the touchpad does not. Since several people have mentioned that they use Logitech wireless mice, I tested a wired USB mouse ($1 from ebay). It works perfectly, so this may be specific of those Logitech USB mice/wireless, have others noted this?

I had this bug for a couple of days on my desktop machine running Ubuntu 10.10. It started after a kernel update, but that might not be relevant. Motherboard is Abit AV8, Radeon 9600 graphics.

My mouse is Logitech Cordless Click! and plugging a similar Microsoft mouse did not help right away, but after rebooting with the MS mouse (Logitech unplugged) I haven't seen the problem again.

Changing workspace did not help, actually reboot was the only solution I found, and it helped for only a couple of clicks. But I didn't try many of the workarounds mentioned here.

Also, I often had a random tooltip left hanging on the screen. My keyboard worked mostly fine, but Alt-F1 did not open the system menu, only highlighted it.

I had the same problem with ubuntu 11.10 running Gnome Classic...

This is what I did as a test to see if it might fix it:

started: Symnaptic Package Manager
Remove mousetweaks
reinstall xserver-xorg-input-mouse

did not install mousetweaks again.

time will tell if that has an effect on it.

Don

I have been running without mousetweaks for 2 days now - the system runs faster and their has been no mouse problems what-so-ever. In fact, I can't tell what the benefit of mousetweaks really is.

Remove mousetweaks for a more stable, reliable and faster ubuntu. I would recommend that this program should be removed from the default system.

Hooooooooo, well!

It seems you feel right man !
I was searching in many directions - before i move to another mouse
manufacturer !

But with that i think, and over all i hope your right.

If you can validate this don't forget to propagate the news. Numbers of
users saw this problem landing....

Cldt
xtrip

Le jeudi 05 janvier 2012 à 19:54 +0000, Don Golding a écrit :

> I have been running without mousetweaks for 2 days now - the system runs
> faster and their has been no mouse problems what-so-ever. In fact, I
> can't tell what the benefit of mousetweaks really is.
>
> Remove mousetweaks for a more stable, reliable and faster ubuntu. I
> would recommend that this program should be removed from the default
> system.
>

I am experiencing this bug on a System76 Pangolin P7 laptop. Bug was first encountered in 11.04 after latest kernel upgrade (3.0.0-15-generic), and upgrade to 11.10 did not help. I also tried a clean install of linux mint 12, but bug was still there. So now I have done a clean install of ubuntu 11.10, but the problem still persists, I have tried the workaround suggested by Don Golding above (remove mousetweaks), and it seemed to work for a little while, but the issue came back. It seemed to be related to when I plugged in an external USB sound card. Unplugging the sound card and rebooting does not cure the problem now either...

IMO, this is a pretty serious bug. While I *can* use the computer, I *can't* use it well, and some things don't work at all. For example, even if I use the multiple right-click technique to bring focus to the desktop, I can't double click on any of the icons, or even select them with a single click, or drag them around. I can only right-click on them, and select "open". Sometimes, the multiple-right-clcik technique fails to ever bring the mouse focus to the desired window, and I have to close it with Alt-F4.

Any ideas on another workaround, or info on an impending fix? I'd really like to be rid of this super-annoying bug!!

Cheers,

~Isaac

The fix is to buy a new mouse.

Sean, while I appreciate that you took the time to try to provide an answer, if you read the details of the bug, you will see that this is clearly NOT a hardware issue. This bug affects ANY mouse plugged into the computer, as well as the built-in track pad of the laptop. Thus, simply getting a new mouse is NOT a fix, in any sense of the word.

Any other suggestions for workarounds?

Oh, and I am using 64bit.

It can be either actually. For me, the solution to this issue was hardware. My mouse's faulty connectors didn't work.

What is your motherboard model?

Hi Sean, according to the output of lshw, my motherboard is a CLEVO W76x/M77xCUH. Would such a hardware problem affect also USB mice? Because I am having this problem with any external mouse I try to use, as well as with the touchpad... Any help is appreciated!

On System76 help forums, isantop has told me that this is a known software issue supposedly to be fixed in 12.04. Do you (or anyone else) know anything about that?

Well, I have been trying the various workarounds suggested in this thread, and it seems that the workaround suggested by Dimitri in post #120 (sudo modprobe -r psmouse && sudo modeprobe psmous) gets both my mouse (swiftpoint) and trackpad (synaptics) working normally. Unfortunately, it doesn't last long (maybe 15 minutes or so), until it comes back.

By the way, I've just seen in my update manager that I'm about to get a new kernel (2.6.38-13-generic) and a new version of X. I'll install these and see if that changes anything.

If the bug still rears it's ugly head, I will try to do the "restart x-server" workaround, and see if that will work...

Just reporting back that restarting X works for me, and seems to provide a longer time of normal mouse behaviour. I am now about three hours in, and mouse is still working normally.

The exact procedure that worked for me was to reboot, log in, immediately resart X, log in again, immediately restart X again, and then log in one last time.

I have the same bug. Mouse moves but I can't clcik anything.

Th suggestion of #120 helped without restarting X just:

"sudo modprobe -r psmouse"

That's it. I guess it has something to do with the new Kernel 3.5.x or 3.6.x because I have this bug since I installed one of these mainline kernels.

See 165 & 166.

Removing mousetweaks using Synaptic Package Manager, fixed the problem on my new Samsung Q530 laptop. I haven't had the problem for over one month, now (I do allow all updates). Running ubuntu 64 bit with Gnome Classic. If you search on what Mousetweaks does, it is trying to make your computer smarter about a simple function: A MOUSE CLICK! KISS is usually the best engineering way...

I have this sort of problem with 11.04 as well with Mint12 (KDE) after installing anew. Suggestion "sudo rmmod psmouse && sudo modprobe psmouse" doesn't help in my case. In my case I get repetively (and always) rid of this problems with log off and then log on! It seems that any stuff that is "stopped" during logoff prepares for correct mouse operation.

Note: in the case of ingoring left mouse key, sudo evtest /dev/input/event5 (5 in my case) show up response of all mouse events, but left mouse ignored by the desktop.

There is no difference whether I use the mouse directly on an USB port, or via a USB/PS2-adapter pod. The mouse itself is generic simple mouse.

Bug is tracked here for X11: https://bugs.freedesktop.org/show_bug.cgi?id=26213

I suspect there are different bugs mixed here. If you are experiencing this problem and:

- You are running 'nautilus'.
- Maybe you use the 'awesome' window manager.
- 'evtest' actually shows all mouse events.

Then: https://bugs.launchpad.net/ubuntu/+source/awesome/+bug/884255

This bug has been solved for me if of course i was suffering from it :) my symptoms where:

-mouse failing to get focus on various windows
-keyboad alt-tab also not responding
-unity keeps focus
-and other kinds of weird behaviour of the mouse

How? Regular ubuntu update on 09-05-2012.

Thank you Ubuntu

comment on post #181

bug not solved

rebooted and had the issues still

login logout as mentioned before resolves the bug for a period

I have found that using X forwarding with putty is what triggers this condition for me. If I switch to another tty (Alt-Crtrl-F2), I can list the putty processes, kill them, and free X to respond to mouseclicks again.

Same problem for me since I upgraded to 12.04 in April. I can't click anything. I have to ALT+CTRL+DEL, then log out. After logging in a second time, the mouse works again.

My mouse works fine, until I use it to launch something (i.e. I can click the desktop and drag select icons, click the launcher, etc). For instance, if I launch my browser or terminal, I can no longer use the mouse*.
*Sometimes I can click the bar at the top of the window (I can click the task bar area near the time, or minimize the window).

My keyboard still works. I can still press the Start button on my keyboard and open the dash, and type. I just can't click properly! Is there anything like xprop or xwininfo that can tell me what has stolen my mouse? evtest still shows the mouse events - the desktop simply doesn't respond.

I tried adding noapic acpi=off to grub, but then my system won't boot.

Not sure if it's related, but I also experience bug 971748 on every boot. When aptd crashes, I get a windows stating "Could not grab your mouse. A malicious client may be eavesdropping on your session or you may have just clicked a menu or some application just decided to get focus."

I'm on Kubuntu 12.04. I have "noapic acpi=off" in my boot flags. This effects me on two different machines with both the open source FGLRX drivers for my ATI cards.

The exact symptoms are that mouse clicks will sporadically stop working, except that right clicking on some specific application - frequently the KDE taskbar - will make the mouse work normally for one or two clicks.

The problem seems to have gone away after implementing the work around described here: http://forums.fedoraforum.org/showthread.php?t=256841

Specifically, I performed the following steps:

# Create an xorg.conf file.
Xorg -configure
cp /root/xorg.conf.new /etc/X11/xorg.conf

# Disable input device autodetection by adding the following to
# Section "ServerLayout" in the new xorg.conf file:
    Option "AllowEmptyInput" "Off"
    Option "AutoAddDevices" "Off"

# Install the old default keyboard driver since the new
# driver depends on auto-detection.
apt-get install xserver-xorg-input-kbd

For me, the psmouse was the issue on a T420

I had this bug sporadically, too. I cannot reproduce it, though. Usually pressed Ctrl-Alt-F1, logged in on console and killed X. Now I have tried to do the

sudo modprobe -r psmouse && sudo modprobe psmouse

This worked! I am using two mice with Kubuntu 12.04, namely the builtin AlpsPS/2 ALPS DualPoint TouchPad and Logitech Bluetooth Mouse M555b. The problem appeared in different applications, e.g. firefox or when unlocking the screensaver on KDE.

This also happens on my Dell Studio XPS 1640 laptop.

The only workaround that works for me is to close the lid to suspend & repon it. Then the mouse works agian.

Seems to be an old bug;

As it was suggested previously for some kind of logitech mouse you can try to restart this driver:
sudo modprobe -r hid_logitech && sudo modprobe hid_logitech

This is still happening for me, even now in 12.04.1. I've tried EVERY workaround suggest above (and some more fooling with xorg.conf.d stuff) to no avail. Restarting x-server is the only thing that works even temporarily (lasts an indefinite amount of time, then bug resurfaces). Is there really no advance on this OLD and VERY ANNOYING bug? It's a pretty serious issue.

If it helps, this bug is DEFINATELY something to do with the touchpad drivers (I imagine synaptic, as I've got that installed). If touch pad is disabled and an external mouse is used, then after x restart, the external mouse functions fine. It is only when the touchpad is enabled that this bug returns...