About King Puru

My photo
Hi Everyone. Welcome to my page. Here i would like to share some latest news and findings regarding open source. Although i'm still in the learning process on open source, i do hope all my post is useful to those who might face the same problem as i did. Also time to time i'll post some updates & latest stuff on some of the cool gadgets i get to know. Hope you find this page useful. Thank you, enjoy reading and have a nice day.

Error : An error occurred while loading or saving configuration information for Nautilus. Some of your configuration settings may not work properly.

Good Day All,

After a long time i'm posting again in my blog... this time its about error while launching Ubuntu 9.10 Karmic Koala after replacing a motherboard (mbo)..

This is the error message i get when i replace the mbo and use back the old hard disc with existing OS and data "An error occurred while loading or saving configuration information for Nautilus. Some of your configuration settings may not work properly."

Tried all i can n did some major search in Google, did find some info but didnt really solved my problem. So i asked help from a friend. After a lot of trial and error we manage to find the solution. So if anyone out there is facing the same problem, you might try this ;

# locate saved_state
(will giv out 2 findings, in /home/username directory and in /root directory)
# cd /home/username/.gconfd
# ls
(will show a file by the name "saved_state")
# rm -rf saved_state
(this will delete the file)
# reboot
(when the machine reboot, a fresh copy of the saved_state file will be generated and this should solved the problem)

Hope this solved your problem. Do feedback the outcome if you have tried this.

P.S : Thanks to my buddy who help me on this.


  1. Helped me to recover my karmic.
    Thank you so much

  2. I faced the same thig.
    the above workaround didnot help me.

    after my trial and errors.. [I didnt delete ~homedir/.gconfd/saved_state]

    observed 777 permissions to dir /tmp/gconfd-username

    then I provided 700 permissions to it.
    [after comparing with the user on different working machine]

    this helped to resolve my issue.

    1. This also worked for me. Earlier today I simply had set executable to everything under tmp: "chmod +x /tmp/*" and then I got those same errors when trying to log back into the desktop session. This seems like really strange behavior to me but I'm glad you identified the solution. Setting back to 700 worked. I also had to do this for /tmp/orbit-username as well.

    2. Setting perms on /tmp/gconfd-root to 700 resolved my issue. Thanks Madan..

  3. i have same issue i was delete saved_state file then reboot
    after reboot same issue and no saved_state file is created
    now what can i do

  4. I got this problem in my root user :( if I clean the saved_state in root, will it be created again?