https://bugs.kde.org/show_bug.cgi?id=420246
Harald Sitter <sit...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Product|kinfocenter |frameworks-kiconthemes
Assignee|plasma-b...@kde.org |cf...@kde.org
Status|REPORTED |CONFIRMED
Component|System Information |general
Summary|Distribution icon is not |icon theme change mucks up
|correctly updated in |icon resolution
|"System Information" KCM |
|immediately after I change |
|global theme |
CC| |kdelibs-b...@kde.org
Ever confirmed|0 |1
Version|unspecified |5.68.0
--- Comment #2 from Harald Sitter <sit...@kde.org> ---
A distro can set the logo as either absolute path (which is likely what
opensuse does) OR icon name (which gets resolved via the theme to support
scaling). Neon does the latter which is why it *can* change. What the recording
shows is unexpected change though.
There is something broken somewhere lower in the stack. If you look at the
recording, the first time the KCM is opened it has the logo start-here-kde
while on neon it should be start-here-kde-neon (which is part of hicolor and
thus always available). So it should *always* be a neonishy icon and the fact
that it is not points at something being wrong with caches somewhere either in
KIconLoader or QIcon. Or perhaps hicolor is lost as fallback theme along the
way?
To reproduce simply put some start-here-kde-foo icon in your hicolor theme and
set LOGO=start-here-kde-foo in /etc/os-release (+ ensure there's no
kcm-about-distrorc anywhere setting an override logo) and check sys info KCM
now shows that foo icon.
Then look at the these two cases:
- opens system settings
- change icon theme
- go to sys info
- observe it now being start-here-kde
next
- open system settings
- **go to sys info**
- it will be start-here-kde-foo
- change icon theme
- go to sys info again
- the icon will still be start-here-kde-foo!
the only difference between these two scenarios is the icon resolution possibly
getting cached in the second scenario and therefore resolution continues to
work as expected the second time.
All KCM instances are thrown away once you go to another KCM, so this isn't a
KCM-side issue, from a KCM POV the icon is loaded every time from scratch.
Moving bug to kiconthemes as closes possible culprit.
--
You are receiving this mail because:
You are watching all bug changes.
