GNOME Bugzilla – Bug 502907
crash in Gimmie: opened library typed s
Last modified: 2008-03-14 12:11:57 UTC
What were you doing when the application crashed? opened library typed s Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Tango 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 --------------------- <gtk.gdk.Pixbuf object at 0x9f8500 (GdkPixbuf at 0xce3ad0)> <gtk.gdk.Pixbuf object at 0x9f8500 (GdkPixbuf at 0xcd58a0)> <gtk.gdk.Pixbuf object at 0x9f8500 (GdkPixbuf at 0xce39e0)> <gtk.gdk.Pixbuf object at 0x9f8500 (GdkPixbuf at 0xbe32d0)> <gtk.gdk.Pixbuf object at 0x9f8500 (GdkPixbuf at 0xbe3400)> <gtk.gdk.Pixbuf object at 0x9f8500 (GdkPixbuf at 0xbe3770)> <gtk.gdk.Pixbuf object at 0x9f8500 (GdkPixbuf at 0xce3a80)> <gtk.gdk.Pixbuf object at 0x9f8500 (GdkPixbuf at 0xbe3400)> <gtk.gdk.Pixbuf object at 0x9f8500 (GdkPixbuf at 0xbe3630)> <gtk.gdk.Pixbuf object at 0x9f8500 (GdkPixbuf at 0xbe36d0)> <gtk.gdk.Pixbuf object at 0x9f8500 (GdkPixbuf at 0xbe3720)> <gtk.gdk.Pixbuf object at 0x9f8500 (GdkPixbuf at 0xce3990)> <gtk.gdk.Pixbuf object at 0x9f8500 (GdkPixbuf at 0xbc5190)> <gtk.gdk.Pixbuf object at 0x9f8500 (GdkP (PySwitcher.py:6467): Wnck-CRITICAL **: update_client_list: assertion `reentrancy_guard == 0' failed -------------------------------------------------- Gimmie Version: 0.2.8 Traceback (most recent call last):
+ Trace 181474
cmp((item1.get_name() or "").lower(), (item2.get_name() or "").lower())
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 ***