Xorg crashed with SIGSEGV in xf86WcmInitTablet()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Tried installing n-trig drivers, then the laptop shut itself down and jumped off a cliff and wouldn't boot again after.
ProblemType: Crash
Architecture: amd64
Date: Sun Nov 1 23:24:08 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/Xorg
MachineType: Hewlett-Packard HP TouchSmart tx2 Notebook PC
NonfreeKernelMo
Package: xserver-xorg-core 2:1.6.4-2ubuntu4 [modified: usr/lib/
ProcCmdLine: root=UUID=
ProcCmdline: /usr/bin/X :0 -br -verbose -auth /var/run/
ProcEnviron:
LANG=en_CA.UTF-8
PATH=(custom, no user)
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: 0x7f1b326ebba1 <xf86WcmInitTab
PC (0x7f1b326ebba1) ok
source "*0x8(%rbx)" ok
Reason could not be automatically determined.
Signal: 11
SourcePackage: xorg-server
StacktraceTop:
xf86WcmInitTablet ()
xf86WcmOpen ()
?? () from /usr/lib/
?? () from /usr/lib/
ActivateDevice ()
Title: Xorg crashed with SIGSEGV in xf86WcmInitTablet()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups:
dmi.bios.date: 05/13/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.14
dmi.board.
dmi.board.name: 3045
dmi.board.vendor: Quanta
dmi.board.version: 16.0B
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP TouchSmart tx2 Notebook PC
dmi.product.
dmi.sys.vendor: Hewlett-Packard
system:
distro: Ubuntu
architecture: x86_64kernel: 2.6.31-14-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 #410478, 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.