← Back to team overview

kernel-packages team mailing list archive

[Bug 1302771] Re: Kernel Update 3.13.0-22 Deletes Desktop Manager and /etc/X11/xorg.conf file


The source package I think is the kernel update which I could not find
in the package list. When the kernel was updated about 50 to 200
packages were updated/downloaded as well so its hard to know the
specific package in this case. If anybody knows which package to select
for this please  do so.

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  Kernel Update 3.13.0-22 Deletes Desktop Manager and /etc/X11/xorg.conf

Status in “linux” package in Ubuntu:

Bug description:
  I updated from Kernel 3.13.0-20 to 3.13.0-22. After the update my
  computer would only log in to a terminal. I found on the webs how to
  get log files from desktop bootup. The error that was reported was
  missing device section for instance BusID PCI:0@1:0:1.

  After searching the web, I also figured out how to fix the problem,
  which turned out to be the update had removed many of the files needed
  for the desktop to run including the /etc/X11/xorg.conf file. I assume
  the error printout on my question above was due to the missing.conf
  file causing fglrx to fail to initialize properly.

  My first step was to reinstall ubuntu-desktop in the command line
  using sudo apt-get install --reinstall ubuntu-desktop. This was a long
  install. In the middle of the install I was asked to select a desktop
  manager. I selected light-dm. I dont know if that was the right choice
  but I had used that for 12.04, so I figured it would work.

  Than I followed the directions on this website
  under the section Generate a new /etc/X11/xorg.conf file. Than I
  forced amd drivers to use that config file. The directions for that
  are also on that website. I than restarted my computer.

  I am hoping the solution to the bug may give a better idea to the
  developers of ubuntu what happened between those kernel updates.

To manage notifications about this bug go to: