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
Received shortly after boot and initial login; no other actions taken.
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
unity-system-
Installed: 0.4.3+16.
Candidate: 0.4.3+16.
Version table:
*** 0.4.3+16.
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unity-system-
ProcVersionSign
Uname: Linux 4.4.0-17-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
Date: Wed Apr 6 21:58:35 2016
ExecutablePath: /usr/sbin/
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21d1]
NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Lenovo GF106GLM [Quadro 2000M] [17aa:21d1]
InstallationDate: Installed on 2016-04-02 (5 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
ProcCmdline: /usr/sbin/
ProcEnviron:
SegvAnalysis:
Segfault happened at: 0x7f11b7423c3b: mov (%rsi),%rax
PC (0x7f11b7423c3b) ok
source "(%rsi)" (0x7f11b3146490) 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.18.1-0ubuntu1
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.