compiz crashed with SIGSEGV in std::__detail::_List_node_base::_M_hook()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
it has been wile I was choosing the driver
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity 4.20.0-0ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Tue Oct 4 15:23:52 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: compiz
ProcEnviron:
LANG=it_IT.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f93c731d263 <_ZNSt8_
PC (0x7f93c731d263) ok
source "%rdi" ok
destination "(%rax)" (0x00000020) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
std::_
LauncherIcon:
BamfLauncherIc
?? () from /lib/x86_
g_main_
Title: compiz crashed with SIGSEGV in std::__
UpgradeStatus: Upgraded to oneiric on 2011-10-04 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare
XsessionErrors:
(gnome-
(gnome-
(nautilus:1917): Gtk-CRITICAL **: gtk_action_
(nautilus:1917): Gtk-CRITICAL **: gtk_action_
(gwibber-
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #863534, 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.