Red Hat Bugzilla – Bug 440126
evolution doesn't remember the stat of the message preview
Last modified: 2008-08-17 08:47:11 EDT
Evolution doesn't always remember the state of the message preview. It seems it remembers it in the current session but if I reboot or logout I need to re-enable it. Everytime after I log back in the preview has gone. Let me know if you need any more information. [root@euuklonw7300b1n ~]# rpm -qa| grep evolution evolution-webcal-2.21.92-1.fc9.x86_64 evolution-2.22.0-4.fc9.x86_64 evolution-data-server-2.22.0-3.fc9.x86_64 evolution-data-server-doc-2.22.0-3.fc9.x86_64 evolution-exchange-2.22.0-1.fc9.x86_64 evolution-data-server-devel-2.22.0-3.fc9.x86_64 evolution-help-2.22.0-4.fc9.x86_64
Can you check on a couple GConf keys? /apps/evolution/shell/recovery /apps/evolution/shell/skip_recovery_dialog Do you usually exit Evolution before logging out?
Keys are: [perobinson@euuklonw7300b1n ~]$ gconftool-2 -g /apps/evolution/shell/recovery true [perobinson@euuklonw7300b1n ~]$ gconftool-2 -g /apps/evolution/shell/skip_recovery_dialog true I usually exit evolution before I log out but not always. It tends to be a matter of how much of a rush I'm in. Sometimes I just type poweroff on a command line. It always seem to work OK with Fedora 8 whatever I happened to do.
Try resetting both of those keys to False. If Evolution crashes, the next time you restart it will ask you if you want to turn off previews as a security measure (crashes are often caused by trying to render an email in the preview pane). If you elect to skip that dialog in the future it will always turn off previews automatically when it detects a crash. Also, I do recall Evolution having issues with session management, such that closing the session without explicitly closing Evolution first makes Evolution think it crashed. I thought this was fixed for Fedora 9, but perhaps not. I guess I need to recheck that.
I have experienced the same thing. And I am pretty sure it just happens when evo crashes, or maybe a logout/reboot without closing it.
This seems to have gone away with later versions of 2.22 even when I have to kill evo because it 'loses connectivity with the exchange backend'. So will close now.