unity_support_test crashed with SIGSEGV in __libc_start_main()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I don't have any idea about this bug.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nux-tools 1.10.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-11-
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Tue Sep 20 08:54:56 2011
DistUpgraded: Log time: 2011-09-14 17:33:29.803732
DistroCodename: oneiric
DistroVariant: ubuntu
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-7246
ProcCmdline: /usr/lib/
ProcEnviron:
PATH=(custom, no user)
LANG=de_DE.UTF-8
LC_MESSAGES=
SHELL=/bin/false
LANGUAGE=de:en
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x8048ec2: movzbl (%esi,%eax,1),%ebx
PC (0x08048ec2) 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: Upgraded to oneiric on 2011-09-14 (8 days ago)
UserGroups:
dmi.bios.date: 11/03/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: V7.9
dmi.board.name: MS-7246
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.board.version: 2.1
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: MS-7246
dmi.product.
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
version.compiz: compiz 1:0.9.5.
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.