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

Bug #1302771 reported by Zach Kraus
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

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 http://wiki.cchtml.com/index.php/Ubuntu_Saucy_Installation_Guide#Installing_Catalyst_Manually_.28from_AMD.2FATI.27s_site.29_BETA.2FEXPERIMENTAL 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.

Tags: bot-comment
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1302771/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu:
status: New → Confirmed
Markus W (z-mw)
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Zach Kraus (zachkraus) wrote :

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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.