package fglrx 2:8.723.1-0ubuntu3 failed to remove (synaptic reports software index broken)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fglrx-installer (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: fglrx
fglrx package cannot be removed - synaptic reports software index broken and does not perfrorm any action
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu3
ProcVersionSign
Uname: Linux 2.6.32-22-generic i686
NonfreeKernelMo
AptOrdering: fglrx: Remove
Architecture: i386
Date: Mon Jun 28 22:08:46 2010
DkmsStatus:
bcmwl, 5.60.48.36+bdcom, 2.6.31-21-generic, i686: installed
bcmwl, 5.60.48.36+bdcom, 2.6.32-22-generic, i686: installed
fglrx, 8.732, 2.6.32-22-generic, i686: installed
ErrorMessage: subprocess installed post-removal script returned error exit status 2
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: Hewlett-Packard HP Compaq 6730s
ProcCmdLine: BOOT_IMAGE=
SourcePackage: fglrx-installer
Title: package fglrx 2:8.723.1-0ubuntu3 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2
dmi.bios.date: 12/15/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PZD Ver. F.09
dmi.board.name: 30E9
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 95.1B
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Compaq 6730s
dmi.product.
dmi.sys.vendor: Hewlett-Packard
glxinfo: Error: command ['glxinfo'] failed with exit code -11:
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-22-generic
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 566437, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.