After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 678798 - gnome shell irresponsive to mouse clicks
gnome shell irresponsive to mouse clicks
Status: RESOLVED DUPLICATE of bug 679832
Product: gnome-shell
Classification: Core
Component: general
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
Depends on:
Reported: 2012-06-25 16:21 UTC by Ernest
Modified: 2012-12-14 14:20 UTC
See Also:
GNOME target: ---
GNOME version: ---

Screenshot of irresponsive gnome-shell (133.70 KB, image/png)
2012-11-19 08:01 UTC, Sander de Leeuw

Description Ernest 2012-06-25 16:21:21 UTC
At random (?) when starting gnome shell, can move the pointer with the mouse but there is no response to mouse clicks of any kind nor to hot corner. As I am not used to work with hotkeys, didn't try to disable extensions to test; just went to the console, /etc/init.d/gdm3 restart and it is solved.

Debian testing updated as per mirrors at 2012-06-25 17:21:51
Linux kernel 3.2.0-2-amd64
Xorg (1.12.2 RC 2)
GNOME 3.4.2

Reproducibility: happened two times in last week; I usually [re]start GNOME about twice a day -> 14% of shell starts.
Comment 1 André Klapper 2012-06-25 16:54:29 UTC
Just to clarify: Is this about touchscreen or "normal" mouse?
Was there a recent kernel update?
Comment 2 Ernest 2012-06-25 20:04:49 UTC
Real mouse, with tail.
Yes, as there is an imminent freeze these days they are a lot of updates in debian testing, frequently involving kernel.
Comment 3 André Klapper 2012-06-25 20:07:43 UTC
Asked as my touchscreen recently misinterpreted clicks, it both came and went away with kernel updates (though that's the 3.4 kernel).

I wonder if "evtest" can also provide some info here, but maybe I'm wrong.
Comment 4 Ernest 2012-06-26 09:44:21 UTC
Once again.

# dpkg -l linux-image* | grep ii
ii  linux-image-3.2.0-2-amd64                3.2.20-1                           Linux 3.2 for 64-bit PCs
ii  linux-image-amd64                        3.2+44                             Linux for 64-bit PCs (meta-package)
Comment 5 Sander de Leeuw 2012-11-19 08:01:11 UTC
Created attachment 229339 [details]
Screenshot of irresponsive gnome-shell
Comment 6 Sander de Leeuw 2012-11-19 08:01:27 UTC
I have the same problem as Ernest. Sometimes after starting or restarting (ALT-F2 r) gnome-shell, my desktop appears but is irresponsive to mouse clicks.

I managed to create a screenshot. Notice that my user's name is not displayed on the top right of the screen, and the network indicator shows disconnected state. When gnome-shell starts up properly, my user's name is displayed and network indicator shows connect state.

When gnome-shell is irresponsive I can switch to the console using CTRL+ALT+F1, login as the same user and restart gnome-shell with the following command: killall -9 gnome-shell. Gnome-Shell will restart and everything works fine afterwards.

I have installed Debian Wheezy for a couple of weeks on my personal desktop, personal laptop and business laptop, and the same issue occurs on all three systems.
Comment 7 Sander de Leeuw 2012-11-20 11:42:11 UTC
I have found related information here:

Seems Debian has two different bug tracking systems... The same bug number in leads to some other bug.
Comment 8 Ernest 2012-11-23 11:37:11 UTC
After reading Sander's post, I payed attention a couple of times the issue occured this week and can confirm that the screen state is as he reports: network indicator disconnected, user's name not displayed in the top right corner.
Comment 9 Sander de Leeuw 2012-11-27 20:13:37 UTC
I added more information to the bug report here:

Comment 10 Sander de Leeuw 2012-12-01 23:07:56 UTC
Provided patched version of gnome-shell for testing purposes:

Comment 11 Sander de Leeuw 2012-12-14 13:39:25 UTC
This bug has been fixed in unstable:

Perhaps somebody can update the status of this report
Comment 12 Cosimo Cecchi 2012-12-14 14:20:02 UTC
Reading the downstream bug report, it turned out this is another occurrence of bug 679832.

*** This bug has been marked as a duplicate of bug 679832 ***