After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 764238 - marlett.ttf crashes gnome-font-viewer, is unviewable in character map
marlett.ttf crashes gnome-font-viewer, is unviewable in character map
Status: RESOLVED INCOMPLETE
Product: gnome-font-viewer
Classification: Core
Component: general
3.16.x
Other Linux
: High critical
: ---
Assigned To: gnome-font-viewer-maint
gnome-font-viewer-maint
Depends on:
Blocks:
 
 
Reported: 2016-03-26 17:35 UTC by Bp
Modified: 2019-09-29 18:12 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bp 2016-03-26 17:35:04 UTC
Ubuntu 16.04, gnome-font-viewer 3.16.2-1build1.

Opening any version of marlett.ttf (the Windows interface font) will cause gnome-font-viewer to crash.
Selecting Marlett in gnome-character-map does not change the font used in the grid.

Tested with:
marlett.ttf (Windows 95): 17412 bytes, 11 July 1995
marlett.ttf (Windows 7): 26672 bytes, 10 June 2009

Log:
gnome-font-view[13140]: segfault at 0 ip 00007f85f5ecaed6 sp 00007ffe0dce3d38 error 4 in libc-2.23.so[7f85f5e40000+1c0000]
gnome-font-view[13146]: segfault at 0 ip 00007fe38dab7ed6 sp 00007ffceca89068 error 4 in libc-2.23.so[7fe38da2d000+1c0000]
Comment 1 André Klapper 2017-08-25 14:08:25 UTC
Thanks for taking the time to report this.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so. When pasting a stack trace in this bug report, please reset the status of this bug report from NEEDINFO to its previous status. Thanks in advance!

I tried to reproduce this in 3.24 but I could not make gnome-font-viewer crash.
Comment 2 André Klapper 2019-09-29 18:12:14 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!