Red Hat Bugzilla – Bug 700733
Folder summary information is not properly updated after migration
Last modified: 2014-01-02 05:45:57 EST
Description of problem: After migrating Evolution settings from RHEL5.6 to RHEL6, when Evolution starts for the first time, folder summary is shown only for Inbox - i.e. unread count is shown only on Inbox, not on the rest of the folders. Folders Properties show right count for Unread messages, but 0 for Total messages. I have to restart Evolution to get proper numbers and even then unread count is shown on folders only when I explicitly click on them. All the above is done before I connected to mail server - i.e. folders were not sync. with mail server. What I would expect is that after migration before I connect to mail server, folders summary is the same as it was in RHEL5.6 when I created the backup. I'm using IMAP account with GSSAPI for auth. Version-Release number of selected component (if applicable): evolution-2.28.3-24.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1.Backup client evolution settings on RHEL5.6 Workstation 2.Open evolution on newly installed RHEL6, and perform a restore operation for evolution-backup.tar.gz created in step #1 3. Check the folder summary. Actual results: unread count is shown only on Inbox Expected results: folder summary is the same as it was on RHEL5.6 during backup. Additional info: Testing this should just be a matter of setting up some kind of IMAP account on RHEL 5, letting Evolution download summary info for your mail folders so it has data to migrate, and then upgrading to RHEL 6 and running Evolution.
Can be same issue as in bug #700726
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
(In reply to Milan Crha from comment #1) > Can be same issue as in bug #700726 Thinking of it, Jiri might know, whether the backup was created on 64bit, and then imported on 32bit, while the migration failed (about which is the bug #700726). Jiri, do you recall the two architectures, please? In case it's the 64bit->32bit, then we can mark this as a duplicate of the mentioned bug report.
(In reply to Milan Crha from comment #4) > (In reply to Milan Crha from comment #1) > > Can be same issue as in bug #700726 > > Thinking of it, Jiri might know, whether the backup was created on 64bit, > and then imported on 32bit, while the migration failed (about which is the > bug #700726). Jiri, do you recall the two architectures, please? In case > it's the 64bit->32bit, then we can mark this as a duplicate of the mentioned > bug report. Nah, forget it, I can reproduce this even when migrating between versions with the same architectire.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-1540.html