Bug 510503

Summary: On table views, context menu appears at wrong position when window is on right-most screen of a multi-screen setup
Product: [Applications] plasma-systemmonitor Reporter: kde
Component: generalAssignee: KSysGuard Developers <ksysguard-bugs>
Status: CONFIRMED ---    
Severity: normal CC: ahiemstra, nate, plasma-bugs-null, vlad.zahorodnii
Priority: NOR Keywords: multiscreen
Version First Reported In: 6.4.5   
Target Milestone: ---   
Platform: CachyOS   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=502715
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Demo of the problem.

Description kde 2025-10-11 19:22:07 UTC
Created attachment 185699 [details]
Demo of the problem.

SUMMARY
When right clicking (opening the context menu) on processes, the menu will appear in the incorrect position, offset down and right to the mouse. This doesn't affect all context menus, for example right clicking on the graph will produce a correctly positioned menu.


STEPS TO REPRODUCE
1. Open system monitor
2. Right click on a process

OBSERVED RESULT
Context menu is in the lower right corner of the window


EXPECTED RESULT
Context menu should appear next to mouse


SOFTWARE/OS VERSIONS
Operating System: CachyOS Linux 
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.10.0
Kernel Version: 6.17.1-2-cachyos (64-bit)
Graphics Platform: Wayland
Graphics Processor 1: NVIDIA GeForce RTX 4070 Ti SUPER
Graphics Processor 2: AMD Radeon Graphics

ADDITIONAL INFORMATION
This is a dual monitor setup at 150% scaling. I tried turning desktop scaling down to 100% and restarting system monitor but observed the same results.
Comment 1 Nate Graham 2025-10-13 20:00:51 UTC
Can reproduce with Qt 6.10 and a multi-monitor system when the window on the right-most screen. Does not seem to be affected by which screen is primary, or any of the screens' scale factors.

According to Bug 502715, it looks like this issue — or a very similar one — was supposed to be fixed in Qt 6.10. So it's not fixed, or it was fixed but later regressed, or else this issue is subtly different and has a different root cause.