Description of problem: This might be an old problem from F18 or even earlier but I am seeing tons of messages like: Jul 09 15:18:27 localhost.localdomain /etc/gdm/Xsession[4379]: (gnome-shell:4559): Clutter-CRITICAL **: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed Jul 09 15:18:27 localhost.localdomain /etc/gdm/Xsession[4379]: (gnome-shell:4559): Clutter-CRITICAL **: clutter_text_get_editable: assertion `CLUTTER_IS_TEXT (self)' failed in system logs when running gnome-shell with some extensions added. These messages don't seem useful - since they don't continue enough information to track down the cause anyway but the quantity of them causes my desktop to stall regularly which is highly annoying. Steps to Reproduce: 1. install gnome-shell with extensions like Weather, Sensors, etc 2. activate screenlock (not sure if this is necessary but it seems trigger this faster) 3. run: journalctl -b | grep Clutter-CRITICAL | wc -l Actual results: 3. I currently have 350764 in my journal log on my f19 laptop. Sometimes the msgs flood the log fast enough to stall the desktop for one or more seconds. Expected results: No spamming of messages! Additional info: I am pretty sure I also saw this with F18. The messages seem to do no good.
I get nothing. # journalctl -b | grep Clutter-CRITICAL | wc -l 0 Do the messages go away if you disable all the extensions?
Jens, see bug 957363. Try to disable sensors extension, and then perhaps close this bug as a dupe.
*** Bug 986772 has been marked as a duplicate of this bug. ***
(In reply to Peter Robinson from comment #1) > Do the messages go away if you disable all the extensions? I think so, but that is not an acceptable solution. (In reply to Michal Nowak from comment #2) > Try to disable sensors extension, and then perhaps > close this bug as a dupe. I don't think it is only the sensors extension. The error message itself is not even useful. Anyway I find it hard to use Gnome 3 in production alas because of its resource heaviness, this issue, and hence having to restart it regularly (twice a week or more?), which is sad because I actually like it and think it is now the best desktop UI, but I have to still use Mate to have a fast, light, stable desktop. :-(
I see this as well with Cinnamon desktop. It looks like this issue and bug 957363 and bug 1008071 are all the same issue? I don't have the sensors extension enabled. (Or, indeed, any extension, at the moment.) I don't know what triggers this. I wonder if it is unlocking my desktop. By habit, I lock my desktop every time I walk away, so I unlock it often. The three repeated lines going into /var/log/messages and into the systemd journal don't give enough information to begin to diagnose anything, so should they be logged at all?
FYI, in one weekly /var/log/messages, I see this message 24,177,649 times. I noticed it because every daily tripwire report reported more and more log files for journald, and because eventually the messages started coming so fast that the desktop effectively froze. It took about 20 minutes to get to a text console, look at the spam in /var/log/messages, figure out it was my cinnamon desktop session, and kill it. At which point I rebooted. (I probably only needed to kill my cinnamon desktop session.)
OK, last comment. For anyone else that comes across this, a quick workaround when you notice this flood of messages is one I discovered in bug 957363 comment 24: Press Alt-F2 and enter the command "r" (and hit ENTER) and the flood stops. Of course, it will just start again later. If I can figure out what the trigger is, I'll update this bugzilla. But at least you don't have to reboot or even log out to stop the flood of messages. Today, when I did the workaround, I was getting just under 100 lines per second of this in my logs. I've seen it be over 1300 lines per second. I'm sure it's been higher than that. (I haven't looked in great detail.) Do these log messages provide any value at all?
Five days later and this happened again. No obvious trigger. How can I begin to figure out why this is happening? Does this message come from one of the clutter libraries? That is, one of these that I have intalled? clutter-gst2-2.0.4-1.fc19.x86_64 clutter-gtk-1.4.4-1.fc19.x86_64 clutter-1.14.4-4.fc19.x86_64
I see this with Cinnamon as well. clutter.x86_64 1.16.2-4.fc20 clutter-gst2.x86_64 2.0.10-1.fc20 clutter-gtk.x86_64 1.4.4-3.fc20 @Edward, thanks for the Alt-F2, r trick. Worked.
confirmed in Cinnamon... very annoying
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.