GNOME Bugzilla – Bug 387380
crash in Evolution: I was in preferences and...
Last modified: 2007-07-04 12:59:42 UTC
What were you doing when the application crashed? I was in preferences and clicked the Canadian English check box. The American English check box was already selected. I'm not running debug code so I'm not sure that this will be useful, but good luck anyway. Cheers, Frank Distribution: openSUSE 10.2 (X86-64) Gnome Release: 2.16.1 2006-11-28 (SUSE) BugBuddy Version: 2.16.0 Memory status: size: 664403968 vsize: 664403968 resident: 35684352 share: 25026560 rss: 60710912 rss_rlim: 1736622080 CPU usage: start_time: 1166493352 rtime: 2911 utime: 2758 stime: 153 cutime:0 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/opt/gnome/bin/evolution-2.8' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47601423150288 (LWP 13395)] [New Thread 1115969856 (LWP 13408)] [New Thread 1107577152 (LWP 13406)] [New Thread 1107310912 (LWP 13405)] [New Thread 1098918208 (LWP 13404)] [New Thread 1090525504 (LWP 13402)] [New Thread 1082132800 (LWP 13399)] (no debugging symbols found) 0x00002b4b0f755c5f in waitpid () from /lib64/libpthread.so.0
+ Trace 95291
Thread 1 (Thread 47601423150288 (LWP 13395))
*** Bug 391510 has been marked as a duplicate of this bug. ***
*** Bug 410188 has been marked as a duplicate of this bug. ***
*** Bug 418932 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
*** Bug 425570 has been marked as a duplicate of this bug. ***
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
*** Bug 437437 has been marked as a duplicate of this bug. ***
*** Bug 453594 has been marked as a duplicate of this bug. ***