compiz crashed with SIGSEGV in ObjectPtr() from unity::launcher::Launcher::DndReset() from unity::launcher::Launcher::OnUpdateDragManagerTimeout()

Bug #936923 reported by Tamas Papp
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Unity
Confirmed
Critical
Unassigned
Unity Distro Priority
New
Undecided
Unassigned
unity (Ubuntu)
Confirmed
Critical
Unassigned
Precise
Confirmed
Critical
Unassigned

Bug Description

I enabled Application switcher beside Static application switcher.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Feb 20 13:02:15 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
SegvAnalysis:
 Segfault happened at: 0x7fea54ffb650 <_ZN5unity8launcher8Launcher8DndResetEv+64>: mov (%rbx),%rax
 PC (0x7fea54ffb650) ok
 source "(%rbx)" (0x68800000074) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 unity::launcher::Launcher::DndReset() () from /usr/lib/compiz/libunityshell.so
 unity::launcher::Launcher::OnUpdateDragManagerTimeout(void*) () from /usr/lib/compiz/libunityshell.so
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: compiz crashed with SIGSEGV in unity::launcher::Launcher::DndReset()
UpgradeStatus: Upgraded to precise on 2011-08-27 (176 days ago)
UserGroups: adm admin bacula cdrom dialout libvirtd lpadmin plugdev sambashare

Revision history for this message
Tamas Papp (tompos) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ObjectPtr (other=<optimized out>, this=0x7fff92c0f280) at /usr/include/Nux-2.0/NuxCore/ObjectPtr.h:51
 unity::launcher::Launcher::DndReset (this=0x2e2abf0) at /build/buildd/unity-5.4.0/plugins/unityshell/src/Launcher.cpp:2575
 unity::launcher::Launcher::OnUpdateDragManagerTimeout (data=0x2e2abf0) at /build/buildd/unity-5.4.0/plugins/unityshell/src/Launcher.cpp:1431
 g_timeout_dispatch (source=0x45da660, callback=<optimized out>, user_data=<optimized out>) at /build/buildd/glib2.0-2.31.16/./glib/gmain.c:3854
 g_main_dispatch (context=0x2214160) at /build/buildd/glib2.0-2.31.16/./glib/gmain.c:2510

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 unity::launcher::Launcher::DndReset()
+ compiz crashed with SIGSEGV in ObjectPtr()
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: compiz crashed with SIGSEGV in ObjectPtr()

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

Changed in unity (Ubuntu):
status: New → Confirmed
Omer Akram (om26er)
visibility: private → public
Changed in unity (Ubuntu):
importance: Medium → High
importance: High → Critical
Changed in unity:
importance: Undecided → Critical
status: New → Confirmed
tags: added: rls-mgr-p-tracking
summary: - compiz crashed with SIGSEGV in ObjectPtr()
+ compiz crashed with SIGSEGV in ObjectPtr() from
+ unity::launcher::Launcher::DndReset() from
+ unity::launcher::Launcher::OnUpdateDragManagerTimeout()
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 931033, so it 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. Feel free to continue to report any other bugs you may find.

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.