Bug 463561

Summary: Pressing F10 after F2 causes cursor/focus problems
Product: [Applications] dolphin Reporter: John Veness <john.kde>
Component: generalAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED LATER    
Severity: normal CC: kfm-devel
Priority: NOR    
Version: 22.12.0   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description John Veness 2022-12-28 17:37:16 UTC
STEPS TO REPRODUCE
1. Open Dolphin
2. Make sure at least two tabs are open
3. Press F10 to create a new folder, doesn't matter name, OK (this will also work on an existing file or folder, you just need to make sure there's something in there that you can highlight and rename)
4. Press F2 to rename - don't type anything or press return
5. Press F10 again to create another new folder, doesn't matter name, press OK or Cancel (doesn't matter which, but has to be one of them).

OBSERVED RESULT
Cursor keys up and down do nothing. A single press or left or right cursor key will cause the tab to the left or right of the current tab to be switched to.

EXPECTED RESULT
Cursor keys up, down, left or right highlight different objects in the current folder/tab.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20221227
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7
Kernel Version: 6.1.0-1-default (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 620
Manufacturer: HP
Product Name: HP ProBook 450 G4

ADDITIONAL INFORMATION
I notice that the state you get in after following the steps to reproduce is the same state that you get in if you press the tab key enough times (two) to get the cursor into the tab bar.
Comment 1 John Veness 2023-05-06 11:27:12 UTC
I'm closing this for now as I found a more general, and possibly related, bug in https://bugs.kde.org/show_bug.cgi?id=421778 so I'll see what F2/F10 does after that bug gets fixed.
Comment 2 John Veness 2023-05-06 11:29:16 UTC
Whoops, I meant https://bugs.kde.org/show_bug.cgi?id=469410 as the possibly-related bug.