GNOME Bugzilla – Bug 360721
crash in Evolution: Hice click sobre un emai...
Last modified: 2006-10-09 03:18:15 UTC
What were you doing when the application crashed? Hice click sobre un email no leido, y la aplicacion se colgo. Intentaré acceder al email para ver que contenido tenía. I clicked over an unreaded email, and the aplication hangs up. I will try to access the email to verify what kind of content it had. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 107823104 vsize: 0 resident: 107823104 share: 0 rss: 28213248 rss_rlim: 0 CPU usage: start_time: 1160333374 rtime: 0 utime: 682 stime: 0 cutime:646 cstime: 0 timeout: 36 it_real_value: 0 frequency: 2 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 -1232562512 (LWP 4768)] [New Thread -1307501664 (LWP 4804)] [New Thread -1288635488 (LWP 4799)] [New Thread -1280242784 (LWP 4798)] [New Thread -1271448672 (LWP 4797)] [New Thread -1250714720 (LWP 4774)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 75294
Created attachment 74311 [details] readed emails when the program crashes
Accedí nuevamente al email en cuestión, pero no paso nada. Aparentemente el cuelgue no tiene nada que ver con el contenido del mensaje. De todas maneras adjunto los correos que estaba viendo en el momento del cuelgue. Debo aclarar que estaba utilizando beryl como gestor de decoraciones en el momento del cuelgue, y ya me paso de tener problemas con otras aplicaciones. -------- I access again the named email, but nothing happens. Apparently, the crash has nothing to do with the content of the message. Anyway, enclosed you will find the emails I was reading when the program hangs out. I must say that I was running beryl as decoration manager when the application crashes, and I already had some problems with bery and other programs.
Thanks for your efforts and all these details, Manual. Much appreciated. :) Anyway... Closing incomplete for now as per comment 2, the crash is not reproducible. Unfortunately the stacktrace does not have any hints about the real cause of the crash and does not help in debugging this issue. Anyway, according to the description, most likely filed already. For some yet unknown reason, such stacktraces are pretty common currently on certain distros. However, almost all of them do turn out to be filed already, once we managed to gather a useful stacktrace. To do so, simply install the corresponding debugging packages and reproduce the issue, if possible. The resulting stacktrace (see bug-buddy details) will help us to identify and fix the issue. Just in case you ever can reproduce this crash later, please consider installing debugging packages [1] and either reopen this bug report or simply file a new one with the resulting stacktrace. Thanks! Also, please feel free to report any further bugs you find. Thanks! [1] debugging packages for evolution and evolution-data-server, plus debugging packages for some basic GNOME libs. More details can be found here: http://live.gnome.org/GettingTraces/DistroSpecificInstructions