Bug 416889

Summary:	Latte Dock jumps up-down when attached at left or right edge of screen
Product:	[Unmaintained] lattedock	Reporter:	Petros <psamaras1>
Component:	application	Assignee:	Michail Vourlakos <mvourlakos>
Status:	RESOLVED DUPLICATE
Severity:	major
Priority:	NOR
Version First Reported In:	0.9.8
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Petros 2020-01-28 23:57:34 UTC

SUMMARY
Using Unity layout on single monitor (laptop), the left side latte dock is jumping up and down continuously.
When set to bottom screen edge, there is no issue.
I cleaned latte cache (--cc) without improvement.
As it happened right after it was updated, I downgraded to 0.9.7-1 which behaves properly (no issue).




STEPS TO REPRODUCE
1. Start latte-dock 
2. Set Unity layout, or place any panel or dock at the left or right side of screen
3. 

OBSERVED RESULT
The panel/dock is jumping up and down continuously.

EXPECTED RESULT
The panel/dock is stable (not jumping up and down)

SOFTWARE/OS VERSIONS
Operating System: Arch Linux (Stable)
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.0
Kernel Version: 4.19.99-1-lts
OS Type: 64-bit
Processors: 4 × Intel® Core™ i3 CPU M 380 @ 2.53GHz
Memory: 7,5 GiB

ADDITIONAL INFORMATION

latte-dock 0.9.8-1

It is a new clean Archlinux installation, new/fresh user.

I could not record video of this, or... more accurately, Latte was not included in my recorded video (giph, recordmydesktop, silentcast)

Comment 1 Michail Vourlakos 2020-01-29 06:42:22 UTC

You need latest version 0.9.8.1 that fixes this, AUR has not included that version yet someone needs to contact the packager.

Comment 2 Petros 2020-01-29 10:42:01 UTC

I still have the repo version.

I may try AUR. Thanks.

Comment 3 Petros 2020-01-29 11:20:07 UTC

Refreshed repoDBs and updated to
latte-dock 0.9.8.1-1

Confirmed fixed! Thanks!

---
FWIW, AUR git did not help (as warned...).

Comment 4 Michail Vourlakos 2020-01-29 18:27:13 UTC


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