Bug 340230 - Icon mapping results in oxygen being used even if all toolkits’ icon theme is Flattr
Summary: Icon mapping results in oxygen being used even if all toolkits’ icon theme is...
Status: RESOLVED FIXED
Alias: None
Product: QtCurve
Classification: Frameworks and Libraries
Component: gtk2 (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Yichao Yu
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-22 14:49 UTC by Philipp A.
Modified: 2022-07-14 07:57 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Make map_kde_icons.pl query the user settings for the theme name to use (405 bytes, patch)
2015-01-25 14:58 UTC, joeloqvist
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp A. 2014-10-22 14:49:08 UTC
my configs all point to Flattr:

~/.gtkrc-2.0{,-kde4}:
gtk-icon-theme-name="Flattr"

~/.config/gtk-3.0/settings.ini:
[Settings]
gtk-icon-theme-name=Flattr

~/.kde4/share/config/kdeglobals:
[Icons]
Theme=Flattr

——————————

yet when a Qtcurve-styled GTK2 application requests a stock icon, it gets served a oxygen icon.

funnily when using any other GTK2 theme, i see Flattr icons.

Reproducible: Always
Comment 1 ShadowKyogre 2014-11-19 19:53:16 UTC
I can confirm the same for a test machine I have:
$ grep icon-theme  ~/.gtkrc-2.0{,-kde4}
~/.gtkrc-2.0:gtk-icon-theme-name="AwOken-255000000"
~/.gtkrc-2.0:gtk-fallback-icon-theme="hicolor"
~/.gtkrc-2.0-kde4:gtk-icon-theme-name="AwOken-255000000"
~/.gtkrc-2.0-kde4:gtk-fallback-icon-theme="hicolor"

$ grep Theme ~/.kde4/share/config/kdeglobals 
Theme=kAwOken-255000000

Note: I installed AwOken thinking that this'd solve the problem, but it didn't.
Comment 2 joeloqvist 2015-01-25 14:58:59 UTC
Created attachment 90647 [details]
Make map_kde_icons.pl query the user settings for the theme name to use

This fixes the problem for me. Disclaimer: since I know nothing about perl, its probably a pretty naive solution.
Comment 3 Justin Zobel 2021-03-09 07:30:29 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 4 Philipp A. 2022-07-14 07:57:22 UTC
seems like it’s no longer a problem