GNOME Bugzilla – Bug 130156
gDesklets crashes while running idle
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 1 (Yarrow) Package: gDesklets Severity: critical Version: GNOME2.4.0 unspecified Gnome-Distributor: GNOME.Org Synopsis: gDesklets crashes while running idle Bugzilla-Product: gDesklets Bugzilla-Component: core Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: gDesklets core application crashes after approx. 5-10 minutes. Steps to reproduce the crash: 1. install Sensors & Displays 2. wait 3. crash Expected Results: gDesklets should continue to run, possible pointing to and terminating the ill-behaving desklet. How often does this happen? Allways. Additional Information: - Fedora Core 1, Python 2.2.3-1, gDesklets 0.25 (compiled into an RPM using Dag Wieers' .spec file) - I'll add a screenshot of the desklets ; on request, I'll provide the default profile configuration files. ------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-12-29 03:48 ------- The original reporter (Didier.Moens@dmbr.UGent.be) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, gdesklets-maint@bugzilla.gnome.org.
When running gDesklets from a terminal, this error message reproducably surfaces when the application crashes : ** ERROR **: file pango-layout.c: line 2938 (pango_layout_check_lines): assertion failed: (!layout->log_attrs) aborting...
It could be useful to know which desklets you were running at that time.
According to a problem report from the multisync-devel list (http://www.mail-archive.com/multisync-devel@lists.sourceforge.net/msg00184.html), this specific error message is related to thread handling. I suppose this is related to http://gnomesupport.org/forums/viewtopic.php?t=4998 and/or the "Xlib: unexpected async reply" error as posted on the news page ? How can we possibly identify the ill-behaving applets ?
@Martin : battery-gdesklet-0.2.tar.gz CPUTemp-0.1.tar.gz hddtemp-0.1.tar.bz2 Install_Wireless_Sensor-0.2.bin.bz2 LTVariations-0.21.tar psi-battery-0.1.tar.bz2 PsiDisplayPackage-20031028.tar.bz2 PsiSensorPackage-20031028.tar.bz2 psi-wireless-0.1.tar.bz2 rssgrab-0.2.2.tar.bz2 SpeedfreqMon-0.2.tar.gz SysInfo-0.23.tar.bz2 and gdesklets-goodweather-0.3-0.rhfc1.dag gdesklets-starterbar-0.22.1-0.rhfc1.dag As you can notice, after discovering gDesklets yesterday (already running gDeskCal for some time), I'm quite enthousiastic. :) Note #1 : I uploaded a screenshot as an attachment to this bug report; seems it did not get through. Note #2 : running gDesklets from a terminal, I noticed several python tracebacks ; should I report these too ?
Yes, please show us the other tracebacks as well. I guess this really is a duplicate of the Xlib async bug... same origin, other symptoms.
*** This bug has been marked as a duplicate of 130068 ***
Other tracebacks (excerpts from gDesklets execution log in terminal) : 1. [/home/didier/.gdesklets/Displays/psi-displays/variable-border-left.display] Traceback (most recent call last):
+ Trace 42929
sensor = module.new_sensor(args)
def new_sensor(args): return apply(FontSelector, args)
if (len(fontargs) == 1 and " " in fontargs[0]):
'in <string>' requires character as left operand Using spaces to separate font entries is deprecated. Use commas instead. [/home/didier/.gdesklets/Displays/hddtemp/hddtemp.display] [/home/didier/.gdesklets/Displays/psi-displays/meminfo.display] [/home/didier/.gdesklets/Displays/psi-displays/border-bottom-right.display] Unknown tag: metha [/usr/share/gdesklets/Displays/GoodWeather/GoodWeather.display] 2. [/home/didier/.gdesklets/Displays/psi-displays/diskinfo.display] [/usr/share/gdesklets/Displays/StarterBar/starterbar.display] Traceback (most recent call last): File "/usr/share/gdesklets/sensor/Sensor.py", line 129, in __wrap return apply(callback, args) File "./Wireless/__init__.py", line 65, in __update File "./Wireless/__init__.py", line 84, in __parse AttributeError: 'NoneType' object has no attribute 'group' Traceback (most recent call last): File "/usr/share/gdesklets/sensor/Sensor.py", line 129, in __wrap return apply(callback, args) File "./StarterBar/IconSet.py", line 143, in load_icons File "./StarterBar/Icon.py", line 27, in __init__ File "./StarterBar/Icon.py", line 37, in __load_icon File "./StarterBar/DesktopReader.py", line 62, in get_icon File "/usr/lib/python2.2/ConfigParser.py", line 276, in get raise NoOptionError(option, section) ConfigParser.NoOptionError: No option `icon' in section: Desktop Entry [/home/didier/.gdesklets/Displays/psi-displays/border-top-right.display] 3. [/usr/share/gdesklets/Displays/StarterBar/starterbar.display] PROFILE CHANGE didtest Traceback (most recent call last): File "/usr/share/gdesklets/display/Window.py", line 114, in __on_motion self.__display.save_position(new_x, new_y) File "/usr/share/gdesklets/display/Display.py", line 399, in save_position nil, nil, w, h = self.__group.get_geometry() AttributeError: 'Display' object has no attribute '_Display__group' Traceback (most recent call last): File "/usr/share/gdesklets/display/Window.py", line 114, in __on_motion self.__display.save_position(new_x, new_y) File "/usr/share/gdesklets/display/Display.py", line 399, in save_position nil, nil, w, h = self.__group.get_geometry() AttributeError: 'Display' object has no attribute '_Display__group' NOTE : (3.) was repeated several times, and seems to be related to a StarterBar which turned up seemingly empty after a gDesklets restart. 4. Traceback (most recent call last): File "/usr/share/gdesklets/sensor/Sensor.py", line 129, in __wrap return apply(callback, args) File "./StarterBar/IconSet.py", line 143, in load_icons File "./StarterBar/Icon.py", line 27, in __init__ File "./StarterBar/Icon.py", line 37, in __load_icon File "./StarterBar/DesktopReader.py", line 62, in get_icon File "/usr/lib/python2.2/ConfigParser.py", line 276, in get raise NoOptionError(option, section) ConfigParser.NoOptionError: No option `icon' in section: Desktop Entry
*** Bug 130222 has been marked as a duplicate of this bug. ***