Bug 443854 - On a multi screen setup, the full-screen launcher always shows on the first monitor, even if one clicks the launch icon on the second screen
Summary: On a multi screen setup, the full-screen launcher always shows on the first m...
Status: RESOLVED DUPLICATE of bug 443787
Alias: None
Product: plasmashell
Classification: Plasma
Component: Application Launcher (Kickoff) (show other bugs)
Version: 5.23.0
Platform: Other Linux
: HI normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2021-10-16 19:45 UTC by jpo
Modified: 2021-10-23 01:46 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description jpo 2021-10-16 19:45:58 UTC 
SUMMARY
On a multi screen setup, the full-screen launcher always shows on the first monitor, even if one clicks the launch icon on the second screen

STEPS TO REPRODUCE
1. two screens, a panel on each, set the application launcher to "Fullscreen launcher" in "Show alternatives"
2. Click on the launcher icon on the second screen

OBSERVED RESULT
The full-screen launcher appears on the first screen

EXPECTED RESULT
The full-screen launcher should appear on the screen it was launched from

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 21.10
KDE Plasma Version: 5.23.0
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Kernel Version: 5.14.12-051412-generic (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 9 5900HX with Radeon Graphics
Memory: 15.1 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2021-10-17 23:09:31 UTC 
Is this a regression compared to 5.22?

Oh I bet this is the same thing as Bug 443892...
Comment 2 jpo 2021-10-18 18:32:56 UTC 
(In reply to Nate Graham from comment #1)
> Is this a regression compared to 5.22?

Yes, it's a regression. It works as expected in 5.22.
Comment 3 Nate Graham 2021-10-23 01:46:18 UTC 

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