Newly installed 20.04 cannot install new packages, 'apt --fix-broken install' does not solve the problem

Bug #1876043 reported by Daniel Jarosik on 2020-04-30
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned

Bug Description

$ sudo apt --fix-broken install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  linux-modules-extra-5.4.0-28-generic
The following NEW packages will be installed:
  linux-modules-extra-5.4.0-28-generic
0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
7 not fully installed or removed.
Need to get 0 B/38,6 MB of archives.
After this operation, 190 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
(Reading database ... 190280 files and directories currently installed.)
Preparing to unpack .../linux-modules-extra-5.4.0-28-generic_5.4.0-28.32_amd64.deb ...
Unpacking linux-modules-extra-5.4.0-28-generic (5.4.0-28.32) ...
dpkg: error processing archive /var/cache/apt/archives/linux-modules-extra-5.4.0-28-generic_5.4.0-28.32_amd64.deb (--unpack):
 unable to open '/lib/modules/5.4.0-28-generic/kernel/drivers/media/usb/stkwebcam/stkwebcam.ko.dpkg-new': Operation not permitted
Errors were encountered while processing:
 /var/cache/apt/archives/linux-modules-extra-5.4.0-28-generic_5.4.0-28.32_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Apr 30 08:51:28 2020
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity
InstallationDate: Installed on 2020-04-27 (2 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: ubiquity
Symptom: installation
UpgradeStatus: No upgrade log present (probably fresh install)

Daniel Jarosik (daniel-jarosik) wrote :
affects: ubuntu → ubiquity (Ubuntu)
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, could you add your 'journalctl -b 0' after getting the issue?

affects: ubiquity (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
Daniel Jarosik (daniel-jarosik) wrote :

journalctl -b 0 in the attached file (journalctl.result)

Daniel Jarosik (daniel-jarosik) wrote :

alfter (yet another) reboot, apt --fix-broken install executed successfully

sudo apt --fix-broken install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  amd64-microcode intel-microcode iucode-tool linux-headers-5.4.0-28 linux-headers-5.4.0-28-generic linux-headers-generic-hwe-20.04 linux-image-5.4.0-28-generic linux-modules-5.4.0-28-generic thermald
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  linux-generic-hwe-20.04 linux-image-generic-hwe-20.04 linux-modules-extra-5.4.0-28-generic
0 upgraded, 0 newly installed, 3 to remove and 2 not upgraded.
8 not fully installed or removed.
After this operation, 34,8 kB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 190280 files and directories currently installed.)
Removing linux-generic-hwe-20.04 (5.4.0.28.33) ...
Removing linux-image-generic-hwe-20.04 (5.4.0.28.33) ...
Removing linux-modules-extra-5.4.0-28-generic (5.4.0-28.32) ...
Setting up linux-headers-5.4.0-28 (5.4.0-28.32) ...
Setting up linux-modules-5.4.0-28-generic (5.4.0-28.32) ...
Setting up linux-image-5.4.0-28-generic (5.4.0-28.32) ...
I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.4.0-26-generic
I: /boot/vmlinuz is now a symlink to vmlinuz-5.4.0-28-generic
I: /boot/initrd.img is now a symlink to initrd.img-5.4.0-28-generic
Setting up linux-headers-5.4.0-28-generic (5.4.0-28.32) ...
Setting up linux-headers-generic-hwe-20.04 (5.4.0.28.33) ...
Processing triggers for linux-image-5.4.0-28-generic (5.4.0-28.32) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.0-28-generic
I: The initramfs will attempt to resume from /dev/sdb1
I: (UUID=a9076284-caa9-465a-8bdf-349d877e135f)
I: Set the RESUME variable to override this.
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.4.0-28-generic
Found initrd image: /boot/initrd.img-5.4.0-28-generic
Found linux image: /boot/vmlinuz-5.4.0-26-generic
Found initrd image: /boot/initrd.img-5.4.0-26-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
Found Windows 10 on /dev/sda1
Found Ubuntu 19.10 (19.10) on /dev/sda5
done

Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers