Created attachment 135993 [details] an archive of neccessary information about this bug SUMMARY STEPS TO REPRODUCE 1. Start latte-dock 2. Use or wait a few minutes 3. After a few minutes of running, the bug may appear OBSERVED RESULT showed in attachment file abnormal.mp4 EXPECTED RESULT showed in attachment file normal.mp4 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION The global theme I'm using is breeze dark, the plasma style is ROUNDED COLOR, and the application style is lightly. I will upload my latte configuration file in the attachment, but I've tried some other configurations that reproduce the bug, so the latte configuration file may not be required. The bug will appear after a few minutes of running, but I can't be sure exactly how many minutes, so maybe the developers need to test a little longer.
1. run latte from command line with: latte-dock -d , when that issue appears do you get any errors in the command line?
2. How did you install Latte git version? Is that the latest latest master version?
(In reply to Michail Vourlakos from comment #2) > 2. How did you install Latte git version? Is that the latest latest master > version? I follow the instruction at https://github.com/KDE/latte-dock/blob/master/INSTALLATION.md Yes, that is the latest master version.
(In reply to Michail Vourlakos from comment #1) > 1. run latte from command line with: latte-dock -d , when that issue > appears do you get any errors in the command line? I tried it. Actually I got some information but I'm not sure if this information is provided by the running software or by latte-dock, and I don't know if it's considered an error or not, but the information does seem abnormal. Here's the situation, first I started latte-dock and it worked fine. Then I double clicked to open an mp4 video that was playing full screen with vlc player, and when the video finished playing, the window would close automatically. After that， the bug appeared and the following message appeared in terminal： [00007fd1e0c08090] avcodec decoder: Using Intel iHD driver for Intel(R) Gen Graphics - 20.1.1 () for hardware decoding uint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&): Condition failed: menu uint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&): Condition failed: menu QFileSystemWatcher::removePaths: list is empty QFileSystemWatcher::removePaths: list is empty QObject::~QObject: Timers cannot be stopped from another thread [Debug : 16:57:19.407407] - " TASKS EXTENDED MANAGER Garbage Collector..." [Debug : 16:57:19.407407] - "IMMEDIATE LAUNCHERS :::" [Debug : 16:57:19.407407] - "TO BE ADDED LAUNCHERS :::" [Debug : 16:57:19.407407] - "TO BE MOVED LAUNCHERS ::: " [Debug : 16:57:19.408408] - "TO BE REMOVED LAUNCHERS ::: " [Debug : 16:57:19.408408] - "WAITING LAUNCHERS ::: " [Debug : 16:57:19.408408] - "FROZEN TASKS ::: "
1. if the video is not fullscreen does it still occur? 2. how did you set vlc to close after the video ends?
(In reply to Michail Vourlakos from comment #5) > 1. if the video is not fullscreen does it still occur? > 2. how did you set vlc to close after the video ends? 1. Let me fix my previous description, the video is not full screen, but maximized window. And I can't set it not to play maximized window, it does that by default. 2. By default config. I double clicked an video file in dolphin, and it was played by vlc media player. After the video ends, the maximized video window automatically closed and there was still a vlc player window which was not maximized and showed the playlist.
Just now I found another way to reproduce this bug. Place any app icon (I tried system settings, dolphin and terminal) in the first position of the latte-dock, then click that app, then maximize that window, then restore it, then close it, then open an app which is not pinned in the dock, then close that app, and then the bug will be successfully reproduced.
this is much larger than a slide-out animation you probably found the best way to reproduce a breakage for plasma libtaskmanager model. If you were using launchers in different activities and after the steps you are mentioning you were switching between different activities the tasks model is totally untrusted, double tasks, double launchers etc... I believe this is plasma libtaskmanager fault but this needs big in-depth investigation.
Git commit 7f9f418b7533fb4a487b27dcbc00cb719d0ff096 by Michail Vourlakos. Committed on 25/02/2021 at 15:17. Pushed by mvourlakos into branch 'master'. do not reanchor simple windows in real removal M +8 -3 plasmoid/package/contents/ui/task/animations/RealRemovalAnimation.qml https://invent.kde.org/plasma/latte-dock/commit/7f9f418b7533fb4a487b27dcbc00cb719d0ff096
(In reply to Michail Vourlakos from comment #9) > Git commit 7f9f418b7533fb4a487b27dcbc00cb719d0ff096 by Michail Vourlakos. > Committed on 25/02/2021 at 15:17. > Pushed by mvourlakos into branch 'master'. > > do not reanchor simple windows in real removal > > M +8 -3 > plasmoid/package/contents/ui/task/animations/RealRemovalAnimation.qml > > https://invent.kde.org/plasma/latte-dock/commit/ > 7f9f418b7533fb4a487b27dcbc00cb719d0ff096 Great! In this version this bug has not appeared again. Thank you very much!