wbauer added a comment.
In D17187#367565 <https://phabricator.kde.org/D17187#367565>, @ngraham wrote: > That's a pre-existing bug: https://bugs.kde.org/show_bug.cgi?id=401507 That's not the full truth though. The cursor theme KCM will affect the default theme of the whole session. I.e. it actually will affect non-KDE applications too, unless they explicitly use a different one. startkde (or startplasmacompositor on Wayland) reads the setting and sets the corresponding environment variable (XCURSOR_THEME) > Ideally we wouldn't need a GTK KCM at all because the other KCMs would change the appropriate GTK settings at the same time as the KDE settings. I'm not sure that's a good idea in every case though. E.g. there likely won't be the same widget styles installed for Qt5, GTK2, and GTK3... Especially since GTK3 dropped support for theme engines like Oxygen or QtCurve. Anyway, I mainly wanted to point out where the wrong cursor theme in GTK3 applications actually comes from. Explicitly setting it in the default GTK configs should normally not be necessary at all, unless there's a system-wide config that sets it already. As we cannot influence the latter, it's probably better to do it anyway though. REPOSITORY R98 Breeze for Gtk REVISION DETAIL https://phabricator.kde.org/D17187 To: fvogt, #plasma, ngraham Cc: wbauer, ngraham, broulik, plasma-devel, ragreen, Pitel, ZrenBot, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol, mart
