[Bug 1856492] Re: linux-generic-hwe-18.04=5.3.0.25.94 in bionic-proposed causes a conflict with virtualbox-guest-x11-hwe
@Sultan Alsawaf Thanks for the feedback, but it must be a dependency problem for the following reasons: 1.) If I had a signed kernel, I could see it when I query the list of installed packages with dpkg -l 2.) It worked until mid-December when Kernel 5.0.0 was available (Kernel 5.3.0 was only in bionic-proposed at that time) Kernel 5.0.0: = root@ubuntu:~# dpkg -l | grep linux-image ii linux-image-5.0.0-31-generic 5.0.0-31.33~18.04.1 i386 Linux kernel image for version 5.0.0 on 32 bit x86 SMP ii linux-image-generic-hwe-18.04 5.0.0.31.88 i386 Generic Linux kernel image apt-get install virtualbox virtualbox-guest-x11-hwe virtualbox-ext-pack (no problems) Kernel 5.3.0: = root@ubuntu:~# dpkg --list | grep linux-image ii linux-image-5.3.0-42-generic 5.3.0-42.34~18.04.1 i386 Linux kernel image for version 5.3.0 on 32 bit x86 SMP ii linux-image-generic-hwe-18.04 5.3.0.42.99 i386 Generic Linux kernel image apt-get install virtualbox virtualbox-guest-x11-hwe virtualbox-ext-pack (kernel gets removed) Someone screwed it up when creating the new packages and nobody is fixing it... as usual... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856492 Title: linux-generic-hwe-18.04=5.3.0.25.94 in bionic-proposed causes a conflict with virtualbox-guest-x11-hwe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1856492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866518] [NEW] Conflict between linux-generic-hwe-18.04 and virtualbox-guest-x11-hwe (arch i386)
Public bug reported: How to reproduce this bug? -- 1.) create a minimal ubuntu with debootstrap (arch i386) 2.) use this sources.list: deb http://de.archive.ubuntu.com/ubuntu bionic main restricted universe multiverse deb http://de.archive.ubuntu.com/ubuntu bionic-security main restricted universe multiverse deb http://de.archive.ubuntu.com/ubuntu bionic-updates main restricted universe multiverse deb http://de.archive.ubuntu.com/ubuntu bionic-proposed main restricted universe multiverse deb http://de.archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse deb http://archive.canonical.com/ubuntu bionic partner 3.) update package lists apt-get update 4.) install kernel 5.3.0 apt-get install linux-generic-hwe-18.04 5.) install virtualbox apt-get install virtualbox virtualbox-guest-x11-hwe virtualbox-ext-pack --- actual result: linux-generic-hwe-18.04 is being removed due to invalid dependencies expected result: linux-generic-hwe-18.04 keeps installed ** Affects: virtualbox-hwe (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866518 Title: Conflict between linux-generic-hwe-18.04 and virtualbox-guest-x11-hwe (arch i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox-hwe/+bug/1866518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787460] Re: Unattended upgrades removed linux-image-generic
Hi, this bug still exists! It is IMPOSSIBLE to install linux-generic- hwe-18.04 and virtualbox virtualbox-guest-x11-hwe virtualbox-ext-pack at the same time. (arch i386) I already reported this problem month ago here: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1856492 Seems like nobody cares! This is just pure shit! Some idiots think they have to release kernel 5.3, but they don't consider that nothing will work afterwards. What is even more stupid is that Kernel 5.0 is no longer available! idiots! idiots! idiots! Damn, fix that! How to reproduce this bug? -- 1.) create a minimal ubuntu with debootstrap 2.) use this sources.list: deb http://de.archive.ubuntu.com/ubuntu bionic main restricted universe multiverse deb http://de.archive.ubuntu.com/ubuntu bionic-security main restricted universe multiverse deb http://de.archive.ubuntu.com/ubuntu bionic-updates main restricted universe multiverse deb http://de.archive.ubuntu.com/ubuntu bionic-proposed main restricted universe multiverse deb http://de.archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse deb http://archive.canonical.com/ubuntu bionic partner 3.) update package lists apt-get update 4.) install kernel 5.3.0 from bionic-proposed apt-get install linux-generic-hwe-18.04 5.) install virtualbox apt-get install virtualbox virtualbox-guest-x11-hwe virtualbox-ext-pack --- actual result: linux-generic-hwe-18.04 is being removed due to invalid dependencies expected result: linux-generic-hwe-18.04 keeps installed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787460 Title: Unattended upgrades removed linux-image-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1787460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856492] [NEW] linux-generic-hwe-18.04=5.3.0.25.94 in bionic-proposed causes a conflict with virtualbox-guest-x11-hwe
Public bug reported: How to reproduce this bug? -- 1.) create a minimal ubuntu with debootstrap 2.) use this sources.list: deb http://de.archive.ubuntu.com/ubuntu bionic main restricted universe multiverse deb http://de.archive.ubuntu.com/ubuntu bionic-security main restricted universe multiverse deb http://de.archive.ubuntu.com/ubuntu bionic-updates main restricted universe multiverse deb http://de.archive.ubuntu.com/ubuntu bionic-proposed main restricted universe multiverse deb http://de.archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse deb http://archive.canonical.com/ubuntu bionic partner 3.) update package lists apt-get update 4.) install kernel 5.3.0 from bionic-proposed apt-get install linux-generic-hwe-18.04 5.) install virtualbox apt-get install virtualbox virtualbox-guest-x11-hwe virtualbox-ext-pack --- actual result: linux-generic-hwe-18.04 is being removed due to invalid dependencies expected result: linux-generic-hwe-18.04 keeps installed ** Affects: linux-meta-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: conflict linux-image virtualbox -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856492 Title: linux-generic-hwe-18.04=5.3.0.25.94 in bionic-proposed causes a conflict with virtualbox-guest-x11-hwe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1856492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848940] Re: gnome-control-center does not respect symbolic links
In short: Symbolic links are absolutely necessary to exclude files from overlayfs. Long explanation: I use overlayfs to protect my system's root file system. With overlayfs all changes are only in RAM. So any change is only temporary. I want some changes to be persistent. To do that I copy these files to another partition and create a link. For example I want that my system remembers any network connection so I move /etc/NetworkManager/system- connections/ to another partition and create a link to it. The same applies to the home directory or /var/lib/AccountsService/users/. This will exclude these files from overlayfs. This gives me a superfast system that allows me to do almost any experiment. If something goes wrong I just restart it and it's the same as before. Even more, it's almost impossible to infect this system with malware. It also use full disk encryption (including /boot) and runs from usb. It is a highly secure system... I'm pretty sure there are many more use cases that require symbolic links for config files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848940 Title: gnome-control-center does not respect symbolic links To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1848940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848940] [NEW] gnome-control-center does not respect symbolic links
Public bug reported: Configuration files created as symbolic links are overwritten by gnome- control-center. This probably affects any configuration file managed by gnome-control-center. Test case: -- 1.) Create symbolic links of the following files sudo mv /etc/default/locale /etc/default/locale.test && sudo ln -s /etc/default/locale.test /etc/default/locale sudo mv /etc/default/keyboard /etc/default/keyboard.test && sudo ln -s /etc/default/keyboard.test /etc/default/keyboard sudo mv /etc/hostname /etc/hostname.test && sudo ln -s /etc/hostname.test /etc/hostname 2.) Change the language, the keyboard layout and the hostname in gnome- control-center. Expected result: The link destination should be overwritten so that the symbolic link is preserved. Actual result: The symbolic link itself is overwritten so that the symbolic link is lost. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: link overwritten symbolic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848940 Title: gnome-control-center does not respect symbolic links To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1848940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621367] Re: 4.4.0-36: keyboard dead at boot & full disk encryption prompt for password
A purely speculative assumption: For some reason, Logitech hardware can immediately go into autosuspend mode. To prevent this, you can add the following kernel command line parameter: usbcore.autosuspend=-1 In addition, you should execute the following commands: tee --append /etc/modprobe.d/usbcore.conf << EOF options usbcore autosuspend=-1 EOF update-initramfs -u -k all Note: It depends on the kernel from where the configuration is read, so it is best to add both the parameter and the config file. It may also be helpful to use a different USB port. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621367 Title: 4.4.0-36: keyboard dead at boot & full disk encryption prompt for password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1621367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842382] Re: /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 & bionic 18.04 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate dailies)
I can confirm that vlc starts on a system where the root filesystem uses obverlayfs + Kernel 5.0.0-31-generic (testet with Ubuntu 18.04, apt-get install linux-generic-hwe-18.04). @Rik I accidentally clicked on the fix committed link, I did not know that anyone can change the status without further confirmation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842382 Title: /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 & bionic 18.04 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate dailies) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842382] Re: /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 & bionic 18.04 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate dailies)
** Changed in: linux (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842382 Title: /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 & bionic 18.04 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate dailies) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843503] Re: PCSX-R in Ubuntu 18.04 cannot configure controllers when more then 1 gamepad is connected
I can confirm that this bug exists -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843503 Title: PCSX-R in Ubuntu 18.04 cannot configure controllers when more then 1 gamepad is connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1843503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842382] Re: /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate daily)
The reason why vlc does not start is definitely the overlay filesystem. How can I know that? I use Ubuntu on a fully encrypted USB stick with overlay root filesystem (which makes the USB super fast, even faster than ssd). To enable the overlay root filesystem I use the following initramfs script: https://gist.github.com/niun/34c945d70753fc9e2cc7 (FYI: the script has a little bug, it can not handle tabulators in fstab, you have to fix that if you want use it for testing, just insert tr "\t" ' ' before grep -v ' / ') You can disable this script with the kernel command line parameter disable-root-to=yes. I tested, once with overlay fs and once without overlay fs. vlc starts as long as you do not use overlay fs. But it does not start with enabled overlay fs. Therefore, the reason must be the overlay filesystem. It can be assumed that thus bug affects all systems that use overlay fs. Not only debian but all distributions. Therefore, I would give this bug a high priority. In addition, my strace looks a bit different than the strace that has been posted here (see attachment). Last 5 lines: mmap2(NULL, 26374, PROT_READ, MAP_SHARED, 3, 0) = 0xb7f94000 close(3)= 0 futex(0xb7f2bfe4, FUTEX_WAKE_PRIVATE, 2147483647) = 0 exit_group(1) = ? +++ exited with 1 +++ I suspect the futex () call fails. The bug probably has nothing to do with /proc/self/maps. ** Attachment added: "strace vlc" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842382/+attachment/5288850/+files/vlc_strace.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842382 Title: /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate daily) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843181] [NEW] cryptsetup-reencrypt may use an incorrect hash if the hash parameter is omitted
Public bug reported: Let's say: - someone setup a fully encrypted bootable ubuntu system - the /boot directory resists in the encrypted root filesystem so that it is also encrypted - the parameters --cipher=aes-xts-plain64 and --hash=sha512 have been passed to cryptsetup luksFormat - everything was configured correctly so that GRUB is able to boot the encrypted system - everything works fine, when you turn on the computer you will be prompted to unlock the encrypted system Let's get to the problem: - for some reason someone want to re-encrypt the entire system which is easily possible with cryptsetup-reencrypt - this is done with the following command: cryptsetup-reencrypt /dev/sda3 --key-file=secret.key --key-slot 0 - the re-encryption process is successful - but the system is now no longer bootable because cryptsetup-reencrypt has used sha256 as hash and NOT sha512 which was used before The reason why the system is unbootable is: - the "early grub core image" which was created by grub-install does not contain an sha256 module, and because of that grub is no longer able to read the encrypted volume in stage 1 Conclusion: - if no cipher and/or hash was passed to cryptsetup-reencrypt then cryptsetup-reencrypt should take over the previous values of the encrypted volume and not use the default hash value which is sha256, only then the system will still be bootable Note: - I can confirm that the system is still bootable if the parameters --cipher=aes-xts-plain64 and --hash=sha512 are passed to cryptsetup- reencrypt explicitly I know: - grub-install could solve the issue but I think this is not the best solution and the behavior described here should be considered as a bug. A user expects everything to work without problems, and that everything is same like before (same cipher, same hash). Summery: cryptsetup-reencrypt should simply re-encrypt, it should not make any decisions regarding the hash or cipher since the consequences are not foreseeable. ** Affects: cryptsetup (Ubuntu) Importance: Undecided Status: New ** Tags: cryptsetup-reencrypt hash sha256 sha512 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843181 Title: cryptsetup-reencrypt may use an incorrect hash if the hash parameter is omitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1843181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837333] [NEW] friendly-recovery should depend on gettext-base
Public bug reported: If gettext-base is not installed, all recovery menu options are missing (due to "gettext.sh missing" errors in the recovery-menu script). Without menu items, friendly-recovery is completely useless. Therefore, friendly-recovery should depend on gettext-base instead of just recommending it. ** Affects: friendly-recovery (Ubuntu) Importance: Undecided Status: New ** Tags: friendly-recovery gettext-base gettext.sh missing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837333 Title: friendly-recovery should depend on gettext-base To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1837333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1247905] Re: update-grub fails in the face of overlayroot
Sorry, I forgot chmod +x /usr/sbin/grub-probe-overlay -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1247905 Title: update-grub fails in the face of overlayroot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1247905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1247905] Re: update-grub fails in the face of overlayroot
WORKING SOLUTION
After encountering this problem, I developed a very simple solution:
nano /usr/sbin/grub-probe-overlay
-[BEGIN]--
#!/bin/sh
ARGS=
for ARG in $@; do
if [ "${ARG%%[!/]*}" = "/" ]; then
OPTIONS=
if FSTYPE=$( findmnt -n -o FSTYPE "$ARG" ); then
if [ "$FSTYPE" = "overlay" ]; then
OPTIONS=$(findmnt -n -o OPTIONS "$ARG")
fi
elif FSTYPE=$( findmnt -n -o FSTYPE / ); then
if [ "$FSTYPE" = "overlay" ]; then
OPTIONS=$(findmnt -n -o OPTIONS /)
fi
fi
if LOWERDIR=$(echo "$OPTIONS" | grep -m 1 -oP
'lowerdir=\K[^,]+'); then
# echo "[DEBUG] Overlay filesystem detected \${ARG} -->
\${LOWERDIR}\${ARG%*/}" 1>&2
ARG="${LOWERDIR}${ARG%*/}"
fi
fi
ARGS="$ARGS $ARG"
done
grub-probe-default $ARGS
exit $?
-[END]
mv /usr/sbin/grub-probe /usr/sbin/grub-probe-default
ln -s /usr/sbin/grub-probe-overlay /usr/sbin/grub-probe
OPTIONAL STEP:
==
apt-mark hold grub-pc
NOTE: package name can also be "grub-efi-amd64" or "grub-efi-ia32" or
something else, depending on what you use
PROS
- works perfectly with overlay filesystem
- shows a general solution (maybe someone can use it to fix the grub-probe
source code)
- no patching of grub scripts required (some people tried patches as solution,
but grub-probe is used in many grub scripts --> patching nightmare)
CONS
- grub-probe must be renamed (for this reason, I recommend that you set the
status of your grub package to "hold")
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1247905
Title:
update-grub fails in the face of overlayroot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1247905/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
