This makes compiz unable to start in the latest ubuntu trusty.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20131106.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
Uname: Linux 3.13.0-7-generic x86_64
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Feb 6 13:58:10 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
ExecutableTimestamp: 1391532994
InstallationDate: Installed on 2012-11-25 (438 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627)
ProcCmdline: compiz
ProcCwd: /home/shankao
ProcEnviron:
LANGUAGE=en_SG:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_SG.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fba5e698f9f <_ZN3nux11BaseTexture16GetDeviceTextureEv+127>: mov 0xb0(%rbx),%rax
PC (0x7fba5e698f9f) ok
source "0xb0(%rbx)" (0x000000b0) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
nux::BaseTexture::GetDeviceTexture() () from /usr/lib/x86_64-linux-gnu/libnux-graphics-4.0.so.0
unity::PanelView::PanelView(unity::MockableBaseWindow*, std::shared_ptr<unity::indicator::DBusIndicators> const&, char const*, int) () from /usr/lib/compiz/libunityshell.so
unity::panel::Controller::Impl::CreatePanel(unity::debug::Introspectable*) () from /usr/lib/compiz/libunityshell.so
unity::panel::Controller::Impl::OnScreenChanged(unsigned int, std::vector<nux::Rect, std::allocator<nux::Rect> >&, unity::debug::Introspectable*) () from /usr/lib/compiz/libunityshell.so
unity::panel::Controller::Controller(std::shared_ptr<unity::ui::EdgeBarrierController> const&) () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in nux::BaseTexture::GetDeviceTexture()
UpgradeStatus: Upgraded to trusty on 2013-10-23 (106 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
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 #1277826, 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.