[khotkeys] [Bug 321281] starting gtk apps via shortcut uses ugly default theme instead of configured one

[arne anka]

https://bugs.kde.org/show_bug.cgi?id=321281

arne anka <kde-bugs-***@public.gmane.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |critical

--- Comment #1 from arne anka <kde-bugs-***@public.gmane.org> ---
i set it to critical since it makes shortcuts virtually unusable for gtk
applications.

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=321281

Christoph Feck <christoph-1Skg4+ogBTizQB+***@public.gmane.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Severity|critical |normal

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=321281

Thomas Lübking <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@kde.org,
| |***@gmail.com

--- Comment #2 from Thomas Lübking <***@gmail.com> ---
At least kded5 has an empty environment, so GTK won't resolve GTK*_RC_FILES so
you get no theme.

No idea whether kded clears the environment for security reasons, but on sth.
like
env GTK2_RC_FILES=/home/username/.gtkrc-2.0 firefox

This is not fixable from khotkeys, passing on to kded, might be because of the
startkde scripts (but I doubt so, given the environment is *really* empty, it's
likely cleared on startup)


errr... Christoph, do you know where kded's bugzilla is?

[Christoph Feck via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=321281

--- Comment #3 from Christoph Feck <***@kde.org> ---
frameworks-kdaemon

But I would suggest to check which kded module is responsible (by disabling
them in turn) first.

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=321281

--- Comment #4 from Thomas Lübking <***@gmail.com> ---
Starting kded5 from within a session doesn't show this problem anyway, so the
environment will be cleared by its invocation on session startup.

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=321281

--- Comment #5 from Thomas Lübking <***@gmail.com> ---
fwwi, I've no problems with gtk+, likely because ~/.gtkrc-2.0 is looked up by
default, whereas the OP probably relies on some ~/.gtkrc-kde written by the gtk
kcm?

[Haochen Tong]

https://bugs.kde.org/show_bug.cgi?id=321281

Haochen Tong <***@hexchain.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@hexchain.org

--- Comment #6 from Haochen Tong <***@hexchain.org> ---
I've run into this problem today (by starting Inkscape via KRunner).

The visible effect from this bug is that ~/.config/gtkrc-2.0 will affect the
color of GTK+ programs when "Apply colors to non-Qt applications" is enabled in
system settings.

[Haochen Tong]

https://bugs.kde.org/show_bug.cgi?id=321281

--- Comment #7 from Haochen Tong <***@hexchain.org> ---
I've run into this problem today (by starting Inkscape via KRunner).

The visible effect from this bug is that ~/.config/gtkrc-2.0 will affect the
color of GTK+ programs when "Apply colors to non-Qt applications" is enabled in
system settings.