amdcccle crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fglrx-installer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
AMDCCLE crashed after trying to enable Multidesktop-Mode with a dual monitor setup. The displays are a Eizo S2231W 1680x1050 and a DELL U2311H 1920x1080.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: fglrx-amdcccle 2:8.881-0ubuntu3
ProcVersionSign
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Wed Oct 5 21:47:56 2011
DistUpgraded: Fresh install
DistroCodename: oneiric
DistroVariant: ubuntu
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20111003)
MachineType: Gigabyte Technology Co., Ltd. GA-MA790XT-UD4P
ProcCmdline: amdcccle
ProcEnviron:
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x5886f4: cmp 0x10(%rbx),%r12d
PC (0x005886f4) ok
source "0x10(%rbx)" (0x00000010) not located in a known VMA region (needed readable region)!
destination "%r12d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: fglrx-installer
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()
Title: amdcccle crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 07/12/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F8g
dmi.board.name: GA-MA790XT-UD4P
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: GA-MA790XT-UD4P
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.6+
version.ia32-libs: ia32-libs 20090808ubuntu25
version.libdrm2: libdrm2 2.4.26-1ubuntu1
version.
version.
version.
version.
version.
version.
version.
version.
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #647802, so 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.