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!
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!
FS#75757 - lshw: path to icon is hardcoded in desktop file.
Attached to Project:
Community Packages
Opened by Matrix (Matr1x-101) - Wednesday, 31 August 2022, 07:57 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 31 August 2022, 20:42 GMT
Opened by Matrix (Matr1x-101) - Wednesday, 31 August 2022, 07:57 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 31 August 2022, 20:42 GMT
|
DetailsDescription: In the package "lshw", the path to the svg icon is hardcoded in the desktop file. This makes the desktop file incompatible with icon packs, as the icon is hardcoded. Instead of this, the icon (which is /usr/share/lshw/artwork/logo.svg) should be symlinked to /usr/share/icons/hicolor/symbolic/lshw.svg, and the icon parameter in the desktop file should be changed to "Icon=lshw"
Please note, this is not an upstream issue as the developer might have wanted the path to the icon hardcoded. Additional info: * package version(s): all versions are affected * config and/or log files etc.: https://github.com/lyonel/lshw/blob/master/src/gui/integration/gtk-lshw.desktop and https://github.com/lyonel/lshw/blob/master/src/gui/artwork/logo.svg are the files in question * link to upstream bug report, if any: none Steps to reproduce: 1. Install lshw. 2. In /usr/share/applications, you can see that the parameter "Icon" in gtk-lshw.desktop is hardcoded. |
This task depends upon
Closed by Toolybird (Toolybird)
Wednesday, 31 August 2022, 20:42 GMT
Reason for closing: Upstream
Additional comments about closing: Reporter says "I realized is probably an upstream issue"
Wednesday, 31 August 2022, 20:42 GMT
Reason for closing: Upstream
Additional comments about closing: Reporter says "I realized is probably an upstream issue"
Edit: On second thoughts you're probably right. I'll make a pull request to the upstream GitHub, and if that doesn't work, i'll maybe reopen this bug.