GNOME Bugzilla – Bug 382031
crash in Evolution: Opening up a usenet post...
Last modified: 2006-12-09 15:02:06 UTC
What were you doing when the application crashed? Opening up a usenet post to read, after having read several (~20) already Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 278003712 vsize: 0 resident: 278003712 share: 0 rss: 80584704 rss_rlim: 0 CPU usage: start_time: 1165180135 rtime: 0 utime: 5894 stime: 0 cutime:5722 cstime: 0 timeout: 172 it_real_value: 0 frequency: 22 Backtrace was generated from '/usr/bin/evolution-2.8' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1232603472 (LWP 5824)] [New Thread -1377154144 (LWP 5924)] [New Thread -1368749152 (LWP 5923)] [New Thread -1360352352 (LWP 5908)] [New Thread -1311073376 (LWP 5898)] [New Thread -1302013024 (LWP 5844)] [New Thread -1293583456 (LWP 5841)] [New Thread -1285063776 (LWP 5840)] [New Thread -1276671072 (LWP 5839)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 91375
Thread 1 (Thread -1232603472 (LWP 5824))
another one of those bad ubuntu stacktraces... are the debugging packages for evolution, evolution-data-server and gtkhtml installed? we need a better stacktrace...
I'm not sure if it's the same crash, but this one occurred while closing the window of a usenet post. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 271691776 vsize: 0 resident: 271691776 share: 0 rss: 95481856 rss_rlim: 0 CPU usage: start_time: 1165405789 rtime: 0 utime: 4719 stime: 0 cutime:4583 cstime: 0 timeout: 136 it_real_value: 0 frequency: 17 Backtrace was generated from '/usr/bin/evolution-2.8' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1233172816 (LWP 7857)] [New Thread -1378030688 (LWP 7965)] [New Thread -1392510048 (LWP 7961)] [New Thread -1379927136 (LWP 7958)] [New Thread -1369502816 (LWP 7957)] [New Thread -1361110112 (LWP 7956)] [New Thread -1311642720 (LWP 7955)] [New Thread -1302582368 (LWP 7879)] [New Thread -1294152800 (LWP 7870)] [New Thread -1285633120 (LWP 7869)] [New Thread -1277240416 (LWP 7868)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 92035
Thread 1 (Thread -1233172816 (LWP 7857))
I can easily reproduce this, so if there is any other debug info I can get or things you want me to check in gdb let me know.
:-) it's already filed, bug 239441. *** This bug has been marked as a duplicate of 239441 ***