Bug 319172 - Ambigous shortcut detected with pressing Ctrl+Shift+w
Summary: Ambigous shortcut detected with pressing Ctrl+Shift+w
Status: RESOLVED FIXED
Alias: None
Product: yakuake
Classification: Applications
Component: general (show other bugs)
Version: 2.9.9
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Eike Hein
URL:
Keywords: usability
: 338335 393606 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-05-01 13:32 UTC by diabelko
Modified: 2020-06-24 12:22 UTC (History)
13 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description diabelko 2013-05-01 13:32:13 UTC
When I try to use Ctrl+Shift+W I get this message:
The key sequence 'Ctrl+Shift+W' is ambiguous. Use 'Configure Shortcuts'
from the 'Settings' menu to solve the ambiguity.
No action will be triggered.

I looked everywhere for shortcuts with Ctrl+Shift+W, but they just don't exist (except the one in yakuake). Problem occurs from just several days, and that's time when I upgraded my Ubuntu to the newest version (13.04), and KDE was upgraded to 4.10.2.

Of course I tried to google that problem, but I've found exactly nothing.

Reproducible: Always

Steps to Reproduce:
1. Run yakuake
2. Press Ctrl+Shift+w
3. enjoy
Actual Results:  
The key sequence 'Ctrl+Shift+W' is ambiguous. Use 'Configure Shortcuts'
from the 'Settings' menu to solve the ambiguity.
No action will be triggered.

Expected Results:  
The tab should be closed.
Comment 1 José Tomás Atria 2013-09-18 20:42:49 UTC
I can confirm this bug, using Yakuake 2.9.9, KDE 4.11.1 on Kubuntu Saucy Beta 1.

Is there a way to see where Yakuake is reading the other Ctrl+Shift+W shortcut from?
Comment 2 Ciro Santilli 2013-10-22 12:27:44 UTC
It seems that the Ctrl+Shift+W comes from the Konsole part. On the Konsole, it is intended to close a single tab, but console tabs are not used in Yakuake.

There have already been similar problems with ctrl-shift-+ reported here:

    https://bugs.kde.org/show_bug.cgi?id=248469

and bug reports such as this have already been marked as duplicates of the above one in the past such as this one:

    https://bugs.kde.org/show_bug.cgi?id=230915

Maybe we should just reopen that bug and dupe this? I'm commenting there.
Comment 3 José Tomás Atria 2013-10-22 21:39:46 UTC
There is a Ctrl+Shift+W shortcut by default specified in Konsole, yes, but disabling it seems to  have no effect on Yakuake. ie, the sequence is still ambiguous to yakuake even though it has been dissociated in konsole.

I have no idea if marking as dupe of a fixed bug is the right way of managing this issue.
Comment 4 Ciro Santilli 2013-10-23 06:51:18 UTC
I had changed it in Yakuake only.

I am not sure how changing Konsole settings affects Konsole parts used in other applications. If changing Konsole settings does affect the parts, then my theory is wrong.

I have made simple tests and they suggested that changing Konsole config does not necessarily affect Konsole parts in Yakuake.

For example, I changed the Konsole paste to Ctrl+Alt+Shift+V, in Konsole it changed. I restarted Konsole, then restarted Yakuake and in Yakuake paste is still Ctrl+Shift+V and Ctrl+Alt+Shift+V does nothing (Yakuake itself has no paste shortcut).

A similar test with "Clear Scrollback and Reset"  (Ctrl+shift+k default) gives similar results.

Versions: 

- Konsole 2.11.2
- Yakuake: 2.9.9
- KDE 4.11.2
Comment 5 keiner.zwei 2013-11-08 12:58:37 UTC
I've been trying to get this CTRL+SHIFT+W shortcut to work, and it did work for me after reassigning the "Close Session"-Shortcut in Yakuake to "None" while setting everything to default in Konsole (didnt even have to restart anything). Hope this helps someone else, because I've been trying to get this to work for a while now, this shortcut-thing is kind of counter-intuitive (ie. messy)..
Comment 6 Bart 2013-12-11 02:10:15 UTC
Also happens in Arch Linux, KDE 4.11.4.
Comment 7 Ciro Santilli 2013-12-11 07:57:21 UTC
*** This bug has been confirmed by popular vote. ***
Comment 8 Alexey 2014-01-15 22:17:04 UTC
I solved it by setting close session shortcut in yakuake to none.
But shortcut actually works I think because of konsole part of yakuake.
Comment 9 Luis Lezcano Airaldi 2014-08-17 17:41:17 UTC
*** Bug 338335 has been marked as a duplicate of this bug. ***
Comment 10 danbohea 2019-01-21 20:56:02 UTC
*** Bug 393606 has been marked as a duplicate of this bug. ***
Comment 11 Damian Nowak 2019-09-18 22:01:08 UTC
Originally reported in 2010 in https://bugs.kde.org/show_bug.cgi?id=230915. Almost 10 years later, and still buggy as hell.
Comment 12 Bug Janitor Service 2020-06-22 21:40:41 UTC
A possibly relevant merge request was started @ https://invent.kde.org/utilities/yakuake/-/merge_requests/17
Comment 13 Nicolas Fella 2020-06-24 12:22:29 UTC
Git commit 7a08d95b659af3614391df32d80bf2ca90e1077f by Nicolas Fella.
Committed on 24/06/2020 at 12:22.
Pushed by nicolasfella into branch 'release/20.04'.

Fix shortcut conflict for session closing

The Konsole part and Yakuake both provide a close-session action with the same shortcut (Ctrl-Shift-W). This leads to a conflict when invoking it. To work around this this patch removes the shortcut from the action provided by the konsole part.

I'm not particularly happy with this patch. Ideally we'd just reuse the action provided by the part, but this seems hard to do since the part actions appear to be per session and the yakuake action is global

M  +11   -0    app/terminal.cpp

https://invent.kde.org/utilities/yakuake/commit/7a08d95b659af3614391df32d80bf2ca90e1077f