I just installed openSuse 11.2 on Asus X51L laptop. I already have Windows XP installed. The problem came up right after installation, when he installed Suse and tried to enter it for the first time, this message appeared after long wait at login screen:
**
The following installation problem was detected while trying to start KDE:
No write access to ‘/home/nidzge/.ICEauthority’.
KDE is unable to start.
**
I restarted laptop but same thing happened. BTW I installed KDE desktop.
I downloaded image of openSuse 11.2 from this location: Software.openSUSE.org
and burnt on DVD.
Nidzge wrote:
> NO WRITE ACCESS TO ‘/HOME/NIDZGE/.ICEAUTHORITY’.
-=welcome=- to the forum and openSUSE!
that ICEauthority problem i most often associate with damage caused by
logging into KDE/Gnome/etc as the root user…but you say this was
your FIRST login, is that correct?
or was it your first login as yourself, the normal user following a
previous login as root??
if it was actually the first ever login by you or root, then i agree
100% with gogalthorp’s assessment and suggest it sounds a lot like you
may have a corrupted install disk…
if, on the other hand there was a previous login as root, say so and
we can help you repair the damage done, maybe…it may be easier to
start over and never ever log in to KDE/Gnome/etc as root/super
user/administrator…
I checked the medium and it turns out to be ok. I saw somewhere in the forums to use ext3 instead of ext4 (which is default when installing). I started installation all over again and changed to ext3 and it worked with no problems. I don’t know if that was the problem, but it’s all good now except my network connection isn’t working But I will find answers in other topics about that problem.
I had a similar problem after installation of o.S.11.2 with gnome from a DVD about 4 weeks ago:
(previous install o.S.11.1 with KDE3.5.10 dual boot with Windows XP)
Partition / ext4, Partition /home ext 3 by default , all runnuing fine.
After installation of KDE3.5.10 -which i still like-i got’ Unable to update ICVM’ before the gnome greeter and the same warnings as described by Nidzge:‘No write access to /home/<user>/.ICEauthority ’ and
’ unable to start KDE’ after the greeter.
I returned to gnome desktop, opened /home/<user>/.ICEauthority with Dolphin(root)
and changed the accessrights for groups and others.
After this KDE3.5.10 is freely available when chosen in the greeter with all personal settings from previous o.S.11.1.
I had to repeat this procedure just oncea couple of days later,but since then the systems runs fine.
E.K.
eberhardkrehl wrote:
> I had a similar problem after installation of o.S.11.2 with gnome from a
> DVD about 4 weeks ago:
> (previous install o.S.11.1 with KDE3.5.10 dual boot with Windows XP)
> Partition / ext4, Partition /home ext 3 by default , all runnuing
> fine.
> After installation of KDE3.5.10 -which i still like-i got’ Unable to
> update ICVM’ before the gnome greeter and the same warnings as
> described by Nidzge:‘No write access to /home/<user>/.ICEauthority ’ and
> ’ unable to start KDE’ after the greeter.
> I returned to gnome desktop, opened /home/<user>/.ICEauthority with
> Dolphin(root)
> and changed the accessrights for groups and others.
> After this KDE3.5.10 is freely available when chosen in the greeter
> with all personal settings from previous o.S.11.1.
> I had to repeat this procedure just oncea couple of days later,but
> since then the systems runs fine.
> E.K.
>
>
as mentioned, that ICE* file permissions damage is most often (in my
experience) caused by logging into KDE/Gnome/etc as root…and,
exactly as you say the permissions get changed ‘somehow’ and until
they are reassigned as required to the user and user group, you will
remain locked out…
the simple solution is to never log into KDE/etc as root because
doing so 1) opens you up to several different security problems, 2)
too many too easy ways to damage your system no matter how careful
your actions (example: just browsing in your home directory while
logged into KDE/Gnome/etc as root can lock you out later as yourself
due to permissions damage), 3) and, anyway logging into KDE/etc as
root is never required to do any and all administrative duties…
so, always log in as yourself, and “become root” by using a root
powered application (like YaST, File Manager Superuser Mode) or using
“su -”, sudo, kdesu, or gnomesu in a terminal to launch whatever tool
is needed (like Kwrite to edit a config file)…read more on all that
here:
Thanks for the quick response.
However since I never log in as root into gnome or kde–all previous systeminstallations starting with Linux Suse10.0 until now were done with both root and user password.
On my second laptop i am running o.S.11.1 with gnome and kde 3.5.10 + windows XP
and the above mentioned problem did never occur.
May o.S. 11.2 be the reason?
Anyhow my o.S. 11.2 is doing well and insofar i am happy.
E.K.