[Touch-packages] [Bug 1989433] Re: Security patch only available via proposed repository
Thanks for the information, meanwhile this is resolved by 237-3ubuntu10.56. -- 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/1989433 Title: Security patch only available via proposed repository Status in systemd package in Ubuntu: Invalid Bug description: Hello on Ubuntu 18.04, systemd 237-3ubuntu10.54 has a fix for CVE-2022-2526, however this version is only available in proposed, see[1] - not in updates or security - so most users are on 237-3ubuntu10.53. I would expect security updates in the updates or security repo. ~frukto lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 apt-cache policy systemd systemd: Installed: 237-3ubuntu10.54 Candidate: 237-3ubuntu10.54 Version table: *** 237-3ubuntu10.54 100 100 /var/lib/dpkg/status 237-3ubuntu10.53 500 500 http://ubuntu.ethz.ch/ubuntu bionic-updates/main amd64 Packages 237-3ubuntu10.50 500 500 http://ubuntu.ethz.ch/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://ubuntu.ethz.ch/ubuntu bionic/main amd64 Packages [1] https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1989433/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615381] Re: apt-get autoremove may remove current kernel
Hello Jarno, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.17 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-failed-bionic ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1615381 Title: apt-get autoremove may remove current kernel Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Won't Fix Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Artful: Won't Fix Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt source package in Hirsute: Fix Released Bug description: [Impact] APT will try and fail to remove the currently running kernel, when booted into an older kernel that is not protected. May wreak some havoc if mixed with other operations to the point that apt goes weird and needs manual fixing up. [Test case] For the SRUs we have included an automated test case that starts with an empty autoremove config file, and then checks that the running kernel is protected at runtime. You can also test manually, but it's not necessary: - Install new kernel - Reboot into kernel not listed as protected in 01autoremove-kernels - Run autoremove [Where problems could occur] We may more easily run out of space in /boot. hirsute has new autoremoval code that runs completely at runtime; but that seems a bit large to SRU after only a few weeks in hirsute. Hence, we should protect the current kernel _in addition_ to the other kernels, just like unattended-upgrades and update-manager do. This increases the risk of filling up /boot compared to older apt versions, but is at the same level as unattended-upgrades and update-manager. [Original bug report] This may happen, if you boot one of the older kernels, that is not protected by /etc/apt/apt.conf.d/01autoremove-kernels Workaround: run /etc/kernel/postinst.d/apt-auto-removal during each boot (e.g. by using cron). Note: The workaround breaks autoremoving feature of new unneeded kernels in unattended-upgrades i.e. the setting 'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set in '/etc/apt/apt.conf.d/50unattended-upgrades'. In shell: $ uname -r 4.4.0-22-generic $ apt-get -s autoremove NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22 linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic 0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.12~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Aug 21 16:11:27 2016 EcryptfsInUse: Yes InstallationDate: I
[Touch-packages] [Bug 1968154] Please test proposed package
Hello Julian, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.17 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1968154 Title: Only keep 2 kernels Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Released Status in apt source package in Impish: Fix Released Bug description: [Impact] APT currently keeps 3 kernels or even 4 in some releases. Our boot partition is sized for a steady state of 2 kernels + 1 new one being unpacked, hence users run out of space and new kernels fail to install, upgrade runs might abort in the middle. It's not nice. [Test plan] 1. Have two kernels installed (let's call them version 3, 2) 2. Check that both kernels are not autoremovable 3. Install an old kernel (let's call it 1), and mark it automatic 4. Check that 1 will be autoremovable (apt autoremove -s) 5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s) 6. Actually remove 2 7. Reboot into 3 and check that both 1 and 3 are now not autoremovable [Where problems could occur] We could keep the wrong kernels installed that the user did not expect. We remove the requirement to keep the most recently installed version, previously recorded in APT::LastInstalledKernel, to achieve this, as we had 3 hard requirements so far: 1. keep booted kernel 2. keep highest version 3. keep most recently installed 1 can't be removed as it would break running systems, 2 is what you definitely want to keep. During normal system lifetime, the most recently installed kernel is the same as the highest version, so 2==3, and there are no changes to behavior. Likewise, if you most recently installed an older kernel manually for debugging, it would be manually installed and not subject to removal, even if the rule is dropped. The behavior really only changes if you install an older kernel, and then mark it auto - that older kernel becomes automatically removable immediately after it is marked as auto. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+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 1974456] Re: regression: apt.postint fails if never previously configured
Hello David, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.17 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-bionic ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1974456 Title: regression: apt.postint fails if never previously configured Status in apt package in Ubuntu: Confirmed Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Released Bug description: [Impact] bootstrapping a system with apt that fixes #1968154 fails in focal and bionic, as they try to execute the config file that is being removed. This is not a problem on updates, only on new installs, so impact is limited to bootstrapping tools that enable -updates, such as mmdebstrap. [Test case] bootstrapping with -updates enabled can easily be tested with mmdebstrap: mmdebstrap -v focal ~/Projects/Ubuntu/Scratch/focal for example, on focal: Setting up apt (2.0.8) ... /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: not found dpkg: error processing package apt (--configure): installed apt package post-installation script subprocess returned error exit status 127 [Regression potential] We remove 5 lines from the shell postinst script, there could be syntax errors? But then we'd see those during upgrades, so practically none. [Original bug report] #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch: https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0 ...but `apt.postinst` still tries to run it: # create kernel autoremoval blacklist on update if dpkg --compare-versions "$2" lt 0.9.9.3; then /etc/kernel/postinst.d/apt-auto-removal fi If I understand correctly, "$2" is the most-recently-configured- version, and if it's empty `dpkg --compare-versions lt` will evaluate to true. This fails when I'm building a focal (20.04) userspace from scratch: $ dpkg --configure -a [...] Setting up apt (2.0.8) ... /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: not found dpkg: error processing package apt (--configure): installed apt package post-installation script subprocess returned error exit status 127 It works with apt 2.0.6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974456/+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 1831039] Re: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome
** Changed in: oem-priority Importance: Undecided => High -- 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/1831039 Title: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome Status in OEM Priority Project: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: When using wayland - onscreen keyboard not open in text inputs in many applications such as firefox or chrome. Ubuntu 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2015-06-09 (1455 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 PackageArchitecture: amd64 ProcEnviron: LANG=cs_CZ.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Tags: third-party-packages bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-31 (368 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1831039/+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 1981042] Re: /etc/localtime symlink not correctly handled when using /etc/writable
Installed systemd 249.11-0ubuntu3.6 on a jammy VM and confirmed everything working as expected, thanks! ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1981042 Title: /etc/localtime symlink not correctly handled when using /etc/writable Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] When using /etc/writable (e.g. Ubuntu Core) /etc/localtime is a symlink to /etc/writable/localtime (which in itself if a symlink). Systemd doesn't handle this correctly when doing firstboot or using inotify to watch for changes to localtime. [Test Plan] This is somewhat hard to test, the following situations need to be reproduced: - On firstboot the timezone link will not be read correctly, it will with this change. - Starting a timer unit and then changing timezone will cause it not to occur at the correct time. [Where problems could occur] This could potentially break other users of localtime, however the change is similar to existing changes which have been in Ubuntu's version of systemd for some time. The change detects the /etc/writable case and if not should have the same existing behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981042/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961484] Re: 20.04.3: libva2 fails under Wayland (wl_drm@22: error 0: authenticate failed)
In my test, these packages in PPA fixed the problem. add PPA and update & upgrade, the issue disappear. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1961484 Title: 20.04.3: libva2 fails under Wayland (wl_drm@22: error 0: authenticate failed) Status in libva package in Ubuntu: Confirmed Bug description: In current 20.04.3 libva2 fails to authenticate connection to Wayland composer. This may be related to update of Mesa to 21.2.6. Any program using libva2 fails with bor@bor-Latitude-E5450:~$ vainfo wl_drm@7: error 0: authenticate failed VA error: wayland: Wayland roundtrip error: Protocol error (errno 71) libva info: VA-API version 1.7.0 libva error: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) vaInitialize failed with error code 3 (invalid VADisplay),exit bor@bor-Latitude-E5450:~$ This is fixed in libva upstream in pull request https://github.com/intel/libva/pull/476 I verified that upstream libva correctly works: bor@bor-Latitude-E5450:~/src/intel/libva-utils$ ./vainfo/vainfo libva info: VA-API version 1.15.0 libva info: Trying to open /home/bor/pkg/lib/dri/iHD_drv_video.so libva info: va_openDriver() returns -1 libva info: Trying to open /home/bor/pkg/lib/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_6 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.15 (libva 2.15.0.pre1) vainfo: Driver version: Intel i965 driver for Intel(R) Broadwell - 2.4.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Simple : VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileVP8Version0_3 : VAEntrypointVLD bor@bor-Latitude-E5450:~/src/intel/libva-utils$ With *only* commit 283f776a9649dcef58b47958c1269499adfa1cd4 reverted bor@bor-Latitude-E5450:~/src/intel/libva-utils$ ./vainfo/vainfo wl_drm@7: error 0: authenticate failed VA error: wayland: Wayland roundtrip error: Protocol error (errno 71) libva info: VA-API version 1.15.0 libva error: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) vaInitialize failed with error code 3 (invalid VADisplay),exit bor@bor-Latitude-E5450:~/src/intel/libva-utils$ Please update libva in 20.04.3 to match Mesa. This bug affects any application that is trying to use VAAPI for hardware acceleration. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libva2 2.7.0-2 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-lowlatency 5.13.19 Uname: Linux 5.13.0-30-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 19 19:16:15 2022 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-07-02 (2424 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: libva UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1961484/+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 1989515] [NEW] "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic
Public bug reported: Somehow "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic but "goo/gmem.h" still has the statement `#include "GooCheckedOps.h"`. As a result, a compile error will happen when compiling code that uses poppler: /usr/include/poppler/goo/gmem.h:31:11: fatal error: GooCheckedOps.h: No such file or directory I'm using Ubuntu 18.04 and currently having 0.62.0-2ubuntu2.12 (the previous version) installed. I confirmed that "goo/gmem.h" doesn't have the `#include "GooCheckedOps.h"` statement. I found this issue when I was compiling gdal on my Docker container. The Docker container was installed the problematic version 0.62.0-2ubuntu2.13 and I ran into the "No such file or directory" error. I compiled on both Amd64 and AArch64 and I ran into the same error on both platforms. By reading the diff between 2.12 and 2.13 (https://launchpadlibrarian.net/622079418/poppler_0.62.0-2ubuntu2.12_0.62.0-2ubuntu2.13.diff.gz), the patch looks quite right. But when I examined the contents of the built `.deb` packages, I didn't find the file "goo/GooCheckedOps.h". Kind of weird, because the problem seems to be caused by applying "CVE-2022-38784-pre.patch" in half: the first part that creates "goo/GooCheckedOps.h" was not applied during the build process and the second part that modifies "goo/gmem.h" was applied. Any thoughts? Ideas? ** Affects: poppler (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1989515 Title: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic Status in poppler package in Ubuntu: New Bug description: Somehow "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic but "goo/gmem.h" still has the statement `#include "GooCheckedOps.h"`. As a result, a compile error will happen when compiling code that uses poppler: /usr/include/poppler/goo/gmem.h:31:11: fatal error: GooCheckedOps.h: No such file or directory I'm using Ubuntu 18.04 and currently having 0.62.0-2ubuntu2.12 (the previous version) installed. I confirmed that "goo/gmem.h" doesn't have the `#include "GooCheckedOps.h"` statement. I found this issue when I was compiling gdal on my Docker container. The Docker container was installed the problematic version 0.62.0-2ubuntu2.13 and I ran into the "No such file or directory" error. I compiled on both Amd64 and AArch64 and I ran into the same error on both platforms. By reading the diff between 2.12 and 2.13 (https://launchpadlibrarian.net/622079418/poppler_0.62.0-2ubuntu2.12_0.62.0-2ubuntu2.13.diff.gz), the patch looks quite right. But when I examined the contents of the built `.deb` packages, I didn't find the file "goo/GooCheckedOps.h". Kind of weird, because the problem seems to be caused by applying "CVE-2022-38784-pre.patch" in half: the first part that creates "goo/GooCheckedOps.h" was not applied during the build process and the second part that modifies "goo/gmem.h" was applied. Any thoughts? Ideas? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1989515/+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 1964506] Re: Ping: checks payloads incorrectly, ignores all mismatch replies
and I've uploaded a focal SRU candidate to the review queue now ** Changed in: iputils (Ubuntu Focal) Importance: Undecided => Low ** Changed in: iputils (Ubuntu Focal) Status: New => Fix Committed ** Description changed: + = Impact = + + the ping statistics are incorrect when dealing with truncated packets + + = Test case = + + $ ping -c 1 -s 1200 8.8.8.8 + + should list truncated replies and received packets + + = Regression potential = + + the changes are limited to the ping source any regression would impact + that utility, check that responses are correctly handled and statistics + reflecting what is expected + + -- + Problematic commit reverted upstream causing incorrect behavior in Ubuntu Focal. Discussion: https://github.com/iputils/iputils/issues/320 Fix: https://github.com/iputils/iputils/pull/321 Release: https://github.com/iputils/iputils/releases/tag/20210722 Could this patch be added for a Focal update please? 1) Ubuntu 20.04.3 LTS 2) 3:20190709-3 3) focal$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. --- 8.8.8.8 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms 4) xenial$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. 76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated) --- 8.8.8.8 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1964506 Title: Ping: checks payloads incorrectly, ignores all mismatch replies Status in iputils package in Ubuntu: Fix Released Status in iputils source package in Focal: Fix Committed Bug description: = Impact = the ping statistics are incorrect when dealing with truncated packets = Test case = $ ping -c 1 -s 1200 8.8.8.8 should list truncated replies and received packets = Regression potential = the changes are limited to the ping source any regression would impact that utility, check that responses are correctly handled and statistics reflecting what is expected -- Problematic commit reverted upstream causing incorrect behavior in Ubuntu Focal. Discussion: https://github.com/iputils/iputils/issues/320 Fix: https://github.com/iputils/iputils/pull/321 Release: https://github.com/iputils/iputils/releases/tag/20210722 Could this patch be added for a Focal update please? 1) Ubuntu 20.04.3 LTS 2) 3:20190709-3 3) focal$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. --- 8.8.8.8 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms 4) xenial$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. 76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated) --- 8.8.8.8 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1964506/+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 1964506] Re: Ping: checks payloads incorrectly, ignores all mismatch replies
The issue is fixed in the version available in the current Ubuntu serie ** Changed in: iputils (Ubuntu) Importance: Undecided => Low ** Changed in: iputils (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1964506 Title: Ping: checks payloads incorrectly, ignores all mismatch replies Status in iputils package in Ubuntu: Fix Released Status in iputils source package in Focal: New Bug description: Problematic commit reverted upstream causing incorrect behavior in Ubuntu Focal. Discussion: https://github.com/iputils/iputils/issues/320 Fix: https://github.com/iputils/iputils/pull/321 Release: https://github.com/iputils/iputils/releases/tag/20210722 Could this patch be added for a Focal update please? 1) Ubuntu 20.04.3 LTS 2) 3:20190709-3 3) focal$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. --- 8.8.8.8 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms 4) xenial$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. 76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated) --- 8.8.8.8 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1964506/+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 1974115] Re: [UBUNTU 22.04] BINUTILS: Adding new platform name IBM z16
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin2204 -- 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/1974115 Title: [UBUNTU 22.04] BINUTILS: Adding new platform name IBM z16 Status in Ubuntu on IBM z Systems: Fix Committed Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Jammy: Fix Committed Status in binutils source package in Kinetic: Fix Released Bug description: SRU Justification: == [Impact] * As of today the architectural (level) name 'arch14' is used as CPU name for the new IBM z16 system. * The real name 'z16' couldn't be used until officially announced. * That happened meanwhile, hence we can now add and use the real name. [Test Plan] * Check if the same (proper) opcodes are detected on an IBM z16 system with and without the patch. Since only the identification and name of a z16 system was modified. * Or the simplest test is probably to check (after having 'binutils' installed on an Ubuntu 22.04 s390x system) if not only: 'as -m64 -march=arch14 --target-help' but also: 'as -m64 -march=z16 --target-help' succeeds and leads to the same output. (As it does for '-march=arch13' and '-march=arch15'.) [Where problems could occur] * Issues could happen if the conditional statement that look for architectural / CPU name are paired wrongly, since: * 'z16' belongs to 'arch14', 'z15' to 'arch13', etc. * If these pairs are not handled correctly, or the identification is erroneous a wrong system might be identified and wrong instructions used etc. [Other] * This is a hardware enablement SRU to enhance the IBM z16 support. __ After the announcement support for the official machine name z16 has been added to binutils. Please consider picking up the following patch from 2.37 branch: commit e24d2a2d11008aa363366c1087219f3e3405782a (origin/binutils-2_37-branch, 2.37) IBM zSystems: Add support for z16 as CPU name. So far z16 was identified as arch14. After the machine has been announced we can now add the real name. (cherry picked from commit 69341966def7f6551bc4452684136831d6a6941c) (cherry picked from commit fb4d148004f28494e9fb5d2400a13308d07a7988) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1974115/+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 1965439] Re: [SRU] kdesu fails to authenticate with sudo from Jammy
** Changed in: sudo (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: [SRU] kdesu fails to authenticate with sudo from Jammy Status in kdesu package in Ubuntu: Fix Released Status in kubuntu-settings package in Ubuntu: Fix Released Status in sudo package in Ubuntu: Won't Fix Status in ubuntustudio-default-settings package in Ubuntu: Fix Released Status in kdesu source package in Jammy: Fix Released Status in kubuntu-settings source package in Jammy: In Progress Status in sudo source package in Jammy: Won't Fix Status in ubuntustudio-default-settings source package in Jammy: In Progress Status in kdesu source package in Kinetic: Fix Released Status in kubuntu-settings source package in Kinetic: Fix Released Status in sudo source package in Kinetic: Won't Fix Status in ubuntustudio-default-settings source package in Kinetic: Fix Released Status in kdesu package in Debian: Fix Released Bug description: kdesu fails to authenticate with sudo from Jammy. See upstream bug: KDE bug: https://bugs.kde.org/show_bug.cgi?id=452532 Examples: Launch Kubuntu driver manager from system setting, launching ksystemlog from the main menu, or trying to run krusader root mode option via its 'Tools > Start Krusader Root Mode' menu entry. Assuming that the current user is a member of the sudo group. On entering the correct password authentication is refused, stating that possibly an incorrect password has been entered. It appears that kdesu fails to cope with the sudo config change in this commit: https://salsa.debian.org/sudo- team/sudo/-/commit/59db341d46aa4c26b54c1270e69f2562e7f3d751 kdesu was fixed in Debian with: https://tracker.debian.org/news/1330116/accepted-kdesu-5940-2-source- into-unstable/ and fixed in kinetic with: https://launchpad.net/ubuntu/+source/kdesu/5.94.0-0ubuntu2 The issue can be worked around by adding /etc/sudoers.d/kdesu-sudoers with the contents Defaults!/usr/lib/*/libexec/kf5/kdesu_stub !use_pty [Impact] * Users are unable to authenticate to and launch applications via kdesu. * This should be backported to restore functionality that users expect. [Test Plan] * Launch Kubuntu driver manager from system setting, launching ksystemlog from the main menu, or trying to run krusader root mode option via its 'Tools > Start Krusader Root Mode' menu entry. Assuming that the current user is a member of the sudo group. * Confirm that the application authentcate and launch as successfully as in previous releases. [Where problems could occur] * While this update only returns sudo to its default behaviour (used in previous releases and virtually all other distributions) for kdesu, care should be taken to test some other applications that seek root permissions to confirm that no unexpected consequences occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+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 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container
** Changed in: livecd-rootfs (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: livecd-rootfs (Ubuntu Jammy) Importance: Medium => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1981109 Title: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container Status in fwupd package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: New Status in fwupd source package in Jammy: Invalid Status in livecd-rootfs source package in Jammy: Triaged Status in modemmanager source package in Jammy: New Status in ubuntu-meta source package in Jammy: New Bug description: Looking at memory utilization in a pristine Ubuntu lxd container (top -o RES), I see that ModemManager is running, which I was surprised to see is present at all in the stock image. Tracking this I find that fwupd depends on libmm-glib0, which in turn Recommends: modemmanager. Libraries in general should not recommend daemons, so it's possible this should be fixed by libmm-glib0 dropping this Recommends. It certainly doesn't seem to be a deliberate decision by the Server Team to have modemmanager installed and running by default on all systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+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 1988870] Re: apport-autoreport.service fails: whoopsie.path is not enabled
** Changed in: apport (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1988870 Title: apport-autoreport.service fails: whoopsie.path is not enabled Status in apport package in Ubuntu: New Bug description: This is what the service reports. Aside from crash reports no longer uploading automatically, I'm having trouble pointing ubuntu-bug to crash reports in /var/crash - a window opens, but then a browser never opens. ubuntu-bug program-name does open the browser though. × apport-autoreport.service - Process error reports when automatic reporting is enabled Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static) Active: failed (Result: exit-code) since Tue 2022-09-06 14:27:48 EDT; 2min 33s ago TriggeredBy: ● apport-autoreport.path ● apport-autoreport.timer Process: 24994 ExecStart=/usr/share/apport/whoopsie-upload-all --timeout 20 (code=exited, status=1/FAILURE) Main PID: 24994 (code=exited, status=1/FAILURE) CPU: 115ms Sep 06 14:27:48 mbp113 systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 06 14:27:48 mbp113 whoopsie-upload-all[24994]: ERROR: whoopsie.path is not enabled Sep 06 14:27:48 mbp113 systemd[1]: apport-autoreport.service: Main process exited, code=exited, status=1/FAILURE Sep 06 14:27:48 mbp113 systemd[1]: apport-autoreport.service: Failed with result 'exit-code'. Sep 06 14:27:48 mbp113 systemd[1]: Failed to start Process error reports when automatic reporting is enabled. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apport 2.23.0-0ubuntu1 Uname: Linux 6.0.0-rc4 x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportLog: ERROR: apport (pid 20795) Tue Sep 6 14:26:35 2022: called for pid 3732, signal 6, core limit 0, dump mode 1 ERROR: apport (pid 20795) Tue Sep 6 14:26:35 2022: executable: /usr/bin/gnome-shell (command line "/usr/bin/gnome-shell") ERROR: apport (pid 20795) Tue Sep 6 14:26:36 2022: debug: session gdbus call: (true,) ERROR: apport (pid 20795) Tue Sep 6 14:26:46 2022: wrote report /var/crash/_usr_bin_gnome-shell.1000.crash ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 640:1000:123:43075180:2022-09-06 14:26:45.388720512 -0400:2022-09-06 14:27:48.608538333 -0400:/var/crash/_usr_bin_gnome-shell.1000.crash 640:1000:123:8681261:2022-08-29 22:32:29.231918756 -0400:2022-08-29 20:57:41.939131333 -0400:/var/crash/_usr_libexec_goa-daemon.1000.crash 640:1000:123:44557691:2022-08-30 08:01:54.998418753 -0400:2022-08-30 08:01:50.202489325 -0400:/var/crash/_opt_google_chrome_chrome.1000.crash CurrentDesktop: ubuntu:GNOME Date: Tue Sep 6 14:29:03 2022 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1988870/+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 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0)
** Tags added: foundations-triage-discuss -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1842439 Title: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) Status in apport package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: Confirmed Status in apport source package in Focal: Triaged Status in gtk+3.0 source package in Focal: Confirmed Bug description: Steps to reproduce -- 1. Use GNOME with GNOME shell 2. killall -11 gnome-shell Suspicious Apport log: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files Error tracker - https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5 https://errors.ubuntu.com/problem/276759c7bf0b6628977c63ca70d26b53c9defd22 Original report --- Session suddenly stopped and came back to login screen, all opened windows lost. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: apport-gtk 2.20.11-0ubuntu7 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashReports: 640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash 640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash 640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash CurrentDesktop: ubuntu:GNOME Date: Tue Sep 3 16:20:13 2019 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2018-06-16 (443 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 SegvAnalysis: Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax PC (0x7f532548f8c4) ok source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1842439/+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 1937110] Re: dhcp option 121 & 249
** Changed in: isc-dhcp (Ubuntu Jammy) Milestone: ubuntu-22.04.1 => None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1937110 Title: dhcp option 121 & 249 Status in subiquity: New Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Jammy: Incomplete Bug description: Hello, I'm running into issues with subiquity on a cloud provider. The cloud provider is using an on-link L3 gateway. His DHCP response looks like this: OPTION: 53 ( 1) DHCP message type 5 (DHCPACK) OPTION: 54 ( 4) Server identifier 172.31.1.1 OPTION: 51 ( 4) IP address leasetime 86400 (24h) OPTION: 1 ( 4) Subnet mask 255.255.255.255 OPTION: 3 ( 4) Routers 172.31.1.1 OPTION: 6 ( 12) DNS server OPTION: 121 ( 14) Classless Static Route20ac1f010100 ... ac1f0101 .. OPTION: 249 ( 14) MSFT - Classless route20ac1f010100 ... ac1f0101 .. Im booting the subiquity process with an patched ipxe (https://github.com/ipxe/ipxe/pull/104) like this: #!ipxe kernel .../vmlinuz initrd=initrd root=/dev/ram0 ramdisk_size=150 ip=dhcp url=https://cdimage.ubuntu.com/ubuntu-server/focal/daily-live/current/focal-live-server-amd64.iso autoinstall ds=nocloud-net;s=.../...-ad-78/ cloud-config-url=/dev/null initrd .../initrd boot initrd/vmlinuz is extracted right out of focal-live-server-amd64.iso Sadly subiquity is stuck with a broken network (because of missing dhcp option 121/249 support). It happens when its running the /init from the kernel right after kernel is booted, i guess even before the subiquity is started(?). After further debugging, it looks like the provided kernel 5.4.80 #90 Ubuntu, is using busybox 1.30.1-4ubuntu~6.3 which includes isc- dhclient-4.4.1 which is lacking the given options. Would be awesome if this could be fixed.. maybe just a simple busybox compile option? To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1937110/+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 1989352] Re: [WSL] Prepare kinetic for common snap use cases
Upgrading a Jammy instance with `do-release-upgrade -d` worked as expected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1989352 Title: [WSL] Prepare kinetic for common snap use cases Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: Users of Ubuntu WSL might be surprised by unexpected dependencies when dealing with snaps. The Ubuntu WSL development team is looking for ways to let early adopters to experiment some snapd support in Kinetic, while still providing the most seamless experience for them. Tests done in WSL instances showed surprises that we should mitigate soon. Some examples are: * Sublime Text and Sublime Merge apps silently depend on libgl1. This seems a bug which we didn't yet figure out how to fix in the snaps themselves. Being such hidden dependencies, we'd expect to soon find similar cases as those. * Flutter snap provides all dependencies and runs without issues, but apps compiled by Flutter requires libgl1, libegl1 and libgtk-3-0 present in the system during development. Attempting to just run any app compiled with Flutter during development will result in crash due those libs not being found. Most likely, once package as snaps, those apps will behave as expected, if the packager lists dependencies properly. The issue reported here affects the app developer experience. One solution for those problems is seeding for Ubuntu WSL specifically: - libgl1 - libegl1 - libgtk-3-0 Experienced Ubuntu users would figure out how to overcome those issues very quickly, but we should expect that most of Ubuntu WSL userbase won't fit in that persona. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1989352/+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 1969976] Autopkgtest regression report (fwupd/1.8.3-1~22.04.1)
All autopkgtests for the newly accepted fwupd (1.8.3-1~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: fwupd/1.8.3-1~22.04.1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#fwupd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1969976 Title: DynamicUser=1 doesn't get along with services that need dbus-daemon Status in Fwupd: Fix Released Status in systemd: New Status in fwupd package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Won't Fix Status in fwupd source package in Focal: Confirmed Status in systemd source package in Focal: Won't Fix Status in fwupd source package in Impish: Won't Fix Status in systemd source package in Impish: Won't Fix Status in fwupd source package in Jammy: Fix Committed Status in systemd source package in Jammy: Won't Fix Bug description: Updating to systemd 245.4-4ubuntu3.16 has caused a regression in Ubuntu 20.04, that fwupd-refresh.service always fails to run. This has been root caused down to the changes in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538 Unfortunately this is an upstream issue introduced by stable systemd. https://github.com/systemd/systemd/issues/22737 The problem also occurs in Ubuntu 22.04 with a newer systemd release. As discussed in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/comments/61 it's a tradeoff of issues. So within Ubuntu something probably needs to be done about fwupd-refresh.service. One proposal is to remove DynamicUser=yes from the systemd unit, but this will mean fwupdgmr refresh runs as root. It's relatively sandboxed by other security mechanisms, but still not ideal. Could we repurpose any other service account? Or alternatively we can make a new fwupd service account that this systemd unit uses. To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1969976/+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 1989371] Re: test_crash_setuid_unpackaged fails with psutil.NoSuchProcess: process no longer exists
** Changed in: apport (Ubuntu) Importance: Undecided => High ** Changed in: apport (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1989371 Title: test_crash_setuid_unpackaged fails with psutil.NoSuchProcess: process no longer exists Status in Apport: New Status in apport package in Ubuntu: Triaged Bug description: test_crash_setuid_unpackaged is racy and rarely fails with: == ERROR: test_crash_setuid_unpackaged (tests.integration.test_signal_crashes.T) report generation for unpackaged setuid program -- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/psutil/_pslinux.py", line 1661, in wrapper return fun(self, *args, **kwargs) File "/usr/lib/python3/dist-packages/psutil/_pslinux.py", line 1782, in cmdline data = f.read() ProcessLookupError: [Errno 3] No such process During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/tmp/autopkgtest.ukiC2X/autopkgtest_tmp/tests/integration/test_signal_crashes.py", line 746, in test_crash_setuid_unpackaged self.do_crash( File "/tmp/autopkgtest.ukiC2X/autopkgtest_tmp/tests/integration/test_signal_crashes.py", line 918, in do_crash command_process = self.wait_for_gdb_child_process( File "/tmp/autopkgtest.ukiC2X/autopkgtest_tmp/tests/integration/test_signal_crashes.py", line 1088, in wait_for_gdb_child_process cmdline = process.cmdline() File "/usr/lib/python3/dist-packages/psutil/__init__.py", line 684, in cmdline return self._proc.cmdline() File "/usr/lib/python3/dist-packages/psutil/_pslinux.py", line 1665, in wrapper raise NoSuchProcess(self.pid, self._name) psutil.NoSuchProcess: process no longer exists (pid=3767) -- Failing autopkgtest: https://autopkgtest.ubuntu.com/results/autopkgtest- kinetic/kinetic/arm64/a/apport/20220825_140850_23979@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1989371/+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 1989352] Re: [WSL] Prepare kinetic for common snap use cases
Given that these seed changes are happening for Kinetic and the work done in ubuntu-release-upgrader to support WSL upgrades have upgrades from Jammy to Kinetic been considered? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1989352 Title: [WSL] Prepare kinetic for common snap use cases Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: Users of Ubuntu WSL might be surprised by unexpected dependencies when dealing with snaps. The Ubuntu WSL development team is looking for ways to let early adopters to experiment some snapd support in Kinetic, while still providing the most seamless experience for them. Tests done in WSL instances showed surprises that we should mitigate soon. Some examples are: * Sublime Text and Sublime Merge apps silently depend on libgl1. This seems a bug which we didn't yet figure out how to fix in the snaps themselves. Being such hidden dependencies, we'd expect to soon find similar cases as those. * Flutter snap provides all dependencies and runs without issues, but apps compiled by Flutter requires libgl1, libegl1 and libgtk-3-0 present in the system during development. Attempting to just run any app compiled with Flutter during development will result in crash due those libs not being found. Most likely, once package as snaps, those apps will behave as expected, if the packager lists dependencies properly. The issue reported here affects the app developer experience. One solution for those problems is seeding for Ubuntu WSL specifically: - libgl1 - libegl1 - libgtk-3-0 Experienced Ubuntu users would figure out how to overcome those issues very quickly, but we should expect that most of Ubuntu WSL userbase won't fit in that persona. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1989352/+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 1989365] Re: test_omit_all_processes_except_one is racy and fails sometimes
** Changed in: apport (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1989365 Title: test_omit_all_processes_except_one is racy and fails sometimes Status in Apport: New Status in apport package in Ubuntu: Confirmed Bug description: The test case test_omit_all_processes_except_one is racy and fails sometimes: ``` test_omit_all_processes_except_one (tests.system.test_unkillable_shutdown.TestUnkillableShutdown) unkillable_shutdown will write exactly one report. ... Running as unit: run-r0b0d3fe87473410c9eb61a5ae4635938.service FAIL == FAIL: test_omit_all_processes_except_one (tests.system.test_unkillable_shutdown.TestUnkillableShutdown) unkillable_shutdown will write exactly one report. -- Traceback (most recent call last): File "/tmp/autopkgtest.JJoBfX/autopkgtest_tmp/tests/system/test_unkillable_shutdown.py", line 96, in test_omit_all_processes_except_one pid = self._launch_process_with_different_session_id(existing_pids) File "/tmp/autopkgtest.JJoBfX/autopkgtest_tmp/tests/system/test_unkillable_shutdown.py", line 90, in _launch_process_with_different_session_id self.assertEqual(len(test_executable_pids), 1, test_executable_pids) AssertionError: 0 != 1 : set() -- ``` autopkgtest log: https://autopkgtest.ubuntu.com/results/autopkgtest- kinetic/kinetic/amd64/a/apport/20220912_055849_5f03e@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1989365/+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 1974115] Re: [UBUNTU 22.04] BINUTILS: Adding new platform name IBM z16
Hi Andreas, thanks for the verification, I'm going to adjust the tags accordingly. Don't worry about the potential regression, it's an automated mail based on the results of the autopkgtests that run automatically while processing such an SRU like this - and binutils trigger a lot of tests. Such regressions can be caused by several different things, like a different package that is handled at the same time and triggers similar tests or a flaky test etc. - we deal with it. (IF we think it's due to s390x-specific code, we may reach out to you ;-) ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1974115 Title: [UBUNTU 22.04] BINUTILS: Adding new platform name IBM z16 Status in Ubuntu on IBM z Systems: Fix Committed Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Jammy: Fix Committed Status in binutils source package in Kinetic: Fix Released Bug description: SRU Justification: == [Impact] * As of today the architectural (level) name 'arch14' is used as CPU name for the new IBM z16 system. * The real name 'z16' couldn't be used until officially announced. * That happened meanwhile, hence we can now add and use the real name. [Test Plan] * Check if the same (proper) opcodes are detected on an IBM z16 system with and without the patch. Since only the identification and name of a z16 system was modified. * Or the simplest test is probably to check (after having 'binutils' installed on an Ubuntu 22.04 s390x system) if not only: 'as -m64 -march=arch14 --target-help' but also: 'as -m64 -march=z16 --target-help' succeeds and leads to the same output. (As it does for '-march=arch13' and '-march=arch15'.) [Where problems could occur] * Issues could happen if the conditional statement that look for architectural / CPU name are paired wrongly, since: * 'z16' belongs to 'arch14', 'z15' to 'arch13', etc. * If these pairs are not handled correctly, or the identification is erroneous a wrong system might be identified and wrong instructions used etc. [Other] * This is a hardware enablement SRU to enhance the IBM z16 support. __ After the announcement support for the official machine name z16 has been added to binutils. Please consider picking up the following patch from 2.37 branch: commit e24d2a2d11008aa363366c1087219f3e3405782a (origin/binutils-2_37-branch, 2.37) IBM zSystems: Add support for z16 as CPU name. So far z16 was identified as arch14. After the machine has been announced we can now add the real name. (cherry picked from commit 69341966def7f6551bc4452684136831d6a6941c) (cherry picked from commit fb4d148004f28494e9fb5d2400a13308d07a7988) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1974115/+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 1988119] Re: systemd-udevd: Run net_setup_link on 'change' uevents to prevent DNS outages on Azure
This bug was fixed in the package systemd - 237-3ubuntu10.56 --- systemd (237-3ubuntu10.56) bionic-security; urgency=medium * debian/udev.preinst: Add check_ID_NET_DRIVER() to ensure that on upgrade or install from an earlier version ID_NET_DRIVER is present on network interfaces. (LP: #1988119) -- Matthew Ruffell Tue, 06 Sep 2022 15:18:05 +1200 ** Changed in: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1988119 Title: systemd-udevd: Run net_setup_link on 'change' uevents to prevent DNS outages on Azure Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: [Impact] A widespread outage was caused on Azure instances earlier today, when systemd 237-3ubuntu10.54 was published to the bionic-security pocket. Instances could no longer resolve DNS queries, breaking networking. For affected users, the following workarounds are available. Use whatever is most convenient. - Reboot your instances - or - - Issue "udevadm trigger -cadd -yeth0 && systemctl restart systemd-networkd" as root The trigger was found to be open-vm-tools issuing "udevadm trigger". Azure has a specific netplan setup that uses the `driver` match to set up networking. If a udevadm trigger is executed, the KV pair that contains this info is lost. Next time netplan is executed, the server loses it's DNS information. This is the same as bug 1902960 experienced on Focal two years ago. The root cause was found to be a bug in systemd, where if we receive a "Remove" action from a change uevent, we need to run net_setup_link(), we need to skip device rename and keep the old name. [Testcase] Start an instance up on Azure, any type. Simply issue udevadm trigger and reload systemd-networkd: $ ping google.com PING google.com (172.253.62.102) 56(84) bytes of data. 64 bytes from bc-in-f102.1e100.net (172.253.62.102): icmp_seq=1 ttl=56 time=1.85 ms $ sudo udevadm trigger && sudo systemctl restart systemd-networkd $ ping google.com ping: google.com: Temporary failure in name resolution To fix a broken instance, you can run: $ sudo udevadm trigger -cadd -yeth0 && sudo systemctl restart systemd- networkd and then install the test packages below: Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf343528-test If you install them, the issue should no longer occur. [Where problems could occur] If a regression were to occur, it would affect systemd-udevd processing 'change' events from network devices, which could lead to network outages. Since this would happen when systemd-networkd is restarted on postinstall, a regression would cause widespread outages due to this SRU being targeted to the security pocket, where unattended-upgrades will automatically install from. Side effects could include incorrect udevd device properties. It is very important that this SRU is well tested before release. [Other info] This was fixed in Systemd 247 with the following commit: commit e0e789c1e97e2cdf1cafe0c6b7d7e43fa054f151 Author: Yu Watanabe Date: Mon, 14 Sep 2020 15:21:04 +0900 Subject: udev: re-assign ID_NET_DRIVER=, ID_NET_LINK_FILE=, ID_NET_NAME= properties on non-'add' uevent Link: https://github.com/systemd/systemd/commit/e0e789c1e97e2cdf1cafe0c6b7d7e43fa054f151 This was backported to Focal's systemd 245.4-4ubuntu3.4 in bug 1902960 two years ago. Focal required a heavy backport, which was performed by Dan Streetman. Focals backport can be found in d/p/lp1902960-udev-re- assign-ID_NET_DRIVER-ID_NET_LINK_FILE-ID_NET.patch, or the below pastebin: https://paste.ubuntu.com/p/K5k7bGt3Wx/ The changes between the Focal backport and the Bionic backport are: - We use udev_device_get_action() instead of device_get_action() - device_action_from_string() is used to get to enum DeviceAction - We return 0 from the "if (a == DEVICE_ACTION_MOVE) " hunk instead of "goto no_rename" - log_device_* has been changed to log_*. See attached debdiff for Bionic backport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1971901] Re: dlltool uses non-unique temp filenames
It's fixed upstream on the 2.38 branch too, and kinetic has that update in binutils-source_2.38-4ubuntu1. So binutils-mingw-w64 just needs to be recompiled against that latest binutils-source package (no other changes needed, it already pulls the latest). And ideally an SRU back to jammy LTS, just as upstream backported it to 2.38. But I'm not someone who can actually make that upload... -- 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/1971901 Title: dlltool uses non-unique temp filenames Status in binutils: Fix Released Status in Wine: Won't Fix Status in binutils package in Ubuntu: Confirmed Status in binutils-mingw-w64 package in Ubuntu: Confirmed Bug description: Description:Ubuntu 22.04 LTS Release:22.04 binutils-mingw-w64-x86-64 2.38-3ubuntu1+9build1 /usr/bin/x86_64-w64-mingw32-dlltool now encounters errors like tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o dlls/winmm/libwinmm.delay.a --export \ ../wine-6.0.4/dlls/winmm/winmm.spec Assembler messages: Error: can't open winmm_dll_t.s for reading: No such file or directory /usr/bin/x86_64-w64-mingw32-dlltool: /usr/bin/x86_64-w64-mingw32-as exited with status 1 /usr/bin/x86_64-w64-mingw32-dlltool: failed to open temporary tail file: winmm_dll_t.o: No such file or directory winebuild: /usr/bin/x86_64-w64-mingw32-dlltool failed with status 1 make: *** [Makefile:195227: dlls/winmm/libwinmm.delay.a] Error 1 make: *** Waiting for unfinished jobs tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o dlls/winmm/libwinmm.cross.a --export \ ../wine-6.0.4/dlls/winmm/winmm.spec Due to dlltool using names like winmm_dll_t.s and winmm_dll_t.o for it's temp file - these are not unique when building libwinmm.delay.a and libwinmm.cross.a in parallel. (This can of course affect any dll wine is building import libs for, winmm is just the one I happaned to get caught on). This is regression newly introduced in binutils 2.38 vs older versions which used getpid() as the basis of their temp name. We just encountered it as part of updating our CI for a winelib application from focal to jammy, but it seems to have been discovered by others already: see https://sourceware.org/bugzilla/show_bug.cgi?id=28885 There is an upstream fix on master (2.39) which is already backported to the binutils-2_38 branch: https://sourceware.org/git/gitweb.cgi?p=binutils- gdb.git;h=99852365513266afdd793289813e8e565186c9e6, so it should just be a matter of cherry-picking. Hopefully the fact it's a regression from impish->jammy and that upstream already backported it to 2.38 might make this a candidate for jammy-updates? To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1971901/+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 1964506] Re: Ping: checks payloads incorrectly, ignores all mismatch replies
** Also affects: iputils (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1964506 Title: Ping: checks payloads incorrectly, ignores all mismatch replies Status in iputils package in Ubuntu: New Status in iputils source package in Focal: New Bug description: Problematic commit reverted upstream causing incorrect behavior in Ubuntu Focal. Discussion: https://github.com/iputils/iputils/issues/320 Fix: https://github.com/iputils/iputils/pull/321 Release: https://github.com/iputils/iputils/releases/tag/20210722 Could this patch be added for a Focal update please? 1) Ubuntu 20.04.3 LTS 2) 3:20190709-3 3) focal$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. --- 8.8.8.8 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms 4) xenial$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. 76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated) --- 8.8.8.8 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1964506/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1988994] Re: TEST-58-REPART autopkgtest failure on ppc64el
The TEST-58-REPART test was skipped in the ppc64el autopkgtest run of systemd 249.11-0ubuntu3.6: https://autopkgtest.ubuntu.com/results/autopkgtest- jammy/jammy/ppc64el/s/systemd/20220912_215034_cf2f5@/log.gz. This demonstrates the fix works as intended. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1988994 Title: TEST-58-REPART autopkgtest failure on ppc64el Status in systemd package in Ubuntu: New Status in systemd source package in Jammy: Fix Committed Bug description: [Impact] With systemd 249.11-0ubuntu3.5 in jammy-proposed, which enables systemd-repart, the TEST-58-REPART fails on ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest- jammy/jammy/ppc64el/s/systemd/20220906_165335_6dd88@/log.gz. After trying to cherry-pick upstream commits, including [1], the test is still failing on ppc64el. This may be a testbed issue, and for now it seems the best course is to skip the test. [Test Plan] This fix is verified by TEST-58-REPART being skipped on ppc64el. [Where problems could occur] If we messed up the denylist usage, the test would not be skipped, or a different one would be. [1] https://github.com/systemd/systemd/commit/8e65d93e85f06e3f2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988994/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1974115] Comment bridged from LTC Bugzilla
--- Comment From andreas.kreb...@de.ibm.com 2022-09-13 10:40 EDT--- I've installed binutils 2.38-4ubuntu2 on jammy. With that the -march=z16 option is accepted by 'as'. So looks good to me. No idea about the regressions mentioned above. I don't see how an IBM zSystems only patch can affect builds on arm and amd64. -- 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/1974115 Title: [UBUNTU 22.04] BINUTILS: Adding new platform name IBM z16 Status in Ubuntu on IBM z Systems: Fix Committed Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Jammy: Fix Committed Status in binutils source package in Kinetic: Fix Released Bug description: SRU Justification: == [Impact] * As of today the architectural (level) name 'arch14' is used as CPU name for the new IBM z16 system. * The real name 'z16' couldn't be used until officially announced. * That happened meanwhile, hence we can now add and use the real name. [Test Plan] * Check if the same (proper) opcodes are detected on an IBM z16 system with and without the patch. Since only the identification and name of a z16 system was modified. * Or the simplest test is probably to check (after having 'binutils' installed on an Ubuntu 22.04 s390x system) if not only: 'as -m64 -march=arch14 --target-help' but also: 'as -m64 -march=z16 --target-help' succeeds and leads to the same output. (As it does for '-march=arch13' and '-march=arch15'.) [Where problems could occur] * Issues could happen if the conditional statement that look for architectural / CPU name are paired wrongly, since: * 'z16' belongs to 'arch14', 'z15' to 'arch13', etc. * If these pairs are not handled correctly, or the identification is erroneous a wrong system might be identified and wrong instructions used etc. [Other] * This is a hardware enablement SRU to enhance the IBM z16 support. __ After the announcement support for the official machine name z16 has been added to binutils. Please consider picking up the following patch from 2.37 branch: commit e24d2a2d11008aa363366c1087219f3e3405782a (origin/binutils-2_37-branch, 2.37) IBM zSystems: Add support for z16 as CPU name. So far z16 was identified as arch14. After the machine has been announced we can now add the real name. (cherry picked from commit 69341966def7f6551bc4452684136831d6a6941c) (cherry picked from commit fb4d148004f28494e9fb5d2400a13308d07a7988) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1974115/+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 1989433] Re: Security patch only available via proposed repository
Typically, when a version of a package is in -proposed for a stable release, that is because it is going through the SRU process and is in the minimum 7-day aging period [1]. In this case, systemd 237-3ubuntu10.54 was removed from -security due to a serious regression [2]. A fix is being worked on to avoid the regression, and it will be released to -security when it is ready. [1] https://wiki.ubuntu.com/StableReleaseUpdates [2] https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119 ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- 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/1989433 Title: Security patch only available via proposed repository Status in systemd package in Ubuntu: Invalid Bug description: Hello on Ubuntu 18.04, systemd 237-3ubuntu10.54 has a fix for CVE-2022-2526, however this version is only available in proposed, see[1] - not in updates or security - so most users are on 237-3ubuntu10.53. I would expect security updates in the updates or security repo. ~frukto lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 apt-cache policy systemd systemd: Installed: 237-3ubuntu10.54 Candidate: 237-3ubuntu10.54 Version table: *** 237-3ubuntu10.54 100 100 /var/lib/dpkg/status 237-3ubuntu10.53 500 500 http://ubuntu.ethz.ch/ubuntu bionic-updates/main amd64 Packages 237-3ubuntu10.50 500 500 http://ubuntu.ethz.ch/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://ubuntu.ethz.ch/ubuntu bionic/main amd64 Packages [1] https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1989433/+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 1950996] Re: Missing all modules for usb nics in initrd which makes PXE boot impossible
Hello, we are also experiencing this problem and would like to see it resolved. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1950996 Title: Missing all modules for usb nics in initrd which makes PXE boot impossible Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Focal: Confirmed Status in initramfs-tools source package in Hirsute: Confirmed Status in initramfs-tools source package in Impish: Won't Fix Status in initramfs-tools source package in Jammy: Fix Released Status in initramfs-tools package in Debian: Fix Released Bug description: initrd taken from the live iso for PXE boot does not contain USB NIC drivers which makes PXE installation/netboot impossible via usb. This is the case on 20.04 server iso (both hwe and normal kernel/initrd) and desktop iso. "kernel/drivers/net/usb" is empty and needs to be included in the initramfs build. As most modern thin laptops lack physical rj45 ethernet this is a big issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.8.0-64.72-generic 5.8.18 Uname: Linux 5.8.0-64-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 15 16:47:45 2021 PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to focal on 2020-05-11 (552 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1950996/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1982462] Re: Some modprobe loading services requested by the pstore service fail
Since the 249.11-0ubuntu3.6 upload of systemd only contains a change to skip an autopkgtest, Alfonso's previous verification on jammy using 249.11-0ubuntu3.6 is still valid (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982462/comments/11). ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1982462 Title: Some modprobe loading services requested by the pstore service fail Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] It has been detected that some modprobe services fail on UC22 after the jammy upgrade 249.11-0ubuntu3.4: $ systemctl --system --no-ask-password --no-pager list-units --state=failed Failed units: UNIT LOAD ACTIVE SUBDESCRIPTION ● modprobe@chromeos_pstore.service loaded failed failed Load Kernel Module chromeos_pstore ● modprobe@efi_pstore.service loaded failed failed Load Kernel Module efi_pstore ● modprobe@mtdpstore.service loaded failed failed Load Kernel Module mtdpstore ● modprobe@pstore_blk.service loaded failed failed Load Kernel Module pstore_blk ● modprobe@pstore_zone.service loaded failed failed Load Kernel Module pstore_zone ● modprobe@ramoops.service loaded failed failed Load Kernel Module ramoops This happens because of some changes to systemd-pstore.service that now has: After=modprobe@efi_pstore.service modprobe@mtdpstore.service modprobe@chromeos_pstore.service modprobe@ramoops.service modprobe@pstore_zone.service modprobe@pstore_blk.service Wants=modprobe@efi_pstore.service modprobe@mtdpstore.service modprobe@chromeos_pstore.service modprobe@ramoops.service modprobe@pstore_zone.service modprobe@pstore_blk.service This causes too many tries of the modprobe services, that fail in the end with Jul 20 09:02:39 ubuntu systemd[1]: modprobe@chromeos_pstore.service: Start request repeated too quickly. Although we have seen this only on UC22, it potentially can affect classic systems as well, as systemd-pstore.service is re-tried there a few times too. See https://github.com/snapcore/core-base/issues/72 for more details. A fix for this is available upstream: https://github.com/systemd/systemd/commit/9625350e5381a68c1179ae4581e7586c206663e1 [Test Plan] Start the device and check that there is no modprobe-pstore related failed service. This is racy, so a few tries will be needed to make sure things are fine. [Where problems could occur] The modprobe services are usually dependencies from other services, so it should be fine if the retry behavior is controlled by those other services. Risk should be small. If something goes wrong we might see a lot of restarts for these services. [Other Info] Testing should happen on UC22 too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982462/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1989457] Re: Enable riscv64 build
This should not need a feature freeze exception as we only supply a new package for the riscv64 architecture which is not preinstalled on any image. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1989457 Title: Enable riscv64 build Status in systemd package in Ubuntu: Confirmed Bug description: The upstream source supports building systemd-boot for the riscv64 architecture. We just haven't enabled it yet in debian/control. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1989457/+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 1989467] [NEW] Several autopkgtest failures on Ubuntu 22.04 and older
Public bug reported: All autopkgtest fail on Ubuntu 22.04 (jammy) and older: https://autopkgtest.ubuntu.com/packages/apport Following test cases fail: * backend_apt_dpkg: ** test_get_dependencies (armhf) ** test_get_source_tree_sandbox (arm64, armhf, ppc64el) ** test_install_old_packages (arm64, armhf, ppc64el) ** test_install_package_from_a_ppa (arm64, armhf, ppc64el) ** test_install_packages_dependencies (arm64, armhf, ppc64el) ** test_install_packages_from_launchpad (arm64, armhf, ppc64el) ** test_install_packages_permanent_sandbox (arm64, armhf, ppc64el) ** test_install_packages_permanent_sandbox_repack (arm64, armhf, ppc64el) ** test_install_packages_unversioned (arm64, armhf, ppc64el) ** test_install_packages_versioned (arm64, armhf, ppc64el) * hookutils: ** test_module_license_evaluation (armhf) * python_crashes: ** test_dbus_service_timeout_running (armhf) ** test_dbus_service_unknown_wrongbus_notrunning (armhf) * report: ** test_add_gdb_info_abort (armhf) ** test_add_gdb_info_script (armhf) ** test_add_zz_parse_segv_details (arm64, armhf, ppc64el, s390x) * signal_crashes: ** test_core_dump_packaged (armhf, ppc64el, s390x) ** test_core_dump_unpackaged (armhf) ** test_core_file_injection (armhf) ** test_crash_system_slice (amd64, ppc64el, s390x) ** test_empty_core_dump (follow-up failure for test_crash_system_slice) ** test_flood_limit (follow-up failure for test_crash_system_slice) ** test_ignore (follow-up failure for test_crash_system_slice) ** test_ignore_sigquit (follow-up failure for test_crash_system_slice) * ui: ** test_run_crash_kernel (arm64, s390x) ** Affects: apport (Ubuntu) Importance: High Status: Fix Released ** Affects: apport (Ubuntu Focal) Importance: High Status: Triaged ** Affects: apport (Ubuntu Jammy) Importance: High Status: Triaged ** Also affects: apport (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: apport (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: apport (Ubuntu) Status: New => Fix Released ** Changed in: apport (Ubuntu) Importance: Undecided => High ** Changed in: apport (Ubuntu Focal) Importance: Undecided => High ** Changed in: apport (Ubuntu Focal) Status: New => Triaged ** Changed in: apport (Ubuntu Jammy) Importance: Undecided => High ** Changed in: apport (Ubuntu Jammy) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1989467 Title: Several autopkgtest failures on Ubuntu 22.04 and older Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Triaged Status in apport source package in Jammy: Triaged Bug description: All autopkgtest fail on Ubuntu 22.04 (jammy) and older: https://autopkgtest.ubuntu.com/packages/apport Following test cases fail: * backend_apt_dpkg: ** test_get_dependencies (armhf) ** test_get_source_tree_sandbox (arm64, armhf, ppc64el) ** test_install_old_packages (arm64, armhf, ppc64el) ** test_install_package_from_a_ppa (arm64, armhf, ppc64el) ** test_install_packages_dependencies (arm64, armhf, ppc64el) ** test_install_packages_from_launchpad (arm64, armhf, ppc64el) ** test_install_packages_permanent_sandbox (arm64, armhf, ppc64el) ** test_install_packages_permanent_sandbox_repack (arm64, armhf, ppc64el) ** test_install_packages_unversioned (arm64, armhf, ppc64el) ** test_install_packages_versioned (arm64, armhf, ppc64el) * hookutils: ** test_module_license_evaluation (armhf) * python_crashes: ** test_dbus_service_timeout_running (armhf) ** test_dbus_service_unknown_wrongbus_notrunning (armhf) * report: ** test_add_gdb_info_abort (armhf) ** test_add_gdb_info_script (armhf) ** test_add_zz_parse_segv_details (arm64, armhf, ppc64el, s390x) * signal_crashes: ** test_core_dump_packaged (armhf, ppc64el, s390x) ** test_core_dump_unpackaged (armhf) ** test_core_file_injection (armhf) ** test_crash_system_slice (amd64, ppc64el, s390x) ** test_empty_core_dump (follow-up failure for test_crash_system_slice) ** test_flood_limit (follow-up failure for test_crash_system_slice) ** test_ignore (follow-up failure for test_crash_system_slice) ** test_ignore_sigquit (follow-up failure for test_crash_system_slice) * ui: ** test_run_crash_kernel (arm64, s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1989467/+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 1989457] Re: Enable riscv64 build
** Patch added: "systemd-251.4-1ubuntu4..251.4-1ubuntu5.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1989457/+attachment/5615517/+files/systemd-251.4-1ubuntu4..251.4-1ubuntu5.debdiff -- 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/1989457 Title: Enable riscv64 build Status in systemd package in Ubuntu: New Bug description: The upstream source supports building systemd-boot for the riscv64 architecture. We just haven't enabled it yet in debian/control. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1989457/+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 1989457] Re: Enable riscv64 build
** Tags added: fr-2681 -- 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/1989457 Title: Enable riscv64 build Status in systemd package in Ubuntu: New Bug description: The upstream source supports building systemd-boot for the riscv64 architecture. We just haven't enabled it yet in debian/control. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1989457/+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 1989457] [NEW] Enable riscv64 build
Public bug reported: The upstream source supports building systemd-boot for the riscv64 architecture. We just haven't enabled it yet in debian/control. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: riscv64 ** Tags added: riscv64 -- 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/1989457 Title: Enable riscv64 build Status in systemd package in Ubuntu: New Bug description: The upstream source supports building systemd-boot for the riscv64 architecture. We just haven't enabled it yet in debian/control. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1989457/+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 1989433] Re: Security patch only available via proposed repository
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1989433 Title: Security patch only available via proposed repository Status in systemd package in Ubuntu: Confirmed Bug description: Hello on Ubuntu 18.04, systemd 237-3ubuntu10.54 has a fix for CVE-2022-2526, however this version is only available in proposed, see[1] - not in updates or security - so most users are on 237-3ubuntu10.53. I would expect security updates in the updates or security repo. ~frukto lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 apt-cache policy systemd systemd: Installed: 237-3ubuntu10.54 Candidate: 237-3ubuntu10.54 Version table: *** 237-3ubuntu10.54 100 100 /var/lib/dpkg/status 237-3ubuntu10.53 500 500 http://ubuntu.ethz.ch/ubuntu bionic-updates/main amd64 Packages 237-3ubuntu10.50 500 500 http://ubuntu.ethz.ch/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://ubuntu.ethz.ch/ubuntu bionic/main amd64 Packages [1] https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1989433/+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 1989433] [NEW] Security patch only available via proposed repository
Public bug reported: Hello on Ubuntu 18.04, systemd 237-3ubuntu10.54 has a fix for CVE-2022-2526, however this version is only available in proposed, see[1] - not in updates or security - so most users are on 237-3ubuntu10.53. I would expect security updates in the updates or security repo. ~frukto lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 apt-cache policy systemd systemd: Installed: 237-3ubuntu10.54 Candidate: 237-3ubuntu10.54 Version table: *** 237-3ubuntu10.54 100 100 /var/lib/dpkg/status 237-3ubuntu10.53 500 500 http://ubuntu.ethz.ch/ubuntu bionic-updates/main amd64 Packages 237-3ubuntu10.50 500 500 http://ubuntu.ethz.ch/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://ubuntu.ethz.ch/ubuntu bionic/main amd64 Packages [1] https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.54 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1989433 Title: Security patch only available via proposed repository Status in systemd package in Ubuntu: New Bug description: Hello on Ubuntu 18.04, systemd 237-3ubuntu10.54 has a fix for CVE-2022-2526, however this version is only available in proposed, see[1] - not in updates or security - so most users are on 237-3ubuntu10.53. I would expect security updates in the updates or security repo. ~frukto lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 apt-cache policy systemd systemd: Installed: 237-3ubuntu10.54 Candidate: 237-3ubuntu10.54 Version table: *** 237-3ubuntu10.54 100 100 /var/lib/dpkg/status 237-3ubuntu10.53 500 500 http://ubuntu.ethz.ch/ubuntu bionic-updates/main amd64 Packages 237-3ubuntu10.50 500 500 http://ubuntu.ethz.ch/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://ubuntu.ethz.ch/ubuntu bionic/main amd64 Packages [1] https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1989433/+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 1989434] [NEW] poppler 0.62.0-2ubuntu2.13 breaks GDAL compilation
Public bug reported: The security update poppler 0.62.0-2ubuntu2.13 that fixes CVE-2022-38784 adds a new header file goo/GooCheckedOps.h that is included by goo/gmem.h goo/gmem.h is a file installed in the libpoppler-private-dev package, which is used by GDAL, but the patches added in the 0.62.0-2ubuntu2.13 update omit installing goo/GooCheckedOps.h, consequently any external code including goo/gmem.h breaks at compilation The following extra patch should fix this: ``` $ diff -u CMakeLists.txt.ori CMakeLists.txt --- CMakeLists.txt.ori 2022-09-13 10:58:42.282712260 +0200 +++ CMakeLists.txt 2022-09-13 10:58:44.198709344 +0200 @@ -578,6 +578,7 @@ goo/GooString.h goo/gtypes.h goo/gmem.h +goo/GooCheckedOps.h goo/gfile.h goo/FixedPoint.h goo/ImgWriter.h ``` ** Affects: poppler (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1989434 Title: poppler 0.62.0-2ubuntu2.13 breaks GDAL compilation Status in poppler package in Ubuntu: New Bug description: The security update poppler 0.62.0-2ubuntu2.13 that fixes CVE-2022-38784 adds a new header file goo/GooCheckedOps.h that is included by goo/gmem.h goo/gmem.h is a file installed in the libpoppler-private-dev package, which is used by GDAL, but the patches added in the 0.62.0-2ubuntu2.13 update omit installing goo/GooCheckedOps.h, consequently any external code including goo/gmem.h breaks at compilation The following extra patch should fix this: ``` $ diff -u CMakeLists.txt.ori CMakeLists.txt --- CMakeLists.txt.ori2022-09-13 10:58:42.282712260 +0200 +++ CMakeLists.txt2022-09-13 10:58:44.198709344 +0200 @@ -578,6 +578,7 @@ goo/GooString.h goo/gtypes.h goo/gmem.h +goo/GooCheckedOps.h goo/gfile.h goo/FixedPoint.h goo/ImgWriter.h ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1989434/+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 1892559] Re: [MIR] ccid opensc pcsc-lite
** Changed in: ccid (Ubuntu) Assignee: Ray Veldkamp (rayveldkamp) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1892559 Title: [MIR] ccid opensc pcsc-lite Status in ccid package in Ubuntu: In Progress Status in opensc package in Ubuntu: Incomplete Status in pam-pkcs11 package in Ubuntu: Invalid Status in pcsc-lite package in Ubuntu: New Status in pcsc-perl package in Ubuntu: Invalid Status in pcsc-tools package in Ubuntu: Invalid Bug description: ==> ccid <== [Availability] ccid is in universe, and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs for ccid are listed in our database. Doesn't appear to bind to a socket. No privileged executables, but does have udev rules. Probably needs a security review. [Quality assurance] No test suite. Does require odd hardware that we'll probably need to buy. I don't see debconf questions. ccid is well maintained in Debian by upstream author. One open wishlist bug in BTS, harmless. One open bug in launchpad, not security, but looks very frustrating for the users. The upstream author was engaged but it never reached resolution. https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465 Has a debian/watch file. Quilt packaging. P: ccid source: no-dep5-copyright P: ccid source: package-uses-experimental-debhelper-compat-version 13 [Dependencies] Minimal dependencies, in main [Standards compliance] Appears to satisfy FHS and Debian policy [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] ccid provides drivers to interact with usb-connected smart card readers. ==> libpam-pkcs11 <== [Availability] Source package pam-pkcs11 is in universe and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs in our database. Doesn't appear to bind to sockets. No privileged executables (but is a PAM module). As a PAM module this will require a security review. [Quality assurance] The package does not call pam-auth-update in its postinst #1650366 Does not ask questions during install. One Ubuntu bug claims very poor behaviour if a card isn't plugged in. No Debian bugs. Occasional updates in Debian by long-term maintainer. Does require odd hardware that we'll probably need to buy. Does not appear to run tests during build. Has scary warnings in the build logs. Has a debian/watch file. Ancient standards version; other smaller lintian messages, mostly documentation problems. Quilt packaging. [Dependencies] Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1 All are in main. [Standards compliance] The package does not call pam-auth-update in its postinst #1650366 Otherwise looks to conform to FHS and Debian policies [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] This PAM module can use CRLs and full-chain verification of certificates. It can also do LDAP, AD, and Kerberos username mapping. ==> libpcsc-perl <== [Availability] Source package pcsc-perl is in universe, builds for all architectures, plus i386 [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] There are no cves for pcsc-perl in our database. No privileged executables. Doesn't appear to bind to sockets. Probably needs a security review. [Quality assurance] Library package not intended to be used directly. No debconf questions. No bugs in Debian. No bugs in Ubuntu. Does require odd hardware that we'll probably need to buy. Tests exist, not run during the build; probably can't run during the build. Includes debian/watch file. A handful of lintian issues Quilt packaging. [Dependencies] libpcsc-perl depends upon libpcsclite1, libc6, perl, perlapi-5.30.0. All are in main. [Standards compliance] One oddity, Card.pod is stored in /usr/lib/x86_64-linux-gnu/perl5/5.30/Chipcard/PCSC/ Many other perl packages have .pod files in these directory trees so maybe it's fine, but it seems funny all the same. Otherwise appears to satisfy FHS and Debian policy. [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background info
[Touch-packages] [Bug 1988364] Re: Missing the A2DP profile and defaults to low quality
"May be notified" generally means people will be receiving some comments as emails, like when a bug is closed or changes status. Only "Notified of all changes" will be receiving all comments but even then expect those people to have email filters set up so they don't have to read everything. Usually very few people are listening :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1988364 Title: Missing the A2DP profile and defaults to low quality Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Released Bug description: Sony WH-1000XM4 missing the A2DP profile and defaults to low quality https://github.com/bluez/bluez/issues/313 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1988364/+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 1079232] Re: OpenCV built without Qt support
** Changed in: opencv (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opencv in Ubuntu. https://bugs.launchpad.net/bugs/1079232 Title: OpenCV built without Qt support Status in opencv package in Ubuntu: Triaged Status in opencv package in Debian: New Bug description: Is there any specific reason for openCV to be built without Qt support? The "new" Highgui Qt functions, already available in the version which ships with Ubuntu Precise, provide for much better user interfaces for simpler cases without having to build complete GUIs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1079232/+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 1988364] Re: Missing the A2DP profile and defaults to low quality
Thanks for clarifying, that makes sense now. Actually I just wanted to thank you, if there would be reactions to comments that would be great for that. But as I'm writing this comment now I got one other question: In the sidebar I see many people being listed under "May be notified". And I'm very sorry if all people listed there now receive an email because of this comment, I'm already feeling a bit guilty writing it just because I wanted to thank Daniel. But what does "May be notified" mean? Are there going emails out to everyone there? Edit: Is there maybe a "Getting Started with Launchpad", maybe even specific to Ubuntu? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1988364 Title: Missing the A2DP profile and defaults to low quality Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Released Bug description: Sony WH-1000XM4 missing the A2DP profile and defaults to low quality https://github.com/bluez/bluez/issues/313 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1988364/+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 1988702] Re: FFe: Upstream 2.9.0 release
This bug was fixed in the package mir - 2.9.0-0ubuntu2 --- mir (2.9.0-0ubuntu2) kinetic; urgency=medium * Cherry-pick series of build-system patches to disable false-positive -Werror on gcc-12 on some architectures * debian/rules: - Disable -Werror=restrict on libinput_environment on ppc64el - Disable -Werror=use-after-free on test_linearising_executor on riscv64 * Fixes FTBFS on ppc64el and riscv64 -- Christopher James Halse Rogers Tue, 13 Sep 2022 13:11:12 +1000 ** Changed in: mir (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1988702 Title: FFe: Upstream 2.9.0 release Status in mir package in Ubuntu: Fix Released Bug description: This is low-risk, as we have no reverse-dependencies in the archive. This bumps some SONAMEs (libmiral4 -> libmiral5, libmircore1 -> libmircore2, libmiroil1 -> libmiroil2). The autopkgtest (checking conformance against in-archive wlcs) passes. * New upstream release 2.9.0 - ABI summary: . miral ABI bumped to 5 . mircommon ABI unchanged at 9 . mircookie ABI unchanged at 2 . mircore ABI bumped to 2 . miroil ABI bumped to 2 . mirplatform ABI unchanged at 23 . mirserver ABI unchanged at 58 . mirwayland ABI unchanged at 3 . mirplatformgraphics ABI unchanged at 20 . mirinputplatform ABI unchanged at 8 - Enhancements: . [Wayland] Implement zwp_idle_inhibit_manager_v1 . [Wayland] Implement zwlr_virtual_pointer_v1 . [Wayland] Implement zwp_text_input_manager_v1 (Electron works with OSK) . [Wayland] Bump wl_seat to v8 and implement hi-res scrolling . [Wayland platform] improve failed to connect error . [Wayland platform] Port to xdg-shell (Fixes #1903, Fixes: #2434) . [MirAL] Allow `--add-wayland-extenions all` . [MirAL] Allow servers to get repeated string options . [MirAL] Improvement to ExternalClientLauncher: Don't force clients to split command lines themselves . [MirAL] Tidy up event filtering API . [MirAL] Expose miral::Zone::id() . [MirAL] Rename CommandLineOption => ConfigurationOption . [Input] Filter 2 distinct bogus touch event scenarios (UBports) . [gbm-kms] new driver quirk to disable KMS modeset probe . [gbm-kms] Add defaults to driver-quirks for nvidia and evdi (Fixes: #2467) . [gbm-kms] Add defaults to driver-quirks for vc4-drm and v3d . [mir-smoke-test-runner] Enable working in a Wayland only environment - Bugs fixed: . Fix ABI breakage of libmircore.so.1 with v2.8.0 vs v1.8.2 (Fixes #2465) . [Wayland] Text Input v2: do not use commit count as serial . [Wayland] Send keyboard modifiers after keyboard enter (Fixes: #2535, Fixes: #2025) . [Wayland] wlr-screencopy-v1: send .damage event as required (wayvnc fix) . [Wayland] wlr-screencopy-v1: Waits until the copy area has been damaged in `.copy_with_damage` request (wayvnc fix) . [MirAL] Unblock signals before execing child processes (Fixes: #1284) . [eglstream-kms] Kill clients, not Mir, when they submit bad EGLStreams (Fixes: #2061) . [eglstream-kms] Handle EGL errors in devnum_for_device (Fixes: #2426) . [test clients] Explicitly ask for a GLESv2 context (Fixes: #2440) . [renderers/gl] Clear framebuffer to opaque black (Fixes: #2427) . CMake cleanup for locally built dependencies (Fixes: #2507, Fixes: #2261) . Fix event timestamps (Fixes: #2577) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1988702/+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 1079232] Re: OpenCV built without Qt support
The attachment "4.5.4+dfsg-9ubuntu4.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.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opencv in Ubuntu. https://bugs.launchpad.net/bugs/1079232 Title: OpenCV built without Qt support Status in opencv package in Ubuntu: Triaged Status in opencv package in Debian: Unknown Bug description: Is there any specific reason for openCV to be built without Qt support? The "new" Highgui Qt functions, already available in the version which ships with Ubuntu Precise, provide for much better user interfaces for simpler cases without having to build complete GUIs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1079232/+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 1889443] Re: "ValueError: ['separator'] has no binary content" when running `apport-unpack /var/crash/...`
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apport (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1889443
Title:
"ValueError: ['separator'] has no binary content" when running
`apport-unpack /var/crash/...`
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Bionic:
Confirmed
Status in apport source package in Focal:
Confirmed
Status in apport source package in Jammy:
Confirmed
Bug description:
The crash file I'm using is as-produced by the system (on groovy), and
appears to have an empty value for separator:
$ grep separator /var/crash/_usr_bin_neomutt.1000.crash
separator:
Traceback (most recent call last):
File "/usr/bin/apport-unpack", line 77, in
pr.extract_keys(f, bin_keys, dir)
File "/usr/lib/python3/dist-packages/problem_report.py", line 269, in
extract_keys
raise ValueError('%s has no binary content' %
ValueError: ['separator'] has no binary content
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: apport 2.20.11-0ubuntu42
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu42
Architecture: amd64
CasperMD5CheckResult: skip
CrashReports:
640:1000:117:1620030:2020-07-29 12:16:57.045274496 -0400:2020-07-29
12:19:15.559243636 -0400:/var/crash/_usr_bin_neomutt.1000.crash
640:1000:117:4399480:2020-07-23 10:30:21.433552906 -0400:2020-07-23
10:30:18.921508067 -0400:/var/crash/_usr_bin_pavucontrol.1000.crash
640:1000:117:29909:2020-07-29 12:19:15.603244279 -0400:2020-07-29
12:19:15.603244279 -0400:/var/crash/_usr_bin_apport-unpack.1000.crash
CurrentDesktop: i3
Date: Wed Jul 29 12:22:54 2020
InstallationDate: Installed on 2019-05-07 (448 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to groovy on 2020-06-22 (37 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1889443/+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 1889443] Re: "ValueError: ['separator'] has no binary content" when running `apport-unpack /var/crash/...`
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apport (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1889443
Title:
"ValueError: ['separator'] has no binary content" when running
`apport-unpack /var/crash/...`
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Bionic:
Confirmed
Status in apport source package in Focal:
Confirmed
Status in apport source package in Jammy:
Confirmed
Bug description:
The crash file I'm using is as-produced by the system (on groovy), and
appears to have an empty value for separator:
$ grep separator /var/crash/_usr_bin_neomutt.1000.crash
separator:
Traceback (most recent call last):
File "/usr/bin/apport-unpack", line 77, in
pr.extract_keys(f, bin_keys, dir)
File "/usr/lib/python3/dist-packages/problem_report.py", line 269, in
extract_keys
raise ValueError('%s has no binary content' %
ValueError: ['separator'] has no binary content
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: apport 2.20.11-0ubuntu42
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu42
Architecture: amd64
CasperMD5CheckResult: skip
CrashReports:
640:1000:117:1620030:2020-07-29 12:16:57.045274496 -0400:2020-07-29
12:19:15.559243636 -0400:/var/crash/_usr_bin_neomutt.1000.crash
640:1000:117:4399480:2020-07-23 10:30:21.433552906 -0400:2020-07-23
10:30:18.921508067 -0400:/var/crash/_usr_bin_pavucontrol.1000.crash
640:1000:117:29909:2020-07-29 12:19:15.603244279 -0400:2020-07-29
12:19:15.603244279 -0400:/var/crash/_usr_bin_apport-unpack.1000.crash
CurrentDesktop: i3
Date: Wed Jul 29 12:22:54 2020
InstallationDate: Installed on 2019-05-07 (448 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to groovy on 2020-06-22 (37 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1889443/+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 1889443] Re: "ValueError: ['separator'] has no binary content" when running `apport-unpack /var/crash/...`
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apport (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1889443
Title:
"ValueError: ['separator'] has no binary content" when running
`apport-unpack /var/crash/...`
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Bionic:
Confirmed
Status in apport source package in Focal:
Confirmed
Status in apport source package in Jammy:
Confirmed
Bug description:
The crash file I'm using is as-produced by the system (on groovy), and
appears to have an empty value for separator:
$ grep separator /var/crash/_usr_bin_neomutt.1000.crash
separator:
Traceback (most recent call last):
File "/usr/bin/apport-unpack", line 77, in
pr.extract_keys(f, bin_keys, dir)
File "/usr/lib/python3/dist-packages/problem_report.py", line 269, in
extract_keys
raise ValueError('%s has no binary content' %
ValueError: ['separator'] has no binary content
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: apport 2.20.11-0ubuntu42
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu42
Architecture: amd64
CasperMD5CheckResult: skip
CrashReports:
640:1000:117:1620030:2020-07-29 12:16:57.045274496 -0400:2020-07-29
12:19:15.559243636 -0400:/var/crash/_usr_bin_neomutt.1000.crash
640:1000:117:4399480:2020-07-23 10:30:21.433552906 -0400:2020-07-23
10:30:18.921508067 -0400:/var/crash/_usr_bin_pavucontrol.1000.crash
640:1000:117:29909:2020-07-29 12:19:15.603244279 -0400:2020-07-29
12:19:15.603244279 -0400:/var/crash/_usr_bin_apport-unpack.1000.crash
CurrentDesktop: i3
Date: Wed Jul 29 12:22:54 2020
InstallationDate: Installed on 2019-05-07 (448 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to groovy on 2020-06-22 (37 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1889443/+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 1988364] Re: Missing the A2DP profile and defaults to low quality
Yes you are right that it looks confusing, but this is how Launchpad works. A bug that is fixed in any release is closed. :/ Adding a task to fix it in 22.04 will reopen the bug just for 22.04 but generally we don't do that until someone is assigned to actually do the work. To request that a fix be considered in 22.04 you add the 'rls-jj- incoming' tag which has already been done in comment #1. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1988364 Title: Missing the A2DP profile and defaults to low quality Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Released Bug description: Sony WH-1000XM4 missing the A2DP profile and defaults to low quality https://github.com/bluez/bluez/issues/313 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1988364/+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 1988230] Re: glib 2.73 breaks modemmanager
** Changed in: glib Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1988230 Title: glib 2.73 breaks modemmanager Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Triaged Status in modemmanager package in Ubuntu: Fix Released Status in glib2.0 package in Debian: Fix Released Bug description: I'm filing this bug in case we want to fix it before letting glib 2.73 in to kinetic. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1988230/+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 1981385] Re: initrd lacks modules to mount boot image from http boot
@Michael, can you help backport this patch to Jammy too? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1981385 Title: initrd lacks modules to mount boot image from http boot Status in initramfs-tools package in Ubuntu: Fix Released Bug description: If you use UEFI http boot to boot an image (rather than an EFI executable) and get all the way to a normal userspace, you can access the boot image as /dev/pmem0. But this is not accessible in the initrd; presumably some modules are missing. Dimitri added some modules that are clearly going to be necessary (kernel/drivers/nvdimm) in 0.140ubuntu14 and I added kernel/drivers/dax too in local experiments but this appears not to be enough to get it to appear. This is desirable because then you can just feed an installer ISO to a machine via http boot and the installer just works as normal (the speed and, uh, quality, of the implementation of HTTP in a given machine's firmware may mean this isn't always the best option but it would be nice if it worked in case someone's machine actually does this well). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1981385/+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 1989410] [NEW] Not able to connect to hotspot because of WPA2 WPA3 security
Public bug reported:
Both security WPA2 and WPA3 displaying on the security section due to
this not able to connect the hotspot.
Same device and firmware working properly in ubuntu 20.04 OS, But in
ubuntu 22.04 we are facing this issue.
"nmcli dev wifi" on client side:
On Ubuntu 20.04:
IN-USE
SSID ubuntu_new_golden
MODE Infra
CHAN 1
RATE 130Mbit/s
SECURITY WPA2
On Ubuntu 22.04:
IN-USE
SSID ubuntu_new_golden
MODE Infra
CHAN 1
RATE 130Mbit/s
SECURITY WPA2 WPA3
Only difference we can see is SECURITY
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libwpa-client-dev 2:2.10-6ubuntu2
Uname: Linux 5.19.0-rpl-ww37bkc x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 15 12:23:41 2022
Dependencies:
InstallationDate: Installed on 2022-09-10 (4 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: wpa (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy wayland-session
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1989410
Title:
Not able to connect to hotspot because of WPA2 WPA3 security
Status in wpa package in Ubuntu:
New
Bug description:
Both security WPA2 and WPA3 displaying on the security section due to
this not able to connect the hotspot.
Same device and firmware working properly in ubuntu 20.04 OS, But in
ubuntu 22.04 we are facing this issue.
"nmcli dev wifi" on client side:
On Ubuntu 20.04:
IN-USE
SSID ubuntu_new_golden
MODE Infra
CHAN 1
RATE 130Mbit/s
SECURITY WPA2
On Ubuntu 22.04:
IN-USE
SSID ubuntu_new_golden
MODE Infra
CHAN 1
RATE 130Mbit/s
SECURITY WPA2 WPA3
Only difference we can see is SECURITY
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libwpa-client-dev 2:2.10-6ubuntu2
Uname: Linux 5.19.0-rpl-ww37bkc x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 15 12:23:41 2022
Dependencies:
InstallationDate: Installed on 2022-09-10 (4 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1989410/+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 1988364] Re: Missing the A2DP profile and defaults to low quality
But now it looks like a fix is released, no? Sorry, I'm still new to launchpad and not everything is obvious to me yet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1988364 Title: Missing the A2DP profile and defaults to low quality Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Released Bug description: Sony WH-1000XM4 missing the A2DP profile and defaults to low quality https://github.com/bluez/bluez/issues/313 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1988364/+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 1079232] Re: OpenCV built without Qt support
** Patch added: "4.5.4+dfsg-9ubuntu4.patch" https://bugs.launchpad.net/debian/+source/opencv/+bug/1079232/+attachment/5615395/+files/4.5.4+dfsg-9ubuntu4.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opencv in Ubuntu. https://bugs.launchpad.net/bugs/1079232 Title: OpenCV built without Qt support Status in opencv package in Ubuntu: Triaged Status in opencv package in Debian: Unknown Bug description: Is there any specific reason for openCV to be built without Qt support? The "new" Highgui Qt functions, already available in the version which ships with Ubuntu Precise, provide for much better user interfaces for simpler cases without having to build complete GUIs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1079232/+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 1079232] Re: OpenCV built without Qt support
** Patch added: "4.6.0+dfsg-4ubuntu4.patch" https://bugs.launchpad.net/debian/+source/opencv/+bug/1079232/+attachment/5615396/+files/4.6.0+dfsg-4ubuntu4.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opencv in Ubuntu. https://bugs.launchpad.net/bugs/1079232 Title: OpenCV built without Qt support Status in opencv package in Ubuntu: Triaged Status in opencv package in Debian: Unknown Bug description: Is there any specific reason for openCV to be built without Qt support? The "new" Highgui Qt functions, already available in the version which ships with Ubuntu Precise, provide for much better user interfaces for simpler cases without having to build complete GUIs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1079232/+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 1079232] Re: OpenCV built without Qt support
My patch enabling Qt support was merged into the Debian packaging repository (https://salsa.debian.org/science- team/opencv/-/commit/dbbcdf83190e06af47b052e1c7e422d5968e3218), so this bug will be fixed in the next release in Debian. I have attached patches that are rebased on the current versions in jammy and kinetic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opencv in Ubuntu. https://bugs.launchpad.net/bugs/1079232 Title: OpenCV built without Qt support Status in opencv package in Ubuntu: Triaged Status in opencv package in Debian: Unknown Bug description: Is there any specific reason for openCV to be built without Qt support? The "new" Highgui Qt functions, already available in the version which ships with Ubuntu Precise, provide for much better user interfaces for simpler cases without having to build complete GUIs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1079232/+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
