Bug 464740

Summary: System tray widgets/menus appear in the center of the screen instead of near the mouse pointer
Product: [Frameworks and Libraries] libplasma Reporter: Augusto Fornitani <augusto.fornitani>
Component: libplasmaAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: minor CC: materka, me, nate, niccolo.venerandi, notmart
Priority: NOR Keywords: regression
Version: 5.102.0   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=464513
Latest Commit: Version Fixed In:
Attachments: The attachment illustrates the problem. Since it is visual in nature, the attachment should be helpful

Description Augusto Fornitani 2023-01-24 13:22:32 UTC
Created attachment 155558 [details]
The attachment illustrates the problem. Since it is visual in nature, the attachment should be helpful

SUMMARY
After switching to a new monitor, the system tray widgets don't appear where they should. I was using the default behavior: click and have the pop-up/slide menu appear right above the mouse pointer.

STEPS TO REPRODUCE
1. Click on any icon in the system tray 
2. The corresponding pop-up menu will open

OBSERVED RESULT
Pop-up menus are always centered

EXPECTED RESULT
The pop-up menu should appear near where I clicked (as it does by default).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux, kernel 6.1.7-zen1-1-zen (64-bit)
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
This started happening after I bought a new monitor. I had two 1920×1080 displays: one rotated 90° counterclockwise, and the main one, with no rotation. Then, I switched the main one with the new monitor, with 2560×1080.
I have searched for possible related/duplicate tickets, but have not found any.
Comment 1 Augusto Fornitani 2023-01-24 21:46:56 UTC
After some searching, it seems that this is a duplicate of https://bugs.kde.org/show_bug.cgi?id=464201
Comment 2 Nate Graham 2023-01-24 21:48:26 UTC
Aha! Great find.

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