the "On this computer" account does not stay minimized in account tree

thanks for the report, that's known upstream you can track it here: http://bugzilla.gnome.org/show_bug.cgi?id=253279

Pedro: AFAIK the bug on GNOME's bugzilla is not the same at all. The present report deals with a bug that appeared with the last SRU in Intrepid (evolution 2.24.1.1-0ubuntu1 to 2.24.2-0ubuntu1), while the remote one is from 2004 and is in calendar. At least this is how it appeared for me. See [1] for the changelog.

What I can notice is that now (i.e. after the update to 2.24.2-0ubuntu1), at startup the folder that was selected when Evo was closed is shown. But it's entry in the tree is not highlighted if this folder is on an IMAP account. Even stranger, if I select 'Drafts' on IMAP before exiting, at startup the 'Drafts' folder in 'On this computer' is shown (and highlighted). So a real mess has been recently introduced!

This is not a terrible problem, but still it is annoying, especially coming from a SRU...

1: https://launchpad.net/ubuntu/intrepid/+source/evolution/2.24.2-0ubuntu1

I've just checked downgrading to 2.24.1-0ubuntu2 (original version in Intrepid), and I can confirm it solved this bug. Going back to 2.24.2-0ubuntu1 brought the problem again. Since the new version is still in intrepid-proposed, I suggest it shouldn't enter -updates before this is fixed.

the updated version fixes several crashers and annoying issues, this bug doesn't seem worth delaying those changes

Obviously the crashers are more important than this bug.Maybe we can find the specific change that is likely to have raised the present issue. Do you have somewhere a debdiff of 2.24.1.1-0ubuntu1, 2.24.1.1-0ubuntu1 and 2.24.2-0ubuntu1? I can have a look at the code to see what we can suspect. Else I'll open a new report on GNOME's bugzilla.

the changes are on bug #276346 or you can use the viewsvn website, opening a bug upstream is a good idea though

I have filed a GNOME bug.

I filed a duplicate.

Thanks!

Sebastien Bacher: Upstream identified the patch that broke things, it was about password storage. A new version of the patch has already been committed (see [1]), so Ubuntu can do the same ASAP instead of committing the wrong patch.

1: http://bugzilla.gnome.org/show_bug.cgi?id=552583#c28

As far as I can tell, this debdiff takes the two relevant patches from the GNOME bug.

On testing, my package makes no difference.

the bug has been fixed upstream now, they will roll new stable tarballs

This bug was fixed in the package evolution - 2.26.0-0ubuntu3

---------------
evolution (2.26.0-0ubuntu3) jaunty; urgency=low

  * debian/patches/90_svn_update.patch:
    - update to the current svn version so it get testing before next tarball
      (lp: #233620, #347852, #302637, #345189, #290287, #353226)

 -- Sebastien Bacher <email address hidden> Wed, 08 Apr 2009 18:24:08 +0200