Bug 387896 - Submenus from context menu open in wrong position under Wayland
Summary: Submenus from context menu open in wrong position under Wayland
Status: RESOLVED DUPLICATE of bug 395177
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 18.04.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-14 12:11 UTC by Patrick Silva
Modified: 2018-06-14 19:45 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2017-12-14 12:11:26 UTC
The problem with submenus opening in wrong position under Wayland was supposedly fixed in qt 5.9.2, but this problem is still happening with submenus from dolphin context menu, mainly with "open with".

I use Arch Linux, dolphin 17.12 rc, qt 5.10.
Comment 1 Nate Graham 2017-12-14 16:53:17 UTC
Just Dolphin, or throughout Qt/KDE apps?
Comment 2 Patrick Silva 2017-12-14 18:35:31 UTC
I noticed this problem only with dolphin so far.
It does not occur always.
Comment 3 Patrick Silva 2018-03-10 01:02:11 UTC
Just happened again on neon dev unstable.
"Create New...", "Activities" and "Compress..." submenus appeared in wrong position.
Comment 4 petrk 2018-05-04 18:34:57 UTC
My system is affected. When there is not enough space on either side of popup then it should show itself on a sensible place, insteads it covers previous menu.

Tested with dolphin and kate.
Other problem may be related, systemsettings left sidebar mouseover tooltips are misplaced. They should be rendered near cursor, instead they show in top left corner of a window.

Plasma 5.12.5 Qt 5.10.1 Frameworks 5.45 Arch
Comment 5 petrk 2018-05-04 18:35:53 UTC
Possible duplicate: https://bugs.kde.org/show_bug.cgi?id=391172
Comment 6 Patrick Silva 2018-05-04 20:24:55 UTC
Bug 391649 is about tooltips in system settings.
Comment 7 Patrick Silva 2018-06-14 19:45:29 UTC

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