compiz crashed with SIGSEGV in nux::WindowCompositor::MouseEventCycle()

Bug #834626 reported by Florian Greinus
90
This bug affects 21 people
Affects Status Importance Assigned to Milestone
nux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Tried to close software-center (which has crashed before) through the menu in the launcher and then everything slows down, launcher stucks and then compiz crashed...

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libnux-1.0-0 1.4.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
Architecture: i386
Date: Fri Aug 26 13:24:02 2011
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110803.1)
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 ?? ()
 nux::WindowCompositor::MouseEventCycle(nux::Event&) () from /usr/lib/libnux-1.0.so.0
 nux::WindowCompositor::ProcessEvent(nux::Event&) () from /usr/lib/libnux-1.0.so.0
 nux::WindowThread::ExecutionLoop(unsigned int) () from /usr/lib/libnux-1.0.so.0
 nux::nux_event_dispatch(_GSource*, int (*)(void*), void*) () from /usr/lib/libnux-1.0.so.0
Title: compiz crashed with SIGSEGV in nux::WindowCompositor::MouseEventCycle()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Florian Greinus (florian-greinus) wrote :
Changed in nux (Ubuntu):
status: New → Confirmed
Revision history for this message
TheMiddaySun (themiddaysun) wrote :

received this error when trying to pin terminal to the launcher

Revision history for this message
Peter Silva (peter-bsqt) wrote :

received this error when trying to pin system-settings to the launcher. after compiz restart, repeated the operation and it worked on the second try.

Revision history for this message
D (tenswiths) wrote :

In the 15 minutes before I got this error, the dash would appear behind all windows whenever I opened it. Immediately before the error, I was unmounting a USB drive through its launcher menu. The launcher disappeared, but the menu remained, and the system became unresponsive for five seconds before compiz restarted itself.

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.