On Mon, Mar 31, 2003 at 12:03:26AM +0200, Nicolas Kratz wrote: > On Sun, Mar 30, 2003 at 04:34:02PM -0500, [EMAIL PROTECTED] wrote: > > > Up-to-date sid installation w/ working X: > > > > > > [EMAIL PROTECTED]:~$ ll /tmp/.X11-unix/ -a > > > total 16 > > > drwxrwxrwt 2 root root 4096 Mar 24 03:19 . > > > drwxrwxrwt 9 root root 12288 Mar 30 22:41 .. > > > srwxrwxrwx 1 root root 0 Mar 24 03:19 X0 > > > srwxrwxrwx 1 root root 0 Feb 15 12:14 X64 > > > > thanks Nick. Mine looks just like that, except without the X0 and X64. > > is that the problem? > > Suppose not. I'm not at all an X guru, but these are sockets and should > only appear when X is running. The only other thing I stumbled across > are some lockfiles (for these sockets?), make sure there are no stale > ones around. But that's just a shot in the dark. > > [EMAIL PROTECTED]:~$ ll /tmp/.X*-lock > -r--r--r-- 1 root root 11 Mar 24 03:19 /tmp/.X0-lock > -r--r--r-- 1 root root 11 Feb 15 12:14 /tmp/.X64-lock > > If all else fails, track the error message down in the source and check > what it's really complaining about.
Since X works on clean installations, I'm pretty sure deleting/moving out of the way /etc/.X* would fix this. -- Rob Weir <[EMAIL PROTECTED]> http://www.ertius.org/ Signed mail preferred: http://www.gnupg.org/ Do I look like I want a CC? Words of the day: ASIO Iran subversive NORAD BROMURE FIPS140 condor
pgp00000.pgp
Description: PGP signature
