Bug 408763 - Conflict of shortcuts: "Previous terminal" and "Next terminal"
Summary: Conflict of shortcuts: "Previous terminal" and "Next terminal"
Status: RESOLVED FIXED
Alias: None
Product: yakuake
Classification: Applications
Component: general (other bugs)
Version First Reported In: 3.0.5
Platform: Ubuntu Linux
: NOR minor
Target Milestone: ---
Assignee: Eike Hein
URL:
Keywords:
: 410038 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-06-16 00:45 UTC by Shihao Xu
Modified: 2021-08-04 10:23 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Shihao Xu 2019-06-16 00:45:41 UTC 
SUMMARY

It seems like that the shortcuts "Next terminal" and "Previous terminal" are in conflict with each other. If both of the two shortcuts are set, only one of them could work. The other one will trigger a "Ambiguous shortcut detected" dialog box.


STEPS TO REPRODUCE
1. Settings -> Configure Shortcuts 
2. Set arbitrary shortcuts for "Previous terminal" and "Next terminal"
3. Use the previously defined shortcuts for previous/next terminal

OBSERVED RESULT
-> The shortcut for "Previous terminal" will trigger "Ambiguous shortcut detected" dialog box, even if it is not ambiguous at all and there is no conflict.


EXPECTED RESULT
-> Previous/Next terminal shortcuts should work if they are not ambiguous.


SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Ubuntu 18.04
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.44.0
Qt Version: 5.9.5

ADDITIONAL INFORMATION
Comment 1 Quentin 2019-08-27 08:19:32 UTC 
*** Bug 410038 has been marked as a duplicate of this bug. ***
Comment 2 Quentin 2019-08-27 08:20:14 UTC 
Seeing the same issue
Comment 3 Gleb Popov 2020-05-05 12:10:51 UTC 
This started to work for me somehow. I've updated X.org to 1.20, switched to libinput, updated Plasma to 5.18.4, KF5 to 5.69 - and now shift+tab works for me in yakuake.
Comment 4 Gleb Popov 2021-08-04 10:23:02 UTC 
Since this seems to be resolved, I'm closing this bug.