in Karmic Koala jockey-kde crashed when trying to activate ATI/AMD proprietary fglrx
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
trying to activate proprietary fglrx driver in Karmic Koala. It just hangs and never activates
ProblemType: Crash
Architecture: i386
Date: Sun Sep 13 07:19:04 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/jockey-kde
InterpreterPath: /usr/bin/python2.6
MachineType: Gigabyte Technology Co., Ltd. P35-DS3P
Package: jockey-kde 0.5.3-0ubuntu3
PackageArchitec
PccardctlIdent:
PccardctlStatus:
ProcCmdLine: root=UUID=
ProcCmdline: /usr/bin/python /usr/bin/jockey-kde
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
LANGUAGE=
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x77b80bc <_ZNK7QWidget6m
PC (0x077b80bc) ok
source "0x8(%eax)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: jockey
StacktraceTop:
QWidget:
QFont::QFont(QFont const&, QPaintDevice*) ()
QWidgetPrivate
QWidgetPrivate
QWidget:
Title: jockey-kde crashed with SIGSEGV in QWidget::metric()
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 09/07/2007
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F6
dmi.board.name: P35-DS3P
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: P35-DS3P
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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 #349419, 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.