Bug 1231479 - [abrt] gimp: pango_ot_info_list_scripts(): gimp-2.8 killed by SIGSEGV
Summary: [abrt] gimp: pango_ot_info_list_scripts(): gimp-2.8 killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gimp
Version: 21
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nils Philippsen
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:0714386d5d7aa516245549400f5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-13 19:20 UTC by Wilf
Modified: 2015-12-02 18:09 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-12-02 13:47:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (35.98 KB, text/plain)
2015-06-13 19:20 UTC, Wilf
no flags Details
File: cgroup (190 bytes, text/plain)
2015-06-13 19:20 UTC, Wilf
no flags Details
File: core_backtrace (13.01 KB, text/plain)
2015-06-13 19:20 UTC, Wilf
no flags Details
File: dso_list (14.54 KB, text/plain)
2015-06-13 19:20 UTC, Wilf
no flags Details
File: environ (3.04 KB, text/plain)
2015-06-13 19:20 UTC, Wilf
no flags Details
File: exploitable (82 bytes, text/plain)
2015-06-13 19:20 UTC, Wilf
no flags Details
File: limits (1.29 KB, text/plain)
2015-06-13 19:20 UTC, Wilf
no flags Details
File: maps (72.18 KB, text/plain)
2015-06-13 19:21 UTC, Wilf
no flags Details
File: open_fds (852 bytes, text/plain)
2015-06-13 19:21 UTC, Wilf
no flags Details
File: proc_pid_status (957 bytes, text/plain)
2015-06-13 19:21 UTC, Wilf
no flags Details

Description Wilf 2015-06-13 19:20:37 UTC
Description of problem:
I installed a few new fonts for a image I was making (coverart for a compilmation album), and restarted gimp by opening the file (a blank 720x720 xcf)
I then scrolled up to top of the font selection popdown of the text tool, and gimp froze and crashed.

I think these fonts just were the following:
http://www.1001fonts.com/brother-deluxe-1350-font-font.html
http://www.1001fonts.com/bohemian-typewriter-font.html
They were installed using Font Viewer to ~/.local/share/fonts/

The XCF file is saved to a NTFS partition on the disk.

Reported using ABRT, if this needs reporting elsewhere please indicate

Version-Release number of selected component:
gimp-2.8.14-1.fc21

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        gimp-2.8 /home/wilf/Music/COVERART/dev/musicwork.xcf
crash_function: pango_ot_info_list_scripts
executable:     /usr/bin/gimp-2.8
kernel:         4.0.4-202.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000
var_log_messages: [System Logs]:\n-- Logs begin at Sun 2015-03-01 01:33:06 GMT, end at Sat 2015-06-13 19:57:19 BST. --

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 pango_ot_info_list_scripts at /lib64/libpangoft2-1.0.so.0
 #1 gimp_font_get_new_preview at gimpfont.c:652
 #3 gimp_viewable_get_preview at gimpviewable.c:741
 #4 gimp_viewable_real_get_new_pixbuf at gimpviewable.c:352
 #5 gimp_viewable_get_pixbuf at gimpviewable.c:911
 #6 gimp_view_renderer_real_render at gimpviewrenderer.c:753
 #7 gimp_view_renderer_real_draw at gimpviewrenderer.c:687
 #8 gimp_view_renderer_draw at gimpviewrenderer.c:606
 #9 gimp_cell_renderer_viewable_render at gimpcellrendererviewable.c:316
 #10 gtk_tree_view_column_cell_process_action.isra at /lib64/libgtk-x11-2.0.so.0

Comment 1 Wilf 2015-06-13 19:20:43 UTC
Created attachment 1038387 [details]
File: backtrace

Comment 2 Wilf 2015-06-13 19:20:45 UTC
Created attachment 1038388 [details]
File: cgroup

Comment 3 Wilf 2015-06-13 19:20:47 UTC
Created attachment 1038389 [details]
File: core_backtrace

Comment 4 Wilf 2015-06-13 19:20:49 UTC
Created attachment 1038390 [details]
File: dso_list

Comment 5 Wilf 2015-06-13 19:20:51 UTC
Created attachment 1038391 [details]
File: environ

Comment 6 Wilf 2015-06-13 19:20:53 UTC
Created attachment 1038392 [details]
File: exploitable

Comment 7 Wilf 2015-06-13 19:20:54 UTC
Created attachment 1038393 [details]
File: limits

Comment 8 Wilf 2015-06-13 19:21:00 UTC
Created attachment 1038394 [details]
File: maps

Comment 9 Wilf 2015-06-13 19:21:02 UTC
Created attachment 1038395 [details]
File: open_fds

Comment 10 Wilf 2015-06-13 19:21:03 UTC
Created attachment 1038396 [details]
File: proc_pid_status

Comment 11 Fedora End Of Life 2015-11-04 11:27:48 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 12 Fedora End Of Life 2015-12-02 13:47:36 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.