Upgrading to 10.10RC removed fglrx. After reboot X was not usable (only displaying colored dots and stripes).

[Ronald Verbeek]

Binary package hint: update-manager

Booting in recovery mode failsafe X-session was possible. Then I could reactivate / reinstall the fglrx driver. And after rebooting my laptop was OK again.

           *-display
                description: VGA compatible controller
                product: Mobility Radeon HD 3400 Series
                vendor: ATI Technologies Inc
                physical id: 0
                bus info: pci@0000:01:00.0
                version: 00
                width: 32 bits
                clock: 33MHz
                capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
                configuration: driver=fglrx_pci latency=0
                resources: irq:47 memory:c0000000-cfffffff ioport:7000(size=256) memory:d2300000-d230ffff memory:d2320000-d233ffff

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: update-manager 1:0.142.19
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Tue Oct 5 08:29:07 2010
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=nl_NL:nl
 PATH=(custom, user)
 LANG=nl_NL.utf8
 SHELL=/bin/bash
SourcePackage: update-manager

[Patrick Koppenburg (patrick-koppenburg)]

Just to say that I had the same problem (Dell XPS studio 16, ATI Mobility RADEON). Installing fglrx cured the problem. I have no evidence in my dpkg logs that I ever had this package installed (fglrx-modalias was upgraded with 10.10 though).

[bugbot (bugbot)]

Hey Ronald,

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

[Ronald Verbeek (n-launchpad-anrosil-nl)]

I am not able to reproduce this problem. (Not willing to use my production laptop to reinstall 10.04 and upgrade to 10.10 again). When I encounter the same issue again upgrading to 11.04 I will file a new bugreport.

[Robert Roth (evfool)]

Thank you for reporting this bug to Ubuntu. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

I've tried recreating this bug with Precise and was unable to, given the information you've provided. Please either a) upgrade and test or b) increase the verbosity of the steps to recreate it so we can try again.

Please feel free to report any other bugs you may find.

[Launchpad Janitor (janitor)]

[Expired for update-manager (Ubuntu) because there has been no activity for 60 days.]