A rather nasty crash…

While preparing and testing XBMC (will write about that soon) I had a really nasty crash which prevented me from doing anything with my computer. After the login screen a couple of error messages with stuff like

"Failed to contact configuration server, some possible causes are that you need to enable TCP/IP networking for ORBIt or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: IOR file '/tmp/gconfd-root/lock/ior' not opened successfully, no gconfd located: Input/output error 2: IOR file '/tmp/gconfd-root/lock/ior' not opened successfully, no gconfd located: Input/output error)"

Tried everything I could think of, booted from a CD, ran FSCK, rebooted, rebooted again, read a thousand pages on Google (on another computer), went through the syslog and messages logs etc. My Gnome screen was black, and the only thing that worked was the mouse and PrntScrn which, apart from bringing up the screendump dialog also generated an error message.

The solution which I found here, sortof, which in turn makes it possible for me to write this, was to rename saved_state like this:

mv ~/.gconfd/saved_state saved_state.old

Reasons like this makes it hard to suggest Linux to my mother…


6 Responses to A rather nasty crash…

  1. Adam says:

    Thankyou for this. I have been pulling my hair out all morning.

  2. Matthew Lock says:

    Fixed my system too! Thanks!

  3. Simanek says:

    As far as things like this making it difficult to recommend Linux to your mother… you could have just as easily accomplished this same action in Nautilus:

    1 Go to your home directory in Nautilus
    2 Main Menu > View > Show Hidden Files
    3 Navigate to ~/.gconfd
    4 Rename file ‘saved_state’ to ‘saved_state_old’

    I’ve certainly had to do crazier things to fix problems in OSX and Windows. If it was even possible to fix. Sometimes with OSX and Windows your just stuck waiting for the company to release an update to fix the problem.

    Otherwise, thanks for this hint. I couldn’t figure out what the problem was!

  4. Rocketman says:

    I changed the file name from ‘saved_state’ to ‘saved_state_old’ and the problem has returned, When I checked ~/.gconfd I now have both ‘saved_state’ and ‘saved_old_state’. This problem, “An error occurred while loading or saving configuration information for evolution-alarm-notify. Some of your configuration settings may not work properly.” appears to change Evolution so that it will not except my password to the mail server.

  5. Ols says:

    Change name of saved_state to saved_state2

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: