GNOME Bugzilla – Bug 329387
crash after time of inatividad
Last modified: 2006-02-01 13:51:55 UTC
Distribution: Ubuntu 5.10 (breezy) Package: Evolution Severity: Normal Version: GNOME2.12.1 2.4.x Gnome-Distributor: Ubuntu Synopsis: crash after time of inatividad Bugzilla-Product: Evolution Bugzilla-Component: Mailer Bugzilla-Version: 2.4.x BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: After 2 hours, I come back,, entered password to get out of ScreenSaver and clicked in Inbox to read new emails, then Evolution crashed. Steps to reproduce the crash: 1. out of screensaver 2. click in Evolution - Inbox 3. Crash Expected Results: Read emails How often does this happen? First time now. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1230378176 (LWP 16874)] [New Thread -1299489872 (LWP 16891)] [New Thread -1299223632 (LWP 16890)] [New Thread -1290806352 (LWP 16889)] [New Thread -1282409552 (LWP 16888)] [New Thread -1272538192 (LWP 16886)] [New Thread -1264145488 (LWP 16885)] [New Thread -1247122512 (LWP 16883)] [New Thread -1255515216 (LWP 16882)] [New Thread -1237980240 (LWP 16880)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 65798
Thread 1 (Thread -1230378176 (LWP 16874))
------- Bug created by bug-buddy at 2006-01-31 19:45 -------
HI, I have more information. This bug happen because I received a email with PGP or autenticated. When I tried to read it. Evolution creshed. I deleted email, because I cant read it :( Jose Carlos
Hi Jose Carlos, thanks for the bug report. This particular bug has already been reported into our bug tracking system (the stacktrace is exactly the same as bug 326801 which has been marked as a duplicate of bug 324327), but the maintainers need more information to fix the bug. Could you please answer the questions in the other report (bug 324327)? *** This bug has been marked as a duplicate of 324327 ***