Bug 514592 - Display configuration overlay gets zoomed in when shortcut is pressed twice
Summary: Display configuration overlay gets zoomed in when shortcut is pressed twice
Status: REPORTED
Alias: None
Product: KScreen
Classification: Plasma
Component: common (other bugs)
Version First Reported In: 6.5.90
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-01-14 13:12 UTC by Iyán M. V.
Modified: 2026-01-19 16:50 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Iyán M. V. 2026-01-14 13:12:07 UTC
SUMMARY

When the overlay is only shown in the external screen (see Bug 514591), and the keyboard shortcut to open the overlay is pressed more than once, the overlay zooms. Hard to explain with words so I attach a small video showing the issue.

https://drive.switch.ch/index.php/s/oeC0j7FPSOe3YDX

STEPS TO REPRODUCE
1. Connect external screen
2. Press Super + P and select "Use only built-in screen" mode
3. Press Super + P and select "Extend to left of built-in screen" mode
4. Press Super + P again

OBSERVED RESULT
Overlay is only shown in external screen, and pressing Super + P zooms the overlay.

EXPECTED RESULT
Overlay should be shown in all screens or active one (see Bug 514591). Independently of this, it should not zoom in when the shortcut is pressed more than once.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.5.90
KDE Frameworks Version: 6.22.0
Qt Version: 6.11.0
Kernel Version: 6.18.5-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 22 × Intel® Core™ Ultra 7 155H
Memory: 32 GiB of RAM (30.9 GiB usable)
Graphics Processor: Intel® Arc
Manufacturer: LENOVO
Product Name: 21KDS00600
System Version: ThinkPad X1 Carbon Gen 12
Comment 1 Zamundaaa 2026-01-19 16:50:22 UTC
What an odd bug. I'm not sure what could be causing it, but it's likely either somewhere in the QML, or in Qt itself.