You are not logged in.
Hi I'm getting thousand of lines with errors related to Xsession like these:
-- Logs begin at Tue 2013-05-07 00:24:06 COT. --
May 08 15:55:04 koven /etc/gdm/Xsession[703]: (gnome-shell:824): Clutter-CRITICAL **: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 08 15:55:04 koven /etc/gdm/Xsession[703]: (gnome-shell:824): Clutter-CRITICAL **: clutter_text_get_editable: assertion `CLUTTER_IS_TEXT (self)' failed
May 08 15:55:04 koven /etc/gdm/Xsession[703]: (gnome-shell:824): Clutter-CRITICAL **: clutter_text_get_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 08 15:55:04 koven /etc/gdm/Xsession[703]: (gnome-shell:824): Clutter-CRITICAL **: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 08 15:55:10 koven /etc/gdm/Xsession[703]: (gnome-shell:824): Clutter-CRITICAL **: clutter_text_get_editable: assertion `CLUTTER_IS_TEXT (self)' failed
May 08 15:55:10 koven /etc/gdm/Xsession[703]: (gnome-shell:824): Clutter-CRITICAL **: clutter_text_get_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 08 15:55:10 koven /etc/gdm/Xsession[703]: (gnome-shell:824): Clutter-CRITICAL **: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 08 15:55:10 koven /etc/gdm/Xsession[703]: (gnome-shell:824): Clutter-CRITICAL **: clutter_text_get_editable: assertion `CLUTTER_IS_TEXT (self)' failed
May 08 15:55:10 koven /etc/gdm/Xsession[703]: (gnome-shell:824): Clutter-CRITICAL **: clutter_text_get_text: assertion `CLUTTER_IS_TEXT (self)' failed
.....
.....
.....
and many more. I just wanted to know if I can disable Xsession errors or gdm errors because logs are so huge, and I only see some errors I don't want to be fixed. Journald still is so young to find any information.
i don't know if this is the place to post this problem. If not be free to move.
BR
Last edited by Koven (2013-07-04 13:51:20)
Offline
I don't know if Gnome configuration permits different log levels; maybe you can search infos on that, first.
Concerning systemd journald, it is possible to change the log level value in '/etc/systemd/journald.conf'.
It is the 'MaxLevelStore' parameter; it defaults to debug which is the highest level; you could try to choose a lower value among the 8 possible choices:
emerg, alert, crit, err, warning, notice, info, debug (see 'man journald.conf' for details)
But it would be better to act at the Gnome level, if it is possible.
Last edited by berbae (2013-05-09 20:07:10)
Offline
As gdm now writes its output in the systemd journal by default, instead of the session.log file,
you can choose to return to the previous behavior by rebuilding the gdm package and tell it to not use the systemd journal.
See https://bbs.archlinux.org/viewtopic.php … 3#p1270403
Last edited by berbae (2013-05-10 09:35:54)
Offline
I really don't like to modify default behaviour in gnome, so I Think there will be another solution for this issue. If anyone knows thanks for leting me know.
Berbae thanks for your solution ,
I'd like to know a workaround to solve this.
Offline
Instead of hiding the error message from the log I would like to know the reasons for this message to appear. What does it mean and what is the problem?
Mai 26 12:03:00 thinkpad /etc/gdm/Xsession[834]: (gnome-shell:948): Clutter-CRITICAL **: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed
Mai 26 12:03:00 thinkpad /etc/gdm/Xsession[834]: (gnome-shell:948): Clutter-CRITICAL **: clutter_text_get_text: assertion `CLUTTER_IS_TEXT (self)' failed
Mai 26 12:03:00 thinkpad /etc/gdm/Xsession[834]: (gnome-shell:948): Clutter-CRITICAL **: clutter_text_get_editable: assertion `CLUTTER_IS_TEXT (self)' failed
Mai 26 12:03:00 thinkpad /etc/gdm/Xsession[834]: (gnome-shell:948): Clutter-CRITICAL **: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed
Mai 26 12:03:00 thinkpad /etc/gdm/Xsession[834]: (gnome-shell:948): Clutter-CRITICAL **: clutter_text_get_text: assertion `CLUTTER_IS_TEXT (self)' failed
Mai 26 12:03:00 thinkpad /etc/gdm/Xsession[834]: (gnome-shell:948): Clutter-CRITICAL **: clutter_text_get_editable: assertion `CLUTTER_IS_TEXT (self)' failed
Mai 26 12:03:00 thinkpad /etc/gdm/Xsession[834]: (gnome-shell:948): Clutter-CRITICAL **: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed
Mai 26 12:03:00 thinkpad /etc/gdm/Xsession[834]: (gnome-shell:948): Clutter-CRITICAL **: clutter_text_get_text: assertion `CLUTTER_IS_TEXT (self)' failed
Offline
tl;tr Debugging Gnome extensions is hard
Having the same issues here starting about a month ago.
I don't expect changing the log-levels will help. This notice is marked CRTICAL.
As for the cause of this issue:
I still expect one of my dozen extensions to blame. I found this hard to debug. The process is gnome-shell and there doesn't seem to be a backtrace of sorts leading to a compoent. I tried sysprof [1] from the Gnome debug help page [2]. The Looking Glass help page [3] points to ~/.cache/gdm/session.log for debugging extensions but I found no relevant issues both in the current as in the saved log.
More down to earth is disabling the extensions one by one. I made a mental error there. You'd want to restart gdm or logout/login after each disabled extension since you're still stuck with the error notice even after you've disabled extensions.
Anway, that's what I'm doing now, running the system without any extension and so far no errors. Once I found what I think is the culprit I will notify this topic and shake some developers.
[1] http://sysprof.com/
[2] https://live.gnome.org/GnomeShell/Debugging
[3] https://live.gnome.org/GnomeShell/LookingGlass
Last edited by foppe (2013-06-20 22:26:56)
Offline
Most likely Sensors [1]
[1] https://extensions.gnome.org/extension/ … indicator/
Epilogue:
I filed a bugreport in Github [1] which led to some clues that made me believe the origin of the bug lies in a previous AUR version of sensors [2].
For me this issue is now SOLVED
[1] https://aur.archlinux.org/packages/gnom … n-sensors/
[2] https://github.com/xtranophilist/gnome- … /issues/83
Last edited by foppe (2013-06-22 02:04:32)
Offline
Thanks fope i didn't even realize I'd installed that extension from AUR and not from extensions webpage. Thanks for your time and I'll mark this topic as solved.
Offline