GNOME Bugzilla – Bug 462199
crash in Evolution: I just closed the window...
Last modified: 2007-08-30 16:43:59 UTC
What were you doing when the application crashed? I just closed the window. I had just deleted some files from the maildir beneath its feet... I suspect this is a duplicate of the last bug I raised (id=450062, in turn a duplicate of 334966) Distribution: openSUSE 10.2 (X86-64) Gnome Release: 2.16.1 2006-11-28 (SUSE) BugBuddy Version: 2.16.0 Memory status: size: 490172416 vsize: 490172416 resident: 13701120 share: 21250048 rss: 34951168 rss_rlim: 1314652160 CPU usage: start_time: 1185899126 rtime: 447 utime: 417 stime: 30 cutime:0 cstime: 0 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 46914875682000 (LWP 9955)] [New Thread 1115969856 (LWP 9971)] [New Thread 1115703616 (LWP 9967)] [New Thread 1107310912 (LWP 9963)] [New Thread 1098918208 (LWP 9961)] [New Thread 1090525504 (LWP 9960)] [New Thread 1082132800 (LWP 9959)] (no debugging symbols found) 0x00002aab360a5c5f in waitpid () from /lib64/libpthread.so.0
+ Trace 151864
Thread 1 (Thread 46914875682000 (LWP 9955))
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 334966 ***
*** Bug 465077 has been marked as a duplicate of this bug. ***
*** Bug 466036 has been marked as a duplicate of this bug. ***
*** Bug 467551 has been marked as a duplicate of this bug. ***
*** Bug 467617 has been marked as a duplicate of this bug. ***
*** Bug 468472 has been marked as a duplicate of this bug. ***
*** Bug 471666 has been marked as a duplicate of this bug. ***
*** Bug 471768 has been marked as a duplicate of this bug. ***