Bug 381893

Summary:	Add .VolumeIcon.png neon logo to root of install image
Product:	[KDE Neon] neon	Reporter:	Vishal Rao <vishalrao>
Component:	Live/Install images	Assignee:	Neon Bugs <neon-bugs>
Status:	RESOLVED WAITINGFORINFO
Severity:	normal	CC:	jr, nate, neon-bugs, sitter, vishalrao
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Vishal Rao 2017-07-02 02:24:02 UTC

This is a request to include the neon logo as a .VolumeIcon.png file in the root of the installed image so that when running other installers they can pick up the OS logo during multiboot configuration. Perhaps this one https://packaging.neon.kde.org/neon/settings.git/plain/usr/share/pixmaps/neon.png

See https://github.com/elementary/pantheon-installer/issues/39 for some context.

Also, see https://github.com/dab2000/rEFInd-custom/blob/master/refind/lib.c#L958 and https://github.com/dab2000/rEFInd-custom/blob/master/libeg/image.c#L366 as an example of what is being sought after.

Comment 1 Vishal Rao 2017-07-02 03:15:21 UTC

Here is an example of some code I proposed in the experimental elementary OS pantheon installer: https://github.com/elementary/pantheon-installer/pull/41

It gives some polish to KDE neon branding while other third party installers (and maybe bootloaders) are being used :-)

What are your thoughts? Thanks!

Comment 2 Vishal Rao 2017-07-02 09:21:44 UTC

Should the filename be `.VolumeIcon.png` or `.VolumeIcon` or can it be either?

Comment 3 Harald Sitter 2021-03-17 10:08:37 UTC

I rather find this iffy. Putting a single resolution PNG there, means that either it needs to have substantial resolution 1024x1024+, or be small and then look terrible on 4K+ resolutions because of up scaling. Both options require the bootloader to do image scaling :(
Meanwhile the only library to generate apple icns files appears to also lack @scale variants support if this bug is to be believed https://sourceforge.net/p/icns/bugs/20/ that's on top of the fact that apparently the resolution tags in the file format are made up on the spot meaning proper support for any given resolution requires all involved software needs to know about it.

All this makes me kinda not want to do this by default TBH. If the bootloader goes fishing for icons already, they could just as well do it the linux way of reading LOGO from $disk/etc/os-release and then resolving the icon from $disk/usr/share/icons/hicolor https://www.freedesktop.org/software/systemd/man/os-release.html#LOGO=

Mind you, I'm not opposed to putting an icon set in a convenient location, but a single resolution for multi resolution use cases seems ill advised.

Nevertheless I've even built a thing that could theoretically generate the volumeicon for us https://invent.kde.org/sitter/kde-volumeicon

Comment 4 Nate Graham 2021-03-17 18:24:53 UTC

A scaled icon is probably better than a generic one, though I agree that using the common thing would be even better.

Comment 5 Carlos De Maine 2025-09-20 09:35:17 UTC

Thank you for your bug report! 
However this bug report was created/provided previous to 01/01/2023 and also has not received any updates since  before 01/01/2025. 
Unfortunately KDE neon no longer provides updates for anything older than noble 24.04 based edition's.
Please upgrade to KDE neon noble and if you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report.
Thanks for understanding!