Re: [Touch-packages] [Bug 1990064] Re: unconfined profile denies userns_create for chromium based processes
> Previously we only had the option of using a system wide sysctl > kernel.unprivileged_userns_clone to disable unprivileged user > namespaces. Debian defaults this to off, and you have to opt in. Just to avoid misunderstandings (I failed to parse the above sentence unambiguously): in Debian, unprivileged user namespaces have been enabled by default since Bullseye. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1990064 Title: unconfined profile denies userns_create for chromium based processes Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: For Ubuntu 22.10, since the last kernel update, i can´t launch any chromium based browser, due to apparmor denying userns_create dmesg shows: apparmor="DENIED" operation="userns_create" class="namespace" info="User namespace creation restricted" error=-13 profile="unconfined" pid=21323 comm="steamwebhelper" requested="userns_create" denied="userns_create" This happens for every process which uses a chromium engine, like google chrome itself or in this case steamwebhelper. Might be related to this change?: https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/ not sure if it got merged in this form though.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990379] Re: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used
** Package changed: linux (Ubuntu) => zlib (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: ubuntu-z-systems Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1990379 Title: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used Status in Ubuntu on IBM z Systems: New Status in zlib package in Ubuntu: New Bug description: == Comment: #0 - Ilya Leoshkevich - 2022-09-21 05:02:24 == inflate() does not update strm.adler if DFLTCC is used. Found with a JDK test. zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349 Updated zlib PR: https://github.com/madler/zlib/pull/410 zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920 zlib diff: https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620 Ubuntu 20.04 and later need to be fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990379] [NEW] [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used
You have been subscribed to a public bug: == Comment: #0 - Ilya Leoshkevich - 2022-09-21 05:02:24 == inflate() does not update strm.adler if DFLTCC is used. Found with a JDK test. zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349 Updated zlib PR: https://github.com/madler/zlib/pull/410 zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920 zlib diff: https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620 Ubuntu 20.04 and later need to be fixed. ** Affects: zlib (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s3903164 bugnameltc-200024 severity-medium targetmilestone-inin2004 -- [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used https://bugs.launchpad.net/bugs/1990379 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Hi Julian,
I didn't see the 'boot failures on older system' from comment#90.
Would you please point it out more specifically?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Confirmed
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c” but I use the
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
Thus it should not impact them.
* There is a “#if defined(__x86_64__)” which intent to limit the >
32bits code in i386 system and also
```
#if defined (__code_model_large__)
-#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
+#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
#else
#define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
#endif
```
If everything works as expected, then i386 should working good.
If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
4GB memory region and never be able to access.
[Other Info]
* Upstream grub2 bug #61058
https://savannah.gnu.org/bugs/index.php?61058
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320
* Test grubx64.efi:
https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320
* Test source code: https://github.com/os369510/grub2/tree/lp1842320
* If you built the package, then test grubx64.efi is under
“obj/monolithic/grub-efi-amd64/grubx64.efi”, in my case:
[Touch-packages] [Bug 1990064] Re: unconfined profile denies userns_create for chromium based processes
In short unprivileged user namespaces a vector for exploit chains, as they expose interfaces that otherwise would not be available. 4 out 5 exploits chains in pwn2own 2022 used unprivileged user namespaces. They were also used in 2021, 2020, ... Yes the actual vulnerabilities were in other interface io_uring, ebpf, nftables, ... but none of them would have been available without unprivileged user namespaces. Previously we only had the option of using a system wide sysctl kernel.unprivileged_userns_clone to disable unprivileged user namespaces. Debian defaults this to off, and you have to opt in. Ubuntu is now moving towards a more fine grained approach where they can be selectively turned on for some applications but aren't generally available. For 22.10 the apparmor sysctl will be defaulted to off, while further packaging work is done for applications that need access to unprivileged user namespaces. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1990064 Title: unconfined profile denies userns_create for chromium based processes Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: For Ubuntu 22.10, since the last kernel update, i can´t launch any chromium based browser, due to apparmor denying userns_create dmesg shows: apparmor="DENIED" operation="userns_create" class="namespace" info="User namespace creation restricted" error=-13 profile="unconfined" pid=21323 comm="steamwebhelper" requested="userns_create" denied="userns_create" This happens for every process which uses a chromium engine, like google chrome itself or in this case steamwebhelper. Might be related to this change?: https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/ not sure if it got merged in this form though.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990586] Re: 22.04: python3* mismatched phasing breaks dist-upgrades
** Attachment added: "lp1990586.edsp" https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1990586/+attachment/5618167/+files/lp1990586.edsp -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1990586 Title: 22.04: python3* mismatched phasing breaks dist-upgrades Status in apt package in Ubuntu: Incomplete Status in python3-defaults package in Ubuntu: Fix Released Status in python3-stdlib-extensions package in Ubuntu: Fix Released Status in python3.10 package in Ubuntu: Fix Released Bug description: Impact -- Users who manually run sudo apt dist-upgrade without paying attention can remove essential parts of their system Test Case - This test case won't work as well if phasing is set to 0% or 100% Create /etc/apt/apt.conf.d/phasing and set its contents to APT::Machine-ID 2c030cfce3b4487f9810f12a3ac6e87c; Then run sudo apt update sudo apt dist-upgrade Workaround In Advance - Don't run sudo apt dist-upgrade. Just run sudo apt upgrade Or use Update Manager or the Ubuntu Store to apply updates Workaround Afterwards - Fortunately, apt phasing is ignored for new package installs. So to get your Ubuntu Desktop back, just run sudo apt install ubuntu-desktop Other Info -- These 3 updates were published today: python3-stdlib-extensions python3-defaults python3.10 Suggested Fix - Fully phase those 3 source packages to 100% Apt Output -- The following packages were automatically installed and are no longer required: apg apport-symptoms aptdaemon-data avahi-utils cups-pk-helper distro-info gdb gedit-common genisoimage gir1.2-dbusmenu-glib-0.4 gir1.2-dee-1.0 gir1.2-goa-1.0 gir1.2-gst-plugins-base-1.0 gir1.2-gtksource-4 gir1.2-gudev-1.0 gir1.2-notify-0.7 gir1.2-packagekitglib-1.0 gir1.2-rb-3.0 gir1.2-secret-1 gir1.2-snapd-1 gir1.2-totem-1.0 gir1.2-totemplparser-1.0 gir1.2-udisks-2.0 gir1.2-unity-7.0 gir1.2-vte-2.91 gir1.2-wnck-3.0 gnome-control-center-faces gnome-software-common gnome-terminal-data hplip-data ibus-data ibus-gtk4 libbabeltrace1 libboost-regex1.74.0 libc6-dbg libcolord-gtk1 libdebuginfod-common libdebuginfod1 libdmapsharing-3.0-2 libglu1-mesa libgpod-common libgpod4 libgsound0 libgssdp-1.2-0 libgupnp-1.2-1 libgupnp-av-1.0-3 libgupnp-dlna-2.0-4 libhpmud0 libimagequant0 libipt2 liblirc-client0 libmalcontent-0-0 libnetplan0 libraqm0 librsync2 librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 libsane-hpaio libsgutils2-2 libsource-highlight-common libsource-highlight4v5 libwhoopsie-preferences0 libwnck-3-0 libwnck-3-common libxatracker2 libxres1 libxss1 libxvmc1 mobile-broadband-provider-info network-manager-gnome patch printer-driver-hpcups printer-driver-postscript-hp python-apt-common python3-blinker python3-certifi python3-cffi-backend python3-chardet python3-click python3-colorama python3-cryptography python3-dateutil python3-debconf python3-debian python3-defer python3-distro-info python3-fasteners python3-future python3-httplib2 python3-idna python3-importlib-metadata python3-jeepney python3-jwt python3-keyring python3-launchpadlib python3-lazr.restfulclient python3-lazr.uri python3-lockfile python3-louis python3-monotonic python3-more-itertools python3-oauthlib python3-olefile python3-pexpect python3-pkg-resources python3-problem-report python3-ptyprocess python3-pyparsing python3-requests python3-rfc3339 python3-secretstorage python3-six python3-tz python3-urllib3 python3-wadllib python3-xkit python3-zipp rygel whoopsie-preferences x11-apps x11-session-utils xbitmaps xbrlapi xcvt xfonts-scalable xinit xinput xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-input-wacom xserver-xorg-video-all xserver-xorg-video-amdgpu xserver-xorg-video-ati xserver-xorg-video-fbdev xserver-xorg-video-intel xserver-xorg-video-nouveau xserver-xorg-video-qxl xserver-xorg-video-radeon xserver-xorg-video-vesa xserver-xorg-video-vmware Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: apport apport-gtk aptdaemon apturl apturl-common command-not-found deja-dup duplicity gedit gnome-control-center gnome-online-accounts gnome-software gnome-software-plugin-snap gnome-terminal hplip ibus ibus-table language-selector-common language-selector-gnome nautilus-extension-gnome-terminal nautilus-share netplan.io networkd-dispatcher orca python3-apport python3-apt python3-aptdaemon python3-aptdaemon.gtk3widgets python3-bcrypt python3-brlapi python3-cairo python3-commandnotfound python3-cups python3-cupshelpers python3-dbus python3-distupgrade python3-gi python3-gi-cairo python3-ibus-1.0 python3-macaroonbakery python3-mako python3-markupsafe
[Touch-packages] [Bug 1990586] Re: 22.04: python3* mismatched phasing breaks dist-upgrades
I attached the edsp file. Hope it helps. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1990586 Title: 22.04: python3* mismatched phasing breaks dist-upgrades Status in apt package in Ubuntu: Incomplete Status in python3-defaults package in Ubuntu: Fix Released Status in python3-stdlib-extensions package in Ubuntu: Fix Released Status in python3.10 package in Ubuntu: Fix Released Bug description: Impact -- Users who manually run sudo apt dist-upgrade without paying attention can remove essential parts of their system Test Case - This test case won't work as well if phasing is set to 0% or 100% Create /etc/apt/apt.conf.d/phasing and set its contents to APT::Machine-ID 2c030cfce3b4487f9810f12a3ac6e87c; Then run sudo apt update sudo apt dist-upgrade Workaround In Advance - Don't run sudo apt dist-upgrade. Just run sudo apt upgrade Or use Update Manager or the Ubuntu Store to apply updates Workaround Afterwards - Fortunately, apt phasing is ignored for new package installs. So to get your Ubuntu Desktop back, just run sudo apt install ubuntu-desktop Other Info -- These 3 updates were published today: python3-stdlib-extensions python3-defaults python3.10 Suggested Fix - Fully phase those 3 source packages to 100% Apt Output -- The following packages were automatically installed and are no longer required: apg apport-symptoms aptdaemon-data avahi-utils cups-pk-helper distro-info gdb gedit-common genisoimage gir1.2-dbusmenu-glib-0.4 gir1.2-dee-1.0 gir1.2-goa-1.0 gir1.2-gst-plugins-base-1.0 gir1.2-gtksource-4 gir1.2-gudev-1.0 gir1.2-notify-0.7 gir1.2-packagekitglib-1.0 gir1.2-rb-3.0 gir1.2-secret-1 gir1.2-snapd-1 gir1.2-totem-1.0 gir1.2-totemplparser-1.0 gir1.2-udisks-2.0 gir1.2-unity-7.0 gir1.2-vte-2.91 gir1.2-wnck-3.0 gnome-control-center-faces gnome-software-common gnome-terminal-data hplip-data ibus-data ibus-gtk4 libbabeltrace1 libboost-regex1.74.0 libc6-dbg libcolord-gtk1 libdebuginfod-common libdebuginfod1 libdmapsharing-3.0-2 libglu1-mesa libgpod-common libgpod4 libgsound0 libgssdp-1.2-0 libgupnp-1.2-1 libgupnp-av-1.0-3 libgupnp-dlna-2.0-4 libhpmud0 libimagequant0 libipt2 liblirc-client0 libmalcontent-0-0 libnetplan0 libraqm0 librsync2 librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 libsane-hpaio libsgutils2-2 libsource-highlight-common libsource-highlight4v5 libwhoopsie-preferences0 libwnck-3-0 libwnck-3-common libxatracker2 libxres1 libxss1 libxvmc1 mobile-broadband-provider-info network-manager-gnome patch printer-driver-hpcups printer-driver-postscript-hp python-apt-common python3-blinker python3-certifi python3-cffi-backend python3-chardet python3-click python3-colorama python3-cryptography python3-dateutil python3-debconf python3-debian python3-defer python3-distro-info python3-fasteners python3-future python3-httplib2 python3-idna python3-importlib-metadata python3-jeepney python3-jwt python3-keyring python3-launchpadlib python3-lazr.restfulclient python3-lazr.uri python3-lockfile python3-louis python3-monotonic python3-more-itertools python3-oauthlib python3-olefile python3-pexpect python3-pkg-resources python3-problem-report python3-ptyprocess python3-pyparsing python3-requests python3-rfc3339 python3-secretstorage python3-six python3-tz python3-urllib3 python3-wadllib python3-xkit python3-zipp rygel whoopsie-preferences x11-apps x11-session-utils xbitmaps xbrlapi xcvt xfonts-scalable xinit xinput xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-input-wacom xserver-xorg-video-all xserver-xorg-video-amdgpu xserver-xorg-video-ati xserver-xorg-video-fbdev xserver-xorg-video-intel xserver-xorg-video-nouveau xserver-xorg-video-qxl xserver-xorg-video-radeon xserver-xorg-video-vesa xserver-xorg-video-vmware Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: apport apport-gtk aptdaemon apturl apturl-common command-not-found deja-dup duplicity gedit gnome-control-center gnome-online-accounts gnome-software gnome-software-plugin-snap gnome-terminal hplip ibus ibus-table language-selector-common language-selector-gnome nautilus-extension-gnome-terminal nautilus-share netplan.io networkd-dispatcher orca python3-apport python3-apt python3-aptdaemon python3-aptdaemon.gtk3widgets python3-bcrypt python3-brlapi python3-cairo python3-commandnotfound python3-cups python3-cupshelpers python3-dbus python3-distupgrade python3-gi python3-gi-cairo python3-ibus-1.0 python3-macaroonbakery python3-mako python3-markupsafe python3-nacl python3-netifaces python3-paramiko python3-pil python3-protobuf python3-pyatspi
[Touch-packages] [Bug 1990586] Re: 22.04: python3* mismatched phasing breaks dist-upgrades
python3{.10,-defaults,-stdlib-extensions} have all had their phasing set
to 100% now to avoid this issue.
** Changed in: python3-defaults (Ubuntu)
Status: Triaged => Fix Released
** Changed in: python3-stdlib-extensions (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: python3-stdlib-extensions (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: python3.10 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1990586
Title:
22.04: python3* mismatched phasing breaks dist-upgrades
Status in apt package in Ubuntu:
Incomplete
Status in python3-defaults package in Ubuntu:
Fix Released
Status in python3-stdlib-extensions package in Ubuntu:
Fix Released
Status in python3.10 package in Ubuntu:
Fix Released
Bug description:
Impact
--
Users who manually run sudo apt dist-upgrade without paying attention can
remove essential parts of their system
Test Case
-
This test case won't work as well if phasing is set to 0% or 100%
Create /etc/apt/apt.conf.d/phasing and set its contents to
APT::Machine-ID 2c030cfce3b4487f9810f12a3ac6e87c;
Then run
sudo apt update
sudo apt dist-upgrade
Workaround In Advance
-
Don't run sudo apt dist-upgrade. Just run sudo apt upgrade
Or use Update Manager or the Ubuntu Store to apply updates
Workaround Afterwards
-
Fortunately, apt phasing is ignored for new package installs. So to get your
Ubuntu Desktop back, just run
sudo apt install ubuntu-desktop
Other Info
--
These 3 updates were published today:
python3-stdlib-extensions
python3-defaults
python3.10
Suggested Fix
-
Fully phase those 3 source packages to 100%
Apt Output
--
The following packages were automatically installed and are no longer
required:
apg apport-symptoms aptdaemon-data avahi-utils cups-pk-helper distro-info
gdb gedit-common genisoimage gir1.2-dbusmenu-glib-0.4 gir1.2-dee-1.0
gir1.2-goa-1.0 gir1.2-gst-plugins-base-1.0
gir1.2-gtksource-4 gir1.2-gudev-1.0 gir1.2-notify-0.7
gir1.2-packagekitglib-1.0 gir1.2-rb-3.0 gir1.2-secret-1 gir1.2-snapd-1
gir1.2-totem-1.0 gir1.2-totemplparser-1.0 gir1.2-udisks-2.0
gir1.2-unity-7.0 gir1.2-vte-2.91 gir1.2-wnck-3.0 gnome-control-center-faces
gnome-software-common gnome-terminal-data hplip-data ibus-data ibus-gtk4
libbabeltrace1 libboost-regex1.74.0
libc6-dbg libcolord-gtk1 libdebuginfod-common libdebuginfod1
libdmapsharing-3.0-2 libglu1-mesa libgpod-common libgpod4 libgsound0
libgssdp-1.2-0 libgupnp-1.2-1 libgupnp-av-1.0-3
libgupnp-dlna-2.0-4 libhpmud0 libimagequant0 libipt2 liblirc-client0
libmalcontent-0-0 libnetplan0 libraqm0 librsync2 librygel-core-2.6-2
librygel-db-2.6-2 librygel-renderer-2.6-2
librygel-server-2.6-2 libsane-hpaio libsgutils2-2
libsource-highlight-common libsource-highlight4v5 libwhoopsie-preferences0
libwnck-3-0 libwnck-3-common libxatracker2 libxres1 libxss1
libxvmc1 mobile-broadband-provider-info network-manager-gnome patch
printer-driver-hpcups printer-driver-postscript-hp python-apt-common
python3-blinker python3-certifi python3-cffi-backend
python3-chardet python3-click python3-colorama python3-cryptography
python3-dateutil python3-debconf python3-debian python3-defer
python3-distro-info python3-fasteners python3-future
python3-httplib2 python3-idna python3-importlib-metadata python3-jeepney
python3-jwt python3-keyring python3-launchpadlib python3-lazr.restfulclient
python3-lazr.uri python3-lockfile
python3-louis python3-monotonic python3-more-itertools python3-oauthlib
python3-olefile python3-pexpect python3-pkg-resources python3-problem-report
python3-ptyprocess python3-pyparsing
python3-requests python3-rfc3339 python3-secretstorage python3-six
python3-tz python3-urllib3 python3-wadllib python3-xkit python3-zipp rygel
whoopsie-preferences x11-apps x11-session-utils
xbitmaps xbrlapi xcvt xfonts-scalable xinit xinput xserver-xorg-core
xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-input-wacom
xserver-xorg-video-all
xserver-xorg-video-amdgpu xserver-xorg-video-ati xserver-xorg-video-fbdev
xserver-xorg-video-intel xserver-xorg-video-nouveau xserver-xorg-video-qxl
xserver-xorg-video-radeon
xserver-xorg-video-vesa xserver-xorg-video-vmware
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
apport apport-gtk aptdaemon apturl apturl-common command-not-found deja-dup
duplicity gedit gnome-control-center gnome-online-accounts gnome-software
gnome-software-plugin-snap gnome-terminal
hplip ibus ibus-table language-selector-common language-selector-gnome
nautilus-extension-gnome-terminal nautilus-share netplan.io networkd-dispatcher
orca python3-apport python3-apt
[Touch-packages] [Bug 1990588] [NEW] package systemd 249.11-0ubuntu3.6 failed to install/upgrade: el subproceso instalado paquete systemd script post-installation devolvió el código de salida de error
Public bug reported: updating from server 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: systemd 249.11-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.15.0-48.54~20.04.1-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Sep 22 19:00:53 2022 ErrorMessage: el subproceso instalado paquete systemd script post-installation devolvió el código de salida de error 127 InstallationDate: Installed on 2020-07-28 (786 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel IC4GG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=UUID=8859cc64-d58f-4403-a3dc-284744628c34 ro rootflags=subvol=@ debian-installer/language=es keyboard-configuration/layoutcode?=es consoleblank=60 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: systemd Title: package systemd 249.11-0ubuntu3.6 failed to install/upgrade: el subproceso instalado paquete systemd script post-installation devolvió el código de salida de error 127 UpgradeStatus: Upgraded to focal on 2022-09-22 (0 days ago) dmi.bios.date: 07/03/2012 dmi.bios.release: 0.1 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 63K dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: IC4GG dmi.board.vendor: Intel dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr63K:bd07/03/2012:br0.1:svnIntel:pnIC4GG:pvr0.1:rvnIntel:rnIC4GG:rvrFAB1:cvnIntelCorporation:ct9:cvr0.1:skuSystemSKUNumber: dmi.product.family: ChiefRiver System dmi.product.name: IC4GG dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: Intel mtime.conffile..etc.systemd.logind.conf: 2020-10-22T18:57:27 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1990588 Title: package systemd 249.11-0ubuntu3.6 failed to install/upgrade: el subproceso instalado paquete systemd script post-installation devolvió el código de salida de error 127 Status in systemd package in Ubuntu: New Bug description: updating from server 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: systemd 249.11-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.15.0-48.54~20.04.1-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Sep 22 19:00:53 2022 ErrorMessage: el subproceso instalado paquete systemd script post-installation devolvió el código de salida de error 127 InstallationDate: Installed on 2020-07-28 (786 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel IC4GG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=UUID=8859cc64-d58f-4403-a3dc-284744628c34 ro rootflags=subvol=@ debian-installer/language=es keyboard-configuration/layoutcode?=es consoleblank=60 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: systemd Title: package systemd 249.11-0ubuntu3.6 failed to install/upgrade: el subproceso instalado paquete systemd script post-installation devolvió el código de salida de error 127 UpgradeStatus: Upgraded to focal on 2022-09-22 (0 days ago) dmi.bios.date: 07/03/2012 dmi.bios.release: 0.1 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 63K dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: IC4GG dmi.board.vendor: Intel dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr63K:bd07/03/2012:br0.1:svnIntel:pnIC4GG:pvr0.1:rvnIntel:rnIC4GG:rvrFAB1:cvnIntelCorporation:ct9:cvr0.1:skuSystemSKUNumber: dmi.product.family: ChiefRiver System dmi.product.name: IC4GG dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: Intel mtime.conffile..etc.systemd.logind.conf: 2020-10-22T18:57:27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990588/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1990064] Re: unconfined profile denies userns_create for chromium based processes
NB, also broke Steam (from .deb). Is there a link anywhere to some of this discussion, happy for security to be improved, but I'd like to understand what is being disabled, and what the specific issue is. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1990064 Title: unconfined profile denies userns_create for chromium based processes Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: For Ubuntu 22.10, since the last kernel update, i can´t launch any chromium based browser, due to apparmor denying userns_create dmesg shows: apparmor="DENIED" operation="userns_create" class="namespace" info="User namespace creation restricted" error=-13 profile="unconfined" pid=21323 comm="steamwebhelper" requested="userns_create" denied="userns_create" This happens for every process which uses a chromium engine, like google chrome itself or in this case steamwebhelper. Might be related to this change?: https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/ not sure if it got merged in this form though.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990586] Re: 22.04: python3* mismatched phasing breaks dist-upgrades
I've been thinking about both some more and I believe we can fix this more easily than I thought earlier, but I'd still like the data to be able to reproduce this. Because obviously no such issues occured during testing. In the meantime could SRU team please pull the python3.10 update, or phase it to 0 should work too? ** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1990586 Title: 22.04: python3* mismatched phasing breaks dist-upgrades Status in apt package in Ubuntu: Incomplete Status in python3-defaults package in Ubuntu: Triaged Status in python3-stdlib-extensions package in Ubuntu: Triaged Status in python3.10 package in Ubuntu: Triaged Bug description: Impact -- Users who manually run sudo apt dist-upgrade without paying attention can remove essential parts of their system Test Case - This test case won't work as well if phasing is set to 0% or 100% Create /etc/apt/apt.conf.d/phasing and set its contents to APT::Machine-ID 2c030cfce3b4487f9810f12a3ac6e87c; Then run sudo apt update sudo apt dist-upgrade Workaround In Advance - Don't run sudo apt dist-upgrade. Just run sudo apt upgrade Or use Update Manager or the Ubuntu Store to apply updates Workaround Afterwards - Fortunately, apt phasing is ignored for new package installs. So to get your Ubuntu Desktop back, just run sudo apt install ubuntu-desktop Other Info -- These 3 updates were published today: python3-stdlib-extensions python3-defaults python3.10 Suggested Fix - Fully phase those 3 source packages to 100% Apt Output -- The following packages were automatically installed and are no longer required: apg apport-symptoms aptdaemon-data avahi-utils cups-pk-helper distro-info gdb gedit-common genisoimage gir1.2-dbusmenu-glib-0.4 gir1.2-dee-1.0 gir1.2-goa-1.0 gir1.2-gst-plugins-base-1.0 gir1.2-gtksource-4 gir1.2-gudev-1.0 gir1.2-notify-0.7 gir1.2-packagekitglib-1.0 gir1.2-rb-3.0 gir1.2-secret-1 gir1.2-snapd-1 gir1.2-totem-1.0 gir1.2-totemplparser-1.0 gir1.2-udisks-2.0 gir1.2-unity-7.0 gir1.2-vte-2.91 gir1.2-wnck-3.0 gnome-control-center-faces gnome-software-common gnome-terminal-data hplip-data ibus-data ibus-gtk4 libbabeltrace1 libboost-regex1.74.0 libc6-dbg libcolord-gtk1 libdebuginfod-common libdebuginfod1 libdmapsharing-3.0-2 libglu1-mesa libgpod-common libgpod4 libgsound0 libgssdp-1.2-0 libgupnp-1.2-1 libgupnp-av-1.0-3 libgupnp-dlna-2.0-4 libhpmud0 libimagequant0 libipt2 liblirc-client0 libmalcontent-0-0 libnetplan0 libraqm0 librsync2 librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 libsane-hpaio libsgutils2-2 libsource-highlight-common libsource-highlight4v5 libwhoopsie-preferences0 libwnck-3-0 libwnck-3-common libxatracker2 libxres1 libxss1 libxvmc1 mobile-broadband-provider-info network-manager-gnome patch printer-driver-hpcups printer-driver-postscript-hp python-apt-common python3-blinker python3-certifi python3-cffi-backend python3-chardet python3-click python3-colorama python3-cryptography python3-dateutil python3-debconf python3-debian python3-defer python3-distro-info python3-fasteners python3-future python3-httplib2 python3-idna python3-importlib-metadata python3-jeepney python3-jwt python3-keyring python3-launchpadlib python3-lazr.restfulclient python3-lazr.uri python3-lockfile python3-louis python3-monotonic python3-more-itertools python3-oauthlib python3-olefile python3-pexpect python3-pkg-resources python3-problem-report python3-ptyprocess python3-pyparsing python3-requests python3-rfc3339 python3-secretstorage python3-six python3-tz python3-urllib3 python3-wadllib python3-xkit python3-zipp rygel whoopsie-preferences x11-apps x11-session-utils xbitmaps xbrlapi xcvt xfonts-scalable xinit xinput xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-input-wacom xserver-xorg-video-all xserver-xorg-video-amdgpu xserver-xorg-video-ati xserver-xorg-video-fbdev xserver-xorg-video-intel xserver-xorg-video-nouveau xserver-xorg-video-qxl xserver-xorg-video-radeon xserver-xorg-video-vesa xserver-xorg-video-vmware Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: apport apport-gtk aptdaemon apturl apturl-common command-not-found deja-dup duplicity gedit gnome-control-center gnome-online-accounts gnome-software gnome-software-plugin-snap gnome-terminal hplip ibus ibus-table language-selector-common language-selector-gnome nautilus-extension-gnome-terminal nautilus-share netplan.io networkd-dispatcher orca python3-apport python3-apt python3-aptdaemon python3-aptdaemon.gtk3widgets python3-bcrypt python3-brlapi python3-cairo
[Touch-packages] [Bug 1990586] Re: 22.04: python3* mismatched phasing breaks dist-upgrades
Same issue as [Bug 1990525] [NEW] E: Internal Error, AutoRemover broke stuff. See the comment there. ** Changed in: apt (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1990586 Title: 22.04: python3* mismatched phasing breaks dist-upgrades Status in apt package in Ubuntu: Incomplete Status in python3-defaults package in Ubuntu: Triaged Status in python3-stdlib-extensions package in Ubuntu: Triaged Status in python3.10 package in Ubuntu: Triaged Bug description: Impact -- Users who manually run sudo apt dist-upgrade without paying attention can remove essential parts of their system Test Case - This test case won't work as well if phasing is set to 0% or 100% Create /etc/apt/apt.conf.d/phasing and set its contents to APT::Machine-ID 2c030cfce3b4487f9810f12a3ac6e87c; Then run sudo apt update sudo apt dist-upgrade Workaround In Advance - Don't run sudo apt dist-upgrade. Just run sudo apt upgrade Or use Update Manager or the Ubuntu Store to apply updates Workaround Afterwards - Fortunately, apt phasing is ignored for new package installs. So to get your Ubuntu Desktop back, just run sudo apt install ubuntu-desktop Other Info -- These 3 updates were published today: python3-stdlib-extensions python3-defaults python3.10 Suggested Fix - Fully phase those 3 source packages to 100% Apt Output -- The following packages were automatically installed and are no longer required: apg apport-symptoms aptdaemon-data avahi-utils cups-pk-helper distro-info gdb gedit-common genisoimage gir1.2-dbusmenu-glib-0.4 gir1.2-dee-1.0 gir1.2-goa-1.0 gir1.2-gst-plugins-base-1.0 gir1.2-gtksource-4 gir1.2-gudev-1.0 gir1.2-notify-0.7 gir1.2-packagekitglib-1.0 gir1.2-rb-3.0 gir1.2-secret-1 gir1.2-snapd-1 gir1.2-totem-1.0 gir1.2-totemplparser-1.0 gir1.2-udisks-2.0 gir1.2-unity-7.0 gir1.2-vte-2.91 gir1.2-wnck-3.0 gnome-control-center-faces gnome-software-common gnome-terminal-data hplip-data ibus-data ibus-gtk4 libbabeltrace1 libboost-regex1.74.0 libc6-dbg libcolord-gtk1 libdebuginfod-common libdebuginfod1 libdmapsharing-3.0-2 libglu1-mesa libgpod-common libgpod4 libgsound0 libgssdp-1.2-0 libgupnp-1.2-1 libgupnp-av-1.0-3 libgupnp-dlna-2.0-4 libhpmud0 libimagequant0 libipt2 liblirc-client0 libmalcontent-0-0 libnetplan0 libraqm0 librsync2 librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 libsane-hpaio libsgutils2-2 libsource-highlight-common libsource-highlight4v5 libwhoopsie-preferences0 libwnck-3-0 libwnck-3-common libxatracker2 libxres1 libxss1 libxvmc1 mobile-broadband-provider-info network-manager-gnome patch printer-driver-hpcups printer-driver-postscript-hp python-apt-common python3-blinker python3-certifi python3-cffi-backend python3-chardet python3-click python3-colorama python3-cryptography python3-dateutil python3-debconf python3-debian python3-defer python3-distro-info python3-fasteners python3-future python3-httplib2 python3-idna python3-importlib-metadata python3-jeepney python3-jwt python3-keyring python3-launchpadlib python3-lazr.restfulclient python3-lazr.uri python3-lockfile python3-louis python3-monotonic python3-more-itertools python3-oauthlib python3-olefile python3-pexpect python3-pkg-resources python3-problem-report python3-ptyprocess python3-pyparsing python3-requests python3-rfc3339 python3-secretstorage python3-six python3-tz python3-urllib3 python3-wadllib python3-xkit python3-zipp rygel whoopsie-preferences x11-apps x11-session-utils xbitmaps xbrlapi xcvt xfonts-scalable xinit xinput xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-input-wacom xserver-xorg-video-all xserver-xorg-video-amdgpu xserver-xorg-video-ati xserver-xorg-video-fbdev xserver-xorg-video-intel xserver-xorg-video-nouveau xserver-xorg-video-qxl xserver-xorg-video-radeon xserver-xorg-video-vesa xserver-xorg-video-vmware Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: apport apport-gtk aptdaemon apturl apturl-common command-not-found deja-dup duplicity gedit gnome-control-center gnome-online-accounts gnome-software gnome-software-plugin-snap gnome-terminal hplip ibus ibus-table language-selector-common language-selector-gnome nautilus-extension-gnome-terminal nautilus-share netplan.io networkd-dispatcher orca python3-apport python3-apt python3-aptdaemon python3-aptdaemon.gtk3widgets python3-bcrypt python3-brlapi python3-cairo python3-commandnotfound python3-cups python3-cupshelpers python3-dbus python3-distupgrade python3-gi python3-gi-cairo python3-ibus-1.0 python3-macaroonbakery python3-mako python3-markupsafe
[Touch-packages] [Bug 1990064] Re: unconfined profile denies userns_create for chromium based processes
It broke for me between 5.19.0-15 and 5.19.0-17, and breaks every flatpak app I have installed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1990064 Title: unconfined profile denies userns_create for chromium based processes Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: For Ubuntu 22.10, since the last kernel update, i can´t launch any chromium based browser, due to apparmor denying userns_create dmesg shows: apparmor="DENIED" operation="userns_create" class="namespace" info="User namespace creation restricted" error=-13 profile="unconfined" pid=21323 comm="steamwebhelper" requested="userns_create" denied="userns_create" This happens for every process which uses a chromium engine, like google chrome itself or in this case steamwebhelper. Might be related to this change?: https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/ not sure if it got merged in this form though.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990586] Re: 22.04: python3* mismatched phasing breaks dist-upgrades
** Description changed: Impact -- Users who manually run sudo apt dist-upgrade without paying attention can remove essential parts of their system Test Case - This test case won't work as well if phasing is set to 0% or 100% - Set /etc/machine-id to 2c030cfce3b4487f9810f12a3ac6e87c + Create /etc/apt/apt.conf.d/phasing and set its contents to + APT::Machine-ID 2c030cfce3b4487f9810f12a3ac6e87c; + + Then run sudo apt update sudo apt dist-upgrade Workaround In Advance - Don't run sudo apt dist-upgrade. Just run sudo apt upgrade Or use Update Manager or the Ubuntu Store to apply updates Workaround Afterwards - Fortunately, apt phasing is ignored for new package installs. So to get your Ubuntu Desktop back, just run sudo apt install ubuntu-desktop Other Info -- These 3 updates were published today: python3-stdlib-extensions python3-defaults python3.10 Suggested Fix - Fully phase those 3 source packages to 100% Apt Output -- The following packages were automatically installed and are no longer required: apg apport-symptoms aptdaemon-data avahi-utils cups-pk-helper distro-info gdb gedit-common genisoimage gir1.2-dbusmenu-glib-0.4 gir1.2-dee-1.0 gir1.2-goa-1.0 gir1.2-gst-plugins-base-1.0 gir1.2-gtksource-4 gir1.2-gudev-1.0 gir1.2-notify-0.7 gir1.2-packagekitglib-1.0 gir1.2-rb-3.0 gir1.2-secret-1 gir1.2-snapd-1 gir1.2-totem-1.0 gir1.2-totemplparser-1.0 gir1.2-udisks-2.0 gir1.2-unity-7.0 gir1.2-vte-2.91 gir1.2-wnck-3.0 gnome-control-center-faces gnome-software-common gnome-terminal-data hplip-data ibus-data ibus-gtk4 libbabeltrace1 libboost-regex1.74.0 libc6-dbg libcolord-gtk1 libdebuginfod-common libdebuginfod1 libdmapsharing-3.0-2 libglu1-mesa libgpod-common libgpod4 libgsound0 libgssdp-1.2-0 libgupnp-1.2-1 libgupnp-av-1.0-3 libgupnp-dlna-2.0-4 libhpmud0 libimagequant0 libipt2 liblirc-client0 libmalcontent-0-0 libnetplan0 libraqm0 librsync2 librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 libsane-hpaio libsgutils2-2 libsource-highlight-common libsource-highlight4v5 libwhoopsie-preferences0 libwnck-3-0 libwnck-3-common libxatracker2 libxres1 libxss1 libxvmc1 mobile-broadband-provider-info network-manager-gnome patch printer-driver-hpcups printer-driver-postscript-hp python-apt-common python3-blinker python3-certifi python3-cffi-backend python3-chardet python3-click python3-colorama python3-cryptography python3-dateutil python3-debconf python3-debian python3-defer python3-distro-info python3-fasteners python3-future python3-httplib2 python3-idna python3-importlib-metadata python3-jeepney python3-jwt python3-keyring python3-launchpadlib python3-lazr.restfulclient python3-lazr.uri python3-lockfile python3-louis python3-monotonic python3-more-itertools python3-oauthlib python3-olefile python3-pexpect python3-pkg-resources python3-problem-report python3-ptyprocess python3-pyparsing python3-requests python3-rfc3339 python3-secretstorage python3-six python3-tz python3-urllib3 python3-wadllib python3-xkit python3-zipp rygel whoopsie-preferences x11-apps x11-session-utils xbitmaps xbrlapi xcvt xfonts-scalable xinit xinput xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-input-wacom xserver-xorg-video-all xserver-xorg-video-amdgpu xserver-xorg-video-ati xserver-xorg-video-fbdev xserver-xorg-video-intel xserver-xorg-video-nouveau xserver-xorg-video-qxl xserver-xorg-video-radeon xserver-xorg-video-vesa xserver-xorg-video-vmware Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: apport apport-gtk aptdaemon apturl apturl-common command-not-found deja-dup duplicity gedit gnome-control-center gnome-online-accounts gnome-software gnome-software-plugin-snap gnome-terminal hplip ibus ibus-table language-selector-common language-selector-gnome nautilus-extension-gnome-terminal nautilus-share netplan.io networkd-dispatcher orca python3-apport python3-apt python3-aptdaemon python3-aptdaemon.gtk3widgets python3-bcrypt python3-brlapi python3-cairo python3-commandnotfound python3-cups python3-cupshelpers python3-dbus python3-distupgrade python3-gi python3-gi-cairo python3-ibus-1.0 python3-macaroonbakery python3-mako python3-markupsafe python3-nacl python3-netifaces python3-paramiko python3-pil python3-protobuf python3-pyatspi python3-pymacaroons python3-renderpm python3-reportlab python3-reportlab-accel python3-software-properties python3-systemd python3-uno python3-update-manager python3-yaml rhythmbox-plugin-alternative-toolbar rhythmbox-plugins software-properties-common software-properties-gtk system-config-printer system-config-printer-common system-config-printer-udev totem-plugins ubuntu-advantage-desktop-daemon ubuntu-advantage-tools
[Touch-packages] [Bug 1990586] Re: 22.04: python3* mismatched phasing breaks dist-upgrades
** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1990586 Title: 22.04: python3* mismatched phasing breaks dist-upgrades Status in apt package in Ubuntu: Triaged Status in python3-defaults package in Ubuntu: Triaged Status in python3-stdlib-extensions package in Ubuntu: Triaged Status in python3.10 package in Ubuntu: Triaged Bug description: Impact -- Users who manually run sudo apt dist-upgrade without paying attention can remove essential parts of their system Test Case - This test case won't work as well if phasing is set to 0% or 100% Set /etc/machine-id to 2c030cfce3b4487f9810f12a3ac6e87c sudo apt update sudo apt dist-upgrade Workaround In Advance - Don't run sudo apt dist-upgrade. Just run sudo apt upgrade Or use Update Manager or the Ubuntu Store to apply updates Workaround Afterwards - Fortunately, apt phasing is ignored for new package installs. So to get your Ubuntu Desktop back, just run sudo apt install ubuntu-desktop Other Info -- These 3 updates were published today: python3-stdlib-extensions python3-defaults python3.10 Suggested Fix - Fully phase those 3 source packages to 100% Apt Output -- The following packages were automatically installed and are no longer required: apg apport-symptoms aptdaemon-data avahi-utils cups-pk-helper distro-info gdb gedit-common genisoimage gir1.2-dbusmenu-glib-0.4 gir1.2-dee-1.0 gir1.2-goa-1.0 gir1.2-gst-plugins-base-1.0 gir1.2-gtksource-4 gir1.2-gudev-1.0 gir1.2-notify-0.7 gir1.2-packagekitglib-1.0 gir1.2-rb-3.0 gir1.2-secret-1 gir1.2-snapd-1 gir1.2-totem-1.0 gir1.2-totemplparser-1.0 gir1.2-udisks-2.0 gir1.2-unity-7.0 gir1.2-vte-2.91 gir1.2-wnck-3.0 gnome-control-center-faces gnome-software-common gnome-terminal-data hplip-data ibus-data ibus-gtk4 libbabeltrace1 libboost-regex1.74.0 libc6-dbg libcolord-gtk1 libdebuginfod-common libdebuginfod1 libdmapsharing-3.0-2 libglu1-mesa libgpod-common libgpod4 libgsound0 libgssdp-1.2-0 libgupnp-1.2-1 libgupnp-av-1.0-3 libgupnp-dlna-2.0-4 libhpmud0 libimagequant0 libipt2 liblirc-client0 libmalcontent-0-0 libnetplan0 libraqm0 librsync2 librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 libsane-hpaio libsgutils2-2 libsource-highlight-common libsource-highlight4v5 libwhoopsie-preferences0 libwnck-3-0 libwnck-3-common libxatracker2 libxres1 libxss1 libxvmc1 mobile-broadband-provider-info network-manager-gnome patch printer-driver-hpcups printer-driver-postscript-hp python-apt-common python3-blinker python3-certifi python3-cffi-backend python3-chardet python3-click python3-colorama python3-cryptography python3-dateutil python3-debconf python3-debian python3-defer python3-distro-info python3-fasteners python3-future python3-httplib2 python3-idna python3-importlib-metadata python3-jeepney python3-jwt python3-keyring python3-launchpadlib python3-lazr.restfulclient python3-lazr.uri python3-lockfile python3-louis python3-monotonic python3-more-itertools python3-oauthlib python3-olefile python3-pexpect python3-pkg-resources python3-problem-report python3-ptyprocess python3-pyparsing python3-requests python3-rfc3339 python3-secretstorage python3-six python3-tz python3-urllib3 python3-wadllib python3-xkit python3-zipp rygel whoopsie-preferences x11-apps x11-session-utils xbitmaps xbrlapi xcvt xfonts-scalable xinit xinput xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-input-wacom xserver-xorg-video-all xserver-xorg-video-amdgpu xserver-xorg-video-ati xserver-xorg-video-fbdev xserver-xorg-video-intel xserver-xorg-video-nouveau xserver-xorg-video-qxl xserver-xorg-video-radeon xserver-xorg-video-vesa xserver-xorg-video-vmware Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: apport apport-gtk aptdaemon apturl apturl-common command-not-found deja-dup duplicity gedit gnome-control-center gnome-online-accounts gnome-software gnome-software-plugin-snap gnome-terminal hplip ibus ibus-table language-selector-common language-selector-gnome nautilus-extension-gnome-terminal nautilus-share netplan.io networkd-dispatcher orca python3-apport python3-apt python3-aptdaemon python3-aptdaemon.gtk3widgets python3-bcrypt python3-brlapi python3-cairo python3-commandnotfound python3-cups python3-cupshelpers python3-dbus python3-distupgrade python3-gi python3-gi-cairo python3-ibus-1.0 python3-macaroonbakery python3-mako python3-markupsafe python3-nacl python3-netifaces python3-paramiko python3-pil python3-protobuf python3-pyatspi python3-pymacaroons python3-renderpm python3-reportlab python3-reportlab-accel python3-software-properties
[Touch-packages] [Bug 1990586] [NEW] 22.04: python3* mismatched phasing breaks dist-upgrades
Public bug reported: Impact -- Users who manually run sudo apt dist-upgrade without paying attention can remove essential parts of their system Test Case - This test case won't work as well if phasing is set to 0% or 100% Set /etc/machine-id to 2c030cfce3b4487f9810f12a3ac6e87c sudo apt update sudo apt dist-upgrade Workaround In Advance - Don't run sudo apt dist-upgrade. Just run sudo apt upgrade Or use Update Manager or the Ubuntu Store to apply updates Workaround Afterwards - Fortunately, apt phasing is ignored for new package installs. So to get your Ubuntu Desktop back, just run sudo apt install ubuntu-desktop Other Info -- These 3 updates were published today: python3-stdlib-extensions python3-defaults python3.10 Suggested Fix - Fully phase those 3 source packages to 100% Apt Output -- The following packages were automatically installed and are no longer required: apg apport-symptoms aptdaemon-data avahi-utils cups-pk-helper distro-info gdb gedit-common genisoimage gir1.2-dbusmenu-glib-0.4 gir1.2-dee-1.0 gir1.2-goa-1.0 gir1.2-gst-plugins-base-1.0 gir1.2-gtksource-4 gir1.2-gudev-1.0 gir1.2-notify-0.7 gir1.2-packagekitglib-1.0 gir1.2-rb-3.0 gir1.2-secret-1 gir1.2-snapd-1 gir1.2-totem-1.0 gir1.2-totemplparser-1.0 gir1.2-udisks-2.0 gir1.2-unity-7.0 gir1.2-vte-2.91 gir1.2-wnck-3.0 gnome-control-center-faces gnome-software-common gnome-terminal-data hplip-data ibus-data ibus-gtk4 libbabeltrace1 libboost-regex1.74.0 libc6-dbg libcolord-gtk1 libdebuginfod-common libdebuginfod1 libdmapsharing-3.0-2 libglu1-mesa libgpod-common libgpod4 libgsound0 libgssdp-1.2-0 libgupnp-1.2-1 libgupnp-av-1.0-3 libgupnp-dlna-2.0-4 libhpmud0 libimagequant0 libipt2 liblirc-client0 libmalcontent-0-0 libnetplan0 libraqm0 librsync2 librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 libsane-hpaio libsgutils2-2 libsource-highlight-common libsource-highlight4v5 libwhoopsie-preferences0 libwnck-3-0 libwnck-3-common libxatracker2 libxres1 libxss1 libxvmc1 mobile-broadband-provider-info network-manager-gnome patch printer-driver-hpcups printer-driver-postscript-hp python-apt-common python3-blinker python3-certifi python3-cffi-backend python3-chardet python3-click python3-colorama python3-cryptography python3-dateutil python3-debconf python3-debian python3-defer python3-distro-info python3-fasteners python3-future python3-httplib2 python3-idna python3-importlib-metadata python3-jeepney python3-jwt python3-keyring python3-launchpadlib python3-lazr.restfulclient python3-lazr.uri python3-lockfile python3-louis python3-monotonic python3-more-itertools python3-oauthlib python3-olefile python3-pexpect python3-pkg-resources python3-problem-report python3-ptyprocess python3-pyparsing python3-requests python3-rfc3339 python3-secretstorage python3-six python3-tz python3-urllib3 python3-wadllib python3-xkit python3-zipp rygel whoopsie-preferences x11-apps x11-session-utils xbitmaps xbrlapi xcvt xfonts-scalable xinit xinput xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-input-wacom xserver-xorg-video-all xserver-xorg-video-amdgpu xserver-xorg-video-ati xserver-xorg-video-fbdev xserver-xorg-video-intel xserver-xorg-video-nouveau xserver-xorg-video-qxl xserver-xorg-video-radeon xserver-xorg-video-vesa xserver-xorg-video-vmware Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: apport apport-gtk aptdaemon apturl apturl-common command-not-found deja-dup duplicity gedit gnome-control-center gnome-online-accounts gnome-software gnome-software-plugin-snap gnome-terminal hplip ibus ibus-table language-selector-common language-selector-gnome nautilus-extension-gnome-terminal nautilus-share netplan.io networkd-dispatcher orca python3-apport python3-apt python3-aptdaemon python3-aptdaemon.gtk3widgets python3-bcrypt python3-brlapi python3-cairo python3-commandnotfound python3-cups python3-cupshelpers python3-dbus python3-distupgrade python3-gi python3-gi-cairo python3-ibus-1.0 python3-macaroonbakery python3-mako python3-markupsafe python3-nacl python3-netifaces python3-paramiko python3-pil python3-protobuf python3-pyatspi python3-pymacaroons python3-renderpm python3-reportlab python3-reportlab-accel python3-software-properties python3-systemd python3-uno python3-update-manager python3-yaml rhythmbox-plugin-alternative-toolbar rhythmbox-plugins software-properties-common software-properties-gtk system-config-printer system-config-printer-common system-config-printer-udev totem-plugins ubuntu-advantage-desktop-daemon ubuntu-advantage-tools ubuntu-desktop ubuntu-desktop-minimal ubuntu-drivers-common ubuntu-minimal ubuntu-release-upgrader-core ubuntu-release-upgrader-gtk ubuntu-session unattended-upgrades update-manager update-manager-core update-notifier update-notifier-common usb-creator-common
[Touch-packages] [Bug 1990562] Re: attempting to diff static library files raises UnicodeDecodeError
** Changed in: dh-python (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1990562 Title: attempting to diff static library files raises UnicodeDecodeError Status in dh-python package in Ubuntu: Confirmed Status in dh-python package in Debian: New Bug description: In verbose mode, if files differ in share_files(), dhpython will try to show a diff of the files. When these files are static libraries, this raises a UnicodeDecodeError. For example, from a recent numpy build on arm64[1]: W: dh_python3 fs:146: Paths differ: debian/python3-numpy/usr/lib/python3.10/dist-packages/numpy/random/lib/libnpyrandom.a and debian/python3-numpy/usr/lib/python3/dist-packages/numpy/random/lib/libnpyrandom.a Traceback (most recent call last): File "/usr/bin/dh_python3", line 284, in main() File "/usr/bin/dh_python3", line 210, in main fix_locations(package, interpreter, SUPPORTED, options) File "/usr/share/dh-python/dhpython/fs.py", line 53, in fix_locations share_files(srcdir, dstdir, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files share_files(fpath1, fpath2, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files share_files(fpath1, fpath2, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files share_files(fpath1, fpath2, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 149, in share_files fromlines = fp1.readlines() File "/usr/lib/python3.10/codecs.py", line 322, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf6 in position 75: invalid start byte make[1]: *** [debian/rules:46: override_dh_python3] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:15: binary-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2 There is already logic to skip this diff for .so files, so the same should be done for .a files. [1] https://launchpadlibrarian.net/624822201/buildlog_ubuntu-kinetic- arm64.numpy_1%3A1.21.5-1build2_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1990562/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1989599] Re: Random auditd start failures on Ubuntu 20.04 EC2 AMIs
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: audit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/1989599 Title: Random auditd start failures on Ubuntu 20.04 EC2 AMIs Status in audit package in Ubuntu: Confirmed Bug description: Description:Ubuntu 20.04.5 LTS Release:20.04 linux-image-aws 5.15.0.1019.23~20.04.11 auditd 1:2.8.5-2ubuntu6 I am having issues with auditd on Ubuntu 20.04 LTS Ubuntu official AMIs. I have tested this with published AMIs ami-0123376e204addb71 and ami-00bb3d0b5b36e89b8. I am following a process that has worked up to June 20 2022. The process installs and configures the audit package for CIS hardening. The process steps are: • Launch an instance as a base, I’ve used ami-0123376e204addb71 or ami-00bb3d0b5b36e89b8 (official Ubuntu AMIs). • Installed the packages listed below. • Copied the “auditdconf” contents as /etc/audit/auditd.conf • Copied the “auditrules” contents as /etc/audit/rules.d/audit.rules • Edit /etc/default/grub, and set: GRUB_CMDLINE_LINUX="audit=1 selinux=1 audit_backlog_limit=8192" • Run: grub-mkconfig > /boot/grub/grub.cfg • Stopped the instance, and created an AMI. I then launch 10 or 14 instances of this AMI in us-west-2. Most will come up with auditd service running, and all rules loaded. Usually at least two come up broken for unknown reason, with the auditd service reporting an error I cannot understand: ● auditd.service - Security Auditing Service Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2022-09-14 15:08:14 UTC; 22min ago Docs: man:auditd(8) https://github.com/linux-audit/audit-documentation Process: 357 ExecStart=/sbin/auditd (code=exited, status=1/FAILURE) Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: Starting Security Auditing Service... Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Error receiving audit netlink packet (No buffer space available) Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Error setting audit daemon pid (No buffer space available) Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Unable to set audit pid, exiting Sep 14 15:08:14 ip-10-210-197-90 auditd[357]: Cannot daemonize (Success) Sep 14 15:08:14 ip-10-210-197-90 auditd[357]: The audit daemon is exiting. Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: The audit daemon is exiting. Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: auditd.service: Control process exited, code=exited, status=1/FAILURE Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: auditd.service: Failed with result 'exit-code'. Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: Failed to start Security Auditing Service. When I launch the above, it is a launch of 10 or so instances from the same AMI, with the same parameters. Matter of fact, the launch is done by requesting X number of instances during the EC2 instance launch I've been trying to solve this for some time, and I've found the only way I can make the instances always start correctly is to remove the kernel "audit_backlog_limit" setting entirely - no value for the parameter works correctly (tried 320, 8192, 16384, 32768). See attachments for the above mentioned files. Thanks. -Alan expected behavior is: * service loaded and active * "auditctl -l" shows list of loaded rules seen behavior: * service dead with errors shown above. * "auditctl -l" reports "No rules". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1989599/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1989309] Re: [FFe] apparmor 3.1.1 upstream release
As you say there are many new things in there. At this point its probably better to just land the two things we care about 1. posix ipc mediation 2. user namespace mediation on top of the existing 3.0.7. That would give us a clear set of important features, with a we defined set of patches instead of the big 3.1.1 blob. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1989309 Title: [FFe] apparmor 3.1.1 upstream release Status in apparmor package in Ubuntu: Incomplete Bug description: AppArmor 3.1.1 is the latest upstream version of the apparmor userspace tooling. This includes a large number of bug fixes since the 3.0.7 release which is currently in kinetic, as well as various cleanups and optimisations to the different tools to improve performance and maintainability. The full ChangeLog can be seen at [1]. Upstream does not provide a ChangeLog file, however I have generated one based on the git commit history of apparmor from the 3.0.7 tag to 3.1.1 as: $ git log v3.0.7...v3.1.1 -- > ~/Downloads/apparmor-3.0.7-to-3.1.1-git-log.log This can be seen in the attached file https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+attachment/5617640/+files/apparmor-3.0.7-to-3.1.1-git- log.log TESTING This has been extensively tested by the security team - this includes following the documented Ubuntu merges test plan[2] for AppArmor and the extensive QA Regression Tests[3] for AppArmor as well. This ensures that the various applications that make heavy use of AppArmor (LXD, docker, lxc, dbus, libvirt, snapd etc) have all been exercised and no regressions have been observed. All tests have passed and demonstrated both apparmor and the various applications that use it to be working as expected. BUILD LOGS This is currently uploaded to https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309, build logs can be found on Launchpad at: https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309/+build/24491969 for amd64 etc DEBDIFF The debdiff can be found in the PPA: https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309/+files/apparmor_3.0.7-1ubuntu1_3.1.1-0ubuntu1.diff.gz INSTALL / UPGRADE LOG The apt upgrade log is attached in https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+attachment/5617638/+files/apparmor-3.1.1-0ubuntu1-apt- upgrade.log [1] https://gitlab.com/apparmor/apparmor/-/wikis/Release_Notes_3.1 [2] https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor [3] https://git.launchpad.net/qa-regression-testing/tree/scripts/test-apparmor.py To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990562] Re: attempting to diff static library files raises UnicodeDecodeError
** Bug watch added: Debian Bug tracker #1020528 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020528 ** Also affects: dh-python (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020528 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1990562 Title: attempting to diff static library files raises UnicodeDecodeError Status in dh-python package in Ubuntu: Confirmed Status in dh-python package in Debian: Unknown Bug description: In verbose mode, if files differ in share_files(), dhpython will try to show a diff of the files. When these files are static libraries, this raises a UnicodeDecodeError. For example, from a recent numpy build on arm64[1]: W: dh_python3 fs:146: Paths differ: debian/python3-numpy/usr/lib/python3.10/dist-packages/numpy/random/lib/libnpyrandom.a and debian/python3-numpy/usr/lib/python3/dist-packages/numpy/random/lib/libnpyrandom.a Traceback (most recent call last): File "/usr/bin/dh_python3", line 284, in main() File "/usr/bin/dh_python3", line 210, in main fix_locations(package, interpreter, SUPPORTED, options) File "/usr/share/dh-python/dhpython/fs.py", line 53, in fix_locations share_files(srcdir, dstdir, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files share_files(fpath1, fpath2, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files share_files(fpath1, fpath2, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files share_files(fpath1, fpath2, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 149, in share_files fromlines = fp1.readlines() File "/usr/lib/python3.10/codecs.py", line 322, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf6 in position 75: invalid start byte make[1]: *** [debian/rules:46: override_dh_python3] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:15: binary-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2 There is already logic to skip this diff for .so files, so the same should be done for .a files. [1] https://launchpadlibrarian.net/624822201/buildlog_ubuntu-kinetic- arm64.numpy_1%3A1.21.5-1build2_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1990562/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990562] Re: attempting to diff static library files raises UnicodeDecodeError
** Changed in: dh-python (Ubuntu) Status: In Progress => Confirmed ** Changed in: dh-python (Ubuntu) Assignee: Nick Rosbrook (enr0n) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1990562 Title: attempting to diff static library files raises UnicodeDecodeError Status in dh-python package in Ubuntu: Confirmed Bug description: In verbose mode, if files differ in share_files(), dhpython will try to show a diff of the files. When these files are static libraries, this raises a UnicodeDecodeError. For example, from a recent numpy build on arm64[1]: W: dh_python3 fs:146: Paths differ: debian/python3-numpy/usr/lib/python3.10/dist-packages/numpy/random/lib/libnpyrandom.a and debian/python3-numpy/usr/lib/python3/dist-packages/numpy/random/lib/libnpyrandom.a Traceback (most recent call last): File "/usr/bin/dh_python3", line 284, in main() File "/usr/bin/dh_python3", line 210, in main fix_locations(package, interpreter, SUPPORTED, options) File "/usr/share/dh-python/dhpython/fs.py", line 53, in fix_locations share_files(srcdir, dstdir, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files share_files(fpath1, fpath2, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files share_files(fpath1, fpath2, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files share_files(fpath1, fpath2, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 149, in share_files fromlines = fp1.readlines() File "/usr/lib/python3.10/codecs.py", line 322, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf6 in position 75: invalid start byte make[1]: *** [debian/rules:46: override_dh_python3] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:15: binary-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2 There is already logic to skip this diff for .so files, so the same should be done for .a files. [1] https://launchpadlibrarian.net/624822201/buildlog_ubuntu-kinetic- arm64.numpy_1%3A1.21.5-1build2_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1990562/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990562] Re: attempting to diff static library files raises UnicodeDecodeError
** Patch added: "dh-python_5.20220819ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1990562/+attachment/5618100/+files/dh-python_5.20220819ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1990562 Title: attempting to diff static library files raises UnicodeDecodeError Status in dh-python package in Ubuntu: Confirmed Bug description: In verbose mode, if files differ in share_files(), dhpython will try to show a diff of the files. When these files are static libraries, this raises a UnicodeDecodeError. For example, from a recent numpy build on arm64[1]: W: dh_python3 fs:146: Paths differ: debian/python3-numpy/usr/lib/python3.10/dist-packages/numpy/random/lib/libnpyrandom.a and debian/python3-numpy/usr/lib/python3/dist-packages/numpy/random/lib/libnpyrandom.a Traceback (most recent call last): File "/usr/bin/dh_python3", line 284, in main() File "/usr/bin/dh_python3", line 210, in main fix_locations(package, interpreter, SUPPORTED, options) File "/usr/share/dh-python/dhpython/fs.py", line 53, in fix_locations share_files(srcdir, dstdir, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files share_files(fpath1, fpath2, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files share_files(fpath1, fpath2, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files share_files(fpath1, fpath2, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 149, in share_files fromlines = fp1.readlines() File "/usr/lib/python3.10/codecs.py", line 322, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf6 in position 75: invalid start byte make[1]: *** [debian/rules:46: override_dh_python3] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:15: binary-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2 There is already logic to skip this diff for .so files, so the same should be done for .a files. [1] https://launchpadlibrarian.net/624822201/buildlog_ubuntu-kinetic- arm64.numpy_1%3A1.21.5-1build2_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1990562/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990562] [NEW] attempting to diff static library files raises UnicodeDecodeError
Public bug reported: In verbose mode, if files differ in share_files(), dhpython will try to show a diff of the files. When these files are static libraries, this raises a UnicodeDecodeError. For example, from a recent numpy build on arm64[1]: W: dh_python3 fs:146: Paths differ: debian/python3-numpy/usr/lib/python3.10/dist-packages/numpy/random/lib/libnpyrandom.a and debian/python3-numpy/usr/lib/python3/dist-packages/numpy/random/lib/libnpyrandom.a Traceback (most recent call last): File "/usr/bin/dh_python3", line 284, in main() File "/usr/bin/dh_python3", line 210, in main fix_locations(package, interpreter, SUPPORTED, options) File "/usr/share/dh-python/dhpython/fs.py", line 53, in fix_locations share_files(srcdir, dstdir, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files share_files(fpath1, fpath2, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files share_files(fpath1, fpath2, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files share_files(fpath1, fpath2, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 149, in share_files fromlines = fp1.readlines() File "/usr/lib/python3.10/codecs.py", line 322, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf6 in position 75: invalid start byte make[1]: *** [debian/rules:46: override_dh_python3] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:15: binary-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2 There is already logic to skip this diff for .so files, so the same should be done for .a files. [1] https://launchpadlibrarian.net/624822201/buildlog_ubuntu-kinetic- arm64.numpy_1%3A1.21.5-1build2_BUILDING.txt.gz ** Affects: dh-python (Ubuntu) Importance: Medium Status: Confirmed ** Changed in: dh-python (Ubuntu) Importance: Undecided => Medium ** Changed in: dh-python (Ubuntu) Status: New => In Progress ** Changed in: dh-python (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1990562 Title: attempting to diff static library files raises UnicodeDecodeError Status in dh-python package in Ubuntu: Confirmed Bug description: In verbose mode, if files differ in share_files(), dhpython will try to show a diff of the files. When these files are static libraries, this raises a UnicodeDecodeError. For example, from a recent numpy build on arm64[1]: W: dh_python3 fs:146: Paths differ: debian/python3-numpy/usr/lib/python3.10/dist-packages/numpy/random/lib/libnpyrandom.a and debian/python3-numpy/usr/lib/python3/dist-packages/numpy/random/lib/libnpyrandom.a Traceback (most recent call last): File "/usr/bin/dh_python3", line 284, in main() File "/usr/bin/dh_python3", line 210, in main fix_locations(package, interpreter, SUPPORTED, options) File "/usr/share/dh-python/dhpython/fs.py", line 53, in fix_locations share_files(srcdir, dstdir, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files share_files(fpath1, fpath2, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files share_files(fpath1, fpath2, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files share_files(fpath1, fpath2, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 149, in share_files fromlines = fp1.readlines() File "/usr/lib/python3.10/codecs.py", line 322, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf6 in position 75: invalid start byte make[1]: *** [debian/rules:46: override_dh_python3] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:15: binary-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2 There is already logic to skip this diff for .so files, so the same should be done for .a files. [1] https://launchpadlibrarian.net/624822201/buildlog_ubuntu-kinetic- arm64.numpy_1%3A1.21.5-1build2_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1990562/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990293] Re: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 )
Hello , do you think this bug will be corrected soon ? or i change parent directory name of mountpoints ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1990293 Title: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 ) Status in glib2.0 package in Ubuntu: New Status in glib2.0 source package in Jammy: New Bug description: Hi , when i delete a file where is in another partition than " / " or mounted in /media/ , i obtain the message in title. how can i use trash again please ? iznobe@iznobe-PC:~$ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/nvme0n1p2 during installation UUID=eb18366b-2ac9-4a7e-8f93-ba2caa30e90e / ext4 noatime,errors=remount-ro 0 1 # /boot/efi was on /dev/nvme0n1p1 during installation UUID=C071-9050/boot/efi vfatdefaults0 0 # swap was on /dev/sdc3 during installation UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456 noneswap sw,pri=10 0 # partition de données separée comune aux OS linux UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257 /datas ext4 defaults0 0 LABEL=WD8 /Vidéos/WD8 ext4 defaults0 0 #/dev/disk/by-label/WD8PRO2 /media/WD8PRO2 ext4 defaults0 0 LABEL=WD8PRO2 /Vidéos/WD8PRO2 ext4defaults 0 0 LABEL=WD8PRO1 /media/WD8PRO1 ext4 defaults0 0 LABEL=Seagate_4T /media/Seagate_4T ext4 defaults,noauto 0 0 trash is working for filesysteme mounted on /media/WD8PRO1 but not in FS mounted on /Vidéos/WD8PRO2 and /Vidéos/WD8 using ubuntu 22.04.1 LTS . Exactly same file systeme mounted on same directory , with same trash directory is working fine on ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1990293/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990525] Re: E: Internal Error, AutoRemover broke stuff
Sorry, "E: External solver failed with: I am too dumb, i can just dump!" is the expected output, this means it created the file. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1990525 Title: E: Internal Error, AutoRemover broke stuff Status in apt package in Ubuntu: New Bug description: I'm trying to run a dist-upgrade, which should be simple enough, but it keeps failing at: Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done Hmm, seems like the AutoRemover destroyed something which really shouldn't happen. Please file a bug report against apt. The following information may help to resolve the situation: The following packages have unmet dependencies: libopenblas0-pthread : Depends: libgfortran5 (>= 8) but it is not going to be installed E: Internal Error, AutoRemover broke stuff libgfortran5 IS installed. Package: libgfortran5 Version: 12.1.0-2ubuntu1~22.04 Priority: optional Section: libs Source: gcc-12 Origin: Ubuntu Maintainer: Ubuntu Core developers Original-Maintainer: Debian GCC Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 3,059 kB Depends: gcc-12-base (= 12.1.0-2ubuntu1~22.04), libc6 (>= 2.34), libgcc-s1 (>= 4.3), libquadmath0 (>= 4.6) Breaks: gcc-4.3 (<< 4.3.6-1), gcc-4.4 (<< 4.4.6-4), gcc-4.5 (<< 4.5.3-2) Homepage: http://gcc.gnu.org/ Task: kubuntu-desktop, kubuntu-full, xubuntu-desktop, lubuntu-desktop, ubuntustudio-desktop, ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop, ubuntu-budgie-desktop, ubuntu-budgie-desktop-raspi Download-Size: 882 kB APT-Manual-Installed: no APT-Sources: http://nova.clouds.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages Apt says to report a bug against Apt, so here I am... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.4.7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Sep 22 13:09:38 2022 Ec2AMI: ami-0008be8e Ec2AMIManifest: FIXME Ec2AvailabilityZone: None Ec2InstanceType: vps2020-starter-1-2-20 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: Upgraded to jammy on 2022-08-15 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1990525/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990187] Re: systemd-resolved recommends libnss-resolve in kinetic, pulls it into minimal system where it was explicitly excluded before
This bug was fixed in the package systemd - 251.4-1ubuntu6 --- systemd (251.4-1ubuntu6) kinetic; urgency=medium * test: deny-list TEST-36-NUMAPOLICY on ppc64el (LP: #1989969) File: debian/patches/lp1989969-test-deny-list-TEST-36-NUMAPOLICY-on-ppc64el.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0f61b31fbeb57cf7e47a5f0922fd2ff47b81caa7 * debian/control: drop systemd-resolved Recommends: (LP: #1990187) libnss-resolve was previously explicitly excluded from ubuntu-minimal, and this Recommends: reverses that change. While here, drop libnss-myhostname too, because it is in universe and there is no real need for systemd-resolved to Recommends: it. File: debian/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=88c134fac13b738efdcc657e160350c061d0a018 * debian/control: set Priority: important on systemd-resolved (LP: #1990278) Since this package used to be a part of the systemd binary package, systemd-resolved would be installed by debootstrap by default. Retain this previous behavior by setting Priority: important on systemd-resolved. File: debian/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1d9ca06dfe8351ed4d03073fbafa5e2212fe4fcb systemd (251.4-1ubuntu5) kinetic; urgency=medium * enable building systemd-boot for riscv64 (LP: #1989457) -- Nick Rosbrook Tue, 20 Sep 2022 11:19:06 -0400 ** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1990187 Title: systemd-resolved recommends libnss-resolve in kinetic, pulls it into minimal system where it was explicitly excluded before Status in systemd package in Ubuntu: Fix Released Bug description: In kinetic, systemd-resolved now Recommends: libnss-resolve, pulling it into the ubuntu-minimal seed. In the past we briefly had libnss-resolve seeded (between xenial and bionic LTSes but not in any LTS) but it was removed because: - it was redundant; /etc/resolv.conf was consistent and correct. - its presence could mask wrong DNS configuration resulting in difficult-to-debug differences in behavior between applications that did use nss_resolved via /etc/nsswitch.conf and those that did not (examples: i386 binaries that could not use nss_resolved because it was not installed; statically-linked go implementations that parsed /etc/resolve.conf directly and did not load NSS modules) This new recommends was noticed specifically because of some broken kinetic container images where /etc/resolv.conf was broken (empty) and *some* applications still worked via nss but others failed by trying to use the DNS protocol directly. (I.e.: 2nd point above) I believe systemd-resolved should drop its recommends on libnss- resolve for Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1989969] Re: autopkgtest TEST-36-NUMAPOLICY failure on ppc64el
This bug was fixed in the package systemd - 251.4-1ubuntu6 --- systemd (251.4-1ubuntu6) kinetic; urgency=medium * test: deny-list TEST-36-NUMAPOLICY on ppc64el (LP: #1989969) File: debian/patches/lp1989969-test-deny-list-TEST-36-NUMAPOLICY-on-ppc64el.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0f61b31fbeb57cf7e47a5f0922fd2ff47b81caa7 * debian/control: drop systemd-resolved Recommends: (LP: #1990187) libnss-resolve was previously explicitly excluded from ubuntu-minimal, and this Recommends: reverses that change. While here, drop libnss-myhostname too, because it is in universe and there is no real need for systemd-resolved to Recommends: it. File: debian/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=88c134fac13b738efdcc657e160350c061d0a018 * debian/control: set Priority: important on systemd-resolved (LP: #1990278) Since this package used to be a part of the systemd binary package, systemd-resolved would be installed by debootstrap by default. Retain this previous behavior by setting Priority: important on systemd-resolved. File: debian/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1d9ca06dfe8351ed4d03073fbafa5e2212fe4fcb systemd (251.4-1ubuntu5) kinetic; urgency=medium * enable building systemd-boot for riscv64 (LP: #1989457) -- Nick Rosbrook Tue, 20 Sep 2022 11:19:06 -0400 ** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1989969 Title: autopkgtest TEST-36-NUMAPOLICY failure on ppc64el Status in systemd package in Ubuntu: Fix Released Bug description: In Kinetic, TEST-36-NUMAPOLICY from upstream-2 fails very frequently on ppc64el. See for example: https://autopkgtest.ubuntu.com/results/autopkgtest- kinetic/kinetic/ppc64el/s/systemd/20220908_195425_da51e@/log.gz, and the full kinetic ppc64el history: https://autopkgtest.ubuntu.com/packages/systemd/kinetic/ppc64el. It has passed on very few occasions. I have tried to debug this locally but have gotten very little useful information (i.e. not enough to open an upstream bug). For now it is probably best to denylist this test on ppc64el. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1989969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990278] Re: systemd-resolved not included in Ubuntu bootstrap
This bug was fixed in the package systemd - 251.4-1ubuntu6 --- systemd (251.4-1ubuntu6) kinetic; urgency=medium * test: deny-list TEST-36-NUMAPOLICY on ppc64el (LP: #1989969) File: debian/patches/lp1989969-test-deny-list-TEST-36-NUMAPOLICY-on-ppc64el.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0f61b31fbeb57cf7e47a5f0922fd2ff47b81caa7 * debian/control: drop systemd-resolved Recommends: (LP: #1990187) libnss-resolve was previously explicitly excluded from ubuntu-minimal, and this Recommends: reverses that change. While here, drop libnss-myhostname too, because it is in universe and there is no real need for systemd-resolved to Recommends: it. File: debian/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=88c134fac13b738efdcc657e160350c061d0a018 * debian/control: set Priority: important on systemd-resolved (LP: #1990278) Since this package used to be a part of the systemd binary package, systemd-resolved would be installed by debootstrap by default. Retain this previous behavior by setting Priority: important on systemd-resolved. File: debian/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1d9ca06dfe8351ed4d03073fbafa5e2212fe4fcb systemd (251.4-1ubuntu5) kinetic; urgency=medium * enable building systemd-boot for riscv64 (LP: #1989457) -- Nick Rosbrook Tue, 20 Sep 2022 11:19:06 -0400 ** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1990278 Title: systemd-resolved not included in Ubuntu bootstrap Status in systemd package in Ubuntu: Fix Released Bug description: By default, i.e. with no --variant specified, debootstrap will only pull in packages with Priority: required or important. Before the systemd-resolved package split, resolved would be included because it was shipped with the systemd binary package, which is Priority: important. Currently there is no Priority: set on systemd-resolved, so it is not included with the deafult Ubuntu bootstrap. The systemd-resolved package should have Priority: important to fix this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
@jeremyszu (os369510) Did you see #90, it seems your patch would cause
boot failures on older system unable to handle this memory range.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Confirmed
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c” but I use the
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
Thus it should not impact them.
* There is a “#if defined(__x86_64__)” which intent to limit the >
32bits code in i386 system and also
```
#if defined (__code_model_large__)
-#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
+#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
#else
#define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
#endif
```
If everything works as expected, then i386 should working good.
If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
4GB memory region and never be able to access.
[Other Info]
* Upstream grub2 bug #61058
https://savannah.gnu.org/bugs/index.php?61058
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320
* Test grubx64.efi:
https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320
* Test source code: https://github.com/os369510/grub2/tree/lp1842320
* If you built the package, then test grubx64.efi is under
“obj/monolithic/grub-efi-amd64/grubx64.efi”, in my case:
[Touch-packages] [Bug 1980494] Re: krb5-multidev is not multi-arch installable due to differences in /usr/bin/krb5-config.mit
I think the right fix here is to strip the output of dpkg-buildflags
from the config script output. We've definitely had problems before
where leaking dpkg-buildflags into other build tools made it effectively
impossible for dependent packages to work around toolchain issues.
** Changed in: krb5 (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1980494
Title:
krb5-multidev is not multi-arch installable due to differences in
/usr/bin/krb5-config.mit
Status in krb5 package in Ubuntu:
New
Bug description:
I am trying to build wine in a wow64 configuration and need to install
the i386 and amd64 version of the krb5-multidev package on Ubuntu
22.04. The two version are not co-installable due to differences in
the /usr/bin/krb5-config.mit file between the two version of the
package.
The diff between the two files is:
--- krb5-config.mit-i386 2022-06-18 21:32:44.034889873 -0400
+++ krb5-config.mit-amd64 2022-06-18 21:31:37.302149522 -0400
@@ -40,7 +40,7 @@
libdir=/usr/lib/${tripple}/mit-krb5
CC_LINK='$(CC) $(PROG_LIBPATH) $(PROG_RPATH_FLAGS) $(CFLAGS) $(LDFLAGS)'
KDB5_DB_LIB=
-LDFLAGS='-Wl,-Bsymbolic-functions -Wl,-z,relro'
+LDFLAGS='-Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -flto=auto
-Wl,-z,relro'
RPATH_FLAG=''
PROG_RPATH_FLAGS=''
PTHREAD_CFLAGS='-pthread'
The krb5-multidev package is co-installable on Debian. It appears that
Ubuntu uses different default linker flags for the i386 and amd64
platforms and Debian does not.
This bug is related to
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1970979
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1980494/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1980494] Re: krb5-multidev is not multi-arch installable due to differences in /usr/bin/krb5-config.mit
** Tags removed: foundations-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1980494
Title:
krb5-multidev is not multi-arch installable due to differences in
/usr/bin/krb5-config.mit
Status in krb5 package in Ubuntu:
New
Bug description:
I am trying to build wine in a wow64 configuration and need to install
the i386 and amd64 version of the krb5-multidev package on Ubuntu
22.04. The two version are not co-installable due to differences in
the /usr/bin/krb5-config.mit file between the two version of the
package.
The diff between the two files is:
--- krb5-config.mit-i386 2022-06-18 21:32:44.034889873 -0400
+++ krb5-config.mit-amd64 2022-06-18 21:31:37.302149522 -0400
@@ -40,7 +40,7 @@
libdir=/usr/lib/${tripple}/mit-krb5
CC_LINK='$(CC) $(PROG_LIBPATH) $(PROG_RPATH_FLAGS) $(CFLAGS) $(LDFLAGS)'
KDB5_DB_LIB=
-LDFLAGS='-Wl,-Bsymbolic-functions -Wl,-z,relro'
+LDFLAGS='-Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -flto=auto
-Wl,-z,relro'
RPATH_FLAG=''
PROG_RPATH_FLAGS=''
PTHREAD_CFLAGS='-pthread'
The krb5-multidev package is co-installable on Debian. It appears that
Ubuntu uses different default linker flags for the i386 and amd64
platforms and Debian does not.
This bug is related to
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1970979
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1980494/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1988819] Re: When apt keeps back packages due to phased updates, it should say so
I want to say I agree with avih and had the same idea but I had no chance to update the bug yet. Currently sorting out actual upgrade failures that might be regressions from the new phasing though. It remains to be seen if we can do this safely. We need to add a new flag "PhasedKeep" or something to the depcache and then make sure to always clear this if we do not keep it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1988819 Title: When apt keeps back packages due to phased updates, it should say so Status in apt package in Ubuntu: Confirmed Bug description: After phased updates have been introduced, it may happen that apt upgrade shows packages as upgradable but ends up not upgrading them. In this case the packages are indicated as being "kept back". Unfortunately, the feedback provided about this to the user is not very informative. The user sees the packages being kept back and thinks something is going wrong on the system. When packages are kept back because of phased updates, apt should say so e.g., it should say that the upgrade is delayed. Incidentally note that aptitude does not respect phased updates. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.4.7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Sep 6 10:05:14 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (933 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: apt UpgradeStatus: Upgraded to jammy on 2022-06-03 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988819/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1988819] Re: When apt keeps back packages due to phased updates, it should say so
** Tags removed: foundations-triage-discuss ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1988819 Title: When apt keeps back packages due to phased updates, it should say so Status in apt package in Ubuntu: Confirmed Bug description: After phased updates have been introduced, it may happen that apt upgrade shows packages as upgradable but ends up not upgrading them. In this case the packages are indicated as being "kept back". Unfortunately, the feedback provided about this to the user is not very informative. The user sees the packages being kept back and thinks something is going wrong on the system. When packages are kept back because of phased updates, apt should say so e.g., it should say that the upgrade is delayed. Incidentally note that aptitude does not respect phased updates. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.4.7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Sep 6 10:05:14 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (933 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: apt UpgradeStatus: Upgraded to jammy on 2022-06-03 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988819/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990525] Re: E: Internal Error, AutoRemover broke stuff
# APT_EDSP_DUMP_FILENAME=/tmp/lp1990525.edsp apt dist-upgrade --solver dump Reading package lists... Done Building dependency tree... Done Reading state information... Done Execute external solver... Error! The solver encountered an error of type: ERR_JUST_DUMPING The following information might help you to understand what is wrong: I am too dumb, i can just dump! Please use one of my friends instead! E: External solver failed with: I am too dumb, i can just dump! Result is the same with the -o Debugs added (the files are identical). # apt -o APT::Get::Phase-Policy=1 dist-upgrade This doesn't complain anymore, but it does hold packages back. Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages have been kept back: libpython3-dev libpython3-stdlib python3 python3-dev python3-distutils python3-gdbm python3-lib2to3 python3-minimal python3-tk 0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded. ** Attachment added: "lp1990525.tar.xz" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1990525/+attachment/5618094/+files/lp1990525.tar.xz ** Changed in: apt (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1990525 Title: E: Internal Error, AutoRemover broke stuff Status in apt package in Ubuntu: New Bug description: I'm trying to run a dist-upgrade, which should be simple enough, but it keeps failing at: Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done Hmm, seems like the AutoRemover destroyed something which really shouldn't happen. Please file a bug report against apt. The following information may help to resolve the situation: The following packages have unmet dependencies: libopenblas0-pthread : Depends: libgfortran5 (>= 8) but it is not going to be installed E: Internal Error, AutoRemover broke stuff libgfortran5 IS installed. Package: libgfortran5 Version: 12.1.0-2ubuntu1~22.04 Priority: optional Section: libs Source: gcc-12 Origin: Ubuntu Maintainer: Ubuntu Core developers Original-Maintainer: Debian GCC Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 3,059 kB Depends: gcc-12-base (= 12.1.0-2ubuntu1~22.04), libc6 (>= 2.34), libgcc-s1 (>= 4.3), libquadmath0 (>= 4.6) Breaks: gcc-4.3 (<< 4.3.6-1), gcc-4.4 (<< 4.4.6-4), gcc-4.5 (<< 4.5.3-2) Homepage: http://gcc.gnu.org/ Task: kubuntu-desktop, kubuntu-full, xubuntu-desktop, lubuntu-desktop, ubuntustudio-desktop, ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop, ubuntu-budgie-desktop, ubuntu-budgie-desktop-raspi Download-Size: 882 kB APT-Manual-Installed: no APT-Sources: http://nova.clouds.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages Apt says to report a bug against Apt, so here I am... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.4.7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Sep 22 13:09:38 2022 Ec2AMI: ami-0008be8e Ec2AMIManifest: FIXME Ec2AvailabilityZone: None Ec2InstanceType: vps2020-starter-1-2-20 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: Upgraded to jammy on 2022-08-15 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1990525/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990552] Re: update apport's package installation failure hook to gather a new file
** Description changed: juliank indicates we should gather /var/lib/dpkg/status when we are reporting apport-package bugs and that it should also be collected for ubuntu-release-upgrader bugs and something else. So maybe it should actually go in the ubuntu general hook. + + This came about because of bug 1990552 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1990552 Title: update apport's package installation failure hook to gather a new file Status in apport package in Ubuntu: New Bug description: juliank indicates we should gather /var/lib/dpkg/status when we are reporting apport-package bugs and that it should also be collected for ubuntu-release-upgrader bugs and something else. So maybe it should actually go in the ubuntu general hook. This came about because of bug 1990552 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1990552/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990552] [NEW] update apport's package installation failure hook to gather a new file
Public bug reported: juliank indicates we should gather /var/lib/dpkg/status when we are reporting apport-package bugs and that it should also be collected for ubuntu-release-upgrader bugs and something else. So maybe it should actually go in the ubuntu general hook. This came about because of bug 1990552 ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1990552 Title: update apport's package installation failure hook to gather a new file Status in apport package in Ubuntu: New Bug description: juliank indicates we should gather /var/lib/dpkg/status when we are reporting apport-package bugs and that it should also be collected for ubuntu-release-upgrader bugs and something else. So maybe it should actually go in the ubuntu general hook. This came about because of bug 1990552 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1990552/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990546] Re: apt.auth uses apt-key
Sorry wrong package ** Package changed: software-properties (Ubuntu) => python-apt (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1990546 Title: apt.auth uses apt-key Status in python-apt package in Ubuntu: Triaged Bug description: apt.auth needs to be deprecated or ported to work with the new regime. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1990546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990546] [NEW] apt.auth uses apt-key
Public bug reported: apt.auth needs to be deprecated or ported to work with the new regime. ** Affects: python-apt (Ubuntu) Importance: High Status: Triaged ** Tags: foundations-todo ** Tags added: foundations-todo ** Changed in: software-properties (Ubuntu) Importance: Undecided => High ** Changed in: software-properties (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1990546 Title: apt.auth uses apt-key Status in python-apt package in Ubuntu: Triaged Bug description: apt.auth needs to be deprecated or ported to work with the new regime. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1990546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990429] Re: software-properties uses deprecated apt-key
** Changed in: software-properties (Ubuntu) Importance: Undecided => High ** Changed in: software-properties (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1990429 Title: software-properties uses deprecated apt-key Status in software-properties package in Ubuntu: Triaged Bug description: software-properties still references apt-key, which is deprecated upstream (https://blog.jak-linux.org/2021/06/20/migrating-away-apt- key/): $ grep -r apt-key tests/test_dbus.py:# test apt-key update tests/test_aptauth.py:"/usr/bin/apt-key", tests/test_aptauth.py:stderr="Warning: apt-key is deprecated.\n", debian/changelog: - thus, add-apt-key for PPAs observes https_proxy for key retrieval debian/changelog: - stop using apt-key for installing keys debian/changelog: * Port AptAuth.py from gpg command parsing to apt-key command debian/changelog:- fix incorrect call call to apt-key for the fingerprint, thanks softwareproperties/SoftwareProperties.py:# apt-key stuff softwareproperties/SoftwareProperties.py:""" Run apt-key update """ softwareproperties/AptAuth.py:cmd = ["/usr/bin/apt-key", "--quiet", "adv", "--with-colons", "--batch", "--fixed-list-mode", "--list-keys"] softwareproperties/AptAuth.py:cmd = ["/usr/bin/apt-key", "--quiet", "--fakeroot", "add", filename] softwareproperties/AptAuth.py:cmd = ["/usr/bin/apt-key", "--quiet", "--fakeroot", "update"] softwareproperties/AptAuth.py:cmd = ["/usr/bin/apt-key", "--quiet", "--fakeroot", "rm", key] $ apt-key will eventually go away, and software-properties needs to adapt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1990429/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1946192] Re: "Press Ctrl+C to cancel all filesystem checks in process" on every boot
Addition: This check is not made in the partition mounted as root. I can see the following in journalctl -b: Condition check resulted in File System Check on Root Device being skipped It is made in all other mounted partitions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1946192 Title: "Press Ctrl+C to cancel all filesystem checks in process" on every boot Status in systemd package in Ubuntu: Confirmed Bug description: I installed Kubuntu 20.04 on Latitude 5591 laptop using flash drive. Installation run without any issues but now on every boot I notice a message "Press Ctrl+C to cancel all filesystem checks in process" on the Plymouth screen with Kubuntu logo. It flashes quickly and disappears. I've got fast NVMe drive so I cannot say for sure whether it runs any checks or not. I booted from LiveCD and performed fsck checks of all my partitions: fsck.vfat /dev/nvme0n1p1 (EFI partition) fsck.vfat /dev/nvme0n1p2 (Dell service partition, not mounted) e2fsck -f /dev/nvme0n1p3 (Root partition) e2fsck -f /dev/nvme0n1p5 (Home partition) These checks showed no problems. I changed mount counter to set periodic checks: sudo tune2fs -c 29 /dev/nvme0n1p3 sudo tune2fs -c 30 /dev/nvme0n1p5 But despite these settings this message still appears on every boot. Operating System: Kubuntu 20.04.3 Kernel Version: 5.4.0-88-generic OS Type: 64-bit Processors: 12 × Intel® Core™ i7-8850H CPU @ 2.60GHz Memory: 15,4 GiB of RAM --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: KDE DefaultPlymouth: /usr/share/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-09 (57 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:568c Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5591 Package: plymouth 0.9.4git20200323-0ubuntu6.2 PackageArchitecture: amd64 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Tags: focal TextPlymouth: /usr/share/plymouth/themes/kubuntu-text/kubuntu-text.plymouth Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/10/2021 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0DVVG1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd06/10/2021:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0DVVG1:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5591 dmi.product.sku: 0819 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1946192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1946192] Re: "Press Ctrl+C to cancel all filesystem checks in process" on every boot
I have this bug after updrading from focal to jammy. Now in every boot I can see for several seconds the message "Press Ctrl+C to cancel all filesystem checks in process". With "journalctl -b", I follow all the booting procedure and I can see several Starting File System Check on /dev/disk/by-uuid/... messages (one for each partition used by my system) and several lines below the corresponding Finished File System Check on /dev/disk/by-uuid/... No error in the checks are reported. If I boot with a live USB and perform e2fsck (or even e2fsck -f) in every partition, no error is reported whatsoever. I have seen this kind of behaviour for other people in some forum (easy to find googling "checking filesystems on every boot" or something of the kind). Not sure, but it looks like it appears in people upgrading from a previous Ubuntu version. It is not a serious bug but it is quite annoying delaying the boot process. Supposedly, filesystems should only be checked regularly from time to time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1946192 Title: "Press Ctrl+C to cancel all filesystem checks in process" on every boot Status in systemd package in Ubuntu: Confirmed Bug description: I installed Kubuntu 20.04 on Latitude 5591 laptop using flash drive. Installation run without any issues but now on every boot I notice a message "Press Ctrl+C to cancel all filesystem checks in process" on the Plymouth screen with Kubuntu logo. It flashes quickly and disappears. I've got fast NVMe drive so I cannot say for sure whether it runs any checks or not. I booted from LiveCD and performed fsck checks of all my partitions: fsck.vfat /dev/nvme0n1p1 (EFI partition) fsck.vfat /dev/nvme0n1p2 (Dell service partition, not mounted) e2fsck -f /dev/nvme0n1p3 (Root partition) e2fsck -f /dev/nvme0n1p5 (Home partition) These checks showed no problems. I changed mount counter to set periodic checks: sudo tune2fs -c 29 /dev/nvme0n1p3 sudo tune2fs -c 30 /dev/nvme0n1p5 But despite these settings this message still appears on every boot. Operating System: Kubuntu 20.04.3 Kernel Version: 5.4.0-88-generic OS Type: 64-bit Processors: 12 × Intel® Core™ i7-8850H CPU @ 2.60GHz Memory: 15,4 GiB of RAM --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: KDE DefaultPlymouth: /usr/share/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-09 (57 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:568c Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5591 Package: plymouth 0.9.4git20200323-0ubuntu6.2 PackageArchitecture: amd64 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Tags: focal TextPlymouth: /usr/share/plymouth/themes/kubuntu-text/kubuntu-text.plymouth Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/10/2021 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0DVVG1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd06/10/2021:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0DVVG1:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5591 dmi.product.sku: 0819 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1946192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990542] [NEW] initrd starts dhclient on interfaces that are not supposed to get an IP address
Public bug reported: After trying several setups, I think this is a bug. If not - I can't find how to fix things. Setup: Ubuntu 22.04, with ubuntu-minimal installed (which depends on isc-dhcp-client). A network with a bridge interface. This can be anything, even an old /etc/network/interfaces file will do. For simplicity, the following netplan setup is used: network: version: 2 ethernets: enp4s0: wakeonlan: true dhcp4: no dhcp6: no bridges: br0: interfaces: [enp4s0] dhcp4: yes dhcp6: yes parameters: stp: false forward-delay: 0 What happens: Starting this machine will, during initrd phase, make dhclient fetch an IP address for enp4s0. Then netplan takes over and fetches an address for br0. If both enp4s0 and br0 have the same IP address from the DHCP-server, the machine will not be reachable. What should happen: enp4s0 should not get an IP address, as the netplan-configuration clearly says. A workaround is to remove isc-dhcp-client (which, in turn, removes meta- package ubuntu-minimal) and run update-initramfs -k all -u; afterwards, the dhclient in initrd is (obviously) not there anymore. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1990542 Title: initrd starts dhclient on interfaces that are not supposed to get an IP address Status in initramfs-tools package in Ubuntu: New Bug description: After trying several setups, I think this is a bug. If not - I can't find how to fix things. Setup: Ubuntu 22.04, with ubuntu-minimal installed (which depends on isc-dhcp-client). A network with a bridge interface. This can be anything, even an old /etc/network/interfaces file will do. For simplicity, the following netplan setup is used: network: version: 2 ethernets: enp4s0: wakeonlan: true dhcp4: no dhcp6: no bridges: br0: interfaces: [enp4s0] dhcp4: yes dhcp6: yes parameters: stp: false forward-delay: 0 What happens: Starting this machine will, during initrd phase, make dhclient fetch an IP address for enp4s0. Then netplan takes over and fetches an address for br0. If both enp4s0 and br0 have the same IP address from the DHCP-server, the machine will not be reachable. What should happen: enp4s0 should not get an IP address, as the netplan-configuration clearly says. A workaround is to remove isc-dhcp-client (which, in turn, removes meta-package ubuntu-minimal) and run update-initramfs -k all -u; afterwards, the dhclient in initrd is (obviously) not there anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1990542/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990525] Re: E: Internal Error, AutoRemover broke stuff
Thank you for your bug report. Please run APT_EDSP_DUMP_FILENAME=/tmp/lp1990525.edsp apt dist-upgrade --solver dump and attach /tmp/lp1990525.edsp to the bug (if that works). If that does not work, please pass -o Debug::pkgDepCache::Marker=1 -o Debug::pkgDepCache::AutoInstall=1 -o Debug::pkgProblemResolver=1 to the dist-upgrade and attach the output, and optimally also a tarball of /etc/apt /var/lib/apt/lists /var/lib/dpkg/status, e.g. tar cJf lp1990525.tar.xz /etc/apt /var/lib/apt/lists /var/lib/dpkg/status and attach the resulting tarball ` lp1990525.tar.xz`. Also my hunch: Try passing -o APT::Get::Phase-Policy=1 to dist-upgrade and see if that works. This might be a regression from the new phaser (sigh). ** Changed in: apt (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1990525 Title: E: Internal Error, AutoRemover broke stuff Status in apt package in Ubuntu: Incomplete Bug description: I'm trying to run a dist-upgrade, which should be simple enough, but it keeps failing at: Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done Hmm, seems like the AutoRemover destroyed something which really shouldn't happen. Please file a bug report against apt. The following information may help to resolve the situation: The following packages have unmet dependencies: libopenblas0-pthread : Depends: libgfortran5 (>= 8) but it is not going to be installed E: Internal Error, AutoRemover broke stuff libgfortran5 IS installed. Package: libgfortran5 Version: 12.1.0-2ubuntu1~22.04 Priority: optional Section: libs Source: gcc-12 Origin: Ubuntu Maintainer: Ubuntu Core developers Original-Maintainer: Debian GCC Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 3,059 kB Depends: gcc-12-base (= 12.1.0-2ubuntu1~22.04), libc6 (>= 2.34), libgcc-s1 (>= 4.3), libquadmath0 (>= 4.6) Breaks: gcc-4.3 (<< 4.3.6-1), gcc-4.4 (<< 4.4.6-4), gcc-4.5 (<< 4.5.3-2) Homepage: http://gcc.gnu.org/ Task: kubuntu-desktop, kubuntu-full, xubuntu-desktop, lubuntu-desktop, ubuntustudio-desktop, ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop, ubuntu-budgie-desktop, ubuntu-budgie-desktop-raspi Download-Size: 882 kB APT-Manual-Installed: no APT-Sources: http://nova.clouds.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages Apt says to report a bug against Apt, so here I am... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.4.7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Sep 22 13:09:38 2022 Ec2AMI: ami-0008be8e Ec2AMIManifest: FIXME Ec2AvailabilityZone: None Ec2InstanceType: vps2020-starter-1-2-20 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: Upgraded to jammy on 2022-08-15 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1990525/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990534] [NEW] package linux-image-5.15.0-48-generic 5.15.0-48.54~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127
Public bug reported: Issue appeared and wanted to send info automatically. No clue what else you need from me. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Sep 22 09:06:40 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 InstallationDate: Installed on 2020-07-24 (790 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package linux-image-5.15.0-48-generic 5.15.0-48.54~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 UpgradeStatus: Upgraded to focal on 2022-09-09 (12 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1990534 Title: package linux-image-5.15.0-48-generic 5.15.0-48.54~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 Status in initramfs-tools package in Ubuntu: New Bug description: Issue appeared and wanted to send info automatically. No clue what else you need from me. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Sep 22 09:06:40 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 InstallationDate: Installed on 2020-07-24 (790 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package linux-image-5.15.0-48-generic 5.15.0-48.54~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 UpgradeStatus: Upgraded to focal on 2022-09-09 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1990534/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990526] Re: [FFe] UDI snap no longer strictly needed for WSL OOBE
** Patch removed: "ubuntu wsl seed diff" https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1990526/+attachment/5618055/+files/ubuntu-seeds.diff ** Patch added: "ubuntu wsl seed diff" https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1990526/+attachment/5618064/+files/0001-WSL-Replaces-UDI-by-Subiquity-snap-LP-1990526.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1990526 Title: [FFe] UDI snap no longer strictly needed for WSL OOBE Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu Desktop Installer (UDI, for short) package implementing the WSL OOBE has been ported to Windows and the WSL application is able to launch the OOBE running as a native Win32 application, instead of relying on WSLg to display the OOBE. That implies in the possibility of replacing UDI by Subiquity snap, which results in a smaller rootfs image (besides an enhanced experience due native rendering on graphics - instead of depending on RDP as it is currently with the OOBE running inside Ubuntu). Fixing this would require: - replace UDI by Subiquity snaps in the WSL seed; - updating the wsl-setup package to the latest upstream (which is able to mount and launch Subiquity from its snap) LP: #1990426 . Following the approach above won't have effects outside of WSL. Kinetic being not an LTS is a good release to receive the fix for this first, as it affects a small audience of Ubuntu WSL community, giving us time to learn from them before backporting this to Jammy early next cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1990526/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738403] Re: iptables-save duplicates all rules related to Linux bridges
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: iptables (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1738403 Title: iptables-save duplicates all rules related to Linux bridges Status in iptables package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 iptables 1.6.1-2ubuntu1 Before "iptables-save > /etc/iptables/rules.v4" --- # cat iptables/rules.v4 | grep virbr0 | sort | uniq -c 14 -A FORWARD -d 192.168.122.0/24 -o virbr0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT 14 -A FORWARD -i virbr0 -j REJECT --reject-with icmp-port-unreachable 14 -A FORWARD -i virbr0 -o virbr0 -j ACCEPT 14 -A FORWARD -o virbr0 -j REJECT --reject-with icmp-port-unreachable 14 -A FORWARD -s 192.168.122.0/24 -i virbr0 -j ACCEPT 14 -A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT 14 -A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT 14 -A INPUT -i virbr0 -p udp -m udp --dport 53 -j ACCEPT 14 -A INPUT -i virbr0 -p udp -m udp --dport 67 -j ACCEPT 14 -A OUTPUT -o virbr0 -p udp -m udp --dport 68 -j ACCEPT 33 -A POSTROUTING -o virbr0 -p udp -m udp --dport 68 -j CHECKSUM --checksum-fill 1 -A ufw-user-input -i virbr0 -j ACCEPT 1 -A ufw-user-output -o virbr0 -j ACCEPT After "iptables-save > /etc/iptables/rules.v4" -- # cat iptables/rules.v4 | grep virbr0 | sort | uniq -c 15 -A FORWARD -d 192.168.122.0/24 -o virbr0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT 15 -A FORWARD -i virbr0 -j REJECT --reject-with icmp-port-unreachable 15 -A FORWARD -i virbr0 -o virbr0 -j ACCEPT 15 -A FORWARD -o virbr0 -j REJECT --reject-with icmp-port-unreachable 15 -A FORWARD -s 192.168.122.0/24 -i virbr0 -j ACCEPT 15 -A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT 15 -A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT 15 -A INPUT -i virbr0 -p udp -m udp --dport 53 -j ACCEPT 15 -A INPUT -i virbr0 -p udp -m udp --dport 67 -j ACCEPT 15 -A OUTPUT -o virbr0 -p udp -m udp --dport 68 -j ACCEPT 34 -A POSTROUTING -o virbr0 -p udp -m udp --dport 68 -j CHECKSUM --checksum-fill 1 -A ufw-user-input -i virbr0 -j ACCEPT 1 -A ufw-user-output -o virbr0 -j ACCEPT It looks like iptables-save is confused by virbrn entries and duplicates them each time it is run. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1738403/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990526] Re: [FFe] UDI snap no longer strictly needed for WSL OOBE
** Patch added: "ubuntu wsl seed diff" https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1990526/+attachment/5618055/+files/ubuntu-seeds.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1990526 Title: [FFe] UDI snap no longer strictly needed for WSL OOBE Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu Desktop Installer (UDI, for short) package implementing the WSL OOBE has been ported to Windows and the WSL application is able to launch the OOBE running as a native Win32 application, instead of relying on WSLg to display the OOBE. That implies in the possibility of replacing UDI by Subiquity snap, which results in a smaller rootfs image (besides an enhanced experience due native rendering on graphics - instead of depending on RDP as it is currently with the OOBE running inside Ubuntu). Fixing this would require: - replace UDI by Subiquity snaps in the WSL seed; - updating the wsl-setup package to the latest upstream (which is able to mount and launch Subiquity from its snap) LP: #1990426 . Following the approach above won't have effects outside of WSL. Kinetic being not an LTS is a good release to receive the fix for this first, as it affects a small audience of Ubuntu WSL community, giving us time to learn from them before backporting this to Jammy early next cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1990526/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990526] Re: [FFe] UDI snap no longer strictly needed for WSL OOBE
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1990526 Title: [FFe] UDI snap no longer strictly needed for WSL OOBE Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu Desktop Installer (UDI, for short) package implementing the WSL OOBE has been ported to Windows and the WSL application is able to launch the OOBE running as a native Win32 application, instead of relying on WSLg to display the OOBE. That implies in the possibility of replacing UDI by Subiquity snap, which results in a smaller rootfs image (besides an enhanced experience due native rendering on graphics - instead of depending on RDP as it is currently with the OOBE running inside Ubuntu). Fixing this would require: - replace UDI by Subiquity snaps in the WSL seed; - updating the wsl-setup package to the latest upstream (which is able to mount and launch Subiquity from its snap) LP: #1990426 . Following the approach above won't have effects outside of WSL. Kinetic being not an LTS is a good release to receive the fix for this first, as it affects a small audience of Ubuntu WSL community, giving us time to learn from them before backporting this to Jammy early next cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1990526/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990526] [NEW] [FFe] UDI snap no longer strictly needed for WSL OOBE
Public bug reported: Ubuntu Desktop Installer (UDI, for short) package implementing the WSL OOBE has been ported to Windows and the WSL application is able to launch the OOBE running as a native Win32 application, instead of relying on WSLg to display the OOBE. That implies in the possibility of replacing UDI by Subiquity snap, which results in a smaller rootfs image (besides an enhanced experience due native rendering on graphics - instead of depending on RDP as it is currently with the OOBE running inside Ubuntu). Fixing this would require: - replace UDI by Subiquity snaps in the WSL seed; - updating the wsl-setup package to the latest upstream (which is able to mount and launch Subiquity from its snap) LP: #1990426 . Following the approach above won't have effects outside of WSL. Kinetic being not an LTS is a good release to receive the fix for this first, as it affects a small audience of Ubuntu WSL community, giving us time to learn from them before backporting this to Jammy early next cycle. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1990526 Title: [FFe] UDI snap no longer strictly needed for WSL OOBE Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu Desktop Installer (UDI, for short) package implementing the WSL OOBE has been ported to Windows and the WSL application is able to launch the OOBE running as a native Win32 application, instead of relying on WSLg to display the OOBE. That implies in the possibility of replacing UDI by Subiquity snap, which results in a smaller rootfs image (besides an enhanced experience due native rendering on graphics - instead of depending on RDP as it is currently with the OOBE running inside Ubuntu). Fixing this would require: - replace UDI by Subiquity snaps in the WSL seed; - updating the wsl-setup package to the latest upstream (which is able to mount and launch Subiquity from its snap) LP: #1990426 . Following the approach above won't have effects outside of WSL. Kinetic being not an LTS is a good release to receive the fix for this first, as it affects a small audience of Ubuntu WSL community, giving us time to learn from them before backporting this to Jammy early next cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1990526/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15
--- Comment From i...@de.ibm.com 2022-09-22 08:10 EDT---
zlib1g s390x 1:1.2.11.dfsg-2ubuntu1.4 passes all of my tests.
--- Comment From boris.m...@de.ibm.com 2022-09-22 08:18 EDT---
@Ilya: thanks a lot for your instant verification on focal!
With that, I am updating the tags / keywords to: verification-done,
verification-done-focal, verification-done-jammy
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427
Title:
zlib: compressBound() returns an incorrect result on z15
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in bedtools package in Ubuntu:
Fix Released
Status in htslib package in Ubuntu:
Invalid
Status in zlib package in Ubuntu:
Fix Released
Status in bedtools source package in Focal:
Invalid
Status in htslib source package in Focal:
Fix Committed
Status in zlib source package in Focal:
Fix Committed
Status in bedtools source package in Impish:
Won't Fix
Status in htslib source package in Impish:
Won't Fix
Status in zlib source package in Impish:
Won't Fix
Status in bedtools source package in Jammy:
Fix Released
Status in htslib source package in Jammy:
Invalid
Status in zlib source package in Jammy:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* zlib: compressBound() returns an incorrect result on IBM z15
hardware.
* Passing the result of compressBound() to compress() results
in an error code.
* This is because compressBound() is not adjusted for DFLTCC.
[Fix]
* Adjust compressBound() for DFLTCC like it's already done
for deflateBound().
* Since zlib project does not accept patches at the moment,
the fix has been integrated into the DFLTCC pull request:
https://github.com/madler/zlib/pull/410
The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
* The fix extracted out of the above is:
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff
* On top of this actual zlib fix, there is another patch needed:
'Remove compressBound assertions. (PR #1258)' for htslib.
* But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).
[Test Plan]
* An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
with Ubuntu Server 21.10 (or 22.04).
* A test can be done based on the following C test program:
#include
#include
#include
int main() {
Bytef in_buf[128], out_buf[1024];
for (size_t i = 0; i < sizeof(in_buf); i++)
in_buf[i] = rand();
uLongf dest_len = compressBound(sizeof(in_buf));
assert(dest_len <= sizeof(out_buf));
int ret = compress(out_buf, _len,
in_buf, sizeof(in_buf));
assert(ret == Z_OK);
}
* The test needs to be done by IBM, due to the requirements
for the special z15 hardware.
* A successful test was just completed, based on the version in jammy-
proposed, which is at the same code level that the impish version this
SRU is targeted for.
[Where problems could occur]
* If the adjustment of compressBound() for DFLTCC is done
erroneously the issue can still be present or in worst case
even affect Z systems other than z15 only.
* The compression can become errorneous with the new changes,
e.g. in compressBound.
* Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
(incl. the bit definitions), may cause various and unforseen defects.
* Any build time issues that might have been introduced by this patch
can be identified by a test build; this was done and is available here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427
[Other Info]
* Ubuntu jammy, impish and focal are affected by the zlib issue.
* The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.
* The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, hence does not need to be (actually can't be)
patched.
* Patched version of the affected htslib and bedtools packages
are build and also available at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427
__
Description: zlib: compressBound() returns an incorrect result on z15
Symptom: Passing the result of compressBound() to compress()
results in an error code.
[Touch-packages] [Bug 1975865] Re: Hash and size mismatch with http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-amd64/Packages.gz
** Changed in: apt (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1975865 Title: Hash and size mismatch with http://ddebs.ubuntu.com/dists/bionic- updates/main/binary-amd64/Packages.gz Status in apt package in Ubuntu: Fix Released Bug description: When adding the debug repos, I am getting: E: Failed to fetch http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-amd64/Packages.gz File has unexpected size (795886 != 795487). Mirror sync in progress? [IP: 91.189.91.49 80] Hashes of expected file: - Filesize:795487 [weak] - SHA512:982169cbaaa6b0fe84e2cac755c140f52c578619beea451baa90234af2cfdaef90ac936eb7a7de24364ee860a6b021f852f11a87b7cd6dcb98923a248bc45a81 - SHA256:4a69b95e20ac09bb3de2d5e3c652b2c027bcfa4d6df9dea0a4aed16c805869e6 - SHA1:11dded397ab87e4fff81acf4aed6af18f8eee0b2 [weak] - MD5Sum:9045f9c8424cf15e897f682708f158b8 [weak] Release file created at: Thu, 26 May 2022 08:04:16 + E: Some index files failed to download. They have been ignored, or old ones used instead. When I manually go to the repositories... many (all?) of the hashes listed in http://ddebs.ubuntu.com/dists/bionic-updates/Release do not match the files (e.g. http://ddebs.ubuntu.com/dists/bionic- updates/main/binary-amd64/Packages.gz ) Note: I filed this against `apt` because `ubuntu-bug` forced me to specify a package and I didn't know any other way to file the bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.14 Uname: Linux 5.16.18-1rodete2-amd64 x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 Date: Thu May 26 18:36:21 2022 ProcEnviron: TERM=xterm PATH=(custom, no user) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1975865/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1971538] Re: My machine has Wi-Fi Hotspot broken after upgrade to 22.04
doan van thang, please report a new bug for your issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1971538 Title: My machine has Wi-Fi Hotspot broken after upgrade to 22.04 Status in network-manager package in Ubuntu: Confirmed Bug description: * Impact The hotspot feature fails to forward the data to the clients * Test case - log into an Ubuntu or GNOME session - connect the machine to an eth cable for internet - go to gnome-control-center -> wifi - enable the hotspot from the menu in the headerbar - connect another device to the wifi created -> the client should connect and access to internet work correctly Upon updating to 22.04, none of my machines can use the connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990525] [NEW] E: Internal Error, AutoRemover broke stuff
Public bug reported: I'm trying to run a dist-upgrade, which should be simple enough, but it keeps failing at: Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done Hmm, seems like the AutoRemover destroyed something which really shouldn't happen. Please file a bug report against apt. The following information may help to resolve the situation: The following packages have unmet dependencies: libopenblas0-pthread : Depends: libgfortran5 (>= 8) but it is not going to be installed E: Internal Error, AutoRemover broke stuff libgfortran5 IS installed. Package: libgfortran5 Version: 12.1.0-2ubuntu1~22.04 Priority: optional Section: libs Source: gcc-12 Origin: Ubuntu Maintainer: Ubuntu Core developers Original-Maintainer: Debian GCC Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 3,059 kB Depends: gcc-12-base (= 12.1.0-2ubuntu1~22.04), libc6 (>= 2.34), libgcc-s1 (>= 4.3), libquadmath0 (>= 4.6) Breaks: gcc-4.3 (<< 4.3.6-1), gcc-4.4 (<< 4.4.6-4), gcc-4.5 (<< 4.5.3-2) Homepage: http://gcc.gnu.org/ Task: kubuntu-desktop, kubuntu-full, xubuntu-desktop, lubuntu-desktop, ubuntustudio-desktop, ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop, ubuntu-budgie-desktop, ubuntu-budgie-desktop-raspi Download-Size: 882 kB APT-Manual-Installed: no APT-Sources: http://nova.clouds.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages Apt says to report a bug against Apt, so here I am... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.4.7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Sep 22 13:09:38 2022 Ec2AMI: ami-0008be8e Ec2AMIManifest: FIXME Ec2AvailabilityZone: None Ec2InstanceType: vps2020-starter-1-2-20 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: Upgraded to jammy on 2022-08-15 (38 days ago) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1990525 Title: E: Internal Error, AutoRemover broke stuff Status in apt package in Ubuntu: New Bug description: I'm trying to run a dist-upgrade, which should be simple enough, but it keeps failing at: Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done Hmm, seems like the AutoRemover destroyed something which really shouldn't happen. Please file a bug report against apt. The following information may help to resolve the situation: The following packages have unmet dependencies: libopenblas0-pthread : Depends: libgfortran5 (>= 8) but it is not going to be installed E: Internal Error, AutoRemover broke stuff libgfortran5 IS installed. Package: libgfortran5 Version: 12.1.0-2ubuntu1~22.04 Priority: optional Section: libs Source: gcc-12 Origin: Ubuntu Maintainer: Ubuntu Core developers Original-Maintainer: Debian GCC Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 3,059 kB Depends: gcc-12-base (= 12.1.0-2ubuntu1~22.04), libc6 (>= 2.34), libgcc-s1 (>= 4.3), libquadmath0 (>= 4.6) Breaks: gcc-4.3 (<< 4.3.6-1), gcc-4.4 (<< 4.4.6-4), gcc-4.5 (<< 4.5.3-2) Homepage: http://gcc.gnu.org/ Task: kubuntu-desktop, kubuntu-full, xubuntu-desktop, lubuntu-desktop, ubuntustudio-desktop, ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop, ubuntu-budgie-desktop, ubuntu-budgie-desktop-raspi Download-Size: 882 kB APT-Manual-Installed: no APT-Sources: http://nova.clouds.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages Apt says to report a bug against Apt, so here I am... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.4.7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Sep 22 13:09:38 2022 Ec2AMI: ami-0008be8e Ec2AMIManifest: FIXME Ec2AvailabilityZone: None Ec2InstanceType: vps2020-starter-1-2-20 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: Upgraded to jammy on 2022-08-15 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1990525/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1981622] Re: mtd device must be supplied (device name is empty)
Hi,
on 21.09.2022 updating ubuntu broke it with this bug.
Running on i386, dell latitude e7450 with ssd and ubuntu22.04.1, kernel
5.15.0-48 generic, x86.
After booting, I get the mtd device must be supplied etc etc error, and
I am left with a terminal only version.
I have an important hint: as suggested above, it's a problem with some
authentication stuff. Yesterday after the bad upgrade, I put the pc in
suspend mode. When I re opened it, I failed to log in into my account
(the graphical session was otherwise normal) in a funny way: when
propmted the password, it was as if the Enter key was continuosly being
pressedm and I could at most enter one single word.
I have seen from a link provided above that the i386 version has not
been tested, which is indeed my version.
Running apt-cache policy systemd returns (roughly, cannot copy and past as I'm
from another machine):
Installed 249.11-0ubuntu3.4
Candidate same
version tables has entries:
249.11-ubuntu3.4 500
249.11-ubuntu3
I have tried the other suggested actions but none worked.
I have failed in installing the proposed ubuntu3.6 version of systemd, goes
beyond my skills, I would need more detailed instructions.
Otherwise is it possible to undo the update of 21.09.22?
I may try this path or just switch to something Fedora, it is not accetaple
that a daily update breaks down an LTS, it's the first time it happens to me in
8 years of ubuntu, please provide a fix on the main brench.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1981622
Title:
mtd device must be supplied (device name is empty)
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Invalid
Status in systemd source package in Jammy:
Fix Released
Bug description:
[WORKAROUND]
This will NOT fix a system that is not booting, because the "mtd
device must be supplied (device name is empty)" message is not the
cause of failed boots. This work around is only for those who are
annoyed by the error message, but are otherwise not experiencing any
issues.
If you are not able to boot your system, but you see this error
message, please open a separate bug with your journalctl and dmesg
logs.
# cp /{lib,etc}/systemd/system/systemd-pstore.service
# sed -i 's/modprobe@mtdpstore.service //'
/etc/systemd/system/systemd-pstore.service
# systemctl daemon-reload
[Impact]
Due to mtdpstore not being properly configured as a pstore backend,
when systemd-pstore.service tries to load the module, users get the
following error in dmesg:
[ 18.453473] systemd[1]: Starting Load Kernel Module mtdpstore...
[ 18.462685] mtd device must be supplied (device name is empty)
This is a distracting error for users trying to diagnose other system
issues, especially if their system does not boot after a kernel crash
and this is the only message displayed on the console.
[Test Plan]
* Force a kernel crash to populate /sys/fs/pstore, thus causing
systemd-pstore.service to start on the subsequent boot:
# echo 1 > /proc/sys/kernel/sysrq
# echo 1 > /proc/sys/kernel/panic
# echo c > /proc/sysrq-trigger
* When the system reboots, observe the error in dmesg:
# dmesg | grep mtd
[Where problems could occur]
If a system was relying on this pstore backend, and mtdpstore is built
as a module, it is possible for systemd-pstore.service to trigger
before mtdpstore is loaded, causing systemd-pstore to not copy the
contents of /sys/fs/pstore. Note however that before the patched
introduced as a result of bug 1978079, systemd-pstore.service would
not attempt to load *any* kernel modules.
[Original Description]
After updating my 22.04 system (possibly caused by Systemd update).
And now booting, dmesg has two errors:
'mtd device must be supplied (device name is empty)'.
See line 8 and 134 in the included logfile.
The system are booting as it should though, and the system are working
like it should no errors at all.
Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
systemd?
I have an EFI mounted at boot but it isn't used because I have
installed my system in legacy BIOS mode.
Is this maybe the culprit?
I could ignore the message but it isn't nice though.
Regards
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15
** Tags removed: verification-done verification-done-focal
** Tags added: verification-needed verification-needed-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427
Title:
zlib: compressBound() returns an incorrect result on z15
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in bedtools package in Ubuntu:
Fix Released
Status in htslib package in Ubuntu:
Invalid
Status in zlib package in Ubuntu:
Fix Released
Status in bedtools source package in Focal:
Invalid
Status in htslib source package in Focal:
Fix Committed
Status in zlib source package in Focal:
Fix Committed
Status in bedtools source package in Impish:
Won't Fix
Status in htslib source package in Impish:
Won't Fix
Status in zlib source package in Impish:
Won't Fix
Status in bedtools source package in Jammy:
Fix Released
Status in htslib source package in Jammy:
Invalid
Status in zlib source package in Jammy:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* zlib: compressBound() returns an incorrect result on IBM z15
hardware.
* Passing the result of compressBound() to compress() results
in an error code.
* This is because compressBound() is not adjusted for DFLTCC.
[Fix]
* Adjust compressBound() for DFLTCC like it's already done
for deflateBound().
* Since zlib project does not accept patches at the moment,
the fix has been integrated into the DFLTCC pull request:
https://github.com/madler/zlib/pull/410
The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
* The fix extracted out of the above is:
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff
* On top of this actual zlib fix, there is another patch needed:
'Remove compressBound assertions. (PR #1258)' for htslib.
* But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).
[Test Plan]
* An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
with Ubuntu Server 21.10 (or 22.04).
* A test can be done based on the following C test program:
#include
#include
#include
int main() {
Bytef in_buf[128], out_buf[1024];
for (size_t i = 0; i < sizeof(in_buf); i++)
in_buf[i] = rand();
uLongf dest_len = compressBound(sizeof(in_buf));
assert(dest_len <= sizeof(out_buf));
int ret = compress(out_buf, _len,
in_buf, sizeof(in_buf));
assert(ret == Z_OK);
}
* The test needs to be done by IBM, due to the requirements
for the special z15 hardware.
* A successful test was just completed, based on the version in jammy-
proposed, which is at the same code level that the impish version this
SRU is targeted for.
[Where problems could occur]
* If the adjustment of compressBound() for DFLTCC is done
erroneously the issue can still be present or in worst case
even affect Z systems other than z15 only.
* The compression can become errorneous with the new changes,
e.g. in compressBound.
* Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
(incl. the bit definitions), may cause various and unforseen defects.
* Any build time issues that might have been introduced by this patch
can be identified by a test build; this was done and is available here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427
[Other Info]
* Ubuntu jammy, impish and focal are affected by the zlib issue.
* The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.
* The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, hence does not need to be (actually can't be)
patched.
* Patched version of the affected htslib and bedtools packages
are build and also available at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427
__
Description: zlib: compressBound() returns an incorrect result on z15
Symptom: Passing the result of compressBound() to compress()
results in an error code.
Problem: compressBound() is not adjusted for DFLTCC.
Solution: Adjust compressBound() for DFLTCC like it's already done
for deflateBound(). Since zlib project does not accept
patches at the moment, the fix has been integrated into
the DFLTCC pull request:
https://github.com/madler/zlib/pull/410
[Touch-packages] [Bug 1980408] Proposed package removed from archive
The version of glib2.0 in the proposed pocket of Jammy that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1980408 Title: Update glib to 2.72.3 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: Confirmed Bug description: Impact -- There is a new bugfix release in the stable 2.72 series https://gitlab.gnome.org/GNOME/glib/-/blob/2.72.3/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopgktest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1980408/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1980408] Proposed package removed from archive
The version of glib2.0 in the proposed pocket of Jammy that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. ** Changed in: glib2.0 (Ubuntu Jammy) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1980408 Title: Update glib to 2.72.3 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: Confirmed Bug description: Impact -- There is a new bugfix release in the stable 2.72 series https://gitlab.gnome.org/GNOME/glib/-/blob/2.72.3/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopgktest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1980408/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15
Well, I had comment #11 in mind where the 1:1.2.11.dfsg-2ubuntu1.3 was
successfully verified on focal.
Meanwhile that version got overruled by a security update:
zlib (1:1.2.11.dfsg-2ubuntu1.3) focal-security; urgency=medium
and became 'already used', hence a new version was needed for this bug and so
we are now at:
1:1.2.11.dfsg-2ubuntu1.4 - but it incl. the same patches.
Anyway, I'll ask to get 1:1.2.11.dfsg-2ubuntu1.4 verified again on focal.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427
Title:
zlib: compressBound() returns an incorrect result on z15
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in bedtools package in Ubuntu:
Fix Released
Status in htslib package in Ubuntu:
Invalid
Status in zlib package in Ubuntu:
Fix Released
Status in bedtools source package in Focal:
Invalid
Status in htslib source package in Focal:
Fix Committed
Status in zlib source package in Focal:
Fix Committed
Status in bedtools source package in Impish:
Won't Fix
Status in htslib source package in Impish:
Won't Fix
Status in zlib source package in Impish:
Won't Fix
Status in bedtools source package in Jammy:
Fix Released
Status in htslib source package in Jammy:
Invalid
Status in zlib source package in Jammy:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* zlib: compressBound() returns an incorrect result on IBM z15
hardware.
* Passing the result of compressBound() to compress() results
in an error code.
* This is because compressBound() is not adjusted for DFLTCC.
[Fix]
* Adjust compressBound() for DFLTCC like it's already done
for deflateBound().
* Since zlib project does not accept patches at the moment,
the fix has been integrated into the DFLTCC pull request:
https://github.com/madler/zlib/pull/410
The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
* The fix extracted out of the above is:
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff
* On top of this actual zlib fix, there is another patch needed:
'Remove compressBound assertions. (PR #1258)' for htslib.
* But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).
[Test Plan]
* An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
with Ubuntu Server 21.10 (or 22.04).
* A test can be done based on the following C test program:
#include
#include
#include
int main() {
Bytef in_buf[128], out_buf[1024];
for (size_t i = 0; i < sizeof(in_buf); i++)
in_buf[i] = rand();
uLongf dest_len = compressBound(sizeof(in_buf));
assert(dest_len <= sizeof(out_buf));
int ret = compress(out_buf, _len,
in_buf, sizeof(in_buf));
assert(ret == Z_OK);
}
* The test needs to be done by IBM, due to the requirements
for the special z15 hardware.
* A successful test was just completed, based on the version in jammy-
proposed, which is at the same code level that the impish version this
SRU is targeted for.
[Where problems could occur]
* If the adjustment of compressBound() for DFLTCC is done
erroneously the issue can still be present or in worst case
even affect Z systems other than z15 only.
* The compression can become errorneous with the new changes,
e.g. in compressBound.
* Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
(incl. the bit definitions), may cause various and unforseen defects.
* Any build time issues that might have been introduced by this patch
can be identified by a test build; this was done and is available here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427
[Other Info]
* Ubuntu jammy, impish and focal are affected by the zlib issue.
* The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.
* The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, hence does not need to be (actually can't be)
patched.
* Patched version of the affected htslib and bedtools packages
are build and also available at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427
__
Description: zlib: compressBound() returns an incorrect result on z15
Symptom: Passing the result of compressBound() to compress()
results in an error code.
Problem: compressBound() is not adjusted
[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427
Title:
zlib: compressBound() returns an incorrect result on z15
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in bedtools package in Ubuntu:
Fix Released
Status in htslib package in Ubuntu:
Invalid
Status in zlib package in Ubuntu:
Fix Released
Status in bedtools source package in Focal:
Invalid
Status in htslib source package in Focal:
Fix Committed
Status in zlib source package in Focal:
Fix Committed
Status in bedtools source package in Impish:
Won't Fix
Status in htslib source package in Impish:
Won't Fix
Status in zlib source package in Impish:
Won't Fix
Status in bedtools source package in Jammy:
Fix Released
Status in htslib source package in Jammy:
Invalid
Status in zlib source package in Jammy:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* zlib: compressBound() returns an incorrect result on IBM z15
hardware.
* Passing the result of compressBound() to compress() results
in an error code.
* This is because compressBound() is not adjusted for DFLTCC.
[Fix]
* Adjust compressBound() for DFLTCC like it's already done
for deflateBound().
* Since zlib project does not accept patches at the moment,
the fix has been integrated into the DFLTCC pull request:
https://github.com/madler/zlib/pull/410
The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
* The fix extracted out of the above is:
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff
* On top of this actual zlib fix, there is another patch needed:
'Remove compressBound assertions. (PR #1258)' for htslib.
* But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).
[Test Plan]
* An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
with Ubuntu Server 21.10 (or 22.04).
* A test can be done based on the following C test program:
#include
#include
#include
int main() {
Bytef in_buf[128], out_buf[1024];
for (size_t i = 0; i < sizeof(in_buf); i++)
in_buf[i] = rand();
uLongf dest_len = compressBound(sizeof(in_buf));
assert(dest_len <= sizeof(out_buf));
int ret = compress(out_buf, _len,
in_buf, sizeof(in_buf));
assert(ret == Z_OK);
}
* The test needs to be done by IBM, due to the requirements
for the special z15 hardware.
* A successful test was just completed, based on the version in jammy-
proposed, which is at the same code level that the impish version this
SRU is targeted for.
[Where problems could occur]
* If the adjustment of compressBound() for DFLTCC is done
erroneously the issue can still be present or in worst case
even affect Z systems other than z15 only.
* The compression can become errorneous with the new changes,
e.g. in compressBound.
* Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
(incl. the bit definitions), may cause various and unforseen defects.
* Any build time issues that might have been introduced by this patch
can be identified by a test build; this was done and is available here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427
[Other Info]
* Ubuntu jammy, impish and focal are affected by the zlib issue.
* The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.
* The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, hence does not need to be (actually can't be)
patched.
* Patched version of the affected htslib and bedtools packages
are build and also available at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427
__
Description: zlib: compressBound() returns an incorrect result on z15
Symptom: Passing the result of compressBound() to compress()
results in an error code.
Problem: compressBound() is not adjusted for DFLTCC.
Solution: Adjust compressBound() for DFLTCC like it's already done
for deflateBound(). Since zlib project does not accept
patches at the moment, the fix has been integrated into
the DFLTCC pull request:
https://github.com/madler/zlib/pull/410
[Touch-packages] [Bug 1989969] Re: autopkgtest TEST-36-NUMAPOLICY failure on ppc64el
** Changed in: systemd (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1989969 Title: autopkgtest TEST-36-NUMAPOLICY failure on ppc64el Status in systemd package in Ubuntu: Fix Committed Bug description: In Kinetic, TEST-36-NUMAPOLICY from upstream-2 fails very frequently on ppc64el. See for example: https://autopkgtest.ubuntu.com/results/autopkgtest- kinetic/kinetic/ppc64el/s/systemd/20220908_195425_da51e@/log.gz, and the full kinetic ppc64el history: https://autopkgtest.ubuntu.com/packages/systemd/kinetic/ppc64el. It has passed on very few occasions. I have tried to debug this locally but have gotten very little useful information (i.e. not enough to open an upstream bug). For now it is probably best to denylist this test on ppc64el. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1989969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990187] Re: systemd-resolved recommends libnss-resolve in kinetic, pulls it into minimal system where it was explicitly excluded before
** Changed in: systemd (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1990187 Title: systemd-resolved recommends libnss-resolve in kinetic, pulls it into minimal system where it was explicitly excluded before Status in systemd package in Ubuntu: Fix Committed Bug description: In kinetic, systemd-resolved now Recommends: libnss-resolve, pulling it into the ubuntu-minimal seed. In the past we briefly had libnss-resolve seeded (between xenial and bionic LTSes but not in any LTS) but it was removed because: - it was redundant; /etc/resolv.conf was consistent and correct. - its presence could mask wrong DNS configuration resulting in difficult-to-debug differences in behavior between applications that did use nss_resolved via /etc/nsswitch.conf and those that did not (examples: i386 binaries that could not use nss_resolved because it was not installed; statically-linked go implementations that parsed /etc/resolve.conf directly and did not load NSS modules) This new recommends was noticed specifically because of some broken kinetic container images where /etc/resolv.conf was broken (empty) and *some* applications still worked via nss but others failed by trying to use the DNS protocol directly. (I.e.: 2nd point above) I believe systemd-resolved should drop its recommends on libnss- resolve for Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990278] Re: systemd-resolved not included in Ubuntu bootstrap
** Changed in: systemd (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1990278 Title: systemd-resolved not included in Ubuntu bootstrap Status in systemd package in Ubuntu: Fix Committed Bug description: By default, i.e. with no --variant specified, debootstrap will only pull in packages with Priority: required or important. Before the systemd-resolved package split, resolved would be included because it was shipped with the systemd binary package, which is Priority: important. Currently there is no Priority: set on systemd-resolved, so it is not included with the deafult Ubuntu bootstrap. The systemd-resolved package should have Priority: important to fix this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1959475] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1959475 Title: "machinectl shell" connections immediately terminated Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [Impact] This bug prevents users on Impish and newer from connecting to Focal systemd containers using `machinectl shell`. This limits users ability to manage containers spawned with systemd-nspawn. [Test Plan] On a Jammy host, do the following: * Install systemd-container and debootstrap if necessary: $ sudo apt install debootstrap systemd-container * Create a Focal filesystem for the container: $ sudo debootstrap --arch= focal /var/lib/containers/lp1959475/ * Launch the container: $ sudo systemd-nspawn -D /var/lib/containers/lp1959475/ --machine test-container * Inside the container, set a password for root and then exit: $ passwd # Enter password when prompted $ exit * Re-launch the container with -b option: $ sudo systemd-nspawn -D /var/lib/containers/lp1959475/ --machine test-container -b * In a separate terminal window, try to connect to the container: $ sudo machinectl shell test-container * Observe the "Connection to machine test-container terminated" error message. [Where problems could occur] The patch changes a path_equal() call to path_equal_ptr() which NULL- checks before calling path_compare(). This avoids an assertion failure in path_compare() and allows the term to be correctly configured in execution environments requiring one. If were regressions were to occur, it would be related to this configuration. [Other Info] This bug occurs when trying to connect to a Focal container from e.g. a Jammy host. For SRU verification, the container should be Focal, and the host should be Jammy. The -proposed package should be installed in the Focal container. [Original Description] The command "machinectl shell" does not work in systemd 249.9-0ubuntu2: $ sudo machinectl shell ns-xxx Connected to machine ns-xxx. Press ^] three times within 1s to exit session. Connection to machine ns-xxx terminated. The issue seems to be described here: https://forum.manjaro.org/t/the-machinectl-shell-command-stopped-working-after-systemd-upgrade-to-250-2-1/99899 https://github.com/systemd/systemd/issues/22234 and solved here: https://github.com/systemd/systemd/commit/e8cf09b2a2ad0d48e5493050d54251d5f512d9b6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1959475/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1959475] Re: "machinectl shell" connections immediately terminated
This bug was fixed in the package systemd - 245.4-4ubuntu3.18 --- systemd (245.4-4ubuntu3.18) focal; urgency=medium [ Nick Rosbrook ] * core: make sure we don't get confused when setting TERM for a tty fd (LP: #1959475) File: debian/patches/lp1959475-core-make-sure-we-don-t-get-confused-when-setting-TERM-fo.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b10c6853050dde26665caf3b15444d768d2bc498 * shared/calendarspec: when mktime() moves us backwards, jump forward (LP: #1966800) File: debian/patches/lp1966800-shared-calendarspec-when-mktime-moves-us-backwards-jump-f.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1f063541e44f6ff1a6904676d4264a2e49a09594 * network: do not remove localhost address (LP: #1979951) File: debian/patches/lp1979951-network-do-not-remove-localhost-address.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=87f872b8c5451f353601fb606e7fd7a479217cef * units: remove the restart limit on the modprobe@.service (LP: #1982462) File: debian/patches/lp1982462-units-remove-the-restart-limit-on-the-modprobe-.service.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=68353ffaf3539e6a58ef62a8b50850f56eae29ea [ Mustafa Kemal Gilor ] * d/p/lp1978079-efi-pstore-not-cleared-on-boot.patch: pstore: Run after modules are loaded. Thanks to Alexander Graf . (LP: #1978079) Author: Mustafa Kemal Gilor File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6e60756f2079d6408abdb967127a1d9b9a0eba8c -- Nick Rosbrook Wed, 31 Aug 2022 11:27:33 -0400 ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1959475 Title: "machinectl shell" connections immediately terminated Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [Impact] This bug prevents users on Impish and newer from connecting to Focal systemd containers using `machinectl shell`. This limits users ability to manage containers spawned with systemd-nspawn. [Test Plan] On a Jammy host, do the following: * Install systemd-container and debootstrap if necessary: $ sudo apt install debootstrap systemd-container * Create a Focal filesystem for the container: $ sudo debootstrap --arch= focal /var/lib/containers/lp1959475/ * Launch the container: $ sudo systemd-nspawn -D /var/lib/containers/lp1959475/ --machine test-container * Inside the container, set a password for root and then exit: $ passwd # Enter password when prompted $ exit * Re-launch the container with -b option: $ sudo systemd-nspawn -D /var/lib/containers/lp1959475/ --machine test-container -b * In a separate terminal window, try to connect to the container: $ sudo machinectl shell test-container * Observe the "Connection to machine test-container terminated" error message. [Where problems could occur] The patch changes a path_equal() call to path_equal_ptr() which NULL- checks before calling path_compare(). This avoids an assertion failure in path_compare() and allows the term to be correctly configured in execution environments requiring one. If were regressions were to occur, it would be related to this configuration. [Other Info] This bug occurs when trying to connect to a Focal container from e.g. a Jammy host. For SRU verification, the container should be Focal, and the host should be Jammy. The -proposed package should be installed in the Focal container. [Original Description] The command "machinectl shell" does not work in systemd 249.9-0ubuntu2: $ sudo machinectl shell ns-xxx Connected to machine ns-xxx. Press ^] three times within 1s to exit session. Connection to machine ns-xxx terminated. The issue seems to be described here: https://forum.manjaro.org/t/the-machinectl-shell-command-stopped-working-after-systemd-upgrade-to-250-2-1/99899 https://github.com/systemd/systemd/issues/22234 and solved here: https://github.com/systemd/systemd/commit/e8cf09b2a2ad0d48e5493050d54251d5f512d9b6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1959475/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15
Hey Frank! You switched the focal verification tags, but I do not see
any verification of the focal packages. Comment #65 only mentions
versions for jammy. Have the focal packages been tested in any way?
Switching back tags for focal.
** Tags removed: verification-done verification-done-focal
** Tags added: verification-needed verification-needed-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427
Title:
zlib: compressBound() returns an incorrect result on z15
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in bedtools package in Ubuntu:
Fix Released
Status in htslib package in Ubuntu:
Invalid
Status in zlib package in Ubuntu:
Fix Released
Status in bedtools source package in Focal:
Invalid
Status in htslib source package in Focal:
Fix Committed
Status in zlib source package in Focal:
Fix Committed
Status in bedtools source package in Impish:
Won't Fix
Status in htslib source package in Impish:
Won't Fix
Status in zlib source package in Impish:
Won't Fix
Status in bedtools source package in Jammy:
Fix Released
Status in htslib source package in Jammy:
Invalid
Status in zlib source package in Jammy:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* zlib: compressBound() returns an incorrect result on IBM z15
hardware.
* Passing the result of compressBound() to compress() results
in an error code.
* This is because compressBound() is not adjusted for DFLTCC.
[Fix]
* Adjust compressBound() for DFLTCC like it's already done
for deflateBound().
* Since zlib project does not accept patches at the moment,
the fix has been integrated into the DFLTCC pull request:
https://github.com/madler/zlib/pull/410
The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
* The fix extracted out of the above is:
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff
* On top of this actual zlib fix, there is another patch needed:
'Remove compressBound assertions. (PR #1258)' for htslib.
* But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).
[Test Plan]
* An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
with Ubuntu Server 21.10 (or 22.04).
* A test can be done based on the following C test program:
#include
#include
#include
int main() {
Bytef in_buf[128], out_buf[1024];
for (size_t i = 0; i < sizeof(in_buf); i++)
in_buf[i] = rand();
uLongf dest_len = compressBound(sizeof(in_buf));
assert(dest_len <= sizeof(out_buf));
int ret = compress(out_buf, _len,
in_buf, sizeof(in_buf));
assert(ret == Z_OK);
}
* The test needs to be done by IBM, due to the requirements
for the special z15 hardware.
* A successful test was just completed, based on the version in jammy-
proposed, which is at the same code level that the impish version this
SRU is targeted for.
[Where problems could occur]
* If the adjustment of compressBound() for DFLTCC is done
erroneously the issue can still be present or in worst case
even affect Z systems other than z15 only.
* The compression can become errorneous with the new changes,
e.g. in compressBound.
* Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
(incl. the bit definitions), may cause various and unforseen defects.
* Any build time issues that might have been introduced by this patch
can be identified by a test build; this was done and is available here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427
[Other Info]
* Ubuntu jammy, impish and focal are affected by the zlib issue.
* The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.
* The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, hence does not need to be (actually can't be)
patched.
* Patched version of the affected htslib and bedtools packages
are build and also available at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427
__
Description: zlib: compressBound() returns an incorrect result on z15
Symptom: Passing the result of compressBound() to compress()
results in an error code.
Problem: compressBound() is not adjusted for DFLTCC.
Solution: Adjust compressBound() for DFLTCC like it's already done
[Touch-packages] [Bug 1966800] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1966800 Title: systemd locks up due to incorrect handling of time zone changes Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd package in Fedora: Unknown Bug description: [Impact] This bug can cause systemd timers to lock up systems using the Europe/Dublin timezone if certain OnCalendar values are used. If the timer is enabled at boot, this bug prevents the system from booting. If the timer is started later, systemd becomes unresponsive. [Test Plan] * Create a systemd service and corresponding timer scheduled for 01:00 on Sundays: $ cat /etc/systemd/system/lp-1966800-reproducer.timer [Unit] Description=LP 1966800 reproducer [Timer] OnCalendar=Sun *-*-* 01:00:00 Persistent=true [Install] WantedBy=timers.target $ cat /etc/systemd/system/lp-1966800-reproducer.service [Service] ExecStart=/usr/bin/echo "LP 1966800 reproducer" $ systemctl daemon-reload * Set the date to 21 March, 2021 in the Europe/Dublin timezone (need to disable NTP first): $ timedatectl set-ntp false $ timedatectl set-time "2021-03-21" $ timedatectl set-timezone Europe/Dublin * Try to start the timer, and observe that systemd becomes unresponsive. This command will time out, as will `systemctl status` etc. $ systemctl start lp-1966800-reproducer.timer [Where problems could occur] The patch makes changes in the calendar spec code, which is used by systemd timers to determine the next time to trigger a timer. If this patch breaks something, it would be related to the triggering of systemd timers. [Original Description] Recently on systems in Ireland, systemd became unresponsive due the change from GMT to Irish Standard Time. This is due to Ireland being unique in having their standard time during the summer, unlike most regions. Related to: https://bugzilla.redhat.com/show_bug.cgi?id=1941335 Fixed by: https://github.com/systemd/systemd-stable/commit/a8b66ca9af811148b67ee952ab32748f88b8bba3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966800] Re: systemd locks up due to incorrect handling of time zone changes
This bug was fixed in the package systemd - 245.4-4ubuntu3.18 --- systemd (245.4-4ubuntu3.18) focal; urgency=medium [ Nick Rosbrook ] * core: make sure we don't get confused when setting TERM for a tty fd (LP: #1959475) File: debian/patches/lp1959475-core-make-sure-we-don-t-get-confused-when-setting-TERM-fo.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b10c6853050dde26665caf3b15444d768d2bc498 * shared/calendarspec: when mktime() moves us backwards, jump forward (LP: #1966800) File: debian/patches/lp1966800-shared-calendarspec-when-mktime-moves-us-backwards-jump-f.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1f063541e44f6ff1a6904676d4264a2e49a09594 * network: do not remove localhost address (LP: #1979951) File: debian/patches/lp1979951-network-do-not-remove-localhost-address.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=87f872b8c5451f353601fb606e7fd7a479217cef * units: remove the restart limit on the modprobe@.service (LP: #1982462) File: debian/patches/lp1982462-units-remove-the-restart-limit-on-the-modprobe-.service.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=68353ffaf3539e6a58ef62a8b50850f56eae29ea [ Mustafa Kemal Gilor ] * d/p/lp1978079-efi-pstore-not-cleared-on-boot.patch: pstore: Run after modules are loaded. Thanks to Alexander Graf . (LP: #1978079) Author: Mustafa Kemal Gilor File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6e60756f2079d6408abdb967127a1d9b9a0eba8c -- Nick Rosbrook Wed, 31 Aug 2022 11:27:33 -0400 ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1966800 Title: systemd locks up due to incorrect handling of time zone changes Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd package in Fedora: Unknown Bug description: [Impact] This bug can cause systemd timers to lock up systems using the Europe/Dublin timezone if certain OnCalendar values are used. If the timer is enabled at boot, this bug prevents the system from booting. If the timer is started later, systemd becomes unresponsive. [Test Plan] * Create a systemd service and corresponding timer scheduled for 01:00 on Sundays: $ cat /etc/systemd/system/lp-1966800-reproducer.timer [Unit] Description=LP 1966800 reproducer [Timer] OnCalendar=Sun *-*-* 01:00:00 Persistent=true [Install] WantedBy=timers.target $ cat /etc/systemd/system/lp-1966800-reproducer.service [Service] ExecStart=/usr/bin/echo "LP 1966800 reproducer" $ systemctl daemon-reload * Set the date to 21 March, 2021 in the Europe/Dublin timezone (need to disable NTP first): $ timedatectl set-ntp false $ timedatectl set-time "2021-03-21" $ timedatectl set-timezone Europe/Dublin * Try to start the timer, and observe that systemd becomes unresponsive. This command will time out, as will `systemctl status` etc. $ systemctl start lp-1966800-reproducer.timer [Where problems could occur] The patch makes changes in the calendar spec code, which is used by systemd timers to determine the next time to trigger a timer. If this patch breaks something, it would be related to the triggering of systemd timers. [Original Description] Recently on systems in Ireland, systemd became unresponsive due the change from GMT to Irish Standard Time. This is due to Ireland being unique in having their standard time during the summer, unlike most regions. Related to: https://bugzilla.redhat.com/show_bug.cgi?id=1941335 Fixed by: https://github.com/systemd/systemd-stable/commit/a8b66ca9af811148b67ee952ab32748f88b8bba3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1979951] Re: 127.0.0.1/::1 removed from loopback interface if you configure extra IPs on lo (r104 regression/behaviour change)
This bug was fixed in the package systemd - 245.4-4ubuntu3.18 --- systemd (245.4-4ubuntu3.18) focal; urgency=medium [ Nick Rosbrook ] * core: make sure we don't get confused when setting TERM for a tty fd (LP: #1959475) File: debian/patches/lp1959475-core-make-sure-we-don-t-get-confused-when-setting-TERM-fo.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b10c6853050dde26665caf3b15444d768d2bc498 * shared/calendarspec: when mktime() moves us backwards, jump forward (LP: #1966800) File: debian/patches/lp1966800-shared-calendarspec-when-mktime-moves-us-backwards-jump-f.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1f063541e44f6ff1a6904676d4264a2e49a09594 * network: do not remove localhost address (LP: #1979951) File: debian/patches/lp1979951-network-do-not-remove-localhost-address.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=87f872b8c5451f353601fb606e7fd7a479217cef * units: remove the restart limit on the modprobe@.service (LP: #1982462) File: debian/patches/lp1982462-units-remove-the-restart-limit-on-the-modprobe-.service.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=68353ffaf3539e6a58ef62a8b50850f56eae29ea [ Mustafa Kemal Gilor ] * d/p/lp1978079-efi-pstore-not-cleared-on-boot.patch: pstore: Run after modules are loaded. Thanks to Alexander Graf . (LP: #1978079) Author: Mustafa Kemal Gilor File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6e60756f2079d6408abdb967127a1d9b9a0eba8c -- Nick Rosbrook Wed, 31 Aug 2022 11:27:33 -0400 ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1979951 Title: 127.0.0.1/::1 removed from loopback interface if you configure extra IPs on lo (r104 regression/behaviour change) Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in netplan.io source package in Focal: New Status in systemd source package in Focal: Fix Released Status in netplan.io source package in Jammy: New Status in systemd source package in Jammy: Fix Released Bug description: [Impact] Users who wish to configure additional addresses on lo may inadvertently remove the 127.0.0.1/8 address from the interface. And, because this only happens on the second invocation of `netplan apply`, it can create confusing breakages for users. Although this is not a recommended configuration, it was previously supported and the current behavior is a regression. [Test Plan] * Configure additional addresses on the lo interface. I am testing in a LXD container, so I added the following to /etc/netplan/10-lxc.yaml under `ethernets:` lo: addresses: ["10.10.10.17/24","10.10.10.19/24"] * Apply the config, and then inspect the lo interface's addresses: $ netplan apply $ ip addr show dev lo * Observe that the 127.0.0.1/8 address is still present. Now, run the same commands again: $ netplan apply $ ip addr show dev lo * On an affected system, observe that the 127.0.0.1/8 address is now gone. On a patched system, the address should still be present. [Where problems could occur] The patch removes cases where systemd-networkd will drop foreign addresses from a managed link. If problems were to occur, it would be related to the addresses configured on a managed link. [Original Description] If you configure the loopback interface using netplan without listing the standard loopback addresses (127.0.0.1 / ::1) that are auto- configured on boot then they are removed by netplan in r104+ but were not in r103. Confusingly this only happens the second time "netplan apply" is invoked and not the first time. There is some argument this is not a valid configuration, however - It worked on r103 and broke in the r104 SRU for 20.04 and breaks on upgrade - Since it only occurs on the second "netplan apply" it is likely people will accidentally create a configuration that on first verification works but breaks later - Adding addresses to a loopback or dummy interface is a common need - There is no dummy interface support in Netplan - Removing the loopback IP doesn't immediately cause obvious breakage in an SSH session but causes all sorts of hard to diagnose issues with applications Thus I consider this a high priority regression because of the multiple ways this can break a system at an unexpected/unrelated time to when the original change was made. As a workaround you can add 127.0.0.1/::1 to the file and this seems to generally
[Touch-packages] [Bug 1978079] Re: EFI pstore not cleared on boot
This bug was fixed in the package systemd - 245.4-4ubuntu3.18 --- systemd (245.4-4ubuntu3.18) focal; urgency=medium [ Nick Rosbrook ] * core: make sure we don't get confused when setting TERM for a tty fd (LP: #1959475) File: debian/patches/lp1959475-core-make-sure-we-don-t-get-confused-when-setting-TERM-fo.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b10c6853050dde26665caf3b15444d768d2bc498 * shared/calendarspec: when mktime() moves us backwards, jump forward (LP: #1966800) File: debian/patches/lp1966800-shared-calendarspec-when-mktime-moves-us-backwards-jump-f.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1f063541e44f6ff1a6904676d4264a2e49a09594 * network: do not remove localhost address (LP: #1979951) File: debian/patches/lp1979951-network-do-not-remove-localhost-address.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=87f872b8c5451f353601fb606e7fd7a479217cef * units: remove the restart limit on the modprobe@.service (LP: #1982462) File: debian/patches/lp1982462-units-remove-the-restart-limit-on-the-modprobe-.service.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=68353ffaf3539e6a58ef62a8b50850f56eae29ea [ Mustafa Kemal Gilor ] * d/p/lp1978079-efi-pstore-not-cleared-on-boot.patch: pstore: Run after modules are loaded. Thanks to Alexander Graf . (LP: #1978079) Author: Mustafa Kemal Gilor File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6e60756f2079d6408abdb967127a1d9b9a0eba8c -- Nick Rosbrook Wed, 31 Aug 2022 11:27:33 -0400 ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1978079 Title: EFI pstore not cleared on boot Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Impish: Won't Fix Status in systemd source package in Jammy: Fix Released Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] Systemd has a systemd-pstore component that scans the pstore on boot and if non-empty, takes all previously created dumps, transfers them into its journal and removes the pstore elements. This is very important on UEFI systems, which only have a limited amount of space for variables. In Ubuntu, the kernel is configured with CONFIG_EFI_VARS_PSTORE=m which means the EFI pstore support gets loaded dynamically. In all of my boots, this dynamic module loading happened *after* systemd tried to check for pstore variables. So systemd-pstore never starts and never clears the UEFI variable store. I see this happening in AWS on Graviton instances, which eventually run out of space to store the dumps. On real hardware, this behavior may lead to unbootable systems. ``` $ systemctl status systemd-pstore ○ systemd-pstore.service - Platform Persistent Storage Archival Loaded: loaded (/lib/systemd/system/systemd-pstore.service; enabled; vendor preset: enabled) Active: inactive (dead) Condition: start condition failed at Thu 2022-06-09 09:11:41 UTC; 29min ago └─ ConditionDirectoryNotEmpty=/sys/fs/pstore was not met Docs: man:systemd-pstore(8) Jun 09 09:11:41 ip-172-31-0-61 systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. $ ls -la /sys/fs/pstore total 0 drwxr-x--- 2 root root0 Jun 9 09:11 . drwxr-xr-x 8 root root0 Jun 9 09:11 .. -r--r--r-- 1 root root 1803 Jun 9 09:07 dmesg-efi-165476562001001 -r--r--r-- 1 root root 1777 Jun 9 09:07 dmesg-efi-165476562002001 -r--r--r-- 1 root root 1773 Jun 9 09:07 dmesg-efi-165476562003001 -r--r--r-- 1 root root 1815 Jun 9 09:07 dmesg-efi-165476562004001 -r--r--r-- 1 root root 1826 Jun 9 09:07 dmesg-efi-165476562005001 -r--r--r-- 1 root root 1754 Jun 9 09:07 dmesg-efi-165476562006001 -r--r--r-- 1 root root 1821 Jun 9 09:07 dmesg-efi-165476562007001 -r--r--r-- 1 root root 1767 Jun 9 09:07 dmesg-efi-165476562008001 -r--r--r-- 1 root root 1729 Jun 9 09:07 dmesg-efi-165476562009001 -r--r--r-- 1 root root 1819 Jun 9 09:07 dmesg-efi-165476562010001 -r--r--r-- 1 root root 1767 Jun 9 09:07 dmesg-efi-165476562011001 -r--r--r-- 1 root root 1775 Jun 9 09:07 dmesg-efi-165476562012001 -r--r--r-- 1 root root 1802 Jun 9 09:07 dmesg-efi-165476562013001 -r--r--r-- 1 root root 1812 Jun 9 09:07 dmesg-efi-165476562014001 -r--r--r-- 1 root root 1764 Jun 9 09:07 dmesg-efi-165476562015001 -r--r--r-- 1 root root 1795 Jun 9 09:11 dmesg-efi-165476589801001
[Touch-packages] [Bug 1982462] Re: Some modprobe loading services requested by the pstore service fail
This bug was fixed in the package systemd - 245.4-4ubuntu3.18 --- systemd (245.4-4ubuntu3.18) focal; urgency=medium [ Nick Rosbrook ] * core: make sure we don't get confused when setting TERM for a tty fd (LP: #1959475) File: debian/patches/lp1959475-core-make-sure-we-don-t-get-confused-when-setting-TERM-fo.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b10c6853050dde26665caf3b15444d768d2bc498 * shared/calendarspec: when mktime() moves us backwards, jump forward (LP: #1966800) File: debian/patches/lp1966800-shared-calendarspec-when-mktime-moves-us-backwards-jump-f.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1f063541e44f6ff1a6904676d4264a2e49a09594 * network: do not remove localhost address (LP: #1979951) File: debian/patches/lp1979951-network-do-not-remove-localhost-address.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=87f872b8c5451f353601fb606e7fd7a479217cef * units: remove the restart limit on the modprobe@.service (LP: #1982462) File: debian/patches/lp1982462-units-remove-the-restart-limit-on-the-modprobe-.service.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=68353ffaf3539e6a58ef62a8b50850f56eae29ea [ Mustafa Kemal Gilor ] * d/p/lp1978079-efi-pstore-not-cleared-on-boot.patch: pstore: Run after modules are loaded. Thanks to Alexander Graf . (LP: #1978079) Author: Mustafa Kemal Gilor File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6e60756f2079d6408abdb967127a1d9b9a0eba8c -- Nick Rosbrook Wed, 31 Aug 2022 11:27:33 -0400 ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1982462 Title: Some modprobe loading services requested by the pstore service fail Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Jammy: Fix Released Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] It has been detected that some modprobe services fail on UC22 after the jammy upgrade 249.11-0ubuntu3.4: $ systemctl --system --no-ask-password --no-pager list-units --state=failed Failed units: UNIT LOAD ACTIVE SUBDESCRIPTION ● modprobe@chromeos_pstore.service loaded failed failed Load Kernel Module chromeos_pstore ● modprobe@efi_pstore.service loaded failed failed Load Kernel Module efi_pstore ● modprobe@mtdpstore.service loaded failed failed Load Kernel Module mtdpstore ● modprobe@pstore_blk.service loaded failed failed Load Kernel Module pstore_blk ● modprobe@pstore_zone.service loaded failed failed Load Kernel Module pstore_zone ● modprobe@ramoops.service loaded failed failed Load Kernel Module ramoops This happens because of some changes to systemd-pstore.service that now has: After=modprobe@efi_pstore.service modprobe@mtdpstore.service modprobe@chromeos_pstore.service modprobe@ramoops.service modprobe@pstore_zone.service modprobe@pstore_blk.service Wants=modprobe@efi_pstore.service modprobe@mtdpstore.service modprobe@chromeos_pstore.service modprobe@ramoops.service modprobe@pstore_zone.service modprobe@pstore_blk.service This causes too many tries of the modprobe services, that fail in the end with Jul 20 09:02:39 ubuntu systemd[1]: modprobe@chromeos_pstore.service: Start request repeated too quickly. Although we have seen this only on UC22, it potentially can affect classic systems as well, as systemd-pstore.service is re-tried there a few times too. See https://github.com/snapcore/core-base/issues/72 for more details. A fix for this is available upstream: https://github.com/systemd/systemd/commit/9625350e5381a68c1179ae4581e7586c206663e1 [Test Plan] Start the device and check that there is no modprobe-pstore related failed service. This is racy, so a few tries will be needed to make sure things are fine. [Where problems could occur] The modprobe services are usually dependencies from other services, so it should be fine if the retry behavior is controlled by those other services. Risk should be small. If something goes wrong we might see a lot of restarts for these services. [Other Info] Testing should happen on UC22 too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982462/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1966849] Update Released
The verification of the Stable Release Update for gzip has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1966849 Title: gzip exec format error under WSL1 Status in gzip: New Status in gzip package in Ubuntu: Fix Released Status in gzip source package in Jammy: Fix Released Status in gzip source package in Kinetic: Fix Released Bug description: [Impact] * Optimization features included in jammy cause atypical alignment of LOAD ELF sections. This in turn causes failure to execute binaries on WSL1. Upstream have since integrated the optimization features included in jammy, but also reverted alignment to a previously used one. This also results in working binary under WSL1. * Cherry-pick upstream applied revert to alignment to resolve running gzip under WSL1. [Test Plan] * Use powershell to set default WSL version to 1 * Deploy WSL1, unpack and use updated gzip package * gzip --version should execute correctly under WSL 1 [Where problems could occur] * I cannot tell why performance improvement patches introduced alignment change, and if revert of the alignment change affects the performance. Note that this change aligns the codebase closer to what kinetic & upstream now are. [Other Info] * This bug fix is upstream commit https://git.savannah.gnu.org/cgit/gzip.git/commit/gzip.c?id=23a870d14a49803c6d2579071886c1acf497c9d1 --- gzip version 1.10-4ubuntu3 fails to run under WSL1 on Windows 19044.1620, making WSL pretty much unusable. bash: /usr/bin/gzip: cannot execute binary file: Exec format error ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gzip 1.10-4ubuntu3 ProcVersionSignature: Microsoft 4.4.0-19041.1237-Microsoft 4.4.35 Uname: Linux 4.4.0-19041-Microsoft x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Mar 29 06:40:33 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/usr/bin/fish SourcePackage: gzip UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gzip/+bug/1966849/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966849] Re: gzip exec format error under WSL1
This bug was fixed in the package gzip - 1.10-4ubuntu4.1 --- gzip (1.10-4ubuntu4.1) jammy; urgency=medium * Cherry-pick upstream patch to use more portable alignment to resolve failure to execute on WSL1. https://github.com/microsoft/WSL/issues/8219 LP: #1966849 -- Dimitri John Ledkov Mon, 05 Sep 2022 14:33:59 +0100 ** Changed in: gzip (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1966849 Title: gzip exec format error under WSL1 Status in gzip: New Status in gzip package in Ubuntu: Fix Released Status in gzip source package in Jammy: Fix Released Status in gzip source package in Kinetic: Fix Released Bug description: [Impact] * Optimization features included in jammy cause atypical alignment of LOAD ELF sections. This in turn causes failure to execute binaries on WSL1. Upstream have since integrated the optimization features included in jammy, but also reverted alignment to a previously used one. This also results in working binary under WSL1. * Cherry-pick upstream applied revert to alignment to resolve running gzip under WSL1. [Test Plan] * Use powershell to set default WSL version to 1 * Deploy WSL1, unpack and use updated gzip package * gzip --version should execute correctly under WSL 1 [Where problems could occur] * I cannot tell why performance improvement patches introduced alignment change, and if revert of the alignment change affects the performance. Note that this change aligns the codebase closer to what kinetic & upstream now are. [Other Info] * This bug fix is upstream commit https://git.savannah.gnu.org/cgit/gzip.git/commit/gzip.c?id=23a870d14a49803c6d2579071886c1acf497c9d1 --- gzip version 1.10-4ubuntu3 fails to run under WSL1 on Windows 19044.1620, making WSL pretty much unusable. bash: /usr/bin/gzip: cannot execute binary file: Exec format error ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gzip 1.10-4ubuntu3 ProcVersionSignature: Microsoft 4.4.0-19041.1237-Microsoft 4.4.35 Uname: Linux 4.4.0-19041-Microsoft x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Mar 29 06:40:33 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/usr/bin/fish SourcePackage: gzip UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gzip/+bug/1966849/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1982108] Re: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS
This bug was fixed in the package python3.10 - 3.10.6-1~22.04 --- python3.10 (3.10.6-1~22.04) jammy-proposed; urgency=medium * SRU: LP: #1982108: Backport 3.10.6 to 20.04 LTS. python3.10 (3.10.6-1) unstable; urgency=medium * Python 3.10.6 release. [ Leonidas Da Silva Barbosa ] * SECURITY UPDATE: Injection Attack - debian/patches/CVE-2015-20107.patch: Make mailcap refuse to match unsafe filenames/types/param in Lib/mailcap.py, Lib/test/test_mailcap.py. - CVE-2015-20107 python3.10 (3.10.5-1) unstable; urgency=medium * Python 3.10.5 release. * Update VCS attributes. python3.10 (3.10.4-4) unstable; urgency=medium * Source-only upload. * Backport gh-78214: marshal: Stabilize FLAG_REF usage. Closes: #1010368. -- Matthias Klose Wed, 10 Aug 2022 13:40:04 +0200 ** Changed in: python3.10 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2015-20107 ** Changed in: python3-defaults (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1982108 Title: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: Confirmed Status in python3.10 package in Ubuntu: Confirmed Status in python3-defaults source package in Jammy: Fix Released Status in python3-stdlib-extensions source package in Jammy: Fix Committed Status in python3.10 source package in Jammy: Fix Released Bug description: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS we are doing a test rebuild of 22.04 main to check for regressions. test rebuilds at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-jammy.html https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-gcc-jammy.html the first one is the reference test rebuild, the second one the rebuild using updated binutils, GCC and python packages. Analysis: regressions on riscv64 (caused by enabling the tests) are: abseil adsys colord dovecot glib-networking glibc gnome-bluetooth3 gnome-control-center google-perftools json-glib libfprint libgdata memcached mir openvswitch ovn pmdk power-profiles-daemon strace swtpm vim devscripts is not a regression, introduced by a custom dpkg- buildpackage wrapper. binutils and python3-stdlib-extensions are superseded which are part of the planned updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1982108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1982108] Re: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS
This bug was fixed in the package python3-defaults - 3.10.6-1~22.04 --- python3-defaults (3.10.6-1~22.04) jammy-proposed; urgency=medium * SRU: LP: #1982108. Update to Python 3.10.6 in Ubuntu 22.04 LTS. python3-defaults (3.10.6-1) unstable; urgency=medium * Bump version to 3.10.6. python3-defaults (3.10.5-3) unstable; urgency=medium * Source-only upload. -- Matthias Klose Thu, 18 Aug 2022 12:39:04 +0200 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1982108 Title: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: Confirmed Status in python3.10 package in Ubuntu: Confirmed Status in python3-defaults source package in Jammy: Fix Released Status in python3-stdlib-extensions source package in Jammy: Fix Committed Status in python3.10 source package in Jammy: Fix Released Bug description: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS we are doing a test rebuild of 22.04 main to check for regressions. test rebuilds at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-jammy.html https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-gcc-jammy.html the first one is the reference test rebuild, the second one the rebuild using updated binutils, GCC and python packages. Analysis: regressions on riscv64 (caused by enabling the tests) are: abseil adsys colord dovecot glib-networking glibc gnome-bluetooth3 gnome-control-center google-perftools json-glib libfprint libgdata memcached mir openvswitch ovn pmdk power-profiles-daemon strace swtpm vim devscripts is not a regression, introduced by a custom dpkg- buildpackage wrapper. binutils and python3-stdlib-extensions are superseded which are part of the planned updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1982108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1982108] Update Released
The verification of the Stable Release Update for python3-defaults has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1982108 Title: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: Confirmed Status in python3.10 package in Ubuntu: Confirmed Status in python3-defaults source package in Jammy: Fix Released Status in python3-stdlib-extensions source package in Jammy: Fix Committed Status in python3.10 source package in Jammy: Fix Released Bug description: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS we are doing a test rebuild of 22.04 main to check for regressions. test rebuilds at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-jammy.html https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-gcc-jammy.html the first one is the reference test rebuild, the second one the rebuild using updated binutils, GCC and python packages. Analysis: regressions on riscv64 (caused by enabling the tests) are: abseil adsys colord dovecot glib-networking glibc gnome-bluetooth3 gnome-control-center google-perftools json-glib libfprint libgdata memcached mir openvswitch ovn pmdk power-profiles-daemon strace swtpm vim devscripts is not a regression, introduced by a custom dpkg- buildpackage wrapper. binutils and python3-stdlib-extensions are superseded which are part of the planned updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1982108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1897932] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1897932 Title: systemd-repart not packaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Status in systemd package in Debian: Fix Released Bug description: [Impact] systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? The bug reporter would like to use it in their new raspberry pi images where they don't have cloud-init installed. The reporter is already using systemd-growfs, but they are missing the nice partition resizing part (so are using cloud-initramfs-growroot). Furthermore, in the mkosi image builder (https://github.com/systemd/mkosi), the systemd/mkosi developers would like to start using systemd-repart for partitioning. Unfortunately, they're currently blocked on this because 22.04 doesn't ship systemd- repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy and will do so until the next Ubuntu LTS is released. If we have to wait for the next LTS to be released, we'll have to wait for a considerable amount of time before we're able to start using systemd- repart. Being able to use systemd-repart will allow the systemd/mkosi developers to take advantage of its improved interface compared to sfdisk, as well as its builtin protections against race conditions surrounding the use of loop devices. The systemd/mkosi developers expect to be able to get rid of some nasty loop device failure in mkosi by using systemd-repart. [Test Plan] This is a missing extra executable. Once enabled it has self-tests in the build-time unit tests, and also a regression test in the autopkgtest 'upstream' suite. * Attach (local) build-log showing the systemd-repart self-tests passing, as found in build-deb/meson-logs/testlog.txt * Attach autopkgtest logs showing the regression tests passing (especially TEST-58-REPART from "upstream-2" testsuite) * Test upgrade-path Jammy->Kinetic to make sure systemd-repart is properly replaced by Kinetic's "systemd" binary package [Where problems could occur] Shipping systemd-repart will come with no additional risk. While there is a systemd-repart.service that runs on boot, it's configured to not do anything if no config files are shipped with the system or provided by the user. As such, the service, if enabled, will effectively be a noop. Aside from the service, there's the CLI tool systemd-repart and the accompanying man pages that will be shipped as part of the systemd package. Given that there's no risk involved with enabling systemd-repart, and given the useful features it provides, the systemd/mkosi developers would like to request that systemd-repart be enabled in Ubuntu and backported to Jammy so that they can start adopting it in mkosi. Runtime behavior of existing components is not affected by the build config change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897932/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1975667] Re: systemd-resolved does not reset DNS server and search domain list properly after VPN disconnect
This bug was fixed in the package systemd - 249.11-0ubuntu3.6 --- systemd (249.11-0ubuntu3.6) jammy; urgency=medium * Deny-list TEST-58-REPART on ppc64el (LP: #1988994) File: debian/patches/lp1988994-Deny-list-TEST-58-REPART-on-ppc64el.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d2ed3cc1d223bf35015b15ff83b50156b58f0f38 systemd (249.11-0ubuntu3.5) jammy; urgency=medium [ Nick Rosbrook ] * Ensure dns_search_domain_unlink_marked removes all marked domains (LP: #1975667) File: debian/patches/lp1975667-Ensure-dns_search_domain_unlink_marked-removes-all-marked.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=919d5ddedd5bb8b45ab9437bf42d66c2821bb074 * core,firstboot: workaround timezone issues on Ubuntu Core (LP: #1981042) Thanks to Robert Ancell for preparing the patch. File: debian/patches/lp1981042-core-firstboot-workaround-timezone-issues-caused-by-Ubunt.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b15546361b549217908fb6ca5d473be23d7fa757 * network: do not remove localhost address (LP: #1979951) File: debian/patches/lp1979951-network-do-not-remove-localhost-address.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2cd88391cce9fe95a486ae6dd214c12f236f3881 * units: remove the restart limit on the modprobe@.service (LP: #1982462) File: debian/patches/lp1982462-units-remove-the-restart-limit-on-the-modprobe-.service.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8f0acd1b2fbb8eed1259c34963e5e9b201bef900 * pstore: do not try to load mtdpstore (LP: #1981622) File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=15225032c3657f5906ee49d48929f9295a8664a0 * core/mount: downgrade log level about several mkdir failures (LP: #1979952) Files: - debian/patches/lp1979952-Revert-core-mount-fail-early-if-directory-cannot-be-creat.patch - debian/patches/lp1979952-core-mount-downgrade-log-level-about-several-mkdir-failur.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ee8cfcf500698fab2e990de291ecf4c3ab87a4ae * debian/control: add Recommends: systemd-hwe-hwdb to udev. The systemd-hwe-hwdb brings in additional hwdb rules for HWE, so we want those installed with udev by default. File: debian/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4a7a3258c33201cca305956820fcc6bcd6052d76 * hwdb: implement --root option for systemd-hwdb query (LP: #1988078) Files: - debian/libsystemd0.symbols - debian/patches/lp1988078-hwdb-implement-root-option-for-systemd-hwdb-query.patch - debian/patches/lp1988078-sd-hwdb-add-sd_hwdb_new_from_path.patch - debian/patches/lp1988078-sd-hwdb-include-sys-stat.h-in-hwdb-internal.h.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=937fef96c858f2f2042bf71032f315647c14add0 [ Luca Boccassi ] * Enable systemd-repart and ship it in a new systemd-repart package. (LP: #1897932) Add fdisk as test dependency, needed by test-repart which calls sfdisk. Add libfdisk-dev/libssl-dev as dependencies, needed for systemd-repart. Author: Luca Boccassi Files: - debian/control - debian/rules - debian/systemd-repart.install https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=debbc5e9362522210096ae5fa9da48378791e381 [ Lukas Märdian ] * Add sd-repart as test depend, to avoid skipping TEST-58-REPART File: debian/tests/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=669190653f06a6554ddf9725cbeccac65149df23 -- Nick Rosbrook Fri, 09 Sep 2022 14:47:16 -0400 ** Changed in: systemd (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1975667 Title: systemd-resolved does not reset DNS server and search domain list properly after VPN disconnect Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] Networking components such as VPNs that rely on systemd-resolved's API to configure search domains may inadvertently leave the network configuration in a bad state. This is a result of a broken systemd- resolved API. [Test Plan] * On a jammy host, configure a couple search domains with resolvectl: $ resolvectl domain search1.internal search2.internal $ resolvectl domain * In any case, both domains should be displayed. Then, attempt to clear the configured domains: $ resolvectl domain "" $ resolvectl domain
[Touch-packages] [Bug 1897932] Re: systemd-repart not packaged
This bug was fixed in the package systemd - 249.11-0ubuntu3.6 --- systemd (249.11-0ubuntu3.6) jammy; urgency=medium * Deny-list TEST-58-REPART on ppc64el (LP: #1988994) File: debian/patches/lp1988994-Deny-list-TEST-58-REPART-on-ppc64el.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d2ed3cc1d223bf35015b15ff83b50156b58f0f38 systemd (249.11-0ubuntu3.5) jammy; urgency=medium [ Nick Rosbrook ] * Ensure dns_search_domain_unlink_marked removes all marked domains (LP: #1975667) File: debian/patches/lp1975667-Ensure-dns_search_domain_unlink_marked-removes-all-marked.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=919d5ddedd5bb8b45ab9437bf42d66c2821bb074 * core,firstboot: workaround timezone issues on Ubuntu Core (LP: #1981042) Thanks to Robert Ancell for preparing the patch. File: debian/patches/lp1981042-core-firstboot-workaround-timezone-issues-caused-by-Ubunt.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b15546361b549217908fb6ca5d473be23d7fa757 * network: do not remove localhost address (LP: #1979951) File: debian/patches/lp1979951-network-do-not-remove-localhost-address.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2cd88391cce9fe95a486ae6dd214c12f236f3881 * units: remove the restart limit on the modprobe@.service (LP: #1982462) File: debian/patches/lp1982462-units-remove-the-restart-limit-on-the-modprobe-.service.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8f0acd1b2fbb8eed1259c34963e5e9b201bef900 * pstore: do not try to load mtdpstore (LP: #1981622) File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=15225032c3657f5906ee49d48929f9295a8664a0 * core/mount: downgrade log level about several mkdir failures (LP: #1979952) Files: - debian/patches/lp1979952-Revert-core-mount-fail-early-if-directory-cannot-be-creat.patch - debian/patches/lp1979952-core-mount-downgrade-log-level-about-several-mkdir-failur.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ee8cfcf500698fab2e990de291ecf4c3ab87a4ae * debian/control: add Recommends: systemd-hwe-hwdb to udev. The systemd-hwe-hwdb brings in additional hwdb rules for HWE, so we want those installed with udev by default. File: debian/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4a7a3258c33201cca305956820fcc6bcd6052d76 * hwdb: implement --root option for systemd-hwdb query (LP: #1988078) Files: - debian/libsystemd0.symbols - debian/patches/lp1988078-hwdb-implement-root-option-for-systemd-hwdb-query.patch - debian/patches/lp1988078-sd-hwdb-add-sd_hwdb_new_from_path.patch - debian/patches/lp1988078-sd-hwdb-include-sys-stat.h-in-hwdb-internal.h.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=937fef96c858f2f2042bf71032f315647c14add0 [ Luca Boccassi ] * Enable systemd-repart and ship it in a new systemd-repart package. (LP: #1897932) Add fdisk as test dependency, needed by test-repart which calls sfdisk. Add libfdisk-dev/libssl-dev as dependencies, needed for systemd-repart. Author: Luca Boccassi Files: - debian/control - debian/rules - debian/systemd-repart.install https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=debbc5e9362522210096ae5fa9da48378791e381 [ Lukas Märdian ] * Add sd-repart as test depend, to avoid skipping TEST-58-REPART File: debian/tests/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=669190653f06a6554ddf9725cbeccac65149df23 -- Nick Rosbrook Fri, 09 Sep 2022 14:47:16 -0400 ** Changed in: systemd (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1897932 Title: systemd-repart not packaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Status in systemd package in Debian: Fix Released Bug description: [Impact] systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? The bug reporter would like to use it in their new raspberry pi images where they don't have cloud-init installed. The reporter is already using systemd-growfs, but they are missing the nice partition resizing part (so are using cloud-initramfs-growroot). Furthermore, in the mkosi image builder (https://github.com/systemd/mkosi), the systemd/mkosi developers would like to start using
[Touch-packages] [Bug 1975667] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1975667 Title: systemd-resolved does not reset DNS server and search domain list properly after VPN disconnect Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] Networking components such as VPNs that rely on systemd-resolved's API to configure search domains may inadvertently leave the network configuration in a bad state. This is a result of a broken systemd- resolved API. [Test Plan] * On a jammy host, configure a couple search domains with resolvectl: $ resolvectl domain search1.internal search2.internal $ resolvectl domain * In any case, both domains should be displayed. Then, attempt to clear the configured domains: $ resolvectl domain "" $ resolvectl domain * On a patched system, the two domains should no longer be displayed. On an un-patched system, one of the domains will still be configured. [Where problems could occur] This patch touches the logic that configures search domains in systemd-resolved. If the patch caused regressions, it would be related to the set of configured search domains. [Original Description] Hi, in Ubuntu 21.10 I am facing a problem with DNS server list and search domain list is not properly reset back to the previous values after a VPN is disconnected. I reproduced this in Ubuntu 21.10 instance which was upgraded from the older version of Ubuntu as well as in Live USB Ubuntu 21.10 so it is not an "upgrade issue". I use this resolv.conf symlink: /etc/resolv.conf -> ../run/systemd/resolve/resolv.conf Actual behavior: VPN connect will add VPN's DNS servers and search domains into /etc/resolv.conf. When VPN is disconnected there are some of the VPN's DNS server and search domain entries left there, so it is not reset back properly. Desired behavior: VPN connect will add VPN's DNS servers and search domains into /etc/resolv.conf. When VPN is disconnected DNS servers and search domain list is restored to exactly the same state as was prior to the VPN connection. Steps for reproducing: 1. Before VPN is connected this is the DNS server and search domain list in /etc/resolv.conf: nameserver 192.168.122.1 search . 2. Once the VPN is connected, we see there were VPN's DNS server and serach domain list entries added: nameserver 2xx.xx.xx.x0 nameserver 2xx.xx.xx.x1 nameserver 192.168.122.1 search domain1.local domain2.internal domain3.internal 3. After VPN disconnection, we see the DNS server and search domain list in /etc/resolv.conf is not restored to the state at point (1.) and some entries from VPN is being kept there: nameserver 2xx.xx.xx.x1 nameserver 192.168.122.1 search domain2.internal domain3.internal ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: systemd 248.3-1ubuntu8 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Wed May 25 06:06:05 2022 LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED]
[Touch-packages] [Bug 1981622] Re: mtd device must be supplied (device name is empty)
This bug was fixed in the package systemd - 249.11-0ubuntu3.6
---
systemd (249.11-0ubuntu3.6) jammy; urgency=medium
* Deny-list TEST-58-REPART on ppc64el (LP: #1988994)
File: debian/patches/lp1988994-Deny-list-TEST-58-REPART-on-ppc64el.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d2ed3cc1d223bf35015b15ff83b50156b58f0f38
systemd (249.11-0ubuntu3.5) jammy; urgency=medium
[ Nick Rosbrook ]
* Ensure dns_search_domain_unlink_marked removes all marked domains (LP:
#1975667)
File:
debian/patches/lp1975667-Ensure-dns_search_domain_unlink_marked-removes-all-marked.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=919d5ddedd5bb8b45ab9437bf42d66c2821bb074
* core,firstboot: workaround timezone issues on Ubuntu Core (LP: #1981042)
Thanks to Robert Ancell for preparing the patch.
File:
debian/patches/lp1981042-core-firstboot-workaround-timezone-issues-caused-by-Ubunt.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b15546361b549217908fb6ca5d473be23d7fa757
* network: do not remove localhost address (LP: #1979951)
File: debian/patches/lp1979951-network-do-not-remove-localhost-address.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2cd88391cce9fe95a486ae6dd214c12f236f3881
* units: remove the restart limit on the modprobe@.service (LP: #1982462)
File:
debian/patches/lp1982462-units-remove-the-restart-limit-on-the-modprobe-.service.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8f0acd1b2fbb8eed1259c34963e5e9b201bef900
* pstore: do not try to load mtdpstore (LP: #1981622)
File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=15225032c3657f5906ee49d48929f9295a8664a0
* core/mount: downgrade log level about several mkdir failures (LP: #1979952)
Files:
-
debian/patches/lp1979952-Revert-core-mount-fail-early-if-directory-cannot-be-creat.patch
-
debian/patches/lp1979952-core-mount-downgrade-log-level-about-several-mkdir-failur.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ee8cfcf500698fab2e990de291ecf4c3ab87a4ae
* debian/control: add Recommends: systemd-hwe-hwdb to udev.
The systemd-hwe-hwdb brings in additional hwdb rules for HWE, so we want
those installed with udev by default.
File: debian/control
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4a7a3258c33201cca305956820fcc6bcd6052d76
* hwdb: implement --root option for systemd-hwdb query (LP: #1988078)
Files:
- debian/libsystemd0.symbols
-
debian/patches/lp1988078-hwdb-implement-root-option-for-systemd-hwdb-query.patch
- debian/patches/lp1988078-sd-hwdb-add-sd_hwdb_new_from_path.patch
-
debian/patches/lp1988078-sd-hwdb-include-sys-stat.h-in-hwdb-internal.h.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=937fef96c858f2f2042bf71032f315647c14add0
[ Luca Boccassi ]
* Enable systemd-repart and ship it in a new systemd-repart package.
(LP: #1897932)
Add fdisk as test dependency, needed by test-repart which calls sfdisk.
Add libfdisk-dev/libssl-dev as dependencies, needed for systemd-repart.
Author: Luca Boccassi
Files:
- debian/control
- debian/rules
- debian/systemd-repart.install
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=debbc5e9362522210096ae5fa9da48378791e381
[ Lukas Märdian ]
* Add sd-repart as test depend, to avoid skipping TEST-58-REPART
File: debian/tests/control
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=669190653f06a6554ddf9725cbeccac65149df23
-- Nick Rosbrook Fri, 09 Sep 2022
14:47:16 -0400
** Changed in: systemd (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1981622
Title:
mtd device must be supplied (device name is empty)
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Invalid
Status in systemd source package in Jammy:
Fix Released
Bug description:
[WORKAROUND]
This will NOT fix a system that is not booting, because the "mtd
device must be supplied (device name is empty)" message is not the
cause of failed boots. This work around is only for those who are
annoyed by the error message, but are otherwise not experiencing any
issues.
If you are not able to boot your system, but you see this error
message, please open a separate bug with your journalctl and dmesg
logs.
# cp /{lib,etc}/systemd/system/systemd-pstore.service
# sed -i 's/modprobe@mtdpstore.service //'
[Touch-packages] [Bug 1979951] Re: 127.0.0.1/::1 removed from loopback interface if you configure extra IPs on lo (r104 regression/behaviour change)
This bug was fixed in the package systemd - 249.11-0ubuntu3.6 --- systemd (249.11-0ubuntu3.6) jammy; urgency=medium * Deny-list TEST-58-REPART on ppc64el (LP: #1988994) File: debian/patches/lp1988994-Deny-list-TEST-58-REPART-on-ppc64el.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d2ed3cc1d223bf35015b15ff83b50156b58f0f38 systemd (249.11-0ubuntu3.5) jammy; urgency=medium [ Nick Rosbrook ] * Ensure dns_search_domain_unlink_marked removes all marked domains (LP: #1975667) File: debian/patches/lp1975667-Ensure-dns_search_domain_unlink_marked-removes-all-marked.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=919d5ddedd5bb8b45ab9437bf42d66c2821bb074 * core,firstboot: workaround timezone issues on Ubuntu Core (LP: #1981042) Thanks to Robert Ancell for preparing the patch. File: debian/patches/lp1981042-core-firstboot-workaround-timezone-issues-caused-by-Ubunt.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b15546361b549217908fb6ca5d473be23d7fa757 * network: do not remove localhost address (LP: #1979951) File: debian/patches/lp1979951-network-do-not-remove-localhost-address.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2cd88391cce9fe95a486ae6dd214c12f236f3881 * units: remove the restart limit on the modprobe@.service (LP: #1982462) File: debian/patches/lp1982462-units-remove-the-restart-limit-on-the-modprobe-.service.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8f0acd1b2fbb8eed1259c34963e5e9b201bef900 * pstore: do not try to load mtdpstore (LP: #1981622) File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=15225032c3657f5906ee49d48929f9295a8664a0 * core/mount: downgrade log level about several mkdir failures (LP: #1979952) Files: - debian/patches/lp1979952-Revert-core-mount-fail-early-if-directory-cannot-be-creat.patch - debian/patches/lp1979952-core-mount-downgrade-log-level-about-several-mkdir-failur.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ee8cfcf500698fab2e990de291ecf4c3ab87a4ae * debian/control: add Recommends: systemd-hwe-hwdb to udev. The systemd-hwe-hwdb brings in additional hwdb rules for HWE, so we want those installed with udev by default. File: debian/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4a7a3258c33201cca305956820fcc6bcd6052d76 * hwdb: implement --root option for systemd-hwdb query (LP: #1988078) Files: - debian/libsystemd0.symbols - debian/patches/lp1988078-hwdb-implement-root-option-for-systemd-hwdb-query.patch - debian/patches/lp1988078-sd-hwdb-add-sd_hwdb_new_from_path.patch - debian/patches/lp1988078-sd-hwdb-include-sys-stat.h-in-hwdb-internal.h.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=937fef96c858f2f2042bf71032f315647c14add0 [ Luca Boccassi ] * Enable systemd-repart and ship it in a new systemd-repart package. (LP: #1897932) Add fdisk as test dependency, needed by test-repart which calls sfdisk. Add libfdisk-dev/libssl-dev as dependencies, needed for systemd-repart. Author: Luca Boccassi Files: - debian/control - debian/rules - debian/systemd-repart.install https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=debbc5e9362522210096ae5fa9da48378791e381 [ Lukas Märdian ] * Add sd-repart as test depend, to avoid skipping TEST-58-REPART File: debian/tests/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=669190653f06a6554ddf9725cbeccac65149df23 -- Nick Rosbrook Fri, 09 Sep 2022 14:47:16 -0400 ** Changed in: systemd (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1979951 Title: 127.0.0.1/::1 removed from loopback interface if you configure extra IPs on lo (r104 regression/behaviour change) Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in netplan.io source package in Focal: New Status in systemd source package in Focal: Fix Released Status in netplan.io source package in Jammy: New Status in systemd source package in Jammy: Fix Released Bug description: [Impact] Users who wish to configure additional addresses on lo may inadvertently remove the 127.0.0.1/8 address from the interface. And, because this only happens on the second invocation of `netplan apply`, it can create confusing breakages for users. Although this is not a recommended configuration, it was
[Touch-packages] [Bug 1979951] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1979951 Title: 127.0.0.1/::1 removed from loopback interface if you configure extra IPs on lo (r104 regression/behaviour change) Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in netplan.io source package in Focal: New Status in systemd source package in Focal: Fix Released Status in netplan.io source package in Jammy: New Status in systemd source package in Jammy: Fix Released Bug description: [Impact] Users who wish to configure additional addresses on lo may inadvertently remove the 127.0.0.1/8 address from the interface. And, because this only happens on the second invocation of `netplan apply`, it can create confusing breakages for users. Although this is not a recommended configuration, it was previously supported and the current behavior is a regression. [Test Plan] * Configure additional addresses on the lo interface. I am testing in a LXD container, so I added the following to /etc/netplan/10-lxc.yaml under `ethernets:` lo: addresses: ["10.10.10.17/24","10.10.10.19/24"] * Apply the config, and then inspect the lo interface's addresses: $ netplan apply $ ip addr show dev lo * Observe that the 127.0.0.1/8 address is still present. Now, run the same commands again: $ netplan apply $ ip addr show dev lo * On an affected system, observe that the 127.0.0.1/8 address is now gone. On a patched system, the address should still be present. [Where problems could occur] The patch removes cases where systemd-networkd will drop foreign addresses from a managed link. If problems were to occur, it would be related to the addresses configured on a managed link. [Original Description] If you configure the loopback interface using netplan without listing the standard loopback addresses (127.0.0.1 / ::1) that are auto- configured on boot then they are removed by netplan in r104+ but were not in r103. Confusingly this only happens the second time "netplan apply" is invoked and not the first time. There is some argument this is not a valid configuration, however - It worked on r103 and broke in the r104 SRU for 20.04 and breaks on upgrade - Since it only occurs on the second "netplan apply" it is likely people will accidentally create a configuration that on first verification works but breaks later - Adding addresses to a loopback or dummy interface is a common need - There is no dummy interface support in Netplan - Removing the loopback IP doesn't immediately cause obvious breakage in an SSH session but causes all sorts of hard to diagnose issues with applications Thus I consider this a high priority regression because of the multiple ways this can break a system at an unexpected/unrelated time to when the original change was made. As a workaround you can add 127.0.0.1/::1 to the file and this seems to generally work and product almost the same configuration with the exception that "brd 127.255.255.255" is added to the "ip addr" output compared to the auto-created configuration. All of the different routing tables seem otherwise the tame. = Test Case = (1) Add IP configuration for lo to /etc/netplan/lo.yaml lo: match: name: lo addresses: - 10.10.10.17/24 - 10.10.10.19/24 (2) Run "netplan apply" and observe the "ip addr show dev lo" output. Expected: 127.0.0.1/::1 are still there. (3) Run "netplan apply" a second time and observe the "ip addr show dev lo" output. Expected: 127.0.0.1/::1 are now removed. (4) Repeat the same test under netplan r103. Expected: 127.0.0.1/::1 are still there in both cases. = Observations = I found this change of behaviour happens only in r104. It is suspected but not clear that this is due to the configuraiton diffing behaviour introduced in r104. It's not clear to me why it doesn't happen on the first "netplan apply". I also found a recent upstream systemd commit to prevent networkd removing 127.0.0.1/::1 which solves this issue on r104 as well. It's possible this is a better fix to backport to solve this: https://github.com/systemd/systemd/commit/b69bfa43052586cd6894c32d7d3d447195539ec5 Reverting to r103 *or* running a newer systemd with that patch resolves the issue on 20.04 and 22.04 in my
[Touch-packages] [Bug 1979952] Re: Bind mount to NFS mount fails on Ubuntu 22.04
This bug was fixed in the package systemd - 249.11-0ubuntu3.6 --- systemd (249.11-0ubuntu3.6) jammy; urgency=medium * Deny-list TEST-58-REPART on ppc64el (LP: #1988994) File: debian/patches/lp1988994-Deny-list-TEST-58-REPART-on-ppc64el.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d2ed3cc1d223bf35015b15ff83b50156b58f0f38 systemd (249.11-0ubuntu3.5) jammy; urgency=medium [ Nick Rosbrook ] * Ensure dns_search_domain_unlink_marked removes all marked domains (LP: #1975667) File: debian/patches/lp1975667-Ensure-dns_search_domain_unlink_marked-removes-all-marked.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=919d5ddedd5bb8b45ab9437bf42d66c2821bb074 * core,firstboot: workaround timezone issues on Ubuntu Core (LP: #1981042) Thanks to Robert Ancell for preparing the patch. File: debian/patches/lp1981042-core-firstboot-workaround-timezone-issues-caused-by-Ubunt.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b15546361b549217908fb6ca5d473be23d7fa757 * network: do not remove localhost address (LP: #1979951) File: debian/patches/lp1979951-network-do-not-remove-localhost-address.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2cd88391cce9fe95a486ae6dd214c12f236f3881 * units: remove the restart limit on the modprobe@.service (LP: #1982462) File: debian/patches/lp1982462-units-remove-the-restart-limit-on-the-modprobe-.service.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8f0acd1b2fbb8eed1259c34963e5e9b201bef900 * pstore: do not try to load mtdpstore (LP: #1981622) File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=15225032c3657f5906ee49d48929f9295a8664a0 * core/mount: downgrade log level about several mkdir failures (LP: #1979952) Files: - debian/patches/lp1979952-Revert-core-mount-fail-early-if-directory-cannot-be-creat.patch - debian/patches/lp1979952-core-mount-downgrade-log-level-about-several-mkdir-failur.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ee8cfcf500698fab2e990de291ecf4c3ab87a4ae * debian/control: add Recommends: systemd-hwe-hwdb to udev. The systemd-hwe-hwdb brings in additional hwdb rules for HWE, so we want those installed with udev by default. File: debian/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4a7a3258c33201cca305956820fcc6bcd6052d76 * hwdb: implement --root option for systemd-hwdb query (LP: #1988078) Files: - debian/libsystemd0.symbols - debian/patches/lp1988078-hwdb-implement-root-option-for-systemd-hwdb-query.patch - debian/patches/lp1988078-sd-hwdb-add-sd_hwdb_new_from_path.patch - debian/patches/lp1988078-sd-hwdb-include-sys-stat.h-in-hwdb-internal.h.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=937fef96c858f2f2042bf71032f315647c14add0 [ Luca Boccassi ] * Enable systemd-repart and ship it in a new systemd-repart package. (LP: #1897932) Add fdisk as test dependency, needed by test-repart which calls sfdisk. Add libfdisk-dev/libssl-dev as dependencies, needed for systemd-repart. Author: Luca Boccassi Files: - debian/control - debian/rules - debian/systemd-repart.install https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=debbc5e9362522210096ae5fa9da48378791e381 [ Lukas Märdian ] * Add sd-repart as test depend, to avoid skipping TEST-58-REPART File: debian/tests/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=669190653f06a6554ddf9725cbeccac65149df23 -- Nick Rosbrook Fri, 09 Sep 2022 14:47:16 -0400 ** Changed in: systemd (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1979952 Title: Bind mount to NFS mount fails on Ubuntu 22.04 Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] Some NFS setups that have worked on previous versions of Ubuntu are now broken. Specifically, when creating a bind mount, systemd will fail if the directory already exists on NFS. [Test Plan] This test plan requires an NFS server to be in place. The exact setup is not important, but for the purposes of this test plan we will assume the server exports /data, which contains a directory called home. * Make sure nfs-common is installed: $ apt install nfs-common -y * Check the NFS
[Touch-packages] [Bug 1979952] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1979952 Title: Bind mount to NFS mount fails on Ubuntu 22.04 Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] Some NFS setups that have worked on previous versions of Ubuntu are now broken. Specifically, when creating a bind mount, systemd will fail if the directory already exists on NFS. [Test Plan] This test plan requires an NFS server to be in place. The exact setup is not important, but for the purposes of this test plan we will assume the server exports /data, which contains a directory called home. * Make sure nfs-common is installed: $ apt install nfs-common -y * Check the NFS server exports using showmount: $ showmount -e $NFS_SERVER_IP Export list for $NFS_SERVER_IP: /data * * Add the appropriate entries to /etc/fstab. In this example, we will make /home2 a bind mount to /data/home: # /etc/fstab $NFS_SERVER_IP:/data /data nfs defaults,nfsvers=3 0 0 /data/home /home2 none bind,_netdev,x-systemd.requires-mounts-for=/data 0 0 * Check systemctl status home2.mount. On an affected system, we should see a permission denied error: $ systemctl status home2.mount x home2.mount - /home2 Loaded: loaded (/etc/fstab; generated) Active: failed (Result: resources) Where: /home2 What: /data/home Docs: man:fstab(5) man:systemd-fstab-generator(8) systemd[1]: home2.mount: Failed to make bind mount source '/data/home': Permission denied systemd[1]: home2.mount: Failed to run 'mount' task: Permission denied systemd[1]: home2.mount: Failed with result 'resources'. systemd[1]: Failed to mount /home2. * On a patched system, we expect /home2 to be mounted successfully. [Where problems could occur] The patch makes it so that systemd will not fail bind mounts immediately if creating the directory fails. Thus, any regressions would be seen during bind mounts with systemd. N.B. that this patch restores previous behavior in systemd. [Original Description] I have the following setup: - /data is an NFS mount. - /home is a bind mount to /data/home. Configured in /etc/fstab with these lines: $FILE_SERVER:/data /data nfs defaults 0 0 /data/home /home none bind,_netdev,x-systemd.requires-mounts-for=/data 0 0 This has worked with the same configuration for me on at least Ubuntu 18.04 and Ubuntu 20.04, but on Ubuntu 22.04 the mount of /home fails when attempted by systemd. So not only is /home not mounted after boot, but also when I run "sudo systemctl start home.mount", it fails. The journal entries are this: sudo[1316]: wendler : TTY=pts/0 ; PWD=/home/wendler ; USER=root ; COMMAND=/usr/bin/systemctl start home.mount sudo[1316]: pam_unix(sudo:session): session opened for user root(uid=0) by wendler(uid=1000) systemd[1]: home.mount: Directory /home to mount over is not empty, mounting anyway. systemd[1]: home.mount: Failed to make bind mount source '/data/home': Permission denied systemd[1]: home.mount: Failed to run 'mount' task: Permission denied systemd[1]: home.mount: Failed with result 'resources'. systemd[1]: Failed to mount /home. However, when I run "sudo mount /home" it works. Now the weird thing is that after I have mounted /home manually once and unmounted it again, then "sudo systemctl start home.mount" suddenly also works! But of course only until the next reboot. And even if I just do "ls /data" once (either as root or as my user), it also makes "sudo systemctl start home.mount" start working! To be fully clear: - Booting the system (/home fails to mount) - sudo systemctl start home.mount # fails - sudo ls /data # shows correct output - sudo systemctl start home.mount # works! Additional information: The NFS export for /data has root_squash set and if I remove this option, the bind mount of /home works as it should. However, both /data and /data/home have mode rwxr-xr-x, so root is able to enter and read these directories even despite root_squash. It is not a network or mount-order problem. Not only is the bind mount to /home correctly attempted after /data is mounted during boot,
[Touch-packages] [Bug 1981042] Re: /etc/localtime symlink not correctly handled when using /etc/writable
This bug was fixed in the package systemd - 249.11-0ubuntu3.6 --- systemd (249.11-0ubuntu3.6) jammy; urgency=medium * Deny-list TEST-58-REPART on ppc64el (LP: #1988994) File: debian/patches/lp1988994-Deny-list-TEST-58-REPART-on-ppc64el.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d2ed3cc1d223bf35015b15ff83b50156b58f0f38 systemd (249.11-0ubuntu3.5) jammy; urgency=medium [ Nick Rosbrook ] * Ensure dns_search_domain_unlink_marked removes all marked domains (LP: #1975667) File: debian/patches/lp1975667-Ensure-dns_search_domain_unlink_marked-removes-all-marked.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=919d5ddedd5bb8b45ab9437bf42d66c2821bb074 * core,firstboot: workaround timezone issues on Ubuntu Core (LP: #1981042) Thanks to Robert Ancell for preparing the patch. File: debian/patches/lp1981042-core-firstboot-workaround-timezone-issues-caused-by-Ubunt.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b15546361b549217908fb6ca5d473be23d7fa757 * network: do not remove localhost address (LP: #1979951) File: debian/patches/lp1979951-network-do-not-remove-localhost-address.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2cd88391cce9fe95a486ae6dd214c12f236f3881 * units: remove the restart limit on the modprobe@.service (LP: #1982462) File: debian/patches/lp1982462-units-remove-the-restart-limit-on-the-modprobe-.service.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8f0acd1b2fbb8eed1259c34963e5e9b201bef900 * pstore: do not try to load mtdpstore (LP: #1981622) File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=15225032c3657f5906ee49d48929f9295a8664a0 * core/mount: downgrade log level about several mkdir failures (LP: #1979952) Files: - debian/patches/lp1979952-Revert-core-mount-fail-early-if-directory-cannot-be-creat.patch - debian/patches/lp1979952-core-mount-downgrade-log-level-about-several-mkdir-failur.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ee8cfcf500698fab2e990de291ecf4c3ab87a4ae * debian/control: add Recommends: systemd-hwe-hwdb to udev. The systemd-hwe-hwdb brings in additional hwdb rules for HWE, so we want those installed with udev by default. File: debian/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4a7a3258c33201cca305956820fcc6bcd6052d76 * hwdb: implement --root option for systemd-hwdb query (LP: #1988078) Files: - debian/libsystemd0.symbols - debian/patches/lp1988078-hwdb-implement-root-option-for-systemd-hwdb-query.patch - debian/patches/lp1988078-sd-hwdb-add-sd_hwdb_new_from_path.patch - debian/patches/lp1988078-sd-hwdb-include-sys-stat.h-in-hwdb-internal.h.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=937fef96c858f2f2042bf71032f315647c14add0 [ Luca Boccassi ] * Enable systemd-repart and ship it in a new systemd-repart package. (LP: #1897932) Add fdisk as test dependency, needed by test-repart which calls sfdisk. Add libfdisk-dev/libssl-dev as dependencies, needed for systemd-repart. Author: Luca Boccassi Files: - debian/control - debian/rules - debian/systemd-repart.install https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=debbc5e9362522210096ae5fa9da48378791e381 [ Lukas Märdian ] * Add sd-repart as test depend, to avoid skipping TEST-58-REPART File: debian/tests/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=669190653f06a6554ddf9725cbeccac65149df23 -- Nick Rosbrook Fri, 09 Sep 2022 14:47:16 -0400 ** Changed in: systemd (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1981042 Title: /etc/localtime symlink not correctly handled when using /etc/writable Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] When using /etc/writable (e.g. Ubuntu Core) /etc/localtime is a symlink to /etc/writable/localtime (which in itself if a symlink). Systemd doesn't handle this correctly when doing firstboot or using inotify to watch for changes to localtime. [Test Plan] This is somewhat hard to test, the following situations need to be reproduced: - On firstboot the timezone link will not be read correctly, it will with this change. - Starting a timer unit and then changing timezone will cause it not to occur
[Touch-packages] [Bug 1981042] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1981042 Title: /etc/localtime symlink not correctly handled when using /etc/writable Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] When using /etc/writable (e.g. Ubuntu Core) /etc/localtime is a symlink to /etc/writable/localtime (which in itself if a symlink). Systemd doesn't handle this correctly when doing firstboot or using inotify to watch for changes to localtime. [Test Plan] This is somewhat hard to test, the following situations need to be reproduced: - On firstboot the timezone link will not be read correctly, it will with this change. - Starting a timer unit and then changing timezone will cause it not to occur at the correct time. [Where problems could occur] This could potentially break other users of localtime, however the change is similar to existing changes which have been in Ubuntu's version of systemd for some time. The change detects the /etc/writable case and if not should have the same existing behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981042/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1982462] Re: Some modprobe loading services requested by the pstore service fail
This bug was fixed in the package systemd - 249.11-0ubuntu3.6 --- systemd (249.11-0ubuntu3.6) jammy; urgency=medium * Deny-list TEST-58-REPART on ppc64el (LP: #1988994) File: debian/patches/lp1988994-Deny-list-TEST-58-REPART-on-ppc64el.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d2ed3cc1d223bf35015b15ff83b50156b58f0f38 systemd (249.11-0ubuntu3.5) jammy; urgency=medium [ Nick Rosbrook ] * Ensure dns_search_domain_unlink_marked removes all marked domains (LP: #1975667) File: debian/patches/lp1975667-Ensure-dns_search_domain_unlink_marked-removes-all-marked.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=919d5ddedd5bb8b45ab9437bf42d66c2821bb074 * core,firstboot: workaround timezone issues on Ubuntu Core (LP: #1981042) Thanks to Robert Ancell for preparing the patch. File: debian/patches/lp1981042-core-firstboot-workaround-timezone-issues-caused-by-Ubunt.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b15546361b549217908fb6ca5d473be23d7fa757 * network: do not remove localhost address (LP: #1979951) File: debian/patches/lp1979951-network-do-not-remove-localhost-address.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2cd88391cce9fe95a486ae6dd214c12f236f3881 * units: remove the restart limit on the modprobe@.service (LP: #1982462) File: debian/patches/lp1982462-units-remove-the-restart-limit-on-the-modprobe-.service.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8f0acd1b2fbb8eed1259c34963e5e9b201bef900 * pstore: do not try to load mtdpstore (LP: #1981622) File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=15225032c3657f5906ee49d48929f9295a8664a0 * core/mount: downgrade log level about several mkdir failures (LP: #1979952) Files: - debian/patches/lp1979952-Revert-core-mount-fail-early-if-directory-cannot-be-creat.patch - debian/patches/lp1979952-core-mount-downgrade-log-level-about-several-mkdir-failur.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ee8cfcf500698fab2e990de291ecf4c3ab87a4ae * debian/control: add Recommends: systemd-hwe-hwdb to udev. The systemd-hwe-hwdb brings in additional hwdb rules for HWE, so we want those installed with udev by default. File: debian/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4a7a3258c33201cca305956820fcc6bcd6052d76 * hwdb: implement --root option for systemd-hwdb query (LP: #1988078) Files: - debian/libsystemd0.symbols - debian/patches/lp1988078-hwdb-implement-root-option-for-systemd-hwdb-query.patch - debian/patches/lp1988078-sd-hwdb-add-sd_hwdb_new_from_path.patch - debian/patches/lp1988078-sd-hwdb-include-sys-stat.h-in-hwdb-internal.h.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=937fef96c858f2f2042bf71032f315647c14add0 [ Luca Boccassi ] * Enable systemd-repart and ship it in a new systemd-repart package. (LP: #1897932) Add fdisk as test dependency, needed by test-repart which calls sfdisk. Add libfdisk-dev/libssl-dev as dependencies, needed for systemd-repart. Author: Luca Boccassi Files: - debian/control - debian/rules - debian/systemd-repart.install https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=debbc5e9362522210096ae5fa9da48378791e381 [ Lukas Märdian ] * Add sd-repart as test depend, to avoid skipping TEST-58-REPART File: debian/tests/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=669190653f06a6554ddf9725cbeccac65149df23 -- Nick Rosbrook Fri, 09 Sep 2022 14:47:16 -0400 ** Changed in: systemd (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1982462 Title: Some modprobe loading services requested by the pstore service fail Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Jammy: Fix Released Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] It has been detected that some modprobe services fail on UC22 after the jammy upgrade 249.11-0ubuntu3.4: $ systemctl --system --no-ask-password --no-pager list-units --state=failed Failed units: UNIT LOAD ACTIVE SUBDESCRIPTION ● modprobe@chromeos_pstore.service loaded failed failed Load Kernel Module chromeos_pstore ● modprobe@efi_pstore.service loaded failed failed Load Kernel Module
[Touch-packages] [Bug 1982462] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1982462 Title: Some modprobe loading services requested by the pstore service fail Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Jammy: Fix Released Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] It has been detected that some modprobe services fail on UC22 after the jammy upgrade 249.11-0ubuntu3.4: $ systemctl --system --no-ask-password --no-pager list-units --state=failed Failed units: UNIT LOAD ACTIVE SUBDESCRIPTION ● modprobe@chromeos_pstore.service loaded failed failed Load Kernel Module chromeos_pstore ● modprobe@efi_pstore.service loaded failed failed Load Kernel Module efi_pstore ● modprobe@mtdpstore.service loaded failed failed Load Kernel Module mtdpstore ● modprobe@pstore_blk.service loaded failed failed Load Kernel Module pstore_blk ● modprobe@pstore_zone.service loaded failed failed Load Kernel Module pstore_zone ● modprobe@ramoops.service loaded failed failed Load Kernel Module ramoops This happens because of some changes to systemd-pstore.service that now has: After=modprobe@efi_pstore.service modprobe@mtdpstore.service modprobe@chromeos_pstore.service modprobe@ramoops.service modprobe@pstore_zone.service modprobe@pstore_blk.service Wants=modprobe@efi_pstore.service modprobe@mtdpstore.service modprobe@chromeos_pstore.service modprobe@ramoops.service modprobe@pstore_zone.service modprobe@pstore_blk.service This causes too many tries of the modprobe services, that fail in the end with Jul 20 09:02:39 ubuntu systemd[1]: modprobe@chromeos_pstore.service: Start request repeated too quickly. Although we have seen this only on UC22, it potentially can affect classic systems as well, as systemd-pstore.service is re-tried there a few times too. See https://github.com/snapcore/core-base/issues/72 for more details. A fix for this is available upstream: https://github.com/systemd/systemd/commit/9625350e5381a68c1179ae4581e7586c206663e1 [Test Plan] Start the device and check that there is no modprobe-pstore related failed service. This is racy, so a few tries will be needed to make sure things are fine. [Where problems could occur] The modprobe services are usually dependencies from other services, so it should be fine if the retry behavior is controlled by those other services. Risk should be small. If something goes wrong we might see a lot of restarts for these services. [Other Info] Testing should happen on UC22 too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982462/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981622] Update Released
The verification of the Stable Release Update for systemd has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1981622
Title:
mtd device must be supplied (device name is empty)
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Invalid
Status in systemd source package in Jammy:
Fix Released
Bug description:
[WORKAROUND]
This will NOT fix a system that is not booting, because the "mtd
device must be supplied (device name is empty)" message is not the
cause of failed boots. This work around is only for those who are
annoyed by the error message, but are otherwise not experiencing any
issues.
If you are not able to boot your system, but you see this error
message, please open a separate bug with your journalctl and dmesg
logs.
# cp /{lib,etc}/systemd/system/systemd-pstore.service
# sed -i 's/modprobe@mtdpstore.service //'
/etc/systemd/system/systemd-pstore.service
# systemctl daemon-reload
[Impact]
Due to mtdpstore not being properly configured as a pstore backend,
when systemd-pstore.service tries to load the module, users get the
following error in dmesg:
[ 18.453473] systemd[1]: Starting Load Kernel Module mtdpstore...
[ 18.462685] mtd device must be supplied (device name is empty)
This is a distracting error for users trying to diagnose other system
issues, especially if their system does not boot after a kernel crash
and this is the only message displayed on the console.
[Test Plan]
* Force a kernel crash to populate /sys/fs/pstore, thus causing
systemd-pstore.service to start on the subsequent boot:
# echo 1 > /proc/sys/kernel/sysrq
# echo 1 > /proc/sys/kernel/panic
# echo c > /proc/sysrq-trigger
* When the system reboots, observe the error in dmesg:
# dmesg | grep mtd
[Where problems could occur]
If a system was relying on this pstore backend, and mtdpstore is built
as a module, it is possible for systemd-pstore.service to trigger
before mtdpstore is loaded, causing systemd-pstore to not copy the
contents of /sys/fs/pstore. Note however that before the patched
introduced as a result of bug 1978079, systemd-pstore.service would
not attempt to load *any* kernel modules.
[Original Description]
After updating my 22.04 system (possibly caused by Systemd update).
And now booting, dmesg has two errors:
'mtd device must be supplied (device name is empty)'.
See line 8 and 134 in the included logfile.
The system are booting as it should though, and the system are working
like it should no errors at all.
Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
systemd?
I have an EFI mounted at boot but it isn't used because I have
installed my system in legacy BIOS mode.
Is this maybe the culprit?
I could ignore the message but it isn't nice though.
Regards
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1988078] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1988078 Title: Please backport systemd-hwdb patches to support src:systemd-hwe tests Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] We plan to SRU src:systemd-hwe to Jammy[1] to provide an easier way to SRU HWE hwdb rules to Ubuntu. The src:systemd-hwe package contains a test script[2] to ensure that no redundant hwdb rules are added to the package, i.e. rules that are already present in src:systemd. This test requires patches to implement --root flag support for the `systemd- hwdb query` command[3]. These patches are already present in kinetic. Without these patches in Jammy, src:systemd-hwe would have to disable these tests, which are important to maintaining HWE hwdb rules in Ubuntu. [1] https://bugs.launchpad.net/ubuntu/+source/systemd-hwe/+bug/1983996 [2] https://git.launchpad.net/~canonical-foundations/+git/systemd-hwe/tree/tests/hwdb-redundancy?h=main [3] https://github.com/systemd/systemd/pull/23518 [Test plan] * Create a new directory for testing hwdb rule queries: $ mkdir -p fakeroot/etc/udev/hwdb.d * Add a new .hwdb file to override an existing rule. For example, I chose to override the last entry from /lib/udev/hdwb.d/60-keyboard.hwdb: $ tail -2 /lib/udev/hwdb.d/60-keyboard.hwdb > fakeroot/etc/udev/hwdb.d/60-keyboard.hwdb $ sed -i 's/chromebook/reserved/g' fakeroot/etc/udev/hwdb.d/60-keyboard.hwdb $ cat fakeroot/etc/udev/hwdb.d/60-keyboard.hwdb evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnPeppy:* XKB_FIXED_MODEL=reserved * Create the hwdb.bin within fakeroot: $ systemd-hwdb update --root fakeroot $ ls fakeroot/etc/udev/hwdb.bin fakeroot/etc/udev/hwdb.bin * Finally, attempt to query this new hwdb.bin using systemd-hwdb query. On an unpatched system, we will see results from the system's hwdb.bin: $ systemd-hwdb query --root fakeroot evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnPeppy:* | grep XKB_FIXED_MODEL XKB_FIXED_MODEL=chromebook ...and on a patched system we should see the overridden rule: $ systemd-hwdb query --root fakeroot evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnPeppy:* | grep XKB_FIXED_MODEL XKB_FIXED_MODEL=reserved [Where problems could occur] The patches add support for the --root flag when calling systemd-hwdb query, thus changing the behavior of this command (previously, query would always load the system's hwdb.bin). It is unlikely that existing scripts try to use the --root flag with `systemd-hwdb query`, but if they did, this is where we would see problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988078/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1988078] Re: Please backport systemd-hwdb patches to support src:systemd-hwe tests
This bug was fixed in the package systemd - 249.11-0ubuntu3.6 --- systemd (249.11-0ubuntu3.6) jammy; urgency=medium * Deny-list TEST-58-REPART on ppc64el (LP: #1988994) File: debian/patches/lp1988994-Deny-list-TEST-58-REPART-on-ppc64el.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d2ed3cc1d223bf35015b15ff83b50156b58f0f38 systemd (249.11-0ubuntu3.5) jammy; urgency=medium [ Nick Rosbrook ] * Ensure dns_search_domain_unlink_marked removes all marked domains (LP: #1975667) File: debian/patches/lp1975667-Ensure-dns_search_domain_unlink_marked-removes-all-marked.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=919d5ddedd5bb8b45ab9437bf42d66c2821bb074 * core,firstboot: workaround timezone issues on Ubuntu Core (LP: #1981042) Thanks to Robert Ancell for preparing the patch. File: debian/patches/lp1981042-core-firstboot-workaround-timezone-issues-caused-by-Ubunt.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b15546361b549217908fb6ca5d473be23d7fa757 * network: do not remove localhost address (LP: #1979951) File: debian/patches/lp1979951-network-do-not-remove-localhost-address.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2cd88391cce9fe95a486ae6dd214c12f236f3881 * units: remove the restart limit on the modprobe@.service (LP: #1982462) File: debian/patches/lp1982462-units-remove-the-restart-limit-on-the-modprobe-.service.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8f0acd1b2fbb8eed1259c34963e5e9b201bef900 * pstore: do not try to load mtdpstore (LP: #1981622) File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=15225032c3657f5906ee49d48929f9295a8664a0 * core/mount: downgrade log level about several mkdir failures (LP: #1979952) Files: - debian/patches/lp1979952-Revert-core-mount-fail-early-if-directory-cannot-be-creat.patch - debian/patches/lp1979952-core-mount-downgrade-log-level-about-several-mkdir-failur.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ee8cfcf500698fab2e990de291ecf4c3ab87a4ae * debian/control: add Recommends: systemd-hwe-hwdb to udev. The systemd-hwe-hwdb brings in additional hwdb rules for HWE, so we want those installed with udev by default. File: debian/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4a7a3258c33201cca305956820fcc6bcd6052d76 * hwdb: implement --root option for systemd-hwdb query (LP: #1988078) Files: - debian/libsystemd0.symbols - debian/patches/lp1988078-hwdb-implement-root-option-for-systemd-hwdb-query.patch - debian/patches/lp1988078-sd-hwdb-add-sd_hwdb_new_from_path.patch - debian/patches/lp1988078-sd-hwdb-include-sys-stat.h-in-hwdb-internal.h.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=937fef96c858f2f2042bf71032f315647c14add0 [ Luca Boccassi ] * Enable systemd-repart and ship it in a new systemd-repart package. (LP: #1897932) Add fdisk as test dependency, needed by test-repart which calls sfdisk. Add libfdisk-dev/libssl-dev as dependencies, needed for systemd-repart. Author: Luca Boccassi Files: - debian/control - debian/rules - debian/systemd-repart.install https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=debbc5e9362522210096ae5fa9da48378791e381 [ Lukas Märdian ] * Add sd-repart as test depend, to avoid skipping TEST-58-REPART File: debian/tests/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=669190653f06a6554ddf9725cbeccac65149df23 -- Nick Rosbrook Fri, 09 Sep 2022 14:47:16 -0400 ** Changed in: systemd (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1988078 Title: Please backport systemd-hwdb patches to support src:systemd-hwe tests Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] We plan to SRU src:systemd-hwe to Jammy[1] to provide an easier way to SRU HWE hwdb rules to Ubuntu. The src:systemd-hwe package contains a test script[2] to ensure that no redundant hwdb rules are added to the package, i.e. rules that are already present in src:systemd. This test requires patches to implement --root flag support for the `systemd- hwdb query` command[3]. These patches are already present in kinetic. Without these patches in Jammy, src:systemd-hwe would have to disable these tests, which are important to maintaining HWE hwdb rules
[Touch-packages] [Bug 1988994] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1988994 Title: TEST-58-REPART autopkgtest failure on ppc64el Status in systemd package in Ubuntu: New Status in systemd source package in Jammy: Fix Released Bug description: [Impact] With systemd 249.11-0ubuntu3.5 in jammy-proposed, which enables systemd-repart, the TEST-58-REPART fails on ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest- jammy/jammy/ppc64el/s/systemd/20220906_165335_6dd88@/log.gz. After trying to cherry-pick upstream commits, including [1], the test is still failing on ppc64el. This may be a testbed issue, and for now it seems the best course is to skip the test. [Test Plan] This fix is verified by TEST-58-REPART being skipped on ppc64el. [Where problems could occur] If we messed up the denylist usage, the test would not be skipped, or a different one would be. [1] https://github.com/systemd/systemd/commit/8e65d93e85f06e3f2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988994/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1988994] Re: TEST-58-REPART autopkgtest failure on ppc64el
This bug was fixed in the package systemd - 249.11-0ubuntu3.6 --- systemd (249.11-0ubuntu3.6) jammy; urgency=medium * Deny-list TEST-58-REPART on ppc64el (LP: #1988994) File: debian/patches/lp1988994-Deny-list-TEST-58-REPART-on-ppc64el.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d2ed3cc1d223bf35015b15ff83b50156b58f0f38 systemd (249.11-0ubuntu3.5) jammy; urgency=medium [ Nick Rosbrook ] * Ensure dns_search_domain_unlink_marked removes all marked domains (LP: #1975667) File: debian/patches/lp1975667-Ensure-dns_search_domain_unlink_marked-removes-all-marked.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=919d5ddedd5bb8b45ab9437bf42d66c2821bb074 * core,firstboot: workaround timezone issues on Ubuntu Core (LP: #1981042) Thanks to Robert Ancell for preparing the patch. File: debian/patches/lp1981042-core-firstboot-workaround-timezone-issues-caused-by-Ubunt.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b15546361b549217908fb6ca5d473be23d7fa757 * network: do not remove localhost address (LP: #1979951) File: debian/patches/lp1979951-network-do-not-remove-localhost-address.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2cd88391cce9fe95a486ae6dd214c12f236f3881 * units: remove the restart limit on the modprobe@.service (LP: #1982462) File: debian/patches/lp1982462-units-remove-the-restart-limit-on-the-modprobe-.service.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8f0acd1b2fbb8eed1259c34963e5e9b201bef900 * pstore: do not try to load mtdpstore (LP: #1981622) File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=15225032c3657f5906ee49d48929f9295a8664a0 * core/mount: downgrade log level about several mkdir failures (LP: #1979952) Files: - debian/patches/lp1979952-Revert-core-mount-fail-early-if-directory-cannot-be-creat.patch - debian/patches/lp1979952-core-mount-downgrade-log-level-about-several-mkdir-failur.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ee8cfcf500698fab2e990de291ecf4c3ab87a4ae * debian/control: add Recommends: systemd-hwe-hwdb to udev. The systemd-hwe-hwdb brings in additional hwdb rules for HWE, so we want those installed with udev by default. File: debian/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4a7a3258c33201cca305956820fcc6bcd6052d76 * hwdb: implement --root option for systemd-hwdb query (LP: #1988078) Files: - debian/libsystemd0.symbols - debian/patches/lp1988078-hwdb-implement-root-option-for-systemd-hwdb-query.patch - debian/patches/lp1988078-sd-hwdb-add-sd_hwdb_new_from_path.patch - debian/patches/lp1988078-sd-hwdb-include-sys-stat.h-in-hwdb-internal.h.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=937fef96c858f2f2042bf71032f315647c14add0 [ Luca Boccassi ] * Enable systemd-repart and ship it in a new systemd-repart package. (LP: #1897932) Add fdisk as test dependency, needed by test-repart which calls sfdisk. Add libfdisk-dev/libssl-dev as dependencies, needed for systemd-repart. Author: Luca Boccassi Files: - debian/control - debian/rules - debian/systemd-repart.install https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=debbc5e9362522210096ae5fa9da48378791e381 [ Lukas Märdian ] * Add sd-repart as test depend, to avoid skipping TEST-58-REPART File: debian/tests/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=669190653f06a6554ddf9725cbeccac65149df23 -- Nick Rosbrook Fri, 09 Sep 2022 14:47:16 -0400 ** Changed in: systemd (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1988994 Title: TEST-58-REPART autopkgtest failure on ppc64el Status in systemd package in Ubuntu: New Status in systemd source package in Jammy: Fix Released Bug description: [Impact] With systemd 249.11-0ubuntu3.5 in jammy-proposed, which enables systemd-repart, the TEST-58-REPART fails on ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest- jammy/jammy/ppc64el/s/systemd/20220906_165335_6dd88@/log.gz. After trying to cherry-pick upstream commits, including [1], the test is still failing on ppc64el. This may be a testbed issue, and for now it seems the best course is to skip the test. [Test Plan] This fix is verified by TEST-58-REPART being skipped on ppc64el. [Where problems could occur] If we messed up the denylist usage, the test would not
[Touch-packages] [Bug 1989959] Re: Incorrect ESM coverage information
Let's stick to the following, please: over 2,300 packages in Ubuntu Main and over 23,000 packages in Ubuntu Universe, meaning over 25,000 packages in total. It should work for every LTS from Xenial forward. Remember that: Standard Ubuntu LTS gives you 5 years of coverage for Main, esm-infra gives you additional 5 years (10 years total), and esm-apps gives you 10 years of security coverage for Universe. both esm-infra and esm-apps are available with subscriptions (free and paid) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1989959 Title: Incorrect ESM coverage information Status in software-properties package in Ubuntu: New Bug description: Software Properties says that Extended Security Maintenance provides security updates for over 3 Ubuntu packages, see lines 1269 and 1346 in data/gtkbuilder/main.ui. According to https://ubuntu.com/16-04, Canonical provides extended security maintenance for binary packages that reside in the "main" Ubuntu repository, which contains about 7000 architecture-specific packages depending on the Ubuntu release. Moreover, ESM is only provided for a part of packages, not for all packages in the "main" repository. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1989959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1971538] Re: My machine has Wi-Fi Hotspot broken after upgrade to 22.04
I got a workaround by disabling the firewall. But the moment you turn it on (even if clients connected beforehand), the internet loses connection again. Quite annoying (also dangerous) for hotspot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1971538 Title: My machine has Wi-Fi Hotspot broken after upgrade to 22.04 Status in network-manager package in Ubuntu: Confirmed Bug description: * Impact The hotspot feature fails to forward the data to the clients * Test case - log into an Ubuntu or GNOME session - connect the machine to an eth cable for internet - go to gnome-control-center -> wifi - enable the hotspot from the menu in the headerbar - connect another device to the wifi created -> the client should connect and access to internet work correctly Upon updating to 22.04, none of my machines can use the connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990293] Re: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 )
what it is amazing : iznobe@iznobe-PC:~$ tree /Vidéos/.Trash /Vidéos/.Trash └── 1000 ├── files │ ├── Nouveau document.txt │ └── test.odt └── info ├── Nouveau document.txt.trashinfo └── test.odt.trashinfo 3 directories, 4 files iznobe@iznobe-PC:~$ Mounting a FS directly on /Vidéos is working well trash include ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1990293 Title: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 ) Status in glib2.0 package in Ubuntu: New Status in glib2.0 source package in Jammy: New Bug description: Hi , when i delete a file where is in another partition than " / " or mounted in /media/ , i obtain the message in title. how can i use trash again please ? iznobe@iznobe-PC:~$ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/nvme0n1p2 during installation UUID=eb18366b-2ac9-4a7e-8f93-ba2caa30e90e / ext4 noatime,errors=remount-ro 0 1 # /boot/efi was on /dev/nvme0n1p1 during installation UUID=C071-9050/boot/efi vfatdefaults0 0 # swap was on /dev/sdc3 during installation UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456 noneswap sw,pri=10 0 # partition de données separée comune aux OS linux UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257 /datas ext4 defaults0 0 LABEL=WD8 /Vidéos/WD8 ext4 defaults0 0 #/dev/disk/by-label/WD8PRO2 /media/WD8PRO2 ext4 defaults0 0 LABEL=WD8PRO2 /Vidéos/WD8PRO2 ext4defaults 0 0 LABEL=WD8PRO1 /media/WD8PRO1 ext4 defaults0 0 LABEL=Seagate_4T /media/Seagate_4T ext4 defaults,noauto 0 0 trash is working for filesysteme mounted on /media/WD8PRO1 but not in FS mounted on /Vidéos/WD8PRO2 and /Vidéos/WD8 using ubuntu 22.04.1 LTS . Exactly same file systeme mounted on same directory , with same trash directory is working fine on ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1990293/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
