Dear All, I'm running Debian Jessie amd4 on a recent MacBook Pro. The if I move things around in the claws-mail main program (the width of the folder list for example) it is not saved if I close and reopen the program. Furthermore (tell me if this should be reported as another bug), the same sort of problem occurs with the trayicon part of the notification plugin: I select which folders I want it to monitor, and it forgets on when I re-run the program! Any ideas? Thanks, Edward
how do you quit Claws?
the little "x" in the corner, should I try something different?
(In reply to comment #2) > the little "x" in the corner, should I try something different? Is this bug still happening with version 3.11.1 ?
yes, on the jessie version, mostly the widths of the columns in the folder view doesn't seem to be remembered.
(In reply to comment #4) > yes, on the jessie version, mostly the widths of the columns in the folder > view doesn't seem to be remembered. In a terminal, could you run command “ls -ld ~/.claws-mail ~/.claws-mail/clawsrc” and paste the output here?
drwx------ 14 ed users 4096 Jan 7 14:03 /home/ed/.claws-mail -rw------- 1 ed users 11198 Dec 15 09:50 /home/ed/.claws-mail/clawsrc
(In reply to comment #6) > drwx------ 14 ed users 4096 Jan 7 14:03 /home/ed/.claws-mail > -rw------- 1 ed users 11198 Dec 15 09:50 /home/ed/.claws-mail/clawsrc This is weird, unless you haven't exited Claws Mail since December 15th :) because the file and directory timestamps are updated on exit. Do you have enough disk space on partition where /home/ed/.claws-mail is located? If you do, next step, on a terminal again: run “claws-mail --debug > debug.log 2>&1” and when Claws Mail had finished to startup, just go File/Exit. Check the debug.log has no personal info you don't want to share (replace it with other similar token) and attach it to this bug.
There is too much personal data to filter in here -- I'll email it to you personally, if you don't mind, please confirm.
(In reply to comment #8) > There is too much personal data to filter in here -- I'll email it to you > personally, if you don't mind, please confirm. Well, yes, that could be too. The idea is to look for some error/warning relevant to this, probably in the end of the log, after the File/Quit option is activated. If you don't find anything yourself go ahead and mail me the whole debug.log privately (gzipped, preferably ;-)