Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#67593 - [retroarch] ozone theme requires both retroarch-assets-ozone and retroarch-assets-xmb

Attached to Project: Community Packages
Opened by Andrew Rabert (Draje) - Sunday, 16 August 2020, 00:32 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:01 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Maxime Gauduin (Alucryd)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The retoarch ozone theme requires both retroarch-assets-ozone and retroarch-assets-xmb be installed. Attempting to use ozone without retroarch-assets-xmb results in a retroarch notification indicating that assets are missing.

The missing assets are visually apparent in the UI with some things rendering as black boxes.


Package versions:
* retroarch 1.9.0-1
* retroarch-assets-ozone 1:331-1

Steps to reproduce:
Install packages listed above. Start retroarch with a fresh config.
This task depends upon

Closed by  Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:01 GMT
Reason for closing:  Moved
Additional comments about closing:  https://gitlab.archlinux.org/archlinux/p ackaging/packages/retroarch/issues/1
Comment by Alexandre Bouvier (doskoi) - Friday, 21 August 2020, 23:03 GMT
xmb menu needs retroarch-assets-ozone too, at least for the font used in notifications message for example
Comment by Alexandre Bouvier (doskoi) - Friday, 21 August 2020, 23:24 GMT
I don't think you can split this repo in fact. There is also a "sounds" folder required to play audio in the menu, and a "menu_widgets" folder needed to display icons in achievement notifications for example.
Comment by Maxime Gauduin (Alucryd) - Tuesday, 25 August 2020, 06:31 GMT
Before I delve into the code, did you notice all that visually or in the code? I'd like to contact upstream to clean this up before it gets out of hand. Why bother making seperate themes if all of them depend on each other.
Comment by Maxime Gauduin (Alucryd) - Tuesday, 25 August 2020, 09:39 GMT
Before I delve into the code, did you notice all that visually or in the code? I'd like to contact upstream to clean this up before it gets out of hand. Why bother making seperate themes if all of them depend on each other.
Comment by Alexandre Bouvier (doskoi) - Tuesday, 25 August 2020, 22:05 GMT
Just visually. I put the whole repo in my assets_directory and saw new icons in the interface. Also the menu sounds settings only works if the "sounds" folder is present.
Comment by Maxime Gauduin (Alucryd) - Wednesday, 26 August 2020, 06:28 GMT
Thanks for the feedback, I've opened an issue upstream: https://github.com/libretro/retroarch-assets/issues/381

Ultimately I'd like to have a base package with common assets, and still split each UI into their own package. Will see how upstream responds to that.
Comment by Maxime Gauduin (Alucryd) - Friday, 28 August 2020, 07:49 GMT
Good news, this is being worked on upstream: https://github.com/libretro/retroarch-assets/issues/341
Comment by Buggy McBugFace (bugbot) - Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.

Loading...