GNOME Bugzilla – Bug 435218
crash in Evolution: first run of program
Last modified: 2007-05-21 21:25:44 UTC
What were you doing when the application crashed? first run of program Distribution: Mandriva Linux release 2007.1 (Official) for i586 Gnome Release: 2.18.0 2007-03-15 (Mandriva) BugBuddy Version: 2.18.0 System: Linux 2.6.17-13mdvlegacy #1 SMP Fri Mar 23 19:05:24 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Ia Ora Blue Icon Theme: gnome Memory status: size: 60428288 vsize: 60428288 resident: 22552576 share: 14446592 rss: 22552576 rss_rlim: 4294967295 CPU usage: start_time: 1178120726 rtime: 93 utime: 85 stime: 8 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/i686/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1236982048 (LWP 10957)] (no debugging symbols found) 0xbfffe410 in __kernel_vsyscall ()
+ Trace 131912
Thread 1 (Thread -1236982048 (LWP 10957))
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Could you please install some debugging packages [1] and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the "details", now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks! [1] debugging packages for evolution, evolution-data-server and gtkhtml, plus debugging packages for some basic GNOME libs. More details can be found here: http://live.gnome.org/GettingTraces/DistroSpecificInstructions
*** Bug 436400 has been marked as a duplicate of this bug. ***
*** Bug 437171 has been marked as a duplicate of this bug. ***
The temporary solution of bug is running Evolution from terminal: 'evolution -c mail --disable-eplugin' or change properties of button as above. The functionality of Evolution is full implemented.
*** Bug 437417 has been marked as a duplicate of this bug. ***
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 425129 ***
*** Bug 440258 has been marked as a duplicate of this bug. ***