Bad Xorg symbolic link in Breezy
nielsen at oz.net
Wed Jun 1 16:46:50 UTC 2005
On Wed, May 25, 2005 at 10:02:44PM -0700, Bob Nielsen wrote:
> On Thu, May 26, 2005 at 11:05:35AM +1000, Daniel Stone wrote:
> > On Wed, May 25, 2005 at 11:08:54AM -0700, Bob Nielsen wrote:
> > > X died on me and won't restart. I see that /etc/X11/X is a symlink to
> > > /usr/bin/X11/Xorg, which is a symlink to /usr/X11R6/bin/Xorg. However,
> > > in the latest Breezy xserver-xorg (6.8.2-20), /usr/X11R6/bin/Xorg is not
> > > an executable, but is a symlink to itself! Thus there is no server.
> > Um, in -20, /usr/bin/X11/Xorg is a symlink to /usr/X11R6/bin/Xorg.
> Um, yes, as I said in the first sentence above. But (and I removed the
> symlink and reinstalled, but nothing changed):
> $ ls -al /usr/X11R6/bin/Xorg
> lrwxrwxrwx 1 root root 20 2005-05-25 21:41 /usr/X11R6/bin/Xorg ->
> > Unless, of course, you attempted to repair the damage by making
> > /usr/bin/X11 a symlink to /usr/X11R6/bin somehow, in which case you get
> > to keep both pieces.
> Nope. I solved the problem by extracting Xorg from the archive and
> copying it to /usr/X11R6/bin/. I'm not sure what caused the original
> problem or why reinstalling kept recreating the bad symlink. I suspect
> the -16 to -20 upgrade causes something to break.
> But then, I didn't really expect Breezy to be stable anyway.
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
It looks like -21 is broken also. It (probably an installation script)
recreated the bad symlink from /usr/X11R6/bin/Xorg to itself. When I
tried the same tactic I used for -20 (above), that didn't work, since
Xorg is only a 7460 byte file which won't execute!
More information about the ubuntu-users