accenn shotdwn
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fglrx-installer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
1
ProblemType: Crash
Architecture: amd64
Date: Thu Oct 29 20:05:44 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/amdcccle
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: System manufacturer System Product Name
Package: fglrx-amdcccle 2:8.660-0ubuntu4
ProcCmdLine: root=UUID=
ProcCmdline: amdcccle
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
xserver-xorg 1:7.4+3ubuntu7
libgl1-mesa-glx 7.6.0-1ubuntu4
libdrm2 2.4.14-1ubuntu1
xserver-
xserver-
SegvAnalysis:
Segfault happened at: 0x7fc38c075bee <_XSend+30>: mov (%rax),%rdx
PC (0x7fc38c075bee) ok
source "(%rax)" (0x00001390) not located in a known VMA region (needed readable region)!
destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: fglrx-installer
StacktraceTop:
_XSend () from /usr/lib/
XQueryExtension () from /usr/lib/
XInitExtension () from /usr/lib/
XextAddDisplay () from /usr/lib/
?? () from /usr/lib/libGL.so.1
Title: amdcccle crashed with SIGSEGV in _XSend()
Uname: Linux 2.6.28-15-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
(gnome-
(gnome-
(polkit-
(nautilus:2389): Eel-CRITICAL **: eel_preferences
dmi.bios.date: 04/21/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0707
dmi.board.
dmi.board.name: P5Q3
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
fglrx: Not loaded
system:
distro: Ubuntu
architecture: x86_64kernel: 2.6.28-15-generic
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 #452738, 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.