Bug 281629 - Configuration is not stored, all changes are forgotten after new session is strated
Summary: Configuration is not stored, all changes are forgotten after new session is s...
Status: RESOLVED DUPLICATE of bug 281627
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: 4.6
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-08 15:08 UTC by Dan
Modified: 2012-10-31 22:07 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dan 2011-09-08 15:08:10 UTC
Version:           4.6 (using KDE 4.6.5) 
OS:                Linux

On my notebook, any configuration I made through System Settings, plasma (e.g. adjusting panel size and location), or for a particular application (e.g. kmail setting), is forgotten next time I log into KDE. I have my home mounted on encrypted partition, using 'encfs', but the files seems to be OK. May this be a cause?

Other non-KDE applications (sure for mc and VirtualBox) do remember their config.


Reproducible: Always

Steps to Reproduce:
e.g. open kwrite, change any settings, close kwrite. Open it again and the changes are not there.
Or ajust any plasma applet (change size, position, add new, ...), log out, then log in again and all changes will be forgotten.


Expected Results:  
Persistent configuration.

I have found a report with similar issue (I think it has been about home mounted from a remote directory, or something like this). As I remebmer, it is claimed there that it has to do something with FUSE not following POSIX standard. There was also note that it should be fixed in KDE 4.6.5, but it does not work for me in this version.

Unfortunately, I am not able to find the report again ...
Comment 1 Dan 2012-10-31 22:07:18 UTC
Most likely caused by "paranoid" encfs settings.

*** This bug has been marked as a duplicate of bug 281627 ***