GNOME Bugzilla – Bug 483230
crash in Gimmie: Trying to open Library c...
Last modified: 2007-10-05 20:39:07 UTC
What were you doing when the application crashed? Trying to open Library crashes Gimmie. note: I just installed Gimmie 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: Human-Blue 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 (4557 sec old) --------------------- alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0 alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80cc070: ReceivedWindow manager warning: "" found in configuration database is not a valid value for keybinding "toggle_shaded" Window manager warning: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager. (emerald:6534): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() (emerald:6534): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() CalDAV Eplugin starting up ... (evolution-2.10:6780): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one (evolution-2.10:6780): e-utils-WARNING **: Plugin 'Spamassassin junk plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.0' ** (evolution-2.10:6780): DEBUG: mailto URL command: evolution %s ** (evolution-2.10:6780): DEBUG: mailto URL program: evolution DOUBLE-CLICK: 400 --> -1 THRESHOLD: 8 --> -1 -------------------------------------------------- Traceback (most recent call last):
+ Trace 167606
cmp(item1.get_name().lower(), item2.get_name().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 ***