GNOME Bugzilla – Bug 730106
Cursor position always reset and scrolls to the top of the message listview for the current folder
Last modified: 2015-03-05 19:13:35 UTC
Evolution remembers the last position within folders, so if you scroll down and select some message at the end (or middle, or wherever you want to scroll to), when you switch between folders it will remember that position and restore it. The problem is that Evolution resets it for the current shown folder on startup, so it scrolls back up to the top no matter where you were before. But if you click one of the other folders, you'll see it restore their previous scroll positions. So the problem is really "whatever folder is shown on startup... gets its scroll position reset". This is particularly annoying when your sorting order is descending date (newest messages at the bottom, so that threading actually makes sense :)
Demonstration: http://jeff.ecchi.ca/public/evolution-730106.webm
Thanks for a bug report. I tried the same steps, but it works fine for me. Can it be, that the message is properly selected, but the view is not scrolled to the right position? I'm testing with a change for bug #730110, but I've no idea whether it has any influence on this non-scrolling.
Hi Milan, No, no message is selected at all on startup (in addition to the view not being scrolled to the proper position). Personally I'm fine with the thought of no message being selected. To easily reproduce in my end, I just use a threaded folder view where it is sorted by date (oldest at the top, newest at the bottom): 1. Scroll to the bottom, select one of the last messages (optional) 2. Restart evolution 3. Notice the scroll it's gone right back to the top.
Right, I did exactly the same, in one of my On This Computer folders and also in one of my IMAP folders, but none stroke the issue; with or without the preview panel being visible. I'd expect that you have the right message selected, but the scroll failed for some reason. By any chance, is there any runtime warning printed on the console when you run evolution? Could you copy ~/.config/evolution/mail/state.ini file, do some change in selected message, close evolution, check the difference (diff -u state.ini.bak state.ini) to see whether the SelectedMessage in that folder was properly saved, and then run evolution and see whether the state.ini file changed again? It may change whenever you change anything in UI, like the message select.
These are the things I see printed to the terminal when starting Evolution: (evolution:10535): CRITICAL **: categories_icon_theme_hack: assertion 'filename != NULL && *filename != '\0'' failed (evolution:10535): camel-imapx-WARNING **: Unable to load store summary: Expected version (1), got (0) (evolution:10535): camel-WARNING **: Cannot load summary file: Success No bp log location saved, using default. [000:000] Cpu: 6.37.5, x4, 2134Mhz, 3751MB [000:000] Computer model: Not available [000:001] Browser XEmbed support present: 1 [000:001] Browser toolkit is Gtk2. [000:008] Using Gtk2 toolkit No bp log location saved, using default. [000:000] Cpu: 6.37.5, x4, 2134Mhz, 3751MB [000:000] Computer model: Not available -------------- And regarding the state.ini file, I copied it before restarting, during restart and after re-quitting; the resulting three files are strictly identical since I did not actually change the message selection (only restarted a few times), but at least its value is not 0 or something. If I select another message in the view and exit, the SelectedMessage value correctly changes (it is currently SelectedMessage=31091).
This had been fixed within bug #741858. *** This bug has been marked as a duplicate of bug 741858 ***