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

Bug #938755 reported by Mario Bosco
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
New
Undecided
Unassigned

Bug Description

Non vedendo più alcune icone (Cartella home, terminale, etc.) ho avviato Compiz.
Non ho concluso nulla ma mentre stavo cercando come fare c'è stato il crash

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 i686
ApportVersion: 1.92-0ubuntu1
Architecture: i386
Date: Wed Feb 22 16:24:42 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x12f5570 <_ZN5unity8launcher8Launcher8DndResetEv+96>: mov (%esi),%edx
 PC (0x012f5570) ok
 source "(%esi)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL 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/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: compiz crashed with SIGSEGV in unity::launcher::Launcher::DndReset()
UpgradeStatus: Upgraded to precise on 2012-02-22 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin nopasswdlogin plugdev sambashare

Revision history for this message
Mario Bosco (mariobosco2010) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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

visibility: private → public
visibility: private → public
tags: removed: need-i386-retrace
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.