GNOME Bugzilla – Bug 361414
crash in Evolution: trying to access my inbo...
Last modified: 2006-10-18 16:39:16 UTC
What were you doing when the application crashed? trying to access my inbox via imap. it worked a second ago and now i got an error a couple of times stating that the search expresion was invalid and then evolution crashed. The search expression looked like an internal evolution thing for the inbox. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 290320384 vsize: 0 resident: 290320384 share: 0 rss: 43675648 rss_rlim: 0 CPU usage: start_time: 1160556976 rtime: 0 utime: 2478 stime: 0 cutime:2398 cstime: 0 timeout: 80 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 -1232857424 (LWP 6016)] [New Thread -1389089888 (LWP 11165)] [New Thread -1441043552 (LWP 11162)] [New Thread -1390412896 (LWP 6207)] [New Thread -1379927136 (LWP 6203)] [New Thread -1329484896 (LWP 6196)] [New Thread -1320608864 (LWP 6182)] [New Thread -1312216160 (LWP 6180)] [New Thread -1303823456 (LWP 6179)] [New Thread -1295430752 (LWP 6178)] [New Thread -1287038048 (LWP 6177)] [New Thread -1278645344 (LWP 6176)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 75788
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. Can you reproduce this?
According to the description, this most likely is another duplicate of bug 360237, which has been fixed already. Please feel free to report any further bugs you find. Thanks! *** This bug has been marked as a duplicate of 360237 ***