Hello, coming for help/advice again ...
I did a mistake (running a GUIapp with sudo or sth like this), had this classical problem (can't write to /home/user/.ICEauthority), tried to solve it, but it still didn't work, and after login, KDE starts to load but even before the 1st icon appears, black screen and back to login screen.
More detailed : I was running out of diskspace (100% full on home partition - ok, now I'm aware it builds up), I cleaned some old packages (apt-get autoremove/autoclean/clean as well as .thumbnails/large &/normal folder), but I did this with sudo dolphin. On next boot, "can't write access to */.ICEauthority".
I found out I could login in console and do startx with sudo (how bad is it to do this ?), then I thought stuff would come back to normal. I also did a $sudo aptitude update, and may have upgraded some packages, but I don't remember (I was unaware I was logged as root!).
Next boot, same problem. In console login, I tried several times (having stopped kdm first) to remove or chown to user .ICEauthority and .Xauthority. It then shows the right owner (user), but still no login possible (I tried stopping kdm and doing startx from the Konsole, and also rebooting and login from the login screen -- in order to have only one active login session as two maybe be impossible - is it the case ?).
NB: in /home, the folder /user is owned by user.
In this post http://kubuntuforums.net/forums/inde...pic=3113764.15, there is sth about var/tmp/kdecache-user. I deleted it, but it doesn't solve the problem.
Here is the /xsession-errors file, after unsuccessful login into KDE (I then made a copy of the file in console login).
Side question : is every file/folder visited when running as root turned to being owned by root ?
Still so much to learn, it seems ...
NB II: there are four security packages available to update. is it better to wait the problem to be solved rather than upgrading when logged as root ?
Thanks
kln
Maverick Meerkat 2.6.35.24-generic
I did a mistake (running a GUIapp with sudo or sth like this), had this classical problem (can't write to /home/user/.ICEauthority), tried to solve it, but it still didn't work, and after login, KDE starts to load but even before the 1st icon appears, black screen and back to login screen.
More detailed : I was running out of diskspace (100% full on home partition - ok, now I'm aware it builds up), I cleaned some old packages (apt-get autoremove/autoclean/clean as well as .thumbnails/large &/normal folder), but I did this with sudo dolphin. On next boot, "can't write access to */.ICEauthority".
I found out I could login in console and do startx with sudo (how bad is it to do this ?), then I thought stuff would come back to normal. I also did a $sudo aptitude update, and may have upgraded some packages, but I don't remember (I was unaware I was logged as root!).
Next boot, same problem. In console login, I tried several times (having stopped kdm first) to remove or chown to user .ICEauthority and .Xauthority. It then shows the right owner (user), but still no login possible (I tried stopping kdm and doing startx from the Konsole, and also rebooting and login from the login screen -- in order to have only one active login session as two maybe be impossible - is it the case ?).
NB: in /home, the folder /user is owned by user.
In this post http://kubuntuforums.net/forums/inde...pic=3113764.15, there is sth about var/tmp/kdecache-user. I deleted it, but it doesn't solve the problem.
Here is the /xsession-errors file, after unsuccessful login into KDE (I then made a copy of the file in console login).
Code:
Xsession: X session started for user at Wed Dec 15 01:53:32 CST 2010 QMetaObject::invokeMethod: No such method Konsole::Application::loadCommandLineOptionsForNewInstance() x-terminal-emulator: Fatal IO error: client killed konsole(1744) Konsole::SessionManager::~SessionManager: Konsole SessionManager destroyed with sessions still alive
Still so much to learn, it seems ...
NB II: there are four security packages available to update. is it better to wait the problem to be solved rather than upgrading when logged as root ?
Thanks
kln
Maverick Meerkat 2.6.35.24-generic
Comment