Bug 302928

Summary: kde-config-gtk: breaks gtk-key-theme (can't use Emacs shortcuts)
Product: unknown Reporter: Richard Neill <kde>
Component: generalAssignee: Aleix Pol <aleixpol>
Status: RESOLVED FIXED    
Severity: normal CC: cfeck, mail
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In: 5.18.0
Sentry Crash Report:

Description Richard Neill 2012-07-02 21:55:30 UTC
Under KDE, GTK apps don't respect their keyboard-shortcut settings.

GTK apps (when run under Gnome) usually support:
    gtk-key-theme-name = "Emacs"
which allows the keybindings to act like Emacs (or readline) *.

Under KDE (perhaps because gnome-system-settings isn't running), this setting is not applied, 
not even if ~/.gtkrc-2.0-kde4 is edited to include that line. (Nor is there any other way to change the keyboard shortcuts: the KDE prefs aren't applied either).

(*) Notably, binding Ctrl-A as "go to start of line" rather than "select all" . When these are confused, it's very easy to destroy an entire document with one shortcut!

[BTW, I'd like to see another enhancement to kde-config-gtk, namely an option to leave GTK applications with their native (gnome) prefs, keeping them distinct from KDE. This is probably a minority view, but imho, a GTK app should respect the gnome-control-center rules for appearance at all times, even when run as a guest under KDE.]
Comment 1 Aleix Pol 2012-07-04 07:50:31 UTC
Hi,
How is it possible that a configuration dialog breaks your key theme?
Comment 2 Richard Neill 2012-07-04 17:12:29 UTC
Is it possible that I'm seeing the kde-config-gtk in too large a scale? I assumed that this wasn't just the KDE control center module, but the whole "making GTK apps look native under KDE" process.
As far as I can understand it, the root cause for the problem is a combination:

1.Merely having the gtk-key-theme setting idefined in the right config file sn't sufficient for the app.
2. The app relies on gnome-settings-daemon to manage this pref.
3.Gnome-settings-daemon refuses to run under KDE: there is already an "xsettings manager". But the KDE Xsettings-manager doesn't manage this particular setting.
4. KDE doesn't offer an alternative configuration, nor does it aply the KDE global scheme.
Comment 3 Andrew Crouthamel 2018-11-09 00:53:37 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-11-18 03:21:23 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Mikhail Zolotukhin 2020-04-25 16:03:29 UTC
Since 5.18 Plasma now uses GTK daemon to manage configurations for GTK applications and does not override GTK2 file. You can also disable settings sync via Services KCM.