Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1744951 - Gimp under Fedora 31 does not find fonts: "Due to lack of any fonts, text functionality is not available."
Summary: Gimp under Fedora 31 does not find fonts: "Due to lack of any fonts, text fun...
Keywords:
Status: CLOSED DUPLICATE of bug 1744377
Alias: None
Product: Fedora
Classification: Fedora
Component: gimp
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Nils Philippsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-23 10:48 UTC by Thomas Dreibholz
Modified: 2019-08-23 11:35 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-23 11:35:20 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Thomas Dreibholz 2019-08-23 10:48:36 UTC 
Description of problem:
Gimp does not find fonts in the upcoming Fedora 31 release. Gimp worked in Fedora 30 and earlier.

Version-Release number of selected component (if applicable):
$ rpm -q gimp
gimp-2.10.12-2.module_f31+5293+eb7fed42.x86_64


How reproducible:
100%

Steps to Reproduce:
1. Start Gimp
2. New image
3. Use text tool and type a character

Actual results:
GIMP Message:
"Due to lack of any fonts, text functionality is not available"

Expected results:
Display typed character with default font.

Additional info:
Comment 1 Josef Ridky 2019-08-23 11:35:20 UTC 
This looks like f31 specific issue, due the same version of GIMP under f30 is working fine.

Closing this as duplicate of #1744377, for further updates, please use that bug report.

*** This bug has been marked as a duplicate of bug 1744377 ***
Note You need to log in before you can comment on or make changes to this bug.