GNOME Bugzilla – Bug 359931
crash in Evolution: Mülleimer gelehrt; I emp...
Last modified: 2006-10-10 12:17:14 UTC
What were you doing when the application crashed? Mülleimer gelehrt; I emptied the Recycle Bin Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 151298048 vsize: 0 resident: 151298048 share: 0 rss: 41439232 rss_rlim: 0 CPU usage: start_time: 1160064965 rtime: 0 utime: 8633 stime: 0 cutime:6281 cstime: 0 timeout: 2352 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 -1232603472 (LWP 6803)] [New Thread -1283335264 (LWP 6846)] [New Thread -1274942560 (LWP 6845)] [New Thread -1252422752 (LWP 6816)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 74715
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.
Surely. I installed the debug package and tried reproducing the bug, but didn't succeed. Might want to add that I am using an Outlook 2003 imported mbox file (Converted my .PST file to Outlook 97/2002 file in Outlook, then used readpst). I then put the Evolution welcome message into the recycle bin. When I tried to empty it, the crash occured. Now, it doesn't crash anymore, but produces this message when I access the inbox after the recycle bin. Fehler beim Ausführen eines Suchausdrucks: Unknown type in parse tree: 141160856: (and (match-all (and (not (system-flag "deleted")) (not (system-flag "junk")))) ) What to do, what to do? Also something I should mention is that my .PST file might have been slightly corrupted even before it was converted...
I'll reopen and see if the additional info is useful to the maintainers, though they may have to remark as needinfo and just hope that you or someone else can trigger the problem again.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. I believe this to be yet another duplicate of bug 360237. *** This bug has been marked as a duplicate of 360237 ***