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 712199 - Everything becomes unresponsive when expanding a notification
Everything becomes unresponsive when expanding a notification
Status: RESOLVED DUPLICATE of bug 711694
Product: gnome-shell
Classification: Core
Component: general
3.10.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2013-11-13 09:02 UTC by Mathieu Bridon
Modified: 2013-11-18 07:48 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mathieu Bridon 2013-11-13 09:02:56 UTC
When a notification comes, if I move the mouse over it to expand it, then everything becomes unresponsive.

I can't switch windows any more with the mouse, keyboard input is ignored,...

All I can still do is click on the elements of GNOME Shell. For example, if I click on the time, then the calendar/clock menu opens itself fine, same for the status menu.

Sending a HUP to the GNOME Shell process to restart it (I can't run alt+f2 any more) solves the issue...

... until I move the mouse over the next notification.

I can reproduce 100% of the time.

This is with gnome-shell-3.10.1-2.fc20.x86_64
Comment 1 Mathieu Bridon 2013-11-18 07:25:14 UTC
A bit more details: it seems to not happen 100% of the time as I initially thought.

It's just incredibly easy to reproduce it with chat (Empathy) notifications.

However, I have so far never had it with hexchat notifications.

Not sure what the difference between these two is, though.
Comment 2 Jasper St. Pierre (not reading bugmail) 2013-11-18 07:48:35 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

(In reply to comment #1)
> A bit more details: it seems to not happen 100% of the time as I initially
> thought.
> 
> It's just incredibly easy to reproduce it with chat (Empathy) notifications.
> 
> However, I have so far never had it with hexchat notifications.
> 
> Not sure what the difference between these two is, though.

The text entry is the difference...

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