package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[nana]

It failed to install

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Sun Oct 10 12:40:06 2010
DkmsStatus:

ErrorMessage: subprocess installed post-installation script returned error exit status 1
GdmLog1: X: /tmp/.X11-unix has suspicious mode (not 1777) or is not a directory, aborting.
LiveMediaBuild: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: Hewlett-Packard HP G62 Notebook PC
ProcCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz splash -- BOOT_IMAGE=/casper/vmlinuz
SourcePackage: fglrx-installer
Title: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
dmi.bios.date: 04/27/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.07
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1444
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 69.15
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.07:bd04/27/2010:svnHewlett-Packard:pnHPG62NotebookPC:pvr0499100000242710000020000:rvnHewlett-Packard:rn1444:rvr69.15:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP G62 Notebook PC
dmi.product.version: 0499100000242710000020000
dmi.sys.vendor: Hewlett-Packard
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-21-generic

[Brian Murray (brian-murray)]

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