https://bugs.kde.org/show_bug.cgi?id=494589

            Bug ID: 494589
           Summary: Discover does not work and fails to update after
                    updating to 6.2.0
    Classification: Applications
           Product: Discover
           Version: 6.2.0
          Platform: Neon
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: Updates (interactive)
          Assignee: plasma-b...@kde.org
          Reporter: henrique.f.vel...@proton.me
                CC: aleix...@kde.org
  Target Milestone: ---

Created attachment 174733
  --> https://bugs.kde.org/attachment.cgi?id=174733&action=edit
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.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to