GNOME Bugzilla – Bug 493001
crash in Email:
Last modified: 2007-11-03 16:02:41 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 176685056 vsize: 176685056 resident: 48881664 share: 41922560 rss: 48881664 rss_rlim: 4294967295 CPU usage: start_time: 1194089748 rtime: 75 utime: 69 stime: 6 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 -1209080096 (LWP 5570)] [New Thread -1268782192 (LWP 5575)] [New Thread -1258292336 (LWP 5574)] [New Thread -1245746288 (LWP 5572)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 174823
Thread 1 (Thread -1209080096 (LWP 5570))
----------- .xsession-errors --------------------- Channels : 1 Sample Rate : 11025 Time: 00:00.43 [00:00.00] of 00:00.43 ( 100.0%) Output Buffer: 20.67K play sox: 'resample' clipped 14 samples; decrease volume? play sox: alsa: output clipped 10 samples; decrease volume? Done. CalDAV Eplugin starting up ... (evolution:5570): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one (evolution:5570): e-utils-WARNING **: Plugin 'Bogofilter junk plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.0' ** (evolution:5570): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:5570): 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 364700 ***