compiz crashed with SIGSEGV in PanelMenuView::ProcessEvent()

Bug #743469 reported by graingert
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
nux (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

This is not https://bugs.launchpad.net/ubuntu/+source/nux/+bug/742139 as I was not drag and dropping an icon, I was moving a window.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libnux-0.9-0 0.9.36-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
Date: Sun Mar 27 06:15:58 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x4e46d70: adc %ebx,(%rsi)
 PC (0x04e46d70) in non-executable VMA region: 0x00ef4000-0x098ef000 rw-p [heap]
 source "%ebx" ok
 destination "(%rsi)" (0x7fffd4e8e830) ok
SegvReason: executing writable VMA [heap]
Signal: 11
SourcePackage: nux
StacktraceTop:
 ?? ()
 PanelMenuView::ProcessEvent(nux::Event&, long, long) () from /usr/lib/compiz/libunityshell.so
 nux::Layout::ProcessEvent(nux::Event&, long, long) () from /usr/lib/libnux-0.9.so.0
 nux::Layout::ProcessEvent(nux::Event&, long, long) () from /usr/lib/libnux-0.9.so.0
 nux::BaseWindow::ProcessEvent(nux::Event&, long, long) () from /usr/lib/libnux-0.9.so.0
Title: compiz crashed with SIGSEGV in PanelMenuView::ProcessEvent()
UpgradeStatus: Upgraded to natty on 2011-03-27 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
graingert (tagrain) wrote :
Revision history for this message
graingert (tagrain) wrote :

gosh: "executing writable VMA [heap]" not quite a security vuln though!

Revision history for this message
Omer Akram (om26er) wrote :

are you able to reproduce this crash? if so can you please get a backtrace by following the procedure here. else its most likely a duplicate of bug 742139 as sometimes the same crash is reproduced by different steps.

Revision history for this message
Omer Akram (om26er) wrote :

https://wiki.ubuntu.com/Backtrace <sorry the link was left behind>

Changed in nux (Ubuntu):
status: New → Incomplete
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.