Blog Closed

This blog has moved to Github. This page will not be updated and is not open for comments. Please go to the new site for updated content.

Monday, August 25, 2008


Turn on my laptop today, and start up with my daily routine. I log in, check some email and stuff on my family computer, and then click the icon in the corner telling me I have software updates to install.

I open the update manager and read through the list of updates, like I always do. I actually take the time to read through the updates I install unlike most users, I'm sure. The update has something to do with the kernel development header files, and maybe some update to a library (I don't remember now). It looked relatively harmless, so I clicked install. Install goes quickly, and then I'm prompted to restart my laptop so the changes can take effect.

Restart. Boot up. log in. blackness. Nothing appears on my screen for several seconds, then I get an error message from GNOME: "The GNOME session manager was unable to lock the file '/home/andrew/.ICEauthority'. Please report this as a GNOME bug. Sometimes this error may occur if the file's director is unwritable, you could try logging in via the failsafe session and ensuring that it is." I click OK, and it kicks me back to the login screen.

So I try again, same error. I try logging into the failsafe session, same error. Good. I try logging in to a different user account, and that works but it's not what I want. I don't like having my one administrator account locked because of a software problem. So I go looking through the internet and find a series of people who have also received this error, and a series of unhelpful responses. People offer solutions and I try every single one. I create directories, I throw around chmod and chown. nothing works. More then one person suggests the solution to the problem is a fresh install. I find that to be severely upsetting

It's a few minutes later and I'm still fighting with this issue. I'm going to be very upset if I can't get my laptop working again without having to do a complete system reinstall.

1 comment:

  1. Fix, I found a few potential fixes scattered throughout the interschmoe. If you are having a similar problem, here are some things you can try:

    1) Enter the terminal, call "sudo chmod 777" on the file in question.
    2) Enter the terminal, call "sudo chown MYUSERNAME:MYUSERNAME" on the file, where MYUSERNAME is your username.
    3) Delete .ICUauthority
    4) Delete any temporary residual files that match the pattern .ICUauthority*. For me, these files were named .ICUauthority-c and .ICEauthority-l.

    If these don't work for you, you have some kind of problem that I havent seen yet.


Note: Only a member of this blog may post a comment.