[Bug 1876043] Re: Newly installed 20.04 cannot install new packages, 'apt --fix-broken install' does not solve the problem

2020-06-29 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876043

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876043/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1876043] Re: Newly installed 20.04 cannot install new packages, 'apt --fix-broken install' does not solve the problem

2020-04-30 Thread Daniel Jarosik
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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876043

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876043/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1876043] Re: Newly installed 20.04 cannot install new packages, 'apt --fix-broken install' does not solve the problem

2020-04-30 Thread Daniel Jarosik
journalctl -b 0 in the attached file (journalctl.result)

** Attachment added: "journalctl.result"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876043/+attachment/5363939/+files/journalctl.result

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876043

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876043/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1876043] Re: Newly installed 20.04 cannot install new packages, 'apt --fix-broken install' does not solve the problem

2020-04-30 Thread Sebastien Bacher
Thank you for your bug report, could you add your 'journalctl -b 0'
after getting the issue?

** Package changed: ubiquity (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876043

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876043/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1876043] Re: Newly installed 20.04 cannot install new packages, 'apt --fix-broken install' does not solve the problem

2020-04-30 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => ubiquity (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876043

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1876043/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs