compiz crashed with SIGSEGV in ObjectPtr()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
I just installed all updates for Trusty from the past two weeks (over 300Mb to download, included updated Kernel and Unity). After restart, I got the usual LightDM log in screen. However, the desktop didn't load after logging in. Instead, I got a black screen with Apport's error message saying that there was an internal error in my system. Both Apport and Firefox that got opened by it are displayed on the screen without a window and its buttons/menus.
This issue seems to be persistent after reboots. I managed to get to the desktop by logging to tty1 and then running the startx command. Applications' windows are now visible with menus but Unity still doesn't load. Also, the desktop is shown without the background image but all files/folders are visible and right clicking on the desktop works. This bug could be related to bug 1277382 (I got a new Apport window about an Xorg crash).
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.
ProcVersionSign
Uname: Linux 3.13.0-17-generic x86_64
NonfreeKernelMo
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Sat Mar 15 22:25:46 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
InstallationDate: Installed on 2013-06-19 (269 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
ProcCmdline: compiz
SegvAnalysis:
Segfault happened at: 0x7fb5ff8baa0f <_ZN3nux11BaseT
PC (0x7fb5ff8baa0f) 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::BaseTextu
unity:
unity:
unity:
unity:
Title: compiz crashed with SIGSEGV in nux::BaseTextur
UpgradeStatus: Upgraded to trusty on 2014-02-28 (15 days ago)
UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo
description: | updated |
description: | updated |
information type: | Private → Public |
This crash has the same stack trace characteristics as bug #1286511. 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.