GNOME Bugzilla – Bug 686269
[abrt] Crash on search in server-side removed folder
Last modified: 2014-02-19 18:23:12 UTC
Moving this from a downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=861756 Description of problem: while searching all messages on an imap account, evo tried to access a folder that existed the last time it was launched but was removed since by another imap client Version-Release number of selected component: evolution-3.5.92-3.fc19 Additional info: libreport version: 2.0.14 abrt_version: 2.0.13 backtrace_rating: 4 cmdline: evolution crash_function: memset kernel: 3.6.0-0.rc4.git2.1.fc18.x86_64 > Thanks for a bug report. I see from the bakctrace that the folder you > selected had set filter on itself (the one above message list, on the line > with "Show:" on the left), the messages were filtered for those with 'a2bcd' > in To or CC headers. This search parsing failed and caused evolution crash. > I see your IMAP account is IMAPx, is it correct? Also, did the folder > vanished the next start, as it should when it was removed from the server? I > made some fixes regarding this for IMAP, but not for IMAPx. 1. evo says the account is of 'imap+' type 2. evo was used to perform a search on all messages in the account 3. it crashed trying to search a folder that existed the last time it was run, but which had been removed since with another imap client (so the bug is that evo tries to search in folders without checking if they still exist, and no I was not vicious enough to remove the fomder between evo startup and search order though that would have been a valid scenario 4. I don't remember if the forler finaly vanished by itself of if I had to force refreshes in evo to make sure it didn't crash anew Core was generated by `evolution'. Program terminated with signal 11, Segmentation fault.
+ Trace 231050
Thread 1 (Thread 0x7f3ab64aea00 (LWP 13605))
I tried to reproduce this with 3.11.90 development version and it doesn't crash, it even notices the folder was removed and updates UI accordingly. And even if not, the search in that folder failed properly for me, and reading messages/entering the folder doesn't crash the application. From that I believe the 3.12.0 will be fine.