Summary: | Latte crashed when changing virtual desktops | ||
---|---|---|---|
Product: | [Plasma] lattedock | Reporter: | bernardocrodrigues |
Component: | application | Assignee: | Michail Vourlakos <mvourlakos> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | Keywords: | drkonqi |
Priority: | NOR | ||
Version: | 0.9.3 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
bernardocrodrigues
2020-03-23 16:46:33 UTC
This points to plasma libtaskmanager, what is your plasma version? Does not look a Latte crash but rather plasma I have the following installed package: libtaskmanager6/eoan,now 4:5.16.5-0ubuntu1 amd64 I have some new info that can be related (did not notice when I filed the bug): Before the freeze happened, the launchers on my Latte Dock stated to get all crazy. They changed into another that was already pinned. For example, I normally have Dolphin, Konsole, Visual Studio and Firefox. When I switched virtual desktops, eventually the Firefox Laucher would become a Visual Studio (Now 2 visual studios on the dock). This error was local to a virtual desktop, if a switched to the next it would be different (normal or other case of duplication). Finally I noticed that it only happend to lauchers to the right of a "Separator". When I removed the separators from my dock, the duplication issue and the desktop freeze stopped. Thanks! 1. you should use a much newer version 0.9.3 is too old, this might have already been fixed. So please use either 0.9.11 or git version 2. provide a concrete way to reproduce the crash or the craziness Without [1] and [2] I consider it a plasma libtaskmanager issue and Latte can not do something. 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! |