Ubuntu Support Template
Ubuntu Version: 24.04 LTS
Example: 22.04 LTS, 24.04, 25.10
Desktop Environment (if applicable): KDE Plasma 5.27.12
Example: GNOME, KDE Plasma, XFCE, Budgie, etc.
Problem Description: My Ubuntu system was operating and stable with 24.04 LTS. The upgrade to Kernel 7.0.0.28 broke the system, and it locked/crashed repeatedly, several times per day. I reverted to Kernel 6.17.0-40 and the system became functional again. I attempted to lock out any further updates to Kernel 7 until the problem resolved. However, after a few days of normal operation (and concurrent with the time of the root certificate updates), my graphics card (AMD Bonaire FirePro W5100) stopped functioning and my GPU driver in System Settings changed from Bonaire to llvmpipe. I can no longer access advanced functions under display and monitor, and my second monitor is no longer recognized (the graphics card supports 4). I have attempted to reinstall the amdgpu package, but it will not install due to repository certificate errors.
Relevant System Information:
Operating System: Ubuntu Studio 24.04
KDE Plasma Version: 5.27.12
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13
Kernel Version: 6.17.0-40-generic (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5500
Memory: 30.7 GiB of RAM
Graphics Processor: llvmpipe
Product Name: A520M Phantom Gaming 4
Graphics Card: AMD FirePro W5100 (Bonaire)
Screenshots or Error Messages:
NOTE: IP 192.168.1.254 is the LAN address of my AT&T Fiber Internet gateway.
E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/noble-updates/InRelease 400 Bad Request [IP: 192.168.1.254 80]
E: The repository ‘http://us.archive.ubuntu.com/ubuntu noble-updates InRelease’ is no longer signed.
W: Updating from such a repository can’t be done securely, and is therefore disabled by default.
W: See apt-secure(8) manpage for repository creation and user configuration details.
E: http://us.archive.ubuntu.com/ubuntu noble-updates InRelease is not (yet) available (400 Bad Request [IP: 192.168.1.254 80])
E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/noble-backports/InRelease 400 Bad Request [IP: 192.168.1.254 80]
E: The repository ‘http://us.archive.ubuntu.com/ubuntu noble-backports InRelease’ is no longer signed.
W: Updating from such a repository can’t be done securely, and is therefore disabled by default.
W: See apt-secure(8) manpage for repository creation and user configuration details.
E: http://us.archive.ubuntu.com/ubuntu noble-backports InRelease is not (yet) available (400 Bad Request [IP: 192.168.1.254 80])
E: https://repo.radeon.com/amdgpu/6.4.2/ubuntu noble InRelease is not (yet) available (Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown. The certificate chain uses expired certificate. The name in the certificate does not match the expected. Could not handshake: Error in the certificate verification. [IP: 192.168.1.254 443])
E: https://apt.enpass.io stable InRelease is not (yet) available (Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown. The certificate chain uses expired certificate. The name in the certificate does not match the expected. Could not handshake: Error in the certificate verification. [IP: 192.168.1.254 443])
E: https://repo.radeon.com/rocm/apt/6.4.2 noble InRelease is not (yet) available (Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown. The certificate chain uses expired certificate. The name in the certificate does not match the expected. Could not handshake: Error in the certificate verification. [IP: 192.168.1.254 443])
What I’ve Tried: As mentioned in description, I have reverted to Kernel 6.17.0-40generic, which temporarily fixed the problem. However, when the root certificate upgrade was pushed, it broke the system again.
Before Posting:
Please check if similar issues have already been reported and resolved.
I could not find any recent, similar reports.