gnome-font-viewer crashed with SIGSEGV

Bug #1337727 reported by dino99
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-font-viewer (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Got that crash from nautilus after right clicking on the wingdings font to view it

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: gnome-font-viewer 3.12.0-1
ProcVersionSignature: Ubuntu 3.16.0-1.3-generic 3.16.0-rc3
Uname: Linux 3.16.0-1-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.4-0ubuntu1
Architecture: i386
CurrentDesktop: GNOME
Date: Fri Jul 4 08:24:26 2014
ExecutablePath: /usr/bin/gnome-font-viewer
ProcCmdline: gnome-font-viewer /home/username/.wine/drive_c/windows/Fonts/Wingdings.TTF
SegvAnalysis:
 Segfault happened at: 0xb69bd9e6 <__strlen_sse2_bsf+22>: movdqu (%edi),%xmm1
 PC (0xb69bd9e6) ok
 source "(%edi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-font-viewer
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
Title: gnome-font-viewer crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo

Revision history for this message
dino99 (9d9) wrote :
information type: Private → Public
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 : StacktraceTop.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-font-viewer (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
dino99 (9d9) wrote :

Does not crash now

Changed in gnome-font-viewer (Ubuntu):
status: New → Invalid
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.