GNOME Bugzilla – Bug 431110
crash in Gimmie: klick auf bibliothek
Last modified: 2007-05-03 03:36:40 UTC
What were you doing when the application crashed? klick auf bibliothek 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 Icon Theme: gnome 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 (18 sec old) --------------------- evolution-alarm-notify-Message: Wed Apr 18 21:38:52 2007 alarm-notify.c:368 (alarm_notify_new) - Alarm Notify New alarm-notify.c:304 (alarm_channel_setup) - Channel Setup alarm-notify.c:243 (alarm_notify_init) - Initing Alarm Notify alarm-queue.c:1875 (alarm_queue_init) alarm-queue.c:218 (queue_midnight_refresh) - Refresh at Thu Apr 19 00:00:00 2007 alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/nils/.evolution/calendar/local/system alarm-notify.c:456 (alarm_notify_add_calendar) file:///home/nils/.evolution/calendar/local/system - Calendar Open Async... 0x80a31d0 alarm-notify.c:220 (load_calendars) - Loading Calendar contacts:/// alarm-notify.c:456 (alarm_notify_add_calendar) contacts:/// - Calendar Open Async... 0x80bad20 alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/nils/.evolution/tasks/local/system alarm-notify.c:456 (alarm_notify_add_calendar) file:///home/nils/.evolution/tasks/local/system - Calendar Open Async... 0x80c0080 alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/nils/.evolution/ta -------------------------------------------------- Traceback (most recent call last):
+ Trace 128843
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 ***