GNOME Bugzilla – Bug 491253
crash in Gimmie: Opening an Evolution ema...
Last modified: 2007-10-29 15:27:35 UTC
What were you doing when the application crashed? Opening an Evolution email attachment in Archive Manager. 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 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 (63 sec old) --------------------- ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) send: Bad file descriptor connect: Operation now in progress Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3e00061 (OpenOffice) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3e00061 (OpenOffice) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3e00061 (FedEx_Kink) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. ** (evolution-2.10:16494): WARNING **: aspell error: No word lists can be found for the language "en_US". (evolution-2.10:16494): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?) -------------------------------------------------- Traceback (most recent call last):
+ Trace 173571
self.recent_items[recent_item.get_uri()] = recent_item
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 417988 ***