Bug 483235 - Attaching the Keyboard Layout widget to a panel causes the global shortcut for switching keyboard layout to defocus the current window
Summary: Attaching the Keyboard Layout widget to a panel causes the global shortcut fo...
Status: RESOLVED DUPLICATE of bug 479084
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-03-11 13:13 UTC by accounts
Modified: 2024-03-19 18:50 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 accounts 2024-03-11 13:13:05 UTC
SUMMARY
Attaching the Keyboard Layout widget to a panel causes the global shortcut for switching keyboard layout to defocus the current window. This upsets the flow of trying to type with multiple keyboard layouts, as you have to re-focus the window every time you switch the layout.

STEPS TO REPRODUCE
1. Configure a shortcut to switch keyboard layouts (system settings -> keyboard -> advanced -> switching to another layout -> win + space) (problem occurs on any set shortcut)
2. On a second monitor, add a new default panel (right-click desktop -> enter edit mode -> add panel -> default panel)
3. Add the keyboard layout widget (add widgets -> keyboard layout)
4. Drag the keyboard layout widget to the newly created default panel
5. Open any application
6. Press the layout-switch shortcut

OBSERVED RESULT
Currently selected application loses focus, must re-select to continue typing.

EXPECTED RESULT
Don't lose window focus, and continue typing as normal.

SOFTWARE/OS VERSIONS
Linux: 6.7.9.arch1-1
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Comment 1 Nate Graham 2024-03-11 19:44:19 UTC

*** This bug has been marked as a duplicate of bug 482653 ***
Comment 2 Nate Graham 2024-03-19 18:50:55 UTC

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