← Back to team overview

touch-packages team mailing list archive

[Bug 1132736] Re: Xorg fails to start after installing the hardware enablement stack on precise due to missing symlink after purging old xserver-xorg

 

Hmm, this may have been fixed now in the upcoming 14.04.3 LTS HWE
upgrade, can anyone confirm?

That is, after purging the configuration files of -utopic packages, the
link /etc/X11/X is removed but system continues to work.

I upgraded by temporarily enabling trusty-proposed updates and sudo apt
install --install-recommends libgles2-mesa-lts-vivid libglapi-mesa-lts-
vivid xserver-xorg-lts-vivid libgl1-mesa-dri-lts-vivid libegl1-mesa-lts-
vivid libgl1-mesa-glx-lts-vivid:i386

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1132736

Title:
  Xorg fails to start after installing the hardware enablement stack on
  precise due to missing symlink after purging old xserver-xorg

Status in xorg package in Ubuntu:
  Triaged
Status in xorg-lts-trusty package in Ubuntu:
  Confirmed
Status in xorg-lts-utopic package in Ubuntu:
  Confirmed
Status in xorg-lts-vivid package in Ubuntu:
  New

Bug description:
  Bug:

  The bug happens whenever the remaining configuration files of the
  original X stack is removed, ie purging. It does not happen for users
  who do not explicitly remove those.

  Workaround:

  For example, if upgraded 14.04 LTS to the 14.04.2 HWE stack
  (=14.10/utopic):

  sudo dpkg-reconfigure xserver-xorg-lts-utopic

  This restores the symlink /etc/X11/X -> /usr/bin/Xorg

  ---

  After installing the hardware enablement stack on precise by running:
  sudo apt-get install linux-generic-lts-quantal xserver-xorg-lts-quantal

  Xorg fail to start. There is no error message or anything, just a black screen. Switching to a vt i possible and lightdm/x-0.log shows that a symlink is missing:
  X: cannot stat /etc/X11/X (No such file or directory), aborting.

  I updates two computers running precise x86_64 and both had the
  problem.

  Just recreating the symlink fixes the problem and then precise runs
  perfectly fine with the new stack (in fact, it's more stable so far).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1132736/+subscriptions