abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: evolution comment: I needed to to a cold-reboot(/reset because there was some kernel oops related to ext4 component: evolution executable: /usr/bin/evolution kernel: 2.6.35.6-48.fc14.x86_64 package: evolution-2.32.1-1.fc14 reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1290609818 uid: 500 How to reproduce ----- 1. Ext4 Partition 2. Kerneloops with evolution open 3.
Created attachment 462651 [details] File: backtrace
Thanks for a bug report. As this is crashing within sqlite3 command, when executing an SQL command, and you said you had an issue with your partition, is it possible that this was caused also by the partition issue? I mean if yes, and evolution was trying to access part of the partition which had trouble, then there is not much what can the application do. At least from my point of view. Or did I misunderstand anything?
Yes, I suppose that the crash was related to that filesystem issue. I was able to solve this problem by deleting ~/.local/share/evolution I suppose that the sqlite3 db was corrupted.
Thanks for the update. I guess that too. Would you mind if I just close this bug report? Or we can link this to some upstream, if you wish, though it's pretty rare to see this kind of failure (I see this for the first time, to be honest).
Maybe other people just wondered why Evolution stoppped working and switched quitely to Thunderbird or Outlook ;) It would be nice if this case could be handled and s simple error message like: Your message cache is corrupted and needs to be rebuild. (So the folder just needs to be deleted, as the rebuild happens automatically, if it is not present, right?) But it's up to you wheter to close this bug or not :)
Package: evolution-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I Send an E-Mail
Yes, I agree. There is filled a similar upstream bug [1], thus I'm moving this there. Please see [1] for any further updates. [1] https://bugzilla.gnome.org/show_bug.cgi?id=602319
Thanks for your help.