search

isDipesh / gnome-shell-extension-sensors

Gnome shell extension: Shows CPU temperature, HDD temperature, voltage and fan RPM
https://motorscript.com/gnome-shell-extension-sensors/
161 stars 153 forks source link

assertion `CLUTTER_IS_TEXT (self)' failed #83

Closed Afwas closed 10 years ago

Afwas commented 11 years ago

For some time I have issues with Gnome extensions leading to increasing CPU-activity and temperature rise (laptop). I've tried to find the culprit and it turns out to be the Sensors extension. Logs are cluttered with:

May 08 15:55:04 xxxxx /etc/gdm/Xsession[703]: (gnome-shell:824): Clutter-CRITICAL _: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed May 08 15:55:04 xxxxx /etc/gdm/Xsession[703]: (gnome-shell:824): Clutter-CRITICAL _: clutter_text_get_editable: assertion `CLUTTER_IS_TEXT (self)' failed

either journal or syslog. These contnue after extensions are disabld so only reboot, re-login or restarting GDM solves the issue untiil it returns.One clue of Sensors being the culprit is that the logs are five seconds apart.

See [1] for some more information

System:Arch linux Gome 3.8.[0-3] lm_sensors 3.3.4-1

[1] https://bbs.archlinux.org/viewtopic.php?id=162968

adrianbroher commented 11 years ago

Hello Afwas,

One clue of Sensors being the culprit is that the logs are five seconds apart.

The default is for polling sensors is 15 seconds so I doubt that the statement

I've tried to find the culprit and it turns out to be the Sensors extension.

is true. Did you try some failsafe method to check if the sensors extension is really the source of the problem (uninstalling would come in mind)? Also what is the version of the sensors extension that you have installed and how did you installed it?

Afwas commented 11 years ago

Thanks. Your are really clver asking the right questions.

I remember now I installed sensors from AUR [1] , not te extensions.gnome.org version [2]. That's because at the time sensors wasn't available for Gnome 3.8 on the extensions page. This is v1.3.21.g9571365-1 [installed: 20130530-1] but as I write this I see there ś a new version available. One of the things I was wondering about was why there weren't more users with issues, but me using the AUR version would explain that. BTW this bug has been troubling me for at least over a month.

I will upgrade AUR version and compare the extensions.gnome.org version as well and I will report in this topic if the bug is persistent.

[1] https://aur.archlinux.org/packages/gnome-shell-extension-sensors/ [2] https://extensions.gnome.org/extension/82/cpu-temperature-indicator/

Afwas commented 11 years ago

The good news is that the bug is gone. The bad news is that it's not reproducable. First I upgraded sensors from AUR, leadig to imminent errors. Then I uninstaled the extension and installed the version from extensions.gnome.org. Hooray: no more errors. I then reversed the operation by removing the extension and installing the one from AUR/git. I'm stll waiting for any errors, so this quirk magically disappeared.

I do think the reason of the bug was in a previous version of sensors. Likely one from AUR. The true cause may remain a mistery.

Please mark this bugreport as solved.

adrianbroher commented 11 years ago

Good to hear that the problem is gone for you.

I'm stll waiting for any errors, so this quirk magically disappeared.

Feel free to reopen the bug if the problem occurs again.

genodeftest commented 11 years ago

This bug is still present for some users, see https://bugzilla.redhat.com/show_bug.cgi?id=957363 (Fedora) For some users it is reproduceable by locking and unlocking the screen. I am using lm_sensors 3.3.3-3.

I tracked this down to the sensors extension by enabling just one extension at a time, restarting gnome shell, locking the screen and unlocking it again.

adrianbroher commented 11 years ago

For some users it is reproduceable by locking and unlocking the screen.

I'm using Fedora 19 and can confirm the problem. (Actually the described behaviour annoys me since I have installed Fedora a few days ago but I didn't investigate it and haven't thought that this extension could be the cause ;) ).

Also the first comment gives finally a hint what is actually wrong with this. I'm trying to fix this the next days.

StefanescuCristian commented 11 years ago

Archlinux here, gnome-shell 3.8.3, the bug is still present.

kparal commented 11 years ago

Fedora 19, same problem. The error messages are printed out several times per second, making my logs huge. The desktop responses are slowed down. After disabling Sensors and re-logging, the problem is gone.

I don't know where to find out the version of this extension, but it's the most recent one installed from extensions.gnome.org.

I can reproduce it easily by installing the extension and then locking and unlocking the screen.

timgabets commented 11 years ago

Hi, I experienced the same problem with "assertion `CLUTTER_IS_TEXT (self)' failed". My solution to get rid with this was rebuilding lm_sensors and recompiling kernel with I2C_CHARDEV enabled (compiled as module). Please also check that your lm_sensors service is running (systemd enable lm_sensors), and i2c modules are loaded.

Hope this will help.

timgabets commented 11 years ago

Ooops, my mistake, the bug still exists, and it is not looks like it is a problem with Sensorss extension. Checking now.

smoebody commented 10 years ago

same for me. no sensors-extension but same error flood. fedora 19 + gnome 3.8 and the following extensions. lets nail it down and file a bug report.

from ~/.local/share/gnome-shell/extensions: caffeine@patapon.info impatience@gfxmonk.net insensitivetray@tovotu.de Pulse-Audio-Shortcuts@l300lvl.tk topIcons@adel.gadllah@gmail.com windowoverlay-icons@sustmidown.centrum.cz

from /usr/share/gnome-shell/extensions: GPaste@gnome-shell-extensions.gnome.org systemMonitor@gnome-shell-extensions.gcampax.github.com user-theme@gnome-shell-extensions.gcampax.github.com weather-extension@xeked.com

jh-dwolla commented 10 years ago

It seems this same, or at least very similar, issue was fixed in another gnome plugin repo recently:

https://github.com/Chousuke/gnome-shell-extension-transmission-daemon/tree/clutter-fix

genodeftest commented 10 years ago

So https://github.com/xtranophilist/gnome-shell-extension-sensors/blob/master/src/extension.js#L31 and https://github.com/xtranophilist/gnome-shell-extension-sensors/blob/master/src/extension.js#L32 may be called with empty labels. Don't know if that helps.

adrianbroher commented 10 years ago

The reported error messages are gone for me with the newest HEAD on master and gnome-3.8 branch. If the problem still persists for you feel free to reopen the bug.