Bug 409877

Summary: [Wayland] Latte-Dock Is Not Working Well
Product: [Plasma] lattedock Reporter: Alberto Díaz López <takuya>
Component: plasmoidAssignee: Michail Vourlakos <mvourlakos>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate
Priority: NOR    
Version: 0.9.0   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Alberto Díaz López 2019-07-16 21:42:56 UTC 
SUMMARY

Latte-Dock Is Not Working Well Under Wayland Session

STEPS TO REPRODUCE
1. Login Wayland session.
2. Go to Latte-Dock.
3. Context menu > Add a Widget.
4. Select a widget (e.g. Global Menu).
5. Drag & drop to Latte-Dock.

OBSERVED RESULT

Latte-Dock doesn't show when you place the mouse cursor at the place where it should show (auto-hide enabled). This happens with an addition of a widget to Latte-Dock, as well as drag & drop an element (e.g. an image) to Latte-Dock to go Telegram (opened as a task), etc.

EXPECTED RESULT

Latte-Dock should show when you are drag & dropping an element to it.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 5.2.1/5.16.3
(available in About System)
KDE Plasma Version: 5.16.3
KDE Frameworks Version: 5.60
Qt Version: 5.13

ADDITIONAL INFORMATION
Comment 1 Michail Vourlakos 2019-07-16 23:38:56 UTC 
Wayland support for v0.8.9 it is just a technology preview

Wayland support for git version and upcoming v0.9.0 is ALSO a technology preview. Try to reproduce with v0.9.0 and we will see how it will go...

BTW global menu is not supported under wayland
Comment 2 Michail Vourlakos 2019-07-27 08:00:02 UTC 
waiting v0.9 feedback
Comment 3 Michail Vourlakos 2019-07-27 08:00:23 UTC 
--
Comment 4 Alberto Díaz López 2019-07-30 14:54:12 UTC 
Tested now 0.9 version.

It's still the same status.
Comment 5 Michail Vourlakos 2019-07-30 15:35:58 UTC 
Kwin issue probably from KWin edges, 

Disable Behavior -> Activate KWin edge after hiding
Comment 6 Michail Vourlakos 2019-07-30 15:40:47 UTC 
*** This bug has been marked as a duplicate of bug 410411 ***
Comment 7 Nate Graham 2022-01-12 17:59:36 UTC 
*** This bug has been marked as a duplicate of bug 430391 ***