GNOME Bugzilla – Bug 355956
crash in Evolution: Clicked on new to write ...
Last modified: 2006-09-14 13:44:55 UTC
What were you doing when the application crashed? Clicked on new to write an email. Using our exchange server that has always worked with this... Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 34902016 vsize: 0 resident: 179539968 share: 0 rss: 179539968 rss_rlim: 0 CPU usage: start_time: 1896 rtime: 0 utime: 1158239252 stime: 0 cutime:501 cstime: 0 timeout: 458 it_real_value: 0 frequency: 43 Backtrace was generated from '/usr/bin/evolution-2.8' (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 805576944 (LWP 5972)] [New Thread 911037680 (LWP 5999)] [New Thread 910775536 (LWP 5997)] [New Thread 901772528 (LWP 5993)] [New Thread 857375984 (LWP 5992)] [New Thread 892163312 (LWP 5990)] [New Thread 883381488 (LWP 5985)] [New Thread 866227440 (LWP 5983)] [New Thread 848987376 (LWP 5981)] [New Thread 840205552 (LWP 5980)] [New Thread 831812848 (LWP 5978)] [New Thread 823407856 (LWP 5977)] 0x0ea10220 in __waitpid_nocancel () from /lib/libc.so.6
+ Trace 72337
Thread 1 (Thread 805576944 (LWP 5972))
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. Although this stacktrace looks a little bit odd, I believe this to be another duplicate of bug 350981. *** This bug has been marked as a duplicate of 350981 ***
Hmm, a crash like this running a stable GNOME version... What does running the command 'echo $G_DEBUG' in a terminal return? Can you reproduce this crash reliably? Does it work, if you unset that var before starting Evo (if $G_DEBUG is set)? Please try reproducing the crash by starting Evo like this from a terminal -- does it work now? $ unset G_DEBUG; evolution