GNOME Bugzilla – Bug 692636
doesn't delete certain contacts
Last modified: 2014-12-01 17:14:24 UTC
Just a while ago I started up Evolution and it behaved in a very strange way. I switched to the calendars and observed that one calendar was still enabled in the left sidebar, but didn't show its appointments anymore. Removing the calendar and importing the iCalendar file again had no effect, it still didn't show the appointments. Then I switch to contacts. I select all the contacts in an address book and delete them, but after being asked for confirmation Evolution did nothing. This happened more than once. I reboot my laptop and try again. This time most of the contacts were deleted, but three remaining contacts persistently refused to be deleted after multiple attempts: try to delete, confirm, Evolution does nothing. There was no crash or error message at all, so I guess I can't make a stack trace or something. Is there any other way to log what's going on to determine what's wrong?
Thanks for a bug report. If it's still an issue, try to run evolution-addressbook-factory from a console like this: $ /usr/libexec/evolution-addressbook-factory -w The best if you'll make sure there will be no same process already running. Then run evolution from another console and try to reproduce the issue. When you manage to do so, get backtrace of both running processes by: $ gdb --batch --ex "t a a bt" -pid=`pidof evolution` &>evo.txt $ gdb --batch --ex "t a a bt" -pid=`pidof evolution-addressbook-factory` &>eaf.txt Please make sure you'll have installed debuginfo packages for evolution-data-server and evolution, and that the files will not contain any private information, like passwords; I usually search for "pass" (quotes for clarity only). Also check the book console, maybe it'll print something useful. By the way, what is the address book type, please?
Thank you for your reply. I only use local address books. I rarely delete or add contacts and haven't been hit by the bug recently, so I'll have to test deliberately to have any chance of reproducing the bug. I probably won't have much time for that soon.
I'm closing this for now, please try with more recent evolution, while the current stable version is 3.12.8. Feel free to reopen if you'll face this with it again. Thanks in advance.