compiz crashed with SIGSEGV in nux::Property<bool>::Set()

Bug #1279564 reported by Ken Harkey
100
This bug affects 11 people
Affects Status Importance Assigned to Milestone
Unity
Won't Fix
Medium
Unassigned
unity (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Happened when I tried to change the unity scopes

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20131106.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
Uname: Linux 3.13.0-8-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Feb 12 15:02:26 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
InstallationDate: Installed on 2014-02-12 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f548a56c73a: mov 0x3c0(%rax),%rax
 PC (0x7f548a56c73a) ok
 source "0x3c0(%rax)" (0x000003c0) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? () from /usr/lib/compiz/libunityshell.so
 nux::Property<bool>::Set(bool const&) () from /usr/lib/compiz/libunityshell.so
 ?? () from /usr/lib/compiz/libunityshell.so
 nux::Button::RecvClick(int, int, unsigned long, unsigned long) () from /usr/lib/x86_64-linux-gnu/libnux-4.0.so.0
 nux::InputArea::EmitMouseClickSignal(int, int, unsigned long, unsigned long) () from /usr/lib/x86_64-linux-gnu/libnux-4.0.so.0
Title: compiz crashed with SIGSEGV in nux::Property<bool>::Set()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Ken Harkey (kenny727) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? () from /tmp/apport_sandbox_nyNYqC/usr/lib/compiz/libunityshell.so
 nux::Property<bool>::Set(bool const&) () from /tmp/apport_sandbox_nyNYqC/usr/lib/compiz/libunityshell.so
 ?? () from /tmp/apport_sandbox_nyNYqC/usr/lib/compiz/libunityshell.so
 emit (_A_a1=@0x7fff5a3987c8: 0x2f84f20, impl=0x1bf9960) at /usr/include/sigc++-2.0/sigc++/signal.h:1010
 emit (this=0x2f85420, _A_a1=@0x7fff5a3987c8: 0x2f84f20) at /usr/include/sigc++-2.0/sigc++/signal.h:2781

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Changed in unity:
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity (Ubuntu):
status: New → Confirmed
Andrea Azzarone (azzar1)
information type: Private → Public
Changed in unity:
status: New → Confirmed
Revision history for this message
Øyvind Stegard (oyvindstegard) wrote :

I'm seeing segfault crashes in the same method (nux::Property<bool>::Set()) on resume from suspend, and it typically causes the lockscreen to hang for a short time, then the session dies due to the Compiz crash. After session death I'm back to login screen. This problem occurs often enough to become annoying.

I'm on Ubuntu 14.04 with LTS enablement upgrades (kernel 3.16.0-36-generic, updated Xorg) and -proposed enabled. Intel Haswell graphics.

# apt-cache policy compiz
compiz:
  Installed: 1:0.9.11.3+14.04.20150313-0ubuntu1
[...]

# apt-cache policy unity
unity:
  Installed: 7.2.4+14.04.20150316-0ubuntu1
[...]

Revision history for this message
Will Cooke (willcooke) wrote :

As part of the big bug clear up for 16.04 LTS I am marking this bug as Wont Fix.
These types of crasher are better handled by errors.ubutnu.com which can collate similar crash reports to help us identify persitent bugs rather than one-off crashes.
Sorry we are not able to help with this specific issue. If you are still experiencing this crash, please re-open the bug and add the tag "desktop-bugscrub-reopened". See https://wiki.ubuntu.com/BigDesktopBugScrub for more information.

Changed in unity:
status: Confirmed → Won't Fix
Changed in unity (Ubuntu):
status: Confirmed → Won't Fix
tags: added: desktop-bugscrub-autoclosed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.