SUMMARY after days or in some cases weeks after fresh installation; application menu and or task bar freezes completely or takes 20-30 seconds to respond to each click. Totally unusable. A reboot is the only known way to resolve the problem, only to reoccure just minutes or hours later after the reboot, or in some cases days later. Its seemingly random without any observable cause. there does not seem to be any specific application associated with this issues. It is NOT related to a lack of system resources. many of the systems have different kernels 4.19, 5.10, 5.14, 5.15. all these systems are being used by different people with completely different environments and use cases. none of these systems have kernel errors or any errors related to plasma or misbehaving apps in the system logs. all have different GPU's, amd, intel, nvidia and various models. so far we have many users all experiencing this issue. These systems are a mix of MX Linux Wildflower and also pure Debian 11 with KDE (both non-free and Live installs), both have exactly the same issue. Debian 11 and MX wildflower are both Plasma 5.20.5 Plasma Frameworks 5.78 Qt 5.15.2 Systems affected so far: Thinkpad 590 (i7 NVME SSD + 32GB ram) Thinkpad 540p (i7 SSD + 16GB ram) Thinkpad 480S (i7 SSD + 16GB ram) Thinkpad X250 (i5 SSD + 8GB ram) Thinkpad T430S (i5 and i7smultiple users) Min 8GB, most have 16GB Thinkpad T430 (i5 SSD + 16GB ram) Thinkpad T450s (i7 SSD + 20GB ram) HP Z220 (i7 SSD + 16GB RAM) HP Z230 (Xeon 2 stripped samsung EVO 870 500GB SSD + 32GB RAM) HP Persario, Elite PC (i7, 16GB RAM, SSD) Dell XPS 8700 (i7 5th gen, 2 stripped samsung EVO 870 500GB SSD, 32GB ram) Various other i3, and i5 custom built PCs with 8GB ram or more and all have SSDs STEPS TO REPRODUCE there are no know specific steps to reproduce this issue. It behaves like when MS Windows has a items in the start menu that points to a network location that no longer is accessible. Lags and waits for timeout, just for an example ADDITIONAL INFORMATION I mean no disrespect but all of are workflows are being seriously disrupted. we see no errors (not that we rally know where to dig deep anyway) and have no idea whats going on and have absolutely no way to fix this issue. We are all really weary after making considerable disruptions to peoples lives but migrating to Wildflower and Debian 11/KDE. We have no clue as to when this issue will be resolved or if ever it will be. We are left with little choice but to go back to Debian 11/Cinnamon if there is no timely resolution, because we never had any issues with cinnamon even though have many users using that for 5 years or more. Some users were so frustrated they just went out and bought new Macs because they just could deal with the stress this issue further caused them, obviously not solely related to this issue but still. Please do anything you can to help. i will provide any information im directed to.
many other poeple on the internet complaining about exactly the same issue in Debian 11 / KDE. No resolution yet. https://www.reddit.com/r/kde/comments/snhb2c/kde_panel_plasma_frozen_what_to_try/
> all these systems are being used by different people with completely different environments and use cases Are you an admin of a large Plasma deployment where this issue is appearing? Do you have any manual network mounts set up on these machines? You should also know that Plasma 5.20 is out of support; Debian really did something regrettable when they froze on a non-LTS version. Ideally that would have shipped 5.18 which was the LTS version. However at this point that version is also very old and also out of support, as we just released the new Plasma 5.24 LTS version. Is there a chance you can upgrade one of those systems to 5.24 and try again?
Also are these machines running X11 or Wayland? We recently had some freezing issues on Wayland (Bug 449163) that was fixed by a Qt change that was backported to the KDE patch collection.
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!