After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 583553 - Summary and folder mismatch, even after a sync
Summary and folder mismatch, even after a sync
Status: RESOLVED DUPLICATE of bug 550414
Product: evolution
Classification: Applications
Component: Mailer
2.26.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[disk-summary]
Depends on:
Blocks:
 
 
Reported: 2009-05-22 12:51 UTC by tremaine
Modified: 2009-05-25 12:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Attachments
evolution debug output from May 1 2009 to present (31.53 KB, application/x-gzip)
2009-05-23 01:53 UTC, tremaine
Details

Description tremaine 2009-05-22 12:51:34 UTC
Please describe the problem:
This problem has been occurring through three different versions of Ubuntu

Currently running Jaunty x86_64 from a fresh install.

Linux quad 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux
evolution:
  Installed: 2.26.1-0ubuntu1
  Candidate: 2.26.1-0ubuntu1
  Version table:
 *** 2.26.1-0ubuntu1 0
        500 http://ca.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status


Problem has been reported a number of times through Launchpad.  After a few hours or days of use, I will start getting a 'summary and folder mismatch even after sync' error when moving between folders.  


https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/360667

Steps to reproduce:
1. Open evolution
2. Use for a few hours or a couple of days
3. Get error


Actual results:
Program becomes unusable

Expected results:
Nothing :)

Does this happen every time?
Yep.  It's repeatable enough that I run evolution out of a script now to do all the steps to make it run without errors for a period of time.

Other information:
There is currently 1.1G of data in .evolution after removing anything older than 2 years.

tlea@quad:~$ cat /usr/local/bin/evolution.sh
#!/bin/bash

# script for https://bugs.launchpad.net/bugs/360667

# /usr/local/bin/cmetaibex.sh is simply the commands below.  The rm *.ev-summary* should be unneccessary
# in current versions of evolution, but may be left over from an upgrade

# rm *.cmeta;
# rm *.ibex.*
# rm *.ev-summary*

DATE=`date +%a%m%d%Y:%T`

evolution --force-shutdown;

cd /home/$USER/.evolution/mail/local/;
/usr/local/bin/cmetaibex.sh;
cd /home/$USER/.evolution/mail/local/Inbox.sbd/ddiction.sbd/ ;
/usr/local/bin/cmetaibex.sh;
cd /home/$USER/.evolution/mail/local/Inbox.sbd/Facebook.sbd/ ;
/usr/local/bin/cmetaibex.sh;
cd /home/$USER/.evolution/mail/local/Inbox.sbd/FD.sbd/ ;
/usr/local/bin/cmetaibex.sh;
cd /home/$USER/.evolution/mail/local/Inbox.sbd/GoogleAlerts.sbd/ ;
/usr/local/bin/cmetaibex.sh;
cd /home/$USER/.evolution/mail/local/Inbox.sbd/Livejournal.sbd/ ;
/usr/local/bin/cmetaibex.sh;
cd /home/$USER/.evolution/mail/local/Inbox.sbd/SierraSystems.sbd/ ;
/usr/local/bin/cmetaibex.sh;
cd /home/$USER/.evolution/mail/local/Inbox.sbd/Zorch.sbd/ ;
/usr/local/bin/cmetaibex.sh;
cd /home/$USER/.evolution/mail/local/Inbox.sbd/zot.sbd/ ;
/usr/local/bin/cmetaibex.sh;

evolution --debug /home/tlea/Desktop/evolution-debugs/evolution.debug.$DATE
Comment 1 tremaine 2009-05-23 01:53:16 UTC
Created attachment 135219 [details]
evolution debug output from May 1 2009 to present
Comment 2 André Klapper 2009-05-24 18:54:19 UTC
(In reply to comment #1)
> Created an attachment (id=135219) [edit]
> evolution debug output from May 1 2009 to present

That's not debug output, it's just shell output...
Comment 3 tremaine 2009-05-24 19:17:31 UTC
Where do I find the actual output of evolution --debug?

I'm more than happy to provide any needed info/output, just let me know how/where.
Comment 4 Akhil Laddha 2009-05-25 06:17:57 UTC
i guess it can be marked as dupe of bug 550414
Comment 5 tremaine 2009-05-25 12:02:52 UTC
http://bugzilla.gnome.org/show_bug.cgi?id=550414 certainly looks like the same issue, or at least very closely related.

*** This bug has been marked as a duplicate of 550414 ***