Arch Linux

ichfarbstift

Member

Registered: 2011-11-22

Posts: 14

Claws-Mail resets preferences

Hi,

Since some time now I have this weird issue when using claws-mail and have not managed to understand what triggers it.
Maybe someone else in the forum has encountered it as well and knows how to solve it.

The problem is that from time to time the settings of claws-mail are reset. Not the accounts settings, only the appearance preferences and all plugins are unloaded (actually, I use only one plugin, notification). This usually happens when the application is started (I use gnome-tweaks to have it starting at boot), but I don't think that is the reason of the issue.

It is quite annoying, every time that happens I have to reconfigure my preferred settings only to see that they are lost again a couple of days later.

Does anybody have a clue of what I might do to solve it?
Thanks in advance, cheers!

GordonGR

Member

From: Thessaloniki, Greece

Registered: 2011-11-07

Posts: 276

Re: Claws-Mail resets preferences

It happens to me occasionally, too. I thinks the settings are lost because (somehow), we start Claws on boot and terminate it on shutdown. Try configuring your settings as you want them, close Claws completely and then starting it by hand. That works for me.

---

Intel(R) Celeron(R) CPU E3400 @ 2.60GHz, x86_64. AURs.

“No one without the knowledge of geometry may enter.“ Plato.

ichfarbstift

Member

Registered: 2011-11-22

Posts: 14

Re: Claws-Mail resets preferences

I was hoping it was not something like that!
The reason I have claws-mail started at boot is that otherwise I forget it and then don't check my office email...that could be dangerous!!!
Thanks anyway for the answer GordonGR.

ichfarbstift

Member

Registered: 2011-11-22

Posts: 14

Re: Claws-Mail resets preferences

Just in case anybody else has the same issue.
It seems that the problem is related to the notification plugin, that does not store preferences properly.
The only reference I found is a bug on the FreeBSD mailing list, but it seems exactly the same issue I have.

I hope this will be fixed at some point in the future!