compiz crashed with SIGSEGV in gray_render_scanline()

Bug #1273693 reported by Eder Andrés Ávila Niño
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Unity
Won't Fix
Medium
Unassigned
unity (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

I'm testing the development brach Ubuntu 14.04 Unity. Frozeen Screen when typing into the Ubuntu Dash.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20131106.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
Uname: Linux 3.13.0-5-generic x86_64
ApportVersion: 2.13.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jan 28 08:45:07 2014
ExecutablePath: /usr/bin/compiz
InstallationDate: Installed on 2014-01-28 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140127.1)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x7fbcd0a4a5a8: add %rdx,0x48(%r14)
 PC (0x7fbcd0a4a5a8) ok
 source "%rdx" ok
 destination "0x48(%r14)" (0x00000049) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL 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
 FT_Outline_Decompose () 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 in FT_Outline_Decompose()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Eder Andrés Ávila Niño (ederandresan) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gray_render_scanline (worker=0x1, worker@entry=0x22b8bd0, ey=ey@entry=3, x1=x1@entry=9151, y1=-288, y1@entry=256, x2=x2@entry=9792, y2=y2@entry=48) at /build/buildd/freetype-2.5.2/freetype-2.5.2/src/smooth/ftgrays.c:753
 gray_render_line (worker=0x22b8bd0, to_x=9792, to_y=816) at /build/buildd/freetype-2.5.2/freetype-2.5.2/src/smooth/ftgrays.c:901
 gray_line_to (to=<optimized out>, worker=<optimized out>) at /build/buildd/freetype-2.5.2/freetype-2.5.2/src/smooth/ftgrays.c:1200
 FT_Outline_Decompose (outline=outline@entry=0x22b92f8, func_interface=func_interface@entry=0x7fbcd0c8cde0 <func_interface>, user=user@entry=0x22b8bd0) at /build/buildd/freetype-2.5.2/freetype-2.5.2/src/base/ftoutln.c:161
 gray_convert_glyph_inner (worker=worker@entry=0x22b8bd0) at /build/buildd/freetype-2.5.2/freetype-2.5.2/src/smooth/ftgrays.c:1791

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity (Ubuntu):
importance: Undecided → Medium
summary: - compiz crashed with SIGSEGV in FT_Outline_Decompose()
+ compiz crashed with SIGSEGV in gray_render_scanline()
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity (Ubuntu):
status: New → Confirmed
Changed in unity:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Will Cooke (willcooke) wrote :

As part of the big bug clear up for 16.04 LTS I am marking this bug as Wont Fix. These types of crasher are better handled by errors.ubutnu.com which can collate similar crash reports to help us identify persitent bugs rather than one-off crashes. Sorry we are not able to help with this specific issue. If you are still experiencing this crash, please re-open the bug and add the tag “desktop-bugscrub-reopen”. See https://wiki.ubuntu.com/BigDesktopBugScrub for more information.

Changed in unity:
status: Confirmed → Won't Fix
Changed in unity (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.