Created attachment 890652 [details] This is a gzipped tar file (BUGZILLA_ATTACHMENTS.tar.gz) containing Xorg.0.log, dmesg.out, lspci.out, messages-20140428, and a hardware listing, hardware.2014-04-29.txt (all are "text" files) Description of problem: This problem started immediatly after "upgrading" (clean install) from FC17 to FC19. I switched to FC20 hoping to get rid of the problem - but it didn't help. After starting an X windows session (my default run level is multi-window without X and I start X via "startx") randomly at some point, suddenly the focus becomes "locked" in the current window and there is no way to "break" that lock except by closing the window altogether. Panels, other windows, icons, etc. - or anything and evrything NOT in that window might be visible but clicking on that item does not work - focus stays fixed on the window which has "trapped" it. This may happen 2 minutes after starting the X session or 2 hours. Typicallly the time is more like 60-90 minutes but once I went for 11 hours without it occurring. I have no idea what the trigger causing the problem is. It seems to occur more quickly if I run Firefox, Google Chrome, or Seamonkey. (I don't think that konqueror or rekonq hasten the problem's appearance.) Version-Release number of selected component (if applicable): This same thing has occurred with ALL servers starting (under FC19) with xorg-x11-server-Xorg-1.14.1-4.fc19.x86_64.rpm and continuing up through (under FC20) xorg-x11-server-Xorg-1.14.4-7.fc20.x86_64 How reproducible: Steps to Reproduce: 1.startx 2.Open a few windows (mostly xterms, but an eamil client, a music player, and a few other "random" apps. 3.Continue working. Actual results: At some point minutes or hours later, focus will lock on the current window, and the only way to restore normal operation will be to exit that window/application altogether. Expected results: "Normal opeation" should continue indefinitely. Additional info: I have an Nvidia card. The same thing occurs whether I use the "normal" xorg-x11-drv-nouveau driver or the non-free one from nvidia. FWIW, the problem started while I was using the nouveau driver. I also normally use an IOgear 4-port DVI/USB KVM switch. I thought the problem was connected with the switch. However from testing, it occurs whether the mouse, keyboard, and monitor are connected directly to the computer or indirectly through the KVM switch. The problem has only occurred on one of my boxes here - but I am keeping 2 others back under FC17 out of the fear that the same thing could happen with them as well after upgrading. (Sorry) I kept my old FC17 root disk and putting it back into the machine and booting under FC17 the problem does not occur. Originally with FC19 and now with FC20 it does - every time, sooner or later. Obviously this could be the result of a configuration issue (cockpit error on my part) or of an unusual HW compatibility issue. But as the only "unusual" thing in my system is the KVM switch, and as the problem occurs with or without it, I don't think that's the problem. (I could be wrong, but I can't figure out what the root cause is.) I use a wireless (Logitech) mouse. Replacing it with a different wireless mouse OR with a wired mouse has no effect on the problem. Focus method (selected from System Settings > Window Behavior > Focus > Focus follows mouse - mouse precedence) does not seem to have any effect on the problem (click to focus doesn't change the problem), and selinux appears to be "innocent" for once (the problem occurs whether SELINUX is set to "enforcing," "permissive," or "disabled", and the SELINUXTYPE doesn't make a difference (I've literally tried all of the combinations). I have included a gzipped tar file (BUGZILLA_ATTACHMENTS.tar.gz) containing Xorg.0.log, dmesg.out, lspci.out, messages-20140428, and a hardware listing, hardware.2014-04-29.txt (all files are "text" files).
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.