GNOME Bugzilla – Bug 461341
crash in Gimmie: I clicked on the "Librar...
Last modified: 2007-08-30 23:54:27 UTC
What were you doing when the application crashed? I clicked on the "Library" icon and Gimmie crashed immediately. I could confirm and repeat the bug after restarting the applet and clicking on the same tab. 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 Thu Jun 7 20:19:32 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Neutronium DeepBlack Icon Theme: OSX 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 (139 sec old) --------------------- to Sat Jul 28 23:02:26 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80ce6a8: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0x80ce6e8: Received at thread b5c50b90 alarm-queue.c:2008 (alarm_queue_add_async) - 0x80d1800 alarm-queue.c:560 (load_alarms_for_today) - From Sat Jul 28 23:02:26 2007 to Sat Jul 28 23:02:26 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80ce6e8: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/fabio/.evolution/memos/local/system - Calendar Status 0 alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80df418: -------------------------------------------------- Traceback (most recent call last):
+ Trace 151252
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 ***