could not update ice authority file
I turned on "hidden files" in a folder yesterday.
Today when trying to boot the machine I get the message "could not update ICE authority file", and when I click through it go's back to the password screen.
How do I fix this??
Running Ubuntu 11.10
On an Acer Aspire 3600 laptop
Ubuntu is a stand loan OS on this machine.
Thanks
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Ubuntu gdm Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- Allen
- Solved:
- Last query:
- Last reply:
Revision history for this message
|
#1 |
Revision history for this message
|
#2 |
I'm going to need some clearer details on how to do this.
I get a message "event failed" and the problem remains.
Revision history for this message
|
#3 |
Hope it helps.
https:/
Revision history for this message
|
#4 |
Sam's help got me the mesage "cannot access file no such file exsists" on every word I typed in.
I would hope this isn't that big a deal, any other ideas?
Thank you
Revision history for this message
|
#5 |
You did replace the user name with yours when attempting to set permissions correctly?
Please describe what you did exactly and which cmds you've issued. Thanks.
.ICEauthority is a hidden file in your /home/<user>, it must be write- and readable by the user.
Work in recovery mode or virtual console (text mode only): ctrl+alt+f1
Update database and try to locate the file:
sudo updatedb
locate .ICEauthority
Revision history for this message
|
#6 |
Hey Sam,
Thanks for sticking with me.
Yes I changed the user name when I made my last attempt.
I have tried so many things I couldn't possibly remember all the stuff I wrote or received. Sorry.
I know it's a pain but, I think going back to the begining and getting precice input comands ie: spelling, spaces, and the like. Either I'm thrashing around making mistakes or the problem runs deeper than we think.
I went to recovery mode and typed "sudo updatedb locate .ICE authority" and got a masty gram that didn't make any sense about the updatedb being a problem.
What should I type when in the root shell to get what we want?
Thanks, Allen
Revision history for this message
|
#7 |
OK, I've taken some time and done this all over again.
I ran Action Parsnip's sugestion and here's what followed.
I typed "chown -R allen:allen /home/allen; reboot"
It flew through pages of files and said "Will Reboot" it did and went back to the recovery screen, I went ahead and booted with my password and the problem was still there.
I did Sam's sugestion:
chown allen:allen /home/allen/ .ICEauthority
chmod 600 /home/allen/
It came back with:
chown: changing ownership of /home/allen': Read only File System
chown: cannot access'
chown: cannot access '600': no such file or directory
chown: changing ownership '/home/allen': read only file system
chown: cannot access :.ICEauthority': no such file or directory
All I wanted to do was view hidden files and look at the mess I've got on my hands here!
I hope this helps
Thanks
Revision history for this message
|
#8 |
> chown allen:allen /home/allen/ .ICEauthority
There shouldn't be an empty space, it's:
chown allen:allen /home/allen/
Anyway it doesn't sound healthy when the filesystem is read only. Perhaps run fsck.
touch /forcefsck
reboot
## It'll check fs on reboot.
https:/
> I went to recovery mode and typed "sudo updatedb locate .ICE authority" and got a masty gram
Where does #5 indicate it's a one-liner?
To use 'locate' the database should be up-to-date.
This updates database, there is no feedback expected.
sudo updatedb
## Of course in recovery mode (root shell) no 'sudo' necessary.
Revision history for this message
|
#9 |
I ran chownallen:
bash: chownallen:
I ran the same thing with a space between chown and allen with the result,
chown: missing operand after “allen:
As to #5, when I type "updatedb" and enter I get,
updatedb: cannot open a temporary file for '/var/lib/
I can't imagine the point in writing a second line “locate .ICEauthority”
when it can't open the file in the first place.
This is my situation, I have a business to run and customers becoming ugly as I attempt to
correct this train wreck.
Can I just install 12.4 and overwrite all this or am I stuck wasting hours, days, weeks going round and round on this??
I know it's all second nature to you folks but I never had the time to learn the nomenclature and all
the in and outs of this stuff!!
Please advise.
Thanks, Allen
Revision history for this message
|
#10 |
Decided to forgo eating!
While thrashing around hoping to not make matters worse I retried (while in the root shell)
Nothing happened unlike before, I then typed “locate .ICEauthority” it came back with,
Of course it still doesn’t log in but it's something new.
What dose it mean???
Thanks
Revision history for this message
|
#11 |
> What dose it mean?
That the file exists and you've located it. Well done.
Regarding /var/lib/
chown -R gdm:gdm /var/lib/gdm
chmod 600 /var/lib/
Afterwards verify permissions:
ls -al /var/lib/gdm
Regarding /home/allen/
chown allen:allen /home/allen/
chmod 600 /home/allen/
Afterwards verify permissions:
ls -al /home/allen/
When all is as expected please reboot.
Revision history for this message
|
#12 |
Sam,
Looks like I screwed up right out of the box!
Typed the following, chown -R gdm:gdm/var/lib/gdm and hit enter, the result was
chown: missing operand after 'gdm:gdm/
What am I doing wrong ??
Allen
Revision history for this message
|
#13 |
> What am I doing wrong ??
You're missing empty spaces again. I'll paste it there, hope it makes it easier for you to visualize the difference.
http://
Revision history for this message
|
#14 |
Sam,
That did help greatly thanks! Here's what happened.
Typed: chown -R gdm:gdm /var/lib/gdm
Response was: changing ownershipp of (and it went through many files)
Typed: chmod 600 /var/lib/
Response was: changing permissions of '/var/lib/
Typed: ls -al /var/lib/gdm
Response was: total 60
Typed: chown allen:allen /home/allen/
response was: chown: changing ownership of 'allen:
Typed: chmod 600 /home/allen/
Response was: chmod: changing permissions of '/home/
Typed: ls -al /home/allen/
Response was: -rwx--x--x 1 allen allen 108116 20 05 12 10:51 /home/allen/
I then typed exit and resumed normal boot.
It still won't let me login.
What now??
Allen
Revision history for this message
|
#15 |
Allen, you're working from recovery mode 'root shell'? Otherwise you need to prefix with 'sudo'.
Also verify that /home/allen doesn't belong to root:
ls -al /home/allen
There shouldn't be one single entry saying 'root'.
There is a reason when filesystem is mounted read only, it usually does that to prevent damage.
Did you fsck the filesystem as suggested in #8?
Verify there is enough disk space:
df -h
Other workarounds in case of autologin, encrypted fs.
http://
http://
Revision history for this message
|
#16 |
I am using “recovery mode” and the “root shell prompt”.
I verified /home/allen.
I typed: ls -al /home/allen
No mention of the word “root” anywhere.
I retried fsck as instructed in #8 from the “root shell prompt”.
I typed: touch /forcefsck
Response was: touch: cannot touch ' /forcefsck' read-only file system
I also tried the first suggestion under “Other workarounds in case of auto login.
While in recovery and root shell.
I typed: login
then: allen
and: (my password)
Response was: failed to add entry for user allen
Are we getting anywhere??
Allen
Revision history for this message
|
#17 |
I am using “recovery mode” and the “root shell prompt”.
I verified /home/allen.
I typed: ls -al /home/allen
No mention of the word “root” anywhere.
I retried fsck as instructed in #8 from the “root shell prompt”.
I typed: touch /forcefsck
Response was: touch: cannot touch ' /forcefsck' read-only file system
I also tried the first suggestion under “Other workarounds in case of auto login.
While in recovery and root shell.
I typed: login
then: allen
and: (my password)
Response was: failed to add entry for user allen
Are we getting anywhere??
Allen
Revision history for this message
|
#18 |
Could you reboot and right after boot login to virtual console: ctrl+alt+f1
Enter your username and pw, then repeat cmds of #14, there you'll need 'sudo'.
Revision history for this message
|
#19 |
It took a while to figure out how to get out of the virtual console, reboot did the trick.
The results where the same: verify ls -al /var/lib/gdm where
drwxr-x---11 gdm 4096 2011-10-14 14:01.
drwxr-xr-x 65 root root 4096 2012-5-9 07:59..
drwxr-xr-x 3 gdm gdm 4096 2011-05-07 00:03. cache
ect. ect.
verify ls -al /home/allen/
-rw------- 1 allen allen 108116 2012-05-12 10:51 /home/allen/
hope this helps,
Allen
Revision history for this message
|
#20 |
Thanks Allen and yes 'sudo reboot' exits the virtual console and reboots.
The output looks good from here.
The /var/lib/
Now when you're in virtual console can you stop gdm, reconfigure gdm and start gdm please:
sudo service gdm stop
## or if there is a complain about 'service' try:
sudo gdm stop
sudo dpkg-reconfigure gdm
sudo service gdm restart
## alternative:
sudo gdm start
In case of errors please post exact error output, thank you.
Revision history for this message
|
#21 |
This round was different!
I am typing the commands as you have showed me and going to next command so /var/lib/
As mentioned this test was a trip.
From virtual console I typed :
Response: [sudo] password for allen I put in my password.
“ stop: unknown instance:
I typed: sudo gdm stop
Response: gdm -binary[1752]: warning: GdmDisplaylasts 0.111395 seconds
I then lost my prompt and was unable to do anything, I could type whatever I wanted but nothing would happen.
I had to force the machine down at that point. No other way out.
Allen
Revision history for this message
|
#22 |
This round was different!
I am typing the commands as you have showed me and going to next command so /var/lib/
As mentioned this test was a trip.
From virtual console I typed :
Response: [sudo] password for allen I put in my password.
“ stop: unknown instance:
I typed: sudo gdm stop
Response: gdm -binary[1752]: warning: GdmDisplaylasts 0.111395 seconds
I then lost my prompt and was unable to do anything, I could type whatever I wanted but nothing would happen.
I had to force the machine down at that point. No other way out.
Allen
Revision history for this message
|
#23 |
Allen, try MagicSysRq 'REISUB' instead of hard reset.
http://
Anyway, do you still get the initial issue "could not update ICE authority file"?
Allen, did you try the other cmds?
sudo dpkg-reconfigure gdm
sudo service gdm restart
## alternative:
sudo gdm start
What happens when you try to start Xserver:
startx
Revision history for this message
|
#24 |
Sam,
Regarding SysRq: Now that's a cool little trick, got it documented for future use, thanks.
I still have the .ICEauthority issue.
The responses were as follows:
service gdm stop
unknown instance
gdm stop
unknown instance
dpk-reconfigure gdm
dpk-reconfigure: command not found
gdm start
gives me the warnings listed above #21 & #22
gdm restart
same warnings
All this is in virtual console using sudo.
Allen
Revision history for this message
|
#26 |
Sam,
Sorry!
As you can imagine that changes things a little.
I got a purple screen with a white box full of text.
It had a heading of "Configuring gdm"
First line reads: a display manager is a program that provides graphical login capabilities for the X Window system
a bunch of stuff about displays and servers.
It had two choices "gdm" and "lightdm", lightdm was high lighted so I hit enter, the display flashed sevral times and I had the warnings back.
Revision history for this message
|
#27 |
If lightdm is the display manager now rename all ICEauthority and reboot. Seems the upgrade messed up, unfortunately you're not the only one, assume a fresh installation would've saved lots of time.
Revision history for this message
|
#28 |
So, I should get a copy of 12.4 and run it?
Allen
Revision history for this message
|
#29 |
Allen, that's the easy path to get a clean system, but it doesn't clarify the ICEauthority complain though.
When lightdm is active you could actually try to purge gdm and also apply autoremove.
Revision history for this message
|
#30 |
Sam, I would be happy to just get this thing going again.
I suppose it would be nice to know what caused all this, but my situation may not be the best venue to learn what triggered the problem.
I'm not sure I can do anything while lightdm is active.
Assuming I can, what is the command for purge gdm or autoremove when there?
Allen
Revision history for this message
|
#31 |
sudo apt-get purge gdm
sudo apt-get autoremove
sudo reboot
Usually ICEauthority gets corrupted when playing with 'sudo' and not knowing the consequences.
But in this case one could blame the conflict gdm vs lightdm too.