Bug 422217

Summary: After opening and closing a Steam game, the dock won't rise to the expected height anymore.
Product: [Unmaintained] lattedock Reporter: Raphael Marx <raphael.marx>
Component: applicationAssignee: Michail Vourlakos <mvourlakos>
Status: RESOLVED WORKSFORME    
Severity: major CC: captain_rage, jontysewell
Priority: NOR    
Version First Reported In: git (master)   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Video of behavior

Description Raphael Marx 2020-05-29 09:57:40 UTC
Created attachment 128898 [details]
Video of behavior

SUMMARY
Opening and then closing a Steam game (like Dota 2 in my example), makes the dock get stuck a 3rd or 4th of the way up. While the game is running, the dock works fine. The problem only appears after quitting the game.


STEPS TO REPRODUCE
1. Run a Steam game (Dota 2 adn CS:GO tested)
2. Close said game
3. Move mouse to the dock's edge

OBSERVED RESULT
Dock barely comes up.

EXPECTED RESULT
Dock comes up to full height as defined by its config.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.15.0

ADDITIONAL INFORMATION
Kernel 5.6.14-gentoo
Latest Steam version available
Mesa 20.1.0
Comment 1 Jonty Sewell 2020-07-08 17:52:50 UTC
I believe I can corroborate this issue; however it occurs for me after suspending and resuming the compositor - which usually happens when playing a full-screen game from Steam.  My floating dock gets stuck in whatever position it was when the switch occured, whether it's onscreen, off the bottom edge, or somewhere inbetween.  I know it's still there because I can hover and get window previews.

I've got suspend/resume compositor on a keyboard shortcut (alt+shift+f12), and if I suspend it again, hover the dock to make it visible, then resume it, then the dock resumes normal behaviour.

Latte version: bf2c7ebb-git (from AUR)
Operating System: Arch Linux
KDE Plasma Version: 5.19.2
KDE Frameworks Version: 5.71.0
Qt Version: 5.15.0
Kernel Version: 5.7.7-zen1-1-zen
OS Type: 64-bit
Processors: 12 × Intel® Xeon® CPU X5660 @ 2.80GHz
Memory: 23.5 GiB of RAM
Graphics Processor: Radeon RX 580 Series
Comment 2 Michail Vourlakos 2020-07-16 12:49:28 UTC
Please recheck with latest master version that this is not fixed.
Comment 3 Jonty Sewell 2020-07-16 17:44:51 UTC
Sorry, just compiled and run rev 4b909796 (via aur) and the issue is still present when suspending and resuming the compositor.
Comment 4 Michail Vourlakos 2020-07-16 19:52:41 UTC
(In reply to Jonty Sewell from comment #3)
> Sorry, just compiled and run rev 4b909796 (via aur) and the issue is still
> present when suspending and resuming the compositor.

that behavior has started to point to Qt and compositor issues.
Comment 5 Michail Vourlakos 2021-03-07 11:57:04 UTC
This should be just fine with latest git version, please reopen if this is not the case
Comment 6 Bug Janitor Service 2021-03-22 04:33:40 UTC
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!
Comment 7 Bug Janitor Service 2021-04-06 04:33:34 UTC
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!