compiz crashed with SIGSEGV in std::__detail::_List_node_base::_M_hook() from unity::ui::PointerBarrierWrapper::EmitCurrentData
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
Fix Released
|
High
|
Andrea Azzarone | ||
Unity Distro Priority |
Fix Released
|
High
|
Unassigned | ||
unity (Ubuntu) |
Fix Released
|
High
|
Andrea Azzarone |
Bug Description
Compiz crashed hard after I unplugged an external monitor.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.4.0-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
Date: Thu Mar 1 18:23:44 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
ProcCmdline: compiz
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f36ff1aa433 <_ZNSt8_
PC (0x7f36ff1aa433) ok
source "%rdi" ok
destination "(%rax)" (0x00000440) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
std::_
unity:
?? () from /usr/lib/
?? () from /lib/x86_
g_main_
Title: compiz crashed with SIGSEGV in std::__
UpgradeStatus: Upgraded to precise on 2012-02-22 (8 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare staff
Related branches
- Thomi Richards (community): Approve
-
Diff: 39 lines (+19/-1)2 files modifiedmanual-tests/MultiMonitor.txt (+16/-1)
plugins/unityshell/src/PointerBarrier.cpp (+3/-0)
visibility: | private → public |
Changed in unity-distro-priority: | |
status: | New → Fix Committed |
importance: | Undecided → High |
Changed in unity: | |
importance: | Undecided → High |
Changed in unity (Ubuntu): | |
importance: | Medium → High |
Changed in unity: | |
status: | New → Confirmed |
tags: | added: rls-p-tracking |
summary: |
- compiz crashed with SIGSEGV in - std::__detail::_List_node_base::_M_hook(). + compiz crashed with SIGSEGV in std::__detail::_List_node_base::_M_hook() + from unity::ui::PointerBarrierWrapper::EmitCurrentData |
Changed in unity: | |
assignee: | nobody → Andrea Azzarone (andyrock) |
milestone: | none → 5.10.0 |
Changed in unity (Ubuntu): | |
assignee: | nobody → Andrea Azzarone (andyrock) |
Changed in unity: | |
status: | Confirmed → In Progress |
Changed in unity (Ubuntu): | |
status: | Confirmed → In Progress |
Changed in unity: | |
status: | In Progress → Fix Committed |
Changed in unity (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in unity: | |
status: | Fix Committed → Fix Released |
Changed in unity-distro-priority: | |
status: | Fix Committed → Fix Released |
This crash has the same stack trace characteristics as bug #863534. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.