unity-system-compositor crashed with SIGSEGV in __gxx_personality_v0()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-system-compositor (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Optimus Nvidia Intel
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unity-system-
Uname: Linux 4.4.5-040405-
NonfreeKernelMo
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Fri Mar 11 08:45:35 2016
ExecutablePath: /usr/sbin/
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0504]
NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] GF119M [GeForce GT 520M] [1025:0505]
InstallationDate: Installed on 2015-12-06 (95 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151206)
ProcCmdline: /usr/sbin/
ProcEnviron:
SegvAnalysis:
Segfault happened at: 0x35e3e8cc3b: mov (%rsi),%rax
PC (0x35e3e8cc3b) ok
source "(%rsi)" (0x7f842385a490) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity-system-
StacktraceTop:
?? () from /usr/lib/
__gxx_
_Unwind_
_Unwind_
__cxa_rethrow () from /usr/lib/
Title: unity-system-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
version.libdrm: libdrm2 2.4.67-1
version.lightdm: lightdm 1.17.5-0ubuntu2
version.mesa: libegl1-mesa-dev N/A
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1553549, 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.