Created attachment 851889 [details] The mouse has been moved to corner, activities menu not open Description of problem: I have been experiencing a problem where after a while working in a GNOME session some strange things begin to happen and make my workstation almost unusable. I believe this is a gnome-shell bug, but it may be elsewhere, I am not an expert on the relationship between GNOME components. 1. GNOME Shell does not show the activities menu when the mouse is moved to the upper left corner (see screenshot) 2. GNOME Shell keyboard shortcuts do not work (Super key, ALT+F2, etc) 3. Mouse clicks seem to go unnoticed. i.e. I can't click on buttons, can't change tabs, browser links etc 4. A window that is not raised seems to have focus (see screenshot) 5. Alt+TAB, Alt+~ still switch windows, tab still changes focus among widgets on screen 6. Sometimes it all starts working again, enough that I can Alt+F2, "r", ENTER which seems to help but not fix the problems. Version-Release number of selected component (if applicable): GNOME Shell 3.8.4 $ gnome-shell --version GNOME Shell 3.8.4 $ rpm -q gnome-shell gnome-shell-3.8.4-3.fc19.x86_64 How reproducible: Login to GNOME shell, start working... Additional info: $ uname -a Linux alan-laptop 3.12.7-200.fc19.x86_64 #1 SMP Fri Jan 10 15:32:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ modinfo nvidia | head -n11 filename: /lib/modules/3.12.7-200.fc19.x86_64/extra/nvidia-304xx/nvidia.ko alias: char-major-195-* version: 304.116 supported: external license: NVIDIA alias: pci:v000010DEd00000E00sv*sd*bc04sc80i00* alias: pci:v000010DEd00000AA3sv*sd*bc0Bsc40i00* alias: pci:v000010DEd*sv*sd*bc03sc02i00* alias: pci:v000010DEd*sv*sd*bc03sc00i00* depends: i2c-core vermagic: 3.12.7-200.fc19.x86_64 SMP mod_unload 01:00.0 VGA compatible controller: NVIDIA Corporation GK107GLM [Quadro K2000M] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device 21f6 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 16 Region 0: Memory at f2000000 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at e0000000 (64-bit, prefetchable) [size=256M] Region 3: Memory at f0000000 (64-bit, prefetchable) [size=32M] Region 5: I/O ports at 5000 [size=128] [virtual] Expansion ROM at f3080000 [disabled] [size=512K] Capabilities: <access denied> Kernel driver in use: nvidia $ rpm -qa xorg-x11-drv-nvidia\* xorg-x11-drv-nvidia-304xx-304.116-3.fc19.x86_64 xorg-x11-drv-nvidia-304xx-libs-304.116-3.fc19.x86_64 $ Xorg -version X.Org X Server 1.14.4 Release Date: 2013-10-31 X Protocol Version 11, Revision 0 Build Operating System: 3.10.9-200.fc19.x86_64 Current Operating System: Linux alan-laptop 3.12.7-200.fc19.x86_64 #1 SMP Fri Jan 10 15:32:06 UTC 2014 x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-3.12.7-200.fc19.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap rd.md=0 rd.dm=0 rd.luks=0 vconsole.keymap=us rd.lvm.lv=fedora/root rhgb quiet nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off LANG=en_US.UTF-8 Build Date: 13 November 2013 07:28:45AM Build ID: xorg-x11-server 1.14.4-3.fc19 Current version of pixman: 0.30.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version.
Created attachment 851890 [details] Terminal is raised, firefox seems to have focus Terminal is raised but firefox seems to have focus, mouse movement across tabs brings up tooltips.
I have a similar problem on GNOME Shell 3.6.3.1, gnome-shell-3.6.3.1-2.fc18.i686. All the latest upadates are installed. The mouse becomes partly unresponsive when over an application's window but I am still able to use the mouse to choose applications from the menu appearing when "Alt+Tab" is issued. I can still click to choose which widow I want to focus on when viewing all the windows on one screen but when selecting the appication window no mouse action is sent to that application. /var/log/messages is full of "Unknown key" type messages. All goes back to normal after killin Xorg. (not the most elegant of solutions, but it does the trick and skips me rebooting which is most important) Keybord is still working throughout so I can close and save all my work sessions before killing Xorg, but would rather it did not happen at all :) Sample from /var/log/messages before restarting Xorg: Jan 28 10:22:15 localhost dbus-daemon[631]: dbus[631]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Jan 28 10:22:15 localhost dbus[631]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Jan 28 10:22:15 localhost dbus-daemon[631]: dbus[631]: [system] Successfully activated service 'org.freedesktop.PackageKit' Jan 28 10:22:15 localhost dbus[631]: [system] Successfully activated service 'org.freedesktop.PackageKit' Jan 28 10:25:05 localhost kernel: [93892.446777] atkbd serio0: Unknown key pressed (translated set 2, code 0xa8 on isa0060/serio0). Jan 28 10:25:05 localhost kernel: [93892.446786] atkbd serio0: Use 'setkeycodes e028 <keycode>' to make it known. Jan 28 10:27:27 localhost kernel: [94034.183832] atkbd serio0: Unknown key pressed (translated set 2, code 0xa8 on isa0060/serio0). Jan 28 10:27:27 localhost kernel: [94034.183846] atkbd serio0: Use 'setkeycodes e028 <keycode>' to make it known. Jan 28 10:30:10 localhost kernel: [94197.825126] atkbd serio0: Unknown key pressed (translated set 2, code 0xa8 on isa0060/serio0). Jan 28 10:30:10 localhost kernel: [94197.825135] atkbd serio0: Use 'setkeycodes e028 <keycode>' to make it known. Jan 28 10:30:22 localhost kernel: [94209.812568] atkbd serio0: Unknown key pressed (translated set 2, code 0xa8 on isa0060/serio0). Jan 28 10:30:22 localhost kernel: [94209.812577] atkbd serio0: Use 'setkeycodes e028 <keycode>' to make it known. Jan 28 10:31:48 localhost kernel: [94296.124112] atkbd serio0: Unknown key pressed (translated set 2, code 0xa6 on isa0060/serio0). Jan 28 10:31:48 localhost kernel: [94296.124120] atkbd serio0: Use 'setkeycodes e026 <keycode>' to make it known. Jan 28 10:31:57 localhost kernel: [94304.219478] atkbd serio0: Unknown key pressed (translated set 2, code 0xa8 on isa0060/serio0). Jan 28 10:31:57 localhost kernel: [94304.219487] atkbd serio0: Use 'setkeycodes e028 <keycode>' to make it known. Jan 28 10:34:20 localhost kernel: [94448.172009] atkbd serio0: Unknown key pressed (translated set 2, code 0xa8 on isa0060/serio0). Jan 28 10:34:20 localhost kernel: [94448.172018] atkbd serio0: Use 'setkeycodes e028 <keycode>' to make it known. Jan 28 11:53:37 localhost NetworkManager[856]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.75': no such name Jan 28 11:53:37 localhost NetworkManager[856]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.75': no such name Jan 28 11:53:37 localhost gdm-simple-slave[737]: WARNING: Child process 797 was already dead. Jan 28 11:53:37 localhost gdm-simple-slave[737]: WARNING: Child process 797 was already dead. Jan 28 11:53:37 localhost gdm-simple-slave[737]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed Jan 28 11:53:37 localhost gdm-simple-slave[737]: GLib-GObject-CRITICAL: g_object_unref: assertion `object->ref_count > 0' failed Jan 28 11:53:37 localhost gdm[636]: gdm-binary[636]: WARNING: GdmDisplay: display lasted 0.002449 seconds Jan 28 11:53:37 localhost gdm-binary[636]: WARNING: GdmDisplay: display lasted 0.002449 seconds Jan 28 11:53:37 localhost dbus-daemon[631]: dbus[631]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.3" (uid=0 pid=636 comm="/usr/sbin/gdm-binary ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.204" (uid=0 pid=30863 comm="/usr/libexec/gdm-simple-slave --display-id /org/gn") Jan 28 11:53:37 localhost dbus[631]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.3" (uid=0 pid=636 comm="/usr/sbin/gdm-binary ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.204" (uid=0 pid=30863 comm="/usr/libexec/gdm-simple-slave --display-id /org/gn") Jan 28 11:53:38 localhost gdm-simple-slave[30863]: WARNING: Failed to give slave programs access to the display. Trying to proceed. Jan 28 11:53:38 localhost systemd-logind[622]: New session 31 of user gdm. Jan 28 11:53:38 localhost systemd-logind[622]: Linked /tmp/.X11-unix/X1 to /run/user/42/X11-display. Jan 28 11:53:37 localhost NetworkManager[856]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.75': no such name Jan 28 11:53:37 localhost NetworkManager[856]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.75': no such name Jan 28 11:53:37 localhost gdm-simple-slave[737]: WARNING: Child process 797 was already dead. Jan 28 11:53:37 localhost gdm-simple-slave[737]: WARNING: Child process 797 was already dead. Jan 28 11:53:37 localhost gdm-simple-slave[737]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed Jan 28 11:53:37 localhost gdm-simple-slave[737]: GLib-GObject-CRITICAL: g_object_unref: assertion `object->ref_count > 0' failed Jan 28 11:53:37 localhost gdm[636]: gdm-binary[636]: WARNING: GdmDisplay: display lasted 0.002449 seconds Jan 28 11:53:37 localhost gdm-binary[636]: WARNING: GdmDisplay: display lasted 0.002449 seconds Jan 28 11:53:37 localhost dbus-daemon[631]: dbus[631]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.3" (uid=0 pid=636 comm="/usr/sbin/gdm-binary ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.204" (uid=0 pid=30863 comm="/usr/libexec/gdm-simple-slave --display-id /org/gn") Jan 28 11:53:37 localhost dbus[631]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.3" (uid=0 pid=636 comm="/usr/sbin/gdm-binary ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.204" (uid=0 pid=30863 comm="/usr/libexec/gdm-simple-slave --display-id /org/gn") Jan 28 11:53:38 localhost gdm-simple-slave[30863]: WARNING: Failed to give slave programs access to the display. Trying to proceed. Jan 28 11:53:38 localhost systemd-logind[622]: New session 31 of user gdm. Jan 28 11:53:38 localhost systemd-logind[622]: Linked /tmp/.X11-unix/X1 to /run/user/42/X11-display.
Something similar on F20 with all updates since ~ 1 week ago Also, when mouse over terminal or terminator, url higligh doesn't work so I can't click, or even select at it. Mouse is like a cursor instead of arrow or viceversa on areas where it should be changing. Sometimes gnome-shell --replace mitigates for a few minutes or the whole session this issue, but suspending and restoring laptop makes it happen again most of the time.
The only change that I've been checking is adding a monitor (FHD) in vertical mode (rotate 90º degrees), but it makes it very difficult to use the computer with the mouse behaving that way. Is there any data that could be provided to better diagnose this issue? Regards
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.