Bug 483714 - Focus stays on old terminal
Summary: Focus stays on old terminal
Status: RESOLVED DUPLICATE of bug 482119
Alias: None
Product: yakuake
Classification: Applications
Component: general (show other bugs)
Version: 24.02.0
Platform: Arch Linux Linux
: NOR major
Target Milestone: ---
Assignee: Eike Hein
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-03-16 00:41 UTC by Angel Docampo
Modified: 2024-03-16 01:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Angel Docampo 2024-03-16 00:41:43 UTC
SUMMARY
Since the latest update, I noticed when I split a terminal (vertically or horizontally), focus remain on the original terminal, and not in the new spawned one. 

If I hide and show yakuake again, then, the focus goes to the new splitted terminal, but if I split the terminal again, then I lose the focus completely, and I have to point it with the mouse (or hide and show the terminal once again to regain focus on the new opened terminal).

STEPS TO REPRODUCE
1. open yakuake
2. split a terminal
3. focus remains on the first terminal, not in the new one
------ don't do nothing yet
4. hide yakuake
5. show it again
6. focus now is in the newest terminal split
------ still don't do nothing 
7. split the terminal again
8. now there is no terminal focused at all, you need to a) grab your mouse and point it, b) switch focus with your hotkeys, or c) hide and show yakuake once again.
9. now, every time you split your terminal, the focus is lost.

EXPECTED RESULT
When a terminal is split, focused split terminal should be the newest one. Besides, hiding and showing the terminal should not lose the focus at all, nor losing it when new splitting are done.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 24.02.0
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
Comment 1 Christian Muehlhaeuser 2024-03-16 01:22:13 UTC

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