Bug 501137 - GTK appmenus initially open in the wrong position until moving the cursor over a different menu entry
Summary: GTK appmenus initially open in the wrong position until moving the cursor ove...
Status: RESOLVED DUPLICATE of bug 490833
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: 6.3.2
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2025-03-06 10:47 UTC by Naxdy
Modified: 2025-03-06 12:22 UTC (History)
1 user (show)

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


Attachments
Bug showcase (161.99 KB, video/webm)
2025-03-06 10:47 UTC, Naxdy
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Naxdy 2025-03-06 10:47:28 UTC
Created attachment 179173 [details]
Bug showcase

SUMMARY
GTK appmenus initially open in the wrong position until moving the cursor over a different menu entry (see attached video)

STEPS TO REPRODUCE
1. Open an affected GTK app (tested with DBeaver and KiCad)
2. Click on an appmenu item that isn't the first
3. Move the mouse over to a different appemenu item

OBSERVED RESULT
Appmenu opens under the first menu entry initially ("File"), then updates to the current menu entry once hovering over a different entry.

EXPECTED RESULT
Appmenu opens initially under the menu entry that is being hovered over during the click, then updates to the new menu entry once hovering over a new one.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.5-zen1 (64-bit)
Graphics Platform: Wayland
Processors: 32 × AMD Ryzen 9 3950X 16-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor 1: AMD Radeon RX 7900 XTX
Graphics Processor 2: llvmpipe

ADDITIONAL INFORMATION
-
Comment 1 cwo 2025-03-06 12:22:29 UTC
Thank you for the bug report! This issue is already being tracked; marking as a duplicate. We believe it to be an upstream issue, please see the linked bug report for more information. A workaround should be included in Plasma 6.3.3 next week.

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