After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 486430 - crash in Gimmie: I lost network connectiv...
crash in Gimmie: I lost network connectiv...
Status: RESOLVED DUPLICATE of bug 419093
Product: gimmie
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Gimmie Maintainers
Gimmie Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-13 22:01 UTC by fred.fungus
Modified: 2007-10-14 13:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description fred.fungus 2007-10-13 22:01:48 UTC 
What were you doing when the application crashed?
I lost network connectivity and selected the Library tab from gimmie resulting in the demise of gimmie.  This problem occurs now every time I select the Library tab (even with network connectivity restored).


Distribution: Ubuntu 7.04 (feisty)
Gnome Release: 2.18.1 2007-04-10 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.20-16-generic #2 SMP Sun Sep 23 19:50:39 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Mist

Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0
CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0



----------- .xsession-errors (11 sec old) ---------------------
Window manager warning: Log level 8: gtk_paint_arrow: assertion `style->depth == gdk_drawable_get_depth (window)' failed
Window manager warning: Log level 8: gtk_paint_arrow: assertion `style->depth == gdk_drawable_get_depth (window)' failed
Window manager warning: Log level 8: gtk_paint_arrow: assertion `style->depth == gdk_drawable_get_depth (window)' failed
Window manager warning: Log level 8: gtk_paint_arrow: assertion `style->depth == gdk_drawable_get_depth (window)' failed
Window manager warning: Log level 8: gtk_paint_arrow: assertion `style->depth == gdk_drawable_get_depth (window)' failed
Window manager warning: Log level 8: gtk_paint_arrow: assertion `style->depth == gdk_drawable_get_depth (window)' failed
Window manager warning: Log level 8: gtk_paint_arrow: assertion `style->depth == gdk_drawable_get_depth (window)' failed
Window manager warning: Log level 8: gtk_paint_arrow: assertion `style->depth == gdk_drawable_get_depth (window)' failed
Window manager warning: Log level 8: gtk_paint_arrow: assertion `style->depth == gdk_drawable_get_depth (window)' failed
Window manager warning: Log level 8: gtk_paint_arrow: assertion `style->depth == gdk_drawable_get_depth (window)' failed
Window manager warning: Log level 8: gtk_paint_arrow: assertion `style->depth == gdk_drawable_get_depth (window)' failed
Window manager warning: Log level 8: gtk_paint_arrow: assertion `style->depth == gdk_drawable_get_depth (window)' failed
Window manager warning: Log level 8: gtk_paint_arrow: assertion `style->depth == gdk_drawable_get_depth (window)' failed
Window manager warning: Log level 8: gtk_paint_arrow: assertion `style->depth == gdk_drawable_get_depth (window)' failed
Window manager warning: Log level 8: gtk_paint_arrow: assertion `style->depth == gdk_drawable_get_depth (window)' failed
--------------------------------------------------
Gimmie Version: 0.2.7

Traceback (most recent call last):

+ Trace 170040

  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_topicwin.py", line 591 in _compare_item_name 
    cmp((item1.get_name() or "").lower(), (item2.get_name() or "").lower())
UnicodeDecodeError: 'utf8' codec can't decode bytes in position 4-6: invalid data 






Comment 1


H.





          2007-10-14 13:32:44 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 419093 ***