Hide Forgot
abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: evolution component: evolution crash_function: ____strtoull_l_internal executable: /usr/bin/evolution kernel: 2.6.35.9-64.fc14.x86_64 package: evolution-2.32.1-1.fc14 rating: 4 reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1295911920 uid: 500 How to reproduce ----- 1.I have Evolution opened in the background. It closed without doing something 2.I already try to remove rspam plugin 3.I already installed the developement version, but it's the same
Created attachment 475078 [details] File: backtrace
Error in point 3 - I installed evolution-dataserver 2.32.1-2.fc14 from updates-testing repo. Already try to install evolution 2.32.0-2, but returns the same error
Thanks for a bug report. This is crashing because of broken folders.db file, some value didn't write to the database, and as NULL passed to strtoul it crashes. This was fixed in [1]. This seems to be in your ~/.local/share/evolution/mail/local/folders.db in the Inbox table, the UID column is probably NULL. You have two options: a) move away that folders.db file when evolution is not running and it'll be regenerated the next start. This solution has a disadvantage, you may lose labels and similar tags on your local messages, as these are stored in this file b) remove only broken rows from the Inbox table there. You can do that either in some UI sqlite3 table editor like sqliteman or run a command like this in the terminal (I hope I didn't do a typo in it): $ sqlite3 ~/.local/share/evolution/mail/local/folders.db "DELETE FROM 'Inbox' WHERE uid IS NULL;" Though before running it do a backup of the folders.db file, just in case. [1] https://bugzilla.gnome.org/show_bug.cgi?id=573125
Thanks! Removing the folders.db works for me. If Evolution returns a simple error message, the solution for this issue will be much more easy
Yup, I agree. The upstream fix ignores these errors gracefully, which means you may not see this again.
*** Bug 672979 has been marked as a duplicate of this bug. ***
*** Bug 695305 has been marked as a duplicate of this bug. ***