compiz crashed with SIGSEGV in nux::GraphicsDisplay::StartDndDrag() from nux::InputArea::StartDragAsSource() from nux::WindowCompositor::MouseEventCycle()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Nux |
Won't Fix
|
Undecided
|
Unassigned | ||
nux (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
I don't have any other information.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libnux-1.0-0 1.16.0-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-7-generic-pae i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Sun Jan 1 16:56:10 2012
DuplicateOf: https:/
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120101)
ProcCmdline: compiz
ProcEnviron:
PATH=(custom, no user)
LANG=pl_PL.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0xb3dd381b <_ZN3nux15Graph
PC (0xb3dd381b) ok
source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
nux::GraphicsD
nux::InputArea
nux::WindowCom
nux::WindowCom
nux::WindowThr
Title: compiz crashed with SIGSEGV in nux::GraphicsDi
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.