compiz crashed with SIGSEGV in DecorWindow::updateFrame()

Bug #945400 reported by fantab
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Compiz
Won't Fix
High
Unassigned
Compiz Core
Won't Fix
High
Unassigned
compiz (Ubuntu)
Won't Fix
High
Unassigned

Bug Description

Compiz crashed when I disabled "Snapping Windows" while enabling "Wobbly Windows". However, after CCSM was restarted or relaunched Wobbly effect is working.

(I don't know if this is a "security vulnerablity", anyways I have reported this as such.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.4.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.94-0ubuntu1
Architecture: amd64
Date: Sat Mar 3 10:29:17 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_IN:en
 LANG=en_IN
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f4375517a2f <_ZN11DecorWindow11updateFrameEv+47>: mov (%rax),%ecx
 PC (0x7f4375517a2f) ok
 source "(%rax)" (0x00000328) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 DecorWindow::updateFrame() () from /usr/lib/compiz/libdecor.so
 DecorScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libdecor.so
 CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20120216
 PlaceScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libplace.so
 CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20120216
Title: compiz crashed with SIGSEGV in DecorWindow::updateFrame()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
fantab (fantab) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 DecorWindow::updateFrame (this=0x4bb7d80) at /build/buildd/compiz-0.9.7.0~bzr2995/plugins/decor/src/decor.cpp:1658
 DecorScreen::handleEvent (this=<optimized out>, event=0x58a1a20) at /build/buildd/compiz-0.9.7.0~bzr2995/plugins/decor/src/decor.cpp:2471
 CompScreen::handleEvent (this=0x2076910, event=<optimized out>) at /build/buildd/compiz-0.9.7.0~bzr2995/src/event.cpp:996
 PlaceScreen::handleEvent (this=0x4be8ec0, event=0x58a1a20) at /build/buildd/compiz-0.9.7.0~bzr2995/plugins/place/src/place.cpp:209
 CompScreen::handleEvent (this=0x2076910, event=<optimized out>) at /build/buildd/compiz-0.9.7.0~bzr2995/src/event.cpp:996

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
tags: removed: need-amd64-retrace
visibility: private → public
affects: unity (Ubuntu) → compiz (Ubuntu)
Changed in compiz-core:
importance: Undecided → High
Changed in compiz (Ubuntu):
importance: Medium → High
Changed in compiz:
importance: Undecided → High
Stephen M. Webb (bregma)
Changed in compiz-core:
status: New → Won't Fix
tags: added: plugin-decor
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 compiz:
status: New → Won't Fix
Changed in compiz (Ubuntu):
status: New → 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.