GNOME Bugzilla – Bug 441722
crash in Gimmie: Trying to close it. Tha...
Last modified: 2007-08-30 23:47:03 UTC
What were you doing when the application crashed? Trying to close it. Thank god it crashed i felt trapped by it. Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks-DarkOrange Icon Theme: Human 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 --------------------- *** Setting source: <RecentAggregate object (gimmie+gimmie_base+Item) at 0x8 ** (gimmie:16286): WARNING **: IPP request failed with status 1280 ** (gimmie:16286): WARNING **: IPP request failed with status 1280 /usr/lib/python2.5/site-packages/gimmie/gimmie_topicwin.py:579: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal cmp(item1.get_name().lower(), item2.get_name().lower()) Traceback (most recent call last):
+ Trace 136375
cmp(item1.get_name().lower(), item2.get_name().lower())
/home/conor/.themes/Clearlooks-DarkOrange/gtk-2.0/gtkrc:58: Clearlooks configuration option "sunkenmenu" is not supported and will be ignored. /home/conor/.themes/Clearlooks-DarkOrange/gtk-2.0/gtkrc:59: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored. /home/conor/.themes/Clearlooks-DarkOrange/gtk-2.0/gtkrc:60: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored. /home/conor/.themes/Clearlooks-DarkOrange/gtk-2.0/gtkrc:61: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. -------------------------------------------------- Traceback (most recent call last):
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 ***