compiz crashed with SIGABRT in raise()

[Anthony Trovarelli]

me@me2:~$ lsb_release -rd
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
me@me2:~$ apt-cache policy compiz
compiz:
  Installed: 1:0.9.12.2+16.04.20160331-0ubuntu1
  Candidate: 1:0.9.12.2+16.04.20160331-0ubuntu1
  Version table:
 *** 1:0.9.12.2+16.04.20160331-0ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
        500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
        100 /var/lib/dpkg/status
This is the MATE Beta 2 version. I was editing the Florence Virtual Keyboard settings when this popped up. I have no idea what caused it and nothing crashed. Just the apport error appeared.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: compiz-core 1:0.9.12.2+16.04.20160331-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
Uname: Linux 4.4.0-17-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: MATE
Date: Thu Apr 7 19:02:05 2016
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
InstallationDate: Installed on 2016-03-28 (11 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323.1)
ProcCmdline: compiz --replace ccp
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: compiz
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 free () from /lib/x86_64-linux-gnu/libc.so.6
Title: compiz crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[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 #1499492, 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.