After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 785574 - banshee asks for a 128x128 multimedia-player icon, but uses a 512x512 unscaled one instead
banshee asks for a 128x128 multimedia-player icon, but uses a 512x512 unscale...
Status: RESOLVED FIXED
Product: adwaita-icon-theme
Classification: Core
Component: general
3.24.x
Other Linux
: Normal normal
: ---
Assigned To: adwaita-icon-theme maintainer(s)
adwaita-icon-theme maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2017-07-29 19:56 UTC by Fabrice Bellet
Modified: 2017-11-20 10:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
512 mistakenly not scalable (997 bytes, patch)
2017-09-26 13:46 UTC, Jakub Steiner
committed Details | Review

Description Fabrice Bellet 2017-07-29 19:56:01 UTC
In Fedora 25, with adwaita-icon-theme-3.22, banshee uses the 256x256/devices/multimedia-player.png file scaled at size 128x128. But this icon has been removed in 3.24, and in Fedora 26, banshee now uses the huge 512x512 icon instead (this one is not scaled down, because this category is marked with Type=Fixed).

This icon is used in banshee in the main window, when plugging an usb media player for example.

https://bugzilla.redhat.com/show_bug.cgi?id=1475534
Comment 1 Fabrice Bellet 2017-08-12 16:35:11 UTC
256x256/mimetypes/audio-x-generic.png is also concerned BTW. This is the icon used below the libraries and devices list in the main window.
Comment 2 Jakub Steiner 2017-09-26 13:46:39 UTC
Created attachment 360447 [details] [review]
512 mistakenly not scalable

- during the 256 > 512 transition, the automake system wasn't updated
  to mark the 512 size as scalable, thus some lower sizes were handled
  by 48x48 or icons appeared giant (512 nominal size).
Comment 3 Jakub Steiner 2017-09-26 13:46:59 UTC
Attachment 360447 [details] pushed as 824af3c - 512 mistakenly not scalable
Comment 4 Bjørn Lie 2017-11-18 20:17:04 UTC
It would be awesome if this could be pushed to the 3-26 stable branch and a 3.26.1 release made after, so I don't have to wait for 3.28
Pretty please with sugar on top :-)
Comment 5 Lapo Calamandrei 2017-11-18 23:31:00 UTC
Jakub the fix won't work, it fixes 512x512, setting them to 'scalable', but breaks 256x256 which became 'fixed'. I'm not on the right machine to fix this, anyway the test statement you changed should be something like: test "$$size" = "256" -o "$$size" = "512"
Comment 6 Lapo Calamandrei 2017-11-20 10:31:07 UTC
Uhm, nope, the max size won't do for 256, forget about my last comment. It needs a different fix.
Comment 7 Lapo Calamandrei 2017-11-20 10:43:55 UTC
Pushed a fix to both master and 3.26, closing.