[Touch-packages] [Bug 1997093] Re: bash 5.2 regression too-aggressive optimizing of forks in an `eval' command inside a (command) subshell
This bug was fixed in the package ovn - 22.12.0-4 --- ovn (22.12.0-4) unstable; urgency=medium * Extend list of tests to skip (LP: #2002475, LP: #2002476, LP: #2002477). -- Frode Nordahl Wed, 11 Jan 2023 09:23:01 +0100 ** Changed in: ovn (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1997093 Title: bash 5.2 regression too-aggressive optimizing of forks in an `eval' command inside a (command) subshell Status in bash package in Ubuntu: Fix Committed Status in ovn package in Ubuntu: Fix Released Bug description: OVN makes use of GNU autotest for its testsuite. This in turn is a heavy user of bash. For some reason, when the 'ovn-controller incremental processing' test is executed using bash 5.2 on Debian experimental or Ubuntu Kinetic/Lunar, the `eval` [0] in the `counter_delta_` function misinterprets successful execution of commands [1], leading to a false negative for the 'ovn-controller incremental processing' test [2]. Backporting the bash 5.1 package from Jammy, or compiling bash 5.1 from upstream sources and rerunning the test makes it succeed. This does come across as a regression in bash. 0: https://github.com/ovn-org/ovn/blob/a042aa23e79a0d36f1ce7b0ccfcf0a5995b045cd/tests/ovn-performance.at#L116 1: https://github.com/ovn-org/ovn/blob/a042aa23e79a0d36f1ce7b0ccfcf0a5995b045cd/tests/ovn-performance.at#L479 2: https://github.com/ovn-org/ovn/blob/a042aa23e79a0d36f1ce7b0ccfcf0a5995b045cd/tests/ovn-performance.at#L227 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1997093/+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 1307883] Re: ca-certificates-java misses runtime dependency on initscripts
Probably still relevant, needs validation -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1307883 Title: ca-certificates-java misses runtime dependency on initscripts Status in ca-certificates-java package in Ubuntu: Confirmed Status in openjdk-7 package in Ubuntu: Confirmed Status in openjdk-8 package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Triaged Bug description: Jitsi build-depends on openjdk-7-jre but the package fails to install in pbuilder and thus I currently cannot build the package. Here is the output I get while I am logged in to the trusty chroot. # aptitude install default-jdk [...] E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up ca-certificates-java (20130815ubuntu1) ... /var/lib/dpkg/info/ca-certificates-java.postinst: line 90: mountpoint: command not found the keytool command requires a mounted proc fs (/proc). dpkg: error processing package ca-certificates-java (--configure): subprocess installed post-installation script returned error exit status 1 Setting up openjdk-7-jre-headless:i386 (7u51-2.4.6-1ubuntu4) ... /var/lib/dpkg/info/openjdk-7-jre-headless:i386.postinst: 18: /var/lib/dpkg/info/openjdk-7-jre-headless:i386.postinst: mountpoint: not found the java command requires a mounted proc fs (/proc). dpkg: error processing package openjdk-7-jre-headless:i386 (--configure): subprocess installed post-installation script returned error exit status 1 Setting up default-jre-headless (2:1.7-51) ... dpkg: dependency problems prevent configuration of openjdk-7-jre:i386: openjdk-7-jre:i386 depends on openjdk-7-jre-headless (= 7u51-2.4.6-1ubuntu4); however: Package openjdk-7-jre-headless:i386 is not configured yet. dpkg: error processing package openjdk-7-jre:i386 (--configure): dependency problems - leaving unconfigured Setting up default-jre (2:1.7-51) ... dpkg: dependency problems prevent configuration of openjdk-7-jdk:i386: openjdk-7-jdk:i386 depends on openjdk-7-jre (= 7u51-2.4.6-1ubuntu4); however: Package openjdk-7-jre:i386 is not configured yet. dpkg: error processing package openjdk-7-jdk:i386 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of default-jdk: default-jdk depends on openjdk-7-jdk (>= 7~u3-2.1.1); however: Package openjdk-7-jdk:i386 is not configured yet. dpkg: error processing package default-jdk (--configure): dependency problems - leaving unconfigured Processing triggers for ca-certificates (20130906ubuntu2) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d /etc/ca-certificates/update.d/jks-keystore: 33: /etc/ca-certificates/update.d/jks-keystore: mountpoint: not found the keytool command requires a mounted proc fs (/proc). E: /etc/ca-certificates/update.d/jks-keystore exited with code 1. done. Errors were encountered while processing: ca-certificates-java openjdk-7-jre-headless:i386 openjdk-7-jre:i386 openjdk-7-jdk:i386 default-jdk # mount /proc on /proc type proc (rw,relatime) tmpfs on /run/shm type tmpfs (rw,relatime) /dev/pts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1307883/+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 2002558] Re: The ethernet connection icon has disappeared
Can you attach a screenshot or photo of the problem? ** Summary changed: - erro Icon connection + The ethernet connection icon has disappeared ** 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/2002558 Title: The ethernet connection icon has disappeared Status in gnome-shell package in Ubuntu: Incomplete Bug description: The ethernet connection icon has disappeared, it's a cosmetic problem, I can access the internet both via cable, WI-FI and VPN, I would like to report this error, as I still haven't found a solution to the problem on the internet. In settings, it also disappeared, only the VPN settings are still visible. (I used google translator, if possible answer me in Portuguese.) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Wed Jan 11 13:53:57 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6290] [1002:9807] (prog-if 00 [VGA controller]) Subsystem: Lenovo Wrestler [Radeon HD 6290] [17aa:397f] InstallationDate: Installed on 2022-07-29 (166 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20136 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=c7305ad4-8faf-45a3-8420-afbb79aaf181 ro net.ifnames=0 biosdevname=0 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/02/2012 dmi.bios.release: 0.93 dmi.bios.vendor: LENOVO dmi.bios.version: 6CCN93WW(V8.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo G485 dmi.board.vendor: LENOVO dmi.board.version: 3194WIN8 STD SGL dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G485 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnLENOVO:bvr6CCN93WW(V8.05):bd10/02/2012:br0.93:efr0.0:svnLENOVO:pn20136:pvrLenovoG485:rvnLENOVO:rnLenovoG485:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoG485:skuLENOVO_MT_20136: dmi.product.family: IDEAPAD dmi.product.name: 20136 dmi.product.sku: LENOVO_MT_20136 dmi.product.version: Lenovo G485 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2002558/+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 1988859] Re: Periodic black frames and stutter [Failed to post KMS update: drmModeAddFB does not support format 'AR24' (0x34325241)]
Workaround committed to mutter for the next lunar update, whenever that may be. https://salsa.debian.org/gnome-team/mutter/-/commit/d615363fa9 ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-in-mesa-22.3.3 fixed-upstream -- 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/1988859 Title: Periodic black frames and stutter [Failed to post KMS update: drmModeAddFB does not support format 'AR24' (0x34325241)] Status in Mesa: New Status in Mutter: New Status in mesa package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Committed Bug description: Every so often, the desktop will go black and then re appear on Ubuntu 22.10 Wayland Session which should not be occurring (this does not happen on 22.04.) Note that only the cursor can be seen. Reporting this before release so that it can be patched for (at least) the RasPi. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-1001.3-raspi 5.19.0-rc8 Uname: Linux 5.19.0-1001-raspi aarch64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.23.0-0ubuntu1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 6 16:10:37 2022 DisplayManager: gdm3 ImageMediaBuild: 20220826 RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1988859/+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 1983794] Re: Evolution not deleting autosave files
This bug was fixed in the package libcanberra - 0.30-10ubuntu2
---
libcanberra (0.30-10ubuntu2) lunar; urgency=medium
* d/p/gtk-module-Handle-display-closing-gracefully: Do not leak objects on
destruction.
As per previous fix for LP: #1949200 we were leaking Gtk Widgets when they
were manually destroyed, because we never released the reference that we
added previously.
Thanks to Alberts Muktupāvels for providing the test case and some analysis.
(LP: #1983794)
-- Marco Trevisan (Treviño) Tue, 10 Jan 2023
12:59:22 +0100
** Changed in: libcanberra (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Fix Released
Status in libcanberra source package in Jammy:
In Progress
Status in evolution source package in Kinetic:
New
Status in libcanberra source package in Kinetic:
In Progress
Bug description:
[ Impact ]
Autosave files are not removed from evolution local state directories
(and windows leaked)
[ Test case ]
1. Open evolution, and start to compose a new email
2. Write enough text and wait few minutes so that this command returns a file
ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
3. Close the email composer window, hitting "Do not save"
4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
5. Opening and closing again evolution should not ask to restore the previous
email
[ Regression potential ]
No sounds could be performed during some UI actions
---
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 1965518] Re: [USB-Audio - USB Audio, recording] Recording problem
This is most likely related to USB IDs having to be added to ALSA UCM2 configuration. The specific commit for MSI Z690 Edge WiFi (USB ID 0db0:1feb) is https://github.com/alsa-project/alsa-ucm- conf/commit/c9c7559425a1b67a18700367fc54f75046a724f8 On Ubuntu 22.04 (and with an ASUS ALC4080 mainboard having the same symptoms) downloading and installing the latest UCM2 release failed as from version 1.2.7 "Syntax 6" is in use (https://alsa- project.org/wiki/Changes_v1.2.6.3_v1.2.7) which is not supported by the ALSA libraries supplied with Ubuntu 22.04. I had to add the section into the distribution-supplied USB-Audio.conf file manually, microphone is working for me now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1965518 Title: [USB-Audio - USB Audio, recording] Recording problem Status in alsa-driver package in Ubuntu: Confirmed Bug description: Microphone when using built in mbo MSI Z690 Edge WiFi DDR4 audio Realtek ALC4080 is not recording audio. What I did found out, that the bar which indicates that something is recording is going up, when I play some sound on ubuntu, so input "thinks" it is output I think. If raport is somehow saying I was not using that mic at the moment, that is because I was using other card which I need to buy, for mic to temporarly work. I rechecked it before sending report, and yes, that original from MBO audio input is still not working. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity Date: Fri Mar 18 10:39:26 2022 InstallationDate: Installed on 2022-03-12 (5 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Audio failed Symptom_Card: USB Audio - USB Audio Symptom_Type: None of the above Title: [USB-Audio - USB Audio, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2021 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.10 dmi.board.asset.tag: Default string dmi.board.name: MPG Z690 EDGE WIFI DDR4 (MS-7D31) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.10:bd12/13/2021:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D31:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ690EDGEWIFIDDR4(MS-7D31):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D31 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1965518/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2
Hi Fabio Martins,
Thanks for looking into this issue. Attached tar file contains setup.py and
steps to reproduce the issue. In general, the behavior is same with any package
building with extensions.
** Attachment added: "testprog.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+attachment/5640852/+files/testprog.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
New
Bug description:
Compiling a Python extension using Python2 (Python 2.7.18) is making
use of wrong compiler flags, hence dropping required optimizations
when required. This is happening only when python2 is installed from
Ubuntu's repositories. By default, Python's distutils module uses
compiler and linker flags used to compile Python itself to be used to
compile extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
On further investigation, it looks like Ubuntu's specific patch applied on
libpython2.7-stdlib package is altering the original upstream implementation of
distutils/sysconfig.py code.
Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
Patch -
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
Below is the code block which is causing the issue, where the presence of
configure_cflags is modifying cflags. This code is result of ubuntu's patch and
doesn't come directly from upstream python implementation.
File - /usr/lib/python2.7/distutils/sysconfig.py
Part of code block:
elif configure_cflags:
cflags = ' '.join(str(x) for x in (basecflags, configure_cflags,
extra_cflags) if x)
ldshared = ldshared + ' ' + configure_cflags
I don't see problem on Python3 though we have extra code added from patch
there as well. Patch used on python3, is not modifying the cflags completely
and instead appending new flags to cflags.
On python3 (tested on Ubuntu 20.04)
File - /usr/lib/python3.8/distutils/sysconfig.py
Part of code block which doesn't alter cflags completely
elif configure_cflags:
cflags = cflags + ' ' + configure_cflags
ldshared = ldshared + ' ' + configure_cflags
Request to update the python2 patch to behave similar to what is been done on
python3.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1998970] Re: Remove pypy from lunar
pypy removed 30Dec: (From Debian) RoQA; py2 leftover; no rdeps; Debian bug #937511 ** Changed in: pypy (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-setuptools in Ubuntu. https://bugs.launchpad.net/bugs/1998970 Title: Remove pypy from lunar Status in pypy package in Ubuntu: Fix Released Status in python-ipaddress package in Ubuntu: Fix Released Status in python-setuptools package in Ubuntu: Fix Released Status in rawkit package in Ubuntu: Fix Released Bug description: pypy is an alternative implementation of Python2 and was very recently removed from Debian. (There is now a pypy3 source package instead.) We need to remove pypy from Ubuntu Lunar because its autopkgtest failure is blocking the migration of several packages. However, someone will need to work through these reverse dependencies: $ reverse-depends -b -r lunar src:pypy Reverse-Build-Depends * pypy (for pypy) * python-ipaddress (for pypy) * python-setuptools (for pypy) * rawkit(for pypy) Resolved Reverse-Build-Depends: * python-cheroot >= 9.0.0+ds1-2 Resolved Reverse-Testsuite-Triggers: * python-virtualenv >= 20.16.3+ds-4.1 * dh-python >= 5.20221205 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pypy/+bug/1998970/+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 1998265] Re: OverFlow error when using cnf-extractor
Since the SRU team -approved Test Plan was to rely on autopkgtest, and autopkgtests are showing all passed, we can consider this bug verified for those releases. ** Tags removed: verification-needed verification-needed-focal verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done verification-done-focal verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1998265 Title: OverFlow error when using cnf-extractor Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Bionic: Fix Released Status in python-apt source package in Focal: Fix Committed Status in python-apt source package in Jammy: Fix Committed Status in python-apt source package in Kinetic: Fix Committed Bug description: [Impact] Large files can't be downloaded as we use a 32-bit integer in AcquireFile constructor, this breaks e.g. command-not-found generator: I'm trying to update the command-not-found indexes (bin/cnf-extract.py $MIRROR $suite $component $arch) on the production cnf extractor system (running bionic) and have encountered Tracebacks when generating them for Jammy and Lunar. This is causing the command not found indexes to be out of date for all(?) releases of Ubuntu. The lunar failure: Get:1 dotnet-sdk-6.0_6.0.111-0ubuntu3_amd64.deb [79.1 MB] Fetched 79.1 MB in 0s (0 B/s) Traceback (most recent call last):64... 7% File "./bin/cnf-extract.py", line 54, in mirror_root, suite, component, arch) File "/srv/cnf-extractor/extractor/extractor.py", line 174, in command_not_found_extract debpath = pkg.candidate.fetch_binary(destdir=tmpdir) File "/usr/lib/python3/dist-packages/apt/package.py", line 883, in fetch_binary self.size, base, destfile=destfile) OverflowError: signed integer is greater than maximum I'll get more context for the Jammy failure but it wouldn't surprise me if it was the same package. [Test plan] I have included a test for the AcquireFile constructor to accept a large file size, and then a test that ensures it can read the file size. Run the autopkgtest suite. [Where problems could occur] It could fail in other places now. For kinetic, the package was copied in from lunar without changes. This upload is actually built in kinetic and hence there is additional regression potential from toolchain changes. [Other info] Also including some auxiliary changes as we move back to proper upstream releases to enable testing, mostly around d/gbp.conf, .gitlab-ci.yml - being updated to point at right places d/t/control - adding a missing test dependency data/ - updated mirror lists The mirror lists are standard updates; the debian/tests/control change is needed to enable testing on more minimal autopkgtest images (our images accidentally include binutils); the other changes have zero impact on the Ubuntu infra or end user side as they only run during development. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1998265/+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 1998488] Re: Wrong type annotation in apt.progress.text.AcquireProgress
Since the SRU team -approved Test Plan was to rely on autopkgtest, and autopkgtests are showing all passed, we can consider this bug verified for those releases. ** Tags removed: verification-needed verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1998488 Title: Wrong type annotation in apt.progress.text.AcquireProgress Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Jammy: Fix Committed Status in python-apt source package in Kinetic: Fix Committed Status in python-apt source package in Lunar: Fix Released Bug description: [Impact] Type checking fails in CI [Test plan] Have CI type check successfully [Where problems could occur] It's only a comment *inside* the function, so not really anywhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1998488/+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 1961800] Re: Seeing out of memory errors after libexpat1 upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal)
And fixed in bionic expat 2.2.5-3ubuntu0.9 ** Also affects: expat (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: python-xmltodict (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: expat (Ubuntu Bionic) Status: New => Fix Released ** Changed in: python-xmltodict (Ubuntu Bionic) Status: New => Invalid ** Changed in: python-xmltodict (Ubuntu Focal) Status: New => Invalid ** Changed in: python-xmltodict (Ubuntu Jammy) Status: New => Invalid ** Changed in: python-xmltodict (Ubuntu Kinetic) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/1961800 Title: Seeing out of memory errors after libexpat1 upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal) Status in expat package in Ubuntu: Fix Released Status in python-xmltodict package in Ubuntu: Invalid Status in expat source package in Bionic: Fix Released Status in python-xmltodict source package in Bionic: Invalid Status in expat source package in Focal: Fix Released Status in python-xmltodict source package in Focal: Invalid Status in expat source package in Jammy: Fix Released Status in python-xmltodict source package in Jammy: Invalid Status in expat source package in Kinetic: Fix Released Status in python-xmltodict source package in Kinetic: Invalid Status in expat source package in Lunar: Fix Released Status in python-xmltodict source package in Lunar: Invalid Bug description: I started seeing errors parsing XML files today (Feb 22, 2022) after my system was updated to 2.2.5-3ubuntu0.4. This is on a bionic server. The parsing is being done by python3's xmltodict module, which uses python3 expat as the actual parser. This is the error it raises: xml.parsers.expat.ExpatError: out of memory: line 1, column 0 So far this is happening on multiple xml files, although they all come from the same source (these are jenkins config.xml files). I'm working on coming up with a minimal test case which I'll provide once I have it cleaned up of any private data. [System info] $ lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 $ apt-cache policy libexpat1 libexpat1: Installed: 2.2.5-3ubuntu0.4 Candidate: 2.2.5-3ubuntu0.4 Version table: *** 2.2.5-3ubuntu0.4 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.2.5-3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1961800/+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 1961800] Re: Seeing out of memory errors after libexpat1 upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal)
Also fixed in focal expat 2.2.9-1ubuntu0.6 ** Also affects: expat (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: python-xmltodict (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: expat (Ubuntu Focal) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/1961800 Title: Seeing out of memory errors after libexpat1 upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal) Status in expat package in Ubuntu: Fix Released Status in python-xmltodict package in Ubuntu: Invalid Status in expat source package in Bionic: Fix Released Status in python-xmltodict source package in Bionic: Invalid Status in expat source package in Focal: Fix Released Status in python-xmltodict source package in Focal: Invalid Status in expat source package in Jammy: Fix Released Status in python-xmltodict source package in Jammy: Invalid Status in expat source package in Kinetic: Fix Released Status in python-xmltodict source package in Kinetic: Invalid Status in expat source package in Lunar: Fix Released Status in python-xmltodict source package in Lunar: Invalid Bug description: I started seeing errors parsing XML files today (Feb 22, 2022) after my system was updated to 2.2.5-3ubuntu0.4. This is on a bionic server. The parsing is being done by python3's xmltodict module, which uses python3 expat as the actual parser. This is the error it raises: xml.parsers.expat.ExpatError: out of memory: line 1, column 0 So far this is happening on multiple xml files, although they all come from the same source (these are jenkins config.xml files). I'm working on coming up with a minimal test case which I'll provide once I have it cleaned up of any private data. [System info] $ lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 $ apt-cache policy libexpat1 libexpat1: Installed: 2.2.5-3ubuntu0.4 Candidate: 2.2.5-3ubuntu0.4 Version table: *** 2.2.5-3ubuntu0.4 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.2.5-3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1961800/+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 1961800] Re: Seeing out of memory errors after libexpat1 upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal)
Also fixed in jammy expat 2.4.7 ** Also affects: expat (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: python-xmltodict (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: expat (Ubuntu Jammy) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/1961800 Title: Seeing out of memory errors after libexpat1 upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal) Status in expat package in Ubuntu: Fix Released Status in python-xmltodict package in Ubuntu: Invalid Status in expat source package in Bionic: Fix Released Status in python-xmltodict source package in Bionic: Invalid Status in expat source package in Focal: Fix Released Status in python-xmltodict source package in Focal: Invalid Status in expat source package in Jammy: Fix Released Status in python-xmltodict source package in Jammy: Invalid Status in expat source package in Kinetic: Fix Released Status in python-xmltodict source package in Kinetic: Invalid Status in expat source package in Lunar: Fix Released Status in python-xmltodict source package in Lunar: Invalid Bug description: I started seeing errors parsing XML files today (Feb 22, 2022) after my system was updated to 2.2.5-3ubuntu0.4. This is on a bionic server. The parsing is being done by python3's xmltodict module, which uses python3 expat as the actual parser. This is the error it raises: xml.parsers.expat.ExpatError: out of memory: line 1, column 0 So far this is happening on multiple xml files, although they all come from the same source (these are jenkins config.xml files). I'm working on coming up with a minimal test case which I'll provide once I have it cleaned up of any private data. [System info] $ lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 $ apt-cache policy libexpat1 libexpat1: Installed: 2.2.5-3ubuntu0.4 Candidate: 2.2.5-3ubuntu0.4 Version table: *** 2.2.5-3ubuntu0.4 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.2.5-3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1961800/+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 1961800] Re: Seeing out of memory errors after libexpat1 upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal)
This is also fixed in kinetic via expat 2.4.8 ** Also affects: expat (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: python-xmltodict (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: expat (Ubuntu Kinetic) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/1961800 Title: Seeing out of memory errors after libexpat1 upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal) Status in expat package in Ubuntu: Fix Released Status in python-xmltodict package in Ubuntu: Invalid Status in expat source package in Bionic: Fix Released Status in python-xmltodict source package in Bionic: Invalid Status in expat source package in Focal: Fix Released Status in python-xmltodict source package in Focal: Invalid Status in expat source package in Jammy: Fix Released Status in python-xmltodict source package in Jammy: Invalid Status in expat source package in Kinetic: Fix Released Status in python-xmltodict source package in Kinetic: Invalid Status in expat source package in Lunar: Fix Released Status in python-xmltodict source package in Lunar: Invalid Bug description: I started seeing errors parsing XML files today (Feb 22, 2022) after my system was updated to 2.2.5-3ubuntu0.4. This is on a bionic server. The parsing is being done by python3's xmltodict module, which uses python3 expat as the actual parser. This is the error it raises: xml.parsers.expat.ExpatError: out of memory: line 1, column 0 So far this is happening on multiple xml files, although they all come from the same source (these are jenkins config.xml files). I'm working on coming up with a minimal test case which I'll provide once I have it cleaned up of any private data. [System info] $ lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 $ apt-cache policy libexpat1 libexpat1: Installed: 2.2.5-3ubuntu0.4 Candidate: 2.2.5-3ubuntu0.4 Version table: *** 2.2.5-3ubuntu0.4 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.2.5-3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1961800/+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 1961800] Re: Seeing out of memory errors after libexpat1 upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal)
It seems this is fixed in Ubuntu Lunar in expat 2.5.0. ** Changed in: python-xmltodict (Ubuntu) Status: Confirmed => Invalid ** Also affects: expat (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Also affects: python-xmltodict (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Changed in: expat (Ubuntu Lunar) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/1961800 Title: Seeing out of memory errors after libexpat1 upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal) Status in expat package in Ubuntu: Fix Released Status in python-xmltodict package in Ubuntu: Invalid Status in expat source package in Bionic: Fix Released Status in python-xmltodict source package in Bionic: Invalid Status in expat source package in Focal: Fix Released Status in python-xmltodict source package in Focal: Invalid Status in expat source package in Jammy: Fix Released Status in python-xmltodict source package in Jammy: Invalid Status in expat source package in Kinetic: Fix Released Status in python-xmltodict source package in Kinetic: Invalid Status in expat source package in Lunar: Fix Released Status in python-xmltodict source package in Lunar: Invalid Bug description: I started seeing errors parsing XML files today (Feb 22, 2022) after my system was updated to 2.2.5-3ubuntu0.4. This is on a bionic server. The parsing is being done by python3's xmltodict module, which uses python3 expat as the actual parser. This is the error it raises: xml.parsers.expat.ExpatError: out of memory: line 1, column 0 So far this is happening on multiple xml files, although they all come from the same source (these are jenkins config.xml files). I'm working on coming up with a minimal test case which I'll provide once I have it cleaned up of any private data. [System info] $ lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 $ apt-cache policy libexpat1 libexpat1: Installed: 2.2.5-3ubuntu0.4 Candidate: 2.2.5-3ubuntu0.4 Version table: *** 2.2.5-3ubuntu0.4 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.2.5-3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1961800/+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 2000276] Re: FIDO2 user verification impossible when using the ssh agent
Some references I found back then: https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/101 https://github.com/openssh/openssh- portable/commit/39d17e189f8e72c34c722579d8d4e701fa5132da >From my chat messages: plain ssh-agent on kinetic worked with verify-required keys but I had to install ssh-askpass (ugly X11 interface) without it, it fails gnome-keyring's ssh-agent doesn't seem to support PIN entry for verify-required keys that's a lot of exceptions to list in the docs: a) newer openssh-client; b) ssh-askpass-gnome installed; c) use ssh-agent, not gnome-keyring (gnome-keyring is our default) So IIRC, it worked with kinetic's openssh ssh-agent, not ssh-agent from elsewhere (that would be the gnome-keyring bug linked above). ** Bug watch added: gitlab.gnome.org/GNOME/gnome-keyring/-/issues #101 https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/101 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2000276 Title: FIDO2 user verification impossible when using the ssh agent Status in openssh package in Ubuntu: New Bug description: I am having trouble setting up FIDO2 ssh keys with my yubikey 5C NFC if I want to enable user verification (user presence works fine). Steps to reproduce: = Prep work = Client (kinetic): * generate a key that requires user verification: $ ssh-keygen -t ed25519-sk -f ~/.ssh/id_ed25519_verify_sk -O verify-required -C "this key requires UV" [provide your authenticator PIN, touch it, and add an encryption password] Server (jammy): * add id_ed25519_verify_sk.pub to authorized_keys = Symptoms = Shell 1 (w/ssh agent): $ eval $(ssh-agent) Agent pid 3279738 $ ssh-add ~/.ssh/id_ed25519_verify_sk Enter passphrase for /home/aieri/.ssh/id_ed25519_verify_sk: Identity added: /home/aieri/.ssh/id_ed25519_verify_sk (this key requires UV) $ ssh ubuntu@10.35.202.231 -i ~/.ssh/id_ed25519_verify_sk "echo FIDO2 fails\!" sign_and_send_pubkey: signing failed for ED25519-SK "/home/aieri/.ssh/id_ed25519_verify_sk" from agent: agent refused operation ubuntu@10.35.202.231: Permission denied (publickey). [note that the above is printed immediately, and that the yubikey does not light up] Shell 2 (no ssh agent): $ ssh ubuntu@10.35.202.231 -i ~/.ssh/id_ed25519_verify_sk "echo FIDO2 works\!" Enter passphrase for key '/home/aieri/.ssh/id_ed25519_verify_sk': Enter PIN for ED25519-SK key /home/aieri/.ssh/id_ed25519_verify_sk: Confirm user presence for key ED25519-SK SHA256:nhgS4c2rGtE7XKeez3rAsofrjJvsL6rmBLShZxfTXIY User presence confirmed FIDO2 works! NOTE: * user _presence_ can be validated correctly with or without the ssh-agent: keys generated without `-O verify-required` work as expected (aside from bug 1869897) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2000276/+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 2000276] Re: FIDO2 user verification impossible when using the ssh agent
I believe this issue is correct. I noticed this when writing up the documentation[1] on how to use openssh with fido2 resident keys: """ NOTE If you used the -O verify-required option when generating the keys, or if that option is set on the SSH server via /etc/ssh/sshd_config’s PubkeyAuthOptions verify-required, then using the agent currently in Ubuntu 22.04 LTS won’t work. """ I remember I found an upstream bug about this, but it is a bit muddy because there is ssh-agent from ssh, and there is one from gnome (and I think from gpg-agent as well; again, muddy). If I find those pointers again, I'll post them here. 1. https://ubuntu.com/server/docs/service-openssh -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2000276 Title: FIDO2 user verification impossible when using the ssh agent Status in openssh package in Ubuntu: New Bug description: I am having trouble setting up FIDO2 ssh keys with my yubikey 5C NFC if I want to enable user verification (user presence works fine). Steps to reproduce: = Prep work = Client (kinetic): * generate a key that requires user verification: $ ssh-keygen -t ed25519-sk -f ~/.ssh/id_ed25519_verify_sk -O verify-required -C "this key requires UV" [provide your authenticator PIN, touch it, and add an encryption password] Server (jammy): * add id_ed25519_verify_sk.pub to authorized_keys = Symptoms = Shell 1 (w/ssh agent): $ eval $(ssh-agent) Agent pid 3279738 $ ssh-add ~/.ssh/id_ed25519_verify_sk Enter passphrase for /home/aieri/.ssh/id_ed25519_verify_sk: Identity added: /home/aieri/.ssh/id_ed25519_verify_sk (this key requires UV) $ ssh ubuntu@10.35.202.231 -i ~/.ssh/id_ed25519_verify_sk "echo FIDO2 fails\!" sign_and_send_pubkey: signing failed for ED25519-SK "/home/aieri/.ssh/id_ed25519_verify_sk" from agent: agent refused operation ubuntu@10.35.202.231: Permission denied (publickey). [note that the above is printed immediately, and that the yubikey does not light up] Shell 2 (no ssh agent): $ ssh ubuntu@10.35.202.231 -i ~/.ssh/id_ed25519_verify_sk "echo FIDO2 works\!" Enter passphrase for key '/home/aieri/.ssh/id_ed25519_verify_sk': Enter PIN for ED25519-SK key /home/aieri/.ssh/id_ed25519_verify_sk: Confirm user presence for key ED25519-SK SHA256:nhgS4c2rGtE7XKeez3rAsofrjJvsL6rmBLShZxfTXIY User presence confirmed FIDO2 works! NOTE: * user _presence_ can be validated correctly with or without the ssh-agent: keys generated without `-O verify-required` work as expected (aside from bug 1869897) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2000276/+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 2002558] Re: erro Icon connection
** Package changed: ubuntu => xorg (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/2002558 Title: erro Icon connection Status in xorg package in Ubuntu: New Bug description: The ethernet connection icon has disappeared, it's a cosmetic problem, I can access the internet both via cable, WI-FI and VPN, I would like to report this error, as I still haven't found a solution to the problem on the internet. In settings, it also disappeared, only the VPN settings are still visible. (I used google translator, if possible answer me in Portuguese.) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Wed Jan 11 13:53:57 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6290] [1002:9807] (prog-if 00 [VGA controller]) Subsystem: Lenovo Wrestler [Radeon HD 6290] [17aa:397f] InstallationDate: Installed on 2022-07-29 (166 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20136 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=c7305ad4-8faf-45a3-8420-afbb79aaf181 ro net.ifnames=0 biosdevname=0 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/02/2012 dmi.bios.release: 0.93 dmi.bios.vendor: LENOVO dmi.bios.version: 6CCN93WW(V8.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo G485 dmi.board.vendor: LENOVO dmi.board.version: 3194WIN8 STD SGL dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G485 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnLENOVO:bvr6CCN93WW(V8.05):bd10/02/2012:br0.93:efr0.0:svnLENOVO:pn20136:pvrLenovoG485:rvnLENOVO:rnLenovoG485:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoG485:skuLENOVO_MT_20136: dmi.product.family: IDEAPAD dmi.product.name: 20136 dmi.product.sku: LENOVO_MT_20136 dmi.product.version: Lenovo G485 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2002558/+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 2002558] [NEW] erro Icon connection
You have been subscribed to a public bug: The ethernet connection icon has disappeared, it's a cosmetic problem, I can access the internet both via cable, WI-FI and VPN, I would like to report this error, as I still haven't found a solution to the problem on the internet. In settings, it also disappeared, only the VPN settings are still visible. (I used google translator, if possible answer me in Portuguese.) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Wed Jan 11 13:53:57 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6290] [1002:9807] (prog-if 00 [VGA controller]) Subsystem: Lenovo Wrestler [Radeon HD 6290] [17aa:397f] InstallationDate: Installed on 2022-07-29 (166 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20136 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=c7305ad4-8faf-45a3-8420-afbb79aaf181 ro net.ifnames=0 biosdevname=0 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/02/2012 dmi.bios.release: 0.93 dmi.bios.vendor: LENOVO dmi.bios.version: 6CCN93WW(V8.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo G485 dmi.board.vendor: LENOVO dmi.board.version: 3194WIN8 STD SGL dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G485 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnLENOVO:bvr6CCN93WW(V8.05):bd10/02/2012:br0.93:efr0.0:svnLENOVO:pn20136:pvrLenovoG485:rvnLENOVO:rnLenovoG485:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoG485:skuLENOVO_MT_20136: dmi.product.family: IDEAPAD dmi.product.name: 20136 dmi.product.sku: LENOVO_MT_20136 dmi.product.version: Lenovo G485 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic performance third-party-packages ubuntu wayland-session -- erro Icon connection https://bugs.launchpad.net/bugs/2002558 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2
Hello Nafees,
Can you share this setup.py that we can use to reproduce the problem and
investigate?
Regards,
Fabio Martins
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
New
Bug description:
Compiling a Python extension using Python2 (Python 2.7.18) is making
use of wrong compiler flags, hence dropping required optimizations
when required. This is happening only when python2 is installed from
Ubuntu's repositories. By default, Python's distutils module uses
compiler and linker flags used to compile Python itself to be used to
compile extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
On further investigation, it looks like Ubuntu's specific patch applied on
libpython2.7-stdlib package is altering the original upstream implementation of
distutils/sysconfig.py code.
Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
Patch -
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
Below is the code block which is causing the issue, where the presence of
configure_cflags is modifying cflags. This code is result of ubuntu's patch and
doesn't come directly from upstream python implementation.
File - /usr/lib/python2.7/distutils/sysconfig.py
Part of code block:
elif configure_cflags:
cflags = ' '.join(str(x) for x in (basecflags, configure_cflags,
extra_cflags) if x)
ldshared = ldshared + ' ' + configure_cflags
I don't see problem on Python3 though we have extra code added from patch
there as well. Patch used on python3, is not modifying the cflags completely
and instead appending new flags to cflags.
On python3 (tested on Ubuntu 20.04)
File - /usr/lib/python3.8/distutils/sysconfig.py
Part of code block which doesn't alter cflags completely
elif configure_cflags:
cflags = cflags + ' ' + configure_cflags
ldshared = ldshared + ' ' + configure_cflags
Request to update the python2 patch to behave similar to what is been done on
python3.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2002563] [NEW] The ethernet connection icon has disappeared
Public bug reported: The ethernet connection icon has disappeared, it's a cosmetic problem, I can access the internet both via cable, WI-FI and VPN, I would like to report this error, as I still haven't found a solution to the problem on the internet. In settings, it also disappeared, only the VPN settings are still visible. (I used google translator, if possible answer me in Portuguese.) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: network-manager 1.40.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 11 14:50:09 2023 InstallationDate: Installed on 2022-07-29 (166 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 192.168.1.1 dev eth0 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.82 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.40.0 connected started limited enabled enabled disabled missing enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2002563 Title: The ethernet connection icon has disappeared Status in network-manager package in Ubuntu: New Bug description: The ethernet connection icon has disappeared, it's a cosmetic problem, I can access the internet both via cable, WI-FI and VPN, I would like to report this error, as I still haven't found a solution to the problem on the internet. In settings, it also disappeared, only the VPN settings are still visible. (I used google translator, if possible answer me in Portuguese.) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: network-manager 1.40.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 11 14:50:09 2023 InstallationDate: Installed on 2022-07-29 (166 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 192.168.1.1 dev eth0 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.82 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.40.0 connected started limited enabled enabled disabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2002563/+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 1971932] Re: error in rsync protocol data stream
I have confirmed this bug as well. Here is what I have done: rsync failed when transferring large files over network with error 12 when using compression (z option). rsync succeeded when I transferred large files over USB to external SSD when using compression (z option). rsync succeeded when transferring large files over network when NOT using compression (z option). Hope this offers some assistance in tracking and correcting this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1971932 Title: error in rsync protocol data stream Status in rsync package in Ubuntu: Confirmed Bug description: When synchronizing to other systems, rsync exits with "error in rsync protocol data stream (code 12)". The problem occurs since ubuntu 22.04 LTS with two different destination systems not running ubuntu but plain debian. The error did not occur under 20.04 LTS. Synchronisation runs fine for most other files, but always stops at the same (relative large) file. The file itself has also been changed on a test basis to make sure the file is not the problem itself. Log snippet: ... chunk[46131] len=46120 offset=2127561720 sum1=2f48caf4 chunk[46132] len=46120 offset=2127607840 sum1=5dfcb4ee chunk[46133] len=46120 offset=2127653960 sum1=d1037d81 chunk[46134] len=8870 offset=2127700080 sum1=6deedc97 send_files mapped /path/backup/subdir/.thunderbird/profile/ImapMail/imap.domain.com/INBOX of size 2135722584 calling match_sums /path/backup/subdir/.thunderbird/profile/ImapMail/imap.domain.com/INBOX built hash table hash search b=46120 len=2135722584 sum=1e1722dc k=46120 hash search s->blength=46120 len=2135722584 count=46135 potential match at 0 i=0 sum=1e1722dc match at 0 last_match=0 j=0 len=46120 n=0 potential match at 46120 i=1 sum=c482d6b6 match at 46120 last_match=46120 j=1 len=46120 n=0 potential match at 92240 i=2 sum=b21c7e11 match at 92240 last_match=92240 j=2 len=46120 n=0 potential match at 138360 i=3 sum=d066473a match at 138360 last_match=138360 j=3 len=46120 n=0 potential match at 184480 i=4 sum=a32a2984 match at 184480 last_match=184480 j=4 len=46120 n=0 potential match at 230600 i=5 sum=39cc049f match at 230600 last_match=230600 j=5 len=46120 n=0 potential match at 276720 i=6 sum=ad3de98a match at 276720 last_match=276720 j=6 len=46120 n=0 potential match at 322840 i=7 sum=83e16fa9 match at 322840 last_match=322840 j=7 len=46120 n=0 deflate on token returned 0 (8512 bytes left) rsync error: error in rsync protocol data stream (code 12) at token.c(476) [sender=3.2.3] [sender] _exit_cleanup(code=12, file=token.c, line=476): entered [sender] _exit_cleanup(code=12, file=token.c, line=476): about to call exit(12) Sender system: (rsync 3.2.3-8ubuntu3) - rsync version 3.2.3 protocol version 31 Copyright (C) 1996-2020 by Andrew Tridgell, Wayne Davison, and others. Web site: https://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, hardlink-specials, symlinks, IPv6, atimes, batchfiles, inplace, append, ACLs, xattrs, optional protect-args, iconv, symtimes, prealloc, stop-at, no crtimes Optimizations: SIMD, no asm, openssl-crypto Checksum list: xxh128 xxh3 xxh64 (xxhash) md5 md4 none Compress list: zstd lz4 zlibx zlib none rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. Recipient systems: (rsync 3.1.3-6) -- rsync version 3.1.3 protocol version 31 Copyright (C) 1996-2018 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, iconv, symtimes, prealloc rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1971932/+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 2002511] Re: zlib 1.2.13 (and patched 1.2.11) breaks libxml2 on s390x
** Patch added:
"debdiff_zlib_lunar_from_1.2.13.dfsg-1ubuntu3_to_1.2.13.dfsg-1ubuntu4.diff"
https://bugs.launchpad.net/zlib/+bug/2002511/+attachment/5640780/+files/debdiff_zlib_lunar_from_1.2.13.dfsg-1ubuntu3_to_1.2.13.dfsg-1ubuntu4.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/2002511
Title:
zlib 1.2.13 (and patched 1.2.11) breaks libxml2 on s390x
Status in Ubuntu on IBM z Systems:
Triaged
Status in zlib:
In Progress
Status in zlib package in Ubuntu:
In Progress
Status in zlib source package in Focal:
New
Status in zlib source package in Jammy:
New
Status in zlib source package in Kinetic:
New
Status in zlib source package in Lunar:
In Progress
Bug description:
SRU Justification:
--
[ Impact ]
* zlib version 1.2.13, as well as patched zlib versions 1.2.11 with
the patch from LP#1990379, break libxml2 and lxml on s390x.
* The problem appears during loading a gzipped XML file.
* Disabling hw compression with 'export DFLTCC=0' solves this,
hence it's a problem with the hardware acceleration patches DFLTCC.
* For more info see:
https://bugzilla.redhat.com/show_bug.cgi?id=2155328
[ Test Plan ]
* Steps to Reproduce:
1. echo "" > file.xml
2. gzip file.xml
3. python3
>>> import libxml2
>>> libxml2.parseFile("file.xml.gz")
* Actual results:
file.xml.gz:1: parser error : Document is empty
^
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3.11/site-packages/libxml2.py",
line 1362, in parseFile
if ret is None:raise parserError('xmlParseFile() failed')
^^
libxml2.parserError: xmlParseFile() failed
* Expected results:
Loaded file.
[ Where problems could occur ]
* Since this is limited to s390x and DFLTCC / hw acceleration active,
any possible problems are limited to such environments.
* Fix can be broken if the state handling (state->wrap),
or the states mixed.
* The translation from stream to parameter block could be broken
(again due to wrong states) and the inflate as well.
[ Other Info ]
* The official upstream fix is here:
https://github.com/zlib-ng/zlib-ng/pull/1390
but it's for zlib-ng.
* For zlib this needs to be adjusted and was done by the author here:
https://launchpadlibrarian.net/641454325/patch-1.2.11
* And again slightly adjusted by me (renamed, some white-space fixes
and conversion into a quilt patch with proper dep3 header):
https://launchpadlibrarian.net/645435847/1390.patch
* The zlib version in Focal, Jammy, Kinetic and Lunar are affected.
__
It has been reported that 1.2.13 as well as the patch from LP#1990379 breaks
libxml2 (and libxml) on s390x:
(https://bugzilla.redhat.com/show_bug.cgi?id=2155328). The attached patch
should fix the issue.
The upstream author proposed a fix and a new test for zlib-ng
(https://github.com/zlib-ng/zlib-ng/pull/1390) in order to detect such
breakages in the future.
___
This was initially reported as part of LP#1990379,
especially:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1990379/comments/12
but needs a separate LP bug (number) - this one.
___
The proposed patch at https://launchpadlibrarian.net/641454325/patch-1.2.11
needed some tweaks regarding white-spaces, but then applied fine on focal,
jammy, kinetic and also 1.2.13, which is what we currently have in
lunar-proposed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2002511/+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 2002511] Re: zlib 1.2.13 (and patched 1.2.11) breaks libxml2 on s390x
The attachment "1390.patch" seems to be a patch. If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/2002511
Title:
zlib 1.2.13 (and patched 1.2.11) breaks libxml2 on s390x
Status in Ubuntu on IBM z Systems:
Triaged
Status in zlib:
In Progress
Status in zlib package in Ubuntu:
In Progress
Status in zlib source package in Focal:
New
Status in zlib source package in Jammy:
New
Status in zlib source package in Kinetic:
New
Status in zlib source package in Lunar:
In Progress
Bug description:
SRU Justification:
--
[ Impact ]
* zlib version 1.2.13, as well as patched zlib versions 1.2.11 with
the patch from LP#1990379, break libxml2 and lxml on s390x.
* The problem appears during loading a gzipped XML file.
* Disabling hw compression with 'export DFLTCC=0' solves this,
hence it's a problem with the hardware acceleration patches DFLTCC.
* For more info see:
https://bugzilla.redhat.com/show_bug.cgi?id=2155328
[ Test Plan ]
* Steps to Reproduce:
1. echo "" > file.xml
2. gzip file.xml
3. python3
>>> import libxml2
>>> libxml2.parseFile("file.xml.gz")
* Actual results:
file.xml.gz:1: parser error : Document is empty
^
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3.11/site-packages/libxml2.py",
line 1362, in parseFile
if ret is None:raise parserError('xmlParseFile() failed')
^^
libxml2.parserError: xmlParseFile() failed
* Expected results:
Loaded file.
[ Where problems could occur ]
* Since this is limited to s390x and DFLTCC / hw acceleration active,
any possible problems are limited to such environments.
* Fix can be broken if the state handling (state->wrap),
or the states mixed.
* The translation from stream to parameter block could be broken
(again due to wrong states) and the inflate as well.
[ Other Info ]
* The official upstream fix is here:
https://github.com/zlib-ng/zlib-ng/pull/1390
but it's for zlib-ng.
* For zlib this needs to be adjusted and was done by the author here:
https://launchpadlibrarian.net/641454325/patch-1.2.11
* And again slightly adjusted by me (renamed, some white-space fixes
and conversion into a quilt patch with proper dep3 header):
https://launchpadlibrarian.net/645435847/1390.patch
* The zlib version in Focal, Jammy, Kinetic and Lunar are affected.
__
It has been reported that 1.2.13 as well as the patch from LP#1990379 breaks
libxml2 (and libxml) on s390x:
(https://bugzilla.redhat.com/show_bug.cgi?id=2155328). The attached patch
should fix the issue.
The upstream author proposed a fix and a new test for zlib-ng
(https://github.com/zlib-ng/zlib-ng/pull/1390) in order to detect such
breakages in the future.
___
This was initially reported as part of LP#1990379,
especially:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1990379/comments/12
but needs a separate LP bug (number) - this one.
___
The proposed patch at https://launchpadlibrarian.net/641454325/patch-1.2.11
needed some tweaks regarding white-spaces, but then applied fine on focal,
jammy, kinetic and also 1.2.13, which is what we currently have in
lunar-proposed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2002511/+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 2002318] Re: Please merge lsb 11.5 from Debian unstable.
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/2002318 Title: Please merge lsb 11.5 from Debian unstable. Status in lsb package in Ubuntu: New Bug description: Please merge lsb 11.5 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/2002318/+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 1988270] Re: AppArmor fails to start with Yoga UCA libvirt profile on Focal
### VERIFICATION DONE FOCAL ###
# previous apparmor version
apt-cache policy apparmor
package name: apparmor
package version: 2.13.3-7ubuntu5.1
series: Focal
kernel: Linux 5.4.0-136-generic
# before enabling -proposed
generate focal-yoga instance
juju ssh nova-compute/0
# verify no apparmor errors in logs
cat /var/log/syslog | grep Error
# verify apparmor is running
sudo systemctl status apparmor
# trigger error
sudo systemctl restart apparmor
# The apparmor service never successfully restarts
Job for apparmor.service failed because the control process exited with error
code.
See "systemctl status apparmor.service" and "journalctl -xe" for details
cat /var/log/syslog
Error messages in syslog:
Jan 11 15:46:14 juju-5c2ee8-appbug-9 apparmor.systemd[52695]: AppArmor parser
error for /etc/apparmor.d in /etc/apparmor.d/usr.sbin.libvirtd at line 29:
Invalid capability bpf.
Jan 11 15:46:14 juju-5c2ee8-appbug-9 apparmor.systemd[52669]: Error: At least
one profile failed to load
Jan 11 15:46:14 juju-5c2ee8-appbug-9 systemd[1]: apparmor.service: Main process
exited, code=exited, status=1/FAILURE
### Enable proposed ###
# testing with focal-yoga
Apparmor version tested - 2.13.3-7ubuntu5.2
sudo apt-cache policy apparmor
sudo vim /etc/apt/sources.list
# add -proposed
deb http://nova.clouds.archive.ubuntu.com/ubuntu/ focal-proposed main universe
# save and exit
sudo apt-get update
sudo apt-get upgrade apparmor -y
sudo systemctl restart apparmor
systemctl status apparmor
Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset:
enabled)
Active: active (exited) since Wed 2023-01-11 15:55:19 UTC; 20s ago
tail -n 1000 /var/log/syslog
# no errors are thrown by apparmor
Jan 11 15:54:41 juju-5c2ee8-appbug-9 systemd[1]: Reloading.
Jan 11 15:55:19 juju-5c2ee8-appbug-9 systemd[1]: Starting Load AppArmor
profiles...
Jan 11 15:55:19 juju-5c2ee8-appbug-9 apparmor.systemd[66497]: Restarting
AppArmor
Jan 11 15:55:19 juju-5c2ee8-appbug-9 apparmor.systemd[66497]: Reloading
AppArmor profiles
Jan 11 15:55:19 juju-5c2ee8-appbug-9 kernel: [ 2042.612010] kauditd_printk_skb:
9 callbacks suppressed
Jan 11 15:55:19 juju-5c2ee8-appbug-9 kernel: [ 2042.612013] audit: type=1400
audit(1673452519.139:106): apparmor="STATUS" operation="profile_replace"
info="same as current profile, skipping" profile="unconfined"
name="nvidia_modprobe" pid=66503 comm="apparmor_parser"
Jan 11 15:55:19 juju-5c2ee8-appbug-9 kernel: [ 2042.612022] audit: type=1400
audit(1673452519.139:107): apparmor="STATUS" operation="profile_replace"
info="same as current profile, skipping" profile="unconfined"
name="nvidia_modprobe//kmod" pid=66503 comm="apparmor_parser"
Jan 11 15:55:19 juju-5c2ee8-appbug-9 kernel: [ 2042.612179] audit: type=1400
audit(1673452519.139:108): apparmor="STATUS" operation="profile_replace"
profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action"
pid=66502 comm="apparmor_parser"
Jan 11 15:55:19 juju-5c2ee8-appbug-9 kernel: [ 2042.612183] audit: type=1400
audit(1673452519.139:109): apparmor="STATUS" operation="profile_replace"
profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=66502
comm="apparmor_parser"
Jan 11 15:55:19 juju-5c2ee8-appbug-9 kernel: [ 2042.612186] audit: type=1400
audit(1673452519.139:110): apparmor="STATUS" operation="profile_replace"
profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=66502
comm="apparmor_parser"
Jan 11 15:55:19 juju-5c2ee8-appbug-9 kernel: [ 2042.612187] audit: type=1400
audit(1673452519.139:111): apparmor="STATUS" operation="profile_replace"
profile="unconfined" name="/{,usr/}sbin/dhclient" pid=66502
comm="apparmor_parser"
Jan 11 15:55:19 juju-5c2ee8-appbug-9 kernel: [ 2042.614725] audit: type=1400
audit(1673452519.139:112): apparmor="STATUS" operation="profile_replace"
profile="unconfined" name="/usr/bin/man" pid=66504 comm="apparmor_parser"
Jan 11 15:55:19 juju-5c2ee8-appbug-9 kernel: [ 2042.614729] audit: type=1400
audit(1673452519.139:113): apparmor="STATUS" operation="profile_replace"
profile="unconfined" name="man_filter" pid=66504 comm="apparmor_parser"
Jan 11 15:55:19 juju-5c2ee8-appbug-9 kernel: [ 2042.614731] audit: type=1400
audit(1673452519.139:114): apparmor="STATUS" operation="profile_replace"
profile="unconfined" name="man_groff" pid=66504 comm="apparmor_parser"
Jan 11 15:55:19 juju-5c2ee8-appbug-9 kernel: [ 2042.618860] audit: type=1400
audit(1673452519.143:115): apparmor="STATUS" operation="profile_replace"
info="same as current profile, skipping" profile="unconfined"
name="/usr/sbin/tcpdump" pid=66505 comm="apparmor_parser"
Jan 11 15:55:19 juju-5c2ee8-appbug-9 apparmor.systemd[66525]: Skipping profile
in /etc/apparmor.d/disable: usr.bin.nova-compute
Jan 11 15:55:19 juju-5c2ee8-appbug-9 apparmor.systemd[66526]: Skipping profile
in /etc/apparmor.d/disable: usr.sbin.rsyslogd
Jan 11 15:55:19 juju-5c2ee8-appbug-9 systemd[1]: Finished Load AppArmor
[Touch-packages] [Bug 2002318] Re: Please merge lsb 11.5 from Debian unstable.
Attaching patch against Debian unstable. For ease of review, relevant commits and tags have been pushed to the following repository: https://code.launchpad.net/~waveform/ubuntu/+source/lsb/+git/lsb Specifically: * logical/11.2ubuntu1 represents our split-out delta on top of old/debian (11.2) * logical/11.5ubuntu1 represents our rebased delta on top of new/debian (11.5) * merge/11.5ubuntu1 adds changelog and maintainer changes on top of logical/11.5ubuntu1, and then a pile of fixes to tidy up all the lintian warnings and patch various historically broken pieces. Hence, the following commands may produce output useful to the purposes of review. The first compares the rebased delta against the old delta: git range-diff --creation-factor=100 old/debian..logical/11.2ubuntu1 new/debian..logical/11.5ubuntu1 The second shows the additional fixes added to the rebased delta to fix the lintian warnings and historically broken functionality: git show logical/11.5ubuntu1..merge/11.5ubuntu1 I should additionally note that the historical breakage mentioned above includes the fact that certain aspects of lsbinstall have not worked for roughly 17 years (save_lsbinstall_info in initdutils.py has had the wrong argument order to cPickle.dump / pickle.dump for its entire history). We should try and determine if anything in this package is really still used (if it ever was) and follow Debian in expunging it if not because at this point the entire package is pretty much a delta. Incidentally, this is why I've also taken the liberty of replacing "Debian" with "Ubuntu" in the d/control descriptions as it seems unfair to be referencing Debian when the package is now empty upstream. ** Patch added: "1-2002318.debdiff" https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/2002318/+attachment/5640743/+files/1-2002318.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/2002318 Title: Please merge lsb 11.5 from Debian unstable. Status in lsb package in Ubuntu: New Bug description: Please merge lsb 11.5 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/2002318/+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 2002428] Re: Autopkgtest failure due to moved testcase
Thanks for the patch! One comment, when a patch is ready for sponsoring you can drop the "~ppa2" from the version number. I'll just go ahead and do that before uploading for this one. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2002428 Title: Autopkgtest failure due to moved testcase Status in coreutils package in Ubuntu: New Bug description: In 9.1-1ubuntu1 (lunar), a testcase has been renamed from proc- selinux-segfault.sh to selinux-segfault.sh . This changes debian/tests/upstream to reflect the change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2002428/+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 1998265] Update Released
The verification of the Stable Release Update for python-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 python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1998265 Title: OverFlow error when using cnf-extractor Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Bionic: Fix Released Status in python-apt source package in Focal: Fix Committed Status in python-apt source package in Jammy: Fix Committed Status in python-apt source package in Kinetic: Fix Committed Bug description: [Impact] Large files can't be downloaded as we use a 32-bit integer in AcquireFile constructor, this breaks e.g. command-not-found generator: I'm trying to update the command-not-found indexes (bin/cnf-extract.py $MIRROR $suite $component $arch) on the production cnf extractor system (running bionic) and have encountered Tracebacks when generating them for Jammy and Lunar. This is causing the command not found indexes to be out of date for all(?) releases of Ubuntu. The lunar failure: Get:1 dotnet-sdk-6.0_6.0.111-0ubuntu3_amd64.deb [79.1 MB] Fetched 79.1 MB in 0s (0 B/s) Traceback (most recent call last):64... 7% File "./bin/cnf-extract.py", line 54, in mirror_root, suite, component, arch) File "/srv/cnf-extractor/extractor/extractor.py", line 174, in command_not_found_extract debpath = pkg.candidate.fetch_binary(destdir=tmpdir) File "/usr/lib/python3/dist-packages/apt/package.py", line 883, in fetch_binary self.size, base, destfile=destfile) OverflowError: signed integer is greater than maximum I'll get more context for the Jammy failure but it wouldn't surprise me if it was the same package. [Test plan] I have included a test for the AcquireFile constructor to accept a large file size, and then a test that ensures it can read the file size. Run the autopkgtest suite. [Where problems could occur] It could fail in other places now. For kinetic, the package was copied in from lunar without changes. This upload is actually built in kinetic and hence there is additional regression potential from toolchain changes. [Other info] Also including some auxiliary changes as we move back to proper upstream releases to enable testing, mostly around d/gbp.conf, .gitlab-ci.yml - being updated to point at right places d/t/control - adding a missing test dependency data/ - updated mirror lists The mirror lists are standard updates; the debian/tests/control change is needed to enable testing on more minimal autopkgtest images (our images accidentally include binutils); the other changes have zero impact on the Ubuntu infra or end user side as they only run during development. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1998265/+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 1998265] Re: OverFlow error when using cnf-extractor
This bug was fixed in the package python-apt - 1.6.6 --- python-apt (1.6.6) bionic; urgency=medium * The "It's an upstream release again" release. Ran all the usual upstream CI and release bits :) * AcquireFile: Handle large files (LP: #1998265) * Get Debian mirrors from mirror-master.debian.org, the previous location stopped working * Update mirror lists * d/t/control: Add missing binutils test dependency -- Julian Andres Klode Thu, 01 Dec 2022 13:36:29 +0100 ** Changed in: python-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 python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1998265 Title: OverFlow error when using cnf-extractor Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Bionic: Fix Released Status in python-apt source package in Focal: Fix Committed Status in python-apt source package in Jammy: Fix Committed Status in python-apt source package in Kinetic: Fix Committed Bug description: [Impact] Large files can't be downloaded as we use a 32-bit integer in AcquireFile constructor, this breaks e.g. command-not-found generator: I'm trying to update the command-not-found indexes (bin/cnf-extract.py $MIRROR $suite $component $arch) on the production cnf extractor system (running bionic) and have encountered Tracebacks when generating them for Jammy and Lunar. This is causing the command not found indexes to be out of date for all(?) releases of Ubuntu. The lunar failure: Get:1 dotnet-sdk-6.0_6.0.111-0ubuntu3_amd64.deb [79.1 MB] Fetched 79.1 MB in 0s (0 B/s) Traceback (most recent call last):64... 7% File "./bin/cnf-extract.py", line 54, in mirror_root, suite, component, arch) File "/srv/cnf-extractor/extractor/extractor.py", line 174, in command_not_found_extract debpath = pkg.candidate.fetch_binary(destdir=tmpdir) File "/usr/lib/python3/dist-packages/apt/package.py", line 883, in fetch_binary self.size, base, destfile=destfile) OverflowError: signed integer is greater than maximum I'll get more context for the Jammy failure but it wouldn't surprise me if it was the same package. [Test plan] I have included a test for the AcquireFile constructor to accept a large file size, and then a test that ensures it can read the file size. Run the autopkgtest suite. [Where problems could occur] It could fail in other places now. For kinetic, the package was copied in from lunar without changes. This upload is actually built in kinetic and hence there is additional regression potential from toolchain changes. [Other info] Also including some auxiliary changes as we move back to proper upstream releases to enable testing, mostly around d/gbp.conf, .gitlab-ci.yml - being updated to point at right places d/t/control - adding a missing test dependency data/ - updated mirror lists The mirror lists are standard updates; the debian/tests/control change is needed to enable testing on more minimal autopkgtest images (our images accidentally include binutils); the other changes have zero impact on the Ubuntu infra or end user side as they only run during development. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1998265/+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 1983794] Re: Evolution not deleting autosave files
** Description changed:
+ [ Impact ]
+
+ Autosave files are not removed from evolution local state directories
+ (and windows leaked)
+
+
+ [ Test case ]
+
+ 1. Open evolution, and start to compose a new email
+ 2. Write enough text and wait few minutes so that this command returns a file
+ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
+ 3. Close the email composer window, hitting "Do not save"
+ 4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
+ 5. Opening and closing again evolution should not ask to restore the previous
email
+
+
+ [ Regression potential ]
+
+ No sounds could be performed during some UI actions
+
+ ---
+
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1 was
installed with the distribution on a new system and received settings
imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string). When
the email is successfully sent, the autosave file SHOULD be deleted.
It's not. When evolution is shut down and restarted I'm asked if I want
to recover an unfinished email. Answering No to this will delete the
autosave file, but otherwise it persists and the recovery query recurs
the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome people
aren't dealing with it, perhaps considering it a distro-specific bug.
On a system used by many people this is a potential security issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
In Progress
Status in libcanberra source package in Jammy:
In Progress
Status in evolution source package in Kinetic:
New
Status in libcanberra source package in Kinetic:
In Progress
Bug description:
[ Impact ]
Autosave files are not removed from evolution local state directories
(and windows leaked)
[ Test case ]
1. Open evolution, and start to compose a new email
2. Write enough text and wait few minutes so that this command returns a file
ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
3. Close the email composer window, hitting "Do not save"
4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
5. Opening and closing again evolution should not ask to restore the previous
email
[ Regression potential ]
No sounds could be performed during some UI actions
---
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 2002511] Re: zlib 1.2.13 (and patched 1.2.11) breaks libxml2 on s390x
** Summary changed:
- zlib 1.2.13 (and patched 1.2.11) breaks libxml(2) on s390x
+ zlib 1.2.13 (and patched 1.2.11) breaks libxml2 on s390x
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/2002511
Title:
zlib 1.2.13 (and patched 1.2.11) breaks libxml2 on s390x
Status in Ubuntu on IBM z Systems:
Triaged
Status in zlib:
In Progress
Status in zlib package in Ubuntu:
In Progress
Status in zlib source package in Focal:
New
Status in zlib source package in Jammy:
New
Status in zlib source package in Kinetic:
New
Status in zlib source package in Lunar:
In Progress
Bug description:
SRU Justification:
--
[ Impact ]
* zlib version 1.2.13, as well as patched zlib versions 1.2.11 with
the patch from LP#1990379, break libxml2 and lxml on s390x.
* The problem appears during loading a gzipped XML file.
* Disabling hw compression with 'export DFLTCC=0' solves this,
hence it's a problem with the hardware acceleration patches DFLTCC.
* For more info see:
https://bugzilla.redhat.com/show_bug.cgi?id=2155328
[ Test Plan ]
* Steps to Reproduce:
1. echo "" > file.xml
2. gzip file.xml
3. python3
>>> import libxml2
>>> libxml2.parseFile("file.xml.gz")
* Actual results:
file.xml.gz:1: parser error : Document is empty
^
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3.11/site-packages/libxml2.py",
line 1362, in parseFile
if ret is None:raise parserError('xmlParseFile() failed')
^^
libxml2.parserError: xmlParseFile() failed
* Expected results:
Loaded file.
[ Where problems could occur ]
* Since this is limited to s390x and DFLTCC / hw acceleration active,
any possible problems are limited to such environments.
* Fix can be broken if the state handling (state->wrap),
or the states mixed.
* The translation from stream to parameter block could be broken
(again due to wrong states) and the inflate as well.
[ Other Info ]
* The official upstream fix is here:
https://github.com/zlib-ng/zlib-ng/pull/1390
but it's for zlib-ng.
* For zlib this needs to be adjusted and was done by the author here:
https://launchpadlibrarian.net/641454325/patch-1.2.11
* And again slightly adjusted by me (renamed, some white-space fixes
and conversion into a quilt patch with proper dep3 header):
https://launchpadlibrarian.net/645435847/1390.patch
* The zlib version in Focal, Jammy, Kinetic and Lunar are affected.
__
It has been reported that 1.2.13 as well as the patch from LP#1990379 breaks
libxml2 (and libxml) on s390x:
(https://bugzilla.redhat.com/show_bug.cgi?id=2155328). The attached patch
should fix the issue.
The upstream author proposed a fix and a new test for zlib-ng
(https://github.com/zlib-ng/zlib-ng/pull/1390) in order to detect such
breakages in the future.
___
This was initially reported as part of LP#1990379,
especially:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1990379/comments/12
but needs a separate LP bug (number) - this one.
___
The proposed patch at https://launchpadlibrarian.net/641454325/patch-1.2.11
needed some tweaks regarding white-spaces, but then applied fine on focal,
jammy, kinetic and also 1.2.13, which is what we currently have in
lunar-proposed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2002511/+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 1983794] Re: Evolution not deleting autosave files
** Also affects: evolution (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: libcanberra (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Changed in: libcanberra (Ubuntu Kinetic)
Status: New => In Progress
** Changed in: libcanberra (Ubuntu Jammy)
Status: Triaged => In Progress
** Changed in: libcanberra (Ubuntu Kinetic)
Importance: Undecided => Low
** Changed in: libcanberra (Ubuntu Kinetic)
Importance: Low => Medium
** Changed in: evolution (Ubuntu)
Importance: Medium => Low
** Changed in: libcanberra (Ubuntu Kinetic)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
In Progress
Status in libcanberra source package in Jammy:
In Progress
Status in evolution source package in Kinetic:
New
Status in libcanberra source package in Kinetic:
In Progress
Bug description:
[ Impact ]
Autosave files are not removed from evolution local state directories
(and windows leaked)
[ Test case ]
1. Open evolution, and start to compose a new email
2. Write enough text and wait few minutes so that this command returns a file
ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
3. Close the email composer window, hitting "Do not save"
4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
5. Opening and closing again evolution should not ask to restore the previous
email
[ Regression potential ]
No sounds could be performed during some UI actions
---
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 1994146] Re: [SRU] apparmor - Focal, Jammy
** Changed in: apparmor (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 apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1994146 Title: [SRU] apparmor - Focal, Jammy Status in apparmor package in Ubuntu: Confirmed Status in apparmor source package in Focal: Fix Released Status in apparmor source package in Jammy: Fix Committed Bug description: [ Impact ] This is a SRU proposal for apparmor in Focal and Jammy. For focal, we want to SRU fixes for Bug 1964636 which introduces the capability upstream patches. We are also fixing Bug 1728130 and Bug 1993353 which are introducing full backport of abi from apparmor-3.0 and support for POSIX message queue rules, which are both a request from Honeywell. Note that specifically for message queue rules, we are overriding the abi behavior. Message queue mediation is not a part of the 2.13 abi we are pinning. Honeywell has a kernel that has message queue mediation, but their policy does not contain an abi specified, so when we pin the abi for a kernel that does not mediate message queue, it will break Honeywell's AppArmor policies. So we are making an exception: when abi is not specified in the policy, and the policy contain mqueue rules, we are enforcing mqueue rules. When the policy does not contain mqueue rules, then they are not being enforced. This is so we do not break Honeywell policies and we also are not breaking policies that were developed when there was no mqueue or abi support. For jammy, we are SRUing fixes for Bug 1993353 which adds message queue rules support. [ Test Plan ] This has been extensively tested by using QA Regression Tests[1] for AppArmor. All tests have passed and demonstrated AppArmor to be working as expected. We are also adding regression tests for message queue rules[2] which guarantees it is working as expected. [1] https://git.launchpad.net/qa-regression-testing/tree/scripts/test-apparmor.py [2] https://gitlab.com/apparmor/apparmor/-/merge_requests/858 [ Where problems could occur ] The message queue rules support could cause issues for AppArmor policies that were developed before there was support for mqueues, that's why we are also backporting abi support and pinning the abi on parser.conf on focal. Jammy already has the abi pinned for a kernel that does not have support for mqueue mediation. [ Other Info ] The patches for both focal and jammy can be found at: https://launchpad.net/~georgiag/+archive/ubuntu/mqueue-sru/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1994146/+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 1970047] Re: GTK file open dialog hangs Chrome/Brave
Vuk, thank you! It works for me. gsettings set org.gnome.desktop.sound input-feedback-sounds false Browser: Chrome 108.0.5359.124 64bit, Ubuntu OS: Ubuntu 22.04.1 LTS x86_64 Kernel: 5.15.0-57-generic Resolution: 1920x1080, 2560x1440 CPU: Intel i5-7200U (4) @ 3.100GHz GPU: Intel HD Graphics 620 GPU: NVIDIA GeForce 940MX Memory: 6105MiB / 7825MiB -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1970047 Title: GTK file open dialog hangs Chrome/Brave Status in gtk+3.0 package in Ubuntu: Expired Bug description: I removed xdg-desktop-portal because I use Xorg, don't use any snaps or flatpaks and GTK file open dialog is better than portal one. But GTK file open dialog makes Chrome/Brave freeze after closing it. Steps to reproduce: 1. Install Chrome or Brave 2. Remove xdg-desktop-portal so Chrome/Brave use GTK file open dialog instead of portal one 3. Press Ctrl+O to open file open dialog 4. Close dialog or choose any file, does not matter, browser is stuck I don't see this behavior on Debian that I also use, so I guess bug is in GTK rather than Chrome/Brave. Fresh install of Ubuntu 22.04 lsb_release: Description: Ubuntu 22.04 LTS Release: 22.04 libgtk-3-0: Installed: 3.24.33-1ubuntu1 Candidate: 3.24.33-1ubuntu1 Version table: *** 3.24.33-1ubuntu1 500 500 http://rs.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgtk-3-0 3.24.33-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 23 19:27:45 2022 InstallationDate: Installed on 2022-04-22 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1970047/+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 2002511] Re: zlib 1.2.13 (and patched 1.2.11) breaks libxml(2) on s390x
Launchpad has imported 17 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=2155328.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2022-12-20T20:39:24+00:00 lbalhar wrote:
Description of problem:
The latest version of zlib (1.2.13) in rawhide breaks libxml2 (and therefore
lxml). The problem appears during loading a gzipped XML file.
Version-Release number of selected component (if applicable):
zlib-1.2.13-1.fc38.s390x
How reproducible:
Allways.
Steps to Reproduce:
1. echo "" > file.xml
2. gzip file.xml
3. python3
>>> import libxml2
>>> libxml2.parseFile("file.xml.gz")
Actual results:
file.xml.gz:1: parser error : Document is empty
^
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3.11/site-packages/libxml2.py", line 1362, in parseFile
if ret is None:raise parserError('xmlParseFile() failed')
^^
libxml2.parserError: xmlParseFile() failed
Expected results:
Loaded file. It works fine with zlib-1.2.12-5.fc37.s390x.
Additional info:
Might this be caused by the downstream patches we have in Fedora for s390x?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/2002511/comments/0
On 2022-12-21T19:24:28+00:00 iii wrote:
This must be a problem with the latest hardware compression patches.
export DFLTCC=0
makes the problem go away.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/2002511/comments/1
On 2022-12-21T22:18:06+00:00 lbalhar wrote:
Thanks for the info Ilya. Do you know where and how we can fix this?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/2002511/comments/2
On 2022-12-22T01:30:43+00:00 mhroncok wrote:
I can confirm DFLTCC=0 makes the problem go away.
$ python3
..
>>> libxml2.parseFile("file.xml.gz")
file.xml.gz:1: parser error : Document is empty
^
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3.11/site-packages/libxml2.py", line 1362, in parseFile
if ret is None:raise parserError('xmlParseFile() failed')
^^
libxml2.parserError: xmlParseFile() failed
$ DFLTCC=0 python3
...
>>> libxml2.parseFile("file.xml.gz")
Reply at:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/2002511/comments/3
On 2022-12-22T08:56:14+00:00 iii wrote:
Yes, this must be the new strm.adler change - it seems that we should not be
updating this field for raw streams.
I am working on a fix.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/2002511/comments/4
On 2022-12-22T11:01:17+00:00 iii wrote:
Created attachment 1934106
patch for zlib 1.2.11
Reply at:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/2002511/comments/5
On 2022-12-22T11:01:39+00:00 iii wrote:
Created attachment 1934107
patch for zlib 1.2.13
Reply at:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/2002511/comments/6
On 2022-12-22T11:10:21+00:00 iii wrote:
Please try either of the attached patches.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/2002511/comments/7
On 2022-12-22T14:11:45+00:00 lbalhar wrote:
Thanks for the patches. Could one of the package maintainers try it,
please? I've tried to apply it and it does not apply. Looking at the
patches we already have they depend on each other so I don't know
whether I should add this one as a new one or squash it into
zlib-1.2.13-IBM-Z-hw-accelerated-deflate.patch which adds the file the
new patch tries to modify.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/2002511/comments/8
On 2022-12-22T15:19:13+00:00 iii wrote:
Created attachment 1934119
patch for zlib 1.2.13 (rawhide version)
Hm, indeed, the 1.2.13 patch that I posted did not apply to the rawhide
zlib. I generated it against
https://github.com/madler/zlib/pull/410#issuecomment-1353070525, which
is slightly ahead.
I've attached the rebased version; it should go after all the current
rawhide patches, i.e. after Patch23: zlib-1.2.11-covscan-issues-
rhel9.patch.
Reply at:
[Touch-packages] [Bug 2002529] [NEW] package linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned err
Public bug reported: Fresh install près cette opération, 0 o d'espace disque supplémentaires seront utilisés. Paramétrage de initramfs-tools (0.140ubuntu17) ... update-initramfs: deferring update (trigger activated) Paramétrage de linux-firmware (20220923.gitf09bebf3-0ubuntu1.3) ... update-initramfs: Generating /boot/initrd.img-5.19.0-28-generic cpio: erreur d'écriture: Aucun espace disponible sur le périphérique E: mkinitramfs failure cpio 2 update-initramfs: failed for /boot/initrd.img-5.19.0-28-generic with 1. dpkg: erreur de traitement du paquet linux-firmware (--configure) : installed linux-firmware package post-installation script subprocess returned e rror exit status 1 Paramétrage de linux-image-5.19.0-28-generic (5.19.0-28.29) ... Traitement des actions différées (« triggers ») pour initramfs-tools (0.140ubunt u17) ... update-initramfs: Generating /boot/initrd.img-5.19.0-28-generic cpio: erreur d'écriture: Aucun espace disponible sur le périphérique E: mkinitramfs failure cpio 2 update-initramfs: failed for /boot/initrd.img-5.19.0-28-generic with 1. dpkg: erreur de traitement du paquet initramfs-tools (--configure) : installed initramfs-tools package post-installation script subprocess returned error exit status 1 Traitement des actions différées (« triggers ») pour linux-image-5.19.0-28-gener ic (5.19.0-28.29) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.19.0-28-generic ...done. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.19.0-28-generic cpio: erreur d'écriture: Aucun espace disponible sur le périphérique E: mkinitramfs failure cpio 2 update-initramfs: failed for /boot/initrd.img-5.19.0-28-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: erreur de traitement du paquet linux-image-5.19.0-28-generic (--configure) : installed linux-image-5.19.0-28-generic package post-installation script subpro cess returned error exit status 1 Des erreurs ont été rencontrées pendant l'exécution : linux-firmware initramfs-tools linux-image-5.19.0-28-generic pafleury@Bob:~$ df -i Sys. de fichiers Inœuds IUtil.ILibre IUti% Monté sur tmpfs 8219615 1569 82180461% /run /dev/nvme0n1p3 122068992 311467 1217575251% / tmpfs 8219615 1 82196141% /dev/shm tmpfs 8219615 4 82196111% /run/lock tmpfs 8219615 67 82195481% /tmp tmpfs 8219615 6 82196091% /var/spool tmpfs 8219615 25 82195901% /var/tmp /dev/nvme2n1p2 793553772 511886 7930418861% /home/pafleury/PartageWindows /dev/nvme0n1p2 0 0 0 - /boot/efi /dev/sda244195328 719531 2434757971% /home/pafleury/Multimedia /dev/sdb1 244191232 183604 2440076281% /home/pafleury/Vidéos //192.168.1.12/partage/ 0 0 0 - /media/pafleury/DS218_partage //192.168.1.12/music/ 0 0 0 - /media/pafleury/DS218_music //192.168.1.12/video/ 0 0 0 - /media/pafleury/DS218_video //192.168.1.12/photo/ 0 0 0 - /media/pafleury/DS218_photo tmpfs 1643923164 16437591% /run/user/1000 ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pafleury 3152 F wireplumber /dev/snd/controlC2: pafleury 3152 F wireplumber /dev/snd/controlC1: pafleury 3152 F wireplumber /dev/snd/seq:pafleury 3148 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Wed Jan 11 13:39:00 2023 Dependencies: firmware-sof-signed 2.1.1-1ubuntu1.1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-01-06 (4 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp6s0no wireless extensions. enxb04f13f51dd2 no wireless extensions. MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-28-generic root=UUID=c85917c3-d792-4a15-8eb4-df2aa2266795 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu12.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no
[Touch-packages] [Bug 2002511] Re: zlib 1.2.13 (and patched 1.2.11) breaks libxml(2) on s390x
** Bug watch added: Red Hat Bugzilla #2155328
https://bugzilla.redhat.com/show_bug.cgi?id=2155328
** Also affects: zlib via
https://bugzilla.redhat.com/show_bug.cgi?id=2155328
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/2002511
Title:
zlib 1.2.13 (and patched 1.2.11) breaks libxml(2) on s390x
Status in Ubuntu on IBM z Systems:
Triaged
Status in zlib:
Unknown
Status in zlib package in Ubuntu:
In Progress
Status in zlib source package in Focal:
New
Status in zlib source package in Jammy:
New
Status in zlib source package in Kinetic:
New
Status in zlib source package in Lunar:
In Progress
Bug description:
SRU Justification:
--
[ Impact ]
* zlib version 1.2.13, as well as patched zlib versions 1.2.11 with
the patch from LP#1990379, break libxml2 and lxml on s390x.
* The problem appears during loading a gzipped XML file.
* Disabling hw compression with 'export DFLTCC=0' solves this,
hence it's a problem with the hardware acceleration patches DFLTCC.
* For more info see:
https://bugzilla.redhat.com/show_bug.cgi?id=2155328
[ Test Plan ]
* Steps to Reproduce:
1. echo "" > file.xml
2. gzip file.xml
3. python3
>>> import libxml2
>>> libxml2.parseFile("file.xml.gz")
* Actual results:
file.xml.gz:1: parser error : Document is empty
^
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3.11/site-packages/libxml2.py",
line 1362, in parseFile
if ret is None:raise parserError('xmlParseFile() failed')
^^
libxml2.parserError: xmlParseFile() failed
* Expected results:
Loaded file.
[ Where problems could occur ]
* Since this is limited to s390x and DFLTCC / hw acceleration active,
any possible problems are limited to such environments.
* Fix can be broken if the state handling (state->wrap),
or the states mixed.
* The translation from stream to parameter block could be broken
(again due to wrong states) and the inflate as well.
[ Other Info ]
* The official upstream fix is here:
https://github.com/zlib-ng/zlib-ng/pull/1390
but it's for zlib-ng.
* For zlib this needs to be adjusted and was done by the author here:
https://launchpadlibrarian.net/641454325/patch-1.2.11
* And again slightly adjusted by me (renamed, some white-space fixes
and conversion into a quilt patch with proper dep3 header):
https://launchpadlibrarian.net/645435847/1390.patch
* The zlib version in Focal, Jammy, Kinetic and Lunar are affected.
__
It has been reported that 1.2.13 as well as the patch from LP#1990379 breaks
libxml2 (and libxml) on s390x:
(https://bugzilla.redhat.com/show_bug.cgi?id=2155328). The attached patch
should fix the issue.
The upstream author proposed a fix and a new test for zlib-ng
(https://github.com/zlib-ng/zlib-ng/pull/1390) in order to detect such
breakages in the future.
___
This was initially reported as part of LP#1990379,
especially:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1990379/comments/12
but needs a separate LP bug (number) - this one.
___
The proposed patch at https://launchpadlibrarian.net/641454325/patch-1.2.11
needed some tweaks regarding white-spaces, but then applied fine on focal,
jammy, kinetic and also 1.2.13, which is what we currently have in
lunar-proposed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2002511/+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 2002511] Re: zlib 1.2.13 (and patched 1.2.11) breaks libxml(2) on s390x
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/2002511
Title:
zlib 1.2.13 (and patched 1.2.11) breaks libxml(2) on s390x
Status in Ubuntu on IBM z Systems:
Triaged
Status in zlib:
Unknown
Status in zlib package in Ubuntu:
In Progress
Status in zlib source package in Focal:
New
Status in zlib source package in Jammy:
New
Status in zlib source package in Kinetic:
New
Status in zlib source package in Lunar:
In Progress
Bug description:
SRU Justification:
--
[ Impact ]
* zlib version 1.2.13, as well as patched zlib versions 1.2.11 with
the patch from LP#1990379, break libxml2 and lxml on s390x.
* The problem appears during loading a gzipped XML file.
* Disabling hw compression with 'export DFLTCC=0' solves this,
hence it's a problem with the hardware acceleration patches DFLTCC.
* For more info see:
https://bugzilla.redhat.com/show_bug.cgi?id=2155328
[ Test Plan ]
* Steps to Reproduce:
1. echo "" > file.xml
2. gzip file.xml
3. python3
>>> import libxml2
>>> libxml2.parseFile("file.xml.gz")
* Actual results:
file.xml.gz:1: parser error : Document is empty
^
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3.11/site-packages/libxml2.py",
line 1362, in parseFile
if ret is None:raise parserError('xmlParseFile() failed')
^^
libxml2.parserError: xmlParseFile() failed
* Expected results:
Loaded file.
[ Where problems could occur ]
* Since this is limited to s390x and DFLTCC / hw acceleration active,
any possible problems are limited to such environments.
* Fix can be broken if the state handling (state->wrap),
or the states mixed.
* The translation from stream to parameter block could be broken
(again due to wrong states) and the inflate as well.
[ Other Info ]
* The official upstream fix is here:
https://github.com/zlib-ng/zlib-ng/pull/1390
but it's for zlib-ng.
* For zlib this needs to be adjusted and was done by the author here:
https://launchpadlibrarian.net/641454325/patch-1.2.11
* And again slightly adjusted by me (renamed, some white-space fixes
and conversion into a quilt patch with proper dep3 header):
https://launchpadlibrarian.net/645435847/1390.patch
* The zlib version in Focal, Jammy, Kinetic and Lunar are affected.
__
It has been reported that 1.2.13 as well as the patch from LP#1990379 breaks
libxml2 (and libxml) on s390x:
(https://bugzilla.redhat.com/show_bug.cgi?id=2155328). The attached patch
should fix the issue.
The upstream author proposed a fix and a new test for zlib-ng
(https://github.com/zlib-ng/zlib-ng/pull/1390) in order to detect such
breakages in the future.
___
This was initially reported as part of LP#1990379,
especially:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1990379/comments/12
but needs a separate LP bug (number) - this one.
___
The proposed patch at https://launchpadlibrarian.net/641454325/patch-1.2.11
needed some tweaks regarding white-spaces, but then applied fine on focal,
jammy, kinetic and also 1.2.13, which is what we currently have in
lunar-proposed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2002511/+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 2002511] Re: zlib 1.2.13 (and patched 1.2.11) breaks libxml(2) on s390x
** Description changed:
+ SRU Justification:
+ --
+
+ [ Impact ]
+
+ * zlib version 1.2.13, as well as patched zlib versions 1.2.11 with
+the patch from LP#1990379, break libxml2 and lxml on s390x.
+
+ * The problem appears during loading a gzipped XML file.
+
+ * Disabling hw compression with 'export DFLTCC=0' solves this,
+hence it's a problem with the hardware acceleration patches DFLTCC.
+
+ * For more info see:
+ https://bugzilla.redhat.com/show_bug.cgi?id=2155328
+
+ [ Test Plan ]
+
+ * Steps to Reproduce:
+1. echo "" > file.xml
+2. gzip file.xml
+3. python3
+>>> import libxml2
+>>> libxml2.parseFile("file.xml.gz")
+
+ * Actual results:
+file.xml.gz:1: parser error : Document is empty
+^
+Traceback (most recent call last):
+ File "", line 1, in
+ File "/usr/lib/python3.11/site-packages/libxml2.py",
+ line 1362, in parseFile
+if ret is None:raise parserError('xmlParseFile() failed')
+ ^^
+libxml2.parserError: xmlParseFile() failed
+
+ * Expected results:
+Loaded file.
+
+ [ Where problems could occur ]
+
+ * Since this is limited to s390x and DFLTCC / hw acceleration active,
+any possible problems are limited to such environments.
+
+ * Fix can be broken if the state handling (state->wrap),
+or the states mixed.
+
+ * The translation from stream to parameter block could be broken
+(again due to wrong states) and the inflate as well.
+
+ [ Other Info ]
+
+ * The official upstream fix is here:
+https://github.com/zlib-ng/zlib-ng/pull/1390
+but it's for zlib-ng.
+
+ * For zlib this needs to be adjusted and was done by the author here:
+https://launchpadlibrarian.net/641454325/patch-1.2.11
+
+ * And again slightly adjusted by me (renamed, some white-space fixes
+and conversion into a quilt patch with proper dep3 header):
+https://launchpadlibrarian.net/645435847/1390.patch
+
+ * The zlib version in Focal, Jammy, Kinetic and Lunar are affected.
+ __
+
It has been reported that 1.2.13 as well as the patch from LP#1990379 breaks
libxml2 (and libxml) on s390x:
(https://bugzilla.redhat.com/show_bug.cgi?id=2155328). The attached patch
should fix the issue.
The upstream author proposed a fix and a new test for zlib-ng
(https://github.com/zlib-ng/zlib-ng/pull/1390) in order to detect such
breakages in the future.
___
This was initially reported as part of LP#1990379,
especially:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1990379/comments/12
but needs a separate LP bug (number) - this one.
___
The proposed patch at https://launchpadlibrarian.net/641454325/patch-1.2.11
needed some tweaks regarding white-spaces, but then applied fine on focal,
jammy, kinetic and also 1.2.13, which is what we currently have in
lunar-proposed.
** Also affects: zlib (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: zlib (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: zlib (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: zlib (Ubuntu Lunar)
Importance: High
Status: New
** Changed in: ubuntu-z-systems
Status: New => Triaged
** Changed in: zlib (Ubuntu Lunar)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/2002511
Title:
zlib 1.2.13 (and patched 1.2.11) breaks libxml(2) on s390x
Status in Ubuntu on IBM z Systems:
Triaged
Status in zlib package in Ubuntu:
In Progress
Status in zlib source package in Focal:
New
Status in zlib source package in Jammy:
New
Status in zlib source package in Kinetic:
New
Status in zlib source package in Lunar:
In Progress
Bug description:
SRU Justification:
--
[ Impact ]
* zlib version 1.2.13, as well as patched zlib versions 1.2.11 with
the patch from LP#1990379, break libxml2 and lxml on s390x.
* The problem appears during loading a gzipped XML file.
* Disabling hw compression with 'export DFLTCC=0' solves this,
hence it's a problem with the hardware acceleration patches DFLTCC.
* For more info see:
https://bugzilla.redhat.com/show_bug.cgi?id=2155328
[ Test Plan ]
* Steps to Reproduce:
1. echo "" > file.xml
2. gzip file.xml
3. python3
>>> import libxml2
>>> libxml2.parseFile("file.xml.gz")
* Actual results:
file.xml.gz:1: parser error : Document is empty
^
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3.11/site-packages/libxml2.py",
line 1362, in parseFile
if ret is None:raise parserError('xmlParseFile() failed')
^^
libxml2.parserError:
[Touch-packages] [Bug 868395] Re: localtime_r multiple times slower for Europe/Moscow timezone
** Also affects: glibc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/868395
Title:
localtime_r multiple times slower for Europe/Moscow timezone
Status in GLibC:
Unknown
Status in glibc package in Ubuntu:
New
Status in tzdata package in Ubuntu:
Triaged
Bug description:
In version tzdata-2011j (tzdata-2011k also affected) was founded strange bug
in russian timezones.
Because of a law "On the Calculation of Time" there were changes in zone like:
3:00 Russia MSK/MSD 2011
changed to:
3:00 Russia MSK/MSD 2011 Mar 27 2:00s
4:00 - MSK
But if no rule used for this change (using "-" instead of rule "Russia"),
calling of system function localtime_r() takes more time (takes more than 40%
time longer).
I used following code for measuring:
==
#include
#include
int main() {
time_t t = time(0);
int i;
struct tm result;
for(i=0; i < 1000; i++)
localtime_r(, );
puts(ctime());
return 0;
}
==
and also this sql code in mysql db:
select benchmark(100, from_unixtime(1317044847));
For example, when I'm using new tzdata-2011j results are:
1. time ./a.out (c code)
real 0m5.165s
user 0m5.140s
sys 0m0.000s
2. sql query
mysql> select benchmark(100, from_unixtime(1317044847));
+---+
| benchmark(100, from_unixtime(1317044847)) |
+---+
| 0 |
+---+
1 row in set (1.03 sec).
And when I'm using old tzdata-2008b:
1. time ./a.out (c code)
real 0m1.675s
user 0m1.450s
sys 0m0.000s
2. sql query
mysql> select benchmark(100, from_unixtime(1317044847));
+---+
| benchmark(100, from_unixtime(1317044847)) |
+---+
| 0 |
+---+
1 row in set (0.65 sec)
This bug seemed critical on high loaded systems (for example, for
databases that using unix timestamps).
My configuration was:
Description: Ubuntu 8.04.1
Release: 8.04
Packages: 2011j~repack-0ubuntu0.8.04 and 2008b-1ubuntu1
To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/868395/+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 599466] Re: tzdata refers to Americas as "America"
** Changed in: tzdata (Debian) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/599466 Title: tzdata refers to Americas as "America" Status in tzdata package in Ubuntu: Fix Committed Status in tzdata package in Debian: Fix Released Bug description: Binary package hint: tzdata The time zone configuration scripts refer to the Americas as "America". To view this bug, enter "dpkg-reconfigure tzdata". The first page displayed asks you to choose your geographic area, and shows a list that starts with: Africa America ... I'm using Ubuntu 10.04 server. $ lsb_release -rd Description: Ubuntu 10.04 LTS Release: 10.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/599466/+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 868395] Re: localtime_r multiple times slower for Europe/Moscow timezone
** Also affects: zoneinfo via
https://sourceware.org/bugzilla/show_bug.cgi?id=15943
Importance: Unknown
Status: Unknown
** Project changed: zoneinfo => glibc
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/868395
Title:
localtime_r multiple times slower for Europe/Moscow timezone
Status in GLibC:
Unknown
Status in tzdata package in Ubuntu:
Triaged
Bug description:
In version tzdata-2011j (tzdata-2011k also affected) was founded strange bug
in russian timezones.
Because of a law "On the Calculation of Time" there were changes in zone like:
3:00 Russia MSK/MSD 2011
changed to:
3:00 Russia MSK/MSD 2011 Mar 27 2:00s
4:00 - MSK
But if no rule used for this change (using "-" instead of rule "Russia"),
calling of system function localtime_r() takes more time (takes more than 40%
time longer).
I used following code for measuring:
==
#include
#include
int main() {
time_t t = time(0);
int i;
struct tm result;
for(i=0; i < 1000; i++)
localtime_r(, );
puts(ctime());
return 0;
}
==
and also this sql code in mysql db:
select benchmark(100, from_unixtime(1317044847));
For example, when I'm using new tzdata-2011j results are:
1. time ./a.out (c code)
real 0m5.165s
user 0m5.140s
sys 0m0.000s
2. sql query
mysql> select benchmark(100, from_unixtime(1317044847));
+---+
| benchmark(100, from_unixtime(1317044847)) |
+---+
| 0 |
+---+
1 row in set (1.03 sec).
And when I'm using old tzdata-2008b:
1. time ./a.out (c code)
real 0m1.675s
user 0m1.450s
sys 0m0.000s
2. sql query
mysql> select benchmark(100, from_unixtime(1317044847));
+---+
| benchmark(100, from_unixtime(1317044847)) |
+---+
| 0 |
+---+
1 row in set (0.65 sec)
This bug seemed critical on high loaded systems (for example, for
databases that using unix timestamps).
My configuration was:
Description: Ubuntu 8.04.1
Release: 8.04
Packages: 2011j~repack-0ubuntu0.8.04 and 2008b-1ubuntu1
To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/868395/+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 2002470] Re: Software & Updates - Authentication Tab - Restore Defaults - no Trusted Software Providers loaded
** Package changed: ubuntu => software-properties (Ubuntu) ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2002470 Title: Software & Updates - Authentication Tab - Restore Defaults - no Trusted Software Providers loaded Status in software-properties package in Ubuntu: New Bug description: Enabled livepatch on two cleanly installed laptops - entered settings GUI for livepatch by right-clicking on status icon and selecting 'Livepatch Settings...' - navigate to the 'Authentication' tab - click on the 'Restore Defaults' button - on one laptop, keys are loaded from the /etc/apt/ and /etc/apt/trusted.gpg.d folders - on the other, however, nothing happens / no keys are loaded even though the exact same keys are on both machines. I can't determine why these systems behave differently as they were both installed using the exact same USB media using the exact same setup process. Both laptops are configured with: Ubuntu 22.04.1 LTS Livepatch 10.4.1 Gnome Version 42.5 What I expected to happen: Authentication tab's Trusted Software Providers area gets populated with default keys - i.e., Trusted Software Providers' keys are displayed What happened instead: nothing; Authentication tab's Trusted Software Providers area remains blank - i.e., No keys are displayed in the Trusted Software Providers area I don't know if this presents a security vulnerability or not; I guess it depends on whether or not livepatch would retrieve / install packages from untrusted sources? I would expect not, but I'm not certain if that's true. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2002470/+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 2002511] Re: zlib 1.2.13 (and patched 1.2.11) breaks libxml(2) on s390x
PPA test builds a ongoing for F, J, K and L at https://launchpad.net/~fheimes/+archive/ubuntu/lp2002511 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/2002511 Title: zlib 1.2.13 (and patched 1.2.11) breaks libxml(2) on s390x Status in Ubuntu on IBM z Systems: New Status in zlib package in Ubuntu: New Bug description: It has been reported that 1.2.13 as well as the patch from LP#1990379 breaks libxml2 (and libxml) on s390x: (https://bugzilla.redhat.com/show_bug.cgi?id=2155328). The attached patch should fix the issue. The upstream author proposed a fix and a new test for zlib-ng (https://github.com/zlib-ng/zlib-ng/pull/1390) in order to detect such breakages in the future. ___ This was initially reported as part of LP#1990379, especially: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1990379/comments/12 but needs a separate LP bug (number) - this one. ___ The proposed patch at https://launchpadlibrarian.net/641454325/patch-1.2.11 needed some tweaks regarding white-spaces, but then applied fine on focal, jammy, kinetic and also 1.2.13, which is what we currently have in lunar-proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2002511/+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 2002470] [NEW] Software & Updates - Authentication Tab - Restore Defaults - no Trusted Software Providers loaded
You have been subscribed to a public bug: Enabled livepatch on two cleanly installed laptops - entered settings GUI for livepatch by right-clicking on status icon and selecting 'Livepatch Settings...' - navigate to the 'Authentication' tab - click on the 'Restore Defaults' button - on one laptop, keys are loaded from the /etc/apt/ and /etc/apt/trusted.gpg.d folders - on the other, however, nothing happens / no keys are loaded even though the exact same keys are on both machines. I can't determine why these systems behave differently as they were both installed using the exact same USB media using the exact same setup process. Both laptops are configured with: Ubuntu 22.04.1 LTS Livepatch 10.4.1 Gnome Version 42.5 What I expected to happen: Authentication tab's Trusted Software Providers area gets populated with default keys - i.e., Trusted Software Providers' keys are displayed What happened instead: nothing; Authentication tab's Trusted Software Providers area remains blank - i.e., No keys are displayed in the Trusted Software Providers area I don't know if this presents a security vulnerability or not; I guess it depends on whether or not livepatch would retrieve / install packages from untrusted sources? I would expect not, but I'm not certain if that's true. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: livepatch -- Software & Updates - Authentication Tab - Restore Defaults - no Trusted Software Providers loaded https://bugs.launchpad.net/bugs/2002470 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1998942] Re: openssl: merge 3.0.7-1 from Debian unstable
** Patch added: "openssl_3.0.7-1-to-openssl_3.0.7-1ubuntu1~ppa2.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1998942/+attachment/5640640/+files/openssl_3.0.7-1-to-openssl_3.0.7-1ubuntu1~ppa2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1998942 Title: openssl: merge 3.0.7-1 from Debian unstable Status in openssl package in Ubuntu: In Progress Bug description: Debian has moved to 3.0.7 in unstable. Now is a good time to merge it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1998942/+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 1998942] Re: openssl: merge 3.0.7-1 from Debian unstable
Updated patch following Simon's feedback: there was a pretty bad mistake in the debian changelog where I included UNRELEASEd changes from Debian as a dedicated changelog entry. I had to create a new PPA because as part of the changelog fix, I changed the version back to 3.0.7-1ubuntu1 rather than 3.0.7-2ubuntu1. It is at https://launchpad.net/~adrien-n/+archive/ubuntu/merge- openssl-3.0.7-take-two I'm attaching the debdiffs from debian and from ubuntu. ** Patch added: "openssl_3.0.5-2ubuntu2-to-openssl_3.0.7-1ubuntu1~ppa2.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1998942/+attachment/5640639/+files/openssl_3.0.5-2ubuntu2-to-openssl_3.0.7-1ubuntu1~ppa2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1998942 Title: openssl: merge 3.0.7-1 from Debian unstable Status in openssl package in Ubuntu: In Progress Bug description: Debian has moved to 3.0.7 in unstable. Now is a good time to merge it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1998942/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990379] Re: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used
Hi Ilya, yepp, breaking libxml2 is of course an issue. Regarding the fix/patch, you attached here a patch named 'patch-1.2.11'. We have currently the following package versions in the archive: 1.2.11.dfsg-2ubuntu1.5 | focal 1.2.11.dfsg-2ubuntu9.2 | jammy 1.2.11.dfsg-4.1ubuntu1 | kinetic 1.2.13.dfsg-1ubuntu3 | lunar-proposed (After having tweaked the patch a bit regarding white-spaces...) the patch applies fine on focal, jammy and kinetic. I wondered if the patch is also for 1.2.13 (I think so, since the RH bug tells that), which is what we currently have in lunar-proposed - and it actually applies there fine too. I just needed to open a separate LP bug for this, since I need a separate bug number to reference this fix/patch in the changelogs: https://bugs.launchpad.net/bugs/2002511 So regarding the libxml(2) issue, the further work and communication will be there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1990379 Title: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used Status in Ubuntu on IBM z Systems: In Progress Status in zlib package in Ubuntu: In Progress Status in zlib source package in Focal: Triaged Status in zlib source package in Jammy: Triaged Status in zlib source package in Kinetic: In Progress Bug description: SRU Justification: -- [ Impact ] * The zlib function inflate() does not update strm.adler in case DFLTCC is used. * This issue was exposed by Java Certification Kit (JCK) running on z15 hardware and newer and impacts all JDK versions (8,11,17, etc.) that use the system default settings. * The JCK failure impacts the ability to certify Java SDKs on this platform/Linux-distribution combination. * On top the incorrect alder32 result may cause functional issues with Java applications that depend on the result. [ Test Plan ] * An affected Ubuntu release (20.04, 22.04 and 22.10) installed on a z15/LinuxONE III or newer system is needed. * Then it's possible to test the updated package with the help of a small test program (in C) that makes use of the zlib1g library or run the Java Certification Kit. * Test will be done by IBM. [ Where problems could occur ] * The patch is a one-line change: https://launchpadlibrarian.net/626003193/410-lp1990379.patch and there are not many issues to expect. * There could be a potential problem with the adler field in the strm struct. For example in case the struct is not as assumed or contains and unexpected value, which would then ripple through the other fields, too. * Structural changes could be identified with a test build that was done for all affected Ubuntu releases and for all major architectures: https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379 [ Other Info ] * The patch itself is the same for all zlib version in 20.04, 22.04 and 22.10 - no further adjustments were needed. * This bug (LP#1990379) is solved in combination with LP#1982583, so that only one package update is needed. However, this bug affects Kinetic, jammy and Focal, but LP#1982583 only Jammy and Kinetic. * The debdiffs for Kinetic and Jammy should be taken from LP#1982583, and the remaining debdiff for Focal from here. __ == Comment: #0 - Ilya Leoshkevich - 2022-09-21 05:02:24 == inflate() does not update strm.adler if DFLTCC is used. Found with a JDK test. zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349 Updated zlib PR: https://github.com/madler/zlib/pull/410 zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920 zlib diff: https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620 Ubuntu 20.04 and later need to be fixed. --- External link: https://warthogs.atlassian.net/browse/PEI-28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2002511] Re: zlib 1.2.13 (and patched 1.2.11) breaks libxml(2) on s390x
Attaching the slightly modified and renamed patch (original is at LP#1990379), now as quilt patch, with some whitespace adjustments and a proper dep3 header. ** Patch added: "1390.patch" https://bugs.launchpad.net/ubuntu-z-systems/+bug/2002511/+attachment/5640638/+files/1390.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/2002511 Title: zlib 1.2.13 (and patched 1.2.11) breaks libxml(2) on s390x Status in Ubuntu on IBM z Systems: New Status in zlib package in Ubuntu: New Bug description: It has been reported that 1.2.13 as well as the patch from LP#1990379 breaks libxml2 (and libxml) on s390x: (https://bugzilla.redhat.com/show_bug.cgi?id=2155328). The attached patch should fix the issue. The upstream author proposed a fix and a new test for zlib-ng (https://github.com/zlib-ng/zlib-ng/pull/1390) in order to detect such breakages in the future. ___ This was initially reported as part of LP#1990379, especially: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1990379/comments/12 but needs a separate LP bug (number) - this one. ___ The proposed patch at https://launchpadlibrarian.net/641454325/patch-1.2.11 needed some tweaks regarding white-spaces, but then applied fine on focal, jammy, kinetic and also 1.2.13, which is what we currently have in lunar-proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2002511/+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 2002511] Re: zlib 1.2.13 (and patched 1.2.11) breaks libxml(2) on s390x
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/2002511 Title: zlib 1.2.13 (and patched 1.2.11) breaks libxml(2) on s390x Status in Ubuntu on IBM z Systems: New Status in zlib package in Ubuntu: New Bug description: It has been reported that 1.2.13 as well as the patch from LP#1990379 breaks libxml2 (and libxml) on s390x: (https://bugzilla.redhat.com/show_bug.cgi?id=2155328). The attached patch should fix the issue. The upstream author proposed a fix and a new test for zlib-ng (https://github.com/zlib-ng/zlib-ng/pull/1390) in order to detect such breakages in the future. ___ This was initially reported as part of LP#1990379, especially: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1990379/comments/12 but needs a separate LP bug (number) - this one. ___ The proposed patch at https://launchpadlibrarian.net/641454325/patch-1.2.11 needed some tweaks regarding white-spaces, but then applied fine on focal, jammy, kinetic and also 1.2.13, which is what we currently have in lunar-proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2002511/+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 2002511] [NEW] zlib 1.2.13 (and patched 1.2.11) breaks libxml(2) on s390x
Public bug reported: It has been reported that 1.2.13 as well as the patch from LP#1990379 breaks libxml2 (and libxml) on s390x: (https://bugzilla.redhat.com/show_bug.cgi?id=2155328). The attached patch should fix the issue. The upstream author proposed a fix and a new test for zlib-ng (https://github.com/zlib-ng/zlib-ng/pull/1390) in order to detect such breakages in the future. ___ This was initially reported as part of LP#1990379, especially: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1990379/comments/12 but needs a separate LP bug (number) - this one. ___ The proposed patch at https://launchpadlibrarian.net/641454325/patch-1.2.11 needed some tweaks regarding white-spaces, but then applied fine on focal, jammy, kinetic and also 1.2.13, which is what we currently have in lunar-proposed. ** Affects: ubuntu-z-systems Importance: High Status: New ** Affects: zlib (Ubuntu) Importance: High Status: New ** Tags: s390x ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Summary changed: - zlib 1.2.13 breaks libxml(2) on s390x + zlib 1.2.13 (and patched 1.2.11) breaks libxml(2) on s390x ** Changed in: ubuntu-z-systems Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/2002511 Title: zlib 1.2.13 (and patched 1.2.11) breaks libxml(2) on s390x Status in Ubuntu on IBM z Systems: New Status in zlib package in Ubuntu: New Bug description: It has been reported that 1.2.13 as well as the patch from LP#1990379 breaks libxml2 (and libxml) on s390x: (https://bugzilla.redhat.com/show_bug.cgi?id=2155328). The attached patch should fix the issue. The upstream author proposed a fix and a new test for zlib-ng (https://github.com/zlib-ng/zlib-ng/pull/1390) in order to detect such breakages in the future. ___ This was initially reported as part of LP#1990379, especially: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1990379/comments/12 but needs a separate LP bug (number) - this one. ___ The proposed patch at https://launchpadlibrarian.net/641454325/patch-1.2.11 needed some tweaks regarding white-spaces, but then applied fine on focal, jammy, kinetic and also 1.2.13, which is what we currently have in lunar-proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2002511/+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 2002428] Re: Autopkgtest failure due to moved testcase
Attached patch. The crux is: --- coreutils-9.1/debian/tests/upstream2022-12-08 14:47:43.0 +0100 +++ coreutils-9.1/debian/tests/upstream2023-01-10 14:19:26.0 +0100 @@ -136,7 +136,7 @@ ls/m-option.sh \ ls/multihardlink.sh \ ls/no-arg.sh \ -ls/proc-selinux-segfault.sh \ +ls/selinux-segfault.sh \ ls/recursive.sh \ ls/root-rel-symlink-color.sh \ ls/rt-1.sh \ PPA with fixed package is available at https://launchpad.net/~adrien-n/+archive/ubuntu/coreutils-fix-autopkgtest . ** Patch added: "coreutils-fix-autopkgtest.debdiff" https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2002428/+attachment/5640612/+files/coreutils-fix-autopkgtest.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2002428 Title: Autopkgtest failure due to moved testcase Status in coreutils package in Ubuntu: New Bug description: In 9.1-1ubuntu1 (lunar), a testcase has been renamed from proc- selinux-segfault.sh to selinux-segfault.sh . This changes debian/tests/upstream to reflect the change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2002428/+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
