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
Tried to install the new Nvidia driver from their site, wanted to test it in Mir. But the system became unusable so I rolled back to the OS drivers
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unity-system-
ProcVersionSign
Uname: Linux 4.4.0-15-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Wed Mar 23 00:21:08 2016
ExecutablePath: /usr/sbin/
GraphicsCard:
Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller])
Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
Subsystem: Lenovo GM108M [GeForce 840M] [17aa:3817]
InstallationDate: Installed on 2015-06-18 (279 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/sbin/
ProcEnviron:
SegvAnalysis:
Segfault happened at: 0x7f90fe3c1c5b: mov (%rsi),%rax
PC (0x7f90fe3c1c5b) ok
source "(%rsi)" (0x7f90fa506490) 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-
UnitySystemComp
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options.
/usr/bin/
kill -l [exitstatus]
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
version.libdrm: libdrm2 2.4.67-1
version.lightdm: lightdm 1.18.0-0ubuntu1
version.mesa: libegl1-mesa-dev 11.1.2-1ubuntu2
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.