compiz crashed with SIGSEGV in CompWindow::move()

Bug #902991 reported by Helge Jung
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Unity
Invalid
Medium
Unassigned
notify-osd (Ubuntu)
Expired
Medium
Unassigned
unity (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

When moving an empathy window some fancy window-resize bubbles appeared at the side of the window and did not respond at all - like the rest of the whole desktop. Several seconds after, I suppose some watchdog stepped in and killed unity.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity 4.24.0-0ubuntu2b1
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
Uname: Linux 3.0.0-13-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Mon Dec 12 01:14:17 2011
Disassembly: => 0x80000001d: Cannot access memory at address 0x80000001d
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x80000001d: Cannot access memory at address 0x80000001d
 PC (0x80000001d) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? ()
 CompWindow::move(int, int, bool) ()
 GestureEngine::OnDragUpdate(GeisAdapter::_GeisDragData*) () from /usr/lib/compiz/libunityshell.so
 GeisAdapter::GestureUpdate(void*, unsigned int, unsigned int, unsigned long, GeisGestureAttr*) () from /usr/lib/compiz/libunityshell.so
 ?? () from /usr/lib/libutouch-geis.so.1
Title: compiz crashed with SIGSEGV in CompWindow::move()
UpgradeStatus: Upgraded to oneiric on 2011-10-15 (57 days ago)
UserGroups: adm admin cdrom chipcard dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
Helge Jung (youngage) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 CompWindow::move (this=0x5d64120, dx=38, dy=5, immediate=false) at /build/buildd/compiz-0.9.6+bzr20110929/src/window.cpp:2183
 OnDragUpdate (data=<optimized out>, this=0x4167ce0) at /build/buildd/unity-4.24.0/plugins/unityshell/src/GestureEngine.cpp:169
 GestureEngine::OnDragUpdate (this=0x4167ce0, data=<optimized out>) at /build/buildd/unity-4.24.0/plugins/unityshell/src/GestureEngine.cpp:151
 emit (_A_a1=@0x7fff9ebf7798, impl=<optimized out>) at /usr/include/sigc++-2.0/sigc++/signal.h:1010

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
Changed in unity (Ubuntu):
importance: Medium → Critical
Revision history for this message
Bilal Akhtar (bilalakhtar) wrote :

From the stacktrace, it seems like a 3 finger drag was registered by Unity over a window and compiz was given the command to move the window.

Did you mistakenly make that 3 finger tap/drag over the Empathy notification? That could explain a lot about the crash itself.

visibility: private → public
Revision history for this message
Helge Jung (youngage) wrote :

Yes, that could be.

I just tried it out, when using three fingers on my touchpad to move a window these bubbles appear - I did not know these bubbles and did not know how to trigger them. I cannot reproduce the crash itself, though.

Andrea Azzarone (azzar1)
Changed in unity:
status: New → Confirmed
Changed in notify-osd (Ubuntu):
status: New → Confirmed
Changed in unity (Ubuntu):
status: New → Confirmed
Changed in notify-osd (Ubuntu):
status: Confirmed → New
Changed in unity:
importance: Undecided → High
milestone: none → 5.12.0
Changed in unity:
milestone: 5.12.0 → 5.14.0
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in notify-osd (Ubuntu):
status: New → Confirmed
Omer Akram (om26er)
Changed in unity (Ubuntu):
importance: Critical → High
Changed in unity:
importance: High → Medium
Changed in notify-osd (Ubuntu):
importance: Undecided → Medium
Changed in unity (Ubuntu):
importance: High → Medium
Revision history for this message
Omer Akram (om26er) wrote :

Thanks for taking time to report this bug and helping to make ubuntu better. Its been a while since this bug was reported, there have been alot of changes in Unity since then. Can you please test with Ubuntu 12.04 with all updates installed and let us know if the issue is still there.

Changed in unity:
status: Confirmed → Incomplete
Changed in notify-osd (Ubuntu):
status: Confirmed → Incomplete
Changed in unity (Ubuntu):
status: Confirmed → Incomplete
Changed in unity:
milestone: 5.14.0 → 5.16.0
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for notify-osd (Ubuntu) because there has been no activity for 60 days.]

Changed in notify-osd (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for unity (Ubuntu) because there has been no activity for 60 days.]

Changed in unity (Ubuntu):
status: Incomplete → Expired
Changed in unity:
milestone: 5.16.0 → 5.18.0
Changed in unity:
milestone: 5.18.0 → 7.0.0
milestone: 7.0.0 → backlog
Changed in unity (Ubuntu):
status: Expired → Incomplete
Andrea Azzarone (azzar1)
Changed in notify-osd (Ubuntu):
status: Expired → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for notify-osd (Ubuntu) because there has been no activity for 60 days.]

Changed in unity (Ubuntu):
status: Incomplete → Expired
Changed in notify-osd (Ubuntu):
status: Incomplete → Expired
Changed in unity (Ubuntu):
status: Expired → Incomplete
Andrea Azzarone (azzar1)
Changed in unity:
status: Incomplete → Invalid
Changed in unity (Ubuntu):
status: Incomplete → Invalid
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.