Bug 708290
| Summary: | Post upgrade, evolution (under XFCE) no longer stores the current folder view. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gilboa Davara <gilboad> |
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> |
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | lucilanga, mbarnes, mcrha |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-06-01 12:37:07 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Gilboa Davara
2011-05-27 07:24:18 UTC
Thanks for a bug report. This seems to work fine for me. When you run evolution from console, is there any runtime warning printed, either on open, when you collapse/expand any folder, or on close? This folder tree expand state is stored in ~/.config/evolution/mail/state.ini, maybe there is something wrong with it. When you open it (with closed evolution), and search for the folder name, then the key Expanded may reflect your last choice, before the evolution is closed. Could you check that, please? Hello Milan, I've delete state.ini and started from scratch, the state of the folders seems to be holding. However, there seem to be a related (?) issue: Within each folder, evolution used to store the state of the collapsed / open threads. This is no longer the case: In F15 all the threads default to open, -whenever- I switch folder. E.g. Go to folder X, collapse all threads. Switch to folder Y, and than back to X, all threads will be expanded. Is it a related issue, or should I open a new BZ? - Gilboa Thanks for the update. Was there anything special about the state.ini file? It may work even without removing it, supposing it was writeable. I'm closing this for now, but feel free to reopen if you face it again. With respect of threading state, there is a bug report [1] filled upstream, thus we can move there. [1] https://bugzilla.gnome.org/show_bug.cgi?id=578245 |