package linux-firmware 20220302.gitee0667aa-0ubuntu1 failed to install/upgrade: impossibile aprire "/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new": File o directory non esistente
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-firmware (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Ubuntu 21.10 "Impish Indri" -Realease amd64 (202111012)
NonfreeKernelMo
nividia_modeset nividia
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-firmware 20220302.
ProcVersionSign
Uname: Linux 5.15.0-22-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu79
AptOrdering:
linux-
NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CasperMD5CheckR
Date: Tue Mar 15 11:35:42 2022
Dependencies: firmware-sof-signed 2.0-1ubuntu2
ErrorMessage: impossibile aprire "/lib/firmware/
InstallationDate: Installed on 2022-02-10 (32 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: TOSHIBA SATELLITE L50-A
PackageArchitec
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/
PythonDetails: N/A
RelatedPackageV
SourcePackage: linux-firmware
Title: package linux-firmware 20220302.
UpgradeStatus: Upgraded to jammy on 2022-02-10 (32 days ago)
dmi.bios.date: 09/19/2014
dmi.bios.release: 1.90
dmi.bios.vendor: TOSHIBA
dmi.bios.version: 1.90
dmi.board.
dmi.board.name: VG10S
dmi.board.vendor: TOSHIBA
dmi.board.version: To be filled by O.E.M.
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.
dmi.ec.
dmi.modalias: dmi:bvnTOSHIBA:
dmi.product.family: PEGA Family
dmi.product.name: SATELLITE L50-A
dmi.product.sku: PSKK6E
dmi.product.
dmi.sys.vendor: TOSHIBA
Thank you for taking the time to report this bug and helping to make Ubuntu better.
This particular bug has already been reported and is a duplicate of bug 1964814, so it is being marked as such. This issue is in the process of being fixed (an updated package is currently in -proposed).
Feel free to continue to report any other bugs you may find.