GNOME Bugzilla – Bug 450799
crash in Gimmie: trying to access "Recent...
Last modified: 2007-09-08 22:10:43 UTC
What were you doing when the application crashed? trying to access "Recently Used Programs" 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: Mist Icon Theme: Crux 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 (174 sec old) --------------------- alarm-notify.c:337 (alarm_msgport_replied) - 0x80da7e0: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/devil/.evolution/tasks/local/system - Calendar Status 0 alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80c5378: Received at thread b45ffb90 alarm-queue.c:2008 (alarm_queue_add_async) - 0x80c3350 alarm-queue.c:560 (load_alarms_for_today) - From Mon Jun 25 14:37:18 2007 to Mon Jun 25 14:37:18 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80c5378: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/devil/.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) - 0x80cbe40: ** (gnome-cups-icon:5031): WARNING **: Could not start the printer tray icon, because the CUPS server could not be contacted. -------------------------------------------------- Traceback (most recent call last):
+ Trace 143482
icon_size = self._set_item(item, iter, store)
icon = item.get_icon(icon_size)
found = gnomedesktop.find_icon(icon_theme, self.icon_name, icon_size, 0)
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 415965 ***