Bug 409816 - CTRL+C not transmitted to shell in Konsole on Fedora 30
Summary: CTRL+C not transmitted to shell in Konsole on Fedora 30
Status: RESOLVED WORKSFORME
Alias: None
Product: konsole
Classification: Applications
Component: keyboard (show other bugs)
Version: 19.04.2
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-15 09:33 UTC by Tom Lake
Modified: 2019-10-17 04:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Lake 2019-07-15 09:33:44 UTC
SUMMARY


STEPS TO REPRODUCE
1. Install Fedora 30 with KDE
2. Initiate Konsole
3. Type sleep 20
4. Press CTRL+C


OBSERVED RESULT
Wait 19 seconds for shell prompt

EXPECTED RESULT
Immediate shell prompt

SOFTWARE/OS VERSIONS

Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.4

ADDITIONAL INFORMATION

The problem lies in the default initialisation of shortcuts in file 
~/.config/konsolerc by the profile editor as far as I can see.

[Desktop Entry]
DefaultProfile=standard.profile

[Favorite Profiles]
Favorites=standard.profile

[MainWindow]
Height 2160=2034
State=AAAA/wAAAAD9AAAAAAAABKQAAAfNAAAABAAAAAQAAAAIAAAACPwAAAAA
ToolBarsMovable=Disabled
Width 3840=1188

[Profile Shortcuts]
Ctrl+C, Ctrl+C=standard.profile


The profile editor shows under shortcuts "Ctrl+C, Ctrl+C" which is entirely
unintuitive and meaningless to the user. 

Nothing about profile editor in the Konsole handbook which is inadequate.
Comment 1 Christoph Feck 2019-08-05 20:07:16 UTC
Are you sure you didn't accidentally set Ctrl+C as the shortcut in the Manage Profiles dialog? On my system, all existing and newly created profiles start out without any shortcut.
Comment 2 Christoph Feck 2019-08-20 20:53:03 UTC
If you can provide the information requested in comment #1, please add it.
Comment 3 Christoph Feck 2019-09-17 18:19:00 UTC
To further investigate this issue, KDE developers need the information requested in comment #1. If you can provide it, or need help with finding that information, please add a comment.
Comment 4 Bug Janitor Service 2019-10-02 04:33:09 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2019-10-17 04:33:15 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!