Bug 408835

Summary:	Assigning Ctrl+[ shortcut breaks Ctrl+F shortcut
Product:	[Applications] systemsettings	Reporter:	Karlo Dautović <dafta007>
Component:	kcm_keys	Assignee:	Michael Jansen <kde>
Status:	RESOLVED DUPLICATE
Severity:	minor	CC:	fanzhuyifan, justin.zobel, kde, nate, plasma-bugs
Priority:	NOR
Version:	5.20.3
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Karlo Dautović 2019-06-17 15:37:29 UTC

SUMMARY
Ctrl+F stops working if you assign Ctrl+[ to a shortcut in one of the following shortcut menus:
Accessibility
Audio Volume
KAlarm
ksmserver
KWin
Plasma
Run Command

STEPS TO REPRODUCE
1. Open System Settings
2. Choose Shortcuts
3. Choose Global Shortcuts
4. Choose either one of the above mentioned shortcut menus
5. Bind Ctrl+[ to any shortcut
6. Open a browser, vim, or anything that uses Ctrl+F as a shortcut
7. Try to use Ctrl+F

OBSERVED RESULT
Ctrl+F has no effect.

EXPECTED RESULT
Ctrl+F should do whatever it is supposed to do in any application.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.16.0
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.3

ADDITIONAL INFORMATION
Possibly related to https://bugs.kde.org/show_bug.cgi?id=402028

Comment 1 Justin Zobel 2020-11-08 11:07:08 UTC

Thanks for the report Karlo.

I've just tested this on Plasma from git master and I cannot replicate the issue.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved, thanks.

Comment 2 Bug Janitor Service 2020-11-23 04:34:10 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 3 Karlo Dautović 2020-11-23 09:51:16 UTC

Hi.

I've just tested this bug, before and after update to the newest KDE in the Arch repositories, and the bug still exists on KDE 5.20.3.

Comment 4 Justin Zobel 2020-11-24 01:51:42 UTC

Confirmed still occurring in Comment 3.

Comment 5 David Redondo 2021-03-09 07:43:01 UTC

Is F and [ on the same key on your keyboard layout?

Comment 6 Karlo Dautović 2021-03-11 02:57:10 UTC

I'm using the Croatian (US) layout (US keyboard but with certain Croatian characters). On it, the F and [ keys are the same as with the US layout, but AltGr + F is also [.

Comment 7 David Redondo 2021-03-11 08:05:11 UTC

Interesting

And it only happens with the specific components listed in your first comment, or is it any shortcut menu?

Comment 8 Karlo Dautović 2021-03-11 10:12:16 UTC

Well, when I first tested it, it happened with only these menus. However, right now, on 5.21.2 it also happens on Activity Manager and KDE Daemon, for example. I haven't tested it with the rest, though.

Comment 9 David Redondo 2021-03-11 10:13:07 UTC

No problem it is probably all of them if it's that many

Comment 10 Karlo Dautović 2021-03-11 10:15:05 UTC

It's also worth mentioning that, if I don't bind anything else to that shortcut, the default shortcut under Common Actions -> Navigation -> Activate Previous Tab uses the Ctrl + [ keybind, and it works without an issue.

Comment 11 fanzhuyifan 2024-02-01 05:51:45 UTC

Seems to be the same bug as 402028

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