Created attachment 163851 [details] Show where cursor was and menu shows up SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** When I right-click on title bar to bring up window menu it opens in relation to top left of screen and not window. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Ok, I hit enter and it submitted Step to reproduce 1. Open a window away from the top of screen and also away from left. 2. Right Click on title bar at various points, left to right, on title bar. Operating System: Arch Linux KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 Kernel Version: 6.6.4-273-tkg-linux-tkg (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4080/PCIe/SSE2 Product Name: X570M Pro4
Humm can't reproduce.
I was able to track down some more details. When using the Breeze window decoration it works as expected. All the 3rd party themes that I have that were made for Plasma 5 seem to be effected. I was using glowglass cupertino when I noticed it initially. Not sure if that is considered a supported configuration.
(In reply to Jonathan Isom from comment #3) > I was able to track down some more details. When using the Breeze window > decoration it works as expected. All the 3rd party themes that I have that > were made for Plasma 5 seem to be effected. I was using glowglass cupertino > when I noticed it initially. Not sure if that is considered a supported > configuration. Yeah I think that's not supported. Sorry.
*** Bug 484043 has been marked as a duplicate of this bug. ***
I can reproduce with the Plastik window decoration. This seems to be a bug in the Aurorae theming engine
*** This bug has been marked as a duplicate of bug 480864 ***