GNOME Bugzilla – Bug 317329
Evolution 2.4.0 crashes when creating a search folder with no email folder selected.
Last modified: 2005-09-28 10:29:29 UTC
This bug has been opened here: http://bugzilla.ubuntu.com/show_bug.cgi?id=16416 "Evolution 2.4.0 crashes when creating a search vfolder, if no folder is already selected when starting the operation. Steps to reproduce the crash: 1. Ensure no folder is selected in the email folder list... perhaps by selecting the account name. 2. Create a new search from Search->Create Search Folder from Search... 3. Fill arbitrary data into the form. 4. The Search Folder Sources list in the search should be empty, so add INBOX. 5. Click OK... and crash. Expected Results: Search vfolder should be created normally. How often does this happen? Every time."
backtrace of the crash: 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) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1230435520 (LWP 21049)] [New Thread -1265701968 (LWP 21057)] [New Thread -1256146000 (LWP 21056)] [New Thread -1247753296 (LWP 21052)] [New Thread -1238910032 (LWP 21051)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 63225
Thread 1 (Thread -1230435520 (LWP 21049))
confirming the bug.
Created attachment 52760 [details] [review] Patch for the bug This should fix the bug.
Fix committed to both HEAD and 2.4.1 branch. Please update.
thanks, that fixes the issue