SUMMARY This is something that annoys me a lot because it renders the hide dock feature useless. Instead of bringing the mouse to the edge of the screen to bring the dock, as long as the mouse is where the dock would be when unhidden, it will reveal itself. This makes maximized and fullscreen windows a pain to use because elements on the bottom of the screen are immediately blocked by the dock, requiring me to go to windowed mode or just disable the auto hide/dodge windows feature entirely as it is getting in the way of the space that could be used when the dock is hidden. STEPS TO REPRODUCE 1. Enable one of the many visibility modes that hides the dock in some way 2. Maximize a window 3. Move the mouse to where the dock would be when unhidden OBSERVED RESULT The dock reveals itself, blocking elements on the window EXPECTED RESULT The dock should reveal itself only when the mouse touches the bottom of the screen SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210524 KDE Plasma Version: 5.21.90 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.4-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i3-7020U CPU @ 2.30GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 620 ADDITIONAL INFORMATION
Adding a bit of info. This doesn't happen all the time. I still don't know what causes it but changing back and forth between layouts seem to have solved it temporarily.
run in command line, latte-dock -v what is your latte version ?
(In reply to Michail Vourlakos from comment #2) > run in command line, latte-dock -v > > what is your latte version ? Version is lattedock 20210527.git.5d8afda2
Send your layout file that reproduces the issue, I dont have such behavior in my system
In commamd prompt what latte version it says with latte-dock -v ?
Created attachment 138864 [details] Layout as requested I just noticed one thing that may be related to what is causing this. I observed that Latte may, sometimes, reload without explanation. After it is reloaded, the dock is behaving the way I described earlier. I don't know if this is related but I noticed how Latte takes 20% CPU or more in this dual core i3-7020U if the mouse is over the tasks applet, even if the zoom on hover feature is disabled. I wasn't running anything resource intensive when it happened. I was only watching YouTube on Firefox and chatting through text on Discord.
(In reply to Michail Vourlakos from comment #5) > In commamd prompt what latte version it says with latte-dock -v ? Run it on Konsole. Output is the following: lattedock 20210527.git.5d8afda2
(In reply to ryu.ketsueki from comment #7) > (In reply to Michail Vourlakos from comment #5) > > In commamd prompt what latte version it says with latte-dock -v ? > > Run it on Konsole. Output is the following: > > lattedock 20210527.git.5d8afda2 1. You layout does not produce any issues in my system 2. why dock demonstrates the issue, the bottom one? 3. There is no such thing as reloading, Latte reloads only after crashing. There are some applets in your layout that I am not using in my system, they could be related to the crash, try remove them and see how it goes: --launchpadPlasmaMod --org.kde.plasma.virtualdesktopbar --org.kde.plasma.bigSur-inlineBattery --org.kde.plasma.win7showdesktop --org.kxn.cornerMenu 4. You have added two Latte Tasks in bottom dock, I suppose this is intentional from your side. Either way having multiple Latte Tasks is supported so it shouldnt be the faulter here. My guess is that one of your applets is creating crashes and this abnormal behavior.
5. For the cpu usage try to disable parabolic effect and "Thin tooltips on hovering", it might help
(In reply to Michail Vourlakos from comment #8) > (In reply to ryu.ketsueki from comment #7) > > (In reply to Michail Vourlakos from comment #5) > > > In commamd prompt what latte version it says with latte-dock -v ? > > > > Run it on Konsole. Output is the following: > > > > lattedock 20210527.git.5d8afda2 > > 1. You layout does not produce any issues in my system > 2. why dock demonstrates the issue, the bottom one? > 3. There is no such thing as reloading, Latte reloads only after crashing. > There are some applets in your layout that I am not using in my system, they > could be related to the crash, try remove them and see how it goes: > --launchpadPlasmaMod > --org.kde.plasma.virtualdesktopbar > --org.kde.plasma.bigSur-inlineBattery > --org.kde.plasma.win7showdesktop > --org.kxn.cornerMenu > > 4. You have added two Latte Tasks in bottom dock, I suppose this is > intentional from your side. Either way having multiple Latte Tasks is > supported so it shouldnt be the faulter here. > > My guess is that one of your applets is creating crashes and this abnormal > behavior. I've been using those applets for a very long time and they never caused this behavior. It started only yesterday. And I don't know what is causing the crashes exactly. It's why I added the part of CPU because I thought it could be related. What happens is that Latte freezes then crashes, causing the reload. After reloading, the bottom dock has this odd behavior. But it's not all the time so I don't know what could be causing the crash. DrKonqi doesn't appear when it crashes either. Is there a way to enable log to file in case it happens? That way I can add to the report when it happens again. So far I experienced this bug twice
(In reply to Michail Vourlakos from comment #9) > 5. For the cpu usage try to disable parabolic effect and "Thin tooltips on > hovering", it might help It's now on 10%. Is there a way of making this effect GPU accelerated instead of CPU?
(In reply to ryu.ketsueki from comment #11) > (In reply to Michail Vourlakos from comment #9) > > 5. For the cpu usage try to disable parabolic effect and "Thin tooltips on > > hovering", it might help > > It's now on 10%. Is there a way of making this effect GPU accelerated > instead of CPU? no
https://userbase.kde.org/LatteDock/HowToReportCrashes
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!