GNOME Bugzilla – Bug 385943
crash in Evolution:
Last modified: 2007-10-19 01:08:37 UTC
What were you doing when the application crashed? Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 159240192 vsize: 0 resident: 159240192 share: 0 rss: 54575104 rss_rlim: 0 CPU usage: start_time: 1166107527 rtime: 0 utime: 4857 stime: 0 cutime:4541 cstime: 0 timeout: 316 it_real_value: 0 frequency: 740 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 -1232861520 (LWP 3929)] [New Thread -1318061152 (LWP 10640)] [New Thread -1316426848 (LWP 5769)] [New Thread -1288569952 (LWP 3953)] [New Thread -1296962656 (LWP 3951)] [New Thread -1272022112 (LWP 3949)] [New Thread -1263223904 (LWP 3940)] [New Thread -1254786144 (LWP 3938)] [New Thread -1246393440 (LWP 3937)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 94186
Thread 1 (Thread -1232861520 (LWP 3929))
Looks like a gtk bug, reassigning. 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 395186 has been marked as a duplicate of this bug. ***
Dear reporter, could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance for helping to get this fixed! [1] Please install debug packages for glib2 and gtk2. Ubuntu 6.10: libglib2.0-0-dbg, libgtk2.0-0-dbg Fedora Core 6 or OpenSuSE 10.2: glib2-debuginfo, gtk2-debuginfo More details can be found here: http://live.gnome.org/GettingTraces
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!