Bug 1550358 - t1lib does not recognize .t1 files
Summary: t1lib does not recognize .t1 files
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: t1lib
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Terje Røsten
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1593397
TreeView+ depends on / blocked
 
Reported: 2018-03-01 04:35 UTC by Andrew Schultz
Modified: 2021-04-05 01:15 UTC (History)
2 users (show)

Fixed In Version: t1lib-5.1.2-29.fc34 t1lib-5.1.2-29.fc33 t1lib-5.1.2-29.fc32
Clone Of:
Environment:
Last Closed: 2021-04-01 00:51:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
t1lib patch to recognize fonts with .t1 extension (536 bytes, patch)
2018-03-01 04:35 UTC, Andrew Schultz
no flags Details | Diff

Description Andrew Schultz 2018-03-01 04:35:33 UTC
Created attachment 1402212 [details]
t1lib patch to recognize fonts with .t1 extension

Description of problem:
urw-base35 fonts only ships .t1 files and not .pfb files, as expected by t1lib.  Applications like grace that depend on t1lib fail (bug 1502175).  If t1lib would look at the .t1 files, it can handle them fine.

Version-Release number of selected component (if applicable):
t1lib-5.1.2-21.fc27.x86_64

Steps to Reproduce:
1. Try to run xmgrace

Actual results:
xmgrace fails to start because t1lib can't find any fonts

Expected results:
xmgrace starts

Additional info:
Applications like xmgrace also need to be updated to use the right fonts.  Updating t1lib alone won't fix the applications.  t1lib is not particularly useful without fixing this.

I'll attach a patch.

Comment 1 Ben Cotton 2018-11-27 15:07:56 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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 27 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 2019-10-31 20:27:27 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 '29'.

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 29 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 3 Andrew Schultz 2019-10-31 20:36:26 UTC
woe to the republic

Comment 4 Ben Cotton 2020-11-03 15:00:22 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 5 Fedora Admin user for bugzilla script actions 2020-12-17 02:53:13 UTC
This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

Comment 6 Ben Cotton 2021-02-09 15:06:16 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.

Comment 7 Fedora Update System 2021-03-27 12:46:16 UTC
FEDORA-2021-e2a2aa3494 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-e2a2aa3494

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

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

Comment 9 Fedora Update System 2021-03-28 01:08:40 UTC
FEDORA-2021-6b79c6b25d 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-2021-6b79c6b25d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-6b79c6b25d

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

Comment 10 Fedora Update System 2021-03-28 01:58:06 UTC
FEDORA-2021-2d3edef656 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-2021-2d3edef656`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-2d3edef656

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

Comment 11 Fedora Update System 2021-04-01 00:51:43 UTC
FEDORA-2021-e2a2aa3494 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2021-04-05 01:05:04 UTC
FEDORA-2021-6b79c6b25d has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2021-04-05 01:15:58 UTC
FEDORA-2021-2d3edef656 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.