Ubuntu
unity package

compiz crashed with SIGSEGV

Bug #1287081 reported by Daniel Burke on 2014-03-03

This bug report is a duplicate of: Bug #1199571: Huge multi-threading violations in freetype. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	unity (Ubuntu)	New	Undecided	Unassigned

Bug Description

Just enabled the ATi driver from ubuntu-updates using the GUI tool.

Opened dash to see if the AMd control centre was installed and it crashed before I got more than 1 letter typed in.

Machine is a laptop with Intel Ivy Bridge+ATi 7670M

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140228-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
Uname: Linux 3.13.0-14-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Mar 3 20:24:55 2014
ExecutablePath: /usr/bin/compiz
InstallationDate: Installed on 2014-03-03 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140128)
ProcCmdline: compiz
ProcEnviron:
LANGUAGE=en_AU:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_AU.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fc683176d7d: mov %rax,(%rcx)
PC (0x7fc683176d7d) ok
source "%rax" ok
destination "(%rcx)" (0x7fc66810c010) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
Title: compiz crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

Daniel Burke (burkey) wrote on 2014-03-03:

Dependencies.txt Edit (30.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel Burke (burkey) wrote on 2014-03-03:

On reboot Unity failed to load, dropped to a console and ran

aticonfig --initial

Seems to be working again, however performance is very poor (just testing wine + World of Warcraft) and vsync is stuck OFF so everything tears and is horrible.

OT: Previous to this, WoW was running 15fps on the MESA driver (Intel chip) and using fglrx pushes 17fps

Revision history for this message

Apport retracing service (apport) wrote on 2014-03-07: This bug is a duplicate

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 #931389, 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.