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
Installed 16.04. Tried Unity 8 LXR, also the MIR version, and both hang on the login screen if that window managed is chosen. Only a shutdown is possible. Next Unity 7 login gives this error report.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unity-system-
ProcVersionSign
Uname: Linux 4.4.0-18-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Apr 11 19:54:56 2016
ExecutablePath: /usr/sbin/
GraphicsCard:
Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:146a]
InstallationDate: Installed on 2016-01-18 (83 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcCmdline: /usr/sbin/
ProcEnviron:
SegvAnalysis:
Segfault happened at: 0x7fd8dc59ac3b: mov (%rsi),%rax
PC (0x7fd8dc59ac3b) ok
source "(%rsi)" (0x7fd8d62c0668) 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: Upgraded to xenial on 2016-04-08 (3 days ago)
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.