unity_support_test crashed with SIGSEGV in __libc_start_main()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
unuty_support_test crashed with SIGSEGV in __libc_start_main() right after rebooting the Client without taking any actions at all.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nux-tools 1.14.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-11-
ApportVersion: 1.23-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Fri Sep 30 15:44:34 2011
DistUpgraded: Fresh install
DistroCodename: oneiric
DistroVariant: ubuntu
ExecutablePath: /usr/lib/
MachineType: LENOVO 7663PJG
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdline: /usr/lib/
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/false
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x8048ed2: movzbl (%esi,%eax,1),%ebx
PC (0x08048ed2) ok
source "(%esi,%eax,1)" (0x00000003) not located in a known VMA region (needed readable region)!
destination "%ebx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
?? ()
__libc_start_main () from /lib/i386-
?? ()
Title: unity_support_test crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 04/08/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETC7WW (2.27 )
dmi.board.name: 7663PJG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 7663PJG
dmi.product.
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.6+
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 #810182, 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.