Bug 270369 - Pressing 'Ctrl+Q' will close krdc instead of resuming the terminal, even when "grab all possible keys" is enabled.
Summary: Pressing 'Ctrl+Q' will close krdc instead of resuming the terminal, even when...
Status: RESOLVED DUPLICATE of bug 162723
Alias: None
Product: krdc
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Urs Wolfer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-07 22:31 UTC by Rafal Lalik
Modified: 2012-01-02 16:09 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Rafal Lalik 2011-04-07 22:31:52 UTC 
Version:           unspecified (using KDE 4.6.2) 
OS:                Linux

Sometimes would be useful to have clickable action to resume terminal, for example when I work in krdc for vnc session and terminal is suspended, when pressing Ctrl+Q it try to close krdc (even with Grab key on) instead of resume konsole.

The way is to change shortcut for closing krdc but this is workaround not real solution.

Reproducible: Didn't try
Comment 1 Christoph Feck 2011-04-08 04:07:07 UTC 
I think it is the Shell that handles the Ctrl+Q command, not Konsole. So we would have to "fake" input. Not sure if this is possible.
Comment 2 Rafal Lalik 2011-04-08 10:28:03 UTC 
Yes, we would have to send fake signal, but it should be possible. How does it works in screen keyboards?
Comment 3 Jekyll Wu 2011-10-19 14:32:26 UTC 
I do not use krdc often, but from the description it looks like a bug of krdc. More precisely, it looks like a duplication of bug 162723. I am not sure, so just assign this report to krdc developers without marking it as duplication.

And, if this can't be solved by krdc, you still have the workaround. I wonder how many konsole users will need or like a action in the context menu for simulating 'Ctrl+Q'.
Comment 4 Urs Wolfer 2012-01-02 16:09:26 UTC 

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