Bug 402840 - The application bar immediately hides then appears again on hover
Summary: The application bar immediately hides then appears again on hover
Status: RESOLVED DUPLICATE of bug 392464
Alias: None
Product: lattedock
Classification: Plasma
Component: application (show other bugs)
Version: 0.8.3
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: Michail Vourlakos
URL: https://gfycat.com/MajorExemplaryAffe...
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-03 23:46 UTC by felixbrakel
Modified: 2019-01-04 23:34 UTC (History)
0 users

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 felixbrakel 2019-01-03 23:46:50 UTC
SUMMARY
The docks application bar immediately hides, then reappears when hovering. This only appears to happen when the dock is positioned on the left side of the screen 

STEPS TO REPRODUCE
1. Set the location of the dock to "Left", the alignment to "Center" and the visibility to "Dodge all Windows" or "Dodge Active"
2. Move the cursor left side of the screen to allow the dock to appear

OBSERVED RESULT
The dock immediately hides itself and then appears quickly sometimes.

EXPECTED RESULT
The dock should appear and not hide immediately.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.14.4
KDE Frameworks Version: 5.53.0
Qt Version: 5.12.0

ADDITIONAL INFORMATION
It seems to depend on the speed of the cursor moving to the left side. The most consistent way seems to be to move the cursor the the pixel right before the hover of the dock is triggered. Then moving it one pixel on the left to trigger it.
See this gif:
https://gfycat.com/MajorExemplaryAffenpinscher
for a visual explanation of how to trigger this bug.
Comment 1 Michail Vourlakos 2019-01-04 23:34:34 UTC
plasma X11 issue, can be solved with: https://github.com/psifidotos/Latte-Dock/wiki/F.A.Q.#q-my-left-dock-behaves-strangely-from-plasma-510-and-beyond-can-i-fix-this

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