Bug 1821062

Summary:	failed to load font /usr/share/trackballs/fonts/menuFont.ttf
Product:	[Fedora] Fedora	Reporter:	Paul Dufresne <dufresnep>
Component:	trackballs	Assignee:	Hans de Goede <hdegoede>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	hdegoede
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	trackballs-1.3.1-1.fc31 trackballs-1.3.1-1.fc32	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-01 01:35:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Paul Dufresne 2020-04-05 20:10:49 UTC

Description of problem:
The Dejavus font have moved...
[paul@localhost ~]$ ls -lh /usr/share/trackballs/fonts/
total 0
lrwxrwxrwx. 1 root root 33 30 jan 23:39 menuFont.ttf -> ../../fonts/dejavu/DejaVuSans.ttf
does not exist anymore.

The new file location is (I think!):
/usr/share/fonts/dejavu-sans-fonts/DejaVuSans.ttf

Version-Release number of selected component (if applicable):
trackballs-0:1.1.4-36.fc32.x86_64

How reproducible:
Each launch.

Have seen other games having this problem... might be a way to ask for the file location of the font?

Comment 1 Hans de Goede 2020-06-20 09:35:46 UTC

*** Bug 1816471 has been marked as a duplicate of this bug. ***

Comment 2 Hans de Goede 2020-06-20 09:39:03 UTC

(In reply to Paul Dufresne from comment #0)
> Have seen other games having this problem... might be a way to ask for the
> file location of the font?

Yes, this is caused by a file-path changes in the Dejavu fonts packaging this has been discussed extensively in bug 1806272, how to fix this using a way which is future proof to further packaging changes has been discussed in bug 1823360 and Bruno has been so good as to file bugs against all other packages which are possible affected by this, including some hints on how best to fix this, see e.g. bug 1835504.

I'm preparing an updated trackballs package (including the long awaited rebase to 1.3.1) which fixes this.

Comment 3 Fedora Update System 2020-06-20 10:55:59 UTC

FEDORA-2020-e8a6da8bb4 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-e8a6da8bb4

Comment 4 Fedora Update System 2020-06-23 01:03:38 UTC

FEDORA-2020-e8a6da8bb4 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-e8a6da8bb4`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-e8a6da8bb4

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

Comment 5 Fedora Update System 2020-06-23 01:53:39 UTC

FEDORA-2020-16ea6e44cc has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-16ea6e44cc`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-16ea6e44cc

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

Comment 6 Fedora Update System 2020-07-01 01:35:25 UTC

FEDORA-2020-16ea6e44cc has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2020-07-01 01:48:53 UTC

FEDORA-2020-e8a6da8bb4 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.