On lun, 2009-04-20 at 14:32 +0200, Olivier Berger wrote: > On Mon, 2009-04-20 at 14:11 +0200, Yves-Alexis Perez wrote: > > > > > > However, this bug is a FAQ, it seems : > > > http://www.go-evolution.org/FAQ#Why_do_I_get_an_error_.22Summary_and_folder_mismatch.2C_even_after_a_sync.22.3F > > > > > > It points to bug > > > http://bugzilla.gnome.org/show_bug.cgi?id=213072 which is announced as > > > fixed in 2.23.91 ... However it's still not in 2.24.5 AFAICT :( > > > > > > Should we reopen upstream's bug ? > > > > Did you try the steps shown in the FAQ? Did it fix the problem somehow? > > I've done the following : > evolution --force-shutdown > find ~/.evolution/mail/local -name '*ev-summary*' -exec rm -f {} \; > find ~/.evolution/mail/local -name '*.ibex*' -exec rm -f {} \; > find ~/.evolution/mail/local -name '*.cmeta*' -exec rm -f {} \; > > Then I restarted and after tens of minutes recomputing the index, it has > been able to successfully empty the trash :-) > > > The thing is, the index are now in a sqlite file so I'm not sure the FAQ > > still applies. But it might be a good idea to do it anyway. (make > > backups before, just in case). > > Sure ;) > > So there's a bug, there's a workaround... Maybe the upstream bug should > be reopened indeed...
Well, I guess the FAQ is here for that. I guess that the code has been fixed to not reproduce the bug, but if the data already written to disk are wrong, there's not much to do. I guess (again) that the bug shouldn't occur for you now, on the clean data. > > Dunno. > > Maybe 2.26 would fix that ? I think the fixable bits are already fixed. Cheers, -- Yves-Alexis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org