Summary: | (frameworks) Ctrl+<any key> is not sent to terminal in kde5 | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | Luiz Angelo De Luca <luizluca> |
Component: | keyboard | Assignee: | Konsole Developer <konsole-devel> |
Status: | CLOSED FIXED | ||
Severity: | major | CC: | bluescreenavenger |
Priority: | NOR | ||
Version: | 2.99.900 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Luiz Angelo De Luca
2014-04-03 22:51:42 UTC
Yes it has been like this since the beginning of frameworks - I haven't been able to figure it out yet Thanks Kurt, The ctrl+<any key> is fixed. Now my problem is with home/end keys, F1-12 keys and maybe others. Some update: I still have the home/end and F1-12 keys problem. However, I noticed that this occurs only in local shell. If I ssh to a remote shell, keys work as expected. Also, I have no problem with kde4 konsole or xterm (even inside kf5). I cleared all config files from my kf5 and it seems to fix the problem. Now, all ctrl+? and home, end F? keys work! This seems to still affect konsole with the Wayland backend. When I run export QT_QPA_PLATFORM=xcb . ctrl+c works, but under the native Wayland backend, it doesn't see CTRL+C, it just sees 'c' After a recent rebuilt, it seems konsole is still affected, under the QT_QPA_PLATFORM=wayland backend, CTRL+C does not work, and only sends the letter 'c' This still seems to affect konsole 5 for me when starting with an default profile and Wayland... |