nvidia driver error: cannot open linker script file
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux-restricted-modules (Ubuntu) |
Confirmed
|
Undecided
|
Kuba Pawlak | ||
| linux-restricted-modules-hwe-6.14 (Ubuntu) |
Confirmed
|
Undecided
|
Kuba Pawlak | ||
Bug Description
-------
*** If you've come here from a duplicate bug ***
Please make sure you have the headers relevant to your kernel installed
For most people,
sudo apt install linux-headers-
-------
package linux-modules-
ProblemType: Package
DistroRelease: Ubuntu 25.04
Package: linux-modules-
ProcVersionSign
Uname: Linux 6.14.0-15-generic x86_64
NonfreeKernelMo
ApportVersion: 2.32.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
/dev/snd/seq: igor 2728 F.... pipewire
CasperMD5CheckR
Date: Sun Jun 22 10:04:44 2025
ErrorMessage: installed linux-modules-
InstallationDate: Installed on 2025-06-20 (2 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3)
MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=
Python3Details: /usr/bin/
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageV
SourcePackage: linux-restricte
Title: package linux-modules-
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/28/2021
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FX505DT.316
dmi.board.
dmi.board.name: FX505DT
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.
dmi.ec.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: TUF Gaming
dmi.product.name: TUF Gaming FX505DT_FX505DT
dmi.product.
dmi.sys.vendor: ASUSTeK COMPUTER INC.
| Igor Pustovit (qvbnd) wrote : | #1 |
- AlsaInfo.txt Edit (43.2 KiB, text/plain; charset="utf-8")
- AptOrdering.txt Edit (458 bytes, text/plain; charset="utf-8")
- CRDA.txt Edit (352 bytes, text/plain; charset="utf-8")
- CurrentDmesg.txt Edit (100.8 KiB, text/plain; charset="utf-8")
- Dependencies.txt Edit (4.1 KiB, text/plain; charset="utf-8")
- Df.txt Edit (770 bytes, text/plain; charset="utf-8")
- Dmesg.txt Edit (100.8 KiB, text/plain; charset="utf-8")
- DpkgHistoryLog.txt Edit (117.8 KiB, text/plain; charset="utf-8")
- DpkgTerminalLog.txt Edit (3.9 KiB, text/plain; charset="utf-8")
- DuplicateSignature.txt Edit (1.5 KiB, text/plain; charset="utf-8")
- IwDevWlp4s0Link.txt Edit (266 bytes, text/plain; charset="utf-8")
- Lspci.txt Edit (67.2 KiB, text/plain; charset="utf-8")
- Lspci-vt.txt Edit (2.2 KiB, text/plain; charset="utf-8")
- Lsusb.txt Edit (381 bytes, text/plain; charset="utf-8")
- Lsusb-t.txt Edit (6.7 KiB, text/plain; charset="utf-8")
- Lsusb-v.txt Edit (37.2 KiB, text/plain; charset="utf-8")
- ProcCpuinfo.txt Edit (11.2 KiB, text/plain; charset="utf-8")
- ProcCpuinfoMinimal.txt Edit (1.4 KiB, text/plain; charset="utf-8")
- ProcInterrupts.txt Edit (6.4 KiB, text/plain; charset="utf-8")
- ProcModules.txt Edit (6.8 KiB, text/plain; charset="utf-8")
- RfKill.txt Edit (113 bytes, text/plain; charset="utf-8")
- UdevDb.txt Edit (290.7 KiB, text/plain; charset="utf-8")
- WifiSyslog.txt Edit (121.4 KiB, text/plain; charset="utf-8")
- acpidump.txt Edit (620.2 KiB, text/plain; charset="utf-8")
| tags: | removed: need-duplicate-check |
| Launchpad Janitor (janitor) wrote : | #2 |
| Changed in linux-restricted-modules (Ubuntu): | |
| status: | New → Confirmed |
| Changed in linux-restricted-modules (Ubuntu): | |
| assignee: | nobody → Kuba Pawlak (kuba-t-pawlak) |
| Kuba Pawlak (kuba-t-pawlak) wrote (last edit ): | #3 |
A workaround for now is to install kernel headers with:
sudo apt install linux-headers-
| summary: |
- nvidia driver erorr + nvidia driver error: cannot open linker script file |
| Daniel Blanchard (dan-blanchard) wrote : | #4 |
Installing the generic headers does not seem to fix the issue for me when installing the drivers with:
`sudo ubuntu-drivers install --gpgpu nvidia:570-server` which still yields:
```
/usr/bin/ld.bfd: cannot open linker script file /usr/src/
/usr/bin/ld.bfd: cannot open linker script file /usr/src/
/usr/bin/ld.bfd: cannot open linker script file /usr/src/
/usr/bin/ld.bfd: cannot open linker script file /usr/src/
/usr/bin/ld.bfd: cannot open linker script file /usr/src/
sha256sum: nvidia-drm.ko: No such file or directory
nvidia-drm.ko: FAILED open or read
sha256sum: nvidia-modeset.ko: No such file or directory
nvidia-modeset.ko: FAILED open or read
sha256sum: nvidia-peermem.ko: No such file or directory
nvidia-peermem.ko: FAILED open or read
sha256sum: nvidia-uvm.ko: No such file or directory
nvidia-uvm.ko: FAILED open or read
sha256sum: nvidia.ko: No such file or directory
nvidia.ko: FAILED open or read
sha256sum: WARNING: 5 listed files could not be read
```
| Daniel Letzeisen (dtl131) wrote (last edit ): | #5 |
@dan-blanchard: You are not using the generic kernel, so install the headers for your kernel.
sudo apt install linux-headers-aws
| Launchpad Janitor (janitor) wrote : | #6 |
Status changed to 'Confirmed' because the bug affects multiple users.
| Changed in linux-restricted-modules-hwe-6.14 (Ubuntu): | |
| status: | New → Confirmed |
| Graeme Evans (snaveemearg01) wrote : | #7 |
Not affacting everyday operations. Just an error message after a software update.
| tags: | added: kernel-daily-bug |
| Vedran Rafaelic (croraf) wrote (last edit ): | #8 |
Trying to install nvidia-drivers-575 from nvidia-drivers-535 gave this same error, but also caused pretty severe consequences on my Ubuntu.
It corrupted the entire kernel so to say: no external keyboard, no internet, no bluetooth, defaluted to Nouveau. While debugging why I cannot do usb tethering any more I noticed that
`/lib/modules/
Luckily I was able to boot into older kernel which used Nouveau and recover from there.
NOTE: I have mobile Nvidia RTX 2080. Was previously on nvidia-driver-535
Kernel: 6.14.0-27-generic
| Daniel Letzeisen (dtl131) wrote : | #9 |
Do all these people really not have the kernel headers installed or is there something else going on here?
| Aswin Payyampally (aswinp610) wrote : | #10 |
how to recover
| Vedran Rafaelic (croraf) wrote (last edit ): | #11 |
- Screenshot from 2025-08-01 08-27-43.png Edit (47.9 KiB, image/png)
Update to nvidia-drivers-575 corrupted my kernel completely, no usb tethering, no keyboard, no bluetooth, probably many more things. I managed to recover luckily by booting the old kernel. And reinstalling the 6.14.0-27 kernel again. But I still have issues, after installing nvidia-drivers-550.
I particular I have this kernel now (uname -a): 6.14.0-27-generic #27~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC
But apt list --upgradable suggests: linux-image-
Trying to install the new kernel gives following warning: (check attachment)
| Vedran Rafaelic (croraf) wrote : | #12 |
- Screenshot from 2025-08-01 08-33-30.png Edit (68.1 KiB, image/png)
Also on starting of Software Updater application it shows: "Not all updates can be installed" and am unable to select any linux package (check attachment)
| Serge (sspapilin) wrote : | #13 |
This happened for my desktop (Ubuntu 24.04, HWE generic kernel, nvidia drivers 570). It broke after an unattended upgrade.
I suspect it happened because the unattended upgrade tried to upgrade linux-modules-
Why don't these nvidia-module packages depend on the corresponding version of kernel header packages?
| Francisco José Parente Ferreira (chicojpferreira) wrote : Re: [Bug 2115148] Re: nvidia driver error: cannot open linker script file | #14 |
That's probably what happened.
I updated the packages and rebooted. The problem didn't recur.
I usually report bugs through Ubuntu, but they did change the format and
open the web page. So I reported the bug through the website. However, it
didn't persist. It just reported it twice in a row.
Em sex., 1 de ago. de 2025 às 09:20, Serge <email address hidden>
escreveu:
> This happened for my desktop (Ubuntu 24.04, HWE generic kernel, nvidia
> drivers 570). It broke after an unattended upgrade.
>
> I suspect it happened because the unattended upgrade tried to upgrade
> linux-modules-
> before linux-generic-
> required apt header files were not installed yet.
>
> Why don't these nvidia-module packages depend on the corresponding
> version of kernel header packages?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2117257).
> https:/
>
> Title:
> nvidia driver error: cannot open linker script file
>
> Status in linux-restricte
> Confirmed
> Status in linux-restricte
> Confirmed
>
> Bug description:
> package linux-modules-
> to install/upgrade: installed linux-modules-
> nvidia-
> subprocess returned error exit status 1
>
> ProblemType: Package
> DistroRelease: Ubuntu 25.04
> Package: linux-modules-
> ProcVersionSign
> Uname: Linux 6.14.0-15-generic x86_64
> NonfreeKernelMo
> ApportVersion: 2.32.0-0ubuntu5
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC1: igor 2732 F.... wireplumber
> /dev/snd/controlC0: igor 2732 F.... wireplumber
> /dev/snd/seq: igor 2728 F.... pipewire
> CasperMD5CheckR
> Date: Sun Jun 22 10:04:44 2025
> ErrorMessage: installed linux-modules-
> package post-installation script subprocess returned error exit status 1
> InstallationDate: Installed on 2025-06-20 (2 days ago)
> InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64
> (20250415.3)
> MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT
> ProcFB: 0 amdgpudrmfb
> ProcKernelCmdLine: BOOT_IMAGE=
> root=UUID=
> crashkernel=
> vt.handoff=7
> Python3Details: /usr/bin/
> 3.13.3-1
> PythonDetails: N/A
> RebootRequiredPkgs: Error: path contained symlinks.
> RelatedPackageV
> SourcePackage: linux-restricte
> Title: package linux-modules-
> failed to install/upgrade: installed
> linux-modules-
> subpr...
| Vedran Rafaelic (croraf) wrote (last edit ): | #15 |
Adding to my previous comments.
I don't know how I got this linux-image-
Could it be the attempt of installation of nvidia-driver-575 installed this? Because I guess I didn't have linux-image-
Now I deleted it and installed linux-image-
Now from the linux-image-
| Vedran Rafaelic (croraf) wrote : | #16 |
- term_copy.log Edit (7.2 KiB, text/plain)
I don't know why term.log and history shows only 535, when I selected 570.
History log here
Start-Date: 2025-08-02 13:01:17
Commandline: packagekit role='remove-
Requested-By: croraf (1000)
Install: libnvidia-
Remove: libnvidia-
End-Date: 2025-08-02 13:01:38
term.log in attachment.
| Vedran Rafaelic (croraf) wrote (last edit ): | #17 |
Ok, now I again (with the clean linux-image-
Note, if worth, let me also say that now after all this upgrade the `apt list --upgradable` shows this line:
ubuntu-
(Perhaps this appeared after migrating to the 27 kernel.)
But trying to upgrade shows: The following upgrades have been deferred due to phasing:
ubuntu-
| Nestor Caffa (nestorcaffa-m) wrote : | #18 |
Dear Vedram
Unfortunately I couldn't solve it and I had to reinstall the operating
system.
As a fact I tell you that the machine worked in 640 x 480 (it could not be
changed) nor did the network board work, I guess it must have been the
chipset driver of the motherboard.
Thank you for your concern.
Best regards
Nestor
El sáb, 2 de ago de 2025, 08:30, Vedran Rafaelic <email address hidden>
escribió:
> Ok, now I again (with the clean linux-image-
> headers-
> (propriatery, tested) through Additional Drivers and the new driver is
> working correctly now.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2119307).
> https:/
>
> Title:
> nvidia driver error: cannot open linker script file
>
> Status in linux-restricte
> Confirmed
> Status in linux-restricte
> Confirmed
>
> Bug description:
> package linux-modules-
> to install/upgrade: installed linux-modules-
> nvidia-
> subprocess returned error exit status 1
>
> ProblemType: Package
> DistroRelease: Ubuntu 25.04
> Package: linux-modules-
> ProcVersionSign
> Uname: Linux 6.14.0-15-generic x86_64
> NonfreeKernelMo
> ApportVersion: 2.32.0-0ubuntu5
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC1: igor 2732 F.... wireplumber
> /dev/snd/controlC0: igor 2732 F.... wireplumber
> /dev/snd/seq: igor 2728 F.... pipewire
> CasperMD5CheckR
> Date: Sun Jun 22 10:04:44 2025
> ErrorMessage: installed linux-modules-
> package post-installation script subprocess returned error exit status 1
> InstallationDate: Installed on 2025-06-20 (2 days ago)
> InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64
> (20250415.3)
> MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT
> ProcFB: 0 amdgpudrmfb
> ProcKernelCmdLine: BOOT_IMAGE=
> root=UUID=
> crashkernel=
> vt.handoff=7
> Python3Details: /usr/bin/
> 3.13.3-1
> PythonDetails: N/A
> RebootRequiredPkgs: Error: path contained symlinks.
> RelatedPackageV
> SourcePackage: linux-restricte
> Title: package linux-modules-
> failed to install/upgrade: installed
> linux-modules-
> subprocess returned error exit status 1
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 01/28/2021
> dmi.bios.release: 5.14
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: FX505DT.316...
| Vedran Rafaelic (croraf) wrote (last edit ): | #19 |
Hi Nestor.
I'm just a regular user, so I cannot provide proper assistance.
I'm pretty sure that trying to install nvidia-driver-575 corrupted my entire kernel with similar issues (no network, no external keyboard, no bluetooth). But I was able to boot into the old kernel (just without nvidia driver but with nouveau driver only).
Were you able to boot the old kernel?
| Nestor Caffa (nestorcaffa-m) wrote : | #20 |
I couldn't do it, I was in a hurry to work with the team again and I
reinstalled a copy of ubuntu.
I'm sorry I can't give you more help.
El sáb, 2 de ago de 2025, 17:30, Vedran Rafaelic <email address hidden>
escribió:
> Hi Nestor.
> I'm just a regular user, so I cannot provide proper assistance.
>
> I'm pretty sure that trying to install nvidia-driver-575 corrupted my
> entire kernel with similar issues (no network, no external keyboard, no
> bluetooth). But I was able to boot into the old kernel (just without
> nvidia driver but with nouveau driver only).
>
> Were you able to boot the old kernel?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2119307).
> https:/
>
> Title:
> nvidia driver error: cannot open linker script file
>
> Status in linux-restricte
> Confirmed
> Status in linux-restricte
> Confirmed
>
> Bug description:
> package linux-modules-
> to install/upgrade: installed linux-modules-
> nvidia-
> subprocess returned error exit status 1
>
> ProblemType: Package
> DistroRelease: Ubuntu 25.04
> Package: linux-modules-
> ProcVersionSign
> Uname: Linux 6.14.0-15-generic x86_64
> NonfreeKernelMo
> ApportVersion: 2.32.0-0ubuntu5
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC1: igor 2732 F.... wireplumber
> /dev/snd/controlC0: igor 2732 F.... wireplumber
> /dev/snd/seq: igor 2728 F.... pipewire
> CasperMD5CheckR
> Date: Sun Jun 22 10:04:44 2025
> ErrorMessage: installed linux-modules-
> package post-installation script subprocess returned error exit status 1
> InstallationDate: Installed on 2025-06-20 (2 days ago)
> InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64
> (20250415.3)
> MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT
> ProcFB: 0 amdgpudrmfb
> ProcKernelCmdLine: BOOT_IMAGE=
> root=UUID=
> crashkernel=
> vt.handoff=7
> Python3Details: /usr/bin/
> 3.13.3-1
> PythonDetails: N/A
> RebootRequiredPkgs: Error: path contained symlinks.
> RelatedPackageV
> SourcePackage: linux-restricte
> Title: package linux-modules-
> failed to install/upgrade: installed
> linux-modules-
> subprocess returned error exit status 1
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 01/28/2021
> dmi.bios.release: 5.14
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: FX505DT.316
> dmi.board.
| Aldas Zarnauskas (aldas02027) wrote : | #21 |
I installed the Linux header sudo apt install linux-headers-
| aberner (berner) wrote : | #22 |
Same here with kernel 6.14.0-27-generic and Nvidia 470.
After upgrade can not boot into 6.14.0-27 only 6.11.0-26-generic works.
Logfile /var/lib/
make[3]: *** [/usr/src/
make[2]: *** [/usr/src/
there's a compile error:
nvidia/
23 | return follow_pfn(vma, address, pfn);
| ^~~~~~~~~~
| folio_pfn
| Daniel Letzeisen (dtl131) wrote : | #23 |
@aberner: You are in the wrong bug. See bug 2110338
| Nestor Caffa (nestorcaffa-m) wrote : | #24 |
Dear ,Unfortunately I couldn't solve it and I had to reinstall the
operating system. As a fact I tell you that the machine worked in 640 x
480 (it could not be changed) nor did the network board work, I guess it
must have been the chipset driver of the motherboard. Thank you for your
concern.…
El 7/8/25 a las 5:36, aberner escribió:
> Same here with kernel 6.14.0-27-generic and Nvidia 470.
>
> After upgrade can not boot into 6.14.0-27 only 6.11.0-26-generic works.
>
> Logfile /var/lib/
>
> make[3]: *** [/usr/src/
> make[2]: *** [/usr/src/
>
> there's a compile error:
>
> nvidia/
> 23 | return follow_pfn(vma, address, pfn);
> | ^~~~~~~~~~
> | folio_pfn
>
| Andreas (spicavirgo) wrote (last edit ): | #25 |
- synaptics1.png Edit (36.3 KiB, image/png)
@Daniel Letzeisen: Thank you for your help. As you said above, the corresponding linux-header for the linux-kernel in use caused my problems (loss of WLAN, LAN, touchpad).
I don't know why the missing linux-header was not installed by the Ubuntu updater. First time, I run into such a problem.
My workaround was:
- Reboot PC and activate GRUB menu.
- Start Ubuntu with the previous kernel (in my case linux kernel 6.14.0-28). That gives me back my network connection.
- Open synaptic (package management app) and search for installed "linux-headers".
- Found package "linux-
- Let synaptic update the "linux-
- Restart PC as always/normal: system ok :-)
| Roger Fang (geeky-1) wrote : | #26 |
My computer crashed yesterday with an I/O or USB error and when I rebooted,
the LAN port no longer worked and it also didn't recognize my 4K GPU card
and went into a low resolution VGA mode. After several reboots, I suspected
it was a motherboard issue and pulled my drives and GPU and inserted into
another computer, however, that computer also didn't use the GPU card for
4K display, but integrated video for VGA mode as well as not being able to
use the LAN port for Internet connection. It also complained about a
partial upgrade, which it wasn't able to complete without LAN/Internet
connection. I assumed the operating system was corrupt and inserted a
bootable USB with Ubuntu 24.04.3 LTS, but after booting to the GRUB it
launched Ubuntu without reinstalling and the GPU as well as LAN port worked
again and I was able to swap the drives and GPU back to my original
computer and have it work again.
On Thu, Aug 7, 2025 at 10:10 AM Nestor Caffa <email address hidden>
wrote:
> Dear ,Unfortunately I couldn't solve it and I had to reinstall the
> operating system. As a fact I tell you that the machine worked in 640 x
> 480 (it could not be changed) nor did the network board work, I guess it
> must have been the chipset driver of the motherboard. Thank you for your
> concern.…
>
> El 7/8/25 a las 5:36, aberner escribió:
> > Same here with kernel 6.14.0-27-generic and Nvidia 470.
> >
> > After upgrade can not boot into 6.14.0-27 only 6.11.0-26-generic works.
> >
> > Logfile /var/lib/
> >
> > make[3]: *** [/usr/src/
> Fehler 2
> > make[2]: *** [/usr/src/
> __sub-make] Fehler 2
> >
> > there's a compile error:
> >
> > nvidia/
> ‘follow_pfn’; did you mean ‘folio_pfn’?
> [-Werror=
> > 23 | return follow_pfn(vma, address, pfn);
> > | ^~~~~~~~~~
> > | folio_pfn
> >
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> nvidia driver error: cannot open linker script file
>
> Status in linux-restricte
> Confirmed
> Status in linux-restricte
> Confirmed
>
> Bug description:
> package linux-modules-
> to install/upgrade: installed linux-modules-
> nvidia-
> subprocess returned error exit status 1
>
> ProblemType: Package
> DistroRelease: Ubuntu 25.04
> Package: linux-modules-
> ProcVersionSign
> Uname: Linux 6.14.0-15-generic x86_64
> NonfreeKernelMo
> ApportVersion: 2.32.0-0ubuntu5
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC1: igor 2732 F.... wireplumber
> /dev/snd/controlC0: igor 2732 F.... wireplumber
> /dev/snd/seq: ...
| Changed in linux-restricted-modules-hwe-6.14 (Ubuntu): | |
| assignee: | nobody → Juerg Haefliger (juergh) |
| assignee: | Juerg Haefliger (juergh) → Kuba Pawlak (kuba-t-pawlak) |
| information type: | Public → Public Security |
| Vedran Rafaelic (croraf) wrote : | #27 |
Now after did another update through Software Updates app, and restarted, my system reverted to Nuveau, and trying to pick Nvidia driver gives me that post-script error again.
| Daniel Letzeisen (dtl131) wrote : | #28 |
@Vedran: I would try installing the dkms package instead of the pre-built nvidia modules. Switch to nouveau in driver manager, or purge out your nvidia driver packages.
sudo apt install nvidia-
(omit the "-open" from the package names if using an Nvidia Maxwell or Pascal GPU)
If you use SecureBoot, you do need to sign the nvidia modules once (most systems use SecureBoot unless you disable it in BIOS/EFI):
https:/
Nvidia package will run kmodsign automatically. You don't need to worry about that part.
If you are on a screen with an <Ok> button and you cannot click it, press the tab key to access the <Ok> button.
| Christopher Ottley (cottley) wrote : | #29 |
This happened to me on a brand new 24.04 installation. I did not have build-essential or the kernel headers installed. I did an update and the nvidia drivers tried to compile modules but can't (no gcc and no headers). After a reboot the running kernel changed (because it was updated) and the older drivers won't work. To fix:
- Install headers matching the running kernel
$ sudo apt install linux-headers-
- Install build-essential
$ sudo apt install build-essential
- Check the recommended drivers
$ ubuntu-drivers devices
- Install recommended driver
$ ubuntu-drivers autoinstall
| Daniel Letzeisen (dtl131) wrote : | #30 |
@Christopher. The -headers-
| Vedran Rafaelic (croraf) wrote : | #31 |
@Daniel dtl131: I purged the (once again) corrupted kernel (which got corrupted on software update using Software Updater). This was not easy though.
I purged the nvidia packages targeting this kernel also.
I'm on the older kernel now, and using Nuveaou driver.
1. Do you suggest that I use apt in the terminal rather than using the Additional Drivers GUI?
2. If so is this for debugging purposes?
3. If I remember correctly (from the last time this happened) using Additional Drivers GUI might work now, should I try it first?
| Vedran Rafaelic (croraf) wrote (last edit ): | #32 |
The Nouveau driver works great btw now with Nvidia RTX 2080. Using wayland display server.
| Daniel Letzeisen (dtl131) wrote : | #33 |
@Vedran: Yes, I recommend using the terminal instead of the additional driver manager GUI, because the GUI seems to install the pre-built modules that are triggering this bug for hundreds (probably thousands) of people. With apt, you can force the dkms version:
sudo apt install nvidia-
| description: | updated |
| Vedran Rafaelic (croraf) wrote (last edit ): | #34 |
Ok, I tried to install it once again using Additional Drivers GUI (nvidia-
No error shown but...
As suspected previously, THIS ACTION INSTALLS NEW KERNEL for some reason (6.14.0-32-generic) (likely the most recent available?) and this one gets booted next time. And because this new kernel got only partially installed (is thus corrupted) nothing works.
And I also suspect that if you are already on the latest kernel, the update of Nvidia drivers through Additional Drivers GUI works fine. As I think this worked for me last time. Update kernel first, then the drivers should work fine.
| Vedran Rafaelic (croraf) wrote (last edit ): | #35 |
DEBUGGED!!!
The issue in my case comes from the fact that, if you are not on the latest available kernel, updating nvidia drivers (and first time I did it using Software Updater!!! which I think just uses APT under the hood, and verified also using Additional Drivers), automatically tries to install latest kernel, which succeeds only partially.
The kernel then gets booted and is corrupted.
If, I'm already on the latest kernel (6.14.0-32-generic as of now) updating nvidia-drivers through Additioanl Drivers works perfectly (just updated with that on 570-open and 580 closed kernel).
EDIT: Oh I see the note now on the original post. Yes, the headers do not get installed with this automatic latest kernel installation.
| Martin Modrák (modrakm) wrote : | #36 |
The same issue happened for me after upgrading from 6.14.0-34-generic to 6.14.0-35-generic. No Wi-Fi, no Bluetooth, no external display. I fixed it by:
1) Booting into the older version of kernel via Grub (Advanced boot options for ubuntu) - immediately everything works again
2) Manually installing the headers:
sudo apt install linux-headers-
Now everything works also in the new kernel.
| Eduardo Razera (erazera) wrote : | #37 |
Hey i appreciate the response, i'm having the same problem that you
described. I've tried booting up using older versions and it did indeed
solve the problem but i tried using the command you sent: "sudo apt install
linux-headers-
Selecting previously unselected package linux-hwe-
(Reading database ... 272837 files and directories currently installed.)
Preparing to unpack
.../linux-
Unpacking linux-hwe-
Selecting previously unselected package linux-headers-
Preparing to unpack
.../linux-
Unpacking linux-headers-
Setting up linux-modules-
(6.14.0-
linux-image-
/usr/bin/ld.bfd: warning: --package-metadata is empty, ignoring
/usr/bin/ld.bfd: warning: --package-metadata is empty, ignoring
/usr/bin/ld.bfd: warning: --package-metadata is empty, ignoring
/usr/bin/ld.bfd: warning: --package-metadata is empty, ignoring
/usr/bin/ld.bfd: warning: --package-metadata is empty, ignoring
/usr/bin/ld.bfd: warning: --package-metadata is empty, ignoring
/usr/bin/ld.bfd: warning: --package-metadata is empty, ignoring
/usr/bin/ld.bfd: cannot open linker script file
/usr/src/
or directory
/usr/bin/ld.bfd: cannot open linker script file
/usr/src/
or directory
/usr/bin/ld.bfd: cannot open linker script file
/usr/src/
or directory
/usr/bin/ld.bfd: cannot open linker script file
/usr/src/
or directory
/usr/bin/ld.bfd: cannot open linker script file
/usr/src/
or directory
sha256sum: nvidia-drm.ko: No such file or directory
nvidia-drm.ko: FAILED open or read
sha256sum: nvidia-modeset.ko: No such file or directory
nvidia-modeset.ko: FAILED open or read
sha256sum: nvidia-peermem.ko: No such file or directory
nvidia-peermem.ko: FAILED open or read
sha256sum: nvidia-uvm.ko: No such file or directory
nvidia-uvm.ko: FAILED open or read
sha256sum: nvidia.ko: No such file or directory
nvidia.ko: FAILED open or read
sha256sum: WARNING: 5 listed files could not be read
dpkg: error processing package linux-modules-
(--configure):
installed linux-modules-
post-installation script subprocess returned error exit status 1
Setting up linux-hwe-
dpkg: dependency problems prevent configuration of
linux-modules-
linux-
linux-modules-
however:
Package linux-modules-
dpkg: error processing packa...
| Daniel Letzeisen (dtl131) wrote : | #38 |
I have no idea why these nvidia module packages do not depend on the headers if they're needed.
@Eduardo: You also need to install linux-headers-
| Eduardo Razera (erazera) wrote : | #39 |
I did the command and it worked. To do that I booted into the older
version, but after installing the news ones, if I boot normally on grub the
same issues persists, no WiFi, Bluetooth and the trackpad doesn’t work.
Should I do anything else to fix this?
Just to recap what I did was but using the advanced options into an older
version -33 kernel, updated it to 34 and 35, restarted and booted normally
just choosing Ubuntu on the Grub options but all the problem listed above
continued
Em seg., 10 de nov. de 2025 às 11:45, Daniel Letzeisen <
<email address hidden>> escreveu:
> I have no idea why these nvidia module packages do not depend on the
> headers if they're needed.
>
> @Eduardo: You also need to install linux-headers-
> because you still have -34 kernel installed.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2130786).
> https:/
>
> Title:
> nvidia driver error: cannot open linker script file
>
> Status in linux-restricte
> Confirmed
> Status in linux-restricte
> Confirmed
>
> Bug description:
>
> -------
> *** If you've come here from a duplicate bug ***
>
> Please make sure you have the headers relevant to your kernel installed
> For most people,
> sudo apt install linux-headers-
>
> -------
>
>
> package linux-modules-
> to install/upgrade: installed linux-modules-
> package post-installation script subprocess returned error exit status 1
>
> ProblemType: Package
> DistroRelease: Ubuntu 25.04
> Package: linux-modules-
> ProcVersionSign
> Uname: Linux 6.14.0-15-generic x86_64
> NonfreeKernelMo
> ApportVersion: 2.32.0-0ubuntu5
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC1: igor 2732 F.... wireplumber
> /dev/snd/controlC0: igor 2732 F.... wireplumber
> /dev/snd/seq: igor 2728 F.... pipewire
> CasperMD5CheckR
> Date: Sun Jun 22 10:04:44 2025
> ErrorMessage: installed linux-modules-
> package post-installation script subprocess returned error exit status 1
> InstallationDate: Installed on 2025-06-20 (2 days ago)
> InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64
> (20250415.3)
> MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT
> ProcFB: 0 amdgpudrmfb
> ProcKernelCmdLine: BOOT_IMAGE=
> root=UUID=
> crashkernel=
> vt.handoff=7
> Python3Details: /usr/bin/
> 3.13.3-1
> PythonDetails: N/A
> RebootRequiredPkgs: Error: path contained symlinks.
...
| Eduardo Razera (erazera) wrote : | #40 |
Heyy sorry to bother you guys again, but im still having the same issue.
When i boot into older versions of the kernel it works fine. But even if I
update when i boot normally the same thing happens - no wifi, no Bluetooth
and no trackpad
Em seg., 10 de nov. de 2025 às 15:31, Eduardo Razera <email address hidden>
escreveu:
> I did the command and it worked. To do that I booted into the older
> version, but after installing the news ones, if I boot normally on grub the
> same issues persists, no WiFi, Bluetooth and the trackpad doesn’t work.
> Should I do anything else to fix this?
>
> Just to recap what I did was but using the advanced options into an older
> version -33 kernel, updated it to 34 and 35, restarted and booted normally
> just choosing Ubuntu on the Grub options but all the problem listed above
> continued
>
> Em seg., 10 de nov. de 2025 às 11:45, Daniel Letzeisen <
> <email address hidden>> escreveu:
>
>> I have no idea why these nvidia module packages do not depend on the
>> headers if they're needed.
>>
>> @Eduardo: You also need to install linux-headers-
>> because you still have -34 kernel installed.
>>
>> --
>> You received this bug notification because you are subscribed to a
>> duplicate bug report (2130786).
>> https:/
>>
>> Title:
>> nvidia driver error: cannot open linker script file
>>
>> Status in linux-restricte
>> Confirmed
>> Status in linux-restricte
>> Confirmed
>>
>> Bug description:
>>
>> -------
>> *** If you've come here from a duplicate bug ***
>>
>> Please make sure you have the headers relevant to your kernel installed
>> For most people,
>> sudo apt install linux-headers-
>>
>> -------
>>
>>
>> package linux-modules-
>> to install/upgrade: installed linux-modules-
>> package post-installation script subprocess returned error exit status 1
>>
>> ProblemType: Package
>> DistroRelease: Ubuntu 25.04
>> Package: linux-modules-
>> ProcVersionSign
>> Uname: Linux 6.14.0-15-generic x86_64
>> NonfreeKernelMo
>> ApportVersion: 2.32.0-0ubuntu5
>> Architecture: amd64
>> AudioDevicesInUse:
>> USER PID ACCESS COMMAND
>> /dev/snd/controlC1: igor 2732 F.... wireplumber
>> /dev/snd/controlC0: igor 2732 F.... wireplumber
>> /dev/snd/seq: igor 2728 F.... pipewire
>> CasperMD5CheckR
>> Date: Sun Jun 22 10:04:44 2025
>> ErrorMessage: installed linux-modules-
>> package post-installation script subprocess returned error exit status 1
>> InstallationDate: Installed on 2025-06-20 (2 days ago)
>> InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64
>> (20250415.3)
>> MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT
>> P...
| Kuba Pawlak (kuba-t-pawlak) wrote (last edit ): | #41 |
Drivers installed via linux-modules-
Only DKMS set supports booting into old kernels because the drivers are compiled on the machine, for all kernels present, so old kernels get the latest driver that matches the latest userspace. This breaks secure boot as the drivers are not signed with Canonical key, so if it is a must, you would need to enroll your MOK into EFI.
You can switch with:
sudo apt remove linux-modules-
sudo apt install nvidia-driver-570
Or go for 580 driver with:
sudo apt install nvidia-driver-580
| Eduardo Razera (erazera) wrote : | #42 |
Thanks for the reply Kuba!
Although im not gonna lie, i found it confusing to understand what you
sent.
Basically what happened is when the drivers updated they broke with the new
35 kernel?
And what i should do is boot into the version that is working
do this - sudo apt remove linux-modules-
and then sudo apt install nvidia-driver-570
reboot and boot normally to see if its fixed?
Again really appreciate the response
Em qua., 12 de nov. de 2025 às 10:01, Kuba Pawlak <
<email address hidden>> escreveu:
> Drivers installed via linux-modules-
> older version kernels. The issue is in userspace compatibility. NVIDIA does
> not support mixing driver and userspace versions, this must be the exact
> version. Linux-modules-
> specific version. Each kernel has only one matching l-m-n package, so your
> current kernel has the latest nvidia driver, but older kernels have old
> drivers in their respective module trees. But there is only one userspace
> set, the one shipped with the latest driver. This means booting an older
> kernel break 1:1 kernel>userspace relationship and you end up with black
> screen.
> Only DKMS set supports booting into old kernels because the drivers are
> compiled on the machine, for all kernels present, so old kernels get the
> latest driver that matches the latest userspace. This breaks secure boot as
> the drivers are not signed with Canonical key, so if it is a must, you
> would need to enroll your MOK into EFI.
> You can switch with:
> sudo apt remove linux-modules-
> sudo apt install nvidia-driver-570
>
> Or go for 580 driver with:
> sudo apt install nvidia-driver-580
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2130786).
> https:/
>
> Title:
> nvidia driver error: cannot open linker script file
>
> Status in linux-restricte
> Confirmed
> Status in linux-restricte
> Confirmed
>
> Bug description:
>
> -------
> *** If you've come here from a duplicate bug ***
>
> Please make sure you have the headers relevant to your kernel installed
> For most people,
> sudo apt install linux-headers-
>
> -------
>
>
> package linux-modules-
> to install/upgrade: installed linux-modules-
> package post-installation script subprocess returned error exit status 1
>
> ProblemType: Package
> DistroRelease: Ubuntu 25.04
> Package: linux-modules-
> ProcVersionSign
> Uname: Linux 6.14.0-15-generic x86_64
> NonfreeKernelMo
> ApportVersion: 2.32.0-0ubuntu5
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC1: igor 2732 F.... wireplumber
> /dev/snd/controlC0: i...
| Daniel Letzeisen (dtl131) wrote : | #43 |
500 people affected now and still no dependency on the headers? I'm getting tired of marking duplicates..
| Eduardo Razera (erazera) wrote : | #44 |
i still haven't been able to fix it, tried what was told on the email
replies but it didn't work
Em qua., 26 de nov. de 2025 às 20:10, Daniel Letzeisen <
<email address hidden>> escreveu:
> 500 people affected now and still no dependency on the headers? I'm
> getting tired of marking duplicates..
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2130786).
> https:/
>
> Title:
> nvidia driver error: cannot open linker script file
>
> Status in linux-restricte
> Confirmed
> Status in linux-restricte
> Confirmed
>
> Bug description:
>
> -------
> *** If you've come here from a duplicate bug ***
>
> Please make sure you have the headers relevant to your kernel installed
> For most people,
> sudo apt install linux-headers-
>
> -------
>
>
> package linux-modules-
> to install/upgrade: installed linux-modules-
> package post-installation script subprocess returned error exit status 1
>
> ProblemType: Package
> DistroRelease: Ubuntu 25.04
> Package: linux-modules-
> ProcVersionSign
> Uname: Linux 6.14.0-15-generic x86_64
> NonfreeKernelMo
> ApportVersion: 2.32.0-0ubuntu5
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC1: igor 2732 F.... wireplumber
> /dev/snd/controlC0: igor 2732 F.... wireplumber
> /dev/snd/seq: igor 2728 F.... pipewire
> CasperMD5CheckR
> Date: Sun Jun 22 10:04:44 2025
> ErrorMessage: installed linux-modules-
> package post-installation script subprocess returned error exit status 1
> InstallationDate: Installed on 2025-06-20 (2 days ago)
> InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64
> (20250415.3)
> MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT
> ProcFB: 0 amdgpudrmfb
> ProcKernelCmdLine: BOOT_IMAGE=
> root=UUID=
> crashkernel=
> vt.handoff=7
> Python3Details: /usr/bin/
> 3.13.3-1
> PythonDetails: N/A
> RebootRequiredPkgs: Error: path contained symlinks.
> RelatedPackageV
> SourcePackage: linux-restricte
> Title: package linux-modules-
> failed to install/upgrade: installed
> linux-modules-
> subprocess returned error exit status 1
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 01/28/2021
> dmi.bios.release: 5.14
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios...
| Stefan (chemol-e) wrote : | #45 |
I think I run into this problem with every single kernel update now. It's really annoying.
Am 27. November 2025 01:00:34 MEZ schrieb Eduardo Razera <email address hidden>:
>i still haven't been able to fix it, tried what was told on the email
>replies but it didn't work
>
>Em qua., 26 de nov. de 2025 às 20:10, Daniel Letzeisen <
><email address hidden>> escreveu:
>
>> 500 people affected now and still no dependency on the headers? I'm
>> getting tired of marking duplicates..
>>
>> --
>> You received this bug notification because you are subscribed to a
>> duplicate bug report (2130786).
>> https:/
>>
>> Title:
>> nvidia driver error: cannot open linker script file
>>
>> Status in linux-restricte
>> Confirmed
>> Status in linux-restricte
>> Confirmed
>>
>> Bug description:
>>
>> -------
>> *** If you've come here from a duplicate bug ***
>>
>> Please make sure you have the headers relevant to your kernel installed
>> For most people,
>> sudo apt install linux-headers-
>>
>> -------
>>
>>
>> package linux-modules-
>> to install/upgrade: installed linux-modules-
>> package post-installation script subprocess returned error exit status 1
>>
>> ProblemType: Package
>> DistroRelease: Ubuntu 25.04
>> Package: linux-modules-
>> ProcVersionSign
>> Uname: Linux 6.14.0-15-generic x86_64
>> NonfreeKernelMo
>> ApportVersion: 2.32.0-0ubuntu5
>> Architecture: amd64
>> AudioDevicesInUse:
>> USER PID ACCESS COMMAND
>> /dev/snd/controlC1: igor 2732 F.... wireplumber
>> /dev/snd/controlC0: igor 2732 F.... wireplumber
>> /dev/snd/seq: igor 2728 F.... pipewire
>> CasperMD5CheckR
>> Date: Sun Jun 22 10:04:44 2025
>> ErrorMessage: installed linux-modules-
>> package post-installation script subprocess returned error exit status 1
>> InstallationDate: Installed on 2025-06-20 (2 days ago)
>> InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64
>> (20250415.3)
>> MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT
>> ProcFB: 0 amdgpudrmfb
>> ProcKernelCmdLine: BOOT_IMAGE=
>> root=UUID=
>> crashkernel=
>> vt.handoff=7
>> Python3Details: /usr/bin/
>> 3.13.3-1
>> PythonDetails: N/A
>> RebootRequiredPkgs: Error: path contained symlinks.
>> RelatedPackageV
>> SourcePackage: linux-restricte
>> Title: package linux-modules-
>> failed to install/upgrade: installed
>> linux-modules-
| Daniel Letzeisen (dtl131) wrote : | #46 |
@Stefan: if you have the headers metapackage installed, the only thing I can think of is that the modules need a "PreDepends" on the corresponding headers to make sure the headers are installed/
| Eduardo Razera (erazera) wrote : | #47 |
@<email address hidden> @DanielLetzeisen @Stefan
I believe i have found a part time solution, if yall could please read what
i did and chck if there is a problem in doing that
So i booted into an older Kernel version using the advanced options for
Ubuntu (i used de .33 version)
nvidia-smi
Command 'nvidia-smi' not found, but can be installed with:
I checked and realized my nvidia drivers were missing, so i used this
command to auto install the recommended one based on my computer specs:
"sudo ubuntu-drivers autoinstall"
It installed, them i had to DISABLE secure boot to make it work, if it its
disabled i can run the latest kernel with no issues.
My doubt is, what I did was the correct solution? Is there a problem in
disabling secure boot ? I would be able to enable it again when Canonical
fix this issue ?
If yall have some time to answer me i would really appreciate it
Em qui., 27 de nov. de 2025 às 08:36, Daniel Letzeisen <
<email address hidden>> escreveu:
> @Stefan: if you have the headers metapackage installed, the only thing I
> can think of is that the modules need a "PreDepends" on the
> corresponding headers to make sure the headers are installed/
> first.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2130786).
> https:/
>
> Title:
> nvidia driver error: cannot open linker script file
>
> Status in linux-restricte
> Confirmed
> Status in linux-restricte
> Confirmed
>
> Bug description:
>
> -------
> *** If you've come here from a duplicate bug ***
>
> Please make sure you have the headers relevant to your kernel installed
> For most people,
> sudo apt install linux-headers-
>
> -------
>
>
> package linux-modules-
> to install/upgrade: installed linux-modules-
> package post-installation script subprocess returned error exit status 1
>
> ProblemType: Package
> DistroRelease: Ubuntu 25.04
> Package: linux-modules-
> ProcVersionSign
> Uname: Linux 6.14.0-15-generic x86_64
> NonfreeKernelMo
> ApportVersion: 2.32.0-0ubuntu5
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC1: igor 2732 F.... wireplumber
> /dev/snd/controlC0: igor 2732 F.... wireplumber
> /dev/snd/seq: igor 2728 F.... pipewire
> CasperMD5CheckR
> Date: Sun Jun 22 10:04:44 2025
> ErrorMessage: installed linux-modules-
> package post-installation script subprocess returned error exit status 1
> InstallationDate: Installed on 2025-06-20 (2 days ago)
> InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64
> (20250415.3)
> MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT
> ProcF...
| Daniel Letzeisen (dtl131) wrote : | #48 |
@Eduardo: you can always self-sign the Nvidia modules if you want to keep SecureBoot enabled - https:/
I guess you worked around bug 2131230 that you reported?
| Eduardo Razera (erazera) wrote : | #49 |
Honestly i'm not sure, i've had quite a few bugs but doing what i said
above seem to have made me able to run things smoothly again
Really appreciate the help from you guys! I'll check out the link you sent
Em qui., 27 de nov. de 2025 às 12:01, Daniel Letzeisen <
<email address hidden>> escreveu:
> @Eduardo: you can always self-sign the Nvidia modules if you want to
> keep SecureBoot enabled -
> https:/
> automated_
> done automatically when you install the Nvdida dkms driver)
>
> I guess you worked around bug 2131230 that you reported?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2130786).
> https:/
>
> Title:
> nvidia driver error: cannot open linker script file
>
> Status in linux-restricte
> Confirmed
> Status in linux-restricte
> Confirmed
>
> Bug description:
>
> -------
> *** If you've come here from a duplicate bug ***
>
> Please make sure you have the headers relevant to your kernel installed
> For most people,
> sudo apt install linux-headers-
>
> -------
>
>
> package linux-modules-
> to install/upgrade: installed linux-modules-
> package post-installation script subprocess returned error exit status 1
>
> ProblemType: Package
> DistroRelease: Ubuntu 25.04
> Package: linux-modules-
> ProcVersionSign
> Uname: Linux 6.14.0-15-generic x86_64
> NonfreeKernelMo
> ApportVersion: 2.32.0-0ubuntu5
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC1: igor 2732 F.... wireplumber
> /dev/snd/controlC0: igor 2732 F.... wireplumber
> /dev/snd/seq: igor 2728 F.... pipewire
> CasperMD5CheckR
> Date: Sun Jun 22 10:04:44 2025
> ErrorMessage: installed linux-modules-
> package post-installation script subprocess returned error exit status 1
> InstallationDate: Installed on 2025-06-20 (2 days ago)
> InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64
> (20250415.3)
> MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT
> ProcFB: 0 amdgpudrmfb
> ProcKernelCmdLine: BOOT_IMAGE=
> root=UUID=
> crashkernel=
> vt.handoff=7
> Python3Details: /usr/bin/
> 3.13.3-1
> PythonDetails: N/A
> RebootRequiredPkgs: Error: path contained symlinks.
> RelatedPackageV
> SourcePackage: linux-restricte
> Title: package linux-modules-

Status changed to 'Confirmed' because the bug affects multiple users.