compiz crashed with SIGSEGV in empty() from check_selection() [unity-rvgrid-accessible.cpp:171]

Bug #962581 reported by Tim
200
This bug affects 23 people
Affects Status Importance Assigned to Milestone
Unity
Fix Released
High
Unassigned
5.0
Confirmed
High
Unassigned
6.0
Won't Fix
High
Unassigned
unity (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

on update today

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.6.0-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
Date: Thu Mar 22 14:41:58 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201)
ProcCmdline: compiz
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
Title: compiz crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Tim (swearingen-tim) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 empty (this=<optimized out>) at /usr/include/sigc++-2.0/sigc++/functors/slot_base.h:273
 operator() (this=0x6ea3070) at /usr/include/sigc++-2.0/sigc++/functors/slot.h:439
 operator std::basic_string<char> (this=0x6ea3058) at /usr/include/Nux-2.0/NuxCore/Property-inl.h:142
 check_selection (self=0x7fe9d402fd80) at /build/buildd/unity-5.6.0/plugins/unityshell/src/unity-rvgrid-accessible.cpp:171
 check_selection_on_idle (data=0x7fe9d402fd80) at /build/buildd/unity-5.6.0/plugins/unityshell/src/unity-rvgrid-accessible.cpp:234

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity (Ubuntu):
importance: Undecided → Medium
summary: - compiz crashed with SIGSEGV in g_main_context_dispatch()
+ compiz crashed with SIGSEGV in empty()
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: compiz crashed with SIGSEGV in empty()

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

Changed in unity (Ubuntu):
status: New → Confirmed
visibility: private → public
summary: - compiz crashed with SIGSEGV in empty()
+ compiz crashed with SIGSEGV in empty() from check_selection() [unity-
+ rvgrid-accessible.cpp:171]
Changed in unity:
status: New → Confirmed
milestone: none → 5.12.0
Changed in unity:
importance: Undecided → High
Changed in unity:
milestone: 5.12.0 → 5.14.0
Changed in unity:
milestone: 5.14.0 → 5.16.0
tags: added: quantal running-unity
Changed in unity:
milestone: 5.16.0 → 6.4
Changed in unity:
milestone: 6.4 → 6.6
Changed in unity:
milestone: 6.6 → 7.0
Revision history for this message
jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount) wrote :

Indeed, this appears to have been introduced to an update a while ago as I've had frequent instances of crashing since the last batch of compiz/unity updates.

If it helps any, I've moved on to Unity in -proposed (5.16.0-0ubuntu1) and the issue still remains.

Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

Putting back on the 6 series, still a popular crash for quantal.

Changed in unity:
milestone: 7.0.0 → 6.14.0
Michal Hruby (mhr3)
tags: added: apport-request-retrace
Changed in unity:
milestone: 6.14.0 → 7.0.0
Revision history for this message
jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount) wrote :

Hate to be a bother but does the move to the 7 series mean that this fix won't be backported to precise? would be a shame as it's a rather frequent crash.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

It wasn't meant to "move". I've added the 5 series back in for precise. All affected series should be shown for accuracy even if some of them don't get fixes.

Revision history for this message
Apport retracing service (apport) wrote : Updated stack trace from duplicate bug 1124231

Package: unity 5.18.0-0ubuntu2
ProcCmdline: compiz

Revision history for this message
Apport retracing service (apport) wrote : Dependencies.txt
Revision history for this message
Apport retracing service (apport) wrote : ProcMaps.txt
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: removed: apport-request-retrace
Stephen M. Webb (bregma)
Changed in unity:
milestone: 7.0.0 → 7.0.1
tags: added: bugpattern-needed
Revision history for this message
christopherbalz (christophermbalz) wrote :

On Unity, this problem affects users who also use Mac a lot: By accidentally pressing the Meta system key with a modifier key under certain unknown conditions, it is possible to confuse the Unity Lens such that this issue is triggered.

Revision history for this message
Frank Bicknell (fbicknel) wrote :

@christopherbalz: it's nice to know that: I'll try to pay more attention when using the meta key. (But I'm not a Mac user: I just [over] use the meta key a lot. :) )

Changed in unity:
milestone: 7.0.1 → 7.3.1
Revision history for this message
Andrea Azzarone (azzar1) wrote :

Should be fixed in most recent unity releases.

Changed in unity:
status: Confirmed → Fix Released
Changed in unity (Ubuntu):
status: Confirmed → Fix Released
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.