compiz crashed with SIGSEGV in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This crash happened in the wake of changing a setting in CCSM, then reverting it. That seemed to go fine, and compiz restarted each time. The crash was about half an hour later . Maybe that's way off; I just associate CCSM with starting trouble, by now. :-/ Whether that was related, at any rate, I hit Ctrl-Alt-Tab, to switch to a window in another workspace. A minute later I hit it again to switch back and the screen was unresponsive. Compiz restarted and apport came up.
Launchpad offered so many possible dupes that I didn't know what to choose. So I'm filing it, and hoping the retracer may help with that. Thanks.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: unity 6.4.0-0ubuntu6
ProcVersionSign
Uname: Linux 3.5.0-14-generic x86_64
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 11 02:13:15 2012
ExecutablePath: /usr/bin/compiz
ProcCmdline: compiz
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fb68360d82b <_ZNSsC2ERKSs+11>: mov -0x8(%rax),%esi
PC (0x7fb68360d82b) ok
source "-0x8(%rax)" (0x00000009) not located in a known VMA region (needed readable region)!
destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
std::basic_
unity:
?? () from /usr/lib/
g_main_dispatch (context=0x12da000) at /build/
g_main_
Title: compiz crashed with SIGSEGV in std::basic_
UpgradeStatus: Upgraded to quantal on 2012-06-14 (88 days ago)
UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1048274, so it 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. Feel free to continue to report any other bugs you may find.