compiz crashed with SIGSEGV in unity::QuicklistView::ShowQuicklistWithTipAt()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I have experienced this crash several times, under Unity 6.10 and 6.12. Each time, I think, it's been triggered by using the Launcher's workspace switcher. Compiz relaunches succesfully (after some delay). I think this is probably a dupe of bug 972616, but I'd like to see the retracer go to work on it.
I deleted the xsession-errors file, as it had a lot of filenames and other information in it, and only these relevant lines:
gnome-
gnome-
gnome-
which seem like no surprise.
Thanks.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: unity 6.12.0-0ubuntu4
ProcVersionSign
Uname: Linux 3.7.0-3-lowlatency x86_64
ApportVersion: 2.6.2-0ubuntu5
Architecture: amd64
Date: Sat Nov 24 17:53:47 2012
ExecutablePath: /usr/bin/compiz
MarkForUpload: True
ProcCmdline: compiz
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fc66f967e59 <_ZN5unity13Qui
PC (0x7fc66f967e59) ok
source "$0x0" ok
destination "0x5c5(%rdi)" (0xf0000076e) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
unity:
unity:
?? () from /usr/lib/
sigc::
PluginAdapter:
Title: compiz crashed with SIGSEGV in unity::
UpgradeStatus: Upgraded to raring on 2012-06-14 (163 days ago)
UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #972616, 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.