Bug 268942

Summary:	Global shortcuts can't be disabled totally
Product:	[Plasma] plasma4	Reporter:	A.Yerenkow <yerenkow>
Component:	desktop	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	adaptee, carlosdgtorres
Priority:	NOR
Version:	4.11.3
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

Description A.Yerenkow 2011-03-20 10:33:42 UTC

Version:           unspecified (using KDE 4.5.5) 
OS:                FreeBSD

Example - Klipper. I disable Ctrl+Alt+V global shortcut (which klipper register at startup). It disable for this session only, after new start I see again Ctrl+Alt+V bounded.

Reproducible: Always

Steps to Reproduce:
Restart session, and global shortcuts are the same.

Comment 1 Juan Carlos Torres 2011-12-03 16:51:26 UTC

I can confirm that this still happens on KDE 4.7.4 on Fedora 16.

Comment 2 Jekyll Wu 2011-12-26 04:53:32 UTC

(In reply to comment #1)
> I can confirm that this still happens on KDE 4.7.4 on Fedora 16.

Hmm, I failed to reproduce the reported problem using KDE 4.7.4 on FC16.

Since KDE SC 4.5, that global shortcut is provided by systray, not by klipper. So 'systemsettings -> shortcut & gestures -> global shortcut -> klipper ' is NOT the right place to configure it.

For KDE SC 4.8, that will be a slightly different story.

See bug 244620 and bug 254994 for more information :)

Comment 3 Myriam Schweingruber 2012-05-23 09:45:47 UTC

Is this still valid with KDE 4.8.3 or trunk?

Comment 4 A.Yerenkow 2013-12-05 08:44:06 UTC

It's still valid in 4.11.2 (Ubuntu)

I disable hotkey Ctrl+Alt+V, and this is only for session.
After relogin, it's still here.

Comment 5 A.Yerenkow 2013-12-05 08:54:14 UTC

After I made changes this is how config looks:

/.kde/share/config/kglobalshortcutsrc
...
[plasma-desktop]
...
SystemTray-Klipper-6=none,Ctrl+Alt+V,
...

So, it seems that changes are saved, but just not populated from config during login.

Comment 6 Christoph Feck 2014-02-09 19:08:42 UTC


*** This bug has been marked as a duplicate of bug 300532 ***