package fglrx 2:8.780-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fglrx-installer (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
install in usb
ProblemType: Package
DistroRelease: Ubuntu 10.10
Package: fglrx 2:8.780-0ubuntu2
ProcVersionSign
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
DRM.card0.
status: disconnected
enabled: disabled
dpms: On
modes:
edid-base64:
DRM.card0.LVDS.1:
status: connected
enabled: enabled
dpms: On
modes: 1366x768 1280x720 1152x768 1024x768 800x600 848x480 720x480 640x480
edid-base64:
DRM.card0.VGA.1:
status: disconnected
enabled: disabled
dpms: On
modes:
edid-base64:
Date: Sun Oct 17 16:17:35 2010
DkmsStatus:
ErrorMessage: subprocess installed post-installation script returned error exit status 1
GdmLog1: Error: command ['cat', '/var/log/
GdmLog2: Error: command ['cat', '/var/log/
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: Acer Aspire 5740
ProcCmdLine: noprompt cdrom-detect/
SourcePackage: fglrx-installer
Title: package fglrx 2:8.780-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
dmi.bios.date: 11/26/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.09
dmi.board.name: Aspire 5740
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: Aspire 5740
dmi.product.
dmi.sys.vendor: Acer
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: maverick
architecture: i686
kernel: 2.6.35-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 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.