Re: [testing] HELP - lost X
> $ ls -ld /usr/include/X11/
> drwxr-xr-x 11 root root 4096 2006-05-23 10:41 /usr/include/X11/
>
> I think you could try to create the directory with the same owner and
> permissions and then repeat the upgrade. (I am not sure, but I guess
This is with Xorg 6.9.0.dfsg1-6 - doing a dpkg --configure -a warns me
that /usr/include/X11 is not a symbolic link when I make it as a
directory as you suggest.
I may be in a catch-22 situation here - can't fix the present
x11-common, but can't upgrade to the 7.0.22 version either because the
previous one is broken.
> If that fails it might be time for the "no more Mr. Nice Guy" approach:
> You could try "dpkg -r --purge" to remove the old x11-common package,
Well, apart from getting a slew of can't read current directory issues
(not sure from whence I ran aptitude) I'm reinstalling the xorg package.
On the other hand, it's blowing away most of my system in the process,
such as kde. But then my install of 3.5.x might be broken (mostly works
as is, except for amarok crashing left and right). (later) found out I
was in /usr/include/X11 when doing that install. Switched to root's home
and continuing...
Looks like I have put myself into a no-win situation. The upgrade won't
happen because /usr/X11R6/bin belongs to opera, and opera can't be
deinstalled without removing nearly my whole system. But then using dpkg
-i --force on the package x11-common seems to have gotten things going.
As a precaution, of course, I've been jigdo'ing the most recent snapshot
of etch I could find ;) - my previous one I used to install from (last
November) has developed bad sectors - d*mn dvd-rw media from sri lanka
or whatever... :(
Anyway, thanks for the help. Here's hoping I don't have to reinstall
from scratch....
> Florian
--
------------------------------------------------------------------------
David E. Fox Thanks for letting me
dfox@tsoft.com change magnetic patterns
dfox@m206-157.dsl.tsoft.com on your hard disk.
-----------------------------------------------------------------------
Reply to: