You are not logged in.
Hi
Most time when clementine or qbittorrent try display notification gnome freezes. Music don't stop plays, mouse cursor is movable, but i can't click anything. keyboard shortcut also don't work. It's started after upgrading to gnome 3.16
Anyone knows what may cause that?
Thank
Last edited by emlug (2015-04-26 12:00:10)
Offline
Just so you don't think you're the only one, I also have this problem and it's very debilitating. I'm not 100% sure this is QT caused, but I see the same behavior in Gnome 3.16 with bad screen freezes on notifications. I've tried all kinds of things to debug this but have not figured out the cause. My principal notifications come from Spotify, Hipchat, and Empathy. The system typically starts up with no freezes on notifications, but once the problem occurs, it will freeze for 45sec-2minutes on any notification from any application, including Empathy, which I don't think has any QT components.
I used Gnome 3.14 without the issue, have been having notification freezes regularly since moving up to 3.16.
I'd love to hear any thoughts anyone has on figuring this out or how to fix.
cheers,
-Ben
Offline
Interesting. I've heard of the gnome not responding to input issue, but I'm not sure if it had yet been linked to notifications. Are you certain that this happens right after a notification? And are you certain (emlug) that it only with Qt apps? Can you switch to a tty while Gnome is in this frozen state? If so, journalctl might say something of interest.
Offline
100% sure the freeze is notification related.
I will attempt a jump to a tty when it happens, however I think it'll fail because keyboard input and mouse clicks all are non-responsive. The clock in the top bar does not increment seconds until the screen unfreezes, which is typically about 45 seconds but can be longer (yesterday I was clocking ~2 minute freezes).
As emlug stated, mouse cursor is movable, but no input from keyboard or mouse clicks gets through.
-Ben
Offline
100% sure the freeze is notification related.
I will attempt a jump to a tty when it happens, however I think it'll fail because keyboard input and mouse clicks all are non-responsive. The clock in the top bar does not increment seconds until the screen unfreezes, which is typically about 45 seconds but can be longer (yesterday I was clocking ~2 minute freezes).
As emlug stated, mouse cursor is movable, but no input from keyboard or mouse clicks gets through.
-Ben
I would file a bug at bugzilla.gnome.org. Another way to view journalctl would be to initiate an SSH session from a remote computer while gnome is frozen.
Offline
I get plugin weirdness after freeze also; those can be fixed normally with Alt+F2 > r > Enter.
date '+%A, %B %d, %Y %T' | pig | figlet | cowsay -n
Offline
It was tricky but finally got some data visible in journalctl. I will open this at bugzilla.gnome.org, but for completeness on the thread, here it is here too:
I see multiple thousand messages in journalctl at the point of freezing. They almost all say something like this:
May 20 15:21:40 bklaas gnome-session[2277]: (gnome-shell:2412): Clutter-CRITICAL **: clutter_text_get_text: assertion 'CLUTTER_IS_TEXT (self)' failed
May 20 15:21:40 bklaas gnome-session[2277]: (gnome-shell:2412): Clutter-CRITICAL **: clutter_text_set_text: assertion 'CLUTTER_IS_TEXT (self)' failed
I also see about 10 of these, and they are the first 10 messages printed on the exact second of the freeze
May 20 15:13:34 bklaas gnome-session[2277]: (gnome-shell:2412): St-CRITICAL **: st_widget_get_theme_node
Offline
bug opened:
https://bugzilla.gnome.org/show_bug.cgi?id=749656
...which took me 15 or so minutes to write because my screen kept freezing due to this bug ![]()
Last edited by mcstayinskool (2015-05-20 21:15:21)
Offline