On Thursday 17 March 2005 06:29 pm, Leendert Meyer wrote:
On Friday 18 March 2005 00:23, BandiPat wrote:
Cleaned out /tmp and would not log in at all after that.
Yup, that happened to me too. According to the errormessage in ~/.X.err, I had to `chown root: /tmp/.ICE-unix`:
drwxrwxrwt 2 root root 112 2005-03-17 20:17 /tmp/.ICE-unix
(permissions were already ok)
Cheers,
Leen ============
Leen, I didn't have a ~/.X.err, but did have a ~/.xsession-errors file. I tried several things, but still didn't have any luck getting kde started as root. I can start any other window manager as root, but not KDE. Very odd and they've hidden things in different locations again, making it difficult to trace now. This is what my .xsession-errors file mentions though: startkde: Starting up... kbuildsycoca running... kdecore (KLibLoader): WARNING: KLibrary: /opt/kde3/lib/kde3/kcm_kdnssd.so: undefined symbol: init_kdnssd kded: Fatal IO error: client killed kdeinit: Fatal IO error: client killed kdeinit: sending SIGHUP to children. kdeinit: Fatal IO error: client killed kdeinit: sending SIGHUP to children. klauncher: Exiting on signal 1 DCOP aborting call from 'anonymous-11768' to 'klauncher' kdeinit: sending SIGTERM to children. kdeinit: Exit. I've tried creating a link, as it was with 3.3 from /var/tmp/kdecache-root/ksycoca to /tmp/kde-root/ksycoca got this error after doing that: /opt/kde3/share/config/kdm/Xsession: line 51: /root/.xsession: no such file or directory Removed /tmp/.ICE-unix Checked owners for that and as you found, it was ok At the moment, I'm at a loss, but will continue tracking. Sure, you're not suppose to be logging in as root anyway, but I hate it when something doesn't work. :o) regards, Lee