Bug 460783 - LatteDock is not taking space on wayland
Summary: LatteDock is not taking space on wayland
Status: RESOLVED DUPLICATE of bug 459755
Alias: None
Product: lattedock
Classification: Plasma
Component: application (show other bugs)
Version: 0.10.8
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Michail Vourlakos
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-20 20:17 UTC by Removed
Modified: 2024-02-10 05:36 UTC (History)
3 users (show)

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


Attachments
Demontration of the issue, look specificly at search bar at the bottom of firefox window. (1.12 MB, video/mp4)
2022-10-20 20:17 UTC, Removed
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Removed 2022-10-20 20:17:22 UTC
Created attachment 153065 [details]
Demontration of the issue, look specificly at search bar at the bottom of firefox window.

SUMMARY
LatteDock in panel mode is non-solid after switching to wayland.

STEPS TO REPRODUCE
1. Install Arch Linux with KDE/Wayland + xwayland
2. Remove default KDE bar and install latte dock.
3. Right click latte dock, edit dock, and select "Panel".

OBSERVED RESULT
When window is maximazed it is under latte dock itself.

EXPECTED RESULT
Maximized window is not covered by latte dock, but snaps to it's edge.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.26.1
KDE Plasma Version: 5.26.1
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.6

ADDITIONAL INFORMATION
Look at Attachment.
Comment 1 Jonathan Isom 2023-02-18 13:14:30 UTC
I don't know if this was specifically fixed or if what I did fixed it, but it is working here. It wasn't working before.  I nuked all the plasma/kde configs* and started fresh in wayland.  It is now reserving just fine.  Using plasma 5.27.0 on arch and git latte-dock.   

*for crying out loud put these all in sub directories. I had over a hundred just in .config.  6.0 would be a great start /rant
Comment 2 randomland 2023-02-19 15:13:50 UTC
(In reply to Jonathan Isom from comment #1)
> I don't know if this was specifically fixed or if what I did fixed it, but
> it is working here. 
Because it is actually fixed. See https://bugs.kde.org/show_bug.cgi?id=459755

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