Created attachment 174733 [details] Video demonstrating the bug. After updating to version 6.2.0, my system initially booted normally. However, after updating all packages and requiring a reboot, the graphics card stopped working, and I could only boot in Safe Mode. In Safe Mode, it used a different graphics processor (llvmpipe), and the system ran incredibly slowly, with the CPU almost constantly using 100% and RAM using 10GB. This issue persisted during my debugging process as I tried various methods to switch back to the original graphics card. I ran the command "sudo prime-select intel" to try to restore default settings, but after rebooting, it did not work. As the update was for a newer version of KDE, I attempted to switch back to my NVIDIA graphics card by using "sudo prime-select nvidia," but it gave the same result as the intel command. However, after rebooting, it reverted back to the Intel driver for some unknown reason, and my system seemed to work normally again. Now, onto the bug: I tried to update my software through the Discovery app, but it failed to update. It remained stuck at 0% and failed immediately after. Some things I have already tried: "pkcon update" => "No packages require updating to newer versions." "sudo apt update" => "All packages are up to date." This issue has been occurring since yesterday (Today: 12.10.24 / Yesterday: 11.10.24), and typically, I have at least one package to update every day. The problem is only apparent in the Discovery app, which fails to update.
Is this still reproducible?
(In reply to Harald Sitter from comment #1) > Is this still reproducible? Unfortunately no. But was reoccurring. Short answer it the bottom. I forgot to update the thread. Basically it was the flatpak packages that was always failing and I had do manually ipdate on the console with flatpak update. This was occurring and never fixed. But unfortunately my laptop died last month (motherboard) and since them I vhanged from x86 to ARM, but due to poor arm support I did not install KdE neon again. I still want to help and support it, but I lack the advanced knowledge to do it. Anyway, short answer is the flatpak was having problems to update and never fixed (this was the ultimate problem) and my motherboard died so I cannot provide any other information regarding this. If you still need any other information I can try to look for it. My nbme with all the other data (even the kde neon linux on x86) was not touched since the incident.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. 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. Closing as RESOLVED WORKSFORME.