[Touch-packages] [Bug 1908818] Re: pure packaging of libnss3
MP review complete and the build logs LGTM:
lrwxrwxrwx root/root 0 2021-04-06 10:10
./usr/lib/s390x-linux-gnu/libfreebl3.so -> nss/libfreebl3.so
lrwxrwxrwx root/root 0 2021-04-06 10:10
./usr/lib/i386-linux-gnu/libfreebl3.so -> nss/libfreebl3.so
lrwxrwxrwx root/root 0 2021-04-06 10:10
./usr/lib/riscv64-linux-gnu/libfreebl3.so -> nss/libfreebl3.so
Uploading ...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1908818
Title:
pure packaging of libnss3
Status in nss package in Ubuntu:
Fix Released
Status in nss source package in Groovy:
In Progress
Status in nss source package in Hirsute:
Fix Released
Bug description:
[Impact]
* A packaging error in the current version has led library symlinks
to be broken and in the wrong place.
* Fix by applying the later change to Groovy as well
[Test Plan]
* install libnss3
* check (path depends on the architecture) the lib links
$ dpkg -L libnss3 | grep MULTIARCH
# ^^ should be empty
$ ll /usr/lib/x86_64-linux-gnu/libfreebl3.so
# vv should look like that:
lrwxrwxrwx 1 root root 17 Feb 16 15:18
/usr/lib/x86_64-linux-gnu/libfreebl3.so -> nss/libfreebl3.so
root@h:~# ll /usr/lib/x86_64-linux-gnu/libfreebl*
lrwxrwxrwx 1 root root 18 Feb 16 15:18
/usr/lib/x86_64-linux-gnu/libfreebl3.chk -> nss/libfreebl3.chk
lrwxrwxrwx 1 root root 17 Feb 16 15:18
/usr/lib/x86_64-linux-gnu/libfreebl3.so -> nss/libfreebl3.so
lrwxrwxrwx 1 root root 22 Feb 16 15:18
/usr/lib/x86_64-linux-gnu/libfreeblpriv3.chk -> nss/libfreeblpriv3.chk
lrwxrwxrwx 1 root root 21 Feb 16 15:18
/usr/lib/x86_64-linux-gnu/libfreeblpriv3.so -> nss/libfreeblpriv3.so
[Where problems could occur]
* I first was afraid, that no matter how bad the paths would
have been we'd need to retain them for anyone using them
already. But the existing links go into nowhere since they
are relative therefore the regression risk should be minimal
root@g:~# ll '/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so'
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so'
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk'
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk'
lrwxrwxrwx 1 root root 18 Sep 29 2020
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk' -> nss/libfreebl3.chk
lrwxrwxrwx 1 root root 17 Sep 29 2020
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so' -> nss/libfreebl3.so
lrwxrwxrwx 1 root root 22 Sep 29 2020
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk' -> nss/libfreeblpriv3.chk
lrwxrwxrwx 1 root root 21 Sep 29 2020
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so' -> nss/libfreeblpriv3.so
* never the less, to be clear - if problems occur they would be in
loading these libraries. E.g. a user could have had this package
and a self built nss on his system, after the change it might load the
packaged one.
[Other Info]
* n/a
---
dpkg -L libnss3
/.
/usr
/usr/lib
/usr/lib/${DEB_HOST_MULTIARCH}
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libnss3.so
/usr/lib/x86_64-linux-gnu/libnssutil3.so
/usr/lib/x86_64-linux-gnu/libsmime3.so
/usr/lib/x86_64-linux-gnu/libssl3.so
/usr/lib/x86_64-linux-gnu/nss
/usr/lib/x86_64-linux-gnu/nss/libfreebl3.chk
/usr/lib/x86_64-linux-gnu/nss/libfreebl3.so
/usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.chk
/usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.so
/usr/lib/x86_64-linux-gnu/nss/libnssckbi.so
/usr/lib/x86_64-linux-gnu/nss/libnssdbm3.chk
/usr/lib/x86_64-linux-gnu/nss/libnssdbm3.so
/usr/lib/x86_64-linux-gnu/nss/libsoftokn3.chk
/usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so
/usr/share
/usr/share/doc
/usr/share/doc/libnss3
/usr/share/doc/libnss3/changelog.Debian.gz
/usr/share/doc/libnss3/copyright
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/libnss3
/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk
as we can see soft links to libraries do nor resolve
${DEB_HOST_MULTIARCH} to x86_64-linux-gnu
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: libnss3 2:3.55-1ubuntu3
ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
Uname: Linux 5.8.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Dec 20 14:36:10 2020
SourcePackage: nss
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1908818/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help :
[Touch-packages] [Bug 1920837] Re: apport bugs from official raspi or riscv images are not identified
> labelling them as Raspberry Pi would exacerbate the issue Sorry, I should have acknowledged that Dave's proposal would avoid this issue. -- 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/1920837 Title: apport bugs from official raspi or riscv images are not identified Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: In Progress Status in apport source package in Groovy: In Progress Bug description: It would be helpful if bugs reported from images for Raspberry Pi's or RISCV systems were tagged so that one could search for bugs from systems running those images e.g. 'raspi-image'. [Test Case] After installing a preinstalled image of Ubuntu for Raspberry Pi do the following: 1) run 'ubuntu-bug apport' 2) view the bug report and check the Tags field With the current version of apport you will not see the tag 'raspi-image'. With the version of apport in -proposed you will see the tag 'raspi-image'. [Where problems could occur] If the code being added is syntactically incorrect then we'd see a Traceback which would be bad as it could affect all bug / crash reports. [Other Info] Since there aren't any Groovy images for RISC-V there will be nothing to test there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1920837/+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 1920837] Re: apport bugs from official raspi or riscv images are not identified
A couple of thoughts:
1)
In addition to future supported platforms, what about weird third party
hacked up things? Are we going to end up with reports from users who
have grabbed a custom image for some esoteric platform from someone who
is hacking something together for that platform by basing their work on
one of our official Raspberry Pi images? To be clear, they're welcome to
do that; we just don't want images mislabelled as Raspberry Pi causing
confusion in that case. Of course people can do that regardless of what
apport does, but labelling them as Raspberry Pi would exacerbate the
issue.
2)
+if 'ImageMediaBuild' in report:
+if report['Architecture'] in ('arm64', 'armhf'):
+add_tag(report, 'raspi-image')
Why not simply add tags arm64-image and armhf-image? Then you'll get the
same effect you want but without a potentially misleading tag. This may
be kicking the can down the road, but maybe that's exactly what we want
to do here?
This should presumably be settled in the development release before the SRU
proceeds, so I'm deferring SRU review for now.
--
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/1920837
Title:
apport bugs from official raspi or riscv images are not identified
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Focal:
In Progress
Status in apport source package in Groovy:
In Progress
Bug description:
It would be helpful if bugs reported from images for Raspberry Pi's or
RISCV systems were tagged so that one could search for bugs from
systems running those images e.g. 'raspi-image'.
[Test Case]
After installing a preinstalled image of Ubuntu for Raspberry Pi do the
following:
1) run 'ubuntu-bug apport'
2) view the bug report and check the Tags field
With the current version of apport you will not see the tag 'raspi-image'.
With the version of apport in -proposed you will see the tag 'raspi-image'.
[Where problems could occur]
If the code being added is syntactically incorrect then we'd see a Traceback
which would be bad as it could affect all bug / crash reports.
[Other Info]
Since there aren't any Groovy images for RISC-V there will be nothing to test
there.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1920837/+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 1922766] Re: UP and DOWN keys behave erratically
Thanks for the bug report. I can't seem to reproduce the problem in 20.04 here... Please open two Terminal windows and in one run 'top' and in the other run 'journalctl -f'. Then reproduce the bug again. While the bug is happening, do you see high CPU usage in 'top' or any messages flooding the log in the 'journalctl -f' window? Please also try disabling extensions using the 'Extensions' app in case any of those are the problem. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1922766 Title: UP and DOWN keys behave erratically Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since the last update, a couple of days ago the UP and DOWN arrow keys don't work properly. They are either slow to react or don't work at all, very occasionally they work as expected. It is only limited to these two keys. I don't think it is a hardware issue because if I boot my laptop up with another operating system it works fine. I checked to see if my bios needs updating, but it doesn't. Also I have tried starting with an older kernel and the problem is still there so I think this has something to do with xorg and/or gnome. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 6 17:22:59 2021 DistUpgraded: 2020-09-19 18:59:22,820 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] [1043:1280] InstallationDate: Installed on 2016-11-03 (1614 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX310UA ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=eee950f6-e946-46ab-9616-45ba24e1f588 ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-09-19 (198 days ago) dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX310UA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX310UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX310UA.305:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX310UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX310UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX310UA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Sep 21 17:29:50 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.4 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922766/+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 1922723] Re: Weird CTRL+SHIFT+KEY behaviour in Xorg sessions
I can't seem to reproduce the problem using the steps provided above. Can you please try with a USB keyboard? This might be hardware- specific... ** Summary changed: - Weird CTRL+SHIFT+KEY behaviour + Weird CTRL+SHIFT+KEY behaviour in Xorg sessions ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1922723 Title: Weird CTRL+SHIFT+KEY behaviour in Xorg sessions Status in xorg-server package in Ubuntu: Incomplete Bug description: I run a newly installed Ubuntu Hirsute. Inside a "Ubuntu on Xorg"(GNOME) session i cannot use CTRL+SHIFT+KEY shortcut normally. If I press first CTRL, then SHIFT, then KEY everything works. If I press SHIFT, then CTRL then KEY nothing happens. On the Ubuntu (GNOME Wayland) session things works out normal. Step to reproduce: * Log in in a Xorg session * Open gnome-terminal * Press CTRL + SHIFT + "N" (in this order), a new terminal window appears * Press SHIFT + CTRL + "N" (in this order), nothing happens. The same happens with Firefox, Nautilus and other apps. Possibly, Related to this, I also found that, only on a Xorg session, during a Wine-runned gamed I play "CTRL + KEY" behaves just like "KEY". But this might be a Wine bug. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 6 14:14:37 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.11.0-13-generic, x86_64: installed virtualbox, 6.1.18, 5.11.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:84a7] Subsystem: Hewlett-Packard Company GM108M [GeForce MX130] [103c:84a7] InstallationDate: Installed on 2021-03-31 (5 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 002: ID 05c8:03c7 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera Bus 001 Device 004: ID 046d:c51b Logitech, Inc. V220 Cordless Optical Mouse for Notebooks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-da0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=81ec23d7-e690-4f52-b570-c2c252d1f0e8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2018 dmi.bios.release: 15.7 dmi.bios.vendor: Insyde dmi.bios.version: F.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A7 dmi.board.vendor: HP dmi.board.version: 80.31 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 80.31 dmi.modalias: dmi:bvnInsyde:bvrF.07:bd11/21/2018:br15.7:efr80.31:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A7:rvr80.31:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 4YC20EA#ABZ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1922723/+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 1922822] Re: Please remove qtpowerd from Ubuntu
** Changed in: qtpowerd (Ubuntu) Status: Opinion => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtpowerd in Ubuntu. https://bugs.launchpad.net/bugs/1922822 Title: Please remove qtpowerd from Ubuntu Status in qtpowerd package in Ubuntu: New Bug description: Unmaintained Ubuntu-only package that is part of the obsolete Ubuntu Touch stack. FTBFS on rebuild and has no rdeps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtpowerd/+bug/1922822/+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 1922823] Re: Please remove poppler-qml-plugin from Ubuntu
Drew, I'm not sure why you changed all of the removal tickets I just opened to the Opinion status, but that'll remove them from the archive team's queue. Changing back to New accordingly. ** Changed in: poppler-qml-plugin (Ubuntu) Status: Opinion => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler-qml-plugin in Ubuntu. https://bugs.launchpad.net/bugs/1922823 Title: Please remove poppler-qml-plugin from Ubuntu Status in poppler-qml-plugin package in Ubuntu: New Bug description: Unmaintained Ubuntu-only package that is part of the obsolete Ubuntu Touch stack. FTBFS on rebuild and has no rdeps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler-qml-plugin/+bug/1922823/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Maybe it was this we were waiting for: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/507 Regardless, PulseAudio version 15 (not yet released) is the goal. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1922822] Re: Please remove qtpowerd from Ubuntu
** Changed in: qtpowerd (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtpowerd in Ubuntu. https://bugs.launchpad.net/bugs/1922822 Title: Please remove qtpowerd from Ubuntu Status in qtpowerd package in Ubuntu: Opinion Bug description: Unmaintained Ubuntu-only package that is part of the obsolete Ubuntu Touch stack. FTBFS on rebuild and has no rdeps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtpowerd/+bug/1922822/+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 1922823] Re: Please remove poppler-qml-plugin from Ubuntu
** Changed in: poppler-qml-plugin (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler-qml-plugin in Ubuntu. https://bugs.launchpad.net/bugs/1922823 Title: Please remove poppler-qml-plugin from Ubuntu Status in poppler-qml-plugin package in Ubuntu: Opinion Bug description: Unmaintained Ubuntu-only package that is part of the obsolete Ubuntu Touch stack. FTBFS on rebuild and has no rdeps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler-qml-plugin/+bug/1922823/+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 1922792] Re: Bluez should notify users when they need to reboot to apply changes
** Tags added: hirsute raspi ** Changed in: bluez (Ubuntu) Importance: Undecided => Low ** Changed in: bluez (Ubuntu) Status: New => Triaged ** Summary changed: - Bluez should notify users when they need to reboot to apply changes + Bluez should notify users when they need to reboot to apply changes on arm64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1922792 Title: Bluez should notify users when they need to reboot to apply changes on arm64 Status in bluez package in Ubuntu: Triaged Bug description: In the case of upgrading bluez on certain raspberry pi devices, a reboot may be required to apply the changes. We should add a check for this scenario in the postinst script. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1922792/+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 1922548] Re: Error accessing Home of another user [Oops! Something went wrong. Unhandled error message: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Unix process subject
** Also affects: policykit via https://gitlab.freedesktop.org/polkit/polkit/-/issues/136 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1922548 Title: Error accessing Home of another user [Oops! Something went wrong. Unhandled error message: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Unix process subject does not have uid set] Status in PolicyKit: Unknown Status in nautilus package in Ubuntu: New Status in policykit-1 package in Ubuntu: New Bug description: On my PC I have some different users. If from one user I try to access the Home directory of a different user I enter the password and then I have a crash. Seen attached screenshot. Problem happens with both x11 and Wayland sessions. More: opening this bug I have the messages: corrado@corrado-n2-hh-0402:~$ ubuntu-bug -w ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 227, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 945, in attach_casper_md5check with open(location) as json_file: PermissionError: [Errno 13] Permission denied: '/var/log/installer/casper-md5check.json' corrado@corrado-n2-hh-0402:~$ [GFX1-]: glxtest: Could not connect to wayland socket ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 5 12:05:27 2021 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1137, 611)' InstallationDate: Installed on 2021-04-02 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210402) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.39.2-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/policykit/+bug/1922548/+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 1922826] [NEW] /usr/bin/pulseaudio:6:pa_alsa_element_get:element_parse_volume_limit:pa_config_parse:pa_config_parse:pa_alsa_path_new
*** This bug is a duplicate of bug 1922621 *** https://bugs.launchpad.net/bugs/1922621 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:13.99.1-1ubuntu3.10, the problem page at https://errors.ubuntu.com/problem/5bc83665288ea40e5ad4564ebe20d1ab81d04fd3 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/. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1922826 Title: /usr/bin/pulseaudio:6:pa_alsa_element_get:element_parse_volume_limit:pa_config_parse:pa_config_parse:pa_alsa_path_new Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:13.99.1-1ubuntu3.10, the problem page at https://errors.ubuntu.com/problem/5bc83665288ea40e5ad4564ebe20d1ab81d04fd3 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/ubuntu/+source/pulseaudio/+bug/1922826/+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 1922621] Re: PulseAudio Assertion 'section' in pa_alsa_element_get() when laptop in docking station
Thanks. That shows the stack trace is: pa_alsa_element_get → element_parse_volume_limit → pa_config_parse → pa_config_parse → pa_alsa_path_new Next please report the issue to the developers at: https://gitlab.freedesktop.org/groups/pulseaudio/-/issues and then tell us the new issue ID. ** Description changed: + https://errors.ubuntu.com/problem/5bc83665288ea40e5ad4564ebe20d1ab81d04fd3 + + --- + PulseAudio 1:13.99.1-1ubuntu3.10, Ubuntu 20.04.2 Laptop: Lenovo ThinkPad X1 Carbon 7th Soundcards: - 0 [sofhdadsp ]: sof-hda-dsp - sof-hda-dsp - LENOVO-20QES01L00-ThinkPadX1Carbon7th - 1 [Audio ]: USB-Audio - ThinkPad Dock USB Audio - Generic ThinkPad Dock USB Audio at usb-:00:14.0-5.4.4, high speed + 0 [sofhdadsp ]: sof-hda-dsp - sof-hda-dsp + LENOVO-20QES01L00-ThinkPadX1Carbon7th + 1 [Audio ]: USB-Audio - ThinkPad Dock USB Audio + Generic ThinkPad Dock USB Audio at usb-:00:14.0-5.4.4, high speed When the laptop is not docked, everything works fine. Sound is played using the laptop internal speakers. When the laptop is in the docking station, the sound in KDE is not working (no sound devices are shown). Pulseaudio is crashing with an Assertion. D: [pulseaudio] alsa-mixer.c: Profile output:analog-stereo supported. D: [pulseaudio] conf-parser.c: Parsing configuration file '/usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf' D: [pulseaudio] conf-parser.c: Parsing configuration file '/usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common' E: [pulseaudio] alsa-mixer.c: Assertion 'section' failed at modules/alsa/alsa-mixer.c:1954, function pa_alsa_element_get(). Aborting. - - Prime suspect for the change is an "Embedded Controller Update" by fwupdmgr, which was installed a while ago, and applied during last reboot. This cannot be downgraded (Lenovo does not support that). - + Prime suspect for the change is an "Embedded Controller Update" by + fwupdmgr, which was installed a while ago, and applied during last + reboot. This cannot be downgraded (Lenovo does not support that). More details from "pulseaudio -", docked: I: [pulseaudio] module.c: Loaded "module-stream-restore" (index: #1; argument: ""). D: [pulseaudio] database-tdb.c: Opened TDB database '/home/ads/.pulse/8815a710d4ce4667b8c98403eec58bed-card-database.tdb' I: [pulseaudio] module-card-restore.c: Successfully opened database file '/home/ads/.pulse/8815a710d4ce4667b8c98403eec58bed-card-database'. I: [pulseaudio] module.c: Loaded "module-card-restore" (index: #2; argument: ""). I: [pulseaudio] module.c: Loaded "module-augment-properties" (index: #3; argument: ""). I: [pulseaudio] module.c: Loaded "module-switch-on-port-available" (index: #4; argument: ""). D: [pulseaudio] module.c: Checking for existence of '/usr/lib/pulse-13.99.1/modules/module-switch-on-connect.so': success I: [pulseaudio] module.c: Loaded "module-switch-on-connect" (index: #5; argument: ""). D: [pulseaudio] module.c: Checking for existence of '/usr/lib/pulse-13.99.1/modules/module-udev-detect.so': success D: [pulseaudio] module-udev-detect.c: /dev/snd/controlC1 is accessible: yes D: [pulseaudio] module-udev-detect.c: /devices/pci:00/:00:14.0/usb1/1-5/1-5.4/1-5.4.4/1-5.4.4:1.0/sound/card1 is busy: no D: [pulseaudio] module-udev-detect.c: Loading module-alsa-card with arguments 'device_id="1" name="usb-Generic_ThinkPad_Dock_USB_Audio-00" card_name="alsa_card.usb-Generic_ThinkPad_Dock_USB_Audio-00" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1"' D: [pulseaudio] dbus-util.c: Successfully connected to D-Bus session bus 0dd0d23e5ac302eec692d2b2606b9c78 as :1.81 D: [pulseaudio] reserve-wrap.c: Successfully acquired reservation lock on device 'Audio1' I: [pulseaudio] (alsa-lib)main.c: error: failed to import hw:1 use case configuration -2 I: [pulseaudio] (alsa-lib)main.c: error: failed to import ThinkPad Dock USB Audio use case configuration -2 I: [pulseaudio] alsa-ucm.c: UCM not available for card ThinkPad Dock USB Audio D: [pulseaudio] conf-parser.c: Parsing configuration file '/usr/share/pulseaudio/alsa-mixer/profile-sets/default.conf' D: [pulseaudio] alsa-mixer.c: Looking at profile input:analog-stereo D: [pulseaudio] alsa-mixer.c: Checking for recording on Analog Stereo (analog-stereo) D: [pulseaudio] alsa-util.c: Trying front:1 with SND_PCM_NO_AUTO_FORMAT ... - Not docked: I: [pulseaudio] module.c: Loaded "module-stream-restore" (index: #1; argument: ""). D: [pulseaudio] database-tdb.c: Opened TDB database '/home/ads/.pulse/8815a710d4ce4667b8c98403eec58bed-card-database.tdb' I: [pulseaudio] module-card-restore.c: Successfully opened database file
[Touch-packages] [Bug 1922826] Re: /usr/bin/pulseaudio:6:pa_alsa_element_get:element_parse_volume_limit:pa_config_parse:pa_config_parse:pa_alsa_path_new
*** This bug is a duplicate of bug 1922621 *** https://bugs.launchpad.net/bugs/1922621 ** This bug has been marked a duplicate of bug 1922621 PulseAudio Assertion 'section' in pa_alsa_element_get() when laptop in docking station -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1922826 Title: /usr/bin/pulseaudio:6:pa_alsa_element_get:element_parse_volume_limit:pa_config_parse:pa_config_parse:pa_alsa_path_new Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:13.99.1-1ubuntu3.10, the problem page at https://errors.ubuntu.com/problem/5bc83665288ea40e5ad4564ebe20d1ab81d04fd3 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/ubuntu/+source/pulseaudio/+bug/1922826/+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 1615381] Re: apt-get autoremove may remove current kernel
This bug was fixed in the package apt - 1.6.13
---
apt (1.6.13) bionic; urgency=medium
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
[ Julian Andres Klode ]
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all translations when building the cache (LP: #1907850)
* Add basic support for the Protected field
* Do not require force-loopbreak on Important packages
(Closes: #983014) (LP: #1916725)
* Protect currently running kernel at run-time (LP: #1615381)
* Make ADDARG{,C}() macros expand to single statements
* Improve immediate configuration handling (LP: #1871268)
- Do not immediately configure m-a: same packages in lockstep
- Ignore failures from immediate configuration. This does not change the
actual installation ordering - we never passed the return code to the
caller and installation went underway anyway if it could be ordered at a
later stage, this just removes spurious after-the-fact errors.
(Closes: #973305, #188161, #211075, #649588)
* Default Acquire::AllowReleaseInfoChange::Suite to "true" (Closes: #931566)
(LP: #1918907)
[ Balint Reczey ]
* Set LC_ALL=C.UTF-8 for unattended-upgrades environment when parsing its
--help
(LP: #1806076)
-- Julian Andres Klode Fri, 12 Mar 2021 14:09:15
+0100
** Changed in: apt (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: apt (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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1615381
Title:
apt-get autoremove may remove current kernel
Status in apt package in Ubuntu:
Fix Released
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Trusty:
Won't Fix
Status in unattended-upgrades source package in Xenial:
Fix Released
Status in unattended-upgrades source package in Artful:
Won't Fix
Status in apt source package in Bionic:
Fix Released
Status in apt source package in Focal:
Fix Released
Status in apt source package in Groovy:
Fix Released
Status in apt source package in Hirsute:
Fix Released
Bug description:
[Impact]
APT will try and fail to remove the currently running kernel, when booted
into an older kernel that is not protected. May wreak some havoc if mixed with
other operations to the point that apt goes weird and needs manual fixing up.
[Test case]
For the SRUs we have included an automated test case that starts with an
empty autoremove config file, and then checks that the running kernel is
protected at runtime.
You can also test manually, but it's not necessary:
- Install new kernel
- Reboot into kernel not listed as protected in 01autoremove-kernels
- Run autoremove
[Where problems could occur]
We may more easily run out of space in /boot. hirsute has new autoremoval
code that runs completely at runtime; but that seems a bit large to SRU after
only a few weeks in hirsute. Hence, we should protect the current kernel _in
addition_ to the other kernels, just like unattended-upgrades and
update-manager do. This increases the risk of filling up /boot compared to
older apt versions, but is at the same level as unattended-upgrades and
update-manager.
[Original bug report]
This may happen, if you boot one of the older kernels, that is not
protected by /etc/apt/apt.conf.d/01autoremove-kernels
Workaround: run
/etc/kernel/postinst.d/apt-auto-removal
during each boot (e.g. by using cron).
Note: The workaround breaks autoremoving feature of new unneeded kernels in
unattended-upgrades i.e. the setting
'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default
in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set
in '/etc/apt/apt.conf.d/50unattended-upgrades'.
In shell:
$ uname -r
4.4.0-22-generic
$ apt-get -s autoremove
NOTE: This is only a simulation!
apt-get needs root privileges for real execution.
Keep also in mind that locking is deactivated,
so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22
linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic
linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic
linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic
linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic
0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded.
ProblemType: Bug
[Touch-packages] [Bug 1615381] Re: apt-get autoremove may remove current kernel
This bug was fixed in the package apt - 2.0.5
---
apt (2.0.5) focal; urgency=medium
[ Julian Andres Klode ]
* private-search: Only use V.TranslatedDescription() if good (LP: #1877987)
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all translations when building the cache (LP: #1907850)
* Add basic support for the Protected field, and do not require
force-loopbreak
on Protected/Important packages (Closes: #983014) (LP: #1916725)
* Protect currently running kernel at run-time (LP: #1615381)
* Make ADDARG{,C}() macros expand to single statements
* Default Acquire::AllowReleaseInfoChange::Suite to "true" (Closes: #931566)
(LP: #1918907)
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
-- Julian Andres Klode Fri, 12 Mar 2021 12:47:30
+0100
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1615381
Title:
apt-get autoremove may remove current kernel
Status in apt package in Ubuntu:
Fix Released
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Trusty:
Won't Fix
Status in unattended-upgrades source package in Xenial:
Fix Released
Status in unattended-upgrades source package in Artful:
Won't Fix
Status in apt source package in Bionic:
Fix Released
Status in apt source package in Focal:
Fix Released
Status in apt source package in Groovy:
Fix Released
Status in apt source package in Hirsute:
Fix Released
Bug description:
[Impact]
APT will try and fail to remove the currently running kernel, when booted
into an older kernel that is not protected. May wreak some havoc if mixed with
other operations to the point that apt goes weird and needs manual fixing up.
[Test case]
For the SRUs we have included an automated test case that starts with an
empty autoremove config file, and then checks that the running kernel is
protected at runtime.
You can also test manually, but it's not necessary:
- Install new kernel
- Reboot into kernel not listed as protected in 01autoremove-kernels
- Run autoremove
[Where problems could occur]
We may more easily run out of space in /boot. hirsute has new autoremoval
code that runs completely at runtime; but that seems a bit large to SRU after
only a few weeks in hirsute. Hence, we should protect the current kernel _in
addition_ to the other kernels, just like unattended-upgrades and
update-manager do. This increases the risk of filling up /boot compared to
older apt versions, but is at the same level as unattended-upgrades and
update-manager.
[Original bug report]
This may happen, if you boot one of the older kernels, that is not
protected by /etc/apt/apt.conf.d/01autoremove-kernels
Workaround: run
/etc/kernel/postinst.d/apt-auto-removal
during each boot (e.g. by using cron).
Note: The workaround breaks autoremoving feature of new unneeded kernels in
unattended-upgrades i.e. the setting
'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default
in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set
in '/etc/apt/apt.conf.d/50unattended-upgrades'.
In shell:
$ uname -r
4.4.0-22-generic
$ apt-get -s autoremove
NOTE: This is only a simulation!
apt-get needs root privileges for real execution.
Keep also in mind that locking is deactivated,
so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22
linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic
linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic
linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic
linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic
0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apt 1.2.12~ubuntu16.04.1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Aug 21 16:11:27 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-04-28 (114 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified]
mtime.conffile..etc.kernel.postinst.d.apt-auto-removal:
2016-07-30T12:15:32.706300
To
[Touch-packages] [Bug 1693900] Re: apt-get update should return exit code != 0 on error
This bug was fixed in the package apt - 2.0.5
---
apt (2.0.5) focal; urgency=medium
[ Julian Andres Klode ]
* private-search: Only use V.TranslatedDescription() if good (LP: #1877987)
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all translations when building the cache (LP: #1907850)
* Add basic support for the Protected field, and do not require
force-loopbreak
on Protected/Important packages (Closes: #983014) (LP: #1916725)
* Protect currently running kernel at run-time (LP: #1615381)
* Make ADDARG{,C}() macros expand to single statements
* Default Acquire::AllowReleaseInfoChange::Suite to "true" (Closes: #931566)
(LP: #1918907)
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
-- Julian Andres Klode Fri, 12 Mar 2021 12:47:30
+0100
--
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/1693900
Title:
apt-get update should return exit code != 0 on error
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Confirmed
Status in apt source package in Bionic:
Fix Released
Status in apt source package in Focal:
Fix Released
Status in apt source package in Groovy:
Fix Released
Status in apt package in Debian:
Fix Released
Bug description:
[Impact]
There is no way for scripts to run apt update and be sure that it was
entirely successful.
We introduce a new flag, --error-on=any that makes apt update also
error out on transient errors.
[Test plan]
We have included a test in the test-suite in
test-apt-update-failure-propagation that ensures that warnings become errors.
[Where problems could occur]
If there's an issue some warnings for transient errors could become errors,
or worse I suppose it's possible but unlikely for errors to be reported as
warnings...
Since the new behavior is behind a flag, regression potential for
existing scripts is low if there is no bug.
[Original bug report]
When running 'apt-get update' (e.g. on a container install post-
install script), apt-get return with exit code 0, even so it wasn't
able to "update" properly. E.g.:
+ apt-get update
Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
Temporary failure resolving 'security.ubuntu.com'
Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
Reading package lists... Done
W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
W: Failed to fetch
http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary
failure resolving 'de.archive.ubuntu.com'
W: Failed to fetch
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary
failure resolving 'security.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old ones
used instead.
It should be corrected to return useful exit code, so that scripts can
take the appropriate actions ...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1693900/+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 1806076] Re: unattended-upgrade --help raises UnicodeEncodeError when stdout encoding is ascii
This bug was fixed in the package apt - 1.6.13
---
apt (1.6.13) bionic; urgency=medium
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
[ Julian Andres Klode ]
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all translations when building the cache (LP: #1907850)
* Add basic support for the Protected field
* Do not require force-loopbreak on Important packages
(Closes: #983014) (LP: #1916725)
* Protect currently running kernel at run-time (LP: #1615381)
* Make ADDARG{,C}() macros expand to single statements
* Improve immediate configuration handling (LP: #1871268)
- Do not immediately configure m-a: same packages in lockstep
- Ignore failures from immediate configuration. This does not change the
actual installation ordering - we never passed the return code to the
caller and installation went underway anyway if it could be ordered at a
later stage, this just removes spurious after-the-fact errors.
(Closes: #973305, #188161, #211075, #649588)
* Default Acquire::AllowReleaseInfoChange::Suite to "true" (Closes: #931566)
(LP: #1918907)
[ Balint Reczey ]
* Set LC_ALL=C.UTF-8 for unattended-upgrades environment when parsing its
--help
(LP: #1806076)
-- Julian Andres Klode Fri, 12 Mar 2021 14:09:15
+0100
** Changed in: apt (Ubuntu Bionic)
Status: Fix Committed => 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/1806076
Title:
unattended-upgrade --help raises UnicodeEncodeError when stdout
encoding is ascii
Status in apt package in Ubuntu:
Fix Released
Status in unattended-upgrades package in Ubuntu:
Won't Fix
Status in apt source package in Xenial:
New
Status in unattended-upgrades source package in Xenial:
Won't Fix
Status in apt source package in Bionic:
Fix Released
Status in unattended-upgrades source package in Bionic:
Won't Fix
Bug description:
[Impact]
* unattended-upgrades --help crashes in apt.systemd.daily script when
locale is not in UTF-8.
[Test Case]
In the fixed case no crash is observed.
rbalint@yogi:~$ lxc launch ubuntu:18.04 bb-lp-1806076
Creating bb-lp-1806076
Starting bb-lp-1806076
rbalint@yogi:~$ lxc shell bb-lp-1806076
mesg: ttyname failed: No such device
root@bb-lp-1806076:~# apt install -yqq language-pack-ru-base
The following package was automatically installed and is no longer required:
libfreetype6
Use 'apt autoremove' to remove it.
The following additional packages will be installed:
language-pack-ru
The following NEW packages will be installed:
language-pack-ru language-pack-ru-base
0 upgraded, 2 newly installed, 0 to remove and 7 not upgraded.
Need to get 2310 kB of archives.
After this operation, 11.8 MB of additional disk space will be used.
Selecting previously unselected package language-pack-ru-base.
(Reading database ... 28536 files and directories currently installed.)
Preparing to unpack .../language-pack-ru-base_1%3a18.04+20180712_all.deb ...
Unpacking language-pack-ru-base (1:18.04+20180712) ...
Selecting previously unselected package language-pack-ru.
Preparing to unpack .../language-pack-ru_1%3a18.04+20180712_all.deb ...
Unpacking language-pack-ru (1:18.04+20180712) ...
Setting up language-pack-ru (1:18.04+20180712) ...
Setting up language-pack-ru-base (1:18.04+20180712) ...
Generating locales (this might take a while)...
ru_RU.UTF-8... done
ru_UA.UTF-8... done
Generation complete.
root@bb-lp-1806076:~# echo LANG=ru_RU | tee /etc/default/locale
LANG=ru_RU
root@bb-lp-1806076:~#
/usr/lib/apt/apt.systemd.daily update
Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 2171, in
(options, args) = parser.parse_args() # type: ignore
File "/usr/lib/python3.6/optparse.py", line 1387, in parse_args
stop = self._process_args(largs, rargs, values)
File "/usr/lib/python3.6/optparse.py", line 1427, in _process_args
self._process_long_opt(rargs, values)
File "/usr/lib/python3.6/optparse.py", line 1501, in _process_long_opt
option.process(opt, value, values, self)
File "/usr/lib/python3.6/optparse.py", line 785, in process
self.action, self.dest, opt, value, values, parser)
File "/usr/lib/python3.6/optparse.py", line 807, in take_action
parser.print_help()
File "/usr/lib/python3.6/optparse.py", line 1647, in print_help
file.write(self.format_help())
UnicodeEncodeError: 'ascii' codec can't encode characters in position
126-133: ordinal not in range(128)
root@bb-lp-1806076:~# echo LANG=ru_RU.UTF-8 | tee /etc/default/locale
LANG=ru_RU.UTF-8
root@bb-lp-1806076:~#
[Touch-packages] [Bug 1806076] Update Released
The verification of the Stable Release Update for apt 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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1806076 Title: unattended-upgrade --help raises UnicodeEncodeError when stdout encoding is ascii Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Won't Fix Status in apt source package in Xenial: New Status in unattended-upgrades source package in Xenial: Won't Fix Status in apt source package in Bionic: Fix Released Status in unattended-upgrades source package in Bionic: Won't Fix Bug description: [Impact] * unattended-upgrades --help crashes in apt.systemd.daily script when locale is not in UTF-8. [Test Case] In the fixed case no crash is observed. rbalint@yogi:~$ lxc launch ubuntu:18.04 bb-lp-1806076 Creating bb-lp-1806076 Starting bb-lp-1806076 rbalint@yogi:~$ lxc shell bb-lp-1806076 mesg: ttyname failed: No such device root@bb-lp-1806076:~# apt install -yqq language-pack-ru-base The following package was automatically installed and is no longer required: libfreetype6 Use 'apt autoremove' to remove it. The following additional packages will be installed: language-pack-ru The following NEW packages will be installed: language-pack-ru language-pack-ru-base 0 upgraded, 2 newly installed, 0 to remove and 7 not upgraded. Need to get 2310 kB of archives. After this operation, 11.8 MB of additional disk space will be used. Selecting previously unselected package language-pack-ru-base. (Reading database ... 28536 files and directories currently installed.) Preparing to unpack .../language-pack-ru-base_1%3a18.04+20180712_all.deb ... Unpacking language-pack-ru-base (1:18.04+20180712) ... Selecting previously unselected package language-pack-ru. Preparing to unpack .../language-pack-ru_1%3a18.04+20180712_all.deb ... Unpacking language-pack-ru (1:18.04+20180712) ... Setting up language-pack-ru (1:18.04+20180712) ... Setting up language-pack-ru-base (1:18.04+20180712) ... Generating locales (this might take a while)... ru_RU.UTF-8... done ru_UA.UTF-8... done Generation complete. root@bb-lp-1806076:~# echo LANG=ru_RU | tee /etc/default/locale LANG=ru_RU root@bb-lp-1806076:~# /usr/lib/apt/apt.systemd.daily update Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2171, in (options, args) = parser.parse_args() # type: ignore File "/usr/lib/python3.6/optparse.py", line 1387, in parse_args stop = self._process_args(largs, rargs, values) File "/usr/lib/python3.6/optparse.py", line 1427, in _process_args self._process_long_opt(rargs, values) File "/usr/lib/python3.6/optparse.py", line 1501, in _process_long_opt option.process(opt, value, values, self) File "/usr/lib/python3.6/optparse.py", line 785, in process self.action, self.dest, opt, value, values, parser) File "/usr/lib/python3.6/optparse.py", line 807, in take_action parser.print_help() File "/usr/lib/python3.6/optparse.py", line 1647, in print_help file.write(self.format_help()) UnicodeEncodeError: 'ascii' codec can't encode characters in position 126-133: ordinal not in range(128) root@bb-lp-1806076:~# echo LANG=ru_RU.UTF-8 | tee /etc/default/locale LANG=ru_RU.UTF-8 root@bb-lp-1806076:~# /usr/lib/apt/apt.systemd.daily update root@bb-lp-1806076:~# [Where problems could occur] * Nowhere, really. The fix is setting LC_ALL=C.UTF-8 for u-u --help and it is processed by grep then. [Original Bug Text] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.6, the problem page at https://errors.ubuntu.com/problem/b3e3265e302351558260f54ae37c7b4c193dfc95 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/. Also seen in: * https://errors.ubuntu.com/problem/936bb1c75c4efe018f968a5773b820bcf52c298a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1806076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1693900] Re: apt-get update should return exit code != 0 on error
This bug was fixed in the package apt - 1.6.13
---
apt (1.6.13) bionic; urgency=medium
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
[ Julian Andres Klode ]
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all translations when building the cache (LP: #1907850)
* Add basic support for the Protected field
* Do not require force-loopbreak on Important packages
(Closes: #983014) (LP: #1916725)
* Protect currently running kernel at run-time (LP: #1615381)
* Make ADDARG{,C}() macros expand to single statements
* Improve immediate configuration handling (LP: #1871268)
- Do not immediately configure m-a: same packages in lockstep
- Ignore failures from immediate configuration. This does not change the
actual installation ordering - we never passed the return code to the
caller and installation went underway anyway if it could be ordered at a
later stage, this just removes spurious after-the-fact errors.
(Closes: #973305, #188161, #211075, #649588)
* Default Acquire::AllowReleaseInfoChange::Suite to "true" (Closes: #931566)
(LP: #1918907)
[ Balint Reczey ]
* Set LC_ALL=C.UTF-8 for unattended-upgrades environment when parsing its
--help
(LP: #1806076)
-- Julian Andres Klode Fri, 12 Mar 2021 14:09:15
+0100
** Changed in: apt (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: apt (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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1693900
Title:
apt-get update should return exit code != 0 on error
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Confirmed
Status in apt source package in Bionic:
Fix Released
Status in apt source package in Focal:
Fix Released
Status in apt source package in Groovy:
Fix Released
Status in apt package in Debian:
Fix Released
Bug description:
[Impact]
There is no way for scripts to run apt update and be sure that it was
entirely successful.
We introduce a new flag, --error-on=any that makes apt update also
error out on transient errors.
[Test plan]
We have included a test in the test-suite in
test-apt-update-failure-propagation that ensures that warnings become errors.
[Where problems could occur]
If there's an issue some warnings for transient errors could become errors,
or worse I suppose it's possible but unlikely for errors to be reported as
warnings...
Since the new behavior is behind a flag, regression potential for
existing scripts is low if there is no bug.
[Original bug report]
When running 'apt-get update' (e.g. on a container install post-
install script), apt-get return with exit code 0, even so it wasn't
able to "update" properly. E.g.:
+ apt-get update
Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
Temporary failure resolving 'security.ubuntu.com'
Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
Reading package lists... Done
W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
W: Failed to fetch
http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary
failure resolving 'de.archive.ubuntu.com'
W: Failed to fetch
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary
failure resolving 'security.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old ones
used instead.
It should be corrected to return useful exit code, so that scripts can
take the appropriate actions ...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1693900/+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 1877987] Re: apt search coredumping
This bug was fixed in the package apt - 2.0.5
---
apt (2.0.5) focal; urgency=medium
[ Julian Andres Klode ]
* private-search: Only use V.TranslatedDescription() if good (LP: #1877987)
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all translations when building the cache (LP: #1907850)
* Add basic support for the Protected field, and do not require
force-loopbreak
on Protected/Important packages (Closes: #983014) (LP: #1916725)
* Protect currently running kernel at run-time (LP: #1615381)
* Make ADDARG{,C}() macros expand to single statements
* Default Acquire::AllowReleaseInfoChange::Suite to "true" (Closes: #931566)
(LP: #1918907)
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
-- Julian Andres Klode Fri, 12 Mar 2021 12:47:30
+0100
** Changed in: apt (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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1877987
Title:
apt search coredumping
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Focal:
Fix Released
Bug description:
[Impact]
Search sometimes crashes if no translated description is available, as the
translated description object was used without a check as to whether it exists.
[Test case]
No reproducer available at the moment.
[Where problems could occur]
In search command only, and only when looking at descriptions
[Original bug report]
root@citoyx:/var/crash# apt search jdk
Sorting... Done
Segmentation fault (core dumped)
May 11 12:34:25 citoyx kernel: [ 1354.337907] apt[10418]: segfault at
7f67292dcfc0 ip 7f6309ce4997 sp 7ffdab880930 error 4 in
libapt-pkg.so.6.0.0[7f6309bb5000+147000]
May 11 12:34:25 citoyx kernel: [ 1354.337916] Code: 48 8b 45 18 48 8b 04 d0
48 83 c4 08 5b 5d c3 0f 1f 40 00 f3 0f 1e fa 55 48 89 fd 53 48 89 f3 48 83 ec
08 48 8b 06 48 8b 4e 08 <8b> 10 48 8d 04 d5 00 00 00 00 48 29 d0 48 8b 51 60 48
8d 04 c2 0f
root@citoyx:/var/crash# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"
apt search is coredumping
While apt install/upgrade/update is running fine
crash file in attachment.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1877987/+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 1877987] Update Released
The verification of the Stable Release Update for apt 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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1877987 Title: apt search coredumping Status in apt package in Ubuntu: Fix Released Status in apt source package in Focal: Fix Released Bug description: [Impact] Search sometimes crashes if no translated description is available, as the translated description object was used without a check as to whether it exists. [Test case] No reproducer available at the moment. [Where problems could occur] In search command only, and only when looking at descriptions [Original bug report] root@citoyx:/var/crash# apt search jdk Sorting... Done Segmentation fault (core dumped) May 11 12:34:25 citoyx kernel: [ 1354.337907] apt[10418]: segfault at 7f67292dcfc0 ip 7f6309ce4997 sp 7ffdab880930 error 4 in libapt-pkg.so.6.0.0[7f6309bb5000+147000] May 11 12:34:25 citoyx kernel: [ 1354.337916] Code: 48 8b 45 18 48 8b 04 d0 48 83 c4 08 5b 5d c3 0f 1f 40 00 f3 0f 1e fa 55 48 89 fd 53 48 89 f3 48 83 ec 08 48 8b 06 48 8b 4e 08 <8b> 10 48 8d 04 d5 00 00 00 00 48 29 d0 48 8b 51 60 48 8d 04 c2 0f root@citoyx:/var/crash# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" apt search is coredumping While apt install/upgrade/update is running fine crash file in attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1877987/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
This bug was fixed in the package apt - 1.6.13
---
apt (1.6.13) bionic; urgency=medium
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
[ Julian Andres Klode ]
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all translations when building the cache (LP: #1907850)
* Add basic support for the Protected field
* Do not require force-loopbreak on Important packages
(Closes: #983014) (LP: #1916725)
* Protect currently running kernel at run-time (LP: #1615381)
* Make ADDARG{,C}() macros expand to single statements
* Improve immediate configuration handling (LP: #1871268)
- Do not immediately configure m-a: same packages in lockstep
- Ignore failures from immediate configuration. This does not change the
actual installation ordering - we never passed the return code to the
caller and installation went underway anyway if it could be ordered at a
later stage, this just removes spurious after-the-fact errors.
(Closes: #973305, #188161, #211075, #649588)
* Default Acquire::AllowReleaseInfoChange::Suite to "true" (Closes: #931566)
(LP: #1918907)
[ Balint Reczey ]
* Set LC_ALL=C.UTF-8 for unattended-upgrades environment when parsing its
--help
(LP: #1806076)
-- Julian Andres Klode Fri, 12 Mar 2021 14:09:15
+0100
** Changed in: apt (Ubuntu Bionic)
Status: Fix Committed => 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/1871268
Title:
Installation fails due to useless immediate configuration error when
"Install Third-Party Drivers" is selected
Status in Ubuntu CD Images:
Fix Released
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Bionic:
Fix Released
Status in apt source package in Focal:
Fix Released
Status in apt source package in Groovy:
Fix Released
Status in apt package in Debian:
Fix Released
Bug description:
[Impact]
Installations that really succeeded would then fail because APT could not
immediately configure a package. Which is a pointless way to fail at that
point, because everything did work out anyway.
We have two changes that help address this:
* The first one stops immediately configuring multi-arch siblings
(e.g. libc6:i386 when it's configuring libc6:amd64). This was not
necessary, and caused all the libc6:i386 failures here.
* The second change sort of also supersedes the first one: It just
ignores any errors from immediate configuration, relying on the fact
that it's checked and rectified at a later point if there are
unconfigured packages (which is what made all those failures happen
spuriously after having successfully installed everything).
[Test case]
We have one test case in EIPP format in the Debian bug 973305 which was only
helped by the second change, not the first one. Run /usr/lib/apt/planners <
eipp.log and check there are no errors.
TODO: It's unclear if the APT from proposed installed in the live
session will fix the installer, needs investigation, but would make a
useful test case.
[Regression potential]
It's imaginable that we missed something somewhere and some path that checked
for a set error doesn't check it anymore, and we report success when we hit an
error, but it seems unlikely.
Behavior of --simulate changes. This used to fail before as well, and
will now only produce a warning. We don't believe that is a reason of
concern.
[Groovy SRU]
The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable
which also incorporates changes to the documentation: A typo fix, replacing
focal with groovy in examples, and minor Dutch manual pages translation updates.
We do not have test cases for the documentation changes, and we do not
consider there to be a huge regression potential. As long as they
build, they should be readable - maybe some words are wrong in the
translation, who knows.
[Original bug report]
Test Case
1. Install Ubuntu Desktop on hardware with an nVidia card and select to
install 3rd party drivers
2. Proceed with installation
The following error message is displayed in /var/log/syslog
/plugininstall.py: Verifying downloads ...
/plugininstall.py: Failed to find package object for
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version:
'9.3.0-1ubuntu2' not found."
/plugininstall.py: Failed to find package object for
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb:
"Version: '4.4.10-10ubuntu4' not found."
/plugininstall.py: Failed to find package object for
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version:
'9.3.0-1ubuntu2' not found."
/plugininstall.py: Failed
[Touch-packages] [Bug 1907850] Re: Cache not generated for all translations
This bug was fixed in the package apt - 1.6.13
---
apt (1.6.13) bionic; urgency=medium
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
[ Julian Andres Klode ]
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all translations when building the cache (LP: #1907850)
* Add basic support for the Protected field
* Do not require force-loopbreak on Important packages
(Closes: #983014) (LP: #1916725)
* Protect currently running kernel at run-time (LP: #1615381)
* Make ADDARG{,C}() macros expand to single statements
* Improve immediate configuration handling (LP: #1871268)
- Do not immediately configure m-a: same packages in lockstep
- Ignore failures from immediate configuration. This does not change the
actual installation ordering - we never passed the return code to the
caller and installation went underway anyway if it could be ordered at a
later stage, this just removes spurious after-the-fact errors.
(Closes: #973305, #188161, #211075, #649588)
* Default Acquire::AllowReleaseInfoChange::Suite to "true" (Closes: #931566)
(LP: #1918907)
[ Balint Reczey ]
* Set LC_ALL=C.UTF-8 for unattended-upgrades environment when parsing its
--help
(LP: #1806076)
-- Julian Andres Klode Fri, 12 Mar 2021 14:09:15
+0100
** Changed in: apt (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: apt (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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1907850
Title:
Cache not generated for all translations
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Confirmed
Status in apt source package in Bionic:
Fix Released
Status in apt source package in Focal:
Fix Released
Status in apt source package in Groovy:
Fix Released
Status in apt source package in Hirsute:
Fix Released
Bug description:
[Impact]
In bug 1161743 we discovered that if a system is configured with multiple
locales, only the locales of the user who generated the apt-cache will be
available for translated descriptions.
[Test case]
An automated test case has been included as a snippet in
test/integration/test-bug-49-search-in-all-translations which runs during
autopkgtest. That's sufficient for validation.
Manual test:
# apt install locales-all # get the locale
# export LANG=sv_SE.UTF-8
# locale
LANG=sv_SE.UTF-8
LANGUAGE=
LC_CTYPE="sv_SE.UTF-8"
LC_NUMERIC="sv_SE.UTF-8"
LC_TIME="sv_SE.UTF-8"
LC_COLLATE="sv_SE.UTF-8"
LC_MONETARY="sv_SE.UTF-8"
LC_MESSAGES="sv_SE.UTF-8"
LC_PAPER="sv_SE.UTF-8"
LC_NAME="sv_SE.UTF-8"
LC_ADDRESS="sv_SE.UTF-8"
LC_TELEPHONE="sv_SE.UTF-8"
LC_MEASUREMENT="sv_SE.UTF-8"
LC_IDENTIFICATION="sv_SE.UTF-8"
LC_ALL=
# apt update
# apt-cache show tasksel | grep Desc
Description-sv: tool for selecting tasks for installation on Debian systems
Description-md5: cbbb747708986d11ea77c80b9b038fec
# apt-cache showpkg tasksel
Package: tasksel
Versions:
3.34ubuntu16
(/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages)
Description Language:
File:
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages
MD5: cbbb747708986d11ea77c80b9b038fec
Description Language: sv
File:
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-sv
MD5: cbbb747708986d11ea77c80b9b038fec
Description Language: en
File:
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en
MD5: cbbb747708986d11ea77c80b9b038fec
[...]
So far so good, but now assume the root user actually has C configured
as locale, and e.g. runs apt-cache show (or apt-daily.service does an
update):
root@g:~# rm /var/cache/apt/*.bin
root@g:~# LANG=C apt-cache show tasksel
[...]
Description-en: tool for selecting tasks for installation on Debian systems
This package provides 'tasksel', a simple interface for users who
want to configure their system to perform a specific task.
root@g:~# apt-cache showpkg tasksel
Package: tasksel
Versions:
3.34ubuntu16
(/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages)
Description Language:
File:
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages
MD5: cbbb747708986d11ea77c80b9b038fec
Description Language: en
File:
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en
[Touch-packages] [Bug 1907850] Re: Cache not generated for all translations
This bug was fixed in the package apt - 2.0.5
---
apt (2.0.5) focal; urgency=medium
[ Julian Andres Klode ]
* private-search: Only use V.TranslatedDescription() if good (LP: #1877987)
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all translations when building the cache (LP: #1907850)
* Add basic support for the Protected field, and do not require
force-loopbreak
on Protected/Important packages (Closes: #983014) (LP: #1916725)
* Protect currently running kernel at run-time (LP: #1615381)
* Make ADDARG{,C}() macros expand to single statements
* Default Acquire::AllowReleaseInfoChange::Suite to "true" (Closes: #931566)
(LP: #1918907)
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
-- Julian Andres Klode Fri, 12 Mar 2021 12:47:30
+0100
--
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/1907850
Title:
Cache not generated for all translations
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Confirmed
Status in apt source package in Bionic:
Fix Released
Status in apt source package in Focal:
Fix Released
Status in apt source package in Groovy:
Fix Released
Status in apt source package in Hirsute:
Fix Released
Bug description:
[Impact]
In bug 1161743 we discovered that if a system is configured with multiple
locales, only the locales of the user who generated the apt-cache will be
available for translated descriptions.
[Test case]
An automated test case has been included as a snippet in
test/integration/test-bug-49-search-in-all-translations which runs during
autopkgtest. That's sufficient for validation.
Manual test:
# apt install locales-all # get the locale
# export LANG=sv_SE.UTF-8
# locale
LANG=sv_SE.UTF-8
LANGUAGE=
LC_CTYPE="sv_SE.UTF-8"
LC_NUMERIC="sv_SE.UTF-8"
LC_TIME="sv_SE.UTF-8"
LC_COLLATE="sv_SE.UTF-8"
LC_MONETARY="sv_SE.UTF-8"
LC_MESSAGES="sv_SE.UTF-8"
LC_PAPER="sv_SE.UTF-8"
LC_NAME="sv_SE.UTF-8"
LC_ADDRESS="sv_SE.UTF-8"
LC_TELEPHONE="sv_SE.UTF-8"
LC_MEASUREMENT="sv_SE.UTF-8"
LC_IDENTIFICATION="sv_SE.UTF-8"
LC_ALL=
# apt update
# apt-cache show tasksel | grep Desc
Description-sv: tool for selecting tasks for installation on Debian systems
Description-md5: cbbb747708986d11ea77c80b9b038fec
# apt-cache showpkg tasksel
Package: tasksel
Versions:
3.34ubuntu16
(/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages)
Description Language:
File:
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages
MD5: cbbb747708986d11ea77c80b9b038fec
Description Language: sv
File:
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-sv
MD5: cbbb747708986d11ea77c80b9b038fec
Description Language: en
File:
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en
MD5: cbbb747708986d11ea77c80b9b038fec
[...]
So far so good, but now assume the root user actually has C configured
as locale, and e.g. runs apt-cache show (or apt-daily.service does an
update):
root@g:~# rm /var/cache/apt/*.bin
root@g:~# LANG=C apt-cache show tasksel
[...]
Description-en: tool for selecting tasks for installation on Debian systems
This package provides 'tasksel', a simple interface for users who
want to configure their system to perform a specific task.
root@g:~# apt-cache showpkg tasksel
Package: tasksel
Versions:
3.34ubuntu16
(/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages)
Description Language:
File:
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages
MD5: cbbb747708986d11ea77c80b9b038fec
Description Language: en
File:
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en
MD5: cbbb747708986d11ea77c80b9b038fec
This should show the sv locale as well given that it's still around
(also we are still running with LANG=sv_SE.UTF-8), but it only
generated the cache with the english language description in here.
[Where problems could occur]
People might end up seeing a wrong translation if other code paths are wrong,
but then they'd already see them if they explicitly configured multiple
languages and then switched the preferred one.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1907850/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to :
[Touch-packages] [Bug 1916050] Re: Invalid base64 for high-bit characters
This bug was fixed in the package apt - 1.6.13
---
apt (1.6.13) bionic; urgency=medium
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
[ Julian Andres Klode ]
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all translations when building the cache (LP: #1907850)
* Add basic support for the Protected field
* Do not require force-loopbreak on Important packages
(Closes: #983014) (LP: #1916725)
* Protect currently running kernel at run-time (LP: #1615381)
* Make ADDARG{,C}() macros expand to single statements
* Improve immediate configuration handling (LP: #1871268)
- Do not immediately configure m-a: same packages in lockstep
- Ignore failures from immediate configuration. This does not change the
actual installation ordering - we never passed the return code to the
caller and installation went underway anyway if it could be ordered at a
later stage, this just removes spurious after-the-fact errors.
(Closes: #973305, #188161, #211075, #649588)
* Default Acquire::AllowReleaseInfoChange::Suite to "true" (Closes: #931566)
(LP: #1918907)
[ Balint Reczey ]
* Set LC_ALL=C.UTF-8 for unattended-upgrades environment when parsing its
--help
(LP: #1806076)
-- Julian Andres Klode Fri, 12 Mar 2021 14:09:15
+0100
** Changed in: apt (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: apt (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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1916050
Title:
Invalid base64 for high-bit characters
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Confirmed
Status in apt source package in Bionic:
Fix Released
Status in apt source package in Focal:
Fix Released
Status in apt source package in Groovy:
Fix Released
Status in apt source package in Hirsute:
Fix Released
Bug description:
[Impact]
The Base64Encode function incorrectly encodes using char instead of uint8_t,
leading to characters with the high bit set to be encoded wrongly. This
function is used for base authentication, and high bits are set for UTF-8
character sequences, so it's likely affecting people with utf-8 user names and
passwords and might cause them to be denied access to their https resources
(though arguably they'd work around that).
[Test case]
A unit test has been added that checks that the encoding is correct.
[Where problems could occur]
This only affects the base64 encoding function, which is only used for
quoting user names and passwords in basic auth in http, but it's also exposed
to library users and like in python-apt, so problems could occur wherever they
use that base64 encoding function as well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1916050/+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 1916050] Re: Invalid base64 for high-bit characters
This bug was fixed in the package apt - 2.0.5
---
apt (2.0.5) focal; urgency=medium
[ Julian Andres Klode ]
* private-search: Only use V.TranslatedDescription() if good (LP: #1877987)
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all translations when building the cache (LP: #1907850)
* Add basic support for the Protected field, and do not require
force-loopbreak
on Protected/Important packages (Closes: #983014) (LP: #1916725)
* Protect currently running kernel at run-time (LP: #1615381)
* Make ADDARG{,C}() macros expand to single statements
* Default Acquire::AllowReleaseInfoChange::Suite to "true" (Closes: #931566)
(LP: #1918907)
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
-- Julian Andres Klode Fri, 12 Mar 2021 12:47:30
+0100
--
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/1916050
Title:
Invalid base64 for high-bit characters
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Confirmed
Status in apt source package in Bionic:
Fix Released
Status in apt source package in Focal:
Fix Released
Status in apt source package in Groovy:
Fix Released
Status in apt source package in Hirsute:
Fix Released
Bug description:
[Impact]
The Base64Encode function incorrectly encodes using char instead of uint8_t,
leading to characters with the high bit set to be encoded wrongly. This
function is used for base authentication, and high bits are set for UTF-8
character sequences, so it's likely affecting people with utf-8 user names and
passwords and might cause them to be denied access to their https resources
(though arguably they'd work around that).
[Test case]
A unit test has been added that checks that the encoding is correct.
[Where problems could occur]
This only affects the base64 encoding function, which is only used for
quoting user names and passwords in basic auth in http, but it's also exposed
to library users and like in python-apt, so problems could occur wherever they
use that base64 encoding function as well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1916050/+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 1918907] Re: Default Acquire::AllowReleaseInfoChange::Suite to "true"
This bug was fixed in the package apt - 1.6.13
---
apt (1.6.13) bionic; urgency=medium
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
[ Julian Andres Klode ]
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all translations when building the cache (LP: #1907850)
* Add basic support for the Protected field
* Do not require force-loopbreak on Important packages
(Closes: #983014) (LP: #1916725)
* Protect currently running kernel at run-time (LP: #1615381)
* Make ADDARG{,C}() macros expand to single statements
* Improve immediate configuration handling (LP: #1871268)
- Do not immediately configure m-a: same packages in lockstep
- Ignore failures from immediate configuration. This does not change the
actual installation ordering - we never passed the return code to the
caller and installation went underway anyway if it could be ordered at a
later stage, this just removes spurious after-the-fact errors.
(Closes: #973305, #188161, #211075, #649588)
* Default Acquire::AllowReleaseInfoChange::Suite to "true" (Closes: #931566)
(LP: #1918907)
[ Balint Reczey ]
* Set LC_ALL=C.UTF-8 for unattended-upgrades environment when parsing its
--help
(LP: #1806076)
-- Julian Andres Klode Fri, 12 Mar 2021 14:09:15
+0100
** Changed in: apt (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: apt (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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1918907
Title:
Default Acquire::AllowReleaseInfoChange::Suite to "true"
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Bionic:
Fix Released
Status in apt source package in Focal:
Fix Released
Bug description:
[Impact]
APT 1.6-2.0 deny third-party repositories from changing their Suite value.
This change was reverted in later apt releases, and will be reverted in 1.8 in
Debian as well, so for consistency, we want to push that change to stable
[Test plan]
We added test cases to our extensive integration test suite run by
autopkgtest.
[Where problems could occur]
It's hard to imagine anything here, we simply turn the flag for allowed from
false to true. We even add tests for Suite changes :)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918907/+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 1916725] Re: Protected/Important packages are not deconfigured, require Force-LoopBreak
This bug was fixed in the package apt - 1.6.13
---
apt (1.6.13) bionic; urgency=medium
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
[ Julian Andres Klode ]
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all translations when building the cache (LP: #1907850)
* Add basic support for the Protected field
* Do not require force-loopbreak on Important packages
(Closes: #983014) (LP: #1916725)
* Protect currently running kernel at run-time (LP: #1615381)
* Make ADDARG{,C}() macros expand to single statements
* Improve immediate configuration handling (LP: #1871268)
- Do not immediately configure m-a: same packages in lockstep
- Ignore failures from immediate configuration. This does not change the
actual installation ordering - we never passed the return code to the
caller and installation went underway anyway if it could be ordered at a
later stage, this just removes spurious after-the-fact errors.
(Closes: #973305, #188161, #211075, #649588)
* Default Acquire::AllowReleaseInfoChange::Suite to "true" (Closes: #931566)
(LP: #1918907)
[ Balint Reczey ]
* Set LC_ALL=C.UTF-8 for unattended-upgrades environment when parsing its
--help
(LP: #1806076)
-- Julian Andres Klode Fri, 12 Mar 2021 14:09:15
+0100
** Changed in: apt (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: apt (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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1916725
Title:
Protected/Important packages are not deconfigured, require Force-
LoopBreak
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Bionic:
Fix Released
Status in apt source package in Focal:
Fix Released
Status in apt source package in Groovy:
Fix Released
Status in apt source package in Hirsute:
Fix Released
Bug description:
[Impact]
If a package that is Protected: yes (or Important: yes), or one of it's
dependencies, is involved in a dependency loop with Breaks, APT requires
APT::Force-LoopBreak instead of resolving the situation directly.
On focal, we also introduce the actual support for protected packages
to enable upgrading to later releases more easily (in case a protected
package needs to be removed during the upgrade), and to make the
backport more similar to main.
[Test plan]
Run the integration test suite (the autopkgtest) :)
Our test suite covers the tests for both Breaks and Conflicts.
Breaks:
protected-sysvinit (= 1) without dependencies is installed
protected-sysvinit (= 2) Pre-Depends protected-systemd-sysv
protected-systemd-sysv (= 2) Breaks: protected-sysvinit (<< 2)
Test: Install protected-sysvinit (= 2)
Expected result: Unpacking protected-sysvinit (= 2) deconfigures
protected-sysvinit (= 1), and then we unpack and configure protected-sysvinit
(= 2) and end up with a working system.
Conflicts: As for Breaks, but the Conflicts will remove the package
temporarily, requiring the use of APT::Force-LoopBreak option.
For focal, we also do have a test to check that the Protected field is
being used.
[Where problems could occur]
We now allow dpkg to automatically deconfigure protected packages. This
should just make them behave like normal packages to APT's eye, but bugs I
guess could occur somewhere in the APT/dpkg interaction (this only applies to
releases with Protected support in dpkg, Important is not affected, it's always
been "normal" for dpkg).
During development, we accidentally simplified the patch so much that
Conflicts did not require Force-LoopBreak for temporary removal. We
fixed that, but it points out that there is a place where the loop
break check happens that is a potential regression place.
On focal, we pass additional flags to dpkg that focal's dpkg does not
understand, however, we only do that if dpkg asserts it does that, so
in practice, this should all work fine and the code path will only be
taken with >=groovy dpkg.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1916725/+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 1918907] Re: Default Acquire::AllowReleaseInfoChange::Suite to "true"
This bug was fixed in the package apt - 2.0.5
---
apt (2.0.5) focal; urgency=medium
[ Julian Andres Klode ]
* private-search: Only use V.TranslatedDescription() if good (LP: #1877987)
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all translations when building the cache (LP: #1907850)
* Add basic support for the Protected field, and do not require
force-loopbreak
on Protected/Important packages (Closes: #983014) (LP: #1916725)
* Protect currently running kernel at run-time (LP: #1615381)
* Make ADDARG{,C}() macros expand to single statements
* Default Acquire::AllowReleaseInfoChange::Suite to "true" (Closes: #931566)
(LP: #1918907)
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
-- Julian Andres Klode Fri, 12 Mar 2021 12:47:30
+0100
--
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/1918907
Title:
Default Acquire::AllowReleaseInfoChange::Suite to "true"
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Bionic:
Fix Released
Status in apt source package in Focal:
Fix Released
Bug description:
[Impact]
APT 1.6-2.0 deny third-party repositories from changing their Suite value.
This change was reverted in later apt releases, and will be reverted in 1.8 in
Debian as well, so for consistency, we want to push that change to stable
[Test plan]
We added test cases to our extensive integration test suite run by
autopkgtest.
[Where problems could occur]
It's hard to imagine anything here, we simply turn the flag for allowed from
false to true. We even add tests for Suite changes :)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918907/+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 1916725] Re: Protected/Important packages are not deconfigured, require Force-LoopBreak
This bug was fixed in the package apt - 2.0.5
---
apt (2.0.5) focal; urgency=medium
[ Julian Andres Klode ]
* private-search: Only use V.TranslatedDescription() if good (LP: #1877987)
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all translations when building the cache (LP: #1907850)
* Add basic support for the Protected field, and do not require
force-loopbreak
on Protected/Important packages (Closes: #983014) (LP: #1916725)
* Protect currently running kernel at run-time (LP: #1615381)
* Make ADDARG{,C}() macros expand to single statements
* Default Acquire::AllowReleaseInfoChange::Suite to "true" (Closes: #931566)
(LP: #1918907)
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
-- Julian Andres Klode Fri, 12 Mar 2021 12:47:30
+0100
--
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/1916725
Title:
Protected/Important packages are not deconfigured, require Force-
LoopBreak
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Bionic:
Fix Released
Status in apt source package in Focal:
Fix Released
Status in apt source package in Groovy:
Fix Released
Status in apt source package in Hirsute:
Fix Released
Bug description:
[Impact]
If a package that is Protected: yes (or Important: yes), or one of it's
dependencies, is involved in a dependency loop with Breaks, APT requires
APT::Force-LoopBreak instead of resolving the situation directly.
On focal, we also introduce the actual support for protected packages
to enable upgrading to later releases more easily (in case a protected
package needs to be removed during the upgrade), and to make the
backport more similar to main.
[Test plan]
Run the integration test suite (the autopkgtest) :)
Our test suite covers the tests for both Breaks and Conflicts.
Breaks:
protected-sysvinit (= 1) without dependencies is installed
protected-sysvinit (= 2) Pre-Depends protected-systemd-sysv
protected-systemd-sysv (= 2) Breaks: protected-sysvinit (<< 2)
Test: Install protected-sysvinit (= 2)
Expected result: Unpacking protected-sysvinit (= 2) deconfigures
protected-sysvinit (= 1), and then we unpack and configure protected-sysvinit
(= 2) and end up with a working system.
Conflicts: As for Breaks, but the Conflicts will remove the package
temporarily, requiring the use of APT::Force-LoopBreak option.
For focal, we also do have a test to check that the Protected field is
being used.
[Where problems could occur]
We now allow dpkg to automatically deconfigure protected packages. This
should just make them behave like normal packages to APT's eye, but bugs I
guess could occur somewhere in the APT/dpkg interaction (this only applies to
releases with Protected support in dpkg, Important is not affected, it's always
been "normal" for dpkg).
During development, we accidentally simplified the patch so much that
Conflicts did not require Force-LoopBreak for temporary removal. We
fixed that, but it points out that there is a place where the loop
break check happens that is a potential regression place.
On focal, we pass additional flags to dpkg that focal's dpkg does not
understand, however, we only do that if dpkg asserts it does that, so
in practice, this should all work fine and the code path will only be
taken with >=groovy dpkg.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1916725/+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 1918907] Update Released
The verification of the Stable Release Update for apt 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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1918907 Title: Default Acquire::AllowReleaseInfoChange::Suite to "true" Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Released Status in apt source package in Focal: Fix Released Bug description: [Impact] APT 1.6-2.0 deny third-party repositories from changing their Suite value. This change was reverted in later apt releases, and will be reverted in 1.8 in Debian as well, so for consistency, we want to push that change to stable [Test plan] We added test cases to our extensive integration test suite run by autopkgtest. [Where problems could occur] It's hard to imagine anything here, we simply turn the flag for allowed from false to true. We even add tests for Suite changes :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918907/+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 1918920] Re: Harden test for no new acquires after transaction abort
This bug was fixed in the package apt - 2.0.5
---
apt (2.0.5) focal; urgency=medium
[ Julian Andres Klode ]
* private-search: Only use V.TranslatedDescription() if good (LP: #1877987)
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all translations when building the cache (LP: #1907850)
* Add basic support for the Protected field, and do not require
force-loopbreak
on Protected/Important packages (Closes: #983014) (LP: #1916725)
* Protect currently running kernel at run-time (LP: #1615381)
* Make ADDARG{,C}() macros expand to single statements
* Default Acquire::AllowReleaseInfoChange::Suite to "true" (Closes: #931566)
(LP: #1918907)
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
-- Julian Andres Klode Fri, 12 Mar 2021 12:47:30
+0100
--
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/1918920
Title:
Harden test for no new acquires after transaction abort
Status in apt package in Ubuntu:
Fix Committed
Status in apt source package in Bionic:
Fix Released
Status in apt source package in Focal:
Fix Released
Status in apt source package in Groovy:
Fix Released
Bug description:
[Impact]
test-pdiff-usage is somewhat flaky, especially on Debian, this makes it less
flaky. No end user impact as it's a test-only change.
[Test plan]
Running autopkgtest, which runs our extensive integration test suite which
includes the changed test.
[Where problems could occur]
No end user regression potential on its own, but might slightly change
regression potential for future pdiff changes:
Test approach is slightly different now. It still catches that updates
fail correctly, but tests more concretely that a transaction was
aborted rather than that no worker received work (which was not
guaranteed, the work could be scheduled before it was aborted).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918920/+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 1918920] Re: Harden test for no new acquires after transaction abort
This bug was fixed in the package apt - 1.6.13
---
apt (1.6.13) bionic; urgency=medium
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
[ Julian Andres Klode ]
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all translations when building the cache (LP: #1907850)
* Add basic support for the Protected field
* Do not require force-loopbreak on Important packages
(Closes: #983014) (LP: #1916725)
* Protect currently running kernel at run-time (LP: #1615381)
* Make ADDARG{,C}() macros expand to single statements
* Improve immediate configuration handling (LP: #1871268)
- Do not immediately configure m-a: same packages in lockstep
- Ignore failures from immediate configuration. This does not change the
actual installation ordering - we never passed the return code to the
caller and installation went underway anyway if it could be ordered at a
later stage, this just removes spurious after-the-fact errors.
(Closes: #973305, #188161, #211075, #649588)
* Default Acquire::AllowReleaseInfoChange::Suite to "true" (Closes: #931566)
(LP: #1918907)
[ Balint Reczey ]
* Set LC_ALL=C.UTF-8 for unattended-upgrades environment when parsing its
--help
(LP: #1806076)
-- Julian Andres Klode Fri, 12 Mar 2021 14:09:15
+0100
** Changed in: apt (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: apt (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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1918920
Title:
Harden test for no new acquires after transaction abort
Status in apt package in Ubuntu:
Fix Committed
Status in apt source package in Bionic:
Fix Released
Status in apt source package in Focal:
Fix Released
Status in apt source package in Groovy:
Fix Released
Bug description:
[Impact]
test-pdiff-usage is somewhat flaky, especially on Debian, this makes it less
flaky. No end user impact as it's a test-only change.
[Test plan]
Running autopkgtest, which runs our extensive integration test suite which
includes the changed test.
[Where problems could occur]
No end user regression potential on its own, but might slightly change
regression potential for future pdiff changes:
Test approach is slightly different now. It still catches that updates
fail correctly, but tests more concretely that a transaction was
aborted rather than that no worker received work (which was not
guaranteed, the work could be scheduled before it was aborted).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918920/+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 1922823] [NEW] Please remove poppler-qml-plugin from Ubuntu
Public bug reported: Unmaintained Ubuntu-only package that is part of the obsolete Ubuntu Touch stack. FTBFS on rebuild and has no rdeps. ** Affects: poppler-qml-plugin (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler-qml-plugin in Ubuntu. https://bugs.launchpad.net/bugs/1922823 Title: Please remove poppler-qml-plugin from Ubuntu Status in poppler-qml-plugin package in Ubuntu: New Bug description: Unmaintained Ubuntu-only package that is part of the obsolete Ubuntu Touch stack. FTBFS on rebuild and has no rdeps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler-qml-plugin/+bug/1922823/+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 1922822] [NEW] Please remove qtpowerd from Ubuntu
Public bug reported: Unmaintained Ubuntu-only package that is part of the obsolete Ubuntu Touch stack. FTBFS on rebuild and has no rdeps. ** Affects: qtpowerd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtpowerd in Ubuntu. https://bugs.launchpad.net/bugs/1922822 Title: Please remove qtpowerd from Ubuntu Status in qtpowerd package in Ubuntu: New Bug description: Unmaintained Ubuntu-only package that is part of the obsolete Ubuntu Touch stack. FTBFS on rebuild and has no rdeps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtpowerd/+bug/1922822/+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 1877987] Re: apt search coredumping
apt 2.0.5 hasn't appeared in the errors.ubuntu.com crash bin, so that seems a reasonable assertion. -- 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/1877987 Title: apt search coredumping Status in apt package in Ubuntu: Fix Released Status in apt source package in Focal: Fix Committed Bug description: [Impact] Search sometimes crashes if no translated description is available, as the translated description object was used without a check as to whether it exists. [Test case] No reproducer available at the moment. [Where problems could occur] In search command only, and only when looking at descriptions [Original bug report] root@citoyx:/var/crash# apt search jdk Sorting... Done Segmentation fault (core dumped) May 11 12:34:25 citoyx kernel: [ 1354.337907] apt[10418]: segfault at 7f67292dcfc0 ip 7f6309ce4997 sp 7ffdab880930 error 4 in libapt-pkg.so.6.0.0[7f6309bb5000+147000] May 11 12:34:25 citoyx kernel: [ 1354.337916] Code: 48 8b 45 18 48 8b 04 d0 48 83 c4 08 5b 5d c3 0f 1f 40 00 f3 0f 1e fa 55 48 89 fd 53 48 89 f3 48 83 ec 08 48 8b 06 48 8b 4e 08 <8b> 10 48 8d 04 d5 00 00 00 00 48 29 d0 48 8b 51 60 48 8d 04 c2 0f root@citoyx:/var/crash# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" apt search is coredumping While apt install/upgrade/update is running fine crash file in attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1877987/+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] Re: systemd-repart not packaged
** Changed in: systemd (Debian) Status: Unknown => 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/1897932 Title: systemd-repart not packaged Status in systemd package in Ubuntu: Confirmed Status in systemd package in Debian: New Bug description: systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? I'd like to use it in our new raspberry pi images where we don't have cloud-init installed. We're already using systemd-growfs, but we are missing the nice partition resizing part (so are using cloud- initramfs-growroot). Could you please consider enabling it? In another binary package - so it can have extra deps - would be just fine by me. 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 1472288] Re: missing attributes in /etc/os-release
The attachment "2-11ubuntu19.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1472288 Title: missing attributes in /etc/os-release Status in base-files package in Ubuntu: Confirmed Bug description: Please add 'CPE_NAME' and 'BUILD_ID' to /etc/os-release. More at http://www.freedesktop.org/software/systemd/man/os- release.html. I'm not sure BUILD_ID should be something like 'vivid' etc, but it would be a nice use. Or introduce a new attribute/value pair like NICKNAME_ID="vivid" No rush. Thanks for adopting this convention so quickly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: base-files 7.2ubuntu9 Uname: Linux 4.1.0-rc5carif-7-ga8b253b x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 7 10:26:02 2015 Dependencies: InstallationDate: Installed on 2014-11-04 (245 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: base-files UpgradeStatus: Upgraded to vivid on 2015-04-25 (73 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1472288/+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] Re: systemd-repart not packaged
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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: Confirmed Status in systemd package in Debian: Unknown Bug description: systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? I'd like to use it in our new raspberry pi images where we don't have cloud-init installed. We're already using systemd-growfs, but we are missing the nice partition resizing part (so are using cloud- initramfs-growroot). Could you please consider enabling it? In another binary package - so it can have extra deps - would be just fine by me. 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 1897932] Re: systemd-repart not packaged
** Bug watch added: Debian Bug tracker #976959 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976959 ** Also affects: systemd (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976959 Importance: Unknown Status: Unknown -- 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: Confirmed Status in systemd package in Debian: Unknown Bug description: systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? I'd like to use it in our new raspberry pi images where we don't have cloud-init installed. We're already using systemd-growfs, but we are missing the nice partition resizing part (so are using cloud- initramfs-growroot). Could you please consider enabling it? In another binary package - so it can have extra deps - would be just fine by me. 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
Re: [Touch-packages] [Bug 1472288] Re: missing attributes in /etc/os-release
On 4/6/21 5:33 PM, Alexander Scheel wrote: > This is a debdiff for Hirsute, applicable against 11ubuntu18 to add > CPE_NAME. I ended up quoting it to follow what Fedora does but from what > I (and ShellCheck) can tell from testing the resulting .deb with bash > and sh, it doesn't strictly need to be quoted. > > Per discussion with Steve Beattie (~sbeattie), we'd be interested in > pursuing a Feature Exception request for this prior to doing backports > for older releases. Does that sound OK? > > ** Patch added: "2-11ubuntu19.debdiff" > > https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1472288/+attachment/5484958/+files/2-11ubuntu19.debdiff > Not sure what a "feature exception" is. But whatever you deem best (since you did the work). Ty. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1472288 Title: missing attributes in /etc/os-release Status in base-files package in Ubuntu: Confirmed Bug description: Please add 'CPE_NAME' and 'BUILD_ID' to /etc/os-release. More at http://www.freedesktop.org/software/systemd/man/os- release.html. I'm not sure BUILD_ID should be something like 'vivid' etc, but it would be a nice use. Or introduce a new attribute/value pair like NICKNAME_ID="vivid" No rush. Thanks for adopting this convention so quickly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: base-files 7.2ubuntu9 Uname: Linux 4.1.0-rc5carif-7-ga8b253b x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 7 10:26:02 2015 Dependencies: InstallationDate: Installed on 2014-11-04 (245 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: base-files UpgradeStatus: Upgraded to vivid on 2015-04-25 (73 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1472288/+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 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
Having installed Ubuntu Hippo Beta [or a recent daily build version] successfully as in post #32 it is possible to install the Kubuntu desktop over it resulting in a working version of Kubuntu Hippo. I suppose this could be seen as a workaround to install a working Kubuntu 2104. -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Incomplete Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1472288] Re: missing attributes in /etc/os-release
This is a debdiff for Hirsute, applicable against 11ubuntu18 to add CPE_NAME. I ended up quoting it to follow what Fedora does but from what I (and ShellCheck) can tell from testing the resulting .deb with bash and sh, it doesn't strictly need to be quoted. Per discussion with Steve Beattie (~sbeattie), we'd be interested in pursuing a Feature Exception request for this prior to doing backports for older releases. Does that sound OK? ** Patch added: "2-11ubuntu19.debdiff" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1472288/+attachment/5484958/+files/2-11ubuntu19.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1472288 Title: missing attributes in /etc/os-release Status in base-files package in Ubuntu: Confirmed Bug description: Please add 'CPE_NAME' and 'BUILD_ID' to /etc/os-release. More at http://www.freedesktop.org/software/systemd/man/os- release.html. I'm not sure BUILD_ID should be something like 'vivid' etc, but it would be a nice use. Or introduce a new attribute/value pair like NICKNAME_ID="vivid" No rush. Thanks for adopting this convention so quickly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: base-files 7.2ubuntu9 Uname: Linux 4.1.0-rc5carif-7-ga8b253b x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 7 10:26:02 2015 Dependencies: InstallationDate: Installed on 2014-11-04 (245 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: base-files UpgradeStatus: Upgraded to vivid on 2015-04-25 (73 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1472288/+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 1472288] Re: missing attributes in /etc/os-release
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: base-files (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1472288 Title: missing attributes in /etc/os-release Status in base-files package in Ubuntu: Confirmed Bug description: Please add 'CPE_NAME' and 'BUILD_ID' to /etc/os-release. More at http://www.freedesktop.org/software/systemd/man/os- release.html. I'm not sure BUILD_ID should be something like 'vivid' etc, but it would be a nice use. Or introduce a new attribute/value pair like NICKNAME_ID="vivid" No rush. Thanks for adopting this convention so quickly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: base-files 7.2ubuntu9 Uname: Linux 4.1.0-rc5carif-7-ga8b253b x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 7 10:26:02 2015 Dependencies: InstallationDate: Installed on 2014-11-04 (245 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: base-files UpgradeStatus: Upgraded to vivid on 2015-04-25 (73 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1472288/+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 50093] Re: Some sysctls are ignored on boot
As procps has been replaced by systemd in recent releases (at least the sysctl service part), I'm switching the target package to systemd. Also, I'm changing this to wishlist as this isn't actually a bug; from the sysctl.d manpage: "Many sysctl parameters only become available when certain kernel modules are loaded. Modules are usually loaded on demand, e.g. when certain hardware is plugged in or network brought up. This means that systemd-sysctl.service(8) which runs during early boot will not configure such parameters if they become available after it has run. To set such parameters, it is recommended to add an udev(7) rule to set those parameters when they become available. Alternatively, a slightly simpler and less efficient option is to add the module to modules-load.d(5), causing it to be loaded statically before sysctl settings are applied (see example below)." ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Importance: Undecided => Wishlist ** Changed in: procps (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctls are ignored on boot Status in procps package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: New Bug description: Binary package hint: procps /etc/init.d/procps.sh comes too early in the boot process to apply a lot of sysctl's. As it runs before networking modules are loaded and filesystems are mounted, there are quite a lot of commonly-used sysctl's which are simply ignored on boot and produce errors to the console. Simply renaming the symlink from S17 to > S40 probably isn't a great solution, as there are probably folk who want and expect some sysctl's to be applied before filesystems are mounted and so on. However, simply ugnoring something as important as sysctl settings isn't really on. Administrators expect the settings in /etc/sysctl.conf to take effect. One sto-gap solution would be to run sysctl -p twice; once at S17 and once at S41. There may still be some warnings and errors, but everything would be applied. A different, more complex approach might be to re-architect the sysctl configuration into something like; /etc/sysctl.d/$modulename and have the userland module-loading binaries take care of applying them after modules are loaded. Though this may take care of explicitly loaded modules only, I'm not sure. Incidentally, /etc/sysctl.conf still refers to /etc/networking/options, but hasn't that been deprecated? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+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 50093] Re: Some sysctls are ignored on boot
Just to reiterate, I'm only marking procps as 'wontfix' because the sysctl service used in all current releases comes from systemd, *not* the procps package, so there is nothing to 'fix' in the procps package. Also, before people get upset, I've only marked this as Wishlist because the sysctl.d docs clearly explain this is a known issue with clearly documented ways to work around it. That doesn't mean i don't think this should be fixed; I absolutely do agree it should be fixed to properly apply all sysctl settings at boot, including for loadable modules loaded after boot. That will require upstream systemd work to implement, however, before backporting into Ubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctls are ignored on boot Status in procps package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: New Bug description: Binary package hint: procps /etc/init.d/procps.sh comes too early in the boot process to apply a lot of sysctl's. As it runs before networking modules are loaded and filesystems are mounted, there are quite a lot of commonly-used sysctl's which are simply ignored on boot and produce errors to the console. Simply renaming the symlink from S17 to > S40 probably isn't a great solution, as there are probably folk who want and expect some sysctl's to be applied before filesystems are mounted and so on. However, simply ugnoring something as important as sysctl settings isn't really on. Administrators expect the settings in /etc/sysctl.conf to take effect. One sto-gap solution would be to run sysctl -p twice; once at S17 and once at S41. There may still be some warnings and errors, but everything would be applied. A different, more complex approach might be to re-architect the sysctl configuration into something like; /etc/sysctl.d/$modulename and have the userland module-loading binaries take care of applying them after modules are loaded. Though this may take care of explicitly loaded modules only, I'm not sure. Incidentally, /etc/sysctl.conf still refers to /etc/networking/options, but hasn't that been deprecated? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+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 50093] Re: Some sysctls are ignored on boot
Still seeing this in bionic 18.04.3 with the following kernel and procps package. ii procps 2:3.3.12-3ubuntu1.2 amd64/proc file system utilities kernel 5.4.0-62-generic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctls are ignored on boot Status in procps package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: New Bug description: Binary package hint: procps /etc/init.d/procps.sh comes too early in the boot process to apply a lot of sysctl's. As it runs before networking modules are loaded and filesystems are mounted, there are quite a lot of commonly-used sysctl's which are simply ignored on boot and produce errors to the console. Simply renaming the symlink from S17 to > S40 probably isn't a great solution, as there are probably folk who want and expect some sysctl's to be applied before filesystems are mounted and so on. However, simply ugnoring something as important as sysctl settings isn't really on. Administrators expect the settings in /etc/sysctl.conf to take effect. One sto-gap solution would be to run sysctl -p twice; once at S17 and once at S41. There may still be some warnings and errors, but everything would be applied. A different, more complex approach might be to re-architect the sysctl configuration into something like; /etc/sysctl.d/$modulename and have the userland module-loading binaries take care of applying them after modules are loaded. Though this may take care of explicitly loaded modules only, I'm not sure. Incidentally, /etc/sysctl.conf still refers to /etc/networking/options, but hasn't that been deprecated? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+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 1615381] Update Released
The verification of the Stable Release Update for apt 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 unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1615381 Title: apt-get autoremove may remove current kernel Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Won't Fix Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Artful: Won't Fix Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Released Status in apt source package in Hirsute: Fix Released Bug description: [Impact] APT will try and fail to remove the currently running kernel, when booted into an older kernel that is not protected. May wreak some havoc if mixed with other operations to the point that apt goes weird and needs manual fixing up. [Test case] For the SRUs we have included an automated test case that starts with an empty autoremove config file, and then checks that the running kernel is protected at runtime. You can also test manually, but it's not necessary: - Install new kernel - Reboot into kernel not listed as protected in 01autoremove-kernels - Run autoremove [Where problems could occur] We may more easily run out of space in /boot. hirsute has new autoremoval code that runs completely at runtime; but that seems a bit large to SRU after only a few weeks in hirsute. Hence, we should protect the current kernel _in addition_ to the other kernels, just like unattended-upgrades and update-manager do. This increases the risk of filling up /boot compared to older apt versions, but is at the same level as unattended-upgrades and update-manager. [Original bug report] This may happen, if you boot one of the older kernels, that is not protected by /etc/apt/apt.conf.d/01autoremove-kernels Workaround: run /etc/kernel/postinst.d/apt-auto-removal during each boot (e.g. by using cron). Note: The workaround breaks autoremoving feature of new unneeded kernels in unattended-upgrades i.e. the setting 'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set in '/etc/apt/apt.conf.d/50unattended-upgrades'. In shell: $ uname -r 4.4.0-22-generic $ apt-get -s autoremove NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22 linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic 0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.12~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Aug 21 16:11:27 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (114 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified] mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 2016-07-30T12:15:32.706300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615381/+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 1615381] Re: apt-get autoremove may remove current kernel
This bug was fixed in the package apt - 2.1.10ubuntu0.3
---
apt (2.1.10ubuntu0.3) groovy; urgency=medium
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
[ Julian Andres Klode ]
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all translations when building the cache (LP: #1907850)
* Do not require force-loopbreak on Protected packages (Closes: #983014)
(LP: #1916725)
* RunScripts: Do not reset SIGQUIT and SIGINT to SIG_DFL (LP: #1898026)
* Protect currently running kernel at run-time (LP: #1615381)
* Make ADDARG{,C}() macros expand to single statements
-- Julian Andres Klode Fri, 12 Mar 2021 09:22:11
+0100
** Changed in: apt (Ubuntu Groovy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1615381
Title:
apt-get autoremove may remove current kernel
Status in apt package in Ubuntu:
Fix Released
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Trusty:
Won't Fix
Status in unattended-upgrades source package in Xenial:
Fix Released
Status in unattended-upgrades source package in Artful:
Won't Fix
Status in apt source package in Bionic:
Fix Committed
Status in apt source package in Focal:
Fix Committed
Status in apt source package in Groovy:
Fix Released
Status in apt source package in Hirsute:
Fix Released
Bug description:
[Impact]
APT will try and fail to remove the currently running kernel, when booted
into an older kernel that is not protected. May wreak some havoc if mixed with
other operations to the point that apt goes weird and needs manual fixing up.
[Test case]
For the SRUs we have included an automated test case that starts with an
empty autoremove config file, and then checks that the running kernel is
protected at runtime.
You can also test manually, but it's not necessary:
- Install new kernel
- Reboot into kernel not listed as protected in 01autoremove-kernels
- Run autoremove
[Where problems could occur]
We may more easily run out of space in /boot. hirsute has new autoremoval
code that runs completely at runtime; but that seems a bit large to SRU after
only a few weeks in hirsute. Hence, we should protect the current kernel _in
addition_ to the other kernels, just like unattended-upgrades and
update-manager do. This increases the risk of filling up /boot compared to
older apt versions, but is at the same level as unattended-upgrades and
update-manager.
[Original bug report]
This may happen, if you boot one of the older kernels, that is not
protected by /etc/apt/apt.conf.d/01autoremove-kernels
Workaround: run
/etc/kernel/postinst.d/apt-auto-removal
during each boot (e.g. by using cron).
Note: The workaround breaks autoremoving feature of new unneeded kernels in
unattended-upgrades i.e. the setting
'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default
in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set
in '/etc/apt/apt.conf.d/50unattended-upgrades'.
In shell:
$ uname -r
4.4.0-22-generic
$ apt-get -s autoremove
NOTE: This is only a simulation!
apt-get needs root privileges for real execution.
Keep also in mind that locking is deactivated,
so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22
linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic
linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic
linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic
linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic
0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apt 1.2.12~ubuntu16.04.1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Aug 21 16:11:27 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-04-28 (114 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified]
mtime.conffile..etc.kernel.postinst.d.apt-auto-removal:
2016-07-30T12:15:32.706300
To manage notifications about this bug go to:
[Touch-packages] [Bug 1821415] Re: pkexec fails in a non-graphical environment
(but I asked for some input there from an apport maintainer, it could be better than I did it) -- 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/1821415 Title: pkexec fails in a non-graphical environment Status in PolicyKit: New Status in apport package in Ubuntu: Triaged Status in policykit-1 package in Ubuntu: Won't Fix Bug description: The plymouth apport source package hooks wants to gather log files as the root user and apport provides a policy kit policy for collecting that information. This works fine in a graphical environment but not in a non-graphical one. N.B. you first need to create a /var/log/plymouth-debug.log file for the plymouth apport package hook to actually trigger this. ubuntu@disco:~$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. Subsequently, bug reports from servers will contain less information. To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1821415/+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 1887744] 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/1887744 Title: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798 Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: Invalid Status in systemd source package in Focal: Fix Released Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Released Bug description: [impact] if a non-template service file is created as a symlink to a template service file outside the normal unit file paths, systemd will fail assertion and crash [test case] su - cat < /crashsystemd@.service [Unit] Description=Template for instance %i [Service] ExecStart=/bin/true EOF cd /etc/systemd/system ln -s /crashsystemd@.service crashsystemd.service systemctl daemon-reload systemctl start crashsystemd [regression potential] any regression would likely cause a failed assertion and crash, or failure to properly parse and/or load a service file that is a symlink [scope] this is needed in f/g/h this is fixed upstream by commit 3aa57658434e7a95c6000bebb166c31f1c6d051b which is included in v248-rc1, so this is not fixed in any release yet this was introduced by the changes in commit e8630e69523 which was first included in v243, so this bug doesn't exist in b or earlier [original description] On an Ubuntu 20.04 server, when I started a newly installed systemd service 'systemctl start testemail2jira.service', systemd trips on an assertion (from journalctl): Jul 16 13:49:12 pangolin-jiraconf systemd[1]: Assertion 'u->instance' failed at src/core/load-fragment.c:4798, function unit_load_fragment(). Aborting. Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Caught , dumped core as pid 2906637. Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Freezing execution. apport generates a core dump which I trust is attached. The server still works, but my terminal keeps showing: Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) and pauses for 25s after each command. In case it's relevant, the i was trying to start had just been symlinked into /etc/systemd/system/: root@pangolin-jiraconf # ls -la /etc/systemd/system/testemail2jira.service lrwxrwxrwx 1 root root 82 Jul 16 13:48 /etc/systemd/system/testemail2jira.service -> /opt/atlassian/jira/current/emailprocessing/testemail2jira/testemail2jira@.service File contents: [Unit] Description=Check that email to %i JIRA works [Service] #Type=oneshot # Note: I keep the config file, testemail2jira.json5 and rsa.* files in emailprocessing/, one directory below testemail2jira/, so that they can be version-controlled independently. # If you want testemail2jira.json5 and rsa.* within testemail2jira/, then add testemail2jira/ to WorkingDirectory and remove it from the ExecStart command WorkingDirectory=/opt/atlassian/%i/current/emailprocessing ExecStart=/opt/atlassian/%i/current/emailprocessing/testemail2jira/venv/bin/python testemail2jira/testemail2jira.py User=root [Install] WantedBy=multi-user.target Perhaps the problem is that my service file is a template (testemail2jira@.service), but I symlinked it as a regular 'testemail2jira.service'. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jul 16 14:13:06 2020 InstallationDate: Installed on 2020-05-27 (49 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=/dev/sda ro console=ttyS0,19200n8 net.ifnames=0 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full',
[Touch-packages] [Bug 1891810] Re: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers
This bug was fixed in the package libseccomp - 2.5.1-1ubuntu1~20.10.1 --- libseccomp (2.5.1-1ubuntu1~20.10.1) groovy; urgency=medium * Updated to new upstream 2.5.1 version for updated syscalls support (LP: #1891810) - Removed the following patches that are now included in the new version: + d/p/cython3.patch + d/p/riscv64_support.patch + d/p/fix-aarch64-syscalls.patch + d/p/db-consolidate-some-of-the-code-which-adds-rules.patch + d/p/db-add-shadow-transactions.patch - Deleted the patch to add a local copy of architecture specific header files from linux-libc-dev/focal as this is not needed anymore + d/p/add-5.4-local-syscall-headers.patch - debian/control: Added gperf to Build-Depends as this is now required by upstream - debian/libseccomp2.symbols: Added new symbols * Add system call headers for powerpc required for backport to xenial - d/p/add-5.8-powerpc-syscall-headers.patch -- Alex Murray Mon, 01 Mar 2021 13:50:23 +1030 ** Changed in: libseccomp (Ubuntu Groovy) 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/1891810 Title: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers Status in libseccomp package in Ubuntu: Fix Released Status in systemd package in Ubuntu: New Status in libseccomp source package in Xenial: Fix Committed Status in systemd source package in Xenial: New Status in libseccomp source package in Bionic: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in libseccomp source package in Focal: Fix Committed Status in systemd source package in Focal: Fix Released Status in libseccomp source package in Groovy: Fix Released Status in systemd source package in Groovy: New Status in libseccomp source package in Hirsute: Fix Released Status in systemd source package in Hirsute: New Bug description: [Impact] The version of libseccomp2 in X/B/F/G does not know about the openat2 syscall. As such applications that use libseccomp cannot specify a system-call filter against this system-call and so it cannot be mediated. [Test Plan] This can be tested by simply running scmp_sys_resolver from the seccomp binary package and specifying this system-call: Existing behaviour: $ scmp_sys_resolver openat2 -1 Expected behaviour: $ scmp_sys_resolver openat2 437 (Note this value will be different on other architectures) [Where problems could occur] In version 2.5.1 of libseccomp which adds this new system-call, changes were also made in the way the socket system-call is handled by libseccomp on PPC platforms - this resulted in a change in the expected behaviour and so this has already been noticed and a fix is required for the systemd unit tests as a result https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696 There was also a similar change for s390x but so far no regressions have been observed as a result as systemd already expected that behaviour from libseccomp, it was only PPC that was missing. In the event that a regression is observed however, we can easily either patch the affected package to cope with the new behaviour of this updated libseccomp since in each case the change in behaviour only affects a few system calls on particular architectures, or we can revert this update. [Other Info] * As usual thorough testing of this update has been performed both manually via the QA Regression Testing scripts, and via the autopkgtest infrastructure against packages in the Ubuntu Security Proposed PPA https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa/ with results seen https://people.canonical.com/~platform/security-britney/current/ I have attached debdiffs of the prepared updates which are also sitting in the Ubuntu Security Proposed PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1891810/+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 1891810] Re: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers
This bug was fixed in the package systemd - 245.4-4ubuntu3.6 --- systemd (245.4-4ubuntu3.6) focal; urgency=medium * debian/patches/lp1916485-Newer-Glibc-use-faccessat2-to-implement-faccessat.patch: Add support for faccessat2 (LP: #1916485) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=affb2c6507dccfeed02820a2267639648e2a2260 * d/p/lp1918696-shared-seccomp-util-address-family-filtering-is-brok.patch: Stop attempting to restrict address families on ppc archs (LP: #1918696) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=daff4b6604362fcb5d305682216d5ca15a4c5738 * d/p/lp1891810-seccomp-util-add-new-syscalls-from-kernel-5.6-to-sys.patch: Add openat2() syscall to seccomp filter list (LP: #1891810) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=69c8a684e2513b2f6530e5a5cf15c83abfb7bc74 * d/p/lp1915887-Downgrade-a-couple-of-warnings-to-debug.patch: Downgrade some log messages so they stop spamming logs (LP: #1915887) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3c2c4731b90ed430ca1790270e69cd125643b94b * d/p/lp1887744-basic-unit-file-when-loading-linked-unit-files-use-l.patch: Use src name, not dst name, of symlinked unit files (LP: #1887744) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=03770601097cfdc09adeadf5593083da69345409 -- Dan Streetman Wed, 17 Mar 2021 17:36:08 -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/1891810 Title: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers Status in libseccomp package in Ubuntu: Fix Released Status in systemd package in Ubuntu: New Status in libseccomp source package in Xenial: Fix Committed Status in systemd source package in Xenial: New Status in libseccomp source package in Bionic: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in libseccomp source package in Focal: Fix Committed Status in systemd source package in Focal: Fix Released Status in libseccomp source package in Groovy: Fix Released Status in systemd source package in Groovy: New Status in libseccomp source package in Hirsute: Fix Released Status in systemd source package in Hirsute: New Bug description: [Impact] The version of libseccomp2 in X/B/F/G does not know about the openat2 syscall. As such applications that use libseccomp cannot specify a system-call filter against this system-call and so it cannot be mediated. [Test Plan] This can be tested by simply running scmp_sys_resolver from the seccomp binary package and specifying this system-call: Existing behaviour: $ scmp_sys_resolver openat2 -1 Expected behaviour: $ scmp_sys_resolver openat2 437 (Note this value will be different on other architectures) [Where problems could occur] In version 2.5.1 of libseccomp which adds this new system-call, changes were also made in the way the socket system-call is handled by libseccomp on PPC platforms - this resulted in a change in the expected behaviour and so this has already been noticed and a fix is required for the systemd unit tests as a result https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696 There was also a similar change for s390x but so far no regressions have been observed as a result as systemd already expected that behaviour from libseccomp, it was only PPC that was missing. In the event that a regression is observed however, we can easily either patch the affected package to cope with the new behaviour of this updated libseccomp since in each case the change in behaviour only affects a few system calls on particular architectures, or we can revert this update. [Other Info] * As usual thorough testing of this update has been performed both manually via the QA Regression Testing scripts, and via the autopkgtest infrastructure against packages in the Ubuntu Security Proposed PPA https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa/ with results seen https://people.canonical.com/~platform/security-britney/current/ I have attached debdiffs of the prepared updates which are also sitting in the Ubuntu Security Proposed PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1891810/+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 1898026] Update Released
The verification of the Stable Release Update for apt 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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1898026
Title:
interruption of dist-upgrade can leave you next release in
sources.list
Status in apt package in Ubuntu:
Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
Fix Released
Status in apt source package in Bionic:
New
Status in ubuntu-release-upgrader source package in Bionic:
New
Status in apt source package in Focal:
New
Status in ubuntu-release-upgrader source package in Focal:
New
Status in apt source package in Groovy:
Fix Released
Status in ubuntu-release-upgrader source package in Groovy:
New
Status in apt source package in Hirsute:
Fix Released
Status in ubuntu-release-upgrader source package in Hirsute:
Fix Released
Bug description:
[Impact]
Calling update() or installing packages from apt clients resets their SIGINT
and SIGQUIT handlers to SIG_DFL, overriding any signal handlers they might have
set for them.
In case of ubuntu-release-upgrader, this results in the release
upgrader being unable to handle interrupts after it did the initial
update - the default libc handler will run and the program exits.
[Test plan]
[[apt]]
As a standalone test for apt, we can test the following script:
import apt
import time
apt.Cache().update()
print("WAITING")
try:
time.sleep(1)
except BaseException as e:
print("Seen", repr(e))
print("END")
Pressing Ctrl+C while WAITING is printed should print Seen
KeyboardInterrupt, and importantly, also the END line.
[Where problems could occur]
apt: This specific change removes the two lines that SIG_DFL the signal
handlers after running scripts. AFAWCT those lines are unnecessary - the code
that calls it temporarily sets the handlers to SIG_IGN but restores previous
handlers at the end; it was wrongly refactored decades ago. A regression could
occur in that those signals will now continue to be ignored if we missed a spot.
[Original bug report]
As a long-time-user of ?ubuntu, with apt-get as tool of choice for
updates/upgrades I wrote a daily script for updates, with 'dist-upgrade'.
In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu
version; just all packages including new ones. Version updates had to be
initiated manually, and I was always asked if I really wanted the new ?ubuntu
version. Sounds appropriate.
Last night when it (dist-upgrade), it just gave me 20.04. No questions asked.
I for one consider this kind of intrusive, though.
It *might* have to make with me trying 'sudo do-release-upgrade -m desktop' a
number of times earlier; just to *check* if the upgrade was on offer; but this
is only a guess.
In *any* case, a pop-up asking "Are you sure? Are you connected
through an adequate pipe? Are you sitting with full batteries; better
a power supply?" would be convenient; since I am using my PC for
urgent duties, and didn't want to fiddle with unexpected upgrade bugs.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.25
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Thu Oct 1 11:48:39 2020
InstallationDate: Installed on 2019-03-14 (566 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to focal on 2020-09-29 (1 days ago)
VarLogDistupgradeAptlog:
Log time: 2020-09-29 19:44:28.696289
Log time: 2020-09-29 19:44:33.573481
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1898026/+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 1891810] Update Released
The verification of the Stable Release Update for libseccomp 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/1891810 Title: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers Status in libseccomp package in Ubuntu: Fix Released Status in systemd package in Ubuntu: New Status in libseccomp source package in Xenial: Fix Committed Status in systemd source package in Xenial: New Status in libseccomp source package in Bionic: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in libseccomp source package in Focal: Fix Committed Status in systemd source package in Focal: Fix Released Status in libseccomp source package in Groovy: Fix Released Status in systemd source package in Groovy: New Status in libseccomp source package in Hirsute: Fix Released Status in systemd source package in Hirsute: New Bug description: [Impact] The version of libseccomp2 in X/B/F/G does not know about the openat2 syscall. As such applications that use libseccomp cannot specify a system-call filter against this system-call and so it cannot be mediated. [Test Plan] This can be tested by simply running scmp_sys_resolver from the seccomp binary package and specifying this system-call: Existing behaviour: $ scmp_sys_resolver openat2 -1 Expected behaviour: $ scmp_sys_resolver openat2 437 (Note this value will be different on other architectures) [Where problems could occur] In version 2.5.1 of libseccomp which adds this new system-call, changes were also made in the way the socket system-call is handled by libseccomp on PPC platforms - this resulted in a change in the expected behaviour and so this has already been noticed and a fix is required for the systemd unit tests as a result https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696 There was also a similar change for s390x but so far no regressions have been observed as a result as systemd already expected that behaviour from libseccomp, it was only PPC that was missing. In the event that a regression is observed however, we can easily either patch the affected package to cope with the new behaviour of this updated libseccomp since in each case the change in behaviour only affects a few system calls on particular architectures, or we can revert this update. [Other Info] * As usual thorough testing of this update has been performed both manually via the QA Regression Testing scripts, and via the autopkgtest infrastructure against packages in the Ubuntu Security Proposed PPA https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa/ with results seen https://people.canonical.com/~platform/security-britney/current/ I have attached debdiffs of the prepared updates which are also sitting in the Ubuntu Security Proposed PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1891810/+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 1693900] Re: apt-get update should return exit code != 0 on error
This bug was fixed in the package apt - 2.1.10ubuntu0.3
---
apt (2.1.10ubuntu0.3) groovy; urgency=medium
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
[ Julian Andres Klode ]
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all translations when building the cache (LP: #1907850)
* Do not require force-loopbreak on Protected packages (Closes: #983014)
(LP: #1916725)
* RunScripts: Do not reset SIGQUIT and SIGINT to SIG_DFL (LP: #1898026)
* Protect currently running kernel at run-time (LP: #1615381)
* Make ADDARG{,C}() macros expand to single statements
-- Julian Andres Klode Fri, 12 Mar 2021 09:22:11
+0100
** Changed in: apt (Ubuntu Groovy)
Status: Fix Committed => 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/1693900
Title:
apt-get update should return exit code != 0 on error
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Confirmed
Status in apt source package in Bionic:
Fix Committed
Status in apt source package in Focal:
Fix Committed
Status in apt source package in Groovy:
Fix Released
Status in apt package in Debian:
Fix Released
Bug description:
[Impact]
There is no way for scripts to run apt update and be sure that it was
entirely successful.
We introduce a new flag, --error-on=any that makes apt update also
error out on transient errors.
[Test plan]
We have included a test in the test-suite in
test-apt-update-failure-propagation that ensures that warnings become errors.
[Where problems could occur]
If there's an issue some warnings for transient errors could become errors,
or worse I suppose it's possible but unlikely for errors to be reported as
warnings...
Since the new behavior is behind a flag, regression potential for
existing scripts is low if there is no bug.
[Original bug report]
When running 'apt-get update' (e.g. on a container install post-
install script), apt-get return with exit code 0, even so it wasn't
able to "update" properly. E.g.:
+ apt-get update
Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
Temporary failure resolving 'security.ubuntu.com'
Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
Reading package lists... Done
W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
W: Failed to fetch
http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary
failure resolving 'de.archive.ubuntu.com'
W: Failed to fetch
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary
failure resolving 'security.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old ones
used instead.
It should be corrected to return useful exit code, so that scripts can
take the appropriate actions ...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1693900/+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 1693900] Update Released
The verification of the Stable Release Update for apt 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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1693900 Title: apt-get update should return exit code != 0 on error Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Fix Released Bug description: [Impact] There is no way for scripts to run apt update and be sure that it was entirely successful. We introduce a new flag, --error-on=any that makes apt update also error out on transient errors. [Test plan] We have included a test in the test-suite in test-apt-update-failure-propagation that ensures that warnings become errors. [Where problems could occur] If there's an issue some warnings for transient errors could become errors, or worse I suppose it's possible but unlikely for errors to be reported as warnings... Since the new behavior is behind a flag, regression potential for existing scripts is low if there is no bug. [Original bug report] When running 'apt-get update' (e.g. on a container install post- install script), apt-get return with exit code 0, even so it wasn't able to "update" properly. E.g.: + apt-get update Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease Temporary failure resolving 'de.archive.ubuntu.com' Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease Temporary failure resolving 'de.archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. It should be corrected to return useful exit code, so that scripts can take the appropriate actions ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1693900/+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 1821415] Re: pkexec fails in a non-graphical environment
See the attached branch, it's a fix for this in apport. ** Branch linked: lp:~laney/apport/pkttyagent -- 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/1821415 Title: pkexec fails in a non-graphical environment Status in PolicyKit: New Status in apport package in Ubuntu: Triaged Status in policykit-1 package in Ubuntu: Won't Fix Bug description: The plymouth apport source package hooks wants to gather log files as the root user and apport provides a policy kit policy for collecting that information. This works fine in a graphical environment but not in a non-graphical one. N.B. you first need to create a /var/log/plymouth-debug.log file for the plymouth apport package hook to actually trigger this. ubuntu@disco:~$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. Subsequently, bug reports from servers will contain less information. To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1821415/+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 1887744] Re: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798
This bug was fixed in the package systemd - 245.4-4ubuntu3.6 --- systemd (245.4-4ubuntu3.6) focal; urgency=medium * debian/patches/lp1916485-Newer-Glibc-use-faccessat2-to-implement-faccessat.patch: Add support for faccessat2 (LP: #1916485) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=affb2c6507dccfeed02820a2267639648e2a2260 * d/p/lp1918696-shared-seccomp-util-address-family-filtering-is-brok.patch: Stop attempting to restrict address families on ppc archs (LP: #1918696) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=daff4b6604362fcb5d305682216d5ca15a4c5738 * d/p/lp1891810-seccomp-util-add-new-syscalls-from-kernel-5.6-to-sys.patch: Add openat2() syscall to seccomp filter list (LP: #1891810) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=69c8a684e2513b2f6530e5a5cf15c83abfb7bc74 * d/p/lp1915887-Downgrade-a-couple-of-warnings-to-debug.patch: Downgrade some log messages so they stop spamming logs (LP: #1915887) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3c2c4731b90ed430ca1790270e69cd125643b94b * d/p/lp1887744-basic-unit-file-when-loading-linked-unit-files-use-l.patch: Use src name, not dst name, of symlinked unit files (LP: #1887744) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=03770601097cfdc09adeadf5593083da69345409 -- Dan Streetman Wed, 17 Mar 2021 17:36:08 -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/1887744 Title: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798 Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: Invalid Status in systemd source package in Focal: Fix Released Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Released Bug description: [impact] if a non-template service file is created as a symlink to a template service file outside the normal unit file paths, systemd will fail assertion and crash [test case] su - cat < /crashsystemd@.service [Unit] Description=Template for instance %i [Service] ExecStart=/bin/true EOF cd /etc/systemd/system ln -s /crashsystemd@.service crashsystemd.service systemctl daemon-reload systemctl start crashsystemd [regression potential] any regression would likely cause a failed assertion and crash, or failure to properly parse and/or load a service file that is a symlink [scope] this is needed in f/g/h this is fixed upstream by commit 3aa57658434e7a95c6000bebb166c31f1c6d051b which is included in v248-rc1, so this is not fixed in any release yet this was introduced by the changes in commit e8630e69523 which was first included in v243, so this bug doesn't exist in b or earlier [original description] On an Ubuntu 20.04 server, when I started a newly installed systemd service 'systemctl start testemail2jira.service', systemd trips on an assertion (from journalctl): Jul 16 13:49:12 pangolin-jiraconf systemd[1]: Assertion 'u->instance' failed at src/core/load-fragment.c:4798, function unit_load_fragment(). Aborting. Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Caught , dumped core as pid 2906637. Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Freezing execution. apport generates a core dump which I trust is attached. The server still works, but my terminal keeps showing: Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) and pauses for 25s after each command. In case it's relevant, the i was trying to start had just been symlinked into /etc/systemd/system/: root@pangolin-jiraconf # ls -la /etc/systemd/system/testemail2jira.service lrwxrwxrwx 1 root root 82 Jul 16 13:48 /etc/systemd/system/testemail2jira.service -> /opt/atlassian/jira/current/emailprocessing/testemail2jira/testemail2jira@.service File contents: [Unit] Description=Check that email to %i JIRA works [Service] #Type=oneshot # Note: I keep the config file, testemail2jira.json5 and rsa.* files in emailprocessing/, one directory below testemail2jira/, so that they can be version-controlled independently. # If you want testemail2jira.json5 and rsa.* within testemail2jira/, then add testemail2jira/ to WorkingDirectory and remove it from the ExecStart command WorkingDirectory=/opt/atlassian/%i/current/emailprocessing ExecStart=/opt/atlassian/%i/current/emailprocessing/testemail2jira/venv/bin/python
[Touch-packages] [Bug 1887744] Re: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798
This bug was fixed in the package systemd - 246.6-1ubuntu1.3 --- systemd (246.6-1ubuntu1.3) groovy; urgency=medium * d/p/lp1918696-shared-seccomp-util-address-family-filtering-is-brok.patch: Stop attempting to restrict address families on ppc archs (LP: #1918696) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=34d1b2b4f4fdc349da37a07fe98418456167592a * d/p/lp1915887-Downgrade-a-couple-of-warnings-to-debug.patch: Downgrade some log messages so they stop spamming logs (LP: #1915887) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d092e70912009daf6f64182d86b3d92aed28722a * d/p/lp1887744-basic-unit-file-when-loading-linked-unit-files-use-l.patch: Use src name, not dst name, of symlinked unit files (LP: #1887744) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1e42633ccecc9c9157b19387c11ac1bf7ea7d161 -- Dan Streetman Wed, 10 Mar 2021 16:03:13 -0500 ** Changed in: systemd (Ubuntu Groovy) 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/1887744 Title: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798 Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: Invalid Status in systemd source package in Focal: Fix Released Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Released Bug description: [impact] if a non-template service file is created as a symlink to a template service file outside the normal unit file paths, systemd will fail assertion and crash [test case] su - cat < /crashsystemd@.service [Unit] Description=Template for instance %i [Service] ExecStart=/bin/true EOF cd /etc/systemd/system ln -s /crashsystemd@.service crashsystemd.service systemctl daemon-reload systemctl start crashsystemd [regression potential] any regression would likely cause a failed assertion and crash, or failure to properly parse and/or load a service file that is a symlink [scope] this is needed in f/g/h this is fixed upstream by commit 3aa57658434e7a95c6000bebb166c31f1c6d051b which is included in v248-rc1, so this is not fixed in any release yet this was introduced by the changes in commit e8630e69523 which was first included in v243, so this bug doesn't exist in b or earlier [original description] On an Ubuntu 20.04 server, when I started a newly installed systemd service 'systemctl start testemail2jira.service', systemd trips on an assertion (from journalctl): Jul 16 13:49:12 pangolin-jiraconf systemd[1]: Assertion 'u->instance' failed at src/core/load-fragment.c:4798, function unit_load_fragment(). Aborting. Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Caught , dumped core as pid 2906637. Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Freezing execution. apport generates a core dump which I trust is attached. The server still works, but my terminal keeps showing: Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) and pauses for 25s after each command. In case it's relevant, the i was trying to start had just been symlinked into /etc/systemd/system/: root@pangolin-jiraconf # ls -la /etc/systemd/system/testemail2jira.service lrwxrwxrwx 1 root root 82 Jul 16 13:48 /etc/systemd/system/testemail2jira.service -> /opt/atlassian/jira/current/emailprocessing/testemail2jira/testemail2jira@.service File contents: [Unit] Description=Check that email to %i JIRA works [Service] #Type=oneshot # Note: I keep the config file, testemail2jira.json5 and rsa.* files in emailprocessing/, one directory below testemail2jira/, so that they can be version-controlled independently. # If you want testemail2jira.json5 and rsa.* within testemail2jira/, then add testemail2jira/ to WorkingDirectory and remove it from the ExecStart command WorkingDirectory=/opt/atlassian/%i/current/emailprocessing ExecStart=/opt/atlassian/%i/current/emailprocessing/testemail2jira/venv/bin/python testemail2jira/testemail2jira.py User=root [Install] WantedBy=multi-user.target Perhaps the problem is that my service file is a template (testemail2jira@.service), but I symlinked it as a regular 'testemail2jira.service'. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3
[Touch-packages] [Bug 1891810] Re: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers
Actually the Groovy question seems to be answered by the upload of systemd for bug 1918696. -- 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/1891810 Title: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers Status in libseccomp package in Ubuntu: Fix Released Status in systemd package in Ubuntu: New Status in libseccomp source package in Xenial: Fix Committed Status in systemd source package in Xenial: New Status in libseccomp source package in Bionic: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in libseccomp source package in Focal: Fix Committed Status in systemd source package in Focal: Fix Released Status in libseccomp source package in Groovy: Fix Released Status in systemd source package in Groovy: New Status in libseccomp source package in Hirsute: Fix Released Status in systemd source package in Hirsute: New Bug description: [Impact] The version of libseccomp2 in X/B/F/G does not know about the openat2 syscall. As such applications that use libseccomp cannot specify a system-call filter against this system-call and so it cannot be mediated. [Test Plan] This can be tested by simply running scmp_sys_resolver from the seccomp binary package and specifying this system-call: Existing behaviour: $ scmp_sys_resolver openat2 -1 Expected behaviour: $ scmp_sys_resolver openat2 437 (Note this value will be different on other architectures) [Where problems could occur] In version 2.5.1 of libseccomp which adds this new system-call, changes were also made in the way the socket system-call is handled by libseccomp on PPC platforms - this resulted in a change in the expected behaviour and so this has already been noticed and a fix is required for the systemd unit tests as a result https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696 There was also a similar change for s390x but so far no regressions have been observed as a result as systemd already expected that behaviour from libseccomp, it was only PPC that was missing. In the event that a regression is observed however, we can easily either patch the affected package to cope with the new behaviour of this updated libseccomp since in each case the change in behaviour only affects a few system calls on particular architectures, or we can revert this update. [Other Info] * As usual thorough testing of this update has been performed both manually via the QA Regression Testing scripts, and via the autopkgtest infrastructure against packages in the Ubuntu Security Proposed PPA https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa/ with results seen https://people.canonical.com/~platform/security-britney/current/ I have attached debdiffs of the prepared updates which are also sitting in the Ubuntu Security Proposed PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1891810/+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 1898026] Re: interruption of dist-upgrade can leave you next release in sources.list
This bug was fixed in the package apt - 2.1.10ubuntu0.3
---
apt (2.1.10ubuntu0.3) groovy; urgency=medium
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
[ Julian Andres Klode ]
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all translations when building the cache (LP: #1907850)
* Do not require force-loopbreak on Protected packages (Closes: #983014)
(LP: #1916725)
* RunScripts: Do not reset SIGQUIT and SIGINT to SIG_DFL (LP: #1898026)
* Protect currently running kernel at run-time (LP: #1615381)
* Make ADDARG{,C}() macros expand to single statements
-- Julian Andres Klode Fri, 12 Mar 2021 09:22:11
+0100
** Changed in: apt (Ubuntu Groovy)
Status: Fix Committed => 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/1898026
Title:
interruption of dist-upgrade can leave you next release in
sources.list
Status in apt package in Ubuntu:
Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
Fix Released
Status in apt source package in Bionic:
New
Status in ubuntu-release-upgrader source package in Bionic:
New
Status in apt source package in Focal:
New
Status in ubuntu-release-upgrader source package in Focal:
New
Status in apt source package in Groovy:
Fix Released
Status in ubuntu-release-upgrader source package in Groovy:
New
Status in apt source package in Hirsute:
Fix Released
Status in ubuntu-release-upgrader source package in Hirsute:
Fix Released
Bug description:
[Impact]
Calling update() or installing packages from apt clients resets their SIGINT
and SIGQUIT handlers to SIG_DFL, overriding any signal handlers they might have
set for them.
In case of ubuntu-release-upgrader, this results in the release
upgrader being unable to handle interrupts after it did the initial
update - the default libc handler will run and the program exits.
[Test plan]
[[apt]]
As a standalone test for apt, we can test the following script:
import apt
import time
apt.Cache().update()
print("WAITING")
try:
time.sleep(1)
except BaseException as e:
print("Seen", repr(e))
print("END")
Pressing Ctrl+C while WAITING is printed should print Seen
KeyboardInterrupt, and importantly, also the END line.
[Where problems could occur]
apt: This specific change removes the two lines that SIG_DFL the signal
handlers after running scripts. AFAWCT those lines are unnecessary - the code
that calls it temporarily sets the handlers to SIG_IGN but restores previous
handlers at the end; it was wrongly refactored decades ago. A regression could
occur in that those signals will now continue to be ignored if we missed a spot.
[Original bug report]
As a long-time-user of ?ubuntu, with apt-get as tool of choice for
updates/upgrades I wrote a daily script for updates, with 'dist-upgrade'.
In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu
version; just all packages including new ones. Version updates had to be
initiated manually, and I was always asked if I really wanted the new ?ubuntu
version. Sounds appropriate.
Last night when it (dist-upgrade), it just gave me 20.04. No questions asked.
I for one consider this kind of intrusive, though.
It *might* have to make with me trying 'sudo do-release-upgrade -m desktop' a
number of times earlier; just to *check* if the upgrade was on offer; but this
is only a guess.
In *any* case, a pop-up asking "Are you sure? Are you connected
through an adequate pipe? Are you sitting with full batteries; better
a power supply?" would be convenient; since I am using my PC for
urgent duties, and didn't want to fiddle with unexpected upgrade bugs.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.25
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Thu Oct 1 11:48:39 2020
InstallationDate: Installed on 2019-03-14 (566 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to focal on 2020-09-29 (1 days ago)
VarLogDistupgradeAptlog:
Log time: 2020-09-29 19:44:28.696289
Log time: 2020-09-29 19:44:33.573481
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1898026/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1891810] Re: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers
I don't see a reply to sil2100's question in comment #22: "I see systemd has a 'fix' for this bug in the focal upload so adding the systemd task to the bug as well. Should we assume the systemd parts are already there for hirsute and groovy? I'd like someone to check." Is the systemd part already fixed in Groovy? 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/1891810 Title: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers Status in libseccomp package in Ubuntu: Fix Released Status in systemd package in Ubuntu: New Status in libseccomp source package in Xenial: Fix Committed Status in systemd source package in Xenial: New Status in libseccomp source package in Bionic: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in libseccomp source package in Focal: Fix Committed Status in systemd source package in Focal: Fix Released Status in libseccomp source package in Groovy: Fix Released Status in systemd source package in Groovy: New Status in libseccomp source package in Hirsute: Fix Released Status in systemd source package in Hirsute: New Bug description: [Impact] The version of libseccomp2 in X/B/F/G does not know about the openat2 syscall. As such applications that use libseccomp cannot specify a system-call filter against this system-call and so it cannot be mediated. [Test Plan] This can be tested by simply running scmp_sys_resolver from the seccomp binary package and specifying this system-call: Existing behaviour: $ scmp_sys_resolver openat2 -1 Expected behaviour: $ scmp_sys_resolver openat2 437 (Note this value will be different on other architectures) [Where problems could occur] In version 2.5.1 of libseccomp which adds this new system-call, changes were also made in the way the socket system-call is handled by libseccomp on PPC platforms - this resulted in a change in the expected behaviour and so this has already been noticed and a fix is required for the systemd unit tests as a result https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696 There was also a similar change for s390x but so far no regressions have been observed as a result as systemd already expected that behaviour from libseccomp, it was only PPC that was missing. In the event that a regression is observed however, we can easily either patch the affected package to cope with the new behaviour of this updated libseccomp since in each case the change in behaviour only affects a few system calls on particular architectures, or we can revert this update. [Other Info] * As usual thorough testing of this update has been performed both manually via the QA Regression Testing scripts, and via the autopkgtest infrastructure against packages in the Ubuntu Security Proposed PPA https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa/ with results seen https://people.canonical.com/~platform/security-britney/current/ I have attached debdiffs of the prepared updates which are also sitting in the Ubuntu Security Proposed PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1891810/+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 1907850] Re: Cache not generated for all translations
This bug was fixed in the package apt - 2.1.10ubuntu0.3
---
apt (2.1.10ubuntu0.3) groovy; urgency=medium
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
[ Julian Andres Klode ]
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all translations when building the cache (LP: #1907850)
* Do not require force-loopbreak on Protected packages (Closes: #983014)
(LP: #1916725)
* RunScripts: Do not reset SIGQUIT and SIGINT to SIG_DFL (LP: #1898026)
* Protect currently running kernel at run-time (LP: #1615381)
* Make ADDARG{,C}() macros expand to single statements
-- Julian Andres Klode Fri, 12 Mar 2021 09:22:11
+0100
** Changed in: apt (Ubuntu Groovy)
Status: Fix Committed => 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/1907850
Title:
Cache not generated for all translations
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Confirmed
Status in apt source package in Bionic:
Fix Committed
Status in apt source package in Focal:
Fix Committed
Status in apt source package in Groovy:
Fix Released
Status in apt source package in Hirsute:
Fix Released
Bug description:
[Impact]
In bug 1161743 we discovered that if a system is configured with multiple
locales, only the locales of the user who generated the apt-cache will be
available for translated descriptions.
[Test case]
An automated test case has been included as a snippet in
test/integration/test-bug-49-search-in-all-translations which runs during
autopkgtest. That's sufficient for validation.
Manual test:
# apt install locales-all # get the locale
# export LANG=sv_SE.UTF-8
# locale
LANG=sv_SE.UTF-8
LANGUAGE=
LC_CTYPE="sv_SE.UTF-8"
LC_NUMERIC="sv_SE.UTF-8"
LC_TIME="sv_SE.UTF-8"
LC_COLLATE="sv_SE.UTF-8"
LC_MONETARY="sv_SE.UTF-8"
LC_MESSAGES="sv_SE.UTF-8"
LC_PAPER="sv_SE.UTF-8"
LC_NAME="sv_SE.UTF-8"
LC_ADDRESS="sv_SE.UTF-8"
LC_TELEPHONE="sv_SE.UTF-8"
LC_MEASUREMENT="sv_SE.UTF-8"
LC_IDENTIFICATION="sv_SE.UTF-8"
LC_ALL=
# apt update
# apt-cache show tasksel | grep Desc
Description-sv: tool for selecting tasks for installation on Debian systems
Description-md5: cbbb747708986d11ea77c80b9b038fec
# apt-cache showpkg tasksel
Package: tasksel
Versions:
3.34ubuntu16
(/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages)
Description Language:
File:
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages
MD5: cbbb747708986d11ea77c80b9b038fec
Description Language: sv
File:
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-sv
MD5: cbbb747708986d11ea77c80b9b038fec
Description Language: en
File:
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en
MD5: cbbb747708986d11ea77c80b9b038fec
[...]
So far so good, but now assume the root user actually has C configured
as locale, and e.g. runs apt-cache show (or apt-daily.service does an
update):
root@g:~# rm /var/cache/apt/*.bin
root@g:~# LANG=C apt-cache show tasksel
[...]
Description-en: tool for selecting tasks for installation on Debian systems
This package provides 'tasksel', a simple interface for users who
want to configure their system to perform a specific task.
root@g:~# apt-cache showpkg tasksel
Package: tasksel
Versions:
3.34ubuntu16
(/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages)
Description Language:
File:
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages
MD5: cbbb747708986d11ea77c80b9b038fec
Description Language: en
File:
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en
MD5: cbbb747708986d11ea77c80b9b038fec
This should show the sv locale as well given that it's still around
(also we are still running with LANG=sv_SE.UTF-8), but it only
generated the cache with the english language description in here.
[Where problems could occur]
People might end up seeing a wrong translation if other code paths are wrong,
but then they'd already see them if they explicitly configured multiple
languages and then switched the preferred one.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1907850/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe :
[Touch-packages] [Bug 1907850] Update Released
The verification of the Stable Release Update for apt 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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1907850 Title: Cache not generated for all translations Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Released Status in apt source package in Hirsute: Fix Released Bug description: [Impact] In bug 1161743 we discovered that if a system is configured with multiple locales, only the locales of the user who generated the apt-cache will be available for translated descriptions. [Test case] An automated test case has been included as a snippet in test/integration/test-bug-49-search-in-all-translations which runs during autopkgtest. That's sufficient for validation. Manual test: # apt install locales-all # get the locale # export LANG=sv_SE.UTF-8 # locale LANG=sv_SE.UTF-8 LANGUAGE= LC_CTYPE="sv_SE.UTF-8" LC_NUMERIC="sv_SE.UTF-8" LC_TIME="sv_SE.UTF-8" LC_COLLATE="sv_SE.UTF-8" LC_MONETARY="sv_SE.UTF-8" LC_MESSAGES="sv_SE.UTF-8" LC_PAPER="sv_SE.UTF-8" LC_NAME="sv_SE.UTF-8" LC_ADDRESS="sv_SE.UTF-8" LC_TELEPHONE="sv_SE.UTF-8" LC_MEASUREMENT="sv_SE.UTF-8" LC_IDENTIFICATION="sv_SE.UTF-8" LC_ALL= # apt update # apt-cache show tasksel | grep Desc Description-sv: tool for selecting tasks for installation on Debian systems Description-md5: cbbb747708986d11ea77c80b9b038fec # apt-cache showpkg tasksel Package: tasksel Versions: 3.34ubuntu16 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages) Description Language: File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages MD5: cbbb747708986d11ea77c80b9b038fec Description Language: sv File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-sv MD5: cbbb747708986d11ea77c80b9b038fec Description Language: en File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en MD5: cbbb747708986d11ea77c80b9b038fec [...] So far so good, but now assume the root user actually has C configured as locale, and e.g. runs apt-cache show (or apt-daily.service does an update): root@g:~# rm /var/cache/apt/*.bin root@g:~# LANG=C apt-cache show tasksel [...] Description-en: tool for selecting tasks for installation on Debian systems This package provides 'tasksel', a simple interface for users who want to configure their system to perform a specific task. root@g:~# apt-cache showpkg tasksel Package: tasksel Versions: 3.34ubuntu16 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages) Description Language: File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages MD5: cbbb747708986d11ea77c80b9b038fec Description Language: en File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en MD5: cbbb747708986d11ea77c80b9b038fec This should show the sv locale as well given that it's still around (also we are still running with LANG=sv_SE.UTF-8), but it only generated the cache with the english language description in here. [Where problems could occur] People might end up seeing a wrong translation if other code paths are wrong, but then they'd already see them if they explicitly configured multiple languages and then switched the preferred one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1907850/+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 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
To confirm the focal fossa bug, I booted the server using the ubuntu focal fossa live cd and applied the same configuration via netplan. Some interfaces became failed/degraded as here https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1912331/comments/13 -- 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/1912331 Title: Many interfaces lead to "kernel receive buffer overrun" Status in systemd: Fix Released Status in systemd package in Ubuntu: Invalid Status in systemd source package in Focal: Invalid Status in systemd source package in Groovy: Invalid Bug description: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+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 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
Hi, I booted the server using the ubuntu groovy live cd and applied the same configuration via netplan. All interfaces became up. I suspected that this patch https://github.com/systemd/systemd/pull/16982 solved the issue. Can you port this patch to focal fossa? Thanks networkctl -a IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 eth0 etherroutableconfigured 3 eth1 etherno-carrier configuring 4 eth2 etherno-carrier configuring 5 eth3 etherno-carrier configuring 6 eth4 etherno-carrier configuring 7 eth5 etherno-carrier configuring 8 br0bridge no-carrier configured 9 br1bridge no-carrier configured 10 br2bridge no-carrier configured 11 br3bridge no-carrier configured 12 br4bridge no-carrier configured 13 br4.8 vlan no-carrier configured 14 br4.4 vlan no-carrier configured 15 br4.7 vlan no-carrier configured 16 br4.2 vlan no-carrier configured 17 br4.9 vlan no-carrier configured 18 br4.14 vlan no-carrier configured 19 br4.3 vlan no-carrier configured 20 br4.17 vlan no-carrier configured 21 br4.0 vlan no-carrier configured 22 br4.12 vlan no-carrier configured 23 br4.10 vlan no-carrier configured 24 br4.5 vlan no-carrier configured 25 br4.6 vlan no-carrier configured 26 br4.16 vlan no-carrier configured 27 br4.11 vlan no-carrier configured 28 br4.13 vlan no-carrier configured 29 br4.15 vlan no-carrier configured 30 br4.1 vlan no-carrier configured 31 br3.5 vlan no-carrier configured 32 br3.10 vlan no-carrier configured 33 br3.4 vlan no-carrier configured 34 br3.1 vlan no-carrier configured 35 br3.0 vlan no-carrier configured 36 br3.6 vlan no-carrier configured 37 br3.16 vlan no-carrier configured 38 br3.11 vlan no-carrier configured 39 br3.12 vlan no-carrier configured 40 br3.14 vlan no-carrier configured 41 br3.8 vlan no-carrier configured 42 br3.15 vlan no-carrier configured 43 br3.2 vlan no-carrier configured 44 br3.17 vlan no-carrier configured 45 br3.3 vlan no-carrier configured 46 br3.7 vlan no-carrier configured 47 br3.9 vlan no-carrier configured 48 br3.13 vlan no-carrier configured 49 br2.6 vlan no-carrier configured 50 br2.3 vlan no-carrier configured 51 br2.16 vlan no-carrier configured 52 br2.17 vlan no-carrier configured 53 br2.8 vlan no-carrier configured 54 br2.15 vlan no-carrier configured 55 br2.1 vlan no-carrier configured 56 br2.2 vlan no-carrier configured 57 br2.0 vlan no-carrier configured 58 br2.10 vlan no-carrier configured 59 br2.13 vlan no-carrier configured 60 br2.11 vlan no-carrier configured 61 br2.5 vlan no-carrier configured 62 br2.9 vlan no-carrier configured 63 br2.12 vlan no-carrier configured 64 br2.7 vlan no-carrier configured 65 br2.14 vlan no-carrier configured 66 br2.4 vlan no-carrier configured 67 br1.13 vlan no-carrier configured 68 br1.16 vlan no-carrier configured 69 br1.3 vlan no-carrier configured 70 br1.0 vlan no-carrier configured 71 br1.17 vlan no-carrier configured 72 br1.14 vlan no-carrier configured 73 br1.2 vlan no-carrier configured 74 br1.7 vlan no-carrier configured 75 br1.1 vlan no-carrier configured 76 br1.5 vlan no-carrier configured 77 br1.9 vlan no-carrier configured 78 br1.4 vlan no-carrier configured 79 br1.11 vlan no-carrier configured 80 br1.12 vlan no-carrier configured 81 br1.15 vlan no-carrier configured 82 br1.6 vlan no-carrier configured 83 br1.8 vlan no-carrier configured 84 br1.10 vlan no-carrier configured 85 br0.5 vlan no-carrier configured 86 br0.13 vlan no-carrier configured 87 br0.12 vlan no-carrier configured 88 br0.11 vlan no-carrier configured 89 br0.0 vlan no-carrier configured 90 br0.1 vlan no-carrier configured 91 br0.15 vlan no-carrier configured 92 br0.3 vlan no-carrier configured 93 br0.14 vlan no-carrier configured 94 br0.4 vlan no-carrier configured 95 br0.7 vlan no-carrier configured 96 br0.6 vlan no-carrier configured 97 br0.2 vlan no-carrier configured 98 br0.9 vlan no-carrier configured 99 br0.10 vlan no-carrier configured 100 br0.16 vlan no-carrier configured 101 br0.17 vlan no-carrier configured 102 br0.8 vlan no-carrier configured 102 links listed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.
[Touch-packages] [Bug 1915502] Re: "systemd --user" fails to start for non-local users
Ok I think we need to see the pam_systemd side of this then; can you add
'systemd.log_level=debug' to the boot params and reboot, and then
recreate the failure? There will be a whole lot of debug in the journal,
but it should include the pam-side failure.
--
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/1915502
Title:
"systemd --user" fails to start for non-local users
Status in systemd package in Ubuntu:
Incomplete
Status in systemd source package in Focal:
New
Bug description:
systemd-logind fails to start the systemd --user process for non-local
users on Ubuntu 20.04. This is a reproducible problem; all our
systems are displaying the same symptoms.
The systems are using Kerberos (Active Directory) for authentication,
and NIS for account meta-data and authorisation (groups)
A base installation is performed using the server 20.04 ISO image. No
additional packages are selected. Post-install, I run:
apt-get install tcsh nis krb5-user libpam-krb5 libnss-systemd
I set up the NIS client (supply the default domain name, check ypbind
is running and ypcat passwd is working)
I then set up /etc/krb5.conf for kerberos authentication to a domain
controller, confirm that kinit works and a kerberos ticket is issued.
I modify /etc/passwd, /etc/group and /etc/shadow, appending a "+" to
the end of each.
/etc/nsswitch.conf is modified to support compat mode, as well as
systemd:
passwd: compat systemd
group: compat systemd
shadow: compat
I can log in remotely via ssh using my NIS account and Kerberos
credentials. MY NIS meta-data looks like:
amcvey:KRB5:::Andy McVey:/home/amcvey:/bin/tcsh
(where UID and GID are replaced with values unique to the
organisation)
On login, the following occurs:
hostname:~> systemctl --user
Failed to connect to bus: No such file or directory
I put pam-systemd and systemd-logind into debug mode to get more
information:
Feb 12 09:51:32 myhostname sshd[1210]: Accepted publickey for amcvey from
[redact] port 58849 ssh2: RSA SHA256:[redact]
Feb 12 09:51:32 myhostname sshd[1210]: pam_unix(sshd:session): session opened
for user amcvey by (uid=0)
Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_call
sender=:1.13 destination=org.freedesktop.login1 path=/org/freedesktop/login1
interface=org.freedesktop.login1.Manager member=CreateSession cookie=2
reply_cookie=0 signature=uusussbssa(sv) error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): pam-systemd
initializing
Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus
interface=org.freedesktop.DBus member=GetConnectionUnixUser cookie=40
reply_cookie=0 signature=s error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Asking
logind to create session: uid=198083 pid=1210 service=sshd type=tty class=user
desktop= seat= vtnr=0 tty= display= remote=yes remote_user=
remote_host=10.105.121.110
Feb 12 09:51:32 myhostname systemd-logind[903]: Got message
type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a
interface=n/a member=n/a cookie=13 reply_cookie=40 signature=u error-name=n/a
error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Session
limits: memory_max=n/a tasks_max=n/a cpu_weight=n/a io_weight=n/a
runtime_max_sec=n/a
Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus
interface=org.freedesktop.DBus member=GetConnectionUnixProcessID cookie=41
reply_cookie=0 signature=s error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Failed to
create session: No such process
Feb 12 09:51:32 myhostname systemd-logind[903]: Got message
type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a
interface=n/a member=n/a cookie=14 reply_cookie=41 signature=u error-name=n/a
error-message=n/a
Feb 12 09:51:32 myhostname systemd-logind[903]: Unable to connect to
/run/systemd/userdb/io.systemd.Multiplexer: No such file or directory
Feb 12 09:51:32 myhostname systemd-logind[903]: n/a: varlink: setting state
idle-client
Feb 12 09:51:32 myhostname systemd-logind[903]:
/run/systemd/userdb/io.systemd.DynamicUser: Sending message:
{"method":"io.systemd.UserDatabase.GetUserRecord","parameters":{"uid":198083,"service":"io.systemd.DynamicUser"}}
Feb 12 09:51:32 myhostname systemd-logind[903]:
/run/systemd/userdb/io.systemd.DynamicUser: varlink: changing state idle-client
→ awaiting-reply
Feb 12 09:51:32 myhostname systemd-logind[903]:
/run/systemd/userdb/io.systemd.DynamicUser: New
[Touch-packages] [Bug 1915887] Re: systemd spams the syslog about lack of native systemd unit file
This bug was fixed in the package systemd - 245.4-4ubuntu3.6 --- systemd (245.4-4ubuntu3.6) focal; urgency=medium * debian/patches/lp1916485-Newer-Glibc-use-faccessat2-to-implement-faccessat.patch: Add support for faccessat2 (LP: #1916485) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=affb2c6507dccfeed02820a2267639648e2a2260 * d/p/lp1918696-shared-seccomp-util-address-family-filtering-is-brok.patch: Stop attempting to restrict address families on ppc archs (LP: #1918696) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=daff4b6604362fcb5d305682216d5ca15a4c5738 * d/p/lp1891810-seccomp-util-add-new-syscalls-from-kernel-5.6-to-sys.patch: Add openat2() syscall to seccomp filter list (LP: #1891810) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=69c8a684e2513b2f6530e5a5cf15c83abfb7bc74 * d/p/lp1915887-Downgrade-a-couple-of-warnings-to-debug.patch: Downgrade some log messages so they stop spamming logs (LP: #1915887) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3c2c4731b90ed430ca1790270e69cd125643b94b * d/p/lp1887744-basic-unit-file-when-loading-linked-unit-files-use-l.patch: Use src name, not dst name, of symlinked unit files (LP: #1887744) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=03770601097cfdc09adeadf5593083da69345409 -- Dan Streetman Wed, 17 Mar 2021 17:36:08 -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/1915887 Title: systemd spams the syslog about lack of native systemd unit file Status in apport package in Ubuntu: Invalid Status in fam package in Ubuntu: Invalid Status in freeradius package in Ubuntu: Invalid Status in ipfm package in Ubuntu: Invalid Status in n2n package in Ubuntu: Invalid Status in pfm package in Ubuntu: Invalid Status in shadowsocks package in Ubuntu: Invalid Status in sysfsutils package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Invalid Status in xl2tpd package in Ubuntu: Invalid Status in systemd source package in Focal: Fix Released Status in systemd source package in Groovy: Fix Released Status in systemd package in Debian: Fix Released Bug description: [impact] systemd spams journal with log messages [test case] see journalctl output and search for msgs similar to those listed in original description below; specifically messages containing text with "below legacy directory /var/run/" or "lacks a native systemd unit file" [regression potential] any regession would likely result in logs incorrectly not logged when detecting a problem such as lack of native unit file, or using /var/run. [scope] this is needed in f/g this is fixed upstream with commit https://salsa.debian.org/systemd- team/systemd/-/commit/0c6d90f783093fc255e529f8a33b2ed2a8e6c2d6 from debian, which is included in 247.3-2 and later so this is fixed in hirsute already (in -proposed package). these log messages aren't present in b or earlier so aren't needed in x/b [original description] systemd in hirsute spams the syslog file several times per second about services lacking native systemd unit files. Two things should happen. 1) a systemd unit file ought to be created 2) systemd should be slowed down with regards to these messages Feb 17 02:02:48 ubuntu-devel kernel: [ 289.794825] systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 290.165351] systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 291.111278] systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:50 ubuntu-devel kernel: [ 291.507164] systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386062]
[Touch-packages] [Bug 1915887] 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/1915887 Title: systemd spams the syslog about lack of native systemd unit file Status in apport package in Ubuntu: Invalid Status in fam package in Ubuntu: Invalid Status in freeradius package in Ubuntu: Invalid Status in ipfm package in Ubuntu: Invalid Status in n2n package in Ubuntu: Invalid Status in pfm package in Ubuntu: Invalid Status in shadowsocks package in Ubuntu: Invalid Status in sysfsutils package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Invalid Status in xl2tpd package in Ubuntu: Invalid Status in systemd source package in Focal: Fix Released Status in systemd source package in Groovy: Fix Released Status in systemd package in Debian: Fix Released Bug description: [impact] systemd spams journal with log messages [test case] see journalctl output and search for msgs similar to those listed in original description below; specifically messages containing text with "below legacy directory /var/run/" or "lacks a native systemd unit file" [regression potential] any regession would likely result in logs incorrectly not logged when detecting a problem such as lack of native unit file, or using /var/run. [scope] this is needed in f/g this is fixed upstream with commit https://salsa.debian.org/systemd- team/systemd/-/commit/0c6d90f783093fc255e529f8a33b2ed2a8e6c2d6 from debian, which is included in 247.3-2 and later so this is fixed in hirsute already (in -proposed package). these log messages aren't present in b or earlier so aren't needed in x/b [original description] systemd in hirsute spams the syslog file several times per second about services lacking native systemd unit files. Two things should happen. 1) a systemd unit file ought to be created 2) systemd should be slowed down with regards to these messages Feb 17 02:02:48 ubuntu-devel kernel: [ 289.794825] systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 290.165351] systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 291.111278] systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:50 ubuntu-devel kernel: [ 291.507164] systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386062] systemd-sysv-generator[9909]: SysV service '/etc/init.d/fam' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386321] systemd-sysv-generator[9909]: SysV service '/etc/init.d/xl2tpd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386742] systemd-sysv-generator[9909]: SysV service '/etc/init.d/ipfm' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386767] systemd-sysv-generator[9909]: SysV service '/etc/init.d/shadowsocks' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native
[Touch-packages] [Bug 1915887] Re: systemd spams the syslog about lack of native systemd unit file
This bug was fixed in the package systemd - 246.6-1ubuntu1.3 --- systemd (246.6-1ubuntu1.3) groovy; urgency=medium * d/p/lp1918696-shared-seccomp-util-address-family-filtering-is-brok.patch: Stop attempting to restrict address families on ppc archs (LP: #1918696) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=34d1b2b4f4fdc349da37a07fe98418456167592a * d/p/lp1915887-Downgrade-a-couple-of-warnings-to-debug.patch: Downgrade some log messages so they stop spamming logs (LP: #1915887) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d092e70912009daf6f64182d86b3d92aed28722a * d/p/lp1887744-basic-unit-file-when-loading-linked-unit-files-use-l.patch: Use src name, not dst name, of symlinked unit files (LP: #1887744) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1e42633ccecc9c9157b19387c11ac1bf7ea7d161 -- Dan Streetman Wed, 10 Mar 2021 16:03:13 -0500 ** Changed in: systemd (Ubuntu Groovy) 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/1915887 Title: systemd spams the syslog about lack of native systemd unit file Status in apport package in Ubuntu: Invalid Status in fam package in Ubuntu: Invalid Status in freeradius package in Ubuntu: Invalid Status in ipfm package in Ubuntu: Invalid Status in n2n package in Ubuntu: Invalid Status in pfm package in Ubuntu: Invalid Status in shadowsocks package in Ubuntu: Invalid Status in sysfsutils package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Invalid Status in xl2tpd package in Ubuntu: Invalid Status in systemd source package in Focal: Fix Released Status in systemd source package in Groovy: Fix Released Status in systemd package in Debian: Fix Released Bug description: [impact] systemd spams journal with log messages [test case] see journalctl output and search for msgs similar to those listed in original description below; specifically messages containing text with "below legacy directory /var/run/" or "lacks a native systemd unit file" [regression potential] any regession would likely result in logs incorrectly not logged when detecting a problem such as lack of native unit file, or using /var/run. [scope] this is needed in f/g this is fixed upstream with commit https://salsa.debian.org/systemd- team/systemd/-/commit/0c6d90f783093fc255e529f8a33b2ed2a8e6c2d6 from debian, which is included in 247.3-2 and later so this is fixed in hirsute already (in -proposed package). these log messages aren't present in b or earlier so aren't needed in x/b [original description] systemd in hirsute spams the syslog file several times per second about services lacking native systemd unit files. Two things should happen. 1) a systemd unit file ought to be created 2) systemd should be slowed down with regards to these messages Feb 17 02:02:48 ubuntu-devel kernel: [ 289.794825] systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 290.165351] systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 291.111278] systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:50 ubuntu-devel kernel: [ 291.507164] systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386062] systemd-sysv-generator[9909]: SysV service '/etc/init.d/fam' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386321] systemd-sysv-generator[9909]: SysV service '/etc/init.d/xl2tpd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit
[Touch-packages] [Bug 1916050] Re: Invalid base64 for high-bit characters
This bug was fixed in the package apt - 2.1.10ubuntu0.3
---
apt (2.1.10ubuntu0.3) groovy; urgency=medium
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
[ Julian Andres Klode ]
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all translations when building the cache (LP: #1907850)
* Do not require force-loopbreak on Protected packages (Closes: #983014)
(LP: #1916725)
* RunScripts: Do not reset SIGQUIT and SIGINT to SIG_DFL (LP: #1898026)
* Protect currently running kernel at run-time (LP: #1615381)
* Make ADDARG{,C}() macros expand to single statements
-- Julian Andres Klode Fri, 12 Mar 2021 09:22:11
+0100
** Changed in: apt (Ubuntu Groovy)
Status: Fix Committed => 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/1916050
Title:
Invalid base64 for high-bit characters
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Confirmed
Status in apt source package in Bionic:
Fix Committed
Status in apt source package in Focal:
Fix Committed
Status in apt source package in Groovy:
Fix Released
Status in apt source package in Hirsute:
Fix Released
Bug description:
[Impact]
The Base64Encode function incorrectly encodes using char instead of uint8_t,
leading to characters with the high bit set to be encoded wrongly. This
function is used for base authentication, and high bits are set for UTF-8
character sequences, so it's likely affecting people with utf-8 user names and
passwords and might cause them to be denied access to their https resources
(though arguably they'd work around that).
[Test case]
A unit test has been added that checks that the encoding is correct.
[Where problems could occur]
This only affects the base64 encoding function, which is only used for
quoting user names and passwords in basic auth in http, but it's also exposed
to library users and like in python-apt, so problems could occur wherever they
use that base64 encoding function as well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1916050/+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 1916050] Update Released
The verification of the Stable Release Update for apt 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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1916050 Title: Invalid base64 for high-bit characters Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Released Status in apt source package in Hirsute: Fix Released Bug description: [Impact] The Base64Encode function incorrectly encodes using char instead of uint8_t, leading to characters with the high bit set to be encoded wrongly. This function is used for base authentication, and high bits are set for UTF-8 character sequences, so it's likely affecting people with utf-8 user names and passwords and might cause them to be denied access to their https resources (though arguably they'd work around that). [Test case] A unit test has been added that checks that the encoding is correct. [Where problems could occur] This only affects the base64 encoding function, which is only used for quoting user names and passwords in basic auth in http, but it's also exposed to library users and like in python-apt, so problems could occur wherever they use that base64 encoding function as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1916050/+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 1916485] Re: test -x fails inside shell scripts in containers
This bug was fixed in the package systemd - 245.4-4ubuntu3.6 --- systemd (245.4-4ubuntu3.6) focal; urgency=medium * debian/patches/lp1916485-Newer-Glibc-use-faccessat2-to-implement-faccessat.patch: Add support for faccessat2 (LP: #1916485) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=affb2c6507dccfeed02820a2267639648e2a2260 * d/p/lp1918696-shared-seccomp-util-address-family-filtering-is-brok.patch: Stop attempting to restrict address families on ppc archs (LP: #1918696) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=daff4b6604362fcb5d305682216d5ca15a4c5738 * d/p/lp1891810-seccomp-util-add-new-syscalls-from-kernel-5.6-to-sys.patch: Add openat2() syscall to seccomp filter list (LP: #1891810) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=69c8a684e2513b2f6530e5a5cf15c83abfb7bc74 * d/p/lp1915887-Downgrade-a-couple-of-warnings-to-debug.patch: Downgrade some log messages so they stop spamming logs (LP: #1915887) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3c2c4731b90ed430ca1790270e69cd125643b94b * d/p/lp1887744-basic-unit-file-when-loading-linked-unit-files-use-l.patch: Use src name, not dst name, of symlinked unit files (LP: #1887744) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=03770601097cfdc09adeadf5593083da69345409 -- Dan Streetman Wed, 17 Mar 2021 17:36:08 -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/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in docker.io source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: Fix Committed Status in systemd source package in Focal: Fix Released Status in docker.io source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: Fix Committed Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo
[Touch-packages] [Bug 1916485] 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/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in docker.io source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: Fix Committed Status in systemd source package in Focal: Fix Released Status in docker.io source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: Fix Committed Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg
[Touch-packages] [Bug 1916725] Update Released
The verification of the Stable Release Update for apt 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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1916725 Title: Protected/Important packages are not deconfigured, require Force- LoopBreak Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Released Status in apt source package in Hirsute: Fix Released Bug description: [Impact] If a package that is Protected: yes (or Important: yes), or one of it's dependencies, is involved in a dependency loop with Breaks, APT requires APT::Force-LoopBreak instead of resolving the situation directly. On focal, we also introduce the actual support for protected packages to enable upgrading to later releases more easily (in case a protected package needs to be removed during the upgrade), and to make the backport more similar to main. [Test plan] Run the integration test suite (the autopkgtest) :) Our test suite covers the tests for both Breaks and Conflicts. Breaks: protected-sysvinit (= 1) without dependencies is installed protected-sysvinit (= 2) Pre-Depends protected-systemd-sysv protected-systemd-sysv (= 2) Breaks: protected-sysvinit (<< 2) Test: Install protected-sysvinit (= 2) Expected result: Unpacking protected-sysvinit (= 2) deconfigures protected-sysvinit (= 1), and then we unpack and configure protected-sysvinit (= 2) and end up with a working system. Conflicts: As for Breaks, but the Conflicts will remove the package temporarily, requiring the use of APT::Force-LoopBreak option. For focal, we also do have a test to check that the Protected field is being used. [Where problems could occur] We now allow dpkg to automatically deconfigure protected packages. This should just make them behave like normal packages to APT's eye, but bugs I guess could occur somewhere in the APT/dpkg interaction (this only applies to releases with Protected support in dpkg, Important is not affected, it's always been "normal" for dpkg). During development, we accidentally simplified the patch so much that Conflicts did not require Force-LoopBreak for temporary removal. We fixed that, but it points out that there is a place where the loop break check happens that is a potential regression place. On focal, we pass additional flags to dpkg that focal's dpkg does not understand, however, we only do that if dpkg asserts it does that, so in practice, this should all work fine and the code path will only be taken with >=groovy dpkg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1916725/+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 1916725] Re: Protected/Important packages are not deconfigured, require Force-LoopBreak
This bug was fixed in the package apt - 2.1.10ubuntu0.3
---
apt (2.1.10ubuntu0.3) groovy; urgency=medium
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
[ Julian Andres Klode ]
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all translations when building the cache (LP: #1907850)
* Do not require force-loopbreak on Protected packages (Closes: #983014)
(LP: #1916725)
* RunScripts: Do not reset SIGQUIT and SIGINT to SIG_DFL (LP: #1898026)
* Protect currently running kernel at run-time (LP: #1615381)
* Make ADDARG{,C}() macros expand to single statements
-- Julian Andres Klode Fri, 12 Mar 2021 09:22:11
+0100
** Changed in: apt (Ubuntu Groovy)
Status: Fix Committed => 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/1916725
Title:
Protected/Important packages are not deconfigured, require Force-
LoopBreak
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Bionic:
Fix Committed
Status in apt source package in Focal:
Fix Committed
Status in apt source package in Groovy:
Fix Released
Status in apt source package in Hirsute:
Fix Released
Bug description:
[Impact]
If a package that is Protected: yes (or Important: yes), or one of it's
dependencies, is involved in a dependency loop with Breaks, APT requires
APT::Force-LoopBreak instead of resolving the situation directly.
On focal, we also introduce the actual support for protected packages
to enable upgrading to later releases more easily (in case a protected
package needs to be removed during the upgrade), and to make the
backport more similar to main.
[Test plan]
Run the integration test suite (the autopkgtest) :)
Our test suite covers the tests for both Breaks and Conflicts.
Breaks:
protected-sysvinit (= 1) without dependencies is installed
protected-sysvinit (= 2) Pre-Depends protected-systemd-sysv
protected-systemd-sysv (= 2) Breaks: protected-sysvinit (<< 2)
Test: Install protected-sysvinit (= 2)
Expected result: Unpacking protected-sysvinit (= 2) deconfigures
protected-sysvinit (= 1), and then we unpack and configure protected-sysvinit
(= 2) and end up with a working system.
Conflicts: As for Breaks, but the Conflicts will remove the package
temporarily, requiring the use of APT::Force-LoopBreak option.
For focal, we also do have a test to check that the Protected field is
being used.
[Where problems could occur]
We now allow dpkg to automatically deconfigure protected packages. This
should just make them behave like normal packages to APT's eye, but bugs I
guess could occur somewhere in the APT/dpkg interaction (this only applies to
releases with Protected support in dpkg, Important is not affected, it's always
been "normal" for dpkg).
During development, we accidentally simplified the patch so much that
Conflicts did not require Force-LoopBreak for temporary removal. We
fixed that, but it points out that there is a place where the loop
break check happens that is a potential regression place.
On focal, we pass additional flags to dpkg that focal's dpkg does not
understand, however, we only do that if dpkg asserts it does that, so
in practice, this should all work fine and the code path will only be
taken with >=groovy dpkg.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1916725/+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 1918696] Re: libseccomp 2.5.1 will break unit tests on ppc
This bug was fixed in the package systemd - 245.4-4ubuntu3.6 --- systemd (245.4-4ubuntu3.6) focal; urgency=medium * debian/patches/lp1916485-Newer-Glibc-use-faccessat2-to-implement-faccessat.patch: Add support for faccessat2 (LP: #1916485) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=affb2c6507dccfeed02820a2267639648e2a2260 * d/p/lp1918696-shared-seccomp-util-address-family-filtering-is-brok.patch: Stop attempting to restrict address families on ppc archs (LP: #1918696) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=daff4b6604362fcb5d305682216d5ca15a4c5738 * d/p/lp1891810-seccomp-util-add-new-syscalls-from-kernel-5.6-to-sys.patch: Add openat2() syscall to seccomp filter list (LP: #1891810) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=69c8a684e2513b2f6530e5a5cf15c83abfb7bc74 * d/p/lp1915887-Downgrade-a-couple-of-warnings-to-debug.patch: Downgrade some log messages so they stop spamming logs (LP: #1915887) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3c2c4731b90ed430ca1790270e69cd125643b94b * d/p/lp1887744-basic-unit-file-when-loading-linked-unit-files-use-l.patch: Use src name, not dst name, of symlinked unit files (LP: #1887744) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=03770601097cfdc09adeadf5593083da69345409 -- Dan Streetman Wed, 17 Mar 2021 17:36:08 -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/1918696 Title: libseccomp 2.5.1 will break unit tests on ppc Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Released Status in systemd source package in Groovy: Fix Released Bug description: [impact] when libseccomp is upgraded to 2.5.1 on all releases, the systemd seccomp unit tests will start failing on ppc, as RestrictAddressFamilies= will no longer work on that arch. However, the systemd.exec man page has stated that RestrictAddressFamiles= doesn't work on ppc since before bionic. [test case] check systemd autopkgtest on ppc, looking at the test_restrict_access_familes unit test [regression potential] any regression would involve the use of RestrictAddressFamilies=, either no longer restricting or incorrectly restricting address familes. [scope] this is needed for b/f/g this was fixed upstream by commit d5923e38bc0e6cf9d7620ed5f1f8606fe7fe1168 which is included in 247, so this is fixed in h already This isn't needed in x, because it doesn't include upstream commit 469830d1426a91e0897c321fdc8ee428f0a750c1 which reworked the code to switch from seccomp_rule_add to seccomp_rule_add_exact, so systemd could handle lack of arch support itself, instead of allowing the 'not exact' seccomp syscall to just ignore the call due to lack of arch support. [other info] libseccomp will be updated to 2.5.1 in the near future so this is needed before that update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696/+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 1918696] Re: libseccomp 2.5.1 will break unit tests on ppc
This bug was fixed in the package systemd - 246.6-1ubuntu1.3 --- systemd (246.6-1ubuntu1.3) groovy; urgency=medium * d/p/lp1918696-shared-seccomp-util-address-family-filtering-is-brok.patch: Stop attempting to restrict address families on ppc archs (LP: #1918696) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=34d1b2b4f4fdc349da37a07fe98418456167592a * d/p/lp1915887-Downgrade-a-couple-of-warnings-to-debug.patch: Downgrade some log messages so they stop spamming logs (LP: #1915887) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d092e70912009daf6f64182d86b3d92aed28722a * d/p/lp1887744-basic-unit-file-when-loading-linked-unit-files-use-l.patch: Use src name, not dst name, of symlinked unit files (LP: #1887744) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1e42633ccecc9c9157b19387c11ac1bf7ea7d161 -- Dan Streetman Wed, 10 Mar 2021 16:03:13 -0500 ** Changed in: systemd (Ubuntu Groovy) 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/1918696 Title: libseccomp 2.5.1 will break unit tests on ppc Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Released Status in systemd source package in Groovy: Fix Released Bug description: [impact] when libseccomp is upgraded to 2.5.1 on all releases, the systemd seccomp unit tests will start failing on ppc, as RestrictAddressFamilies= will no longer work on that arch. However, the systemd.exec man page has stated that RestrictAddressFamiles= doesn't work on ppc since before bionic. [test case] check systemd autopkgtest on ppc, looking at the test_restrict_access_familes unit test [regression potential] any regression would involve the use of RestrictAddressFamilies=, either no longer restricting or incorrectly restricting address familes. [scope] this is needed for b/f/g this was fixed upstream by commit d5923e38bc0e6cf9d7620ed5f1f8606fe7fe1168 which is included in 247, so this is fixed in h already This isn't needed in x, because it doesn't include upstream commit 469830d1426a91e0897c321fdc8ee428f0a750c1 which reworked the code to switch from seccomp_rule_add to seccomp_rule_add_exact, so systemd could handle lack of arch support itself, instead of allowing the 'not exact' seccomp syscall to just ignore the call due to lack of arch support. [other info] libseccomp will be updated to 2.5.1 in the near future so this is needed before that update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696/+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 1918696] 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/1918696 Title: libseccomp 2.5.1 will break unit tests on ppc Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Released Status in systemd source package in Groovy: Fix Released Bug description: [impact] when libseccomp is upgraded to 2.5.1 on all releases, the systemd seccomp unit tests will start failing on ppc, as RestrictAddressFamilies= will no longer work on that arch. However, the systemd.exec man page has stated that RestrictAddressFamiles= doesn't work on ppc since before bionic. [test case] check systemd autopkgtest on ppc, looking at the test_restrict_access_familes unit test [regression potential] any regression would involve the use of RestrictAddressFamilies=, either no longer restricting or incorrectly restricting address familes. [scope] this is needed for b/f/g this was fixed upstream by commit d5923e38bc0e6cf9d7620ed5f1f8606fe7fe1168 which is included in 247, so this is fixed in h already This isn't needed in x, because it doesn't include upstream commit 469830d1426a91e0897c321fdc8ee428f0a750c1 which reworked the code to switch from seccomp_rule_add to seccomp_rule_add_exact, so systemd could handle lack of arch support itself, instead of allowing the 'not exact' seccomp syscall to just ignore the call due to lack of arch support. [other info] libseccomp will be updated to 2.5.1 in the near future so this is needed before that update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696/+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 1918920] Update Released
The verification of the Stable Release Update for apt 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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1918920 Title: Harden test for no new acquires after transaction abort Status in apt package in Ubuntu: Fix Committed Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Released Bug description: [Impact] test-pdiff-usage is somewhat flaky, especially on Debian, this makes it less flaky. No end user impact as it's a test-only change. [Test plan] Running autopkgtest, which runs our extensive integration test suite which includes the changed test. [Where problems could occur] No end user regression potential on its own, but might slightly change regression potential for future pdiff changes: Test approach is slightly different now. It still catches that updates fail correctly, but tests more concretely that a transaction was aborted rather than that no worker received work (which was not guaranteed, the work could be scheduled before it was aborted). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918920/+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 1918920] Re: Harden test for no new acquires after transaction abort
This bug was fixed in the package apt - 2.1.10ubuntu0.3
---
apt (2.1.10ubuntu0.3) groovy; urgency=medium
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
[ Julian Andres Klode ]
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all translations when building the cache (LP: #1907850)
* Do not require force-loopbreak on Protected packages (Closes: #983014)
(LP: #1916725)
* RunScripts: Do not reset SIGQUIT and SIGINT to SIG_DFL (LP: #1898026)
* Protect currently running kernel at run-time (LP: #1615381)
* Make ADDARG{,C}() macros expand to single statements
-- Julian Andres Klode Fri, 12 Mar 2021 09:22:11
+0100
** Changed in: apt (Ubuntu Groovy)
Status: Fix Committed => 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/1918920
Title:
Harden test for no new acquires after transaction abort
Status in apt package in Ubuntu:
Fix Committed
Status in apt source package in Bionic:
Fix Committed
Status in apt source package in Focal:
Fix Committed
Status in apt source package in Groovy:
Fix Released
Bug description:
[Impact]
test-pdiff-usage is somewhat flaky, especially on Debian, this makes it less
flaky. No end user impact as it's a test-only change.
[Test plan]
Running autopkgtest, which runs our extensive integration test suite which
includes the changed test.
[Where problems could occur]
No end user regression potential on its own, but might slightly change
regression potential for future pdiff changes:
Test approach is slightly different now. It still catches that updates
fail correctly, but tests more concretely that a transaction was
aborted rather than that no worker received work (which was not
guaranteed, the work could be scheduled before it was aborted).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918920/+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 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
@rikmills Tested your suggestion in comment #35 and installed with no errors. -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Incomplete Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+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 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device
Uploaded to 20.10 also, there was another SRU done in novembre though, please try to base your changes on the current version, the debdiff didn't apply to that version since it was done on top of the release pocket version instead -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in OEM Priority Project: In Progress Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: In Progress Status in alsa-lib source package in Groovy: In Progress Status in alsa-lib source package in Hirsute: Fix Released Bug description: [Impact] On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Where problems will occur] "Cmedia Audio" is the sound card name of this usb audio dongle, and this string is got from usb string descriptor, that is to say the "Cmedia Audio" is hard-coded in the firmware of that usb dongle. Not all Cmedia usb audio dongle use "Cmedia Audio", most of the dongles don't set string descriptor, then the audio driver sets a generic name "USB Audio Device" for them, if a dongle has string descriptor, it may have different string like "C-Media USB Headphone Set", and all dongles I met before don't have SPDIF interface. So If this SRU could introduce regression, it will happen on a Cmedia usb audio dongle which also hard-codes the "Cmedia Audio" in the string descriptor and it has SPDIF interface on it, after this SRU, users couldn't find the SPDIF playback device from the gnome-sound-setting. But this regression chance is very low since it is very rare a cmedia usb audio dongle uses "Cmedia Audio" in the string descriptor and it is very rare a usb audio dongle has SPDIF interface. So far we haven't met such a cmedia usb audio dongle. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921452/+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 1922786] [NEW] Apt install of local deb files shows a notification causing confusion
Public bug reported: Installation for a local deb file shows a notification message that causes a lot of confusion whether the package has been successfully installed or not. Steps to reproduce = - Download a package file (xxx.deb) - Install the package file from command line "sudo apt install ./xxx.deb" - A notification messages shows up at the end of the installation saying: "Download is performed unsandboxed as root as file '/home/fredli/harddisc/External/Nordic/nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)" -> Expected no notification or warnings if installation finished successfully. It seems that this is only "Notifcation message" BUT it causes a lot of confusion whether the package has been installed or not. The package seems to be installed correctly from what I understand. $ apt --version apt 2.2.2 (amd64) $ lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 Full log: == $ sudo apt install ./nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb Reading package lists... Done Building dependency tree... Done Reading state information... Done Note, selecting 'nrf-command-line-tools' instead of './nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb' The following NEW packages will be installed: nrf-command-line-tools 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. After this operation, 22,6 MB of additional disk space will be used. Get:1 /home/fredli/harddisc/External/Nordic/nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb nrf-command-line-tools amd64 10.12.1 [3 406 kB] Selecting previously unselected package nrf-command-line-tools. (Reading database ... 149444 files and directories currently installed.) Preparing to unpack .../nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb ... Unpacking nrf-command-line-tools (10.12.1) ... Setting up nrf-command-line-tools (10.12.1) ... N: Download is performed unsandboxed as root as file '/home/fredli/harddisc/External/Nordic/nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: hirsute -- 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/1922786 Title: Apt install of local deb files shows a notification causing confusion Status in apt package in Ubuntu: New Bug description: Installation for a local deb file shows a notification message that causes a lot of confusion whether the package has been successfully installed or not. Steps to reproduce = - Download a package file (xxx.deb) - Install the package file from command line "sudo apt install ./xxx.deb" - A notification messages shows up at the end of the installation saying: "Download is performed unsandboxed as root as file '/home/fredli/harddisc/External/Nordic/nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)" -> Expected no notification or warnings if installation finished successfully. It seems that this is only "Notifcation message" BUT it causes a lot of confusion whether the package has been installed or not. The package seems to be installed correctly from what I understand. $ apt --version apt 2.2.2 (amd64) $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 Full log: == $ sudo apt install ./nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb Reading package lists... Done Building dependency tree... Done Reading state information... Done Note, selecting 'nrf-command-line-tools' instead of './nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb' The following NEW packages will be installed: nrf-command-line-tools 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. After this operation, 22,6 MB of additional disk space will be used. Get:1 /home/fredli/harddisc/External/Nordic/nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb nrf-command-line-tools amd64 10.12.1 [3 406 kB] Selecting previously unselected package nrf-command-line-tools. (Reading database ... 149444 files and directories currently installed.) Preparing to unpack .../nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb ... Unpacking nrf-command-line-tools (10.12.1) ... Setting up nrf-command-line-tools (10.12.1) ... N: Download is performed unsandboxed as root as file '/home/fredli/harddisc/External/Nordic/nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) To manage notifications about this bug go to:
[Touch-packages] [Bug 1922792] [NEW] Bluez should notify users when they need to reboot to apply changes
Public bug reported: In the case of upgrading bluez on certain raspberry pi devices, a reboot may be required to apply the changes. We should add a check for this scenario in the postinst script. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1922792 Title: Bluez should notify users when they need to reboot to apply changes Status in bluez package in Ubuntu: New Bug description: In the case of upgrading bluez on certain raspberry pi devices, a reboot may be required to apply the changes. We should add a check for this scenario in the postinst script. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1922792/+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
Re: [Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
On 06/04/2021 17:35, Timo Aaltonen wrote: > I've tried to bisect mesa to see where it regressed, but turns out that > an older git snapshot (~20.3.0) crashes just like with 21.0, so looks > like this is caused by something else like the toolchain instead? The rebuild of 20.3.4 here does not crash in my tests. https://launchpad.net/~rikmills/+archive/ubuntu/mesa Not the version is bumped to make upgrading on a system easier, but it is a rebuild of 20.3.4 against the same toolchain crashy 21.0.x were done with. Please try those -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Incomplete Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to:
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
I've tried to bisect mesa to see where it regressed, but turns out that an older git snapshot (~20.3.0) crashes just like with 21.0, so looks like this is caused by something else like the toolchain instead? -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Incomplete Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+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 1915502] Re: "systemd --user" fails to start for non-local users
To confirm, this is not a duplicate of bug 1916235. I see none of the
associated errors in the logs and the workaround is ineffective.
--
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/1915502
Title:
"systemd --user" fails to start for non-local users
Status in systemd package in Ubuntu:
Incomplete
Status in systemd source package in Focal:
New
Bug description:
systemd-logind fails to start the systemd --user process for non-local
users on Ubuntu 20.04. This is a reproducible problem; all our
systems are displaying the same symptoms.
The systems are using Kerberos (Active Directory) for authentication,
and NIS for account meta-data and authorisation (groups)
A base installation is performed using the server 20.04 ISO image. No
additional packages are selected. Post-install, I run:
apt-get install tcsh nis krb5-user libpam-krb5 libnss-systemd
I set up the NIS client (supply the default domain name, check ypbind
is running and ypcat passwd is working)
I then set up /etc/krb5.conf for kerberos authentication to a domain
controller, confirm that kinit works and a kerberos ticket is issued.
I modify /etc/passwd, /etc/group and /etc/shadow, appending a "+" to
the end of each.
/etc/nsswitch.conf is modified to support compat mode, as well as
systemd:
passwd: compat systemd
group: compat systemd
shadow: compat
I can log in remotely via ssh using my NIS account and Kerberos
credentials. MY NIS meta-data looks like:
amcvey:KRB5:::Andy McVey:/home/amcvey:/bin/tcsh
(where UID and GID are replaced with values unique to the
organisation)
On login, the following occurs:
hostname:~> systemctl --user
Failed to connect to bus: No such file or directory
I put pam-systemd and systemd-logind into debug mode to get more
information:
Feb 12 09:51:32 myhostname sshd[1210]: Accepted publickey for amcvey from
[redact] port 58849 ssh2: RSA SHA256:[redact]
Feb 12 09:51:32 myhostname sshd[1210]: pam_unix(sshd:session): session opened
for user amcvey by (uid=0)
Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_call
sender=:1.13 destination=org.freedesktop.login1 path=/org/freedesktop/login1
interface=org.freedesktop.login1.Manager member=CreateSession cookie=2
reply_cookie=0 signature=uusussbssa(sv) error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): pam-systemd
initializing
Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus
interface=org.freedesktop.DBus member=GetConnectionUnixUser cookie=40
reply_cookie=0 signature=s error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Asking
logind to create session: uid=198083 pid=1210 service=sshd type=tty class=user
desktop= seat= vtnr=0 tty= display= remote=yes remote_user=
remote_host=10.105.121.110
Feb 12 09:51:32 myhostname systemd-logind[903]: Got message
type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a
interface=n/a member=n/a cookie=13 reply_cookie=40 signature=u error-name=n/a
error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Session
limits: memory_max=n/a tasks_max=n/a cpu_weight=n/a io_weight=n/a
runtime_max_sec=n/a
Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus
interface=org.freedesktop.DBus member=GetConnectionUnixProcessID cookie=41
reply_cookie=0 signature=s error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Failed to
create session: No such process
Feb 12 09:51:32 myhostname systemd-logind[903]: Got message
type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a
interface=n/a member=n/a cookie=14 reply_cookie=41 signature=u error-name=n/a
error-message=n/a
Feb 12 09:51:32 myhostname systemd-logind[903]: Unable to connect to
/run/systemd/userdb/io.systemd.Multiplexer: No such file or directory
Feb 12 09:51:32 myhostname systemd-logind[903]: n/a: varlink: setting state
idle-client
Feb 12 09:51:32 myhostname systemd-logind[903]:
/run/systemd/userdb/io.systemd.DynamicUser: Sending message:
{"method":"io.systemd.UserDatabase.GetUserRecord","parameters":{"uid":198083,"service":"io.systemd.DynamicUser"}}
Feb 12 09:51:32 myhostname systemd-logind[903]:
/run/systemd/userdb/io.systemd.DynamicUser: varlink: changing state idle-client
→ awaiting-reply
Feb 12 09:51:32 myhostname systemd-logind[903]:
/run/systemd/userdb/io.systemd.DynamicUser: New incoming message:
{"error":"io.systemd.UserDatabase.NoRecordFound","parameters":{}}
Feb 12 09:51:32 myhostname
[Touch-packages] [Bug 1922766] Re: UP and DOWN keys behave erratically
I forgot to mention: the problem will happen with any app. It's happened using Terminal, various IDE's, various text editors, various browsers, libre office... it makes you realise how often you use the arrow keys! -- 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/1922766 Title: UP and DOWN keys behave erratically Status in xorg package in Ubuntu: New Bug description: Since the last update, a couple of days ago the UP and DOWN arrow keys don't work properly. They are either slow to react or don't work at all, very occasionally they work as expected. It is only limited to these two keys. I don't think it is a hardware issue because if I boot my laptop up with another operating system it works fine. I checked to see if my bios needs updating, but it doesn't. Also I have tried starting with an older kernel and the problem is still there so I think this has something to do with xorg and/or gnome. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 6 17:22:59 2021 DistUpgraded: 2020-09-19 18:59:22,820 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] [1043:1280] InstallationDate: Installed on 2016-11-03 (1614 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX310UA ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=eee950f6-e946-46ab-9616-45ba24e1f588 ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-09-19 (198 days ago) dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX310UA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX310UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX310UA.305:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX310UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX310UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX310UA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Sep 21 17:29:50 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.4 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1922766/+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 1922766] [NEW] UP and DOWN keys behave erratically
Public bug reported: Since the last update, a couple of days ago the UP and DOWN arrow keys don't work properly. They are either slow to react or don't work at all, very occasionally they work as expected. It is only limited to these two keys. I don't think it is a hardware issue because if I boot my laptop up with another operating system it works fine. I checked to see if my bios needs updating, but it doesn't. Also I have tried starting with an older kernel and the problem is still there so I think this has something to do with xorg and/or gnome. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 6 17:22:59 2021 DistUpgraded: 2020-09-19 18:59:22,820 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] [1043:1280] InstallationDate: Installed on 2016-11-03 (1614 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX310UA ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=eee950f6-e946-46ab-9616-45ba24e1f588 ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-09-19 (198 days ago) dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX310UA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX310UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX310UA.305:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX310UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX310UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX310UA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Sep 21 17:29:50 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.4 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- 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/1922766 Title: UP and DOWN keys behave erratically Status in xorg package in Ubuntu: New Bug description: Since the last update, a couple of days ago the UP and DOWN arrow keys don't work properly. They are either slow to react or don't work at all, very occasionally they work as expected. It is only limited to these two keys. I don't think it is a hardware issue because if I boot my laptop up with another operating system it works fine. I checked to see if my bios needs updating, but it doesn't. Also I have tried starting with an older kernel and the problem is still there so I think this has something to do with xorg and/or gnome. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 6 17:22:59 2021 DistUpgraded:
[Touch-packages] [Bug 1821415] Re: pkexec fails in a non-graphical environment
I don't think we would want to carry the proposed patch as a distro patch. So as long as polkit doesn't have direct support for this, apport should do as systemd does, and spawn pkttyagent (--fallback) itself. I'll try quickly now to work on an initial patch for this. ** Changed in: policykit-1 (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1821415 Title: pkexec fails in a non-graphical environment Status in PolicyKit: New Status in apport package in Ubuntu: Triaged Status in policykit-1 package in Ubuntu: Won't Fix Bug description: The plymouth apport source package hooks wants to gather log files as the root user and apport provides a policy kit policy for collecting that information. This works fine in a graphical environment but not in a non-graphical one. N.B. you first need to create a /var/log/plymouth-debug.log file for the plymouth apport package hook to actually trigger this. ubuntu@disco:~$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. Subsequently, bug reports from servers will contain less information. To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1821415/+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 1920837] Re: apport bugs from official raspi or riscv images are not identified
The most reliable means I know of at the moment for detecting Raspberry
Pi hardware at runtime is to query the device-tree.
For example, flash-kernel determines the type of board it is running on,
by matching the content of /proc/device-tree/model (e.g. "Raspberry Pi
400 Rev 1.0") against a pre-determined list of strings in its database.
Personally I don't much like matching fixed strings -- new board
revisions frequently come out and then f-k needs patching to add them,
but last cycle I did add the ability to match the "Raspberry Pi *" glob
as an attempt to support new boards even if they come out mid-cycle.
Something similar could be accomplished with some Python like so:
try:
with open('/proc/device-tree/model', 'r', encoding='ascii') as f:
is_a_pi = f.read().startswith('Raspberry Pi ')
except FileNotFoundError:
is_a_pi = False
That seems to work reliably (even on compute modules where the model is
"Raspberry Pi Compute Module 4 Rev 1.0"), but I've no idea if the /proc
/device-tree/model file *always* exists or whether other boards publish
useful information in there.
Another possibility is to look at /proc/device-tree/compatible which I
*think* should always exist assuming a device-tree is in use on the
system. This is a binary file containing a sequence of NUL-terminated
strings, each of which is of the form "vendor,model" and is intended for
kernel driver matching. For example, on the Pi 400 it contains:
raspberrypi,400\0brcm,bcm2711\0
(where \0 is the NUL character). And on a 3B+ contains:
raspberrypi,3-model-b-plus\0brcm,bcm2837\0
My understanding is there's no strict requirement that these strings
appear in any particular order so simple prefix matching is potentially
unreliable. However, it's trivial enough to parse and extract the
"raspberrypi" vendor from this with some Python like:
try:
with open('/proc/device-tree/compatible', 'rb') as f:
is_a_pi = any(vendor == 'raspberrypi'
for s in f.read().split(b'\0') if s
for vendor, model in (s.decode('ascii').split(',', 1),))
except FileNotFoundError:
is_a_pi = False
Something similar *should* be reasonably useful with just about any
board that uses a device tree (but obviously PCs don't have device-trees
so we still need the file-not-found check).
--
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/1920837
Title:
apport bugs from official raspi or riscv images are not identified
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Focal:
In Progress
Status in apport source package in Groovy:
In Progress
Bug description:
It would be helpful if bugs reported from images for Raspberry Pi's or
RISCV systems were tagged so that one could search for bugs from
systems running those images e.g. 'raspi-image'.
[Test Case]
After installing a preinstalled image of Ubuntu for Raspberry Pi do the
following:
1) run 'ubuntu-bug apport'
2) view the bug report and check the Tags field
With the current version of apport you will not see the tag 'raspi-image'.
With the version of apport in -proposed you will see the tag 'raspi-image'.
[Where problems could occur]
If the code being added is syntactically incorrect then we'd see a Traceback
which would be bad as it could affect all bug / crash reports.
[Other Info]
Since there aren't any Groovy images for RISC-V there will be nothing to test
there.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1920837/+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 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths
The problem exists with the AMD graphics drivers and using Xpresent. Window managers can work around it by not using Xpresent, but there's also a kernel fix available. https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/10 https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/merge_requests/52 https://gitlab.xfce.org/xfce/xfwm4/-/commit/7c00911a556c27c57c9f719c12cfda967016dc28 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1873895 Title: Regression: block staircase display with side-by-side monitors of different pixel widths Status in Linux: Unknown Status in libxcb package in Ubuntu: Incomplete Status in xfwm4 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Status in libxcb source package in Focal: Incomplete Status in xfwm4 source package in Focal: In Progress Status in xserver-xorg-video-amdgpu source package in Focal: Incomplete Status in libxcb source package in Groovy: Incomplete Status in xfwm4 source package in Groovy: Fix Released Status in xserver-xorg-video-amdgpu source package in Groovy: Incomplete Bug description: [Impact] * This issue affects AMD graphics on Xfwm4 4.14.1. * Windows are displayed staggered with a multi-window layout [Test Plan] * Use AMD graphics drivers * Connect a second display at a different resolution * Open multiple windows * While the issue is present, the windows and desktop will appeared staggered * Once fixed, they display normally. [Where problems could occur] * Regression potential should be relatively low, as the release between 4.14.1 and 4.14.5 are bug releases. * With window managers, some changes could lead to different behavior and other broken displays. Non-AMD graphics users should also test for regressions. [Other Info] * Please see the Xfwm4 release notes for changes between 4.14.1 and 4.14.5: https://gitlab.xfce.org/xfce/xfwm4/-/blob/xfce-4.14/NEWS#L7-44 [Original Report] Update based on further research. This only happens when the secondary external display is operating at a different pixel width to the internal. In this case eDP is 1920x1080 whereas the external HDMI-A-0 is natively 1680x1050. It is caused by xfwm4's recent switch from using glx to xpresent for AMD GPUs. The underlying bug is in the AMD driver. I was able to reproduce on an external 1920x1200 display only when it was set to a non-native 1680x1050 resolution. --- Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred initially on the laptop that is having package upgrades applied regularly. With dual monitors and the external monitor placed left or right the display has a blocked staircase effect shown in the attached photograph, and seems related to https://gitlab.freedesktop.org/xorg/driver/xf86-video- amdgpu/-/issues/10 More detailed investigation suggests it only happens when the X coordinate of the two monitors is different. The symptom looks like an off-by-one error because it appears as if the display is divided into, say, 10 rows and 15 columns but the first row has 16 'columns' worth of blocks on it and so wraps to the beginning of the 2nd row, and so on. On the laptop without package upgrades being applied this didn't happen. So I upgraded it (314 packages) and restarted and it too sees the same problem. I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but that didn't solve it. I now suspect libxcb but so far haven't been able to prove it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) MachineType: LENOVO 20NECTO1WW Package: xserver-xorg-video-amdgpu 19.1.0-1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: LENOVO
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
assigning to timo for better tracking ** Changed in: mesa (Ubuntu Hirsute) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: ubiquity (Ubuntu Hirsute) Status: Confirmed => Incomplete -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Incomplete Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+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 1922548] Re: Error accessing Home of another user [Oops! Something went wrong. Unhandled error message: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Unix process subject
Problem is described in: https://gitlab.freedesktop.org/polkit/polkit/-/issues/136 to try: corrado@corrado-n2-hh-0402:~$ gedit admin:///home (gedit:12489): GVFS-WARNING **: 17:49:21.210: The peer-to-peer connection failed: Could not connect: Permission denied. Falling back to the session bus. Your application is probably missing --filesystem=xdg- run/gvfsd privileges. ** (gedit:12489): WARNING **: 17:49:21.219: Hit unhandled case 36 (GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Unix process subject does not have uid set) in parse_error. corrado@corrado-n2-hh-0402:~$ Could not open the file “admin:///home”. Unexpected error: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Unix process subject does not have uid set ** Bug watch added: gitlab.freedesktop.org/polkit/polkit/-/issues #136 https://gitlab.freedesktop.org/polkit/polkit/-/issues/136 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1922548 Title: Error accessing Home of another user [Oops! Something went wrong. Unhandled error message: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Unix process subject does not have uid set] Status in nautilus package in Ubuntu: New Status in policykit-1 package in Ubuntu: New Bug description: On my PC I have some different users. If from one user I try to access the Home directory of a different user I enter the password and then I have a crash. Seen attached screenshot. Problem happens with both x11 and Wayland sessions. More: opening this bug I have the messages: corrado@corrado-n2-hh-0402:~$ ubuntu-bug -w ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 227, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 945, in attach_casper_md5check with open(location) as json_file: PermissionError: [Errno 13] Permission denied: '/var/log/installer/casper-md5check.json' corrado@corrado-n2-hh-0402:~$ [GFX1-]: glxtest: Could not connect to wayland socket ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 5 12:05:27 2021 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1137, 611)' InstallationDate: Installed on 2021-04-02 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210402) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.39.2-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1922548/+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 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths
This came up on our tracking report for the desktop team, but we're not clear what is required in libxcb/amdgpu vs. a fix in the WMs themselves. Can someone clarify please? ** Changed in: libxcb (Ubuntu) Status: Confirmed => Incomplete ** Changed in: libxcb (Ubuntu Focal) Status: New => Incomplete ** Changed in: libxcb (Ubuntu Groovy) Status: New => Incomplete ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Confirmed => Incomplete ** Changed in: xserver-xorg-video-amdgpu (Ubuntu Focal) Status: New => Incomplete ** Changed in: xserver-xorg-video-amdgpu (Ubuntu Groovy) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1873895 Title: Regression: block staircase display with side-by-side monitors of different pixel widths Status in Linux: Unknown Status in libxcb package in Ubuntu: Incomplete Status in xfwm4 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Status in libxcb source package in Focal: Incomplete Status in xfwm4 source package in Focal: In Progress Status in xserver-xorg-video-amdgpu source package in Focal: Incomplete Status in libxcb source package in Groovy: Incomplete Status in xfwm4 source package in Groovy: Fix Released Status in xserver-xorg-video-amdgpu source package in Groovy: Incomplete Bug description: [Impact] * This issue affects AMD graphics on Xfwm4 4.14.1. * Windows are displayed staggered with a multi-window layout [Test Plan] * Use AMD graphics drivers * Connect a second display at a different resolution * Open multiple windows * While the issue is present, the windows and desktop will appeared staggered * Once fixed, they display normally. [Where problems could occur] * Regression potential should be relatively low, as the release between 4.14.1 and 4.14.5 are bug releases. * With window managers, some changes could lead to different behavior and other broken displays. Non-AMD graphics users should also test for regressions. [Other Info] * Please see the Xfwm4 release notes for changes between 4.14.1 and 4.14.5: https://gitlab.xfce.org/xfce/xfwm4/-/blob/xfce-4.14/NEWS#L7-44 [Original Report] Update based on further research. This only happens when the secondary external display is operating at a different pixel width to the internal. In this case eDP is 1920x1080 whereas the external HDMI-A-0 is natively 1680x1050. It is caused by xfwm4's recent switch from using glx to xpresent for AMD GPUs. The underlying bug is in the AMD driver. I was able to reproduce on an external 1920x1200 display only when it was set to a non-native 1680x1050 resolution. --- Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred initially on the laptop that is having package upgrades applied regularly. With dual monitors and the external monitor placed left or right the display has a blocked staircase effect shown in the attached photograph, and seems related to https://gitlab.freedesktop.org/xorg/driver/xf86-video- amdgpu/-/issues/10 More detailed investigation suggests it only happens when the X coordinate of the two monitors is different. The symptom looks like an off-by-one error because it appears as if the display is divided into, say, 10 rows and 15 columns but the first row has 16 'columns' worth of blocks on it and so wraps to the beginning of the 2nd row, and so on. On the laptop without package upgrades being applied this didn't happen. So I upgraded it (314 packages) and restarted and it too sees the same problem. I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but that didn't solve it. I now suspect libxcb but so far haven't been able to prove it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) MachineType: LENOVO 20NECTO1WW Package: xserver-xorg-video-amdgpu 19.1.0-1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu ubuntu Uname: Linux
[Touch-packages] [Bug 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)
It is possible that you have the key in _two_ keyrings in trusted.gpg.d/ & in trusted.gpg itself. It would be best for you to do the following: 1) sudo apt remove --purge ubuntu-dbgsym-keyring 2) sudo apt-key del 0xC8CAB6595FDFF622 3) sudo apt-key list | grep C8CAB6595FDFF622 => it should be empty now 4) sudo apt install ubuntu-dbgsym-keyring -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1920640 Title: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Status in ubuntu-keyring package in Ubuntu: Fix Released Status in ubuntu-keyring source package in Bionic: Fix Released Status in ubuntu-keyring source package in Focal: Fix Released Status in ubuntu-keyring source package in Groovy: Fix Released Status in ubuntu-keyring source package in Hirsute: Fix Released Bug description: [Impact] * Cannot update apt metadata from ddebs.ubuntu.com whilst using ubuntu-dbgsym-keyring package [Test Plan] * Install ubuntu-dbgsym-keyring package * Add ddebs.ubuntu.com repository for your release * sudo apt update must be successful * Install ubuntu-dbgsym-keyring package * Install and use `apt-key list` and check that there is no expiry on the dbgsym key I.e. bad output /etc/apt/trusted.gpg.d/ubuntu-keyring-2016-dbgsym.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2ED C64D C5AE E1F6 B9C6 21F0 C8CA B659 5FDF F622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Good output has no [date] in the pub line. [Where problems could occur] * At the moment the signature was bumped by one year * Meaning this issue will occur again in 2022 * Instead the key must be set to not expire & new round of SRUs issued [Other Info] * Original bug report The public key used by the debugging symbols repository /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu- dbgsym-keyring expired. $ apt policy ubuntu-dbgsym-keyring ubuntu-dbgsym-keyring: Installed: 2020.02.11.2 Candidate: 2020.02.11.2 Version table: *** 2020.02.11.2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status $ gpg --no-default-keyring --keyring /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Error message on "apt update": E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+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
