GNOME Bugzilla – Bug 361328
crash in Evolution: closing it
Last modified: 2006-10-11 18:46:02 UTC
What were you doing when the application crashed? closing it Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 161505280 vsize: 0 resident: 161505280 share: 0 rss: 38096896 rss_rlim: 0 CPU usage: start_time: 1160536288 rtime: 0 utime: 3018 stime: 0 cutime:2854 cstime: 0 timeout: 164 it_real_value: 0 frequency: 0 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 -1232599376 (LWP 5724)] [New Thread -1334969440 (LWP 5893)] [New Thread -1326576736 (LWP 5892)] [New Thread -1345578080 (LWP 5887)] [New Thread -1269900384 (LWP 5884)] [New Thread -1278293088 (LWP 5766)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 75730
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Does this happen always?
the evoulution crashes sometimes, always when i close it. i installed the "evolution-dbgsym" package for more help this is the info what you need? (sorry for my english) Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 150650880 vsize: 0 resident: 150650880 share: 0 rss: 26697728 rss_rlim: 0 CPU usage: start_time: 1160579550 rtime: 0 utime: 699 stime: 0 cutime:659 cstime: 0 timeout: 40 it_real_value: 0 frequency: 0 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 -1233434960 (LWP 23860)] [New Thread -1343743072 (LWP 23881)] [New Thread -1335350368 (LWP 23879)] [New Thread -1317385312 (LWP 23874)] [New Thread -1308992608 (LWP 23873)] [New Thread -1269400672 (LWP 23869)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 75819
Thread 1 (Thread -1233434960 (LWP 23860))
Thanks for the fast feedback. Yes, that stacktrace is good. :) *** This bug has been marked as a duplicate of 334966 ***