Installing and then removing the proprietary radeon (fglrx) driver breaks unity

[Simon Strandman]

My graphics card (radeon 6300) was working with the open source driver included in onieric, but I decieded to try the proprietary driver by enabling it in jockey. Unfortunalty it was slower and broke suspend so I used jockey to remove it again. After that unity wouldn't work anymore. I just got an empty desktop with the top panel and menu bar visible but nothing else. I tried purging the config files related to fglrx and reinstalling the open source driver but it didn't work. I had to switch to a tty and reinstall fglrx to get the desktop back.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: jockey-gtk 0.9.4-0ubuntu7
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: wl fglrx
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Sun Sep 25 19:49:36 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 305U1A
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-11-generic root=UUID=f482c414-bb8a-4614-9343-f1f0d38abd64 ro quiet splash vt.handoff=7
SourcePackage: jockey
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/29/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 01PS.M002.20110729.LEO
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 305U1A/305U1A
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: 01PS
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr01PS.M002.20110729.LEO:bd07/29/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn305U1A:pvr01PS:rvnSAMSUNGELECTRONICSCO.,LTD.:rn305U1A/305U1A:rvr01PS:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: 305U1A
dmi.product.version: 01PS
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

[Launchpad Janitor (janitor)]

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