After installing madwifi, I get this error message at login
couldn’t update ICEauthority/home/name/ICEaithority.
Now I don’t have to login i.e. enter my password. It just goes to a black screen and I get this error, which I close out and than I am logged into my desktop which seems to be fine.
the Dude abides wrote:
> After installing madwifi, I get this error message at login
>
> couldn’t update ICEauthority/home/name/ICEaithority.
…/home/[you]/.ICEauthority must not be read/write-able by anyone
other than the user [you]…neither can it be owned by root…i
guess you installed madwifi while logged into the GUI as root…or,
you followed an instruction to become root by typing su, instead of
su -
see:
http://tinyurl.com/6ry6yd
http://tinyurl.com/ydbwssh
http://docs.kde.org/stable/en/kdebase-runtime/userguide/root.html
–
palladium
Very insightful recommended topics, I didn’t have the full time to appreciate all that was said in the forums next to su - puts you in the root environment.
I’m not sure if it was exactly after installing madwifi, but it was around that time, It’s most likely as you said using su instead of su - during an istallation. Although, I’m not sure what you are suggesting to look into to find a fix for this problem other than being more conscious of using "su - " instead of su next time.
the Dude abides wrote:
> I’m not sure what you are suggesting to look into to find a fix for
> this problem
sorry, i thought telling you that .ICE* had to be owned and read only
by [you] would prompt you to check if that is the way it is…
you just need to boot to run level 3 [at the first boot screen type 3
and hit enter, soon you will be at a black and white terminal with a
sign in prompt], sign in as root and type:
ls - /home/[you]/.auth
the return should look something like:
-rw------- 1 [you] users 1078 Dec 11 09:16 /home/[you]/.ICEauthority
-rw------- 1 [you] users 163 Dec 11 09:16 /home/[you]/.Xauthority
if it is more like
-rw-rw-rw- 1 root [root] 1078 Dec 11 09:16 /home/[you]/.ICEauthority
-rw-rw-rw- 1 root ????] 163 Dec 11 09:16 /home/[you]/.Xauthority
then the earlier must be repaired using chown and chmod
well, i’ve just spent about half an hour trying to remember exactly
how to do that…and, must be having a ‘senior moment’ or a caffeine
low level condition…
maybe some one else will pop in and give you the correct poop…if
not, i might be back later…
be careful with root stuff…it is possible to kill your system with
it, as you have found…
–
palladium
joerione, Thanks for the referral that did the trick.
chmod 777 fixed the issue.
I’m still not sure how my issue came up in the first place, since I don’t remember logging into Gnome as root.