Bug 351992

Summary:	Fail to bind "Send Keyboard Input" `alt+w` to send `<`
Product:	[Unmaintained] khotkeys	Reporter:	warthogdj
Component:	general	Assignee:	Michael Jansen <kde>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	kdelibs-bugs-null, mgraesslin, warthogdj
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description warthogdj 2015-08-29 19:40:17 UTC

Kubuntu 15.04 (using backports)
Plasma version 5.3.2 
KDE Frameworks 5.12.0

In KDE4 i could make a global shortcut to bind `alt+w`   to send  `<` and `alt+q`   to send  `maj+<`.
With plasma5 this is not working at all. I couldn't manage to find more info on this and i think this may be a bug, if someone can confirm this or give any tips, thanks

PS: It doesn't work with any other shortcut (CTRL+ALT+W, etc) i tried btw

Reproducible: Always

Steps to Reproduce:
1. Go to System Config, Shortcuts, Custom Shortcuts
2. Create a new Global Shortcut with Send to Keyboard
3. Use ALT+W as trigger
4. put < or maj+< int action

Actual Results:  
Nothing is printed (in firefox)
It trigger Apply in the Action tab of the Custom shortcuts window for example (ALT is triggering functions of the window)

It doesn't work with any other shortcut i tried btw

Expected Results:  
It may print < or > when using ALT+W in any active window when a text field is focused.

Comment 1 warthogdj 2015-08-29 20:29:36 UTC

I was trying to find a workaround  with xmodmap and i found that actually the left_alt modifier only works with 'p' and 'n' (didn't try other non ascii).

So while trying to type ALT+P it prints something on terminal and ALT+N too.
But it does not print anything with ALT+A,B,C,W,Q and so long.

The Send Keyboard Input works with alt+p and alt+n and it prints < as expected, but sadly not with other letters, still no explanation to that.

Comment 2 warthogdj 2015-08-30 10:23:07 UTC

xkb_keymap {
	xkb_keycodes  { include "evdev+aliases(azerty)"	};
	xkb_types     { include "complete"	};
	xkb_compat    { include "complete"	};
	xkb_symbols   { include "pc+fr(oss)+us:2+inet(evdev)"	};
	xkb_geometry  { include "pc(pc101)"	};
};
rules:      evdev
model:      pc101
layout:     fr,us
variant:    oss,

Comment 3 Thomas Lübking 2015-08-30 11:59:44 UTC

in konsole, run
   pkill kglobalaccl5
   kglobalaccl5 &

the map from qwerty to azerty has likely not been caught, this is then bug #350816

Comment 4 warthogdj 2015-08-30 12:09:14 UTC

Well i just read this, and i have no issue of inverted keys, my azerty keyboard is working just fine.
Also comment2 is talking about a work around which i don't see a trace of.

Comment 5 warthogdj 2015-08-30 12:10:58 UTC

Just forgot to add this:
kglobalaccel-runtime: Registering key "Alt+W" for "khotkeys" : "{af7a9abb-05b7-4884-b03a-fe838cdf70b0}" (still not working)
kglobalaccel-runtime: Registering key "Ctrl+Alt+E" for "khotkeys" : "{85ee9e78-7e29-4b18-8888-808d6f48c72b}" (is working)
after : pkill kglobalaccel5 && kglobalaccel5 &

Comment 6 warthogdj 2015-08-31 10:15:22 UTC

in ~/.config/khotkeysrc

[Data_9]
Comment=Commentaire
Enabled=true
Name=chleft
Type=SIMPLE_ACTION_DATA

[Data_9Actions]
ActionsCount=1

[Data_9Actions0]
DestinationWindow=0
Input=<
Type=KEYBOARD_INPUT

[Data_9Conditions]
Comment=
ConditionsCount=0

[Data_9Triggers]
Comment=Simple_action
TriggersCount=1

[Data_9Triggers0]
Key=Alt+W
Type=SHORTCUT
Uuid={af7a9abb-05b7-4884-b03a-fe838cdf70b0}

Comment 7 Thomas Lübking 2015-10-15 22:15:21 UTC

The workaround refers to restarting kglobalaccel.

Can you bind alt+w to anything in "kcmshell5 keys" (like showing krunner etc.)?

Comment 8 warthogdj 2015-10-15 22:21:06 UTC

Well i completely forgot this, i reinstalled kubuntu after all, my it was because of a residual config somewehere. Still i was not able to find the thing that caused this.

I cleared my home folder and migrated only needed config files.
My guess it was some residual config file from 14.10 and plasma 4.
I can't confirm that but  i'm pretty sure of it.

So this is no actual bug.

It can be closed.