Switching from Xorg to fglrx-updates and back loses 1 monitor

Bug #1450694 reported by Jeffrey Stern
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kubuntu-driver-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

i started out by posting this bug at

   https://bugs.kde.org/show_bug.cgi?id=346925

and from there was directed to re-post it at

   https://bugs.freedesktop.org/show_bug.cgi?id=90246

where a solution was provided for me (in comment 8, i.e., to go to http://askubuntu.com/questions/68306/how-do-i-remove-the-proprietary-ati-drivers) and follow the directions to repair my own system. It worked.

Now that we know where the problem happened, I have again been redirected here, and am posting here because this bug may be affecting others, and appears to derive from the Driver Manager dialog (see screenshot) or some underlying install script it uses.

The problem is:

Switching (in Driver Manager) from the Xorg Radeon video driver to the proprietary AMD Radeon fglrx video driver, and then back to the Xorg driver, left the system in a broken state. Instead, the fglrx driver was still left running and installed (even on a reboot) and the system defaulted to using a VESA generic driver (i.e., neither of the Xorg nor the fglrx drivers).

1) Ubuntu release: Kubuntu 15.04

2) Package version: kubuntu-driver-manager 15.04ubuntu3

3) What I expected to happen:

In DM, when switching back to the Xorg Radeon video driver, the Xorg driver should be restored, and the fglrx driver should not still be installed and running. The VESA default baseline driver should not be running, but the Xorg driver.

4) Returning back from the proprietary drivers should return the system to using the Xorg radeon drivers correctly and have 2 monitors running, and not have to manually go through the steps in the askubuntu solution above.

Other much more detailed information can be found at the freedesktop bug above, with the solution to repair my system. But it's a lot of info, so I won't repost it here unless the developers would like me to.

Thanks and let me know if there is any more information I can provide for you.

-JS

Revision history for this message
Jeffrey Stern (jas-61803) wrote :
Revision history for this message
Jeffrey Stern (jas-61803) wrote :

To be a bit more precise -- in DM, I switched from Xorg (which was initially working with both monitors) to fglrx-updates (the 2nd choice in the dialog box screenshot). Rebooted, ran under fglrx-updates driver a few times, then switched back to Xorg driver (and rebooted).

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.