Bug 441823 - Menubar dropdowns positioned on wrong place in Wayland when second screen is offset
Summary: Menubar dropdowns positioned on wrong place in Wayland when second screen is ...
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: multi-screen (other bugs)
Version First Reported In: 5.25.3
Platform: Other Linux
: NOR major
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: wayland-only
Depends on:
Blocks:
 
Reported: 2021-08-31 17:42 UTC by Šimon (Simon) Rataj
Modified: 2022-07-22 18:47 UTC (History)
5 users (show)

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

Attachments
The issue shown in Okular (look in the top right corner) (287.07 KB, image/png)
2021-08-31 17:42 UTC, Šimon (Simon) Rataj 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Šimon (Simon) Rataj 2021-08-31 17:42:33 UTC 
Created attachment 141190 [details]
The issue shown in Okular (look in the top right corner)

SUMMARY


STEPS TO REPRODUCE (in Wayland)
1. Change display configuration in Display and Monitor settings
2. Open any app with menubar (e. g. Okular)
3. Click on an item in menubar

OBSERVED RESULT
The dropdown is in the top right corner instead of its normal position.

EXPECTED RESULT
The dropdown should show up under the menu item.

SOFTWARE/OS VERSIONS
KDE Neon 5.22.4 / Linux 5.11.0-27-generic (64-bit)
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
Using Wayland
Comment 1 Aleix Pol 2021-09-01 18:17:31 UTC 
I've seen things like that in the past, wouldn't be able to reliably reproduce though.
Comment 2 David Edmundson 2021-09-05 23:03:01 UTC 
>wouldn't be able to reliably reproduce though.

Primary monitor at non 0,0 is the key trigger
Comment 3 Šimon (Simon) Rataj 2022-02-13 08:43:31 UTC 
I tried Wayland after a while today (Plasma 5.24) and I didn’t encountered the issue this time.
Comment 4 Šimon (Simon) Rataj 2022-07-22 15:51:44 UTC 
I switched to Wayland today (hopefully permanently if I don’t encounter some more serious issues), but it seems that the bug is still there. Is there any progress on this? I got rid of the vertical offset, but it’s just a workaround and it feels unnatural.
Comment 5 Nate Graham 2022-07-22 16:03:19 UTC 
Still an upstream bug in QT; see https://community.kde.org/Get_Involved/Issue_Reporting#Understand_what_the_resolution_statuses_mean
Comment 6 Šimon (Simon) Rataj 2022-07-22 18:36:54 UTC 
(In reply to David Edmundson from comment #2)
> >wouldn't be able to reliably reproduce though.
> 
> Primary monitor at non 0,0 is the key trigger

I’ve been experimenting with it and it doesn’t have to be the primary monitor, but it seems that some monitor must be at (0, 0).
Comment 7 Šimon (Simon) Rataj 2022-07-22 18:43:34 UTC 
(In reply to Nate Graham from comment #5)
> Still an upstream bug in QT; see
> https://community.kde.org/Get_Involved/
> Issue_Reporting#Understand_what_the_resolution_statuses_mean

Sorry, I thought it was closed by me when I tried Wayland in 5.24 and didn’t encounter it. I didn’t realize that it was resolved as a qt bug.
Comment 8 Šimon (Simon) Rataj 2022-07-22 18:47:29 UTC 
I thought about setting −800 offset to my external monitor and leaving zero for the laptop’s, but it can’t be done in the settings and I don’t know how where I could manually enter that.