Bug 2171086

Summary:	Missing ingame textures, including biker and UI
Product:	[Fedora] Fedora	Reporter:	Benedek Horváth <bede.horvath>
Component:	xmoto	Assignee:	Gwyn Ciesla <gwync>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	37	CC:	gwync, hedayatv
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	xmoto-0.6.2-1.fc38 xmoto-0.6.2-1.fc36 xmoto-0.6.2-1.fc37	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-03-11 03:16:05 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 Benedek Horváth 2023-02-17 20:26:23 UTC

Description of problem:

When I start the game and load the map, the biker and the UI (minimap and scores) disappear after a split of a second. In 'ugly mode' everything works as expected.


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

xmoto-0.6.1-9.fc37.x86_64


How reproducible:

Happens every time.


Steps to Reproduce:

1. Open the game and load a map


Actual results:

Map with pickups loaded, but UI and biker is missing.


Expected results:

Everything should be displayed properly.


Additional info:

The problem does not appear when using flatpak or built from source.
I tried using different themes, but did not solve the issue.
The logs also do not show anything strange.
One of the developers tried to reproduce it in a VM, but unsuccessful.

Comment 1 Gwyn Ciesla 2023-02-23 17:17:34 UTC

This seems to have been fixed upstream but not released. I'll ask them to release.

Comment 2 Fedora Update System 2023-03-07 16:20:56 UTC

FEDORA-2023-8512db8e24 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-8512db8e24

Comment 3 Fedora Update System 2023-03-07 16:20:58 UTC

FEDORA-2023-6a5f8d1748 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2023-6a5f8d1748

Comment 4 Fedora Update System 2023-03-08 01:26:47 UTC

FEDORA-2023-3fffc00bee has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-3fffc00bee`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-3fffc00bee

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

Comment 5 Fedora Update System 2023-03-08 02:25:01 UTC

FEDORA-2023-8512db8e24 has been pushed to the Fedora 38 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-8512db8e24

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

Comment 6 Fedora Update System 2023-03-08 02:41:25 UTC

FEDORA-2023-6a5f8d1748 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-6a5f8d1748`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-6a5f8d1748

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

Comment 7 Fedora Update System 2023-03-11 03:16:05 UTC

FEDORA-2023-8512db8e24 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2023-03-16 18:19:13 UTC

FEDORA-2023-6a5f8d1748 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2023-03-16 18:31:52 UTC

FEDORA-2023-3fffc00bee has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.