[Touch-packages] [Bug 1497593] Re: [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed.
** Tags added: lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1497593 Title: [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. Status in Mesa: New Status in libdrm package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. Because nouveau is not thread safe(?) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1497593/+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 1942260] Re: compress firmware in /lib/firmware
** Tags added: patch -- 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/1942260 Title: compress firmware in /lib/firmware Status in initramfs-tools package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware-raspi2 package in Ubuntu: Confirmed Bug description: -- initramfs-tools [Impact] * linux supports xz compressed linux-firmware which saves disk space. In focal, initramfs-tools only knows how to included uncompressed firmware files (even when kernel supports loading compressed ones). Newer releases of linux-firmware may use compressed firmware files only, in such cases it would be nice for focal's initramfs-tools to support compressed firmware files in case of partial or incomplete upgrades (i.e. linux-firmware force installed or upgraded, without newer initramfs-tools). The proposed changes to initramfs-tools are backwards and forwards compatible, they prefer to include uncompressed firmware files; and if missing, include compressed firmware files in their uncompressed form. Thus maintaining compatibility with any kernels, irrespective of compressed/uncompressed firmware inputs. [Test Plan] * Compress all files shipped by linux-firmware with xz * Rebuild initrd * Check that all the same firmware files are still included in the initramfs, in their uncompressed form as before [Where problems could occur] * This SRU is precautionary to prevent accidental installation of compressed linux-firmware from generating incorrect initramfs. It should be noted that whilst initramfs-tools would create a compatible initramfs with any kernels, pre-v5.3 kernels do not support xz compressed firmware files at runtime. Mixing this new initramfs with compressed firmwares and pre 5.3 kernels may lead to expectations of supporting compressed firmware files with them only working at initrd stage and not at runtime. [Other Info] Original bug report Some facts: - The linux kernel has supported loading xz compressed firmware since 5.3 - The size of /lib/firmware in impish is ~650Mb (and growing) - The compressed size of firmware could be ~230Mb It would be nice to install compressed firmware to save space. Here are the plans from the Fedora project: https://fedoraproject.org/wiki/Changes/CompressKernelFirmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1942260/+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 1942260] Re: compress firmware in /lib/firmware
All kernels need to support reading the compressed firmware files (even after partial upgrades). See bug #2028550 for the kernel side. linux-firmware needs two patches to correctly produce compressed firmware files: * https://lore.kernel.org/linux-firmware/1addfae3b9a376ebbf39c0d05642394ebcfb9ee9.ca...@canonical.com/T/#u * https://lore.kernel.org/linux-firmware/c151f7d4837d3a07143ee5191d3f5e57bc6ded2c.ca...@canonical.com/T/#u Attached a tested debdiff that could be uploaded once following points are addressed: * support for zstd compressed firmware files in initramfs-tools (should be in 0.142ubuntu8) * support for zstd compressed firmware in all relevant kernels (see bug #2028550) * a "Breaks: initramfs-tools (<< 0.142ubuntu8~)" for the final uploaded version should be added ** Patch added: "linux-firmware_20230629.gitee91452d-0ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1942260/+attachment/5688141/+files/linux-firmware_20230629.gitee91452d-0ubuntu2.debdiff -- 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/1942260 Title: compress firmware in /lib/firmware Status in initramfs-tools package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware-raspi2 package in Ubuntu: Confirmed Bug description: -- initramfs-tools [Impact] * linux supports xz compressed linux-firmware which saves disk space. In focal, initramfs-tools only knows how to included uncompressed firmware files (even when kernel supports loading compressed ones). Newer releases of linux-firmware may use compressed firmware files only, in such cases it would be nice for focal's initramfs-tools to support compressed firmware files in case of partial or incomplete upgrades (i.e. linux-firmware force installed or upgraded, without newer initramfs-tools). The proposed changes to initramfs-tools are backwards and forwards compatible, they prefer to include uncompressed firmware files; and if missing, include compressed firmware files in their uncompressed form. Thus maintaining compatibility with any kernels, irrespective of compressed/uncompressed firmware inputs. [Test Plan] * Compress all files shipped by linux-firmware with xz * Rebuild initrd * Check that all the same firmware files are still included in the initramfs, in their uncompressed form as before [Where problems could occur] * This SRU is precautionary to prevent accidental installation of compressed linux-firmware from generating incorrect initramfs. It should be noted that whilst initramfs-tools would create a compatible initramfs with any kernels, pre-v5.3 kernels do not support xz compressed firmware files at runtime. Mixing this new initramfs with compressed firmwares and pre 5.3 kernels may lead to expectations of supporting compressed firmware files with them only working at initrd stage and not at runtime. [Other Info] Original bug report Some facts: - The linux kernel has supported loading xz compressed firmware since 5.3 - The size of /lib/firmware in impish is ~650Mb (and growing) - The compressed size of firmware could be ~230Mb It would be nice to install compressed firmware to save space. Here are the plans from the Fedora project: https://fedoraproject.org/wiki/Changes/CompressKernelFirmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1942260/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2
@vorlon - adding to Fabio's question. I agree with your reasoning that
the workarounds should be reasonably easy for a knowledgeable user. We
should enable end users to apply the same fix since they may be affected
without realizing it. While we shouldn't encourage users to stay on 2.7,
there are apps that either won't transition or still have a large amount
of work to do so. For Jammy, I believe these apps can be effectively
guaranteed security patches until 2032.
I believe the path below avoids the regression concerns. Its a bit ugly,
but it at least won't outlive Jammy. None of this is ideal, but I think
solves both sides of the equation.
* Add a feature flag that applies the proposed fix when present. This should be
the default to satisfy the initial bug report constraint. Maybe
UBUNTU_APPLY_DEFAULT_PYTHON_CFLAGS_ON_EXTENSIONS? Extremely verbose, but very
little chance of someone accidentally disabling it. We should also print when
its used so users have a launchpad issue to reference if it happens to cause a
regression for a out of distro package compilation.
* Prevent applying the above feature flag for packages that already exist in
the archive. This is a static list that is very unlikely to change. This does
assume that distutils.sysconfig has a mechanism to introspect the package
currently being built. Public API hints that it MAY be possible, but I haven't
done thorough inspection across the ecosystem of callers.
Would you support a solution similar to the above?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
In Progress
Status in python2.7 source package in Bionic:
Won't Fix
Status in python2.7 source package in Focal:
Won't Fix
Status in python2.7 source package in Jammy:
Won't Fix
Status in python2.7 source package in Kinetic:
Won't Fix
Status in python2.7 source package in Lunar:
Won't Fix
Status in python2.7 source package in Mantic:
Won't Fix
Bug description:
Compiling a Python extension using Python2 (Python 2.7.18) is making
use of wrong compiler flags, hence dropping required optimizations
when required. This is happening only when python2 is installed from
Ubuntu's repositories. By default, Python's distutils module uses
compiler and linker flags used to compile Python itself to be used to
compile extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
On further investigation, it looks like Ubuntu's specific patch applied on
libpython2.7-stdlib package is altering the original upstream implementation of
distutils/sysconfig.py code.
Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
Patch -
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
Below is the code block which is causing the issue, where the presence of
configure_cflags is modifying cflags. This code is result of ubuntu's patch and
doesn't come directly from upstream python implementation.
File - /usr/lib/python2.7/distutils/sysconfig.py
Part of code block:
elif configure_cflags:
cflags = ' '.join(str(x) for x in (basecflags, configure_cflags,
extra_cflags) if x)
ldshared = ldshared + ' ' + configure_cflags
I don't see problem on Python3 though we have extra code added from patch
there as well. Patch used on python3, is not modifying the cflags completely
and instead appending new flags to cflags.
On python3 (tested on Ubuntu 20.04)
File - /usr/lib/python3.8/distutils/sysconfig.py
Part of code block which doesn't alter cflags completely
elif configure_cflags:
cflags = cflags + ' '
[Touch-packages] [Bug 2017317] Re: Ubuntu: upon reboot, forever waiting for encrypted swapfile ...
Similar issue here when upgrading to 6.2.0.26.26 from 5.19*. The only solution so far was fallback to 5.19. Thanks. -- 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/2017317 Title: Ubuntu: upon reboot, forever waiting for encrypted swapfile ... Status in systemd package in Ubuntu: Incomplete Bug description: ### Issue description When restarting my machine, cryptsetup waits forever. Waiting for the swapfile. Unable to start Ubuntu at all. Error message is: ``` cryptsetup: Waiting for encrypted source device /swapfile... ``` ### Steps for reproducing the issue 1. Do a fresh installation of Ubuntu, unencrypted. 2. Later, due to restrictions at work, encrypt Ubuntu POST installation accordingly to this article: https://jumpcloud.com/blog/how-to-encrypt-ubuntu-20-04-desktop-post-installation 3. Reboot, all works fine, but ... 4. Later, after a couple of months, install a new Linux kernel and then ... 5. Upon boot cryptsetup gets stuck, waits forever. See attached photo. ### Additional info I've found a temporary, painful workaround by rebooting in recovery mode and running this command every time: ``` sudo update-initramfs -u -k all ``` Then I can boot again. But I have to do this every time. Why? ### Debug log Hard to say but here's the output of this command `journalctl | grep crypt`, not sure if you can find anything interesting about it: ``` Apr 21 13:48:28 M1 audit[179547]: AVC apparmor="DENIED" operation="getattr" class="file" info="Failed name lookup - disconnected path" error=-13 profile="/usr/bin/evince-thumbnailer" name="home/.ecryptfs/michael-heuberger/.Private/ECRYPTFS_FNEK_ENCRYPTED.FWaKkF5ZO-vAFETGnoPriOb55KN8iA.SprD0W8LFNkfXu75b-QusjTdAA---/ECRYPTFS_FNEK_ENCRYPTED.FXaKkF5ZO-vAFETGnoPriOb55KN8iA.SprD0JjExLlqv3Fk6x4GGYcQdjXda2554lHGsMAmCwjYZWGA-" pid=179547 comm="evince-thumbnai" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Apr 21 17:01:49 M1 gdm-password][219451]: pam_ecryptfs: pam_sm_authenticate: /home/michael-heuberger is already mounted Apr 21 17:26:59 M1 systemd[1]: Requested transaction contradicts existing jobs: Transaction for plymouth-quit.service/start is destructive (dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2dcryptswap1.swap has 'stop' job queued, but 'start' is included in transaction). Apr 21 17:26:59 M1 systemd[1]: gdm.service: Failed to enqueue OnFailure= job, ignoring: Transaction for plymouth-quit.service/start is destructive (dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2dcryptswap1.swap has 'stop' job queued, but 'start' is included in transaction). Apr 21 17:26:59 M1 systemd[3094]: Stopping GnuPG cryptographic agent and passphrase cache... Apr 21 17:27:00 M1 systemd[3094]: Stopped GnuPG cryptographic agent and passphrase cache. Apr 21 17:27:07 M1 systemd[1]: Stopped target Local Encrypted Volumes. Apr 21 17:27:08 M1 umount.ecryptfs[231225]: Failed to find key with sig [2bda85c181b04823]: Required key not available Apr 21 17:27:08 M1 umount.ecryptfs[231225]: Failed to find key with sig [96c111e5680ecc45]: Required key not available Apr 21 17:27:09 M1 systemd[1]: Deactivating swap /dev/disk/by-id/dm-name-cryptswap1... Apr 21 17:27:09 M1 systemd[1]: dev-disk-by\x2dlabel-cryptswap1.swap: Deactivated successfully. Apr 21 17:27:09 M1 systemd[1]: Deactivated swap /dev/disk/by-label/cryptswap1. ``` Do you have any tips, advice please, how to fix this, how can I reboot my machine without running `update-initramfs` every time? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2017317/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2
Hi Steve,
Would you and the SRU team reconsider the "won't fix" decision or
further elaborate on the regression problem, based on the comment above?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
In Progress
Status in python2.7 source package in Bionic:
Won't Fix
Status in python2.7 source package in Focal:
Won't Fix
Status in python2.7 source package in Jammy:
Won't Fix
Status in python2.7 source package in Kinetic:
Won't Fix
Status in python2.7 source package in Lunar:
Won't Fix
Status in python2.7 source package in Mantic:
Won't Fix
Bug description:
Compiling a Python extension using Python2 (Python 2.7.18) is making
use of wrong compiler flags, hence dropping required optimizations
when required. This is happening only when python2 is installed from
Ubuntu's repositories. By default, Python's distutils module uses
compiler and linker flags used to compile Python itself to be used to
compile extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
On further investigation, it looks like Ubuntu's specific patch applied on
libpython2.7-stdlib package is altering the original upstream implementation of
distutils/sysconfig.py code.
Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
Patch -
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
Below is the code block which is causing the issue, where the presence of
configure_cflags is modifying cflags. This code is result of ubuntu's patch and
doesn't come directly from upstream python implementation.
File - /usr/lib/python2.7/distutils/sysconfig.py
Part of code block:
elif configure_cflags:
cflags = ' '.join(str(x) for x in (basecflags, configure_cflags,
extra_cflags) if x)
ldshared = ldshared + ' ' + configure_cflags
I don't see problem on Python3 though we have extra code added from patch
there as well. Patch used on python3, is not modifying the cflags completely
and instead appending new flags to cflags.
On python3 (tested on Ubuntu 20.04)
File - /usr/lib/python3.8/distutils/sysconfig.py
Part of code block which doesn't alter cflags completely
elif configure_cflags:
cflags = cflags + ' ' + configure_cflags
ldshared = ldshared + ' ' + configure_cflags
Request to update the python2 patch to behave similar to what is been done on
python3.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+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 2027847] Re: Bump minimum /boot size in ubuntu-release-upgrader
We have a bunch of bugs to decrease initramfs size and to make it faster: * bug #2028567: initramfs-tools: Do not re-compress compressed kernel modules and firmware files * bug #2028568: Ship kernel modules compressed * bug #1942260: compress firmware in /lib/firmware * bug #2028571: klibc-utils contains identical binaries * bug #2028574: Duplicate firmware files in /lib/firmware This started on ubuntu-devel: https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html -- 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/2027847 Title: Bump minimum /boot size in ubuntu-release-upgrader Status in apt package in Ubuntu: Won't Fix Status in dpkg package in Ubuntu: Invalid Status in kernel-package package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Invalid Status in linux-kernel-headers package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: System information: ubuntu 23.04 x86_64 6.2.0-24-generic Upgrading the system: $ sudo dpkg --configure -a Setting up linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) ... update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/ubuntu--vg-swap_1) I: Set the RESUME variable to override this. zstd: error 70 : Write error : cannot write block : No space left on device E: mkinitramfs failure zstd -q -1 -T0 70 Check space left (none): $ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/sdb2 707M 693M 0 100% /boot What is required is to remove older kernels (and purge them most likely). List all the installed kernels except the current one: $ dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d' linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-libc-dev:amd64 linux-libc-dev:i386 linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Is not possible to uninstall any kernel because fails: $ sudo apt purge linux-headers-6.2.0-23 E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Reconfigure fails again so some kernel have to be manually removed to free up space: $ sudo rm /boot/initrd.img-6.2.0-23-generic $ sudo rm -rf /boot/initrd.img-6.2.0-25-generic.new Now you can reconfigure: $ Remove kernels: $ sudo apt purge linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Reboot: $ sudo reboot Upgrade as usual: $ sudo apt update && sudo apt upgrade Before upgrading new kernels I need to check for free space and remove older kernels manually. Fix this so there's only one kernel left. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2027847/+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 2028571] [NEW] klibc-utils contains identical binaries
Public bug reported: ``` $ jdupes -r /usr/lib/klibc/bin Scanning: 38 files, 1 items (in 1 specified) /usr/lib/klibc/bin/gunzip /usr/lib/klibc/bin/gzip /usr/lib/klibc/bin/zcat /usr/lib/klibc/bin/halt /usr/lib/klibc/bin/poweroff /usr/lib/klibc/bin/reboot ``` Please replace these binaries with symlinks to reduce the size of the uncompressed initramfs. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: klibc-utils 2.0.12-1 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Jul 24 21:14:36 2023 Dependencies: libklibc 2.0.12-1 InstallationDate: Installed on 2022-03-20 (491 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: klibc UpgradeStatus: Upgraded to lunar on 2023-04-20 (95 days ago) ** Affects: klibc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/2028571 Title: klibc-utils contains identical binaries Status in klibc package in Ubuntu: New Bug description: ``` $ jdupes -r /usr/lib/klibc/bin Scanning: 38 files, 1 items (in 1 specified) /usr/lib/klibc/bin/gunzip /usr/lib/klibc/bin/gzip /usr/lib/klibc/bin/zcat /usr/lib/klibc/bin/halt /usr/lib/klibc/bin/poweroff /usr/lib/klibc/bin/reboot ``` Please replace these binaries with symlinks to reduce the size of the uncompressed initramfs. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: klibc-utils 2.0.12-1 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Jul 24 21:14:36 2023 Dependencies: libklibc 2.0.12-1 InstallationDate: Installed on 2022-03-20 (491 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: klibc UpgradeStatus: Upgraded to lunar on 2023-04-20 (95 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/2028571/+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 1997912] Re: /usr/share/apport/whoopsie-upload-all:binascii.Error:/usr/share/apport/whoopsie-upload-all@249:main:collect_info:process_report:load:_decompress_line:b64decode
** Changed in: apport Status: Fix Committed => Fix Released -- 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/1997912 Title: /usr/share/apport/whoopsie-upload- all:binascii.Error:/usr/share/apport/whoopsie-upload- all@249:main:collect_info:process_report:load:_decompress_line:b64decode Status in Apport: Fix Released Status in apport package in Ubuntu: Triaged Status in apport source package in Kinetic: Confirmed Status in apport source package in Lunar: Triaged Bug description: Impact == apport-unpack and whoopsie-upload-all can crash when fed with a malformed problem report. They should print a proper error message instead of crashing. Test Plan = 1. Create malformed report: ``` printf "CoreDump: base64\n H4sICAAC/0NvcmVEdW1wAA==\n 7Z0LYFPV/cdP0rQ\n" > malformed.crash ``` 2. Try to unpack it: ``` apport-unpack malformed.crash unpack ``` It should print an error message instead of a stack trace. Where problems could occur == The patch touches the problem report handling and therefore can affect apport-unpack, apport-bug, whoopsie-upload-all. The change is covered with tests and apport has a test suite running during build and as autopkgtest. Original report === ``` Traceback (most recent call last): File "/usr/share/apport/whoopsie-upload-all", line 249, in main() File "/usr/share/apport/whoopsie-upload-all", line 231, in main stamps = collect_info() File "/usr/share/apport/whoopsie-upload-all", line 162, in collect_info res = process_report(r) File "/usr/share/apport/whoopsie-upload-all", line 76, in process_report r.load(f, binary="compressed") File "/usr/lib/python3/dist-packages/problem_report.py", line 139, in load bd, value = self._decompress_line(line, bd, value) File "/usr/lib/python3/dist-packages/problem_report.py", line 276, in _decompress_line block = base64.b64decode(line) File "/usr/lib/python3.10/base64.py", line 87, in b64decode return binascii.a2b_base64(s) binascii.Error: Incorrect padding ``` The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.23.1-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/dd58c8169d2ec8468b8b37471dfb701ac31c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1997912/+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 2026730] Re: Merge dash 0.5.12-6 from debian
This bug was fixed in the package dash - 0.5.12-6ubuntu1 --- dash (0.5.12-6ubuntu1) mantic; urgency=medium * Merge with Debian unstable (LP: #2026730). Remaining changes: - d/t/control: Disable mmdebstrap autopkgtest test-case, testing only the Debian archive. dash (0.5.12-6) unstable; urgency=medium [ Johannes Schauer Marin Rodrigues ] * debian/tests/mmdebstrap: use copy-host-apt-sources-and-preferences hook. - use the hook provided by mmdebstrap instead of cooking up our own thing, thus preventing code duplication - this also copies over apt pinning rules which were missing before dash (0.5.12-5) unstable; urgency=medium [ Helmut Grohne ] * dash.postinst: fix installing with --path-exclude=/usr/share/man/* (Closes: #1038067) dash (0.5.12-4) unstable; urgency=medium * Upload to unstable. dash (0.5.12-3) experimental; urgency=medium [ Andrej Shadura ] * Fix bug number in the patch description [ Helmut Grohne ] * dash.postinst: Remove upgrade path from pre-sarge ash. (Closes: #989419) * Remove unnecessary diversion in case /bin/sh points to dash. (Closes: #989632) [ Luca Boccassi ] * dash.postinst: remove unused function -- Dominik Viererbe Tue, 11 Jul 2023 12:03:53 +0300 ** Changed in: dash (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/2026730 Title: Merge dash 0.5.12-6 from debian Status in dash package in Ubuntu: Fix Released Bug description: This is a tracking bug to merge dash 0.5.12-6 from debian. Below now follows the report of the automated merge of the Ubuntu changes to the dash source package against the new Debian version. This file is designed to be both human readable and machine-parseable. Any line beginning with four spaces is a file that should be downloaded for the complete merge set. Here are the particulars of the three versions of dash that were chosen for the merge. The base is the newest version that is a common ancestor of both the Ubuntu and Debian packages. It may be of a different upstream version, but that's not usually a problem. The files are the source package itself, and the patch from the common base to that version. base: 0.5.12-2 dash_0.5.12-2.dsc dash_0.5.12.orig.tar.gz dash_0.5.12-2.debian.tar.xz ubuntu: 0.5.12-2ubuntu1 dash_0.5.12-2ubuntu1.dsc dash_0.5.12.orig.tar.gz dash_0.5.12-2ubuntu1.debian.tar.xz base -> ubuntu dash_0.5.12-2ubuntu1.patch debian: 0.5.12-6 dash_0.5.12-6.dsc dash_0.5.12.orig.tar.gz dash_0.5.12-6.debian.tar.xz base -> debian dash_0.5.12-6.patch Generated Result Due to conflict or error, it was not possible to automatically create a source package. Instead the result of the merge has been placed into the following tar file which you will need to turn into a source package once the problems have been resolved. dash_0.5.12-6ubuntu1.src.tar.gz Conflicts = In one or more cases, there were different changes made in both Ubuntu and Debian to the same file; these are known as conflicts. It is not possible for these to be automatically resolved, so this source needs human attention. Those files marked with 'C ' contain diff3 conflict markers, which can be resolved using the text editor of your choice. Those marked with 'C*' could not be merged that way, so you will find .UBUNTU and .DEBIAN files instead and should choose one of them or a combination of both, moving it to the real filename and deleting the other. C debian/tests/control Once you have a source package you are happy to upload, you should make sure you include the orig.tar.* if appropriate and information about all the versions included in the merge. Use the following command to generate a correct .changes file: $ dpkg-genchanges -S -v0.5.12-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/2026730/+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 2028567] [NEW] Do not re-compress compressed kernel modules and firmware files
Public bug reported: initramfs-tools decompresses kernel modules and firmware files before putting them into the initramfs. This has several drawbacks: * The compressed kernel modules and firmware files are probably compressed with a higher level. So recompressing them in the initramfs (default: zstd -1) will increase the size. * Decompressing and compressing these files during mkinitramfs will take time * The size of the decompressed initramfs will be bigger. That size is needed in memory during boot. So put compressed kernel modules and firmware files in an uncompressed cpio instead. To make this change have an impact the files need to be shipped compressed: * kernel modules: bug #2028568 * firmware files: bug #1942260 See https://lists.ubuntu.com/archives/ubuntu-devel/2023-July/042652.html ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Assignee: Benjamin Drung (bdrung) Status: New ** Description changed: initramfs-tools decompresses kernel modules and firmware files before putting them into the initramfs. This has several drawbacks: * The compressed kernel modules and firmware files are probably compressed with a higher level. So recompressing them in the initramfs (default: zstd -1) will increase the size. * Decompressing and compressing these files during mkinitramfs will take time * The size of the decompressed initramfs will be bigger. That size is needed in memory during boot. So put compressed kernel modules and firmware files in an uncompressed - cpio instead. + cpio instead. To make this change have an impact the files need to be + shipped compressed: + + * kernel modules: bug #2028568 + * firmware files: bug #1942260 + + See https://lists.ubuntu.com/archives/ubuntu-devel/2023-July/042652.html ** Changed in: initramfs-tools (Ubuntu) Assignee: (unassigned) => Benjamin Drung (bdrung) -- 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/2028567 Title: Do not re-compress compressed kernel modules and firmware files Status in initramfs-tools package in Ubuntu: New Bug description: initramfs-tools decompresses kernel modules and firmware files before putting them into the initramfs. This has several drawbacks: * The compressed kernel modules and firmware files are probably compressed with a higher level. So recompressing them in the initramfs (default: zstd -1) will increase the size. * Decompressing and compressing these files during mkinitramfs will take time * The size of the decompressed initramfs will be bigger. That size is needed in memory during boot. So put compressed kernel modules and firmware files in an uncompressed cpio instead. To make this change have an impact the files need to be shipped compressed: * kernel modules: bug #2028568 * firmware files: bug #1942260 See https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2028567/+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 1969365] Re: focal: backport kexec fallback patch
Thanks Nick, much appreciated! -- 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/1969365 Title: focal: backport kexec fallback patch Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Triaged Bug description: It would be great if focal's systemd could have https://github.com/systemd/systemd/commit/71180f8e57f8fbb55978b00a13990c79093ff7b3 backported to it. [Impact] We have observed that kexec'ing to another kernel will fail as the drive containing the `kexec` binary has been unmounted by the time systemd attempts to do so, indicated in the console: Starting Reboot via kexec... [ 163.960938] shutdown[1]: (sd-kexec) failed with exit status 1. [ 163.963463] reboot: Restarting system [Test Plan] 1) Launch a 20.04 instance 2) `apt-get install kexec-tools` 3) In `/boot`, filling in whatever needed in your environment: kexec -l vmlinuz --initrd initrd.img --append '' 4) `reboot` (I have reproduced this in a single-disk VM, so I assume it reproduces ~everywhere: if not, `apt-get remove kexec-tools` before the `reboot` could be used to emulate the unmounting.) [Where problems could occur] Users could inadvertently be relying on the current behaviour: if they have configured their systems to kexec, they currently will be rebooting normally, and this patch would cause them to start actually kexec'ing. [Other info] We're currently maintaining a systemd tree with only this patch added to focal's tree: this patch has received a bunch of testing from us in focal. This patch landed in v246, so it's already present in supported releases later than focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969365/+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 2016252] Re: qemu-system-x86_64 crashes inside systemd autopkgtest (nested VM)
I am seeing the same crash with systemd 253.5-1ubuntu1 upstream-{1,2}
tests and qemu 1:8.0.2+dfsg-2ubuntu1[1]. However, the systemd
252.5-2ubuntu3 upstream-{1,2} tests pass against the same version of
qemu[2].
[1]
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/s/systemd/20230720_070515_f604e@/log.gz
[2]
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/s/systemd/20230721_154608_28f76@/log.gz
** Changed in: qemu (Ubuntu)
Status: Expired => New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
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/2016252
Title:
qemu-system-x86_64 crashes inside systemd autopkgtest (nested VM)
Status in qemu package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
Systemd package has autopkgtests
the upstream-2 test cases use upstream systemd testsuite, i.e. make -C
str/test/TEST-70-TPM2 setup run
it launches a nested VM to do quick tests inside it.
It appears that qemu-system-x86_64 crashes in such cases:
TEST-70-TPM2 RUN: cryptenroll/cryptsetup with TPM2 devices
+ timeout --foreground 1800 /bin/qemu-system-x86_64 -smp 4 -net none -m 1024M
-nographic -vga none -kernel /boot/vmlinuz-6.2.0-1003-lowlatency -drive
format=raw,cache=unsafe,file=/var/tmp/systemd-test.G2RH6i/tpm2.img -device
virtio-rng-pci,max-bytes=1024,period=1000 -chardev
socket,id=chrtpm,path=/tmp/tmp.cRBa43SrLC/sock -tpmdev
emulator,id=tpm0,chardev=chrtpm -device tpm-tis,tpmdev=tpm0 -initrd
/boot/initrd.img-6.2.0-1003-lowlatency -append 'root=LABEL=systemd_boot rw
raid=noautodetect rd.luks=0 loglevel=2 init=/lib/systemd/systemd console=ttyS0
SYSTEMD_UNIT_PATH=/usr/lib/systemd/tests/testdata/testsuite-70.units:/usr/lib/systemd/tests/testdata/units:
systemd.unit=testsuite.target systemd.wants=testsuite-70.service oops=panic
panic=1 softlockup_panic=1 systemd.wants=end.service'
qemu-system-x86_64: ../../util/cacheflush.c:208: init_cache_info: Assertion
`(isize & (isize - 1)) == 0' failed.
timeout: the monitored command dumped core
..//test-functions: line 377: 152120 Aborted ( set -x;
"${qemu_cmd[@]}" "${qemu_options[@]}" -append "${kernel_params[*]}" )
E: qemu failed with exit code 134
The important bit seems to be:
qemu-system-x86_64: ../../util/cacheflush.c:208: init_cache_info:
Assertion `(isize & (isize - 1)) == 0' failed.
Which is an assert inside qemu source code.
Is the systemd test suite VM setup doing something wrong, or is there
something wrong in qemu?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2016252/+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 2003250] Re: networkctl reload with bond devices causes slaves to go DOWN and UP, causing couple of seconds of network loss
Seems its not "low importance" bug. 洛 Updating systemd package can trigger such bug, and if you have a unattended-upgrade it's gonna cause a network flap on that host. Easy to reproduce it with: # apt install --reinstall systemd -- Distributor ID: Ubuntu Description:Ubuntu 22.04.2 LTS Release:22.04 Codename: jammy systemd 249 (249.11-0ubuntu3.9) -- 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/2003250 Title: networkctl reload with bond devices causes slaves to go DOWN and UP, causing couple of seconds of network loss Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Kinetic: Triaged Bug description: We currently use Ubuntu 22.04.1 LTS including updates for our production cloud (switched from legacy Centos 7). Although we like the distribution we recently hit serious systemd buggy behavior described in [1] bugreport using packages [2]. Unfortunatelly the clouds we are running consist of openstack on top of kubernetes and we need to have complex network configuration including linux bond devices. Our observation is that every time we apply our configuration via CI/CD infrastructure using ansible and netplan (regardless whether there is actual network configuration change) we see approximatelly 8-16 seconds network interruptions and see bond interfaces going DOWN and then UP. We expect bond interfaces stay UP when there is no network configuration change. We went though couple of options how to solve the issue and the first one is to add such existing patch [3] into current systemd-249.11-0ubuntu3.6. Could you comment whether this kind of non-security patch is likely to land in 22.04.1 LTS soon. We are able to help to bring patch into systemd package community way if you suggest the steps. [1] https://github.com/systemd/systemd/issues/25067 [2] Packages root@controlplane-001:/etc/apt0# apt list | grep -E '^(systemd/|netplan.io)' netplan.io/jammy-updates,now 0.105-0ubuntu2~22.04.1 amd64 [installed,automatic] systemd/jammy-updates,now 249.11-0ubuntu3.6 amd64 [installed,automatic] [3] https://github.com/systemd/systemd/pull/25162 [4] # lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2003250/+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 2028556] [NEW] package initramfs-tools 0.140ubuntu13.2 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: I have no idea if this was reported before, i'm a tech normie ProblemType: Package DistroRelease: Ubuntu 22.04 Package: initramfs-tools 0.140ubuntu13.2 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Jul 24 08:11:59 2023 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-08-11 (712 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: initramfs-tools Title: package initramfs-tools 0.140ubuntu13.2 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-08-16 (341 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/2028556 Title: package initramfs-tools 0.140ubuntu13.2 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: I have no idea if this was reported before, i'm a tech normie ProblemType: Package DistroRelease: Ubuntu 22.04 Package: initramfs-tools 0.140ubuntu13.2 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Jul 24 08:11:59 2023 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-08-11 (712 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: initramfs-tools Title: package initramfs-tools 0.140ubuntu13.2 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-08-16 (341 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2028556/+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 2025563] Re: System can not shutdown if system has multiple VROC RAID arrays
I am planning on doing an SRU for Jammy soon that will fix multiple bugs. I will make sure this is included. ** Tags added: systemd-sru-next -- 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/2025563 Title: System can not shutdown if system has multiple VROC RAID arrays Status in OEM Priority Project: In Progress Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: New Status in systemd source package in Kinetic: Fix Released Bug description: [ Impact ] The system can not shutdown if the system has multiple VROC RAID arrays. Intel has fixed it in systemd v251 [1]. Need to cherry-pick the commit to ubuntu-jammy systemd 249.11-0ubuntu3.9. [1] The commit fixes the issue: commit 3a3b022d2cc112803ea7b9beea98bbcad110368a Author: Mariusz Tkaczyk Date: Tue Mar 29 12:49:54 2022 +0200 shutdown: get only active md arrays. Current md_list_get() implementation filters all block devices, started from "md*". This is ambiguous because list could contain: - partitions created upon md device (mdXpY) - external metadata container- specific type of md array. For partitions there is no issue, because they aren't handle STOP_ARRAY ioctl sent later. It generates misleading errors only. Second case is more problematic because containers are not locked in kernel. They are stopped even if container member array is active. For that reason reboot or shutdown flow could be blocked because metadata manager cannot be restarted after switch root on shutdown. Add filters to remove partitions and containers from md_list. Partitions can be excluded by DEVTYPE. Containers are determined by MD_LEVEL property, we are excluding all with "container" value. Signed-off-by: Mariusz Tkaczyk [ Test Plan ] 1. Build two VROC RAID. One RAID 0 for System volume, another RAID 10 for Data volume. 2. Install system on System volume. 3. Update systemd. 4. Reboot the system. 5. Verify if the system can reboot. [ Where problems could occur ] The patch confirmed fixed the reboot issue on the system with two VROC RAIDs but more than two VROC RAIDs and the combinations of RAID levels are not all tested. [ Scope ] Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2025563/+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 2026730] Re: Merge dash 0.5.12-6 from debian
https://launchpad.net/ubuntu/+source/dash/0.5.12-6ubuntu1 ** Changed in: dash (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/2026730 Title: Merge dash 0.5.12-6 from debian Status in dash package in Ubuntu: In Progress Bug description: This is a tracking bug to merge dash 0.5.12-6 from debian. Below now follows the report of the automated merge of the Ubuntu changes to the dash source package against the new Debian version. This file is designed to be both human readable and machine-parseable. Any line beginning with four spaces is a file that should be downloaded for the complete merge set. Here are the particulars of the three versions of dash that were chosen for the merge. The base is the newest version that is a common ancestor of both the Ubuntu and Debian packages. It may be of a different upstream version, but that's not usually a problem. The files are the source package itself, and the patch from the common base to that version. base: 0.5.12-2 dash_0.5.12-2.dsc dash_0.5.12.orig.tar.gz dash_0.5.12-2.debian.tar.xz ubuntu: 0.5.12-2ubuntu1 dash_0.5.12-2ubuntu1.dsc dash_0.5.12.orig.tar.gz dash_0.5.12-2ubuntu1.debian.tar.xz base -> ubuntu dash_0.5.12-2ubuntu1.patch debian: 0.5.12-6 dash_0.5.12-6.dsc dash_0.5.12.orig.tar.gz dash_0.5.12-6.debian.tar.xz base -> debian dash_0.5.12-6.patch Generated Result Due to conflict or error, it was not possible to automatically create a source package. Instead the result of the merge has been placed into the following tar file which you will need to turn into a source package once the problems have been resolved. dash_0.5.12-6ubuntu1.src.tar.gz Conflicts = In one or more cases, there were different changes made in both Ubuntu and Debian to the same file; these are known as conflicts. It is not possible for these to be automatically resolved, so this source needs human attention. Those files marked with 'C ' contain diff3 conflict markers, which can be resolved using the text editor of your choice. Those marked with 'C*' could not be merged that way, so you will find .UBUNTU and .DEBIAN files instead and should choose one of them or a combination of both, moving it to the real filename and deleting the other. C debian/tests/control Once you have a source package you are happy to upload, you should make sure you include the orig.tar.* if appropriate and information about all the versions included in the merge. Use the following command to generate a correct .changes file: $ dpkg-genchanges -S -v0.5.12-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/2026730/+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 2027636] Re: [SRU] ucsi drivers missing in initramfs
After discussing with Benjamin, will do another upload for IGX and the missing stusb160x module ** Tags removed: verification-done verification-done-jammy verification-done-lunar ** Tags added: verification-needed verification-needed-jammy verification-needed-lunar -- 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/2027636 Title: [SRU] ucsi drivers missing in initramfs Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Jammy: Fix Committed Status in initramfs-tools source package in Lunar: Fix Committed Bug description: [Impact] Some systems rely on a USB type-C UCSI connection; without the corresponding driver in the initramfs, USB storage might not be accessible. This is notably affecting NVIDIA Tegra systems such as Jetson AGX or the IGX and prevents completing USB boot for installation purposes. The initramfs-tools package has a list of relevant USB drivers to include for the default MODULES=most configuration, but didn't list the recently introduced ucsi one. [ Test Plan ] The -generic kernel and probably all kernel flavors contain the ucsi driver. On jammy system, you can verify the current initrd doesn't contain typec_ucsi.ko by decompressing the initramfs and listing its files: $ lsinitramfs /boot/initrd.img-5.19.0-46-generic | grep typec_ucsi.ko After installing the updated initramfs-tools package, your current initramfs should be automatically rebuilt and pick up typec_ucsi.ko: $ lsinitramfs /boot/initrd.img-5.19.0-46-generic | grep typec_ucsi.ko usr/lib/modules/5.19.0-46-generic/kernel/drivers/usb/typec/ucsi/typec_ucsi.ko [ Where problems could occur ] This is making the initramfs slightly bigger. In my testing, typec_ucsi.ko was 99913B and /boot/initrd.img-5.19.0-46-generic grew by 93403B from 122298948B to 122392351B, so by less than 0.08%. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027636/+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 2004551] Re: upgrade to lunar fails due to rescue-ssh.target or port 22 takeover
Crash report ** Attachment added: "openssh-server.0.crash" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2004551/+attachment/5688062/+files/openssh-server.0.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2004551 Title: upgrade to lunar fails due to rescue-ssh.target or port 22 takeover Status in openssh package in Ubuntu: New Bug description: Hi, I just upgraded a system from Jammy to Lunar and openssh-server refuses to upgrade well. Setting up openssh-server (1:9.0p1-1ubuntu8) ... Replacing config file /etc/ssh/sshd_config with new version Replacing config file /etc/ssh/sshd_config with new version Synchronizing state of ssh.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install disable ssh rescue-ssh.target is a disabled or a static unit not running, not starting it. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145. dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Processing triggers for man-db (2.11.2-1) ... Processing triggers for libc-bin (2.36-0ubuntu4) ... Errors were encountered while processing: openssh-server Error: Timeout was reached needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) I'm not sure what exactly it is. This output complains about rescue-ssh.target and indeed that can not be started even directly. $ sudo systemctl start rescue-ssh.target A dependency job for rescue-ssh.target failed. See 'journalctl -xe' for details. And in postinst is a try to start it: $ grep rescue /var/lib/dpkg/info/openssh-server.postinst deb-systemd-invoke $_dh_action 'rescue-ssh.target' >/dev/null || true But I think the underlying issue is that ssh is already on, and I'm logged in via it. And that makes the service restart of the ssh socket which was added break. Feb 02 10:40:56 node-horsea systemd[104560]: ssh.socket: Failed to create listening socket ([::]:22): Address already in use Feb 02 10:40:56 node-horsea systemd[1]: ssh.socket: Failed to receive listening socket ([::]:22): Input/output error Feb 02 10:40:56 node-horsea systemd[1]: ssh.socket: Failed to listen on sockets: Input/output error Feb 02 10:40:56 node-horsea systemd[1]: ssh.socket: Failed with result 'resources'. Now, whichever it is, it is hard to resolve. The only way to get the socket to own it would be rebooting so that sshd lets go and systemd can take over. I could reboot, but that is not the point. What if I'd want to get the service and upgrade completed before reboot. Because as of now dpkg considers the system unhappy, and that would usually be a sign for "better not reboot before being resolved" to me. One thing though, I have not upgraded with do-release-upgrade - would we / do we have magic there to make the ssh socket activation transition smoother? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2004551/+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 2004551] Re: upgrade to lunar fails due to rescue-ssh.target or port 22 takeover
In horsea's syslog.1, some errors happen at the same time that do-dist- upgrade is running and fails: Jul 20 10:20:23 node-horsea fwupd[214065]: 10:20:23:0245 FuEngine failed to get releases for UEFI dbx: No releases found: Not compatible with org.freedesktop.fwupd version 1.7.9, requires >= 1.9.1 Jul 20 10:20:23 node-horsea fwupd[214065]: 10:20:23:0252 FuEngine failed to get releases for UEFI dbx: No releases found: Not compatible with org.freedesktop.fwupd version 1.7.9, requires >= 1.9.1 [...] Jul 20 10:28:26 node-horsea kernel: [610494.600470] systemd[1]: Failed to set up automount Arbitrary Executable File Formats File System Automount Point. [...] Jul 20 10:28:26 node-horsea kernel: [610494.648822] systemd[1]: multipathd.socket: Failed to create listening socket (@/org/kernel/linux/storage/multipathd): Address already in use Jul 20 10:28:26 node-horsea kernel: [610494.707090] systemd[1]: multipathd.socket: Failed to listen on sockets: Address already in use Jul 20 10:28:26 node-horsea kernel: [610494.707135] systemd[1]: multipathd.socket: Failed with result 'resources'. Jul 20 10:28:26 node-horsea kernel: [610494.707179] systemd[1]: Failed to listen on multipathd control socket. [... The next appears several times:] Jul 20 10:28:26 node-horsea kernel: [610494.788337] systemd-journald[529]: Failed to send stream file descriptor to service manager: Transport endpoint is not connected [...] Jul 20 10:28:27 node-horsea systemd[1]: multipathd.service: Found left-over process 576 (multipathd) in control group while starting unit. Ignoring. Jul 20 10:28:27 node-horsea systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Jul 20 10:28:27 node-horsea systemd[1]: Finished Load/Save Random Seed. Jul 20 10:28:27 node-horsea systemd[1]: Finished Flush Journal to Persistent Storage. Jul 20 10:28:27 node-horsea systemd[1]: Condition check resulted in First Boot Complete being skipped. Jul 20 10:28:27 node-horsea systemd[1]: Finished Create System Users. Jul 20 10:28:27 node-horsea multipathd[217042]: process is already running Jul 20 10:28:27 node-horsea multipathd[217042]: failed to create pidfile Jul 20 10:28:27 node-horsea systemd[1]: Starting Create Static Device Nodes in /dev... Jul 20 10:28:27 node-horsea systemd[1]: multipathd.service: Main process exited, code=exited, status=1/FAILURE Jul 20 10:28:27 node-horsea systemd[1]: multipathd.service: Got notification message from PID 576, but reception only permitted for main PID which is currently not known Jul 20 10:28:27 node-horsea systemd[1]: message repeated 2 times: [ multipathd.service: Got notification message from PID 576, but reception only permitted for main PID which is currently not known] Jul 20 10:28:27 node-horsea multipathd[576]: exit (signal) Jul 20 10:28:27 node-horsea multipathd[576]: shut down--- [... A lot of the following: Processes 592, 216916 and then 216963 to 217007, 217010 to 217011] Jul 20 10:28:27 node-horsea systemd[1]: Finished Create Static Device Nodes in /dev. Jul 20 10:28:27 node-horsea systemd[1]: systemd-udevd.service: Found left-over process 592 (systemd-udevd) in control group while starting unit. Ignoring. [...] Jul 20 10:28:27 node-horsea systemd[1]: Starting Rule-based Manager for Device Events and Files... Jul 20 10:28:27 node-horsea systemd[1]: multipathd.service: Failed with result 'exit-code'. Jul 20 10:28:27 node-horsea systemd[1]: Failed to start Device-Mapper Multipath Device Controller. [... Some of this:] Jul 20 10:28:28 node-horsea systemd-udevd[217552]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1. [... A couple of: ] Jul 20 10:28:28 node-horsea libvirtd[87522]: internal error: The keyword is not comprised only of uppercase ASCII letters or digits Jul 20 10:28:28 node-horsea libvirtd[87522]: internal error: A field data length violates the resource length boundary. Jul 20 10:28:28 node-horsea libvirtd[87522]: internal error: The keyword is not comprised only of uppercase ASCII letters or digits Jul 20 10:28:28 node-horsea libvirtd[87522]: internal error: A field data length violates the resource length boundary. [...] Jul 20 10:28:28 node-horsea systemd-udevd[217550]: sdb: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb' failed with exit code 1. [...] Jul 20 10:28:28 node-horsea cloud-init[217927]: 2023-07-20 10:28:28,415 - stages.py[WARNING]: Failed to rename devices: Failed to apply network config names: [nic not present] Cannot rename mac=8c:dc:d4:b3:6d:e8 to eno49, not available. [... More left over processes, but this seems due to the previous dpdk tests:] Jul 20 10:28:28 node-horsea systemd[1]: ovsdb-server.service: Found left-over process 214295 (ovsdb-server) in control group while starting unit. Ignoring. Jul 20 10:28:28 node-horsea systemd[1]: This usually indicates
[Touch-packages] [Bug 2004551] Re: upgrade to lunar fails due to rescue-ssh.target or port 22 takeover
Today I'm trying to reproduce the error in a lxc vm without success: I logged in via ssh to start the do-release-upgrade there so the system would initiate sshd on port 1022 as well. The upgrade process went fine the times I tried it. Thanks Andreas for spotting the same error in the autopkgtest log. I'm looking for similarities between it and the horsea machine. Checking horsea's log, I found the following "FileNotFoundError: [Errno 2] No such file or directory: '/tmp/ubuntu- release-upgrader-x6gsdfa4/removal_denylist.cfg'" in the screenlog.0 under /var/log/dist-upgrade directory: Progress: [ 96%] Processing triggers for man-db (2.10.2-1) ... packages have been installed but needrestart is suspended packages have been installed but needrestart is suspended packages have been installed but needrestart is suspended Reading package lists... 0% Reading package lists... 100% Reading package lists... Done Building dependency tree... 0% Building dependency tree... 0% Building dependency tree... 50% Building dependency tree... 50% Building dependency tree... Done Reading state information... 0% Reading state information... 0% Reading state information... Done Traceback (most recent call last): File "/tmp/ubuntu-release-upgrader-x6gsdfa4/kinetic", line 8, in File "/tmp/ubuntu-release-upgrader-x6gsdfa4/DistUpgrade/DistUpgradeMain.py", line 241, in main File "/tmp/ubuntu-release-upgrader-x6gsdfa4/DistUpgrade/DistUpgradeController.py", line 2042, in run File "/tmp/ubuntu-release-upgrader-x6gsdfa4/DistUpgrade/DistUpgradeController.py", line 1986, in fullUpgrade File "/tmp/ubuntu-release-upgrader-x6gsdfa4/DistUpgrade/DistUpgradeController.py", line 207, in openCache File "/tmp/ubuntu-release-upgrader-x6gsdfa4/DistUpgrade/DistUpgradeController.py", line 231, in _openCache File "/tmp/ubuntu-release-upgrader-x6gsdfa4/DistUpgrade/DistUpgradeCache.py", line 142, in __init__ File "/tmp/ubuntu-release-upgrader-x6gsdfa4/DistUpgrade/DistUpgradeConfigParser.py", line 89, in getListFromFile FileNotFoundError: [Errno 2] No such file or directory: '/tmp/ubuntu-release-upgrader-x6gsdfa4/removal_denylist.cfg' Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 76, in apport_excepthook binary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0])) FileNotFoundError: [Errno 2] No such file or directory Original exception was: Traceback (most recent call last): File "/tmp/ubuntu-release-upgrader-x6gsdfa4/kinetic", line 8, in File "/tmp/ubuntu-release-upgrader-x6gsdfa4/DistUpgrade/DistUpgradeMain.py", line 241, in main File "/tmp/ubuntu-release-upgrader-x6gsdfa4/DistUpgrade/DistUpgradeController.py", line 2042, in run File "/tmp/ubuntu-release-upgrader-x6gsdfa4/DistUpgrade/DistUpgradeController.py", line 1986, in fullUpgrade File "/tmp/ubuntu-release-upgrader-x6gsdfa4/DistUpgrade/DistUpgradeController.py", line 207, in openCache File "/tmp/ubuntu-release-upgrader-x6gsdfa4/DistUpgrade/DistUpgradeController.py", line 231, in _openCache File "/tmp/ubuntu-release-upgrader-x6gsdfa4/DistUpgrade/DistUpgradeCache.py", line 142, in __init__ File "/tmp/ubuntu-release-upgrader-x6gsdfa4/DistUpgrade/DistUpgradeConfigParser.py", line 89, in getListFromFile FileNotFoundError: [Errno 2] No such file or directory: '/tmp/ubuntu-release-upgrader-x6gsdfa4/removal_denylist.cfg' === Command terminated with exit status 1 (Thu Jul 20 10:29:30 2023) ===-- 0:kinetic -- time-stamp -- Jul/20/23 10:31:29 -- It also appears in /var/log/dist-upgrade/main.log : 2023-07-20 10:27:36,606 DEBUG inhibit screensaver 2023-07-20 10:28:21,258 DEBUG quirks: running StartUpgrade 2023-07-20 10:28:21,258 DEBUG running Quirks.StartUpgrade 2023-07-20 10:28:21,259 DEBUG skipping 'README' (no '.') 2023-07-20 10:28:21,260 DEBUG killing update-notifier 2023-07-20 10:28:21,266 DEBUG killing kblueplugd kbluetooth4 2023-07-20 10:28:21,272 DEBUG apt btrfs snapshots supported: False 2023-07-20 10:28:21,272 INFO cache.commit() 2023-07-20 10:28:22,889 DEBUG cache.commit() returned None 2023-07-20 10:28:23,146 DEBUG quirks: running StartUpgrade 2023-07-20 10:28:23,146 DEBUG running Quirks.StartUpgrade 2023-07-20 10:28:23,147 DEBUG skipping 'README' (no '.') 2023-07-20 10:28:23,147 DEBUG killing update-notifier 2023-07-20 10:28:23,152 DEBUG killing kblueplugd kbluetooth4 2023-07-20 10:28:23,157 DEBUG apt btrfs snapshots supported: False 2023-07-20 10:28:23,157 INFO cache.commit() 2023-07-20 10:29:30,470 DEBUG cache.commit() returned None 2023-07-20 10:29:30,471 DEBUG openCache() 2023-07-20 10:29:30,847 ERROR getListFromFile: no '/tmp/ubuntu-release-upgrader-x6gsdfa4/removal_denylist.cfg' found 2023-07-20 10:29:30,848 ERROR not handled exception: Traceback (most recent call last): File "/tmp/ubuntu-release-upgrader-x6gsdfa4/kinetic", line 8, in File "/tmp/ubuntu-release-
[Touch-packages] [Bug 2028454] Re: apt-config crashed with SIGSEGV in _int_malloc()
This bug is about a specific crash in apt-config, not about installer crashing during password entry, please use the other bug for that. -- 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/2028454 Title: apt-config crashed with SIGSEGV in _int_malloc() Status in apt package in Ubuntu: Incomplete Bug description: ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: apt 2.7.2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckMismatches: ./casper/minimal.fr.squashfs CasperMD5CheckResult: fail CasperVersion: 1.481 Date: Sun Jul 23 09:14:39 2023 ExecutablePath: /usr/bin/apt-config JournalErrors: Jul 23 09:14:31 hostname kernel: overlayfs: fs on '/tmp/tmpc4daggpg/root.dir' does not support file handles, falling back to xino=off. Jul 23 09:14:35 hostname kernel: overlayfs: fs on '/tmp/tmpkuua06i6/root.dir' does not support file handles, falling back to xino=off. Jul 23 09:14:37 hostname kernel: overlayfs: fs on '/tmp/tmpkuua06i6/root.dir' does not support file handles, falling back to xino=off. Jul 23 09:14:37 hostname kernel: overlayfs: lowerdir is in-use as upperdir/workdir of another mount, accessing files from both mounts will result in undefined behavior. Jul 23 09:14:40 hostname pipewire[1573]: spa.alsa: front:0: (0 missed) impossible htimestamp diff:-8420 LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230723) ProcCmdline: apt-config shell TRUSTEDPARTS Dir::Etc::TrustedParts/d ProcEnviron: LANG= LC_MESSAGES= PATH=(custom, no user) SHELL=/bin/sh SegvAnalysis: Segfault happened at: 0x7fd06012f111 <_int_malloc+737>: cmp 0x10(%r8),%rdx PC (0x7fd06012f111) ok source "0x10(%r8)" (0x69efc653158d0b5d) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: apt StacktraceTop: _int_malloc (av=av@entry=0x7fd060287c80 , bytes=bytes@entry=472) at ./malloc/malloc.c:3994 __GI___libc_malloc (bytes=bytes@entry=472) at ./malloc/malloc.c:3297 __fopen_internal (is32=1, mode=0x7fd0604878c3 "r", filename=0x5579117a9860 "/usr/share/dpkg/tupletable") at ./libio/iofopen.c:65 _IO_new_fopen (filename=0x5579117a9860 "/usr/share/dpkg/tupletable", mode=0x7fd0604878c3 "r") at ./libio/iofopen.c:86 std::__basic_file::open(char const*, std::_Ios_Openmode, int) () from /lib/x86_64-linux-gnu/libstdc++.so.6 Title: apt-config crashed with SIGSEGV in _int_malloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2028454/+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 1222356] Re: WARNING: Couldn't register with accessibility bus: Did not receive a reply.
On 18.04, I noticed this warning started occurring after i ran a GTK application - gtimelog - with sudo. Now this warning is printed every time i run the application without sudo. Warning disappears when running as sudo. Seems like some permissions problem. Don't know how to fix it. Moral of the story : Don't run gui applications with sudo. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1222356 Title: WARNING: Couldn't register with accessibility bus: Did not receive a reply. Status in at-spi2-core package in Ubuntu: Fix Released Status in at-spi2-core package in Debian: Fix Released Bug description: The following warnings/errors appear after calling ubuntu-bug ** (apport-gtk:3020): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (process:4192): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: apport-gtk 2.12.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Sun Sep 8 10:54:01 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-09-01 (371 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MarkForUpload: True PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to saucy on 2013-09-05 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1222356/+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 2026730] Re: Merge dash 0.5.12-6 from debian
** Changed in: dash (Ubuntu) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/2026730 Title: Merge dash 0.5.12-6 from debian Status in dash package in Ubuntu: Confirmed Bug description: This is a tracking bug to merge dash 0.5.12-6 from debian. Below now follows the report of the automated merge of the Ubuntu changes to the dash source package against the new Debian version. This file is designed to be both human readable and machine-parseable. Any line beginning with four spaces is a file that should be downloaded for the complete merge set. Here are the particulars of the three versions of dash that were chosen for the merge. The base is the newest version that is a common ancestor of both the Ubuntu and Debian packages. It may be of a different upstream version, but that's not usually a problem. The files are the source package itself, and the patch from the common base to that version. base: 0.5.12-2 dash_0.5.12-2.dsc dash_0.5.12.orig.tar.gz dash_0.5.12-2.debian.tar.xz ubuntu: 0.5.12-2ubuntu1 dash_0.5.12-2ubuntu1.dsc dash_0.5.12.orig.tar.gz dash_0.5.12-2ubuntu1.debian.tar.xz base -> ubuntu dash_0.5.12-2ubuntu1.patch debian: 0.5.12-6 dash_0.5.12-6.dsc dash_0.5.12.orig.tar.gz dash_0.5.12-6.debian.tar.xz base -> debian dash_0.5.12-6.patch Generated Result Due to conflict or error, it was not possible to automatically create a source package. Instead the result of the merge has been placed into the following tar file which you will need to turn into a source package once the problems have been resolved. dash_0.5.12-6ubuntu1.src.tar.gz Conflicts = In one or more cases, there were different changes made in both Ubuntu and Debian to the same file; these are known as conflicts. It is not possible for these to be automatically resolved, so this source needs human attention. Those files marked with 'C ' contain diff3 conflict markers, which can be resolved using the text editor of your choice. Those marked with 'C*' could not be merged that way, so you will find .UBUNTU and .DEBIAN files instead and should choose one of them or a combination of both, moving it to the real filename and deleting the other. C debian/tests/control Once you have a source package you are happy to upload, you should make sure you include the orig.tar.* if appropriate and information about all the versions included in the merge. Use the following command to generate a correct .changes file: $ dpkg-genchanges -S -v0.5.12-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/2026730/+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 2021948] Re: New bugfix release 23.0.4
because of comment #7 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2021948 Title: New bugfix release 23.0.4 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Status in mesa source package in Lunar: Fix Released Bug description: [Impact] This is the last point-release of the 23.0.x-series, we should put it in lunar so latest bugfixes would get there, and in jammy for 22.04.3 image. We'll include an additional bugfix (a revert) to fix GPU hangs on some AMD gpu's running certain games. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2021948/+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 2022845] Re: SRU: update binutils to the 2.38 branch and ignore lto-wrapper warnings
after retries, all the autopkg tests pass, binutils test results don't show regressions. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2022845 Title: SRU: update binutils to the 2.38 branch and ignore lto-wrapper warnings Status in binutils package in Ubuntu: New Status in binutils source package in Jammy: Fix Committed Bug description: The tests sometimes fail with spurious lto-wrapper warnings and let the build fail. Ignore these warnings, they don't matter for the test outcome. Also apply four fixes from the binutils 2.38 branch: * SRU: LP: #1982105. Update from the binutils 2.38 branch: - Fix PR ld/29435: elf: Reset alignment for each PT_LOAD segment. - PowerPC64 pcrel got relocs against local symbols. - Fix PR ld/27998: i386: Don't allow GOTOFF relocation against IFUNC symbol for PIC. - Fix PR ld/29377: x86: Properly check invalid relocation against protected symbol. * Ignore lto-wrapper warnings when running the testsuite. https://sourceware.org/bugzilla/show_bug.cgi?id=29435 https://sourceware.org/bugzilla/show_bug.cgi?id=27998 https://sourceware.org/bugzilla/show_bug.cgi?id=29377 All changes are already in 2.39 in kinetic, and 2.40 in lunar. The changes come with test cases, and pass when running the testsuite. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2022845/+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 1409166] Re: Popup dialog "could not set the configuration for CRTC 65" steals keyboard, hinders login in 3-monitor configuration
Thank you for reporting this bug to Ubuntu. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it anymore. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: xorg (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1409166 Title: Popup dialog "could not set the configuration for CRTC 65" steals keyboard, hinders login in 3-monitor configuration Status in xorg package in Ubuntu: Won't Fix Bug description: Every time I boot, while I'm trying to enter my password in the initial login screen (from Unity?), a dialog box pops up saying "Could not switch the monitor configuration could not set the configuration for CRTC 65". The dialog box also steals the keyboard focus, which is very confusing if for some reason you're entering the password on an external display while the normally unused laptop display is not visible. For example, three times in a row this morning I rebooted and tried unsuccessfully to log in. Since the dialog box is only displayed on the laptop display, which I never use when external monitors are available, I had no idea why my keyboard seemed broken. Background: My Lenovo Thinkpad X230 Tablet laptop has a VGA and a DVI connector. I have the VGA hooked up to a Viewsonic 1920x1080 monitor, positioned above the laptop display. I have a Samsung monitor to the right of the Viewsonic. Since my laptop seems to only support two displays (which also seems true in Windows), I normally disable and totally ignore my laptop display, and may have papers propped up in front of it etc. Note that when I initially configured the third display I saw the following highly confusing behavior. From Settings I tried to add a Samsung monitor to the right of the Viewsonic, via a DVI-to-HDMI passive connector, and got this dialog box when I hit "Apply": The selected configuration for displays could not be applied could not set the configuration for CRTC 65 I clicked "OK" and got another dialog box: Failed to apply configuration: %s Can't add monitor: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gnome_2drr_2derror_2dquark.Code2: could not set the configuration for CRTC 65 It works if I disable my laptop monitor, so it looks like the problem is with adding a third display. I would think it would be a pretty common use case to use two nice external displays and disable the laptop display. Even when the hardware can't handle a third display, the error messages should not be so confusing, and the login process shouldn't result in the keyboard being mysteriously stolen by a dialog box on a display which may never be visible. This is on Trusty 64-bit, up-to-date with upgrades. This bug seems similar to bug 1304627, but it seemed cleanest to get all the right information reported via ubuntu-bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 9 15:35:57 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2203] InstallationDate: Installed on 2015-01-01 (8 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 343522U ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-43-generic root=UUID=6dce26c4-3d5b-4980-880e-06f249f77c57 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/22/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GCET96WW (2.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 343522U dmi.board.vendor: LENOVO dmi.board.version: Not Defined
