GNOME Bugzilla – Bug 361112
crash in Evolution: I selected Trash (which ...
Last modified: 2006-10-10 12:15:34 UTC
What were you doing when the application crashed? I selected Trash (which was empty but it should have contained several messages - that's strange). I then clicked my incoming mail folder and it produced the folowing message (this is translation from Slovenian and may not be 100% correct): Error creating message (maybe mail?) list. Error performing search statement Unknown type in parse tree: 139216128: (and (match-all (and (not (system-flag "deleted")) (not (system-flag "junk")))) ) I clicked OK here and then (with my mail folder selected) clicked on search input field and pressed Enter. It then produced this error and crashed. It started to do so a few days ago. When I delete a message, the Trash remains empty and when I choose my folder (= folder containing my incoming mail) it produces the first error message and it doesn't list my mail messages. If I try to perform search, it crashes. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 92508160 vsize: 0 resident: 92508160 share: 0 rss: 25694208 rss_rlim: 0 CPU usage: start_time: 1160477493 rtime: 0 utime: 146 stime: 0 cutime:134 cstime: 0 timeout: 12 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 -1233209680 (LWP 8851)] [New Thread -1285112928 (LWP 8861)] [New Thread -1276716128 (LWP 8860)] [New Thread -1252353120 (LWP 8858)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 75589
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.
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. *** This bug has been marked as a duplicate of 360237 ***