GNOME Bugzilla – Bug 447564
crash in Email:
Last modified: 2007-06-14 19:42:37 UTC
What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 100012032 vsize: 100012032 resident: 22241280 share: 16060416 rss: 22241280 rss_rlim: 4294967295 CPU usage: start_time: 1181837230 rtime: 101 utime: 80 stime: 21 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208949024 (LWP 3611)] [New Thread -1218311280 (LWP 3619)] (no debugging symbols found) 0x008a9402 in __kernel_vsyscall ()
+ Trace 140955
Thread 1 (Thread -1208949024 (LWP 3611))
----------- .xsession-errors (9 sec old) --------------------- ** Message: <info> Adesso si è connessi alla rete cablata. connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! Avviso del window manager: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a0005b (OpenOffice) Avviso del window manager: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. wine: Unhandled exception (thread 0016), starting debugger... err:dbghelp:pe_load_dbg_file -Unable to peruse .DBG file WinWord.DBG ("WinWord.DBG") CalDAV Eplugin starting up ... ** (evolution:3611): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3611): DEBUG: mailto URL program: evolution --------------------------------------------------
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 431342 ***