parole crashed with SIGSEGV in cogl_matrix_entry_ref()

[Set Hallstrom]

Crashed when started from the whisker menu. Looks like there are similar bugs with SIGSEV, but none "in cogl_matrix_entry_ref()"

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: parole 0.8.1-1ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-7.22-lowlatency 4.4.2
Uname: Linux 4.4.0-7-lowlatency x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CasperVersion: 1.367
CurrentDesktop: XFCE
Date: Fri Feb 26 08:31:07 2016
ExecutablePath: /usr/bin/parole
LiveMediaBuild: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
ProcCmdline: parole
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f94da97c018 <cogl_matrix_entry_ref+8>: addl $0x1,0xc(%rdi)
 PC (0x7f94da97c018) ok
 source "$0x1" ok
 destination "0xc(%rdi)" (0x000002a4) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: parole
StacktraceTop:
 cogl_matrix_entry_ref () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
 cogl_matrix_stack_new () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
 cogl_onscreen_new () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
Title: parole crashed with SIGSEGV in cogl_matrix_entry_ref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo

[Set Hallstrom (sakrecoer)]

Not sure why this bug became private... I doubt it contains sensitive information since it was repported from a liveMedia boot.

[Apport retracing service (apport)]

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 #1548079, 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.