[Touch-packages] [Bug 1982441] Re: package python2.7-minimal 2.7.18-1~20.04.3 failed to install/upgrade: installed python2.7-minimal package post-installation script subprocess returned error exit sta
** Tags removed: need-duplicate-check -- 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/1982441 Title: package python2.7-minimal 2.7.18-1~20.04.3 failed to install/upgrade: installed python2.7-minimal package post-installation script subprocess returned error exit status 139 Status in python2.7 package in Ubuntu: New Bug description: idk ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python2.7-minimal 2.7.18-1~20.04.3 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jul 20 19:58:35 2022 DuplicateSignature: package:python2.7-minimal:2.7.18-1~20.04.3 Setting up python2.7-minimal (2.7.18-1~20.04.3) ... Segmentation fault (core dumped) dpkg: error processing package python2.7-minimal (--configure): installed python2.7-minimal package post-installation script subprocess returned error exit status 139 ErrorMessage: installed python2.7-minimal package post-installation script subprocess returned error exit status 139 InstallationDate: Installed on 2022-07-06 (14 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: python2.7 Title: package python2.7-minimal 2.7.18-1~20.04.3 failed to install/upgrade: installed python2.7-minimal package post-installation script subprocess returned error exit status 139 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1982441/+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 1982441] [NEW] package python2.7-minimal 2.7.18-1~20.04.3 failed to install/upgrade: installed python2.7-minimal package post-installation script subprocess returned error exit s
Public bug reported: idk ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python2.7-minimal 2.7.18-1~20.04.3 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jul 20 19:58:35 2022 DuplicateSignature: package:python2.7-minimal:2.7.18-1~20.04.3 Setting up python2.7-minimal (2.7.18-1~20.04.3) ... Segmentation fault (core dumped) dpkg: error processing package python2.7-minimal (--configure): installed python2.7-minimal package post-installation script subprocess returned error exit status 139 ErrorMessage: installed python2.7-minimal package post-installation script subprocess returned error exit status 139 InstallationDate: Installed on 2022-07-06 (14 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: python2.7 Title: package python2.7-minimal 2.7.18-1~20.04.3 failed to install/upgrade: installed python2.7-minimal package post-installation script subprocess returned error exit status 139 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python2.7 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1982441 Title: package python2.7-minimal 2.7.18-1~20.04.3 failed to install/upgrade: installed python2.7-minimal package post-installation script subprocess returned error exit status 139 Status in python2.7 package in Ubuntu: New Bug description: idk ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python2.7-minimal 2.7.18-1~20.04.3 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jul 20 19:58:35 2022 DuplicateSignature: package:python2.7-minimal:2.7.18-1~20.04.3 Setting up python2.7-minimal (2.7.18-1~20.04.3) ... Segmentation fault (core dumped) dpkg: error processing package python2.7-minimal (--configure): installed python2.7-minimal package post-installation script subprocess returned error exit status 139 ErrorMessage: installed python2.7-minimal package post-installation script subprocess returned error exit status 139 InstallationDate: Installed on 2022-07-06 (14 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: python2.7 Title: package python2.7-minimal 2.7.18-1~20.04.3 failed to install/upgrade: installed python2.7-minimal package post-installation script subprocess returned error exit status 139 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1982441/+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 1971715] Re: 22.04 idn -a domain.com idn: could not convert from ASCII to UTF-8
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libidn (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1971715 Title: 22.04 idn -a domain.com idn: could not convert from ASCII to UTF-8 Status in libidn package in Ubuntu: Confirmed Bug description: On Ubuntu 22.04 Jammy: idn -a "xxx-tést.eu" idn: could not convert from ASCII to UTF-8 And idn -u "xn--xxx-tst-fya.eu" idn: could not convert from UTF-8 to ASCII Expected: Successfully conversion from ASCII to UTF-8 Ubuntu 20.04 / 18.04 it works fine Also with idn2 from UTF-8 to ASCII works as expected how ever support lacks from ASCII to UTF-8 Description: Ubuntu 22.04 LTS Release: 22.04 root@test:~# echo $LC_ALL C.UTF-8 root@test:~# apt-cache policy idn idn: Installed: 1.38-4build1 Candidate: 1.38-4build1 Version table: *** 1.38-4build1 500 500 https://mirror.hetzner.com/ubuntu/packages jammy/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1971715/+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 1972123] Re: Online accounts crashes on sign in
[Expired for gnome-online-accounts (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-online-accounts (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1972123 Title: Online accounts crashes on sign in Status in gnome-online-accounts package in Ubuntu: Expired Bug description: I noticed that my to-dos weren't syncing, so I checked online accounts and there's this triangle warning icon. I click into it and it says "Credentials have expired", "Sign in to enable this account." Now when I click "Sign in", the pop up changes to a frozen progress bar on top and with empty content, then crashes after a few seconds. Now I can't sync anything and can't fix it. Ubuntu 22.04 LTS, Wayland on Nvidia 510 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1972123/+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 1982334] Re: Crash
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Summary changed: - Xorg crash + Crash ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: 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/1982334 Title: Crash Status in Ubuntu: Incomplete Bug description: System crashed suddenly while working and log in window shows up. Automatically logged out of system and all the applications closed down. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 20 17:03:14 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f9] InstallationDate: Installed on 2022-04-22 (88 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 34601F4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=be040347-6300-407e-9e19-da58389c3a6f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2013 dmi.bios.release: 2.59 dmi.bios.vendor: LENOVO dmi.bios.version: G6ET99WW (2.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 34601F4 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnLENOVO:bvrG6ET99WW(2.59):bd11/19/2013:br2.59:efr1.4:svnLENOVO:pn34601F4:pvrThinkPadX1Carbon:rvnLENOVO:rn34601F4:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_3460: dmi.product.family: ThinkPad X1 Carbon dmi.product.name: 34601F4 dmi.product.sku: LENOVO_MT_3460 dmi.product.version: ThinkPad X1 Carbon dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/+bug/1982334/+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 1971280] Re: Merge heimdal from Debian unstable for kinetic
** Changed in: heimdal (Ubuntu) Assignee: Utkarsh Gupta (utkarsh) => Bryce Harrington (bryce) ** Changed in: heimdal (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1971280 Title: Merge heimdal from Debian unstable for kinetic Status in heimdal package in Ubuntu: In Progress Bug description: Upstream: tbd Debian: 7.7.0+dfsg-3 Ubuntu: 7.7.0+dfsg-3ubuntu1 ### New Debian Changes ### heimdal (7.7.0+dfsg-3) unstable; urgency=high * Fix CVE-2021-3671: A null pointer de-reference was found in the way samba kerberos server handled missing sname in TGS-REQ. Closes: #996586. * Fix autoconf 2.7 issues. -- Brian May Wed, 17 Nov 2021 12:12:45 +1100 heimdal (7.7.0+dfsg-2) unstable; urgency=medium * Build using python3. Closes: #936695, #960032. -- Brian May Tue, 12 May 2020 06:56:04 +1000 heimdal (7.7.0+dfsg-1) unstable; urgency=medium * New upstream version. * Fix CVE-2019-14870: The DelegationNotAllowed Kerberos feature restriction was not being applied when processing protocol transition requests (S4U2Self), in the AD DC KDC. Closes: #946786. -- Brian May Tue, 17 Dec 2019 20:23:41 +1100 heimdal (7.5.0+dfsg-3) unstable; urgency=high * CVE-2018-16860: Samba AD DC S4U2Self/S4U2Proxy unkeyed checksum. Closes: #928966. * CVE-2019-12098: Always confirm PA-PKINIT-KX for anon PKINIT. Closes: #929064. * Update test certificates to pre 2038 expiry. Closes: #923930. -- Brian May Tue, 21 May 2019 18:04:35 +1000 heimdal (7.5.0+dfsg-2.1) unstable; urgency=medium * Non-maintainer upload * Add patch to create headers before building (Closes: 906623) -- Hilko Bengen Sun, 28 Oct 2018 15:10:44 +0100 heimdal (7.5.0+dfsg-2) unstable; urgency=medium * Replace 'MAXHOSTNAMELEN' with 'MaxHostNameLen' in kdc/kx509.c for The Hurd. Closes: #900079. -- Brian May Sat, 02 Jun 2018 10:01:46 +1000 heimdal (7.5.0+dfsg-1) unstable; urgency=high * New upstream version. (Closes: #850723) + CVE-2017-17439: Remote unauthenticated DoS in Heimdal-KDC 7.4 (Closes: #878144, #868157) + Refresh patches. * Bump Standards-Version to 4.1.2 and compat level to 10. + Remove explicit reference to dh-autoreconf. * Use uscan to get orig source. + Refrain from mangling some bundled RFC texts; just exclude the mas they are not installed into any binary anyway. + Update d/copyright to DEP-5. + Can now use standard uscan/gbp/pristine-tar workflow. * Fix some lintian errors/warnings. + Strip trailing whitespace from changelog. + Fix some duplicate long descriptions. + Use optional priority everywhere. + Update/remove some overrides. + Enforce set -e in maintainer scripts. + Enable hardening. * Migrate to -dbgsym. * Add myself to uploaders. -- Dominik George Fri, 15 Dec 2017 01:13:04 +0100 heimdal (7.4.0.dfsg.1-2) unstable; urgency=medium [ Jelmer Vernooij ] * Remove myself from uploaders. [ Brian May ] * Be explicit with heimdal.mkey filename in postinst. Closes: #868638. * Tests should respect DEB_BUILD_OPTIONS=nocheck. Closes: #868842. -- Brian May Sun, 23 Jul 2017 10:32:34 +1000 heimdal (7.4.0.dfsg.1-1) unstable; urgency=high * New upstream version. * Update standards version to 4.0.0. * CVE-2017-11103: Fix Orpheus' Lyre KDC-REP service name validation. (Closes: #868208). -- Brian May Sat, 15 Jul 2017 19:47:32 +1000 heimdal (7.1.0+dfsg-13) unstable; urgency=medium * Add missing symbols base64_decode and base64_encode back into libroken. Closes: #848694. -- Brian May Wed, 26 Apr 2017 19:38:20 +1000 heimdal (7.1.0+dfsg-12) unstable; urgency=high ### Old Ubuntu Delta ### heimdal (7.7.0+dfsg-3ubuntu1) jammy; urgency=medium * Merge with Debian unstable (LP: #1946860). Remaining changes: - Disable lto, to regain dep on roken, otherwise dependencies on amd64 are different to i386 resulting in different files on amd64 and i386. LP #1934936 - Remove symbol rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 (LP #1945787) -- Andreas Hasenack Wed, 08 Dec 2021 18:02:13 -0300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1971280/+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 1982355] Re: gdk-pixbuf-query-loaders binary path not included in pkgconfig file
Awesome! Thanks seb! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1982355 Title: gdk-pixbuf-query-loaders binary path not included in pkgconfig file Status in gdk-pixbuf package in Ubuntu: In Progress Bug description: The gdk-pixbuf-query-loaders binary path is supposed to be reported in the .pc file variable gdk_pixbuf_query_loaders so that it can be queried: $ pkg-config --variable=gdk_pixbuf_query_loaders gdk-pixbuf-2.0 /usr/bin/gdk-pixbuf-query-loaders However in Ubuntu the binary is in /usr/lib/`gcc -dumpmachine`/gdk- pixbuf-2.0/gdk-pixbuf-query-loaders This poses a challenge to build scripts for pixbuf loaders as they need to adapt to this distro-specific paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982355/+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 1982430] [NEW] nm's -U flag does not work
Public bug reported: nm appears to behave as if the -U flag took an argument: $ nm -DU /usr/lib/x86_64-linux-gnu/libc.so.6 nm: 'a.out': No such file $ nm -DU . /usr/lib/x86_64-linux-gnu/libc.so.6 [3006 lines] ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: binutils 2.38.90.20220713-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Wed Jul 20 23:53:19 2022 InstallationDate: Installed on 2022-06-26 (24 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220624) SourcePackage: binutils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: binutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1982430 Title: nm's -U flag does not work Status in binutils package in Ubuntu: New Bug description: nm appears to behave as if the -U flag took an argument: $ nm -DU /usr/lib/x86_64-linux-gnu/libc.so.6 nm: 'a.out': No such file $ nm -DU . /usr/lib/x86_64-linux-gnu/libc.so.6 [3006 lines] ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: binutils 2.38.90.20220713-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Wed Jul 20 23:53:19 2022 InstallationDate: Installed on 2022-06-26 (24 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220624) SourcePackage: binutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1982430/+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 1981431] Re: systemd-resolved: DNSSEC validation failed: incompatible-server
That would be helpful. You can turn on debug-level logging for systemd- resolved by running `systemctl edit systemd-resolved`, and add the following line to the [Service] section: Environment=SYSTEMD_LOG_LEVEL Then `systemctl restart systemd-resolved`. When you have some debug logs from an occurrence of this issue, I can take another look. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1981431 Title: systemd-resolved: DNSSEC validation failed: incompatible-server Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Incomplete Bug description: Hi, I'm running Ubuntu 22.04 using systemd 249.11-0ubuntu3.4. 2 days ago, I enabled DNSSEC=true through: # grep DNSSEC /etc/systemd/resolved.conf.d/dnssec.conf DNSSEC=yes After running some hours, systemd-resolved stop working. Log lines like incompatible-server starts to spam. Jul 09 13:51:41 htdocs systemd[1]: Starting Network Name Resolution... Jul 09 13:51:41 htdocs systemd-resolved[77507]: Positive Trust Anchors: Jul 09 13:51:41 htdocs systemd-resolved[77507]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Jul 09 13:51:41 htdocs systemd-resolved[77507]: Negative trust anchors: int.creativesandbox.de Jul 09 13:51:41 htdocs systemd-resolved[77507]: Using system hostname 'htdocs'. Jul 09 13:51:41 htdocs systemd[1]: Started Network Name Resolution. Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 214.162.in-addr.arpa IN SOA: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 76.214.162.in-addr.arpa IN DS: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 126.76.214.162.in-addr.arpa IN DS: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 126.76.214.162.in-addr.arpa IN SOA: no-signature Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question . IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question de IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question your-server.de IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question clients.your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 201.138.clients.your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question static.237.11.201.138.clients.your-server.de IN : incompatible-server Mention here, I'm running multiple machines with the same config against the same upstream DNS server. From time to time, only one instance is stop working here. Running a manual query also fails here, for example: # resolvectl query noc3.wordfence.com noc3.wordfence.com: resolve call failed: DNSSEC validation failed: incompatible-server Running 'resolvectl reset-server-features' helps here and can be considered as workaround. # resolvectl query noc3.wordfence.com noc3.wordfence.com: resolve call failed: DNSSEC validation failed: incompatible-server # resolvectl reset-server-features # resolvectl query noc3.wordfence.com noc3.wordfence.com: 35.155.126.231 -- link: eth0 -- Information acquired via protocol DNS in 26.5ms. -- Data is authenticated: no; Data was acquired via local or encrypted transport: no -- Data from: network By reading issues upstream looks like https://github.com/systemd/systemd/issues/6490. A fix is implemented (https://github.com/systemd/systemd/pull/18624) and released in 248 which is included in Ubuntu 22.04. But there is another fix around this issue (https://github.com/systemd/systemd/pull/20214) which is released in systemd 250. I would like to know if it's possible to backport this fix into Ubuntu 22.04. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981431/+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 1982422] [NEW] Multiple vulnerabilities in Bionic, Focal and Jammy
*** This bug is a security vulnerability *** Public security bug reported: The version in Bionic is vulnerable to all CVEs listed below. The versions in Focal and Jammy are vulnerable to CVE-2022-30067 and CVE-2022-32990. Please publish patched packages. ** Affects: gimp (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public Security ** Also affects: gimp (Ubuntu) Importance: Undecided Status: New ** No longer affects: gtk+2.0 (Ubuntu) ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-30067 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-32990 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12713 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1982422 Title: Multiple vulnerabilities in Bionic, Focal and Jammy Status in gimp package in Ubuntu: New Bug description: The version in Bionic is vulnerable to all CVEs listed below. The versions in Focal and Jammy are vulnerable to CVE-2022-30067 and CVE-2022-32990. Please publish patched packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1982422/+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 1981431] Re: systemd-resolved: DNSSEC validation failed: incompatible-server
** Changed in: systemd (Ubuntu Jammy) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1981431 Title: systemd-resolved: DNSSEC validation failed: incompatible-server Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Incomplete Bug description: Hi, I'm running Ubuntu 22.04 using systemd 249.11-0ubuntu3.4. 2 days ago, I enabled DNSSEC=true through: # grep DNSSEC /etc/systemd/resolved.conf.d/dnssec.conf DNSSEC=yes After running some hours, systemd-resolved stop working. Log lines like incompatible-server starts to spam. Jul 09 13:51:41 htdocs systemd[1]: Starting Network Name Resolution... Jul 09 13:51:41 htdocs systemd-resolved[77507]: Positive Trust Anchors: Jul 09 13:51:41 htdocs systemd-resolved[77507]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Jul 09 13:51:41 htdocs systemd-resolved[77507]: Negative trust anchors: int.creativesandbox.de Jul 09 13:51:41 htdocs systemd-resolved[77507]: Using system hostname 'htdocs'. Jul 09 13:51:41 htdocs systemd[1]: Started Network Name Resolution. Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 214.162.in-addr.arpa IN SOA: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 76.214.162.in-addr.arpa IN DS: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 126.76.214.162.in-addr.arpa IN DS: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 126.76.214.162.in-addr.arpa IN SOA: no-signature Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question . IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question de IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question your-server.de IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question clients.your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 201.138.clients.your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question static.237.11.201.138.clients.your-server.de IN : incompatible-server Mention here, I'm running multiple machines with the same config against the same upstream DNS server. From time to time, only one instance is stop working here. Running a manual query also fails here, for example: # resolvectl query noc3.wordfence.com noc3.wordfence.com: resolve call failed: DNSSEC validation failed: incompatible-server Running 'resolvectl reset-server-features' helps here and can be considered as workaround. # resolvectl query noc3.wordfence.com noc3.wordfence.com: resolve call failed: DNSSEC validation failed: incompatible-server # resolvectl reset-server-features # resolvectl query noc3.wordfence.com noc3.wordfence.com: 35.155.126.231 -- link: eth0 -- Information acquired via protocol DNS in 26.5ms. -- Data is authenticated: no; Data was acquired via local or encrypted transport: no -- Data from: network By reading issues upstream looks like https://github.com/systemd/systemd/issues/6490. A fix is implemented (https://github.com/systemd/systemd/pull/18624) and released in 248 which is included in Ubuntu 22.04. But there is another fix around this issue (https://github.com/systemd/systemd/pull/20214) which is released in systemd 250. I would like to know if it's possible to backport this fix into Ubuntu 22.04. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981431/+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 1981431] Re: systemd-resolved: DNSSEC validation failed: incompatible-server
I'm able to assist here, e.g. by enable debugging logs. I need some instructions what I should setup and have to provide here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1981431 Title: systemd-resolved: DNSSEC validation failed: incompatible-server Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Incomplete Bug description: Hi, I'm running Ubuntu 22.04 using systemd 249.11-0ubuntu3.4. 2 days ago, I enabled DNSSEC=true through: # grep DNSSEC /etc/systemd/resolved.conf.d/dnssec.conf DNSSEC=yes After running some hours, systemd-resolved stop working. Log lines like incompatible-server starts to spam. Jul 09 13:51:41 htdocs systemd[1]: Starting Network Name Resolution... Jul 09 13:51:41 htdocs systemd-resolved[77507]: Positive Trust Anchors: Jul 09 13:51:41 htdocs systemd-resolved[77507]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Jul 09 13:51:41 htdocs systemd-resolved[77507]: Negative trust anchors: int.creativesandbox.de Jul 09 13:51:41 htdocs systemd-resolved[77507]: Using system hostname 'htdocs'. Jul 09 13:51:41 htdocs systemd[1]: Started Network Name Resolution. Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 214.162.in-addr.arpa IN SOA: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 76.214.162.in-addr.arpa IN DS: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 126.76.214.162.in-addr.arpa IN DS: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 126.76.214.162.in-addr.arpa IN SOA: no-signature Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question . IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question de IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question your-server.de IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question clients.your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 201.138.clients.your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question static.237.11.201.138.clients.your-server.de IN : incompatible-server Mention here, I'm running multiple machines with the same config against the same upstream DNS server. From time to time, only one instance is stop working here. Running a manual query also fails here, for example: # resolvectl query noc3.wordfence.com noc3.wordfence.com: resolve call failed: DNSSEC validation failed: incompatible-server Running 'resolvectl reset-server-features' helps here and can be considered as workaround. # resolvectl query noc3.wordfence.com noc3.wordfence.com: resolve call failed: DNSSEC validation failed: incompatible-server # resolvectl reset-server-features # resolvectl query noc3.wordfence.com noc3.wordfence.com: 35.155.126.231 -- link: eth0 -- Information acquired via protocol DNS in 26.5ms. -- Data is authenticated: no; Data was acquired via local or encrypted transport: no -- Data from: network By reading issues upstream looks like https://github.com/systemd/systemd/issues/6490. A fix is implemented (https://github.com/systemd/systemd/pull/18624) and released in 248 which is included in Ubuntu 22.04. But there is another fix around this issue (https://github.com/systemd/systemd/pull/20214) which is released in systemd 250. I would like to know if it's possible to backport this fix into Ubuntu 22.04. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981431/+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 1981431] Re: systemd-resolved: DNSSEC validation failed: incompatible-server
If you have not already, I would suggest opening a new upstream issue. After a quick look through https://github.com/systemd/systemd/issues, it seems there have been many closely related DNSSEC issues, so it is not obvious to me if there is a patch for your issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1981431 Title: systemd-resolved: DNSSEC validation failed: incompatible-server Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Incomplete Bug description: Hi, I'm running Ubuntu 22.04 using systemd 249.11-0ubuntu3.4. 2 days ago, I enabled DNSSEC=true through: # grep DNSSEC /etc/systemd/resolved.conf.d/dnssec.conf DNSSEC=yes After running some hours, systemd-resolved stop working. Log lines like incompatible-server starts to spam. Jul 09 13:51:41 htdocs systemd[1]: Starting Network Name Resolution... Jul 09 13:51:41 htdocs systemd-resolved[77507]: Positive Trust Anchors: Jul 09 13:51:41 htdocs systemd-resolved[77507]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Jul 09 13:51:41 htdocs systemd-resolved[77507]: Negative trust anchors: int.creativesandbox.de Jul 09 13:51:41 htdocs systemd-resolved[77507]: Using system hostname 'htdocs'. Jul 09 13:51:41 htdocs systemd[1]: Started Network Name Resolution. Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 214.162.in-addr.arpa IN SOA: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 76.214.162.in-addr.arpa IN DS: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 126.76.214.162.in-addr.arpa IN DS: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 126.76.214.162.in-addr.arpa IN SOA: no-signature Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question . IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question de IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question your-server.de IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question clients.your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 201.138.clients.your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question static.237.11.201.138.clients.your-server.de IN : incompatible-server Mention here, I'm running multiple machines with the same config against the same upstream DNS server. From time to time, only one instance is stop working here. Running a manual query also fails here, for example: # resolvectl query noc3.wordfence.com noc3.wordfence.com: resolve call failed: DNSSEC validation failed: incompatible-server Running 'resolvectl reset-server-features' helps here and can be considered as workaround. # resolvectl query noc3.wordfence.com noc3.wordfence.com: resolve call failed: DNSSEC validation failed: incompatible-server # resolvectl reset-server-features # resolvectl query noc3.wordfence.com noc3.wordfence.com: 35.155.126.231 -- link: eth0 -- Information acquired via protocol DNS in 26.5ms. -- Data is authenticated: no; Data was acquired via local or encrypted transport: no -- Data from: network By reading issues upstream looks like https://github.com/systemd/systemd/issues/6490. A fix is implemented (https://github.com/systemd/systemd/pull/18624) and released in 248 which is included in Ubuntu 22.04. But there is another fix around this issue (https://github.com/systemd/systemd/pull/20214) which is released in systemd 250. I would like to know if it's possible to backport this fix into Ubuntu 22.04. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981431/+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 1981431] Re: systemd-resolved: DNSSEC validation failed: incompatible-server
> But there is another fix around this issue (https://github.com/systemd/systemd/pull/20214) which is released in systemd 250. Taking a closer look, this was actually backported to 249.4 [1] and is present in Jammy, so this appears to be a similar but different issue. [1] https://github.com/systemd/systemd- stable/commit/8280bec34df8e35592f4a4a549127471a9199231 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1981431 Title: systemd-resolved: DNSSEC validation failed: incompatible-server Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: New Bug description: Hi, I'm running Ubuntu 22.04 using systemd 249.11-0ubuntu3.4. 2 days ago, I enabled DNSSEC=true through: # grep DNSSEC /etc/systemd/resolved.conf.d/dnssec.conf DNSSEC=yes After running some hours, systemd-resolved stop working. Log lines like incompatible-server starts to spam. Jul 09 13:51:41 htdocs systemd[1]: Starting Network Name Resolution... Jul 09 13:51:41 htdocs systemd-resolved[77507]: Positive Trust Anchors: Jul 09 13:51:41 htdocs systemd-resolved[77507]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Jul 09 13:51:41 htdocs systemd-resolved[77507]: Negative trust anchors: int.creativesandbox.de Jul 09 13:51:41 htdocs systemd-resolved[77507]: Using system hostname 'htdocs'. Jul 09 13:51:41 htdocs systemd[1]: Started Network Name Resolution. Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 214.162.in-addr.arpa IN SOA: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 76.214.162.in-addr.arpa IN DS: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 126.76.214.162.in-addr.arpa IN DS: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 126.76.214.162.in-addr.arpa IN SOA: no-signature Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question . IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question de IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question your-server.de IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question clients.your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 201.138.clients.your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question static.237.11.201.138.clients.your-server.de IN : incompatible-server Mention here, I'm running multiple machines with the same config against the same upstream DNS server. From time to time, only one instance is stop working here. Running a manual query also fails here, for example: # resolvectl query noc3.wordfence.com noc3.wordfence.com: resolve call failed: DNSSEC validation failed: incompatible-server Running 'resolvectl reset-server-features' helps here and can be considered as workaround. # resolvectl query noc3.wordfence.com noc3.wordfence.com: resolve call failed: DNSSEC validation failed: incompatible-server # resolvectl reset-server-features # resolvectl query noc3.wordfence.com noc3.wordfence.com: 35.155.126.231 -- link: eth0 -- Information acquired via protocol DNS in 26.5ms. -- Data is authenticated: no; Data was acquired via local or encrypted transport: no -- Data from: network By reading issues upstream looks like https://github.com/systemd/systemd/issues/6490. A fix is implemented (https://github.com/systemd/systemd/pull/18624) and released in 248 which is included in Ubuntu 22.04. But there is another fix around this issue (https://github.com/systemd/systemd/pull/20214) which is released in systemd 250. I would like to know if it's possible to backport this fix into Ubuntu 22.04. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981431/+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 283115] Re: Gimp: toolbox windows can't be minimized
** Changed in: gimp (Ubuntu) Status: Confirmed => Fix Released ** Also affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New ** Bug watch added: bugzilla.gnome.org/ #586664 https://bugzilla.gnome.org/show_bug.cgi?id=586664 ** Also affects: gtk via https://bugzilla.gnome.org/show_bug.cgi?id=586664 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/283115 Title: Gimp: toolbox windows can't be minimized Status in The Gimp: Fix Released Status in GTK+: Unknown Status in gimp package in Ubuntu: Fix Released Status in gtk+2.0 package in Ubuntu: New Bug description: gimp 2.6 in intrepid: it is impossible to minimize toolbar windows; they have only a x-Button to close ideally, these windows should be minimized automatically when the (last) Gimp image window is minimized Update While waiting, I designed some sort of workaround : Gnome>System>Preferences>Windows>Double-click titlebar>Roll up To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/283115/+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 1880989] Re: libasound2-plugins-extra is built from outdated ALSA source
This bug was fixed in the package alsa-plugins - 1.2.7.1-1ubuntu1 --- alsa-plugins (1.2.7.1-1ubuntu1) kinetic; urgency=medium * Drop the Ubuntu exclusions from debian/rules; alsa-plugins-extra no longer needs to be a separate source package, we should build the modules here. Also, libasound2-plugins itself has now dropped to universe, so Conflicts/Replaces/Provides: this package rather than building it as a separate binary package here; if pulseaudio + libasound2-plugins came back to main, the binaries should be split again. LP: #1880989. -- Steve Langasek Wed, 20 Jul 2022 13:26:37 + ** Changed in: alsa-plugins (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1880989 Title: libasound2-plugins-extra is built from outdated ALSA source Status in alsa-plugins package in Ubuntu: Fix Released Status in alsa-plugins-extra package in Ubuntu: Won't Fix Bug description: Notice the versions, 1.2.2 is current and libasound2-plugins-extra is build from 1.1.0 sources: ii libasound2-plugins:amd64 1.2.2-1ubuntu1 amd64ALSA library additional plugins ii libasound2-plugins-extra:amd64 1.1.0-1ubuntu2 amd64ALSA library additional plugins I would like to see it updated to 1.2.2, in order to incorporate fixes such as https://github.com/alsa-project/alsa-plugins/commit/cdff2e32537440bf16329c8440d0d02d7ac02d38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1880989/+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 1982355] Re: gdk-pixbuf-query-loaders binary path not included in pkgconfig file
Thanks, indeed Debian moves that file to a versioned location to avoid conflict between api versions but the .pc should be updated to reflect that, I proposed a fix for it on https://salsa.debian.org/gnome- team/gdk-pixbuf/-/merge_requests/3 now ** Changed in: gdk-pixbuf (Ubuntu) Importance: Undecided => Low ** Changed in: gdk-pixbuf (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) ** Changed in: gdk-pixbuf (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1982355 Title: gdk-pixbuf-query-loaders binary path not included in pkgconfig file Status in gdk-pixbuf package in Ubuntu: In Progress Bug description: The gdk-pixbuf-query-loaders binary path is supposed to be reported in the .pc file variable gdk_pixbuf_query_loaders so that it can be queried: $ pkg-config --variable=gdk_pixbuf_query_loaders gdk-pixbuf-2.0 /usr/bin/gdk-pixbuf-query-loaders However in Ubuntu the binary is in /usr/lib/`gcc -dumpmachine`/gdk- pixbuf-2.0/gdk-pixbuf-query-loaders This poses a challenge to build scripts for pixbuf loaders as they need to adapt to this distro-specific paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982355/+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 1960307] Re: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices
We could perhaps add a conflict to force removal of bluez-alsa-utils but that package is in universe and not part of a normal installation so that shouldn't be an issue for most users -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1960307 Title: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices Status in PulseAudio: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Confirmed Status in gstreamer1.0 package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Incomplete Bug description: After the announcements of PulseAudio 15 and Gstreamer 1.20, which both advertised LDAC and AptX (HD) support, I expected that jammy (22.04) would support those codecs. Though in reality it seems that something is missing, gstreamer reports that those codecs are supported but "pactl [...] list-codec" only lists sbc (and variants). Checking here https://packages.ubuntu.com/jammy/pulseaudio-module- bluetooth it seems that PulseAudio is not built with gstreamer support, is that the current blocker? To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1960307/+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 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
I have the same problem as Philipp Jungkamp and Clem Schum on the Yoga 9 14IAP7 on Ubuntu 22.04. Hope this can get fixed soon, thank you very much to everyone who is involved! -- 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/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 1979879] Re: Apparmor profile in 22.04 jammy - fails to start when printing enabled
** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => Michał Małoszewski (michal-maloszewski99) ** Changed in: apparmor (Ubuntu Jammy) Assignee: (unassigned) => Michał Małoszewski (michal-maloszewski99) -- 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/1979879 Title: Apparmor profile in 22.04 jammy - fails to start when printing enabled Status in apparmor package in Ubuntu: Invalid Status in samba package in Ubuntu: Fix Released Status in apparmor source package in Jammy: Triaged Status in samba source package in Jammy: Triaged Bug description: See bug here: https://bugzilla.opensuse.org/show_bug.cgi?id=1191532 Fix was backported, but the path to samba-bgqd is wrong on 22.04. Currently apparmor profile has it like this: /usr/lib*/samba/samba-bgqd When in fact 22.04 has it on /usr/lib/x86_64-linux-gnu/samba/samba- bgqd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1979879/+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 1977764] Re: kernel modules "zstd" and "z3fold" missing.
** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu-seeds/+git/ubuntu-seeds/+merge/427165 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1977764 Title: kernel modules "zstd" and "z3fold" missing. Status in Ubuntu Seeds: New Status in linux-raspi package in Ubuntu: Invalid Status in ubuntu-settings package in Ubuntu: New Status in linux-raspi source package in Jammy: Invalid Status in ubuntu-settings source package in Jammy: New Status in linux-raspi source package in Kinetic: Invalid Status in ubuntu-settings source package in Kinetic: New Bug description: The modules "zstd" and "z3fold" are missing despite being configured for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot display that state they do not exist and so instead use compressor "lzo" and pool "zbud". Ubuntu version is 22.04 LTS flashed from the official image. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 6 17:29:00 2022 ImageMediaBuild: 20220419 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-seeds/+bug/1977764/+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 1977764] Re: kernel modules "zstd" and "z3fold" missing.
To sponsors: let me know if the ubuntu-raspi-settings-desktop name is not desirable; I'm happy to adjust this to (for example) ubuntu-desktop- raspi-settings but it'll need adjusting in both this debdiff, and in the MP for the corresponding seed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1977764 Title: kernel modules "zstd" and "z3fold" missing. Status in Ubuntu Seeds: New Status in linux-raspi package in Ubuntu: Invalid Status in ubuntu-settings package in Ubuntu: New Status in linux-raspi source package in Jammy: Invalid Status in ubuntu-settings source package in Jammy: New Status in linux-raspi source package in Kinetic: Invalid Status in ubuntu-settings source package in Kinetic: New Bug description: The modules "zstd" and "z3fold" are missing despite being configured for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot display that state they do not exist and so instead use compressor "lzo" and pool "zbud". Ubuntu version is 22.04 LTS flashed from the official image. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 6 17:29:00 2022 ImageMediaBuild: 20220419 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-seeds/+bug/1977764/+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 1977764] Re: kernel modules "zstd" and "z3fold" missing.
Attaching debdiff for ubuntu-settings. This adds the ubuntu-raspi- settings-desktop binary package which includes the necessary initramfs- tools configuration to include the missing modules. In addition to this, I'll file a merge proposal for the necessary seed to include this package in the Ubuntu Pi desktop image(s). ** Patch added: "1-1977764.debdiff" https://bugs.launchpad.net/ubuntu-seeds/+bug/1977764/+attachment/5604370/+files/1-1977764.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1977764 Title: kernel modules "zstd" and "z3fold" missing. Status in Ubuntu Seeds: New Status in linux-raspi package in Ubuntu: Invalid Status in ubuntu-settings package in Ubuntu: New Status in linux-raspi source package in Jammy: Invalid Status in ubuntu-settings source package in Jammy: New Status in linux-raspi source package in Kinetic: Invalid Status in ubuntu-settings source package in Kinetic: New Bug description: The modules "zstd" and "z3fold" are missing despite being configured for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot display that state they do not exist and so instead use compressor "lzo" and pool "zbud". Ubuntu version is 22.04 LTS flashed from the official image. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 6 17:29:00 2022 ImageMediaBuild: 20220419 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-seeds/+bug/1977764/+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 1880989] Re: libasound2-plugins-extra is built from outdated ALSA source
** Changed in: alsa-plugins (Ubuntu) Status: New => Fix Committed ** Changed in: alsa-plugins (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1880989 Title: libasound2-plugins-extra is built from outdated ALSA source Status in alsa-plugins package in Ubuntu: Fix Committed Status in alsa-plugins-extra package in Ubuntu: Won't Fix Bug description: Notice the versions, 1.2.2 is current and libasound2-plugins-extra is build from 1.1.0 sources: ii libasound2-plugins:amd64 1.2.2-1ubuntu1 amd64ALSA library additional plugins ii libasound2-plugins-extra:amd64 1.1.0-1ubuntu2 amd64ALSA library additional plugins I would like to see it updated to 1.2.2, in order to incorporate fixes such as https://github.com/alsa-project/alsa-plugins/commit/cdff2e32537440bf16329c8440d0d02d7ac02d38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1880989/+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 1928733] Re: Starting systemd Network Service fails with "Invalid argument"
This issue is fixed in Jammy, but not earlier LTS releases. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1928733 Title: Starting systemd Network Service fails with "Invalid argument" Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Triaged Status in systemd source package in Focal: Triaged Status in systemd source package in Groovy: Won't Fix Status in systemd source package in Hirsute: Won't Fix Status in systemd source package in Impish: Won't Fix Bug description: This server has a new install of Ubuntu 18.04 server. Sometimes (around 50% of the time) when it boots systemd-networkd.service initially fails to start with an error as below. It then tries again and succeeds, however other services which depend on systemd-networkd have already failed on the dependency by then. From the output of "journalctl -u systemd-networkd": -- Reboot -- May 17 19:44:28 server1 systemd[1]: Starting Network Service... May 17 19:44:30 server1 systemd[2261]: systemd-networkd.service: Failed to set up mount namespacing: Invalid argument May 17 19:44:30 server1 systemd[2261]: systemd-networkd.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-networkd: Invalid argument May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=226/NAMESPACE May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Failed with result 'exit-code'. May 17 19:44:30 server1 systemd[1]: Failed to start Network Service. May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart. May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 1. May 17 19:44:30 server1 systemd[1]: Stopped Network Service. May 17 19:44:30 server1 systemd[1]: Starting Network Service... May 17 19:44:30 server1 systemd-networkd[2321]: Enumeration completed May 17 19:44:30 server1 systemd[1]: Started Network Service. May 17 19:44:30 server1 systemd-networkd[2321]: eno2: IPv6 successfully enabled May 17 19:44:30 server1 systemd-networkd[2321]: eno1: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f0np0: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: lo: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f1np1: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: eno1: IPv6 successfully enabled May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f0np0: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: lo: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f1np1: Link is not managed by us May 17 19:44:31 server1 systemd-networkd[2321]: eno2: Link UP May 17 19:44:31 server1 systemd-networkd[2321]: eno1: Link UP May 17 19:44:34 server1 systemd-networkd[2321]: eno2: Gained carrier May 17 19:44:34 server1 systemd-networkd[2321]: eno1: Gained carrier May 17 19:44:35 server1 systemd-networkd[2321]: eno1: Gained IPv6LL May 17 19:44:35 server1 systemd-networkd[2321]: eno1: Configured May 17 19:44:36 server1 systemd-networkd[2321]: eno2: Gained IPv6LL May 17 19:44:36 server1 systemd-networkd[2321]: eno2: Configured ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.46 ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18 Uname: Linux 4.15.0-142-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 Date: Mon May 17 19:53:11 2021 InstallationDate: Installed on 2021-03-18 (60 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1604:10c0 Tascam Bus 001 Device 003: ID 1604:10c0 Tascam Bus 001 Device 002: ID 1604:10c0 Tascam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R440 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic root=/dev/mapper/vg1-lv_root ro processor.max_cstate=1 intel_idle.max_cstate=0 transparent_hugepage=never SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.3 dmi.board.name: 04JN2K dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.3:bd09/23/2020:svnDellInc.:pnPowerEdgeR440:pvr:rvnDellInc.:rn04JN2K:rvrA06:cvnDellInc.:ct23:cvr: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R440 dmi.sys.vendor: Dell Inc. To manage notifications
[Touch-packages] [Bug 1880989] Re: libasound2-plugins-extra is built from outdated ALSA source
This package has now been dropped, the rationale for a separate source package no longer applies. This will be integrated into alsa-plugins directly. ** Changed in: alsa-plugins-extra (Ubuntu) Status: New => Won't Fix ** Also affects: alsa-plugins (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1880989 Title: libasound2-plugins-extra is built from outdated ALSA source Status in alsa-plugins package in Ubuntu: New Status in alsa-plugins-extra package in Ubuntu: Won't Fix Bug description: Notice the versions, 1.2.2 is current and libasound2-plugins-extra is build from 1.1.0 sources: ii libasound2-plugins:amd64 1.2.2-1ubuntu1 amd64ALSA library additional plugins ii libasound2-plugins-extra:amd64 1.1.0-1ubuntu2 amd64ALSA library additional plugins I would like to see it updated to 1.2.2, in order to incorporate fixes such as https://github.com/alsa-project/alsa-plugins/commit/cdff2e32537440bf16329c8440d0d02d7ac02d38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1880989/+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 1982355] [NEW] gdk-pixbuf-query-loaders binary path not included in pkgconfig file
Public bug reported: The gdk-pixbuf-query-loaders binary path is supposed to be reported in the .pc file variable gdk_pixbuf_query_loaders so that it can be queried: $ pkg-config --variable=gdk_pixbuf_query_loaders gdk-pixbuf-2.0 /usr/bin/gdk-pixbuf-query-loaders However in Ubuntu the binary is in /usr/lib/`gcc -dumpmachine`/gdk- pixbuf-2.0/gdk-pixbuf-query-loaders This poses a challenge to build scripts for pixbuf loaders as they need to adapt to this distro-specific paths. ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1982355 Title: gdk-pixbuf-query-loaders binary path not included in pkgconfig file Status in gdk-pixbuf package in Ubuntu: New Bug description: The gdk-pixbuf-query-loaders binary path is supposed to be reported in the .pc file variable gdk_pixbuf_query_loaders so that it can be queried: $ pkg-config --variable=gdk_pixbuf_query_loaders gdk-pixbuf-2.0 /usr/bin/gdk-pixbuf-query-loaders However in Ubuntu the binary is in /usr/lib/`gcc -dumpmachine`/gdk- pixbuf-2.0/gdk-pixbuf-query-loaders This poses a challenge to build scripts for pixbuf loaders as they need to adapt to this distro-specific paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982355/+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 1981807] Re: qt5-network openssl3 armhf does not support tls1.3
Thank you. Once the patch is accepted upstream, I will backport it to
Debian/Ubuntu packaging.
In Ubuntu we don't care about older OpenSSL versions, but upstream Qt
does care.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1981807
Title:
qt5-network openssl3 armhf does not support tls1.3
Status in qtbase-opensource-src package in Ubuntu:
New
Bug description:
lsb_release
Description:Ubuntu 22.04 LTS
Release:22.04
libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf
the qt5 armhf version shipped with ubuntu jammy has a regression in
tls1.3 support (simply missing in runtime).
openssl supports tls1.3, so the underlying library works.
x86_64 is obviously not affected
the short sample applications writes -1 on armhf, 15 on x86_64 (unknown
protocol vs tls1.3)
QSslSocket* s = new QSslSocket();
QSslConfiguration cfg = s->sslConfiguration();
cfg.setProtocol(QSsl::TlsV1_3OrLater);
s->setSslConfiguration(cfg);
s->connectToHostEncrypted("tls13-enabled.server",443);
s->waitForConnected();
printf("%d\n",s->sessionProtocol());
marking it as security since the most secure tls protocol is not used
on some platforms
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+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 1982334] [NEW] Xorg crash
Public bug reported: System crashed suddenly while working and log in window shows up. Automatically logged out of system and all the applications closed down. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 20 17:03:14 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f9] InstallationDate: Installed on 2022-04-22 (88 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 34601F4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=be040347-6300-407e-9e19-da58389c3a6f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2013 dmi.bios.release: 2.59 dmi.bios.vendor: LENOVO dmi.bios.version: G6ET99WW (2.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 34601F4 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnLENOVO:bvrG6ET99WW(2.59):bd11/19/2013:br2.59:efr1.4:svnLENOVO:pn34601F4:pvrThinkPadX1Carbon:rvnLENOVO:rn34601F4:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_3460: dmi.product.family: ThinkPad X1 Carbon dmi.product.name: 34601F4 dmi.product.sku: LENOVO_MT_3460 dmi.product.version: ThinkPad X1 Carbon dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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 crash jammy ubuntu wayland-session -- 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/1982334 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: System crashed suddenly while working and log in window shows up. Automatically logged out of system and all the applications closed down. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 20 17:03:14 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f9] InstallationDate: Installed on 2022-04-22 (88 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 34601F4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=be040347-6300-407e-9e19-da58389c3a6f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2013 dmi.bios.release: 2.59 dmi.bios.vendor: LENOVO dmi.bios.version: G6ET99WW (2.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 34601F4 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnLENOVO:bvrG6ET99WW(2.59):bd11/19/2013:br2.59:efr1.4:svnLENOVO:pn34601F4:pvrThinkPadX1Carbon:rvnLENOVO:rn34601F4:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_3460: dmi.product.family: ThinkPad X1 Carbon dmi.product.name: 34601F4 dmi.product.sku: LENOVO_MT_3460
[Touch-packages] [Bug 1977764] Re: kernel modules "zstd" and "z3fold" missing.
** Also affects: ubuntu-seeds Importance: Undecided Status: New ** Changed in: ubuntu-seeds Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1977764 Title: kernel modules "zstd" and "z3fold" missing. Status in Ubuntu Seeds: New Status in linux-raspi package in Ubuntu: Invalid Status in ubuntu-settings package in Ubuntu: New Status in linux-raspi source package in Jammy: Invalid Status in ubuntu-settings source package in Jammy: New Status in linux-raspi source package in Kinetic: Invalid Status in ubuntu-settings source package in Kinetic: New Bug description: The modules "zstd" and "z3fold" are missing despite being configured for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot display that state they do not exist and so instead use compressor "lzo" and pool "zbud". Ubuntu version is 22.04 LTS flashed from the official image. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 6 17:29:00 2022 ImageMediaBuild: 20220419 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-seeds/+bug/1977764/+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 1981874] Re: gdk_wayland_window_handle_configure_popup: assertion 'impl->transient_for' failed
** Package changed: gtk+3.0 (Ubuntu) => ubuntu -- 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/1981874 Title: gdk_wayland_window_handle_configure_popup: assertion 'impl->transient_for' failed Status in Ubuntu: New Bug description: When running update-manager in the command line, viewing the changelogs for some updates and installing all updates, update-manager outputs the following to standard error. Gdk-Message: 07:32:40.867: Window 0x559accd09420 is a temporary window without parent, application will not be able to position it on screen. (update-manager:30618): Gdk-CRITICAL **: 07:32:40.878: gdk_wayland_window_handle_configure_popup: assertion 'impl->transient_for' failed Gdk-Message: 07:32:41.983: Window 0x559acd626210 is a temporary window without parent, application will not be able to position it on screen. (update-manager:30618): Gdk-CRITICAL **: 07:32:41.992: gdk_wayland_window_handle_configure_popup: assertion 'impl->transient_for' failed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgtk-3-0 3.24.33-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 16 07:37:26 2022 InstallationDate: Installed on 2022-05-04 (72 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/+bug/1981874/+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 1971319] Re: Merge rsync from Debian unstable for kinetic
This bug was fixed in the package rsync - 3.2.4-1 --- rsync (3.2.4-1) unstable; urgency=medium [ Samuel Henrique ] * New upstream version 3.2.4 - Work around a glibc bug where lchmod() breaks in a chroot w/o /proc mounted (closes: #995046). - rsync.1: remove prepended backticks which broke --stop-after and --stop-at formatting (closes: #1007990). * Ship new python-based rrsync with --with-rrsync: - rrsync was previouysly written in bash. - A manpage is now shipped for rrsync. - python3 and python3-cmarkgfm are new B-Ds since they're needed to generate the manpage. * d/control: - Add version requirement for some libxxhash-dev and libzstd-dev as per upstream docs. - Add python3-braceexpand to Suggests as it can be used by rrsync. * d/rsync.install: cull_options has been renamed to cull-options. * d/patches: - Refresh the following patches: ~ disable_reconfigure_req.diff; ~ perl_shebang.patch; ~ skip_devices_test.patch; - Drop the following patches, applied upstream now: ~ CVE-2020-14387.patch; ~ copy-devices.diff; ~ fix_delay_updates.patch; ~ fix_ftcbfs_configure.patch; ~ fix_mkpath.patch; ~ fix_rsync-ssl_RSYNC_SSL_CERT_feature.patch; ~ fix_sparse_inplace.patch; ~ manpage_upstream_fixes.patch; ~ update_rrsync_options.patch; ~ workaround_glibc_lchmod_regression.patch; [ Sergio Durigan Junior ] * d/rules: Disable ASM optimizations when building. This is not needed because the only ASM-optimized implementation available is the MD5 hash, which is actually a no-op because we link against OpenSSL and rsync ends up using that library's implementation of the hash. Even then, the final binary ends up with the ASM-optimized version included, which makes it become CET-incompatible. Thanks to Dimitri John Ledkov -- Samuel Henrique Mon, 18 Apr 2022 14:44:44 +0100 ** Changed in: rsync (Ubuntu) Status: New => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-14387 -- 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/1971319 Title: Merge rsync from Debian unstable for kinetic Status in rsync package in Ubuntu: Fix Released Bug description: Upstream: tbd Debian: 3.2.4-1 Ubuntu: 3.2.3-8ubuntu3 Debian does new releases regularly, so it's likely there will be newer versions available before FF that we can pick up if this merge is done later in the cycle. ### New Debian Changes ### rsync (3.2.4-1) unstable; urgency=medium [ Samuel Henrique ] * New upstream version 3.2.4 - Work around a glibc bug where lchmod() breaks in a chroot w/o /proc mounted (closes: #995046). - rsync.1: remove prepended backticks which broke --stop-after and --stop-at formatting (closes: #1007990). * Ship new python-based rrsync with --with-rrsync: - rrsync was previouysly written in bash. - A manpage is now shipped for rrsync. - python3 and python3-cmarkgfm are new B-Ds since they're needed to generate the manpage. * d/control: - Add version requirement for some libxxhash-dev and libzstd-dev as per upstream docs. - Add python3-braceexpand to Suggests as it can be used by rrsync. * d/rsync.install: cull_options has been renamed to cull-options. * d/patches: - Refresh the following patches: ~ disable_reconfigure_req.diff; ~ perl_shebang.patch; ~ skip_devices_test.patch; - Drop the following patches, applied upstream now: ~ CVE-2020-14387.patch; ~ copy-devices.diff; ~ fix_delay_updates.patch; ~ fix_ftcbfs_configure.patch; ~ fix_mkpath.patch; ~ fix_rsync-ssl_RSYNC_SSL_CERT_feature.patch; ~ fix_sparse_inplace.patch; ~ manpage_upstream_fixes.patch; ~ update_rrsync_options.patch; ~ workaround_glibc_lchmod_regression.patch; [ Sergio Durigan Junior ] * d/rules: Disable ASM optimizations when building. This is not needed because the only ASM-optimized implementation available is the MD5 hash, which is actually a no-op because we link against OpenSSL and rsync ends up using that library's implementation of the hash. Even then, the final binary ends up with the ASM-optimized version included, which makes it become CET-incompatible. Thanks to Dimitri John Ledkov -- Samuel Henrique Mon, 18 Apr 2022 14:44:44 +0100 rsync (3.2.3-8) unstable; urgency=medium * debian/patches: - manpage_upstream_fixes.patch: Import multiple upstream patches to fix manpage. - copy-devices.diff: Add missing manpage changes to patch - CVE-2020-14387.patch: Add Forwarded DEP3 field to point to upstream
[Touch-packages] [Bug 1981807] Re: qt5-network openssl3 armhf does not support tls1.3
@mitya57 the patch is now submitted to codereview. I am however only
able to submit to the dev branch (took me a while to get this, never
used gerrit before). This also means that the patch I submitted is for
qt6. There is no way i send a codereview for qt5 anymore, so I don't
know who will do the backport if the qt6 patch gets merged.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1981807
Title:
qt5-network openssl3 armhf does not support tls1.3
Status in qtbase-opensource-src package in Ubuntu:
New
Bug description:
lsb_release
Description:Ubuntu 22.04 LTS
Release:22.04
libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf
the qt5 armhf version shipped with ubuntu jammy has a regression in
tls1.3 support (simply missing in runtime).
openssl supports tls1.3, so the underlying library works.
x86_64 is obviously not affected
the short sample applications writes -1 on armhf, 15 on x86_64 (unknown
protocol vs tls1.3)
QSslSocket* s = new QSslSocket();
QSslConfiguration cfg = s->sslConfiguration();
cfg.setProtocol(QSsl::TlsV1_3OrLater);
s->setSslConfiguration(cfg);
s->connectToHostEncrypted("tls13-enabled.server",443);
s->waitForConnected();
printf("%d\n",s->sessionProtocol());
marking it as security since the most secure tls protocol is not used
on some platforms
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+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
