GNOME Bugzilla – Bug 695022
Pan drops some settings on system upgrade
Last modified: 2013-03-25 20:56:01 UTC
I recently upgraded from Fedora 16 to 17. When I ran Pan, I quickly found out that it had forgotten my posting password, but not the rest of my posting data. It also forgot that I used a sigmonster (and where it was) and decided that I didn't really want to see signatures, making me think that it was mangling my posts on sending until I happened to find that setting. As it happens, I run Xfce instead of Gnome, but I've been doing that for at least a year without Pan objecting, so I can't see where that's an issue. The version, BTW, is 0.139, which isn't listed up above.
Problems with server passwords (I know from personal experience) can be caused by compiling pan with different 'configure' settings for --enable-gkr (gnome-keyring support). If you once told pan to use gnome-keyring to save your server passwords and then updated to a version of pan that was compiled *without* gnome-keyring support, you can expect exactly that sort of problem. I dunno how to tell if a fedora package was compiled with/without that configure option, though.
BTW, I forgot to mention that xfce depends heavily on the gnome infrastructure, so using xfce doesn't rule out the problem I described above.
I should have mentioned that I never had this type of issue before upgrading from Fedora 16 to 17. And, even if what you say about gnome-keyring is an issue, it doesn't explain why it forgot where my sigmonster is, or why it changed my settings so that I wasn't seeing signatures. (AFAIK, I never told Pan to do that, but it's possible that it had been set at one time to do that by default.) However, thank you for responding so quickly. I've had all too many bugs ignored for months and getting even a little feedback in under seven hours is appreciated.
There is a gnome app called seahorse that allows you to see and modify your gnome keyring saved passwords. I see several entries labelled "Pan Newsreader's server passwords" for various news accounts I've had over the years. If you have such entries in your own gnome keyring database then I think that might explain your problem.
this is not really a bug, but a configuration issue, sorry.