[Touch-packages] [Bug 1987485] [NEW] package libgstreamer1.0-dev:amd64 1.20.3-0ubuntu1 failed to install/upgrade: »installiertes libgstreamer1.0-dev:amd64-Skript des Paketes post-installation«-Unterpr
Public bug reported: error occurred during automatic system update from ubuntu 20.04 LTS to 22.04 LTS ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libgstreamer1.0-dev:amd64 1.20.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-124.140-generic 5.4.195 Uname: Linux 5.4.0-124-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Aug 24 06:36:54 2022 ErrorMessage: »installiertes libgstreamer1.0-dev:amd64-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 2 zurück InstallationDate: Installed on 2017-05-13 (1928 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: gstreamer1.0 Title: package libgstreamer1.0-dev:amd64 1.20.3-0ubuntu1 failed to install/upgrade: »installiertes libgstreamer1.0-dev:amd64-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 2 zurück UpgradeStatus: Upgraded to jammy on 2022-08-24 (0 days ago) ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987485 Title: package libgstreamer1.0-dev:amd64 1.20.3-0ubuntu1 failed to install/upgrade: »installiertes libgstreamer1.0-dev:amd64-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 2 zurück Status in gstreamer1.0 package in Ubuntu: New Bug description: error occurred during automatic system update from ubuntu 20.04 LTS to 22.04 LTS ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libgstreamer1.0-dev:amd64 1.20.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-124.140-generic 5.4.195 Uname: Linux 5.4.0-124-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Aug 24 06:36:54 2022 ErrorMessage: »installiertes libgstreamer1.0-dev:amd64-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 2 zurück InstallationDate: Installed on 2017-05-13 (1928 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: gstreamer1.0 Title: package libgstreamer1.0-dev:amd64 1.20.3-0ubuntu1 failed to install/upgrade: »installiertes libgstreamer1.0-dev:amd64-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 2 zurück UpgradeStatus: Upgraded to jammy on 2022-08-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1987485/+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 1982841] Re: [22.10 FEAT] [SEC2210] p11-kit: add IBM specific mechanisms and attributes (crypto)
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to p11-kit in Ubuntu. https://bugs.launchpad.net/bugs/1982841 Title: [22.10 FEAT] [SEC2210] p11-kit: add IBM specific mechanisms and attributes (crypto) Status in Ubuntu on IBM z Systems: Fix Released Status in p11-kit package in Ubuntu: Fix Released Bug description: Add support for IBM specific attributes and mechanis to the PKCS11 client-server implementation of p11-kit to p11-kit. This enables customers to access IBM Z HSMs remotely via a PKCS #11 API. Upstream Target: p11-kit 0.25.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982841/+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 1979079] Re: Can print to (brother) driverless printer only using aa-complain cupsd
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1979079 Title: Can print to (brother) driverless printer only using aa-complain cupsd Status in cups package in Ubuntu: Expired Bug description: The apparmor configuration for cupsd is incorrect and makes it impossible to print to driverless printers (at least to the brother printer I am trying). Cups cannot obtain the IP address of the printer. You get "No suitable Destination Host found by cups-browsed" There are multiple reports of this issue on the network, also wrt debian. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups-daemon 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Jun 17 18:19:32 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (852 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=/dev/mapper/VG_NVMe-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-06-03 (14 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1979079/+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 1982841] Re: [22.10 FEAT] [SEC2210] p11-kit: add IBM specific mechanisms and attributes (crypto)
This bug was fixed in the package p11-kit - 0.24.1-1ubuntu1 --- p11-kit (0.24.1-1ubuntu1) kinetic; urgency=medium * Add support for IBM specific attributes and mechanis by adding the following upstream commits as quilt patches (LP: #1982841): d/p/lp-1982841-Add-IBM-specific-mechanism-and-attributes.patch d/p/lp-1982841-Add-support-for-serializing-CK_ECDH1_DERIVE_PARAMS-m.patch d/p/lp-1982841-client-Allow-zero-part-length-at-C_SignUpdate.patch d/p/lp-1982841-Fix-support-of-CKA_DERIVE_TEMPLATE.patch d/p/lp-1982841-Add-other-SHA-variants-also-for-RSA-and-EC-signature.patch d/p/lp-1982841-Add-support-for-missing-AES-and-DES-DES3-mechanisms.patch d/p/lp-1982841-Add-support-for-MAC-and-HMAC-general-mechanisms.patch d/p/lp-1982841-Add-support-for-CKM_DH_PKCS_DERIVE.patch d/p/lp-1982841-rpc-Handle-special-cases-for-buffer-and-length.patch d/p/lp-1982841-Add-support-for-CKM_AES_CTR.patch d/p/lp-1982841-Add-support-for-CKM_AES_GCM.patch d/p/lp-1982841-common-pkcs11x.h-Support-CRYPTOKI_GNU-for-IBM-vendor.patch -- Frank Heimes Fri, 05 Aug 2022 15:25:36 +0200 ** Changed in: p11-kit (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to p11-kit in Ubuntu. https://bugs.launchpad.net/bugs/1982841 Title: [22.10 FEAT] [SEC2210] p11-kit: add IBM specific mechanisms and attributes (crypto) Status in Ubuntu on IBM z Systems: Fix Committed Status in p11-kit package in Ubuntu: Fix Released Bug description: Add support for IBM specific attributes and mechanis to the PKCS11 client-server implementation of p11-kit to p11-kit. This enables customers to access IBM Z HSMs remotely via a PKCS #11 API. Upstream Target: p11-kit 0.25.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982841/+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 1097467] Re: bash does not fulfill --rcfile option properly
** Patch added: "manpage-is-wrong.debdiff" https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+attachment/5611101/+files/manpage-is-wrong.debdiff ** Tags added: rls-kk-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1097467 Title: bash does not fulfill --rcfile option properly Status in bash package in Ubuntu: Confirmed Bug description: I am starting a bash shell using $ bash --noprofile --rcfile my-custom-bash-rc-file Due to the --rcflag, the newly started bash should *not* execute commands from /etc/bash.bashrc. That is at least how I interpret `man bash`: --rcfile file Execute commands from file instead of the system wide initialization file /etc/bash.bashrc and the standard personal initial‐ ization file ~/.bashrc if the shell is interactive (see INVOCATION below). However, it seems that the commands in /etc/bash.bashrc are in fact executed. To see/reproduce/diagnose this, on Ubuntu I believe one can just invoke bash like this (as the regular user): $ touch testrc $ env -i bash --noprofile --rcfile testrc The expected result would be that nothing special is printed on the terminal. However, there is an error message, which is printed from /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the invoked shell, which in turn triggers the error. The error message is: > To run a command as administrator (user "root"), use "sudo ". > See "man sudo_root" for details. Another way to see this -- without the "env -i" -- is to add a command to /etc/bash.bashrc, such as echo HELLO THERE To trigger the bug(?), one can then just do $ touch testrc $ bash --noprofile --rcfile testrc The expected result would be that nothing special is shown in the terminal. However, it turns out that the string HELLO THERE is printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+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 1097467] Re: bash does not fulfill --rcfile option properly
** Patch added: "bash-is-wrong.debdiff" https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+attachment/5611100/+files/bash-is-wrong.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1097467 Title: bash does not fulfill --rcfile option properly Status in bash package in Ubuntu: Confirmed Bug description: I am starting a bash shell using $ bash --noprofile --rcfile my-custom-bash-rc-file Due to the --rcflag, the newly started bash should *not* execute commands from /etc/bash.bashrc. That is at least how I interpret `man bash`: --rcfile file Execute commands from file instead of the system wide initialization file /etc/bash.bashrc and the standard personal initial‐ ization file ~/.bashrc if the shell is interactive (see INVOCATION below). However, it seems that the commands in /etc/bash.bashrc are in fact executed. To see/reproduce/diagnose this, on Ubuntu I believe one can just invoke bash like this (as the regular user): $ touch testrc $ env -i bash --noprofile --rcfile testrc The expected result would be that nothing special is printed on the terminal. However, there is an error message, which is printed from /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the invoked shell, which in turn triggers the error. The error message is: > To run a command as administrator (user "root"), use "sudo ". > See "man sudo_root" for details. Another way to see this -- without the "env -i" -- is to add a command to /etc/bash.bashrc, such as echo HELLO THERE To trigger the bug(?), one can then just do $ touch testrc $ bash --noprofile --rcfile testrc The expected result would be that nothing special is shown in the terminal. However, it turns out that the string HELLO THERE is printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+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 1097467] Re: bash does not fulfill --rcfile option properly
I'm unsure what the "correct" solution is here; could be that bash's behaviour is wrong, or it could be that the documentation is wrong. Rather than decide, I'm taking the cowards way out and attaching patches for both solutions, leaving it to the maintainer to decide which is appropriate :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1097467 Title: bash does not fulfill --rcfile option properly Status in bash package in Ubuntu: Confirmed Bug description: I am starting a bash shell using $ bash --noprofile --rcfile my-custom-bash-rc-file Due to the --rcflag, the newly started bash should *not* execute commands from /etc/bash.bashrc. That is at least how I interpret `man bash`: --rcfile file Execute commands from file instead of the system wide initialization file /etc/bash.bashrc and the standard personal initial‐ ization file ~/.bashrc if the shell is interactive (see INVOCATION below). However, it seems that the commands in /etc/bash.bashrc are in fact executed. To see/reproduce/diagnose this, on Ubuntu I believe one can just invoke bash like this (as the regular user): $ touch testrc $ env -i bash --noprofile --rcfile testrc The expected result would be that nothing special is printed on the terminal. However, there is an error message, which is printed from /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the invoked shell, which in turn triggers the error. The error message is: > To run a command as administrator (user "root"), use "sudo ". > See "man sudo_root" for details. Another way to see this -- without the "env -i" -- is to add a command to /etc/bash.bashrc, such as echo HELLO THERE To trigger the bug(?), one can then just do $ touch testrc $ bash --noprofile --rcfile testrc The expected result would be that nothing special is shown in the terminal. However, it turns out that the string HELLO THERE is printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+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 1958055] Re: sudo apport-kde is in a different design (stripped XDG_CURRENT_DESKTOP)
Added 'Where problems could occur' section. ** Description changed: [Impact] Running ubuntu-bug as normal user has the correct theme (see screenshots attached to bug #1881640), but running "sudo ubuntu-bug" has a different, non-matching theme (see attached screenshot). This applies to all Qt applications. [Test Plan] This problem can be reproduce by running a KDE application on Ubuntu Desktop (GNOME): 1. Launch ubuntu-22.04-desktop-amd64.iso 2. Install apport-kde 3. Run: /usr/share/apport/apport-kde -f 4. Run: sudo /usr/share/apport/apport-kde -f 5. Compare both windows. They have different icons and font size. Same result with KDE: 1. Use kubuntu-22.04-desktop-amd64.iso 2. Run ubuntu-bug -f 3. Run: sudo ubuntu-bug -f + + [Where problems could occur] + Passing through an additional environment variable could lead to an undesired side effect (if an application expect it not be be set when run as root). Since this environment variable changes the code paths, it could reveal Qt bugs related to running as root. [Analysis] Qt needs XDG_CURRENT_DESKTOP to be set to determine the correct theme, but XDG_CURRENT_DESKTOP is not in the list of environment variables to preserve (and not in env_keep in /etc/sudoers). On other other hand, sudo preserves the DISPLAY environment variable: $ sudo env | grep -Ev '^(LC|LS|SUDO|LANG|COLOR|TERM|PATH)' XAUTHORITY=/run/user/1000/gdm/Xauthority DISPLAY=:0 MAIL=/var/mail/root LOGNAME=root USER=root HOME=/root SHELL=/bin/bash [Workaround] Prevent sudo from dropping XDG_CURRENT_DESKTOP by running: sudo XDG_CURRENT_DESKTOP=$XDG_CURRENT_DESKTOP /usr/share/apport/apport-kde -f [Other Info] This changes was accepted upstream: https://github.com/sudo- project/sudo/pull/165 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.27 ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-94-generic i686 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: i386 CurrentDesktop: KDE Date: Sun Jan 16 05:04:24 2022 InstallationDate: Installed on 2022-01-15 (0 days ago) InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200806.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: sudo (Ubuntu Jammy) Status: Incomplete => New -- 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/1958055 Title: sudo apport-kde is in a different design (stripped XDG_CURRENT_DESKTOP) Status in sudo package in Ubuntu: Fix Released Status in sudo source package in Jammy: New Bug description: [Impact] Running ubuntu-bug as normal user has the correct theme (see screenshots attached to bug #1881640), but running "sudo ubuntu-bug" has a different, non-matching theme (see attached screenshot). This applies to all Qt applications. [Test Plan] This problem can be reproduce by running a KDE application on Ubuntu Desktop (GNOME): 1. Launch ubuntu-22.04-desktop-amd64.iso 2. Install apport-kde 3. Run: /usr/share/apport/apport-kde -f 4. Run: sudo /usr/share/apport/apport-kde -f 5. Compare both windows. They have different icons and font size. Same result with KDE: 1. Use kubuntu-22.04-desktop-amd64.iso 2. Run ubuntu-bug -f 3. Run: sudo ubuntu-bug -f [Where problems could occur] Passing through an additional environment variable could lead to an undesired side effect (if an application expect it not be be set when run as root). Since this environment variable changes the code paths, it could reveal Qt bugs related to running as root. [Analysis] Qt needs XDG_CURRENT_DESKTOP to be set to determine the correct theme, but XDG_CURRENT_DESKTOP is not in the list of environment variables to preserve (and not in env_keep in /etc/sudoers). On other other hand, sudo preserves the DISPLAY environment variable: $ sudo env | grep -Ev '^(LC|LS|SUDO|LANG|COLOR|TERM|PATH)' XAUTHORITY=/run/user/1000/gdm/Xauthority DISPLAY=:0 MAIL=/var/mail/root LOGNAME=root USER=root HOME=/root SHELL=/bin/bash [Workaround] Prevent sudo from dropping XDG_CURRENT_DESKTOP by running: sudo XDG_CURRENT_DESKTOP=$XDG_CURRENT_DESKTOP /usr/share/apport/apport-kde -f [Other Info] This changes was accepted upstream: https://github.com/sudo- project/sudo/pull/165 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.27 ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-94-generic i686 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: i386 CurrentDesktop: KDE Date: Sun Jan 16 05:04:24 2022 InstallationDate: Installed on 2022-01-15 (0 days ago) InstallationMedia: Kubuntu 18.04.5 LTS
[Touch-packages] [Bug 1947425] Re: Use of deprecated 'imp' module
** Description changed: + Impact + -- + + The deprecation warning is just a warning, but it clutters the output + and can lead to misattributions in case something does not work as + expected. + Test Case - 1. Execute following command: python3 -Wonce -c "import apport.report" 2. There should be no output. + + Where problems could occur + -- + + Except for changes to the test cases, _check_interpreted is the only + consumer for the changed code. Breakage in this code paths can lead to + wrongly assume that the crashing Python code is an interpreted script or + not. This can lead to reports that have only ExecutablePath set (and not + InterpreterPath). Original Description Code using apport/report.py will see the following warning: $ python3 -Wonce -c "import apport.report" /usr/lib/python3/dist-packages/apport/report.py:13 /usr/lib/python3/dist-packages/apport/report.py:13: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses import fnmatch, glob, traceback, errno, sys, atexit, locale, imp, stat The 'imp' module is slated for removal in Python 3.12. https://github.com/python/cpython/blob/main/Lib/imp.py#L31 -- 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/1947425 Title: Use of deprecated 'imp' module Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Jammy: New Bug description: Impact -- The deprecation warning is just a warning, but it clutters the output and can lead to misattributions in case something does not work as expected. Test Case - 1. Execute following command: python3 -Wonce -c "import apport.report" 2. There should be no output. Where problems could occur -- Except for changes to the test cases, _check_interpreted is the only consumer for the changed code. Breakage in this code paths can lead to wrongly assume that the crashing Python code is an interpreted script or not. This can lead to reports that have only ExecutablePath set (and not InterpreterPath). Original Description Code using apport/report.py will see the following warning: $ python3 -Wonce -c "import apport.report" /usr/lib/python3/dist-packages/apport/report.py:13 /usr/lib/python3/dist-packages/apport/report.py:13: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses import fnmatch, glob, traceback, errno, sys, atexit, locale, imp, stat The 'imp' module is slated for removal in Python 3.12. https://github.com/python/cpython/blob/main/Lib/imp.py#L31 To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1947425/+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 1982487] Re: apport fails with PermissionError for dump mode 2 in containers
** Description changed:
[Impact]
Apport will fail for processes with dump mode 2 inside of containers.
[Test plan]
Run following testcase script inside a LXC container:
```
#!/bin/sh
sudo rm -rf /var/crash/* /var/log/apport.log
sudo -u mail sh -c "ping 127.0.0.1 > /dev/null" &
sleep 0.3
killall -11 ping
sleep 0.3
cat /var/log/apport.log
```
apport.log for the affected version:
```
ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: called for pid 6449,
signal 11, core limit 0, dump mode 2
ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: not creating core for pid
with dump mode of 2
ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: Unhandled exception:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 681, in
add_proc_info
self["ExecutablePath"] = _read_proc_link(
File "/usr/lib/python3/dist-packages/apport/report.py", line 92, in
_read_proc_link
return os.readlink(path, dir_fd=dir_fd)
PermissionError: [Errno 13] Permission denied: 'exe'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/share/apport/apport", line 862, in
info.add_proc_info(proc_pid_fd=proc_pid_fd)
File "/usr/lib/python3/dist-packages/apport/report.py", line 686, in
add_proc_info
raise ValueError("not accessible")
ValueError: not accessible
ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: pid: 6452, uid: 0, gid: 0,
euid: 8, egid: 8
ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: environment:
environ({'LANG': 'C.UTF-8', 'PATH':
'/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin',
'LISTEN_PID': '6452', 'LISTEN_FDS': '1', 'LISTEN_FDNAMES': 'connection',
'INVOCATION_ID': '1352c67b4a21480a9b35db8012dafb42', 'JOURNAL_STREAM':
'8:29587491', 'SYSTEMD_EXEC_PID': '6452'})
```
The apport log should not show a Traceback.
+ [Where problems could occur]
+
+ The apport binary is called by the kernel when a process crashes. Worst
+ case scenarios include breaking the apport binary and no problem report
+ is generated any more (or apport uses too much resources). Users will
+ see problems reports inside the container which cause additional load or
+ disk usage. The fix is accompanied by a test case (run in autopkgtest).
+
[Other Info]
The autopkgtest for armhf are run inside a LXC container and some test
cases like test_crash_setuid_drop trigger this bug.
--
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/1982487
Title:
apport fails with PermissionError for dump mode 2 in containers
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
Triaged
Status in apport source package in Focal:
New
Status in apport source package in Jammy:
New
Bug description:
[Impact]
Apport will fail for processes with dump mode 2 inside of containers.
[Test plan]
Run following testcase script inside a LXC container:
```
#!/bin/sh
sudo rm -rf /var/crash/* /var/log/apport.log
sudo -u mail sh -c "ping 127.0.0.1 > /dev/null" &
sleep 0.3
killall -11 ping
sleep 0.3
cat /var/log/apport.log
```
apport.log for the affected version:
```
ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: called for pid 6449,
signal 11, core limit 0, dump mode 2
ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: not creating core for pid
with dump mode of 2
ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: Unhandled exception:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 681, in
add_proc_info
self["ExecutablePath"] = _read_proc_link(
File "/usr/lib/python3/dist-packages/apport/report.py", line 92, in
_read_proc_link
return os.readlink(path, dir_fd=dir_fd)
PermissionError: [Errno 13] Permission denied: 'exe'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/share/apport/apport", line 862, in
info.add_proc_info(proc_pid_fd=proc_pid_fd)
File "/usr/lib/python3/dist-packages/apport/report.py", line 686, in
add_proc_info
raise ValueError("not accessible")
ValueError: not accessible
ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: pid: 6452, uid: 0, gid: 0,
euid: 8, egid: 8
ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: environment:
environ({'LANG': 'C.UTF-8', 'PATH':
'/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin',
'LISTEN_PID': '6452', 'LISTEN_FDS': '1', 'LISTEN_FDNAMES': 'connection',
'INVOCATION_ID': '1352c67b4a21480a9b35db8012dafb42', 'JOURNAL_STREAM':
'8:29587491', 'SYSTEMD_EXEC_PID': '6452'})
```
The apport log should not show a Traceback.
[Where problems could occur]
The apport binary is called by the kernel when
[Touch-packages] [Bug 1982555] Re: core dump file empty inside container
** Description changed: [Impact] Apport will write an empty core dump file inside of containers. [Test plan] Run following testcase script inside a LXC container: ``` rm -f /var/lib/apport/coredump/* ulimit -c 100 sleep 86400 & killall -3 sleep ``` Apport will write a core dump into /var/lib/apport/coredump, but this core dump is empty: ``` $ stat /var/lib/apport/coredump/core._usr_bin_sleep.* - File: /var/lib/apport/coredump/core._usr_bin_sleep.0.44f483a1-e487-44b3-88d1-805d1026f31d.9059.34839819 - Size: 0 Blocks: 0 IO Block: 4096 regular empty file + File: /var/lib/apport/coredump/core._usr_bin_sleep.0.44f483a1-e487-44b3-88d1-805d1026f31d.9059.34839819 + Size: 0 Blocks: 0 IO Block: 4096 regular empty file Device: fd00h/64768d Inode: 120848663 Links: 1 Access: (0400/-r) Uid: (0/root) Gid: (0/root) Access: 2022-07-22 07:54:48.838682067 + Modify: 2022-07-22 07:54:48.838682067 + Change: 2022-07-22 07:54:48.838682067 + - Birth: 2022-07-22 07:54:48.838682067 + + Birth: 2022-07-22 07:54:48.838682067 + ``` This file should not be empty. + + [Where problems could occur] + + The apport binary is called by the kernel when a process crashes. Worst + case scenarios include breaking the apport binary and no problem report + is generated any more (or apport uses too much resources). Users will + see problems reports inside the container which cause additional load or + disk usage. [Other Info] The autopkgtest for armhf are run inside a LXC container and the test case test_core_dump_packaged_sigquit triggers this bug. ** Description changed: [Impact] Apport will write an empty core dump file inside of containers. [Test plan] Run following testcase script inside a LXC container: ``` rm -f /var/lib/apport/coredump/* ulimit -c 100 sleep 86400 & killall -3 sleep ``` Apport will write a core dump into /var/lib/apport/coredump, but this core dump is empty: ``` $ stat /var/lib/apport/coredump/core._usr_bin_sleep.* File: /var/lib/apport/coredump/core._usr_bin_sleep.0.44f483a1-e487-44b3-88d1-805d1026f31d.9059.34839819 Size: 0 Blocks: 0 IO Block: 4096 regular empty file Device: fd00h/64768d Inode: 120848663 Links: 1 Access: (0400/-r) Uid: (0/root) Gid: (0/root) Access: 2022-07-22 07:54:48.838682067 + Modify: 2022-07-22 07:54:48.838682067 + Change: 2022-07-22 07:54:48.838682067 + Birth: 2022-07-22 07:54:48.838682067 + ``` This file should not be empty. [Where problems could occur] The apport binary is called by the kernel when a process crashes. Worst case scenarios include breaking the apport binary and no problem report is generated any more (or apport uses too much resources). Users will see problems reports inside the container which cause additional load or - disk usage. + disk usage. The fix is accompanied by a test case. [Other Info] The autopkgtest for armhf are run inside a LXC container and the test case test_core_dump_packaged_sigquit triggers this bug. -- 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/1982555 Title: core dump file empty inside container Status in Apport: Fix Released Status in apport package in Ubuntu: Triaged Status in apport source package in Focal: Confirmed Status in apport source package in Jammy: Confirmed Bug description: [Impact] Apport will write an empty core dump file inside of containers. [Test plan] Run following testcase script inside a LXC container: ``` rm -f /var/lib/apport/coredump/* ulimit -c 100 sleep 86400 & killall -3 sleep ``` Apport will write a core dump into /var/lib/apport/coredump, but this core dump is empty: ``` $ stat /var/lib/apport/coredump/core._usr_bin_sleep.* File: /var/lib/apport/coredump/core._usr_bin_sleep.0.44f483a1-e487-44b3-88d1-805d1026f31d.9059.34839819 Size: 0 Blocks: 0 IO Block: 4096 regular empty file Device: fd00h/64768d Inode: 120848663 Links: 1 Access: (0400/-r) Uid: (0/root) Gid: (0/root) Access: 2022-07-22 07:54:48.838682067 + Modify: 2022-07-22 07:54:48.838682067 + Change: 2022-07-22 07:54:48.838682067 + Birth: 2022-07-22 07:54:48.838682067 + ``` This file should not be empty. [Where problems could occur] The apport binary is called by the kernel when a process crashes. Worst case scenarios include breaking the apport binary and no problem report is generated any more (or apport uses too much resources). Users will see problems reports inside the container which cause additional load or disk usage. The fix is
[Touch-packages] [Bug 1977954] Re: apport_python_hook: Crashes if os.getcwd() throws FileNotFoundError
** Description changed: + Impact + -- + + The Apport Python hook should be transparent to the user (which is + normally the case). Bugs and crashes inside the hook lead to an + exception inside the exception which clutters the output and confuse the + user. User/Developer need to understand this Python hook and look into + the encapsulated stack trace only. + Test Case - 1. Create /tmp/getcwd.py with following content: ``` #!/usr/bin/python3 import os import tempfile tempdir = tempfile.mkdtemp() os.chdir(tempdir) os.rmdir(tempdir) os.getcwd() ``` 2. Make it executable and execute it. It should produce following output: ``` Traceback (most recent call last): - File "/tmp/getcwd.py", line 9, in - os.getcwd() + File "/tmp/getcwd.py", line 9, in + os.getcwd() FileNotFoundError: [Errno 2] No such file or directory ``` instead of: ``` $ /tmp/getcwd.py Traceback (most recent call last): File "/tmp/getcwd.py", line 9, in os.getcwd() FileNotFoundError: [Errno 2] No such file or directory Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 76, in apport_excepthook binary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0])) FileNotFoundError: [Errno 2] No such file or directory Original exception was: Traceback (most recent call last): File "/tmp/getcwd.py", line 9, in os.getcwd() FileNotFoundError: [Errno 2] No such file or directory ``` Another related issue: bug #1979637 Regression Potential There might be a regression that causes capturing Python exception fail. Then reporting them as bugs to Launchpad or the error tracker would not be possible. -- 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/1977954 Title: apport_python_hook: Crashes if os.getcwd() throws FileNotFoundError Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Jammy: New Bug description: Impact -- The Apport Python hook should be transparent to the user (which is normally the case). Bugs and crashes inside the hook lead to an exception inside the exception which clutters the output and confuse the user. User/Developer need to understand this Python hook and look into the encapsulated stack trace only. Test Case - 1. Create /tmp/getcwd.py with following content: ``` #!/usr/bin/python3 import os import tempfile tempdir = tempfile.mkdtemp() os.chdir(tempdir) os.rmdir(tempdir) os.getcwd() ``` 2. Make it executable and execute it. It should produce following output: ``` Traceback (most recent call last): File "/tmp/getcwd.py", line 9, in os.getcwd() FileNotFoundError: [Errno 2] No such file or directory ``` instead of: ``` $ /tmp/getcwd.py Traceback (most recent call last): File "/tmp/getcwd.py", line 9, in os.getcwd() FileNotFoundError: [Errno 2] No such file or directory Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 76, in apport_excepthook binary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0])) FileNotFoundError: [Errno 2] No such file or directory Original exception was: Traceback (most recent call last): File "/tmp/getcwd.py", line 9, in os.getcwd() FileNotFoundError: [Errno 2] No such file or directory ``` Another related issue: bug #1979637 Regression Potential There might be a regression that causes capturing Python exception fail. Then reporting them as bugs to Launchpad or the error tracker would not be possible. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1977954/+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 1979637] Re: apport_python_hook: FileNotFoundError if cwd was deleted
** Description changed: + Impact + -- + + The Apport Python hook should be transparent to the user (which is + normally the case). Bugs and crashes inside the hook lead to an + exception inside the exception which clutters the output and confuse the + user. User/Developer need to understand this Python hook and look into + the encapsulated stack trace only. + Test Case - Run following shell script: ```sh echo "raise ValueError()" > /tmp/failure.py mkdir /tmp/foo cd /tmp/foo/ rmdir /tmp/foo/ python3 ../failure.py ``` It should only print following stacktrace: ``` Traceback (most recent call last): - File "../failure.py", line 1, in - raise ValueError() + File "../failure.py", line 1, in + raise ValueError() ValueError ``` Regression Potential There might be a regression that causes capturing Python exception fail. Then reporting them as bugs to Launchpad or the error tracker would not be possible. Original Description The script should only show a ValueError, but apport_python_hook.py crashes: ``` Traceback (most recent call last): File "../failure.py", line 1, in raise ValueError() ValueError Error in sys.excepthook: Traceback (most recent call last): File "", line 1372, in _path_importer_cache KeyError: '..' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 55, in apport_excepthook import apt_pkg File "", line 1027, in _find_and_load File "", line 1002, in _find_and_load_unlocked File "", line 945, in _find_spec File "", line 1439, in find_spec File "", line 1408, in _get_spec File "", line 1374, in _path_importer_cache File "", line 1350, in _path_hooks File "", line 1632, in path_hook_for_FileFinder File "", line 1505, in __init__ FileNotFoundError: [Errno 2] No such file or directory Original exception was: Traceback (most recent call last): File "../failure.py", line 1, in raise ValueError() ValueError ``` -- 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/1979637 Title: apport_python_hook: FileNotFoundError if cwd was deleted Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Jammy: Confirmed Bug description: Impact -- The Apport Python hook should be transparent to the user (which is normally the case). Bugs and crashes inside the hook lead to an exception inside the exception which clutters the output and confuse the user. User/Developer need to understand this Python hook and look into the encapsulated stack trace only. Test Case - Run following shell script: ```sh echo "raise ValueError()" > /tmp/failure.py mkdir /tmp/foo cd /tmp/foo/ rmdir /tmp/foo/ python3 ../failure.py ``` It should only print following stacktrace: ``` Traceback (most recent call last): File "../failure.py", line 1, in raise ValueError() ValueError ``` Regression Potential There might be a regression that causes capturing Python exception fail. Then reporting them as bugs to Launchpad or the error tracker would not be possible. Original Description The script should only show a ValueError, but apport_python_hook.py crashes: ``` Traceback (most recent call last): File "../failure.py", line 1, in raise ValueError() ValueError Error in sys.excepthook: Traceback (most recent call last): File "", line 1372, in _path_importer_cache KeyError: '..' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 55, in apport_excepthook import apt_pkg File "", line 1027, in _find_and_load File "", line 1002, in _find_and_load_unlocked File "", line 945, in _find_spec File "", line 1439, in find_spec File "", line 1408, in _get_spec File "", line 1374, in _path_importer_cache File "", line 1350, in _path_hooks File "", line 1632, in path_hook_for_FileFinder File "", line 1505, in __init__ FileNotFoundError: [Errno 2] No such file or directory Original exception was: Traceback (most recent call last): File "../failure.py", line 1, in raise ValueError() ValueError ``` To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1979637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More
[Touch-packages] [Bug 1978301] Re: Broken contact URL in German translation
** Description changed: + Impact + -- + + All German users (and all translations that use "%s." in their + translation template) will get a broken URL link for bug reports against + snaps (e.g. Firefox). + Test Case - 1. Execute following command: LANGUAGE=de ubuntu-bug firefox 2. Click on the URL 3. A browser window should open and not display a 404 page Regression Potential Since there was no test case for converting text to HTML before this fix, there might be some URLs that will become broken by this fix. Original Description "LANGUAGE=de ubuntu-bug firefox" end up in a dialog saying: firefox wird durch einen von mozilla veröffentlichten Snap bereitgestellt. Für Hilfe gehen Sie über https://support.mozilla.org/kb/file-bug-report-or-feature-request- mozilla. The dot at the end is included in the URL link. The dot makes the URL link broken. The regular expression in gtk/apport-gtk for http URLs should become smarter. -- 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/1978301 Title: Broken contact URL in German translation Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Jammy: New Bug description: Impact -- All German users (and all translations that use "%s." in their translation template) will get a broken URL link for bug reports against snaps (e.g. Firefox). Test Case - 1. Execute following command: LANGUAGE=de ubuntu-bug firefox 2. Click on the URL 3. A browser window should open and not display a 404 page Regression Potential Since there was no test case for converting text to HTML before this fix, there might be some URLs that will become broken by this fix. Original Description "LANGUAGE=de ubuntu-bug firefox" end up in a dialog saying: firefox wird durch einen von mozilla veröffentlichten Snap bereitgestellt. Für Hilfe gehen Sie über https://support.mozilla.org/kb/file-bug-report-or-feature-request- mozilla. The dot at the end is included in the URL link. The dot makes the URL link broken. The regular expression in gtk/apport-gtk for http URLs should become smarter. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1978301/+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 1979211] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@531:parse_arguments:print_usage:_print_message
** Description changed:
+ Impact
+ --
+
+ As it can be seen in
+ https://errors.ubuntu.com/problem/e714f8181c0785693f3a66969c594a3b19bcab2b
+ there are thousands of crashes of this type (and multiple duplicate bug
+ reports for it). Instead of apport logging a failure in
+ /var/log/apport.log, it crashes. Fixing this bug also fixes the issue
+ with logging failures in the socket path (for handling crashes in
+ containers).
+
Test Case
-
There should be no instances of
https://errors.ubuntu.com/problem/e714f8181c0785693f3a66969c594a3b19bcab2b
for the fixed version.
+
+ Where problems could occur
+ --
+
+ The apport binary is called by the kernel when a process crashes. Worst
+ case scenarios include breaking the apport binary and no problem report
+ is generated any more (or apport uses too much resources). Since all the
+ desired logs are now logged, it could increase the amount of logs that
+ are written (apport has some flood detection in case a process dies
+ constantly).
Original Description
The Ubuntu Error Tracker has been receiving reports about a problem regarding
apport. This problem was most recently seen with package version
2.20.11-0ubuntu82.1, the problem page at
https://errors.ubuntu.com/problem/e714f8181c0785693f3a66969c594a3b19bcab2b
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
Traceback (most recent call last):
File "/usr/share/apport/apport", line 531, in
options = parse_arguments()
File "/usr/share/apport/apport", line 463, in parse_arguments
parser.print_usage()
File "/usr/lib/python3.10/argparse.py", line 2562, in print_usage
self._print_message(self.format_usage(), file)
File "/usr/lib/python3.10/argparse.py", line 2573, in _print_message
file.write(message)
AttributeError: 'NoneType' object has no attribute 'write'
This bug can be reproduced by configuring the previously supported
parameters to Apport and then let a process crash (e.g. call divide-by-
zero):
```
echo "|/usr/share/apport/apport %p %s %c %d %P %E" | sudo tee
/proc/sys/kernel/core_pattern
```
So this bug is a regression of commit c320e910a516 ("Switch to using
non-positional arguments") which is a fix for CVE-2022-28658 and
CVE-2021-3899.
--
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/1979211
Title:
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@531:parse_arguments:print_usage:_print_message
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Focal:
Fix Committed
Status in apport source package in Impish:
Won't Fix
Status in apport source package in Jammy:
Fix Committed
Bug description:
Impact
--
As it can be seen in
https://errors.ubuntu.com/problem/e714f8181c0785693f3a66969c594a3b19bcab2b
there are thousands of crashes of this type (and multiple duplicate
bug reports for it). Instead of apport logging a failure in
/var/log/apport.log, it crashes. Fixing this bug also fixes the issue
with logging failures in the socket path (for handling crashes in
containers).
Test Case
-
There should be no instances of
https://errors.ubuntu.com/problem/e714f8181c0785693f3a66969c594a3b19bcab2b
for the fixed version.
Where problems could occur
--
The apport binary is called by the kernel when a process crashes.
Worst case scenarios include breaking the apport binary and no problem
report is generated any more (or apport uses too much resources).
Since all the desired logs are now logged, it could increase the
amount of logs that are written (apport has some flood detection in
case a process dies constantly).
Original Description
The Ubuntu Error Tracker has been receiving reports about a problem regarding
apport. This problem was most recently seen with package version
2.20.11-0ubuntu82.1, the problem page at
https://errors.ubuntu.com/problem/e714f8181c0785693f3a66969c594a3b19bcab2b
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
Traceback (most recent call last):
File "/usr/share/apport/apport", line 531, in
options = parse_arguments()
File "/usr/share/apport/apport", line 463, in parse_arguments
parser.print_usage()
File "/usr/lib/python3.10/argparse.py", line 2562, in
[Touch-packages] [Bug 1097467] Re: bash does not fulfill --rcfile option properly
Hmm, on the other hand --norc does indeed suppress both user and system- wide bashrc files. So, the man-page is correct in that instance, and apparently the intent of bash is to allow the system-wide bashrc file to be suppressed in certain circumstances. Which sways me back toward the notion that the bug is in bash's --rcfile behaviour ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1097467 Title: bash does not fulfill --rcfile option properly Status in bash package in Ubuntu: Confirmed Bug description: I am starting a bash shell using $ bash --noprofile --rcfile my-custom-bash-rc-file Due to the --rcflag, the newly started bash should *not* execute commands from /etc/bash.bashrc. That is at least how I interpret `man bash`: --rcfile file Execute commands from file instead of the system wide initialization file /etc/bash.bashrc and the standard personal initial‐ ization file ~/.bashrc if the shell is interactive (see INVOCATION below). However, it seems that the commands in /etc/bash.bashrc are in fact executed. To see/reproduce/diagnose this, on Ubuntu I believe one can just invoke bash like this (as the regular user): $ touch testrc $ env -i bash --noprofile --rcfile testrc The expected result would be that nothing special is printed on the terminal. However, there is an error message, which is printed from /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the invoked shell, which in turn triggers the error. The error message is: > To run a command as administrator (user "root"), use "sudo ". > See "man sudo_root" for details. Another way to see this -- without the "env -i" -- is to add a command to /etc/bash.bashrc, such as echo HELLO THERE To trigger the bug(?), one can then just do $ touch testrc $ bash --noprofile --rcfile testrc The expected result would be that nothing special is shown in the terminal. However, it turns out that the string HELLO THERE is printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+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 1964828] Re: /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json'
** Description changed: + [Impact] + + If the user reports a bug and rejects to enter the root password for + collecting information (like the CasperMD5json), the Ubuntu add_info + hook will fail with a stack trace. The remaining code for collecting + more information is not executed. So the resulting bug reports will be + less helpful. The check_for_disk_error call is not reached and therefore + skipped. + [Test Plan] 1. Launch the Ubuntu installer (i.e. ubuntu-22.04-desktop-amd64.iso) 2. Select "Try Ubuntu" 3. Open a terminal 4. Run: ubuntu-bug -f 5. Select "installer" and click on OK 6. Click on "abort" when ask for the password 7. The terminal should not show a stacktrace + + [Where problems could occur] + + The changed code is the Ubuntu add_info hook. So this hook could fail + due to a regression or reveal bugs in the later code path. The later + code path could cause more more load on the users machine (but only when + the user wants to report the issue). Apport will catch failing add_info + hooks and store the failure in the report. [Orinial report] ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 81, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1016, in attach_casper_md5check check = json.loads(report['CasperMD5json']) File "/usr/lib/python3.10/collections/__init__.py", line 1102, in __getitem__ raise KeyError(key) KeyError: 'CasperMD5json' kubuntu@kubuntu:~$ Gtk-Message: 21:22:43.923: Failed to load module "colorreload-gtk-module" ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperVersion: 1.467 CurrentDesktop: KDE Date: Mon Mar 14 21:22:23 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220314) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1964828 Title: /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json' Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Committed Status in apport source package in Jammy: Fix Committed Bug description: [Impact] If the user reports a bug and rejects to enter the root password for collecting information (like the CasperMD5json), the Ubuntu add_info hook will fail with a stack trace. The remaining code for collecting more information is not executed. So the resulting bug reports will be less helpful. The check_for_disk_error call is not reached and therefore skipped. [Test Plan] 1. Launch the Ubuntu installer (i.e. ubuntu-22.04-desktop-amd64.iso) 2. Select "Try Ubuntu" 3. Open a terminal 4. Run: ubuntu-bug -f 5. Select "installer" and click on OK 6. Click on "abort" when ask for the password 7. The terminal should not show a stacktrace [Where problems could occur] The changed code is the Ubuntu add_info hook. So this hook could fail due to a regression or reveal bugs in the later code path. The later code path could cause more more load on the users machine (but only when the user wants to report the issue). Apport will catch failing add_info hooks and store the failure in the report. [Orinial report] ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 81, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1016, in attach_casper_md5check check = json.loads(report['CasperMD5json']) File "/usr/lib/python3.10/collections/__init__.py", line 1102, in __getitem__ raise KeyError(key) KeyError: 'CasperMD5json' kubuntu@kubuntu:~$ Gtk-Message: 21:22:43.923: Failed to load module "colorreload-gtk-module" ATTENTION: default value of option mesa_glthread overridden by
[Touch-packages] [Bug 1987340] Re: Please merge lvm2 2.03.16-1 from Debian unstable.
I'm afraid the removal of colons in LP: entries of the changelog is a deliberate tactic by maintainers to prevent launchpad from inadvertently marking things closed when it shouldn't (theoretically, this shouldn't happen if things are targetted correctly to the relevant releases, but this isn't always the case). On the subject of basing the branch on salsa, I'm not sure how that could work given I'd need to be working with a repo containing two remotes, one the git-ubuntu import (needed to do the initial split because the delta isn't necessarily a monolithic commit; it can consist of several ubuntu versions), and the second from salsa. But the latter's main/master branch cannot match the git-ubuntu import's commit as the commits in the former are generated from the packaging archive. It would be possible to cherry-pick the rebased delta onto a chosen salsa commit, but that wouldn't affect the output of range-diff, so I'm not seeing how it would improve the ability to review the merge? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1987340 Title: Please merge lvm2 2.03.16-1 from Debian unstable. Status in lvm2 package in Ubuntu: Confirmed Bug description: Please merge lvm2 2.03.16-1 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1987340/+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 1982108] Re: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS
same here, with kodi!!. the problem is fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1982108 Title: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: Confirmed Status in python3.10 package in Ubuntu: Confirmed Status in python3-defaults source package in Jammy: Fix Committed Status in python3-stdlib-extensions source package in Jammy: Fix Committed Status in python3.10 source package in Jammy: Fix Committed Bug description: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS we are doing a test rebuild of 22.04 main to check for regressions. test rebuilds at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-jammy.html https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-gcc-jammy.html the first one is the reference test rebuild, the second one the rebuild using updated binutils, GCC and python packages. Analysis: regressions on riscv64 (caused by enabling the tests) are: abseil adsys colord dovecot glib-networking glibc gnome-bluetooth3 gnome-control-center google-perftools json-glib libfprint libgdata memcached mir openvswitch ovn pmdk power-profiles-daemon strace swtpm vim devscripts is not a regression, introduced by a custom dpkg- buildpackage wrapper. binutils and python3-stdlib-extensions are superseded which are part of the planned updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1982108/+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 1891798] Re: Backport fix from sudo 1.8.22 to fix "stair-stepped output" bug
The test case is already in the "Example output" file. https://launchpadlibrarian.net/493705832/sudo-broken.txt -- 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/1891798 Title: Backport fix from sudo 1.8.22 to fix "stair-stepped output" bug Status in sudo package in Ubuntu: New Status in sudo source package in Bionic: New Bug description: sudo 1.8.20 introduced a bug in commit 44dc15d02dc0b34bf03bc971ba08d3a761c3a031 that is fixed by sudo 1.8.22 in commit 3b88cdfcd8d1a39eabbb5b7d0c8fe8f035d7a264 When the "use_pty" option is enabled, "stair-stepped output" occurs if sudo is piped to another command. Example output attached in a text file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sudo 1.8.21p2-3ubuntu1.2 Uname: Linux 5.4.50+ x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 16 12:29:23 2020 InstallationDate: Installed on 2014-05-10 (2290 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: sudo UpgradeStatus: Upgraded to bionic on 2018-11-24 (630 days ago) modified.conffile..etc.pam.d.sudo: [inaccessible: [Errno 13] Permission denied: '/etc/pam.d/sudo'] modified.conffile..etc.sudoers: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers'] modified.conffile..etc.sudoers.d.README: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/README'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1891798/+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 1097467] Re: bash does not fulfill --rcfile option properly
This has apparently been an issue for some considerable time. I've just now run into it while delving into a failure in pexpect's test-suite (during work on LP: #1987420), which apparently assumes that using --rcfile will suppress both the user *and* the system's bashrc (as the man-page documents). However, I'm not entirely convinced this is a bug in bash, so much as its man-page. Reading the original code (shell.c in bash) its intent is fairly clear: execute the system-wide bashrc in all interactive shells, but permit the user's bashrc to be overridden by --rcfile. It's worth noting that the original (upstream, not Debian) man-page makes no mention of the system-wide bashrc because it's an option that's not activated by default. The Debian packaging enables the system-wide bashrc (SYS_BASHRC in d/p/deb-bash-config.diff) and then patches the man-page to mention it (d/p/man-bashrc.diff). In other words, I suspect this is a documentation bug rather than a behavioural bug (i.e. the man- page is wrong, not the behaviour). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1097467 Title: bash does not fulfill --rcfile option properly Status in bash package in Ubuntu: Confirmed Bug description: I am starting a bash shell using $ bash --noprofile --rcfile my-custom-bash-rc-file Due to the --rcflag, the newly started bash should *not* execute commands from /etc/bash.bashrc. That is at least how I interpret `man bash`: --rcfile file Execute commands from file instead of the system wide initialization file /etc/bash.bashrc and the standard personal initial‐ ization file ~/.bashrc if the shell is interactive (see INVOCATION below). However, it seems that the commands in /etc/bash.bashrc are in fact executed. To see/reproduce/diagnose this, on Ubuntu I believe one can just invoke bash like this (as the regular user): $ touch testrc $ env -i bash --noprofile --rcfile testrc The expected result would be that nothing special is printed on the terminal. However, there is an error message, which is printed from /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the invoked shell, which in turn triggers the error. The error message is: > To run a command as administrator (user "root"), use "sudo ". > See "man sudo_root" for details. Another way to see this -- without the "env -i" -- is to add a command to /etc/bash.bashrc, such as echo HELLO THERE To trigger the bug(?), one can then just do $ touch testrc $ bash --noprofile --rcfile testrc The expected result would be that nothing special is shown in the terminal. However, it turns out that the string HELLO THERE is printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+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 1097467] Re: bash does not fulfill --rcfile option properly
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bash (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1097467 Title: bash does not fulfill --rcfile option properly Status in bash package in Ubuntu: Confirmed Bug description: I am starting a bash shell using $ bash --noprofile --rcfile my-custom-bash-rc-file Due to the --rcflag, the newly started bash should *not* execute commands from /etc/bash.bashrc. That is at least how I interpret `man bash`: --rcfile file Execute commands from file instead of the system wide initialization file /etc/bash.bashrc and the standard personal initial‐ ization file ~/.bashrc if the shell is interactive (see INVOCATION below). However, it seems that the commands in /etc/bash.bashrc are in fact executed. To see/reproduce/diagnose this, on Ubuntu I believe one can just invoke bash like this (as the regular user): $ touch testrc $ env -i bash --noprofile --rcfile testrc The expected result would be that nothing special is printed on the terminal. However, there is an error message, which is printed from /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the invoked shell, which in turn triggers the error. The error message is: > To run a command as administrator (user "root"), use "sudo ". > See "man sudo_root" for details. Another way to see this -- without the "env -i" -- is to add a command to /etc/bash.bashrc, such as echo HELLO THERE To trigger the bug(?), one can then just do $ touch testrc $ bash --noprofile --rcfile testrc The expected result would be that nothing special is shown in the terminal. However, it turns out that the string HELLO THERE is printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+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 1097467] Re: bash does not fulfill --rcfile option properly
** Summary changed: - bash does not fulfill --bashrc option properly + bash does not fulfill --rcfile option properly ** Description changed: I am starting a bash shell using - $ bash --noprofile --bashrc my-custom-bash-rc-file + $ bash --noprofile --rcfile my-custom-bash-rc-file Due to the --rcflag, the newly started bash should *not* execute commands from /etc/bash.bashrc. That is at least how I interpret `man bash`: - --rcfile file - Execute commands from file instead of the system wide initialization file /etc/bash.bashrc and the standard personal initial‐ - ization file ~/.bashrc if the shell is interactive (see INVOCATION below). + --rcfile file + Execute commands from file instead of the system wide initialization file /etc/bash.bashrc and the standard personal initial‐ + ization file ~/.bashrc if the shell is interactive (see INVOCATION below). However, it seems that the commands in /etc/bash.bashrc are in fact executed. To see/reproduce/diagnose this, on Ubuntu I believe one can just invoke bash like this (as the regular user): $ touch testrc - $ env -i bash --noprofile --rcfile testrc + $ env -i bash --noprofile --rcfile testrc The expected result would be that nothing special is printed on the terminal. However, there is an error message, which is printed from /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the invoked shell, which in turn triggers the error. The error message is: > To run a command as administrator (user "root"), use "sudo ". - > See "man sudo_root" for details. + > See "man sudo_root" for details. Another way to see this -- without the "env -i" -- is to add a command to /etc/bash.bashrc, such as echo HELLO THERE To trigger the bug(?), one can then just do $ touch testrc - $ bash --noprofile --bashrc testrc + $ bash --noprofile --rcfile testrc The expected result would be that nothing special is shown in the terminal. However, it turns out that the string HELLO THERE is printed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1097467 Title: bash does not fulfill --rcfile option properly Status in bash package in Ubuntu: Confirmed Bug description: I am starting a bash shell using $ bash --noprofile --rcfile my-custom-bash-rc-file Due to the --rcflag, the newly started bash should *not* execute commands from /etc/bash.bashrc. That is at least how I interpret `man bash`: --rcfile file Execute commands from file instead of the system wide initialization file /etc/bash.bashrc and the standard personal initial‐ ization file ~/.bashrc if the shell is interactive (see INVOCATION below). However, it seems that the commands in /etc/bash.bashrc are in fact executed. To see/reproduce/diagnose this, on Ubuntu I believe one can just invoke bash like this (as the regular user): $ touch testrc $ env -i bash --noprofile --rcfile testrc The expected result would be that nothing special is printed on the terminal. However, there is an error message, which is printed from /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the invoked shell, which in turn triggers the error. The error message is: > To run a command as administrator (user "root"), use "sudo ". > See "man sudo_root" for details. Another way to see this -- without the "env -i" -- is to add a command to /etc/bash.bashrc, such as echo HELLO THERE To trigger the bug(?), one can then just do $ touch testrc $ bash --noprofile --rcfile testrc The expected result would be that nothing special is shown in the terminal. However, it turns out that the string HELLO THERE is printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+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 1987340] Re: Please merge lvm2 2.03.16-1 from Debian unstable.
I removed the trailing spaces from the old debian/changelog entries from Ubuntu and uploaded lvm2 2.03.16-1ubuntu1. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1987340 Title: Please merge lvm2 2.03.16-1 from Debian unstable. Status in lvm2 package in Ubuntu: Confirmed Bug description: Please merge lvm2 2.03.16-1 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1987340/+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 1987340] Re: Please merge lvm2 2.03.16-1 from Debian unstable.
I will sponsor it. Except for some small formatting (patch attached) for the debian/changelog the merge proposal looks good. Having the git repository helped reviewing. Suggestion: Base your branch on https://salsa.debian.org/lvm-team/lvm2 next time. ** Patch added: "0001-Fix-changelog.patch" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1987340/+attachment/5611050/+files/0001-Fix-changelog.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1987340 Title: Please merge lvm2 2.03.16-1 from Debian unstable. Status in lvm2 package in Ubuntu: Confirmed Bug description: Please merge lvm2 2.03.16-1 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1987340/+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 1982218] Re: wait-online does not correctly identify managed links
Hi Mike, Do you have a test case that can demonstrate/reproduce this issue? ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1982218 Title: wait-online does not correctly identify managed links Status in systemd package in Ubuntu: Incomplete Bug description: Ubuntu's packaging of systemd-networkd-wait-online includes a patch (UBUNTU-wait-online-exit-if-no-links-are-managed) intended to exit if none of the present links are managed by systemd-networkd. However, the patch fails to identify links in the "configuring" state, which implies they are managed, but not yet fully online. This undermines the purpose of systemd-networkd-wait-online with the --any option, since at the time the systemd-networkd-wait-online service is started, managed links are _likely_ in a configuring, but-not-yet-configured state. Please see the attached patch. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/+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 1987329] Re: unknown path /var/tmp/mkinitramfs_????? .....
Next update pointing to nowhere again, with a new path: update-initramfs: Generating /boot/initrd.img-5.19.0-15-generic depmod: WARNING: could not open modules.builtin.modinfo at /var/tmp/mkinitramfs_tWthLe/lib/modules/5.19.0-15-generic: No such file or directory ** Summary changed: - unknown path /var/tmp/mkinitramfs_? . + unknown path /var/tmp/mkinitramfs_? . could not open modules.builtin.modinfo -- 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/1987329 Title: unknown path /var/tmp/mkinitramfs_? . could not open modules.builtin.modinfo Status in initramfs-tools package in Ubuntu: New Bug description: Today i get that warning due to pointing to ghost path update-initramfs: Generating /boot/initrd.img-5.19.0-15-generic depmod: WARNING: could not open modules.builtin.modinfo at /var/tmp/mkinitramfs_fv2APy/lib/modules/5.19.0-15-generic: No such file or directory with each new update the path (wrong) change maybe the kernel 15 installation could be faulty In such a case then please change the package reported against --- ProblemType: Bug ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.10 Package: initramfs-tools 0.140ubuntu16 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: kinetic package-from-proposed Uname: Linux 5.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1987329/+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 1983784] Re: LUKS-encrypted partition is not automatically unlocked during the boot process with a fido2 key
** Package changed: systemd (Ubuntu) => libfido2 (Ubuntu) -- 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/1983784 Title: LUKS-encrypted partition is not automatically unlocked during the boot process with a fido2 key Status in libfido2 package in Ubuntu: New Bug description: ubuntu 22.04 systemd 249.11-0ubuntu3.4 The partition is encrypted with luks2 and a fido2 key has been enrolled.with: systemd-cryptenroll --fido2-device=auto /dev/ /etc/crypttab has been setup with: LABEL= none fido2-device=auto /etc/fstab has been setup with: /dev/mapper/ /media/ ext4 defaults,nofail 0 0 After the boot is complete, the partition has not been unlocked despite the fido2 key being present during the whole boot process. Also, a manual unlock works with: /lib/systemd/systemd-cryptsetup attach /dev/ none fido2-device=auto Set cipher aes, mode xts-plain64, key size 256 bits for device /dev/ Automatically discovered security FIDO2 token unlocks volume. Asking FIDO2 token for authentication. Please confirm presence on security token to unlock. How to automatically unlock the partition at boot? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfido2/+bug/1983784/+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 1959211] Re: Please merge dbus 1.14.0-2 from Debian unstable.
Attaching patch against Debian unstable. For ease of review, relevant commits and tags have been pushed to the following repository: https://code.launchpad.net/~waveform/ubuntu/+source/dbus/+git/dbus Specifically: * logical/1.12.20-2ubuntu4 represents our split-out delta on top of old/debian (1.12.20-2) * logical/1.14.0-2ubuntu1 represents our rebased delta on top of new/debian (1.14.0-2) * merge/1.14.0-2ubuntu1 just adds changelog and maintainer changes on top of logical/1.14.0-2ubuntu1 Hence, the following command may produce output useful to the purposes of review: git range-diff old/debian..logical/1.12.20-2ubuntu4 new/debian..logical/1.14.0-2ubuntu1 ** Description changed: - NOTE: Resetting to new; do NOT merge (the current state of the merge - would also produce LP: #1962036 -- will update this merge once that is - fixed) - - - = Original Description = - - Please merge dbus 1.12.20-3 from Debian unstable. + Please merge dbus 1.14.0-2 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. ** Patch added: "2-1959211.debdiff" https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1959211/+attachment/5611005/+files/2-1959211.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1959211 Title: Please merge dbus 1.14.0-2 from Debian unstable. Status in dbus package in Ubuntu: Confirmed Bug description: Please merge dbus 1.14.0-2 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1959211/+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 1959211] Re: Please merge dbus 1.14.0-2 from Debian unstable.
Test builds will be available in ppa:waveform/dbus at the following URL: https://launchpad.net/~waveform/+archive/ubuntu/dbus ** Tags added: fr-2624 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1959211 Title: Please merge dbus 1.14.0-2 from Debian unstable. Status in dbus package in Ubuntu: Confirmed Bug description: Please merge dbus 1.14.0-2 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1959211/+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 1982841] Re: [22.10 FEAT] [SEC2210] p11-kit: add IBM specific mechanisms and attributes (crypto)
** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to p11-kit in Ubuntu. https://bugs.launchpad.net/bugs/1982841 Title: [22.10 FEAT] [SEC2210] p11-kit: add IBM specific mechanisms and attributes (crypto) Status in Ubuntu on IBM z Systems: Fix Committed Status in p11-kit package in Ubuntu: Fix Committed Bug description: Add support for IBM specific attributes and mechanis to the PKCS11 client-server implementation of p11-kit to p11-kit. This enables customers to access IBM Z HSMs remotely via a PKCS #11 API. Upstream Target: p11-kit 0.25.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982841/+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 1982841] Re: [22.10 FEAT] [SEC2210] p11-kit: add IBM specific mechanisms and attributes (crypto)
Uploaded, thanks :) ** Changed in: p11-kit (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to p11-kit in Ubuntu. https://bugs.launchpad.net/bugs/1982841 Title: [22.10 FEAT] [SEC2210] p11-kit: add IBM specific mechanisms and attributes (crypto) Status in Ubuntu on IBM z Systems: In Progress Status in p11-kit package in Ubuntu: Fix Committed Bug description: Add support for IBM specific attributes and mechanis to the PKCS11 client-server implementation of p11-kit to p11-kit. This enables customers to access IBM Z HSMs remotely via a PKCS #11 API. Upstream Target: p11-kit 0.25.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982841/+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 1987304] Re: gtk3 fails to build from source in kinetic
According to https://launchpadlibrarian.net/619433186/gtk+3.0_3.24.34-1ubuntu1_3.24.34-3ubuntu1.diff.gz the patch named `reftest-known-fail.patch` was dropped from `debian/patches/series`. This causes the known failures to not be recognised as such and therefore are now fatal again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987304 Title: gtk3 fails to build from source in kinetic Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: gtk3 has build test failures in kinetic but not in Debian Unstable. (It built on riscv64 because we skip the build tests there). My initial impression is that this is a reftest issue. The reftests are frustrating because dependency changes can lead to images that vary by as little as one pixel and fail the test. And upstream doesn't provide a precise list of dependency versions they are using either. https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.34-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1987304/+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 1968135] Re: BTRFS root subvolume @ mounted always as readonly (... ro rootflags=subvol=@ ...) on Jammy beta
Seems to be fixed since Ubuntu Jammy 22.04.1 has been released, "rw" kernel parameter as a workaround of the read-only RootFS isn't necessary anymore. ** Changed in: systemd (Ubuntu) Status: New => 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/1968135 Title: BTRFS root subvolume @ mounted always as readonly (... ro rootflags=subvol=@ ...) on Jammy beta Status in systemd package in Ubuntu: Fix Released Bug description: = Description = On Ubuntu Jammy Jellyfish (beta 220330) where root (/) is installed on single BTRFS formated partition (no LVM, no separate /boot), then root subvolume (subvol=@) is always mounted as read only. There is a kernel flag (ro) appended to GRUB configuration file /boot/grub/grub.cfg created by script /usr/sbin/update-grub during every kernel update. Only home subvolume (@home) remains mounted as rw according to fstab which is correct. Read-only mounted root (/) leads to many issues. Image: Jammy Beta (220330) = Steps to Reproduce = 1. Install Jammy Beta (220330) on EFI PC x86_64 GPT partitioning and select FS root (/) to one single BTRFS partition (where subvolumes @ and @home are created). There are only 3 partitions EFI system partition (/dev/sda1), one swap (sda2), and one BTRFS formated (/dev/sda3) for FS root (/). 2. Launch the kernel via the default grub entry (or look for kernel boot parameters pressing ) - root subvolume (@) is mounted as readonly. = Expected Results = root / should be mounted as rw (mount -v | grep @), there should be no (ro) flag in /proc/cmdline for FS root. It is possible to temporarily avoid this behaviour in /etc/defaul/grub: GRUB_CMDLINE_LINUX_DEFAULT="rw quiet splash" Then there still remains "ro" kernel parameter which is followed by "rw quiet splash" at the end. = Actual Results = in grub.cfg: linux /@/boot/vmlinuz-5.15.0-23-generic root=UUID=--... rootflags=subvol=@ ro quiet splash $vt_handoff in /proc/cmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic root=UUID=981dd6de-02fc-41a9-9e2a-09dbbc776b2b ro rootflags=subvol=@ quiet splash vt.handoff=7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1968135/+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 1959211] Re: Please merge dbus 1.14.0-2 from Debian unstable.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dbus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1959211 Title: Please merge dbus 1.14.0-2 from Debian unstable. Status in dbus package in Ubuntu: Confirmed Bug description: NOTE: Resetting to new; do NOT merge (the current state of the merge would also produce LP: #1962036 -- will update this merge once that is fixed) = Original Description = Please merge dbus 1.12.20-3 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1959211/+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 1987333] Re: Update dbus to 1.14.0 for kinetic
*** This bug is a duplicate of bug 1959211 *** https://bugs.launchpad.net/bugs/1959211 ** Changed in: dbus (Ubuntu) Assignee: Nathan Teodosio (nteodosio) => (unassigned) ** Changed in: dbus (Ubuntu) Status: Triaged => Invalid ** This bug has been marked a duplicate of bug 1959211 Please merge dbus 1.14.0-2 from Debian unstable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1987333 Title: Update dbus to 1.14.0 for kinetic Status in dbus package in Ubuntu: Invalid Bug description: . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1987333/+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 1959211] Re: Please merge dbus 1.14.0-2 from Debian unstable.
** Summary changed: - Please merge dbus 1.12.20-3 from Debian unstable + Please merge dbus 1.14.0-2 from Debian unstable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1959211 Title: Please merge dbus 1.14.0-2 from Debian unstable. Status in dbus package in Ubuntu: New Bug description: NOTE: Resetting to new; do NOT merge (the current state of the merge would also produce LP: #1962036 -- will update this merge once that is fixed) = Original Description = Please merge dbus 1.12.20-3 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1959211/+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
** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- 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 1987304] Re: gtk3 fails to build from source in kinetic
** Changed in: gtk+3.0 (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987304 Title: gtk3 fails to build from source in kinetic Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: gtk3 has build test failures in kinetic but not in Debian Unstable. (It built on riscv64 because we skip the build tests there). My initial impression is that this is a reftest issue. The reftests are frustrating because dependency changes can lead to images that vary by as little as one pixel and fail the test. And upstream doesn't provide a precise list of dependency versions they are using either. https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.34-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1987304/+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 1978129] Re: Incomplete support for DT_RELR relocations on Ubuntu 22.04
** Changed in: ubuntu-power-systems Status: In Progress => Fix Committed -- 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/1978129 Title: Incomplete support for DT_RELR relocations on Ubuntu 22.04 Status in The Ubuntu-power-systems project: 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] * The latest glibc uses DT_RELR relocations, but it turned out that the linker support is still incomplete, as of binutils-2.38-3ubuntu1 on Ubuntu 22.04. * It lacks the fix/commit 'PowerPC64 DT_RELR relative reloc addresses'. * As discussed at the binutils mailing list: https://sourceware.org/pipermail/binutils/2022-March/119921.html this fixes several (glibc) regressions (from 574 to 17). * Instead of stashing r_offset final address calculations in ppc64_elf_size_stubs for use by ppc64_elf_build_stubs, section/offset pairs need to be kept. [Test Plan] * Build and run the official (make) check: git clone git://sourceware.org/git/glibc.git mkdir build && cd build ../glibc/configure --prefix=/usr && make -j8 && make check [Where problems could occur] * In case relr_addr is not replaced everywhere it's deletion in elf64-ppc.c can cause problems, which will mainly occur at build time. * The relr section/offset array may lead to problems if the array is not properly handled or used. * The rewrite of append_relr_off may cause issues due to wrong allocs erroneous pointer arithmetic or array handling. * The entirely new sort_relr function may introduce new code issues or performance issues. * The adjustments of ppc64_elf_size_stubs and ppc64_elf_build_stubs to the new relr code could be done wrong in which case the linker support is still not working. * But the patch was discussed at the upstream mailing list: https://sourceware.org/pipermail/binutils/2022-March/thread.html#119921 * and is limited to ppc, and even to file 'elf64-ppc.c'. __ == Comment: #0 - Matheus Salgueiro Castanho - 2022-06-09 09:32:29 == ---Problem Description--- Latest glibc uses DT_RELR relocations, but linker support is incomplete as of binutils-2.38-3ubuntu1 on Ubuntu 22.04. It lacks the following fix integrated into the upstream 2.38 branch: PowerPC64 DT_RELR relative reloc addresses https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=e4a35c7319628045302d4c597cb27f1b0a08c858 As mentioned in the binutils mailing list when this patch was discussed, this fixes several glibc regressions: https://sourceware.org/pipermail/binutils/2022-March/119921.html Contact Information = Matheus Castanho/mscasta...@ibm.com ---uname output--- N/A Machine Type = N/A ---Debugger--- A debugger is not configured ---Steps to Reproduce--- git clone git://sourceware.org/git/glibc.git mkdir build && cd build ../glibc/configure --prefix=/usr && make -j8 && make check Userspace tool common name: binutils The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Userspace tool obtained from project website: na *Additional Instructions for Matheus Castanho/mscasta...@ibm.com: -Attach ltrace and strace of userspace application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1978129/+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 1987001] Re: netplan.io autopkgtest failures with NetworkManager 1.39.90
Lukas, could you report your findings to https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues ? Thanks! ** Changed in: network-manager (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1987001 Title: netplan.io autopkgtest failures with NetworkManager 1.39.90 Status in netplan.io package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Triaged Bug description: netplan.io's autopkgtests are failing with NetworkManager 1.40 RC1 (1.39.90). https://autopkgtest.ubuntu.com/packages/n/netplan.io/kinetic/amd64 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-40/NEWS log excerpt: == FAIL: test_bond_mode_8023ad_adselect (__main__.TestNetworkManager) -- Traceback (most recent call last): File "/tmp/autopkgtest.iNCkRv/build.oDI/src/tests/integration/bonds.py", line 147, in test_bond_mode_8023ad_adselect self.assertEqual(f.read().strip(), 'bandwidth 1') AssertionError: 'stable 0' != 'bandwidth 1' - stable 0 + bandwidth 1 == FAIL: test_bond_mode_balance_tlb_learn_interval (__main__.TestNetworkManager) -- Traceback (most recent call last): File "/tmp/autopkgtest.iNCkRv/build.oDI/src/tests/integration/bonds.py", line 670, in test_bond_mode_balance_tlb_learn_interval self.assertEqual(f.read().strip(), '15') AssertionError: '1' != '15' - 1 + 15 ? + To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1987001/+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 634900] Re: "oom never" makes ssh upstart job fail to start in OpenVZ container
I'll mark the bug as fix released as I think Ubuntu releases no longer suffer from this problem. Also, all Ubuntu releases still receiving normal support have moved away from upstart. ** Changed in: upstart (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/634900 Title: "oom never" makes ssh upstart job fail to start in OpenVZ container Status in upstart package in Ubuntu: Fix Released Bug description: Binary package hint: upstart /etc/init/ssh.conf uses "oom never", which causes the job failing to start in an OpenVZ container. Host: - kernel: 2.6.32-5-openvz-amd64 (Debian testing) Container: openssh-server: 1:5.3p1-3ubuntu4 (Lucid) Upstart: 0.6.5-7 (Lucid) This is a known problem (mentioned on http://ubuntuforums.org/showpost.php?p=9170868=2). What information is required to debug this? Some strace output? WORKAROUND: - comment the "oom never" line POSSIBLE FIXES: 1. Ignore any errors when trying to set "oom never" for the job?! 2. Only apply "oom never" if not in a virtualized context (see comment #2). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/634900/+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 1982108] Re: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS
I can confirm this resolves the issue of embedded interpreters crashing (tested with Kodi). Versions used: ii libpython3-dev:amd64 3.10.6-1~22.04 amd64header files and a static library for Python (default) ii libpython3-stdlib:amd64 3.10.6-1~22.04 amd64interactive high-level object-oriented language (default python3 version) ii libpython3.10:amd64 3.10.6-1~22.04 amd64Shared Python runtime library (version 3.10) ii libpython3.10-dev:amd64 3.10.6-1~22.04 amd64Header files and a static library for Python (v3.10) ii libpython3.10-minimal:amd64 3.10.6-1~22.04 amd64Minimal subset of the Python language (version 3.10) ii libpython3.10-stdlib:amd643.10.6-1~22.04 amd64Interactive high-level object-oriented language (standard library, version 3.10) ii python3 3.10.6-1~22.04 amd64interactive high-level object-oriented language (default python3 version) ii python3-dev 3.10.6-1~22.04 amd64header files and a static library for Python (default) ii python3-distutils 3.10.6-1~22.04 all distutils package for Python 3.x ii python3-lib2to3 3.10.6-1~22.04 all Interactive high-level object-oriented language (lib2to3) ii python3-minimal 3.10.6-1~22.04 amd64minimal subset of the Python language (default python3 version) ii python3-venv 3.10.6-1~22.04 amd64venv module for python3 (default python3 version) ii python3.103.10.6-1~22.04 amd64Interactive high-level object-oriented language (version 3.10) ii python3.10-dev3.10.6-1~22.04 amd64Header files and a static library for Python (v3.10) ii python3.10-minimal3.10.6-1~22.04 amd64Minimal subset of the Python language (version 3.10) ii python3.10-venv 3.10.6-1~22.04 amd64Interactive high-level object-oriented language (pyvenv binary, version 3.10) ** 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 python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1982108 Title: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: Confirmed Status in python3.10 package in Ubuntu: Confirmed Status in python3-defaults source package in Jammy: Fix Committed Status in python3-stdlib-extensions source package in Jammy: Fix Committed Status in python3.10 source package in Jammy: Fix Committed Bug description: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS we are doing a test rebuild of 22.04 main to check for regressions. test rebuilds at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-jammy.html https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-gcc-jammy.html the first one is the reference test rebuild, the second one the rebuild using updated binutils, GCC and python packages. Analysis: regressions on riscv64 (caused by enabling the tests) are: abseil adsys colord dovecot glib-networking glibc gnome-bluetooth3 gnome-control-center google-perftools json-glib libfprint libgdata memcached mir openvswitch ovn pmdk power-profiles-daemon strace swtpm vim devscripts is not a regression, introduced by a custom dpkg- buildpackage wrapper. binutils and python3-stdlib-extensions are superseded which are part of the planned updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1982108/+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 1987001] Re: netplan.io autopkgtest failures with NetworkManager 1.39.90
I think this might be a real regression in NM. Netplan is testing something like this (which worked nicely in the past): mybond: parameters: mode: 802.3ad ad-select: bandwidth Therefore, /sys/class/net/mybond/bonding/ad_select should actually contain "bandwidth 1", not the default "stable 0" value. Might be related to this? https://github.com/NetworkManager/NetworkManager/commit/e064eb9d1361f5f17a092097807c452add8040bc Same for learn-interval: mybond: parameters: mode: balance-tlb mii-monitor-interval: 5 learn-packet-interval: 15 => /sys/class/net/mybond/bonding/lp_interval should actually be "15" ** Changed in: netplan.io (Ubuntu) Status: Confirmed => Triaged ** Changed in: network-manager (Ubuntu) Importance: Undecided => High ** Changed in: netplan.io (Ubuntu) Importance: High => Undecided -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1987001 Title: netplan.io autopkgtest failures with NetworkManager 1.39.90 Status in netplan.io package in Ubuntu: Triaged Status in network-manager package in Ubuntu: New Bug description: netplan.io's autopkgtests are failing with NetworkManager 1.40 RC1 (1.39.90). https://autopkgtest.ubuntu.com/packages/n/netplan.io/kinetic/amd64 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-40/NEWS log excerpt: == FAIL: test_bond_mode_8023ad_adselect (__main__.TestNetworkManager) -- Traceback (most recent call last): File "/tmp/autopkgtest.iNCkRv/build.oDI/src/tests/integration/bonds.py", line 147, in test_bond_mode_8023ad_adselect self.assertEqual(f.read().strip(), 'bandwidth 1') AssertionError: 'stable 0' != 'bandwidth 1' - stable 0 + bandwidth 1 == FAIL: test_bond_mode_balance_tlb_learn_interval (__main__.TestNetworkManager) -- Traceback (most recent call last): File "/tmp/autopkgtest.iNCkRv/build.oDI/src/tests/integration/bonds.py", line 670, in test_bond_mode_balance_tlb_learn_interval self.assertEqual(f.read().strip(), '15') AssertionError: '1' != '15' - 1 + 15 ? + To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1987001/+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 1987257] Re: Please merge sysvinit 3.04-1 (main) from Debian unstable (main)
This bug was fixed in the package sysvinit - 3.04-1ubuntu1 --- sysvinit (3.04-1ubuntu1) kinetic; urgency=low * Merge from Debian unstable. (LP: #1987257) Remaining changes: - When building for Ubuntu, skip all binaries except for sysvinit-utils - Define the DEB_HOST_* variables in d/rules if not defined already sysvinit (3.04-1) unstable; urgency=medium * New upstream version 3.04 * Bracket lintian overrides. sysvinit (3.03-1) unstable; urgency=medium * New upstream version 3.03 * Remove patch applied upstream. * mount-functions.sh: add PARTUUID and PARTLABEL support. (Closes: #1008910) * mount-functions.sh: Update comment describing read_fstab(). sysvinit (3.02-1) experimental; urgency=medium * Change upstream to GitHub. * New upstream version 3.02 * Refresh patches. * Delete patch applied upstream. * Add patch to fix groff formatting error in init.8. -- Olivier Gayot Sat, 22 Aug 2022 09:57:41 +0200 ** Changed in: sysvinit (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1987257 Title: Please merge sysvinit 3.04-1 (main) from Debian unstable (main) Status in sysvinit package in Ubuntu: Fix Released Bug description: base: 3.01-1 ubuntu: 3.01-1ubuntu1 debian: 3.04-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1987257/+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
Hello bugproxy, or anyone else affected, Accepted binutils into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/binutils/2.38-4ubuntu2 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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. ** Changed in: binutils (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-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: In Progress 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 1982105] Re: update binutils to the 2.38 branch in 20.04 LTS
Hello Matthias, or anyone else affected, Accepted binutils into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/binutils/2.38-4ubuntu2 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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. ** Changed in: binutils (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-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/1982105 Title: update binutils to the 2.38 branch in 20.04 LTS Status in binutils package in Ubuntu: New Status in binutils source package in Jammy: Fix Committed Bug description: SRU: update binutils to the 2.38 branch in 20.04 LTS. The new build will be validated by the main component on all architectures. test rebuilds at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-jammy.html https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-gcc-jammy.html the first one is the reference test rebuild, the second one the rebuild using updated binutils, GCC and python packages. Analysis: regressions on riscv64 (caused by enabling the tests) are: abseil adsys colord dovecot glib-networking glibc gnome-bluetooth3 gnome-control-center google-perftools json-glib libfprint libgdata memcached mir openvswitch ovn pmdk power-profiles-daemon strace swtpm vim devscripts is not a regression, introduced by a custom dpkg- buildpackage wrapper. binutils and python3-stdlib-extensions are superseded which are part of the planned updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1982105/+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 1978129] Re: Incomplete support for DT_RELR relocations on Ubuntu 22.04
Hello bugproxy, or anyone else affected, Accepted binutils into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/binutils/2.38-4ubuntu2 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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. ** Changed in: binutils (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-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/1978129 Title: Incomplete support for DT_RELR relocations on Ubuntu 22.04 Status in The Ubuntu-power-systems project: In Progress 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] * The latest glibc uses DT_RELR relocations, but it turned out that the linker support is still incomplete, as of binutils-2.38-3ubuntu1 on Ubuntu 22.04. * It lacks the fix/commit 'PowerPC64 DT_RELR relative reloc addresses'. * As discussed at the binutils mailing list: https://sourceware.org/pipermail/binutils/2022-March/119921.html this fixes several (glibc) regressions (from 574 to 17). * Instead of stashing r_offset final address calculations in ppc64_elf_size_stubs for use by ppc64_elf_build_stubs, section/offset pairs need to be kept. [Test Plan] * Build and run the official (make) check: git clone git://sourceware.org/git/glibc.git mkdir build && cd build ../glibc/configure --prefix=/usr && make -j8 && make check [Where problems could occur] * In case relr_addr is not replaced everywhere it's deletion in elf64-ppc.c can cause problems, which will mainly occur at build time. * The relr section/offset array may lead to problems if the array is not properly handled or used. * The rewrite of append_relr_off may cause issues due to wrong allocs erroneous pointer arithmetic or array handling. * The entirely new sort_relr function may introduce new code issues or performance issues. * The adjustments of ppc64_elf_size_stubs and ppc64_elf_build_stubs to the new relr code could be done wrong in which case the linker support is still not working. * But the patch was discussed at the upstream mailing list: https://sourceware.org/pipermail/binutils/2022-March/thread.html#119921 * and is limited to ppc, and even to file 'elf64-ppc.c'. __ == Comment: #0 - Matheus Salgueiro Castanho - 2022-06-09 09:32:29 == ---Problem Description--- Latest glibc uses DT_RELR relocations, but linker support is incomplete as of binutils-2.38-3ubuntu1 on Ubuntu 22.04. It lacks the following fix integrated into the upstream 2.38 branch: PowerPC64 DT_RELR relative reloc addresses https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=e4a35c7319628045302d4c597cb27f1b0a08c858 As mentioned in the binutils mailing list when this patch was discussed, this fixes several glibc regressions: https://sourceware.org/pipermail/binutils/2022-March/119921.html Contact Information = Matheus Castanho/mscasta...@ibm.com ---uname output--- N/A Machine Type = N/A ---Debugger--- A debugger is not configured ---Steps to Reproduce--- git clone git://sourceware.org/git/glibc.git mkdir build && cd build ../glibc/configure --prefix=/usr && make -j8 && make check Userspace tool common name: binutils The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Userspace tool obtained from project website: na *Additional Instructions for Matheus Castanho/mscasta...@ibm.com: -Attach ltrace and strace of userspace application. To manage notifications about this bug go to:
[Touch-packages] [Bug 1987340] Re: Please merge lvm2 2.03.16-1 from Debian unstable.
** Changed in: lvm2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1987340 Title: Please merge lvm2 2.03.16-1 from Debian unstable. Status in lvm2 package in Ubuntu: Confirmed Bug description: Please merge lvm2 2.03.16-1 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1987340/+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 1987340] Re: Please merge lvm2 2.03.16-1 from Debian unstable.
Test builds are available from ppa:waveform/lvm2 at the following URL: https://launchpad.net/~waveform/+archive/ubuntu/lvm2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1987340 Title: Please merge lvm2 2.03.16-1 from Debian unstable. Status in lvm2 package in Ubuntu: New Bug description: Please merge lvm2 2.03.16-1 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1987340/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Hi, @jeremyszu
How can I build grub from your repository
https://github.com/os369510/grub2 with your patches for testing my linux
box?
Thanks in advance!
--
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/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Confirmed
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c” but I use the
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
Thus it should not impact them.
* There is a “#if defined(__x86_64__)” which intent to limit the >
32bits code in i386 system and also
```
#if defined (__code_model_large__)
-#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
+#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
#else
#define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
#endif
```
If everything works as expected, then i386 should working good.
If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
4GB memory region and never be able to access.
[Other Info]
* Upstream grub2 bug #61058
https://savannah.gnu.org/bugs/index.php?61058
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320
* Test grubx64.efi:
https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320
* Test source code: https://github.com/os369510/grub2/tree/lp1842320
* If you built the package, then test grubx64.efi is under
“obj/monolithic/grub-efi-amd64/grubx64.efi”, in
[Touch-packages] [Bug 1987353] Re: Software Updater not showing third-party repository with "signed-by" tag
Reassigning to correct package, and confirmed. So while [arch=amd64] works fine [signed-by=...] does not which is odd. Neither are *properly* supported in software-properties: sources.list options are not exposed at all; it's unclear what happens if you modify them. ** Package changed: update-manager (Ubuntu) => software-properties (Ubuntu) ** Changed in: software-properties (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1987353 Title: Software Updater not showing third-party repository with "signed-by" tag Status in software-properties package in Ubuntu: Triaged Bug description: Since apt-key is now deprecated, I followed various guides and moved all third-party repository keys to /etc/apt/keyrings/, then added the "signed-by" tag to the corresponding source lists. After that, those third-party repositories no longer show up in the "Other Software" tab in Software Updater. /home/jing>lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 /home/jing>apt-cache policy update-manager update-manager: Installed: 1:22.04.9 Candidate: 1:22.04.9 Version table: *** 1:22.04.9 500 500 http://archive.ubuntu.mirror.rafal.ca/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.mirror.rafal.ca/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: update-manager 1:22.04.9 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Mon Aug 22 18:27:09 2022 InstallationDate: Installed on 2018-10-23 (1399 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: Upgraded to jammy on 2022-08-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1987353/+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 1987353] [NEW] Software Updater not showing third-party repository with "signed-by" tag
You have been subscribed to a public bug: Since apt-key is now deprecated, I followed various guides and moved all third-party repository keys to /etc/apt/keyrings/, then added the "signed-by" tag to the corresponding source lists. After that, those third-party repositories no longer show up in the "Other Software" tab in Software Updater. /home/jing>lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 /home/jing>apt-cache policy update-manager update-manager: Installed: 1:22.04.9 Candidate: 1:22.04.9 Version table: *** 1:22.04.9 500 500 http://archive.ubuntu.mirror.rafal.ca/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.mirror.rafal.ca/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: update-manager 1:22.04.9 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Mon Aug 22 18:27:09 2022 InstallationDate: Installed on 2018-10-23 (1399 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: Upgraded to jammy on 2022-08-21 (1 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- Software Updater not showing third-party repository with "signed-by" tag https://bugs.launchpad.net/bugs/1987353 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981622] Re: mtd device must be supplied (device name is empty)
--
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/1981622
Title:
mtd device must be supplied (device name is empty)
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Triaged
Status in systemd source package in Jammy:
Triaged
Bug description:
[WORKAROUND]
This will NOT fix a system that is not booting, because the "mtd
device must be supplied (device name is empty)" message is not the
cause of failed boots. This work around is only for those who are
annoyed by the error message, but are otherwise not experiencing any
issues.
If you are not able to boot your system, but you see this error
message, please open a separate bug with your journalctl and dmesg
logs.
# cp /{lib,etc}/systemd/system/systemd-pstore.service
# sed -i 's/modprobe@mtdpstore.service //'
/etc/systemd/system/systemd-pstore.service
# systemctl daemon-reload
[Impact]
Due to mtdpstore not being properly configured as a pstore backend,
when systemd-pstore.service tries to load the module, users get the
following error in dmesg:
[ 18.453473] systemd[1]: Starting Load Kernel Module mtdpstore...
[ 18.462685] mtd device must be supplied (device name is empty)
This is a distracting error for users trying to diagnose other system
issues, especially if their system does not boot after a kernel crash
and this is the only message displayed on the console.
[Test Plan]
* Force a kernel crash to populate /sys/fs/pstore, thus causing
systemd-pstore.service to start on the subsequent boot:
# echo 1 > /proc/sys/kernel/sysrq
# echo 1 > /proc/sys/kernel/panic
# echo c > /proc/sysrq-trigger
* When the system reboots, observe the error in dmesg:
# dmesg | grep mtd
[Where problems could occur]
If a system was relying on this pstore backend, and mtdpstore is built
as a module, it is possible for systemd-pstore.service to trigger
before mtdpstore is loaded, causing systemd-pstore to not copy the
contents of /sys/fs/pstore. Note however that before the patched
introduced as a result of bug 1978079, systemd-pstore.service would
not attempt to load *any* kernel modules.
[Original Description]
After updating my 22.04 system (possibly caused by Systemd update).
And now booting, dmesg has two errors:
'mtd device must be supplied (device name is empty)'.
See line 8 and 134 in the included logfile.
The system are booting as it should though, and the system are working
like it should no errors at all.
Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
systemd?
I have an EFI mounted at boot but it isn't used because I have
installed my system in legacy BIOS mode.
Is this maybe the culprit?
I could ignore the message but it isn't nice though.
Regards
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+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 1844682] Re: ubuntu-bug _usr_bin_sudo.crash yields AttributeError
*** This bug is a duplicate of bug 1983481 ***
https://bugs.launchpad.net/bugs/1983481
I have to correct my last comment: ui was None. Therefore this bug is a
duplicate of bug #1983481.
** Package changed: sudo (Ubuntu) => apport (Ubuntu)
** This bug has been marked a duplicate of bug 1983481
_run_hook called with ui=None
--
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/1844682
Title:
ubuntu-bug _usr_bin_sudo.crash yields AttributeError
Status in apport package in Ubuntu:
New
Bug description:
While digging through /var/crash folder I've realized that I do have a
few crashes involving sudo. To be exact, couple of files names
_usr_bin_sudo.N.crash
Logically, I've tried uploading those to Ubuntu error tracker using
following:
ubuntu-bug /var/crash/_usr_bin_sudo.0.crash
It failed mumbling about permissions. So, stupid but common next step:
sudo ubuntu-bug /var/crash/_usr_bin_sudo.0.crash
yielded me the following Python Traceback:
** (apport-gtk:6825): WARNING **: Couldn't connect to accessibility bus:
Failed to connect to socket /tmp/dbus-ILURWtYdgA: Connection refused
ERROR: hook /usr/share/apport/package-hooks/source_sudo.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in
_run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_sudo.py", line 20, in add_info
response = ui.yesno("The contents of your /etc/sudoers file may help
developers diagnose your bug more quickly, however, it may contain sensitive
information. Do you want to include it in your bug report?")
AttributeError: 'NoneType' object has no attribute 'yesno'
It seems that in the end, something got uploaded to the server, but it
didn't make any indication of successful upload what-so-ever.
Repeating the same sequence of actions does not yield the same Python
Traceback and exits gracefully.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2.19
ProcVersionSignature: Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-64-generic x86_64
ApportLog:
ApportVersion: 2.20.1-0ubuntu2.19
Architecture: amd64
Date: Thu Sep 19 17:09:29 2019
PackageArchitecture: all
ProcEnviron:
LANGUAGE=en_US
TERM=xterm-256color
PATH=(custom, no user)
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/1844682/+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 1891798] Re: Backport fix from sudo 1.8.22 to fix "stair-stepped output" bug
Can you provide a test case do demonstrate this behavior (and for using in https://wiki.ubuntu.com/StableReleaseUpdates)? -- 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/1891798 Title: Backport fix from sudo 1.8.22 to fix "stair-stepped output" bug Status in sudo package in Ubuntu: New Status in sudo source package in Bionic: New Bug description: sudo 1.8.20 introduced a bug in commit 44dc15d02dc0b34bf03bc971ba08d3a761c3a031 that is fixed by sudo 1.8.22 in commit 3b88cdfcd8d1a39eabbb5b7d0c8fe8f035d7a264 When the "use_pty" option is enabled, "stair-stepped output" occurs if sudo is piped to another command. Example output attached in a text file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sudo 1.8.21p2-3ubuntu1.2 Uname: Linux 5.4.50+ x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 16 12:29:23 2020 InstallationDate: Installed on 2014-05-10 (2290 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: sudo UpgradeStatus: Upgraded to bionic on 2018-11-24 (630 days ago) modified.conffile..etc.pam.d.sudo: [inaccessible: [Errno 13] Permission denied: '/etc/pam.d/sudo'] modified.conffile..etc.sudoers: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers'] modified.conffile..etc.sudoers.d.README: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/README'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1891798/+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 1980578] Re: package sudo 1.9.5p2-3ubuntu2 failed to install/upgrade: installed sudo package pre-removal script subprocess returned error exit status 1
Thanks for reporting this bug. You tried to remove sudo and sudo gave a clear warning in the dpkg terminal log: ``` Removing ubuntu-minimal (1.472) ... Removing sudo (1.9.5p2-3ubuntu2) ... You have asked that the sudo package be removed, but no root password has been set. Without sudo, you may not be able to gain administrative privileges. If you would prefer to access the root account with su(1) or by logging in directly, you must set a root password with "sudo passwd". If you have arranged other means to access the root account, and you are sure this is what you want, you may bypass this check by setting an environment variable (export SUDO_FORCE_REMOVE=yes). Refusing to remove sudo. dpkg: error processing package sudo (--remove): installed sudo package pre-removal script subprocess returned error exit status 1 dpkg: too many errors, stopping ``` So sudo is working as intended. If it wasn't your intention to remove sudo, please file a bug against the package that caused the removal. In that case we need to know what was installed and what was intended to be installed/removed. ** Changed in: sudo (Ubuntu) Status: New => Invalid -- 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/1980578 Title: package sudo 1.9.5p2-3ubuntu2 failed to install/upgrade: installed sudo package pre-removal script subprocess returned error exit status 1 Status in sudo package in Ubuntu: Invalid Bug description: ubuntu software vs code and many app not working ProblemType: Package DistroRelease: Ubuntu 21.10 Package: sudo 1.9.5p2-3ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-52.59-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.2 AptOrdering: ubuntu-minimal:amd64: Purge sudo:amd64: Purge NULL: ConfigurePending NULL: PurgePending NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Jul 3 00:10:20 2022 DpkgHistoryLog: Start-Date: 2022-07-03 00:10:20 Commandline: /usr/bin/apt-get purge sudo Purge: sudo:amd64 (1.9.5p2-3ubuntu2), ubuntu-minimal:amd64 (1.472) ErrorMessage: installed sudo package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2021-04-14 (444 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RelatedPackageVersions: dpkg 1.20.9ubuntu2.2 apt 2.3.9ubuntu0.1 SourcePackage: sudo Title: package sudo 1.9.5p2-3ubuntu2 failed to install/upgrade: installed sudo package pre-removal script subprocess returned error exit status 1 UpgradeStatus: Upgraded to impish on 2022-07-02 (0 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1980578/+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 1838489] Re: adduser & deluser shell command injection
It's fixed in Debian by version 3.121 and therefore fixed in adduser
3.121ubuntu1 in Ubuntu 22.10 (kinetic).
** Changed in: adduser (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to adduser in Ubuntu.
https://bugs.launchpad.net/bugs/1838489
Title:
adduser & deluser shell command injection
Status in adduser package in Ubuntu:
Fix Released
Status in adduser package in Debian:
Fix Released
Bug description:
deluser program is vulnerable to a command injection vulnerability
when a user is added via adduser with special characters (such as
';'). It is only possible when the user exists on the system (adduser
does not prevent usernames with ';' to be added.)
This can be a security risk when user accounts on the system can be
created from arbitrary input, and there are exploitable programs in
PATH to make privilege escalation possible.
-- Proof of concept
# ll /test-file
ls: cannot access '/test-file': No such file or directory
# cat /usr/bin/testscript
#!/bin/bash
touch /test-file
# deluser
Enter a user name to remove: ;testscript
no crontab for root
crontab: usage error: no arguments permitted after this option
usage: crontab [-u user] file
crontab [ -u user ] [ -i ] { -e | -l | -r }
(default operation is replace, per 1003.2)
-e (edit user's crontab)
-l (list user's crontab)
-r (delete user's crontab)
-i (prompt before deleting user's crontab)
/usr/sbin/deluser: `/usr/bin/crontab -r ;testscript' returned error code 1.
Exiting.
(failed reverse-i-search)`': deluser^C
# ll /test-file
-rw--- 1 root root 0 Jul 31 10:25 /test-file
system description
Description: Ubuntu 18.04.2 LTS
Release: 18.04
# apt-cache policy adduser
adduser:
Installed: 3.116ubuntu1
Candidate: 3.116ubuntu1
Version table:
*** 3.116ubuntu1 500
500 http://mirror.optus.net/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1838489/+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 1987252] Re: "Beacon request: No valid channels" for 802.11k measurement (RRM) then frequent disconnections
The attachment "rrm-include-passive-channels-in-active-beacon-report- scan.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 wpa in Ubuntu. https://bugs.launchpad.net/bugs/1987252 Title: "Beacon request: No valid channels" for 802.11k measurement (RRM) then frequent disconnections Status in wpa package in Ubuntu: New Bug description: When running a laptop with a mesh WiFi network, frequent disconnections happen like 10 to 20 times per hour. And the issue has disappeared by applying the following patch. https://w1.fi/cgit/hostap/commit/?id=8e0ac53660aaa9691e140156c47fddb7cd8c62b6 > RRM: Include passive channels in active beacon report scan > When receiving a beacon report request with the mode set to active, > channels that are marked as NO_IR were not added to the scan request. > However, active mode just mean that active scan is allowed, but not > that it is a must, so these channels should not be omitted. > Include channels that are marked as NO_IR in the scan request even > if the mode is set to active. So I'd like to request a backport of it. I believe the following combination of parameters is the key to trigger the "Beacon request: No valid channels" issue. - two or more access points as a mesh with 802.11k/v enabled - wpasupplicant 2.10 series or lower - kinetic with wpasupplicant=2.10-9ubuntu1 - jammy and wpasupplicant=2:2.10-6ubuntu2 - or lower - Using 5GHz - and all of 5GHz channels are marked as: - NO_IR (sudo wpa_cli get_capability freq) - or PASSIVE-SCAN (iw reg get) The log has a sudden "Connection to AP lost" with "No beacon heard and the time event is over already" as follows: > kernel: [136930.972759] wlp3s0: Connection to AP 6c:5a:b0:xx:yy:zz lost > kernel: [136931.217753] wlp3s0: authenticate with 6c:5a:b0:xx:yy:zz > kernel: [136931.229486] wlp3s0: send auth to 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136931.234536] wlp3s0: authenticated > kernel: [136931.239353] wlp3s0: associate with 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136931.253596] wlp3s0: RX AssocResp from 6c:5a:b0:xx:yy:zz (capab=0x1511 status=0 aid=2) > kernel: [136931.255411] wlp3s0: associated > kernel: [136931.843561] iwlwifi :03:00.0: No beacon heard and the time event is over already... > kernel: [136931.843650] wlp3s0: Connection to AP 6c:5a:b0:xx:yy:zz lost > kernel: [136932.067556] wlp3s0: authenticate with 6c:5a:b0:xx:yy:zz > kernel: [136932.078277] wlp3s0: send auth to 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136932.085292] wlp3s0: authenticated > kernel: [136932.087341] wlp3s0: associate with 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136932.100737] wlp3s0: RX AssocResp from 6c:5a:b0:xx:yy:zz (capab=0x1511 status=0 aid=2) > kernel: [136932.103238] wlp3s0: associated > kernel: [136932.392477] wlp3s0: Limiting TX power to 20 (23 - 3) dBm as advertised by 6c:5a:b0:xx:yy:zz And wpa_supplicant considers it in syslog as: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=6c:5a:b0:xx:yy:zz reason=4 locally_generated=1 By enabling debug of wpa_supplicant with `sudo wpa_cli log_level DEBUG`, I found "Beacon request: No valid channels" message on the client (Ubuntu laptop) at the same timing as 11k measuremrent on the AP every 6 seconds. > Aug 21 14:01:06 deco daemon.notice nrd[22822]: estimatorPerformMeasurement: Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from serving BSS APId 255 ChanId 48 ESSId 0 > Aug 21 14:01:06 deco daemon.err nrd[22822] estimatorCmnHandleBeaconReportEvent: Invalid beacon report for D4:3B:04:XX:YY:ZZ > > Aug 21 14:01:06 t480 wpa_supplicant[1613]: Beacon request: No valid channels > > Aug 21 14:01:12 deco daemon.notice nrd[22822]: estimatorPerformMeasurement: Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from serving BSS APId 255 ChanId 48 ESSId 0 > Aug 21 14:01:12 deco daemon.err nrd[22822] estimatorCmnHandleBeaconReportEvent: Invalid beacon report for D4:3B:04:XX:YY:ZZ > > Aug 21 14:01:12 t480 wpa_supplicant[1613]: Beacon request: No valid channels > > Aug 21 14:01:18 deco daemon.notice nrd[22822]: estimatorPerformMeasurement: Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from serving BSS APId 255 ChanId 48 ESSId 0 > Aug 21 14:01:18 deco daemon.err nrd[22822] estimatorCmnHandleBeaconReportEvent: Invalid beacon report for D4:3B:04:XX:YY:ZZ > > Aug 21 14:01:18 t480 wpa_supplicant[1613]: Beacon request: No valid channels This suggests that there is a clear disagreement around 11k between the client and the AP. And after
[Touch-packages] [Bug 1387825] Re: The default NAME_REGEX value in /etc/adduser.conf is incorrect
It's fixed in 3.119 and therefore fixed in adduser 3.121ubuntu1 in Ubuntu 22.10 (kinetic). ** Changed in: adduser (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/1387825 Title: The default NAME_REGEX value in /etc/adduser.conf is incorrect Status in adduser package in Ubuntu: Fix Released Status in adduser package in Debian: Fix Released Bug description: Refer the Debian bug report for more information. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630750 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: adduser 3.113+nmu3ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-22.29-lowlatency 3.16.4 Uname: Linux 3.16.0-22-lowlatency i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: KDE Date: Fri Oct 31 01:55:03 2014 InstallationDate: Installed on 2013-03-08 (600 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) PackageArchitecture: all SourcePackage: adduser UpgradeStatus: Upgraded to trusty on 2014-04-19 (194 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1387825/+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 1982108] Re: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS
Weirdly, two of the syncs prepared (python3.10 and python3-stdlib- extensions) don't have any Launchpad-Bugs-Fixed in their .changes files (even though bugs are correctly visible in the changelog. Since those are binary syncs and time-consuming to rebuild, I accepted those as-is. But please remember that, if in case of the sru-report not figuring this out, there are three packages as part of this update that need to go out at the same time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1982108 Title: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: Confirmed Status in python3.10 package in Ubuntu: Confirmed Status in python3-defaults source package in Jammy: Fix Committed Status in python3-stdlib-extensions source package in Jammy: Fix Committed Status in python3.10 source package in Jammy: Fix Committed Bug description: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS we are doing a test rebuild of 22.04 main to check for regressions. test rebuilds at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-jammy.html https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-gcc-jammy.html the first one is the reference test rebuild, the second one the rebuild using updated binutils, GCC and python packages. Analysis: regressions on riscv64 (caused by enabling the tests) are: abseil adsys colord dovecot glib-networking glibc gnome-bluetooth3 gnome-control-center google-perftools json-glib libfprint libgdata memcached mir openvswitch ovn pmdk power-profiles-daemon strace swtpm vim devscripts is not a regression, introduced by a custom dpkg- buildpackage wrapper. binutils and python3-stdlib-extensions are superseded which are part of the planned updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1982108/+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 1982108] Please test proposed package
Hello Matthias, or anyone else affected, Accepted python3-stdlib-extensions into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python3-stdlib- extensions/3.10.6-1~22.04 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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 python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1982108 Title: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: Confirmed Status in python3.10 package in Ubuntu: Confirmed Status in python3-defaults source package in Jammy: Fix Committed Status in python3-stdlib-extensions source package in Jammy: Fix Committed Status in python3.10 source package in Jammy: Fix Committed Bug description: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS we are doing a test rebuild of 22.04 main to check for regressions. test rebuilds at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-jammy.html https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-gcc-jammy.html the first one is the reference test rebuild, the second one the rebuild using updated binutils, GCC and python packages. Analysis: regressions on riscv64 (caused by enabling the tests) are: abseil adsys colord dovecot glib-networking glibc gnome-bluetooth3 gnome-control-center google-perftools json-glib libfprint libgdata memcached mir openvswitch ovn pmdk power-profiles-daemon strace swtpm vim devscripts is not a regression, introduced by a custom dpkg- buildpackage wrapper. binutils and python3-stdlib-extensions are superseded which are part of the planned updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1982108/+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 1982108] Please test proposed package
Hello Matthias, or anyone else affected, Accepted python3.10 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python3.10/3.10.6-1~22.04 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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. ** Changed in: python3-stdlib-extensions (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1982108 Title: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: Confirmed Status in python3.10 package in Ubuntu: Confirmed Status in python3-defaults source package in Jammy: Fix Committed Status in python3-stdlib-extensions source package in Jammy: Fix Committed Status in python3.10 source package in Jammy: Fix Committed Bug description: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS we are doing a test rebuild of 22.04 main to check for regressions. test rebuilds at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-jammy.html https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-gcc-jammy.html the first one is the reference test rebuild, the second one the rebuild using updated binutils, GCC and python packages. Analysis: regressions on riscv64 (caused by enabling the tests) are: abseil adsys colord dovecot glib-networking glibc gnome-bluetooth3 gnome-control-center google-perftools json-glib libfprint libgdata memcached mir openvswitch ovn pmdk power-profiles-daemon strace swtpm vim devscripts is not a regression, introduced by a custom dpkg- buildpackage wrapper. binutils and python3-stdlib-extensions are superseded which are part of the planned updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1982108/+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 1982108] Re: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS
Hello Matthias, or anyone else affected, Accepted python3-defaults into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python3-defaults/3.10.6-1~22.04 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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. ** Changed in: python3-defaults (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy ** Changed in: python3.10 (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1982108 Title: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: Confirmed Status in python3.10 package in Ubuntu: Confirmed Status in python3-defaults source package in Jammy: Fix Committed Status in python3-stdlib-extensions source package in Jammy: Fix Committed Status in python3.10 source package in Jammy: Fix Committed Bug description: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS we are doing a test rebuild of 22.04 main to check for regressions. test rebuilds at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-jammy.html https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-gcc-jammy.html the first one is the reference test rebuild, the second one the rebuild using updated binutils, GCC and python packages. Analysis: regressions on riscv64 (caused by enabling the tests) are: abseil adsys colord dovecot glib-networking glibc gnome-bluetooth3 gnome-control-center google-perftools json-glib libfprint libgdata memcached mir openvswitch ovn pmdk power-profiles-daemon strace swtpm vim devscripts is not a regression, introduced by a custom dpkg- buildpackage wrapper. binutils and python3-stdlib-extensions are superseded which are part of the planned updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1982108/+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 1987257] Re: Please merge sysvinit 3.04-1 (main) from Debian unstable (main)
Thanks, LGTM! ** Changed in: sysvinit (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1987257 Title: Please merge sysvinit 3.04-1 (main) from Debian unstable (main) Status in sysvinit package in Ubuntu: In Progress Bug description: base: 3.01-1 ubuntu: 3.01-1ubuntu1 debian: 3.04-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1987257/+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
