package fglrx (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

[nachiket]

What is going on UBUNTU??

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx (not installed)
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
AptOrdering:
 fglrx: Install
 fglrx: Configure
 fglrx-amdcccle: Configure
 fglrx-kernel-source: Configure
 xorg-driver-fglrx: Configure
Architecture: i386
BootDmesg:

Date: Thu Jun 10 19:35:33 2010
ErrorMessage: subprocess new pre-installation script returned error exit status 1
GdmLog1:

MachineType: LENOVO 4058CTO
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: root=UUID=30d2d6ae-bb3a-424b-96d5-acb3e075be74 ro single
SourcePackage: fglrx-installer
Title: package fglrx (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
XorgLog:

dmi.bios.date: 10/30/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 6FET50WW (1.20 )
dmi.board.name: 4058CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6FET50WW(1.20):bd10/30/2008:svnLENOVO:pn4058CTO:pvrThinkPadW500:rvnLENOVO:rn4058CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4058CTO
dmi.product.version: ThinkPad W500
dmi.sys.vendor: LENOVO
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-22-generic

[Jean-Baptiste Lallement (jibel)]

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 565407, 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.