Bug 494233
Summary: | Mouse loses ability to select anything | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Joshua Rosen <bjrosen> | ||||
Component: | xorg-x11-server | Assignee: | Peter Hutterer <peter.hutterer> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 10 | CC: | mcepl, xgl-maint | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2009-05-05 00:31:13 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Joshua Rosen
2009-04-05 21:52:01 UTC
It's happen a couple more times, once when using Firefox and once in PAN. Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf, if available) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. We will review this issue again once you've had a chance to attach this information. Thanks in advance. Created attachment 338534 [details]
Xorg.conf
I've uploaded my xorg.conf. I've also disabled NetworkManager. It occurred to me that the problem could be caused by some program capturing the mouse in a model fashion. My first suspect is NetworkManger because it's been behaving so badly with the latest versions. The broke it with the 99-4 release, 99-5 made it work sort of but it doesn't work well. I've been getting this problem more and more frequently today even with very little running. I'm more convinced that this problem is somehow related to NetworkManager or it's applet. I disabled NetworkManager a couple of days ago and I haven't had the problems since. It was happening frequently just before I disabled NetworkManager. It's definitely not NetworkManager, that was a red-herring. I've had the problem again and NetworkManager is disabled. I was accessing a VM via ssh when it happened. I was doing it through Xemacs so when the mouse lost the ability to select anything I was still able to access an Xemacs shell. I killed all of the applets and all the running applications including Evolution and pan. That didn't fix it. An Evolution calender popup appeared which took me out of Xemacs and into the popup, after that I couldn't do anything and had to kill the X-session. you seem to have a synaptics pad and what I think is a logitech wireless mouse. does it happen with both devices or just one of them? when it happens, do you see any click/motion events in xev? If so, please post the output, I'd be interested in the state that is reported. please run http://people.freedesktop.org/~whot/grabtest.c when that happens, this should tell us if there's a stuck grab. I normally have the Synaptics pad disabled, however I did enable it the last time it happened to see if I could get mouse selection to work with it, it didn't help. I also tried pulling out the wireless transponder for the mouse and moving it to another USB port, that didn't fix it either. The only thing that works is to restart X. Right, so it's a server bug then, not a mouse bug. Moving component. I'd still need you to run the grabtest program though to check if it's generally busted of if a particular client doesn't let the mouse go. I haven't been able to compile grabtest. Is there a particular development package I need to install? gcc grabtest.c /tmp/ccEmE4tp.o: In function `main': grabtest.c:(.text+0xe): undefined reference to `XOpenDisplay' grabtest.c:(.text+0x1c): undefined reference to `XOpenDisplay' grabtest.c:(.text+0xb9): undefined reference to `XGrabPointer' grabtest.c:(.text+0xee): undefined reference to `XUngrabPointer' grabtest.c:(.text+0xfc): undefined reference to `XSync' grabtest.c:(.text+0x14d): undefined reference to `XGrabKeyboard' grabtest.c:(.text+0x182): undefined reference to `XUngrabKeyboard' grabtest.c:(.text+0x18b): undefined reference to `XCloseDisplay' grabtest.c:(.text+0x194): undefined reference to `XCloseDisplay' collect2: ld returned 1 exit status /home/bjrosen/tmp> gcc -lX11 -o grabtest grabtest.c When do you want me to run grabtest? Do you want me to run it when the problem occurs? yes. all this program does is to grab the pointer and the keyboard. If this succeeds, it means that the server has an issue where the events get lost. If this fails, it usually means that there is one application currently running that holds a grab. This explains why events aren't delivered as normal - only that application get them. Thanks, I'll run it the next time the problem occurs assuming that it happens when I'm inside of Xemacs (because you can open a shell without a mouse in Xemacs, if I'm in some other program there is no way to run anything else because you can't switch to another application with a keyboard command). I was able to run grabtest after a failure, grabbing pointer failed, grabbing keyboard passed. This time the failure occured when I was away from the system. There as a rsync to a remote system running, as well as Evolution, Xemacs, Firefox, and pan. Firefox was doing one of it's background plugin updates, when I restarted it after logging back in it did a plugin install. I wonder if Firefox was the culprit. I'll try keeping Firefox closed for a while. It's not Firefox, it happened when the only thing I had open was a couple of terminals. I was doing an rsync at the time. Here is another data point, I switched to a wired mouse from a wireless mouse. The frequency of the problem seems to have been reduced but it didn't fix it. I'm now running with F9 instead of F10, I'll let you know if the problem occurs with F9. Looks like the same problem as 494999. *** This bug has been marked as a duplicate of bug 494999 *** |