Thank you Chris. Having first checked my backup, your post gave me the
confidence to start the upgrade. It was a complete nightmare. I thought
my system was completely borked. The upgrade (using do-release-upgrade)
froze part way through, immediately after reporting the following to the
console:
I currently have several installs with encrypted homes. Today I was
going to upgrade the first of them, in this case, from 17.10 to 18.04.
Having one last scan of the release notes before upgrading, I spotted
this issue
I'd like to add another use case requiring non-full disk encryption.
Machines that need to be powered on and off remotely, which is currently
done using a wake-on-lan. The machines are not full-disk encrypted, but
make use of encrypted homes and certain encrypted disks/partitions that
can be
Thank you Dimitri. The dropbear initramfs technique looks interesting.
It ought to provide a solution for my use case... I'll give it a go.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756840
I'm on "Ubuntu 19.04" (disco), with initramfs-rools at version
0.131ubuntu19, and this is still broken for me.
lvdisplay gives /dev/xubuntu-vg/swap_1 as the swap logical volume path
and dzVm4y-Xeh5-o9UB-jLnI-0ldX-azSN-9w6QZq as the UUIS.
I've tried separately with
This looks likely to be some kind of incompatibility with full-disk
encrypted systems. I just spotted that the errors I am getting are not
about the swap partition at all, but instead about /dev/mapper/xubuntu
--vg-root, which is the encrypted root. From /etc/fstab:
/dev/mapper/xubuntu--vg-root /
In case these are in any way relevant (I have no idea):
- I have secure boot enabled.
- Prior to encountering this issue, I had recently installed the
nvidia-driver-435 package.
On another computer, also running a fresh Ubuntu 19.10 server install
with gnome-session on top, with secure boot
For info, when I run "sudo apt --fix-broken install" it sometimes fails
with a segmentation fault. Also, it seems to report "Operation not
permitted" errors on a different drivers each time I run it. It's not
repeatable.
Is there a way that I can uninstall the 5.3.0-24 kernel (apt purge
doesn't
Yes! I can't thank you enough. Sophos AV was the culprit. The following
was able to get my system fully updated again:
sudo systemctl stop sav-protect.service
sudo apt --fix-broken install
sudo apt update
sudo apt full-upgrade
sudo apt autoremove
sudo systemctl start sav-protect.service
I'll
My system was installed using the LVM with full-disk encryption option
of the alternative installer, and uses the default ext4 filesystem, so
the filesystem doesn't appear to the problem.
I previously reported that I didn't have the problem on a system with a
very similar software setup, but
*** This bug is a duplicate of bug 1685984 ***
https://bugs.launchpad.net/bugs/1685984
** This bug has been marked a duplicate of bug 1685984
packages (multiple) failed to install/upgrade: unable to open
'x.dpkg-new': Operation not permitted
--
You received this bug notification
Public bug reported:
I've got this issue on a fresh (last week) Ubuntu-server 19.10 install,
with gnome-session installed on top.
>From history.log:
Start-Date: 2019-12-04 06:24:37
Commandline: /usr/bin/unattended-upgrade
Install: linux-image-5.3.0-24-generic:amd64 (5.3.0-24.26, automatic),
See this duplicate: https://bugs.launchpad.net/ubuntu/+source/update-
manager/+bug/1855259/comments/11. This is likely a bug in fanotify or
Sophos, not dpkg.
It would be useful to know whether the original poster
(https://launchpad.net/~jsamuel-s) was using Sophos AV or fanotify at
the time.
--
*** This bug is a duplicate of bug 1685984 ***
https://bugs.launchpad.net/bugs/1685984
Paulo, please note:
a) Repairing a system using the steps in comment #9 doesn't address the
underlying problem, and so it could potentially break again.
b) Sophos doesn't support newer kernels and Ubuntu
14 matches
Mail list logo
