Bug 1847187 - graphicsmagick cannot find fonts when adding text to image
Summary: graphicsmagick cannot find fonts when adding text to image
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: GraphicsMagick
Version: 32
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Andreas Thienemann
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-15 20:50 UTC by Jim Gomi
Modified: 2021-01-08 02:51 UTC (History)
2 users (show)

Fixed In Version: GraphicsMagick-1.3.36-1.fc33 GraphicsMagick-1.3.36-1.fc32
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-06 01:22:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jim Gomi 2020-06-15 20:50:05 UTC
Description of problem:
When adding text to an image using graphicsmagick, the font is not found.
Using imagemagick, the same command works fine.

Version-Release number of selected component (if applicable):
GraphicsMagick-1.3.34-1

How reproducible:
Consistently

Steps to Reproduce:
Attempt to add text to image using the command:
> gm convert -pointsize 100 -fill black  -draw @caption.mvg test.jpg out.jpg

where file caption.mvg contains:
text 20,80 "This is the caption."


Actual results:
Error message:
gm convert: Unable to read font (/usr/share/fonts/default/Type1/n019003l.pfb) [No such file or directory].


Expected results:
text added to image.


Additional info:
The corresponding command using imagemagick works fine:
> convert -pointsize 100 -fill black  -draw @caption.mvg test.jpg out.jpg
no error message, out.jpg contains image with added text.

Comment 1 Ben Cotton 2020-11-03 16:59:21 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
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 '31'.

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 31 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 2 Ben Cotton 2020-11-24 15:22:05 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.

Comment 3 Jim Gomi 2020-11-29 19:37:59 UTC
This issue is still present in Fedora 32 with GraphicsMagick-1.3.34-2

Comment 4 Fedora Update System 2020-12-31 16:43:59 UTC
FEDORA-2020-8481bac195 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-8481bac195

Comment 5 Fedora Update System 2020-12-31 16:44:09 UTC
FEDORA-2020-402de744f0 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-402de744f0

Comment 6 Fedora Update System 2021-01-01 01:20:54 UTC
FEDORA-2020-8481bac195 has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-8481bac195`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-8481bac195

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2021-01-01 01:34:56 UTC
FEDORA-2020-402de744f0 has been pushed to the Fedora 32 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-402de744f0`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-402de744f0

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Jim Gomi 2021-01-02 02:18:27 UTC
Yes, update FEDORA-2020-402de744f0 fixes the problem.

Comment 9 Fedora Update System 2021-01-06 01:22:25 UTC
FEDORA-2020-8481bac195 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2021-01-08 02:51:37 UTC
FEDORA-2020-402de744f0 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.


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