[Touch-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
The current apparmor profile for digikam in oracular has these rules: /usr/lib/x86_64-linux-gnu/qt5/libexec/QtWebEngineProcess cx -> &digikam//QtWebEngineProcess, /usr/lib/aarch64-linux-gnu/qt5/libexec/QtWebEngineProcess cx -> &digikam//QtWebEngineProcess, /usr/lib/arm-linux-gnueabihf/qt5/libexec/QtWebEngineProcess cx -> &digikam//QtWebEngineProcess, There is not even a qt6 path, which in oracular is indeed without the architecture path component: $ apt-file find QtWebEngineProcess apparmor: /etc/apparmor.d/QtWebEngineProcess libqt5webenginecore5: /usr/lib/aarch64-linux-gnu/qt5/libexec/QtWebEngineProcess libqt6webenginecore6-bin: /usr/lib/qt6/libexec/QtWebEngineProcess nsight-compute: /usr/lib/nsight-compute/host/linux-desktop-t210-a64/libexec/QtWebEngineProcess nsight-systems: /usr/lib/nsight-systems/host-linux-armv8/libexec/QtWebEngineProcess -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in AppArmor: New Status in Wike: New Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Fix Committed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Triaged Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Confirmed Status in foliate package in Ubuntu: Fix Committed Status in freecad package in Ubuntu: Invalid Status in geary package in Ubuntu: Fix Released Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Invalid Status in goldendict-webengine package in Ubuntu: Fix Released Status in guix package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Fix Released Status in kdeplasma-addons package in Ubuntu: Fix Released Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Incomplete Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in loupe package in Ubuntu: Fix Released Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Fix Released Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Fix Released Status in plasma-desktop package in Ubuntu: Fix Released Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Invalid Status in qmapshack package in Ubuntu: Fix Released Status in qutebrowser package in Ubuntu: Fix Released Status in rssguard package in Ubuntu: Fix Released Status in steam package in Ubuntu: Fix Released Status in supercollider package in Ubuntu: Fix Released Status in tellico package in Ubuntu: Fix Released Status in tor package in Ubuntu: Confirmed Status in wike package in Ubuntu: Fix Committed Status in apparmor source package in Noble: Fix Committed Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+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 2078851] Re: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd
I think this should be SRUed to noble, yes. ** Tags added: server-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/2078851 Title: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in cyrus-sasl2 source package in Noble: Triaged Status in cyrus-sasl2 source package in Oracular: Fix Released Bug description: Folder group permission of /var/spool/postfix/var/run/saslauthd gets reset to "root" (should be "sasl") every time saslauthd gets restarted. This worked fine before upgrading from 22.04 to 24.04 My automated workaround currently is this crontab (root) entry: */1 * * * * /usr/bin/chgrp sasl /var/spool/postfix/var/run/saslauthd 2>&1 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: postfix 3.8.6-1build2 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Sep 3 19:52:59 2024 SourcePackage: postfix UpgradeStatus: Upgraded to noble on 2024-08-31 (3 days ago) mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2078851/+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 2078356] Re: python3 preinst failure to run pre-rtupdate hooks
** Description changed: # README first - If you are hit by this bug, please check if your root user's environment - has the "errors" variable set: + https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/comments/62 + has the details. If you are hit by this bug, please check if your root + user's environment has the "errors" variable set: env | grep errors - sudo env | grep errors + And then unset the variable and run "apt -f install" (or repeat the apt + operation that failed and brought you here) [ Original Description ] running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults 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 python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 preinst failure to run pre-rtupdate hooks Status in python3-defaults package in Ubuntu: Confirmed Status in python3-defaults source package in Focal: Confirmed Status in python3-defaults source package in Jammy: Confirmed Status in python3-defaults source package in Noble: Confirmed Status in python3-defaults source package in Oracular: Confirmed Bug description: # README first https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/comments/62 has the details. If you are hit by this bug, please check if your root user's environment has the "errors" variable set: env | grep errors And then unset the variable and run "apt -f install" (or repeat the apt operation that failed and brought you here) [ Original Description ] running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 preinst failure to run pre-rtupdate hooks
Oracular also affected, obviously: Good case: root@o-py3-errors:~# apt install --reinstall python3 Summary: Upgrading: 0, Installing: 0, Reinstalling: 1, Removing: 0, Not Upgrading: 0 Download size: 0 B / 24.0 kB Space needed: 0 B / 98.5 GB available (Reading database ... 35925 files and directories currently installed.) Preparing to unpack .../python3_3.12.5-1_amd64.deb ... running python pre-rtupdate hooks for python3.12... Unpacking python3 (3.12.5-1) over (3.12.5-1) ... Setting up python3 (3.12.5-1) ... running python rtupdate hooks for python3.12... running python post-rtupdate hooks for python3.12... Processing triggers for man-db (2.12.1-3) ... The bug: root@o-py3-errors:~# errors=andreas-was-here apt install --reinstall python3 Summary: Upgrading: 0, Installing: 0, Reinstalling: 1, Removing: 0, Not Upgrading: 0 Download size: 0 B / 24.0 kB Space needed: 0 B / 98.5 GB available (Reading database ... 35925 files and directories currently installed.) Preparing to unpack .../python3_3.12.5-1_amd64.deb ... running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.5-1_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.5-1_amd64.deb Error: Sub-process /usr/bin/dpkg returned an error code (1) ** Also affects: python3-defaults (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: python3-defaults (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: python3-defaults (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: python3-defaults (Ubuntu Oracular) Importance: Undecided Status: Confirmed ** Description changed: # README first - If you are hit by this bug, please provide the information asked in the - comment #53 further down in this page, thanks + If you are hit by this bug, please check if your root user's environment + has the "errors" variable set: + + env | grep errors + + sudo env | grep errors + [ Original Description ] running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: python3-defaults (Ubuntu Focal) Status: New => Confirmed ** Changed in: python3-defaults (Ubuntu Jammy) Status: New => Confirmed ** Changed in: python3-defaults (Ubuntu Noble) Status: New => Confirmed ** Changed in: python3-defaults (Ubuntu Focal) Importance: Undecided => High ** Changed in: python3-defaults (Ubuntu Jammy) Importance: Undecided => High ** Changed in: python3-defaults (Ubuntu Noble) Importance: Undecided => High ** Changed in: python3-defaults (Ubuntu Oracular) Importance: Undecided => High -- 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/2078356 Title: python3 preinst failure to run pre-rtupdate hooks Status in python3-defaults package in Ubuntu: Confirmed Status in python3-defaults source package in Focal: Confirmed Status in python3-defaults source package in Jammy: Confirmed Status in python3-defaults source package in Noble: Confirmed Status in python3-defaults source package in Oracular: Confirmed Bug description: # README first If you are hit by this bug, please check if your root user's environment has the "errors" variable set: env | grep errors sudo env | grep errors [ O
[Touch-packages] [Bug 2078356] Re: python3 preinst failure to run pre-rtupdate hooks
Amazing find @theofficialgman! -- 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/2078356 Title: python3 preinst failure to run pre-rtupdate hooks Status in python3-defaults package in Ubuntu: Confirmed Bug description: # README first If you are hit by this bug, please provide the information asked in the comment #53 further down in this page, thanks [ Original Description ] running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2076542] Re: FTBFS with autoconf 2.72
This was fixed in https://launchpad.net/debian/+source/heimdal/7.8.git20221117.28daf24+dfsg-8, and we have 8ubuntu1 in oracular (with the fix too). ** Changed in: heimdal (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 heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2076542 Title: FTBFS with autoconf 2.72 Status in heimdal package in Ubuntu: Fix Released Status in heimdal package in Debian: Fix Released Bug description: checking for gcc options needed to detect all undeclared functions... cannot detect configure: error: in '/home/ubuntu/git/packages/heimdal/heimdal': configure: error: cannot make gcc report undeclared builtins See 'config.log' for more details and configure:19563: gcc -c -g -O2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix-map=/home/ubuntu/git/packages/heimdal/heimdal=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fdebug-prefix-map=/home/ubuntu/git/packages/heimdal/heimdal=/usr/src/heimdal-7.8.git20221117.28daf24+dfsg-7ubuntu1 -fno-builtin -Wdate-time -D_FORTIFY_SOURCE=3 -D_LARGE_FILES= -D_FILE_OFFSET_BITS= conftest.c >&5 In file included from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, from /usr/include/limits.h:26, from /usr/lib/gcc/x86_64-linux-gnu/14/include/limits.h:210, from /usr/lib/gcc/x86_64-linux-gnu/14/include/syslimits.h:7, from /usr/lib/gcc/x86_64-linux-gnu/14/include/limits.h:34, from conftest.c:50: /usr/include/features.h:398:52: error: operator '&&' has no right operand 398 | #if defined _FILE_OFFSET_BITS && _FILE_OFFSET_BITS == 64 |^~ conftest.c:41:16: error: duplicate 'unsigned' 41 | #define size_t unsigned int |^~~~ conftest.c:41:25: error: two or more data types in declaration specifiers 41 | #define size_t unsigned int | ^~~ Looks like _FILE_OFFSET_BITS is empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2076542/+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 2055239] Please test proposed package
Hello Nobuto, or anyone else affected,
Accepted ubuntu-advantage-tools into bionic-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/34~18.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-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: ubuntu-advantage-tools (Ubuntu Xenial)
Status: New => Fix Committed
** Tags added: verification-needed-xenial
--
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/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
Status in snapd:
New
Status in systemd package in Ubuntu:
Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
In Progress
Status in ubuntu-advantage-tools source package in Xenial:
Fix Committed
Status in ubuntu-advantage-tools source package in Bionic:
Fix Committed
Status in ubuntu-advantage-tools source package in Focal:
Fix Committed
Status in ubuntu-advantage-tools source package in Jammy:
Fix Committed
Status in systemd source package in Noble:
Fix Released
Status in ubuntu-advantage-tools source package in Noble:
Fix Committed
Bug description:
[Impact]
systemd may incorrectly mark units as needing a daemon reload,
therefore unnecessarily printing the warning that a daemon-reload is
needed for the changes to take effect. This is misleading to users,
and particularly visible in cases like running apt update, since there
is an apt hook (/etc/apt/apt.conf.d/20apt-esm-hook.conf) that starts
two systemd services.
[Test Plan]
This bug can be triggered by running systemctl enable/disable on a
non-existent unit. After that, calling systemctl start/status/etc. will show a
false warning
that the unit changed on disk. Hence, to test, simply:
$ systemctl enable somethingthatdefinitelydoesnotexist.service
$ systemctl status systemd-resolved.service
$ apt update
On an effected system, warnings will be shown when calling both
commands after the "enable non-existent unit" step.
[Where problems could occur]
This patch fixes a previous commit by ensuring that the
manager->unit_file_state_outdated flag is set *only* when some
modifications succeeded, but the overall operation failed. In cases
where everything fails, it is not necessary to set the flag.
Since the patch is restricted to this area, any regressions from this
patch would most likely also be related to the NeedDaemonReload
property of units.
[Other information]
The patch is from upstream:
https://github.com/systemd/systemd/pull/32610/commits/d69cba3bfffc7b1e3197e2a34b459db13b1e1cb7#diff-84bbf3361da4139a5620a035ebd24f50a0e4d4ece7952dc2d8b4325e6ebdf6e0L2320
[Original Description]
I recently started seeing the following warning messages when I run
`apt update`.
$ sudo apt update
Warning: The unit file, source configuration file or drop-ins of
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: The unit file, source configuration file or drop-ins of
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload
units.
...
apt-news.service for example is in /lib/systemd/system/apt-
news.service and it's a static file managed by the package. Does the
package maintenance script call systemd related hooks to reload the
config whenever the package gets updated?
$ systemctl cat apt-news.service
# /usr/lib/systemd/system/apt-news.service
# APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
# timely information related to apt updates available to your system.
...
$ dpkg -S /lib/systemd/system/apt-news.service
ubuntu-pro-client: /lib/systemd/system/apt-news.service
ProblemType: BugDistroRelease: Ubuntu 24.04
Packag
[Touch-packages] [Bug 2055239] Please test proposed package
Hello Nobuto, or anyone else affected,
Accepted ubuntu-advantage-tools into xenial-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/34~16.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-
xenial to verification-done-xenial. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-xenial. 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
Status in snapd:
New
Status in systemd package in Ubuntu:
Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
In Progress
Status in ubuntu-advantage-tools source package in Xenial:
Fix Committed
Status in ubuntu-advantage-tools source package in Bionic:
Fix Committed
Status in ubuntu-advantage-tools source package in Focal:
Fix Committed
Status in ubuntu-advantage-tools source package in Jammy:
Fix Committed
Status in systemd source package in Noble:
Fix Released
Status in ubuntu-advantage-tools source package in Noble:
Fix Committed
Bug description:
[Impact]
systemd may incorrectly mark units as needing a daemon reload,
therefore unnecessarily printing the warning that a daemon-reload is
needed for the changes to take effect. This is misleading to users,
and particularly visible in cases like running apt update, since there
is an apt hook (/etc/apt/apt.conf.d/20apt-esm-hook.conf) that starts
two systemd services.
[Test Plan]
This bug can be triggered by running systemctl enable/disable on a
non-existent unit. After that, calling systemctl start/status/etc. will show a
false warning
that the unit changed on disk. Hence, to test, simply:
$ systemctl enable somethingthatdefinitelydoesnotexist.service
$ systemctl status systemd-resolved.service
$ apt update
On an effected system, warnings will be shown when calling both
commands after the "enable non-existent unit" step.
[Where problems could occur]
This patch fixes a previous commit by ensuring that the
manager->unit_file_state_outdated flag is set *only* when some
modifications succeeded, but the overall operation failed. In cases
where everything fails, it is not necessary to set the flag.
Since the patch is restricted to this area, any regressions from this
patch would most likely also be related to the NeedDaemonReload
property of units.
[Other information]
The patch is from upstream:
https://github.com/systemd/systemd/pull/32610/commits/d69cba3bfffc7b1e3197e2a34b459db13b1e1cb7#diff-84bbf3361da4139a5620a035ebd24f50a0e4d4ece7952dc2d8b4325e6ebdf6e0L2320
[Original Description]
I recently started seeing the following warning messages when I run
`apt update`.
$ sudo apt update
Warning: The unit file, source configuration file or drop-ins of
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: The unit file, source configuration file or drop-ins of
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload
units.
...
apt-news.service for example is in /lib/systemd/system/apt-
news.service and it's a static file managed by the package. Does the
package maintenance script call systemd related hooks to reload the
config whenever the package gets updated?
$ systemctl cat apt-news.service
# /usr/lib/systemd/system/apt-news.service
# APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
# timely information related to apt updates available to your system.
...
$ dpkg -S /lib/systemd/system/apt-news.service
ubuntu-pro-client: /lib/systemd/system/apt-news.service
ProblemType: BugDistroRelease: Ubuntu 24.04
Package: ubuntu-pro-client 31.1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKer
[Touch-packages] [Bug 2055239] Please test proposed package
Hello Nobuto, or anyone else affected,
Accepted ubuntu-advantage-tools into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/34~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: ubuntu-advantage-tools (Ubuntu Focal)
Status: New => Fix Committed
** Tags added: verification-needed-focal
--
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/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
Status in snapd:
New
Status in systemd package in Ubuntu:
Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
In Progress
Status in ubuntu-advantage-tools source package in Xenial:
Fix Committed
Status in ubuntu-advantage-tools source package in Bionic:
Fix Committed
Status in ubuntu-advantage-tools source package in Focal:
Fix Committed
Status in ubuntu-advantage-tools source package in Jammy:
Fix Committed
Status in systemd source package in Noble:
Fix Released
Status in ubuntu-advantage-tools source package in Noble:
Fix Committed
Bug description:
[Impact]
systemd may incorrectly mark units as needing a daemon reload,
therefore unnecessarily printing the warning that a daemon-reload is
needed for the changes to take effect. This is misleading to users,
and particularly visible in cases like running apt update, since there
is an apt hook (/etc/apt/apt.conf.d/20apt-esm-hook.conf) that starts
two systemd services.
[Test Plan]
This bug can be triggered by running systemctl enable/disable on a
non-existent unit. After that, calling systemctl start/status/etc. will show a
false warning
that the unit changed on disk. Hence, to test, simply:
$ systemctl enable somethingthatdefinitelydoesnotexist.service
$ systemctl status systemd-resolved.service
$ apt update
On an effected system, warnings will be shown when calling both
commands after the "enable non-existent unit" step.
[Where problems could occur]
This patch fixes a previous commit by ensuring that the
manager->unit_file_state_outdated flag is set *only* when some
modifications succeeded, but the overall operation failed. In cases
where everything fails, it is not necessary to set the flag.
Since the patch is restricted to this area, any regressions from this
patch would most likely also be related to the NeedDaemonReload
property of units.
[Other information]
The patch is from upstream:
https://github.com/systemd/systemd/pull/32610/commits/d69cba3bfffc7b1e3197e2a34b459db13b1e1cb7#diff-84bbf3361da4139a5620a035ebd24f50a0e4d4ece7952dc2d8b4325e6ebdf6e0L2320
[Original Description]
I recently started seeing the following warning messages when I run
`apt update`.
$ sudo apt update
Warning: The unit file, source configuration file or drop-ins of
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: The unit file, source configuration file or drop-ins of
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload
units.
...
apt-news.service for example is in /lib/systemd/system/apt-
news.service and it's a static file managed by the package. Does the
package maintenance script call systemd related hooks to reload the
config whenever the package gets updated?
$ systemctl cat apt-news.service
# /usr/lib/systemd/system/apt-news.service
# APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
# timely information related to apt updates available to your system.
...
$ dpkg -S /lib/systemd/system/apt-news.service
ubuntu-pro-client: /lib/systemd/system/apt-news.service
ProblemType: BugDistroRelease: Ubuntu 24.04
Package: ubu
[Touch-packages] [Bug 2055239] Please test proposed package
Hello Nobuto, or anyone else affected,
Accepted ubuntu-advantage-tools into focal-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/34~20.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-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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: ubuntu-advantage-tools (Ubuntu Bionic)
Status: New => Fix Committed
** Tags added: verification-needed-bionic
--
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/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
Status in snapd:
New
Status in systemd package in Ubuntu:
Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
In Progress
Status in ubuntu-advantage-tools source package in Xenial:
Fix Committed
Status in ubuntu-advantage-tools source package in Bionic:
Fix Committed
Status in ubuntu-advantage-tools source package in Focal:
Fix Committed
Status in ubuntu-advantage-tools source package in Jammy:
Fix Committed
Status in systemd source package in Noble:
Fix Released
Status in ubuntu-advantage-tools source package in Noble:
Fix Committed
Bug description:
[Impact]
systemd may incorrectly mark units as needing a daemon reload,
therefore unnecessarily printing the warning that a daemon-reload is
needed for the changes to take effect. This is misleading to users,
and particularly visible in cases like running apt update, since there
is an apt hook (/etc/apt/apt.conf.d/20apt-esm-hook.conf) that starts
two systemd services.
[Test Plan]
This bug can be triggered by running systemctl enable/disable on a
non-existent unit. After that, calling systemctl start/status/etc. will show a
false warning
that the unit changed on disk. Hence, to test, simply:
$ systemctl enable somethingthatdefinitelydoesnotexist.service
$ systemctl status systemd-resolved.service
$ apt update
On an effected system, warnings will be shown when calling both
commands after the "enable non-existent unit" step.
[Where problems could occur]
This patch fixes a previous commit by ensuring that the
manager->unit_file_state_outdated flag is set *only* when some
modifications succeeded, but the overall operation failed. In cases
where everything fails, it is not necessary to set the flag.
Since the patch is restricted to this area, any regressions from this
patch would most likely also be related to the NeedDaemonReload
property of units.
[Other information]
The patch is from upstream:
https://github.com/systemd/systemd/pull/32610/commits/d69cba3bfffc7b1e3197e2a34b459db13b1e1cb7#diff-84bbf3361da4139a5620a035ebd24f50a0e4d4ece7952dc2d8b4325e6ebdf6e0L2320
[Original Description]
I recently started seeing the following warning messages when I run
`apt update`.
$ sudo apt update
Warning: The unit file, source configuration file or drop-ins of
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: The unit file, source configuration file or drop-ins of
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload
units.
...
apt-news.service for example is in /lib/systemd/system/apt-
news.service and it's a static file managed by the package. Does the
package maintenance script call systemd related hooks to reload the
config whenever the package gets updated?
$ systemctl cat apt-news.service
# /usr/lib/systemd/system/apt-news.service
# APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
# timely information related to apt updates available to your system.
...
$ dpkg -S /lib/systemd/system/apt-news.service
ubuntu-pro-client: /lib/systemd/system/apt-news.service
ProblemType: BugDistroRelease: Ubuntu 24.04
Package: u
[Touch-packages] [Bug 2055239] Re: Warning: The unit file, source configuration file or drop-ins of {apt-news, esm-cache}.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Hello Nobuto, or anyone else affected,
Accepted ubuntu-advantage-tools into noble-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/34~24.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-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. 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: ubuntu-advantage-tools (Ubuntu Noble)
Status: In Progress => Fix Committed
** Tags removed: verification-done verification-done-noble
** Tags added: verification-needed verification-needed-noble
** Changed in: ubuntu-advantage-tools (Ubuntu Jammy)
Status: New => Fix Committed
** Tags added: verification-needed-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
Status in snapd:
New
Status in systemd package in Ubuntu:
Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
In Progress
Status in ubuntu-advantage-tools source package in Xenial:
Fix Committed
Status in ubuntu-advantage-tools source package in Bionic:
Fix Committed
Status in ubuntu-advantage-tools source package in Focal:
Fix Committed
Status in ubuntu-advantage-tools source package in Jammy:
Fix Committed
Status in systemd source package in Noble:
Fix Released
Status in ubuntu-advantage-tools source package in Noble:
Fix Committed
Bug description:
[Impact]
systemd may incorrectly mark units as needing a daemon reload,
therefore unnecessarily printing the warning that a daemon-reload is
needed for the changes to take effect. This is misleading to users,
and particularly visible in cases like running apt update, since there
is an apt hook (/etc/apt/apt.conf.d/20apt-esm-hook.conf) that starts
two systemd services.
[Test Plan]
This bug can be triggered by running systemctl enable/disable on a
non-existent unit. After that, calling systemctl start/status/etc. will show a
false warning
that the unit changed on disk. Hence, to test, simply:
$ systemctl enable somethingthatdefinitelydoesnotexist.service
$ systemctl status systemd-resolved.service
$ apt update
On an effected system, warnings will be shown when calling both
commands after the "enable non-existent unit" step.
[Where problems could occur]
This patch fixes a previous commit by ensuring that the
manager->unit_file_state_outdated flag is set *only* when some
modifications succeeded, but the overall operation failed. In cases
where everything fails, it is not necessary to set the flag.
Since the patch is restricted to this area, any regressions from this
patch would most likely also be related to the NeedDaemonReload
property of units.
[Other information]
The patch is from upstream:
https://github.com/systemd/systemd/pull/32610/commits/d69cba3bfffc7b1e3197e2a34b459db13b1e1cb7#diff-84bbf3361da4139a5620a035ebd24f50a0e4d4ece7952dc2d8b4325e6ebdf6e0L2320
[Original Description]
I recently started seeing the following warning messages when I run
`apt update`.
$ sudo apt update
Warning: The unit file, source configuration file or drop-ins of
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: The unit file, source configuration file or drop-ins of
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload
units.
...
apt-news.service for example is in /lib/systemd/system/apt-
news.service and it's a static file managed by the package. Does the
package maintenance script call systemd related hooks to reload the
config whenever the package gets updated?
$ systemctl cat apt-news.service
# /usr/lib/systemd/system/apt-news.service
# APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
# timely information relat
[Touch-packages] [Bug 2075332] Re: FTBFS with gcc-14
This migrated.
** Changed in: cyrus-sasl2 (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 cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/2075332
Title:
FTBFS with gcc-14
Status in cyrus-sasl2 package in Ubuntu:
Fix Released
Status in cyrus-sasl2 package in Debian:
Fix Released
Bug description:
https://launchpadlibrarian.net/741628620/buildlog_ubuntu-oracular-
amd64.cyrus-sasl2_2.1.28+dfsg1-6_BUILDING.txt.gz
In file included from ../../include/hmac-md5.h:7,
from ../../include/saslplug.h:11,
from ../../lib/common.c:60:
/usr/include/openssl/md5.h:49:27: note: declared here
49 | OSSL_DEPRECATEDIN_3_0 int MD5_Init(MD5_CTX *c);
| ^~~~
../../lib/common.c:2034:19: error: assignment to ‘void (*)(MD5_CTX *)’ {aka
‘void (*)(struct MD5state_st *)’} from incompatible pointer type ‘int
(*)(MD5_CTX *)’ {aka ‘int (*)(struct MD5state_st *)’}
[-Wincompatible-pointer-types]
2034 | utils->MD5Init = &MD5_Init;
| ^
../../lib/common.c:2035:3: warning: ‘MD5_Update’ is deprecated: Since OpenSSL
3.0 [-Wdeprecated-declarations]
2035 | utils->MD5Update= &MD5_Update;
| ^
/usr/include/openssl/md5.h:50:27: note: declared here
50 | OSSL_DEPRECATEDIN_3_0 int MD5_Update(MD5_CTX *c, const void *data,
size_t len);
| ^~
../../lib/common.c:2035:19: error: assignment to ‘void (*)(MD5_CTX *, const
unsigned char *, unsigned int)’ {aka ‘void (*)(struct MD5state_st *, const
unsigned char *, unsigned int)’} from incompatible pointer type ‘int
(*)(MD5_CTX *, const void *, size_t)’ {aka ‘int (*)(struct MD5state_st *, const
void *, long unsigned int)’} [-Wincompatible-pointer-types]
2035 | utils->MD5Update= &MD5_Update;
| ^
../../lib/common.c:2036:3: warning: ‘MD5_Final’ is deprecated: Since OpenSSL
3.0 [-Wdeprecated-declarations]
2036 | utils->MD5Final = &MD5_Final;
| ^
/usr/include/openssl/md5.h:51:27: note: declared here
51 | OSSL_DEPRECATEDIN_3_0 int MD5_Final(unsigned char *md, MD5_CTX *c);
| ^
../../lib/common.c:2036:19: error: assignment to ‘void (*)(unsigned char *,
MD5_CTX *)’ {aka ‘void (*)(unsigned char *, struct MD5state_st *)’} from
incompatible pointer type ‘int (*)(unsigned char *, MD5_CTX *)’ {aka ‘int
(*)(unsigned char *, struct MD5state_st *)’} [-Wincompatible-pointer-types]
2036 | utils->MD5Final = &MD5_Final;
| ^
../../lib/common.c: In function ‘_sasl_find_verifyfile_callback’:
../../lib/common.c:2165:5: warning: cast between incompatible function types
from ‘int (*)(void *, char *, int)’ to ‘int (*)(void)’ [-Wcast-function-type]
2165 | (sasl_callback_ft)&_sasl_verifyfile,
| ^
make[5]: *** [Makefile:608: common.lo] Error 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2075332/+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 2078851] Re: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd
I just synced 2.1.28+dfsg1-8 from debian, which contains the fix. ** Changed in: cyrus-sasl2 (Ubuntu Oracular) Status: Triaged => Fix Committed ** Tags added: bite-size -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/2078851 Title: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd Status in cyrus-sasl2 package in Ubuntu: Fix Committed Status in cyrus-sasl2 source package in Noble: Triaged Status in cyrus-sasl2 source package in Oracular: Fix Committed Bug description: Folder group permission of /var/spool/postfix/var/run/saslauthd gets reset to "root" (should be "sasl") every time saslauthd gets restarted. This worked fine before upgrading from 22.04 to 24.04 My automated workaround currently is this crontab (root) entry: */1 * * * * /usr/bin/chgrp sasl /var/spool/postfix/var/run/saslauthd 2>&1 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: postfix 3.8.6-1build2 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Sep 3 19:52:59 2024 SourcePackage: postfix UpgradeStatus: Upgraded to noble on 2024-08-31 (3 days ago) mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2078851/+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 2078720] Please test proposed package
Hello Ankush, or anyone else affected, Accepted apt into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/2.4.13 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 apt in Ubuntu. https://bugs.launchpad.net/bugs/2078720 Title: Upgrading from jammy to noble results in a linux-headers package being in a broken state Status in apt package in Ubuntu: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-gcp package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Fix Committed Status in apt source package in Jammy: Fix Committed Status in linux-aws source package in Jammy: New Status in linux-gcp source package in Jammy: New Status in apt source package in Noble: New Status in linux-aws source package in Noble: New Status in linux-gcp source package in Noble: New Status in ubuntu-release-upgrader source package in Noble: In Progress Bug description: (For APT SRU versioning, see https://wiki.ubuntu.com/AptUpdates) [Impact] Obsolete packages can be removed despite still having reverse dependencies installed, for example: Now that 24.04.1 has been released, 22.04 users are encouraged to upgrade to 24.04 via the `do-release-upgrade` command. This issue was seen whilst testing this upgrade path. Upgrading and later rebooting a jammy GCP instance results in `linux-headers-6.5.0-1025-gcp` being a broken state. ``` $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-6.5.0-1025-gcp : Depends: linux-gcp-6.5-headers-6.5.0-1025 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` `linux-gcp-6.5-headers-6.5.0-1025` is a dependency of `linux-image-6.5.0-1025-gcp` which is also not removed during the upgrade. ``` $ apt-cache rdepends linux-headers-6.5.0-1025-gcp linux-headers-6.5.0-1025-gcp Reverse Depends: linux-image-6.5.0-1025-gcp $ apt-cache rdepends linux-image-6.5.0-1025-gcp linux-image-6.5.0-1025-gcp Reverse Depends: ``` Running `apt --fix-broken install` resolves the error. ``` $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following packages will be REMOVED: linux-headers-6.5.0-1025-gcp 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 27.9 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 83770 files and directories currently installed.) Removing linux-headers-6.5.0-1025-gcp (6.5.0-1025.27~22.04.1) ... $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ``` This issue was also observed after upgrading a jammy AWS instance to noble. ``` $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-6.5.0-1024-aws : Depends: linux-aws-6.5-headers-6.5.0-1024 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` [Test plan] ## Jammy APT verification To prepare the VMs, follow the following scheme: $ lxc launch ubuntu:jammy jammy-to-noble --vm If using lxc shell or exec to connect to it, also perform the step b
[Touch-packages] [Bug 2078720] Re: Upgrading from jammy to noble results in a linux-headers package being in a broken state
I was able to reproduce this in jammy lxd VM, and tweaked the test plan a bit. I'm going to accept this into jammy-proposed in order to allow for testing to begin quickly, but we still need the noble and oracular uploads as well. The APT noble test plan could also use some refinement, there are still too many unknowns there, and not clear steps as to what should happen and what shouldn't. ** Description changed: (For APT SRU versioning, see https://wiki.ubuntu.com/AptUpdates) [Impact] Obsolete packages can be removed despite still having reverse dependencies installed, for example: Now that 24.04.1 has been released, 22.04 users are encouraged to upgrade to 24.04 via the `do-release-upgrade` command. This issue was seen whilst testing this upgrade path. Upgrading and later rebooting a jammy GCP instance results in `linux-headers-6.5.0-1025-gcp` being a broken state. ``` $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-6.5.0-1025-gcp : Depends: linux-gcp-6.5-headers-6.5.0-1025 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` `linux-gcp-6.5-headers-6.5.0-1025` is a dependency of `linux-image-6.5.0-1025-gcp` which is also not removed during the upgrade. ``` $ apt-cache rdepends linux-headers-6.5.0-1025-gcp linux-headers-6.5.0-1025-gcp Reverse Depends: linux-image-6.5.0-1025-gcp $ apt-cache rdepends linux-image-6.5.0-1025-gcp linux-image-6.5.0-1025-gcp Reverse Depends: ``` Running `apt --fix-broken install` resolves the error. ``` $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following packages will be REMOVED: linux-headers-6.5.0-1025-gcp 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 27.9 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 83770 files and directories currently installed.) Removing linux-headers-6.5.0-1025-gcp (6.5.0-1025.27~22.04.1) ... $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ``` This issue was also observed after upgrading a jammy AWS instance to noble. ``` $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-6.5.0-1024-aws : Depends: linux-aws-6.5-headers-6.5.0-1024 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` [Test plan] ## Jammy APT verification To prepare the VMs, follow the following scheme: $ lxc launch ubuntu:jammy jammy-to-noble --vm - $ lxc exec jammy-to-noble apt-mark lxd-agent-launcher # otherwise it resets - To validate the apt change on jammy, + If using lxc shell or exec to connect to it, also perform the step + below: - Edit /etc/update-manager/release-upgrades and set Prompt to "normal" - (since release upgrades to noble via the lts prompt are temporarily - blocked due to this bug) + $ lxc exec jammy-to-noble apt-mark lxd-agent-launcher # otherwise it + resets + + + On this jammy VM, edit /etc/update-manager/release-upgrades and set Prompt to "normal" (since release upgrades to noble via the lts prompt are temporarily blocked due to this bug) $ sudo do-release-upgrade After the reboot at the end, in the rebooted system, issue: $ sudo apt upgrade With the bug present, you will get an error like this: $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: - linux-headers-5.15.0-1065-kvm : Depends: linux-kvm-headers-5.15.0-1065 but it is not installable + linux-headers-5.15.0-1065-kvm : Depends: linux-kvm-headers-5.15.0-1065 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ## Noble APT verification To validate the APT change on noble, we must rely on the test suite as we won't have a noble->oracular upgrade bug causing it, most likely. To validate an ubuntu-release-upgrader change, instead run: ubuntu@jammy-to-noble$ do-release-upgrade -p ubuntu@mantic-to-noble$ do-release-upgrade -p [Where problems could occur: APT SRU]
[Touch-packages] [Bug 2078720] Re: Upgrading from jammy to noble results in a linux-headers package being in a broken state
** Description changed: (For APT SRU versioning, see https://wiki.ubuntu.com/AptUpdates) [Impact] Obsolete packages can be removed despite still having reverse dependencies installed, for example: Now that 24.04.1 has been released, 22.04 users are encouraged to upgrade to 24.04 via the `do-release-upgrade` command. This issue was seen whilst testing this upgrade path. Upgrading and later rebooting a jammy GCP instance results in `linux-headers-6.5.0-1025-gcp` being a broken state. ``` $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-6.5.0-1025-gcp : Depends: linux-gcp-6.5-headers-6.5.0-1025 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` `linux-gcp-6.5-headers-6.5.0-1025` is a dependency of `linux-image-6.5.0-1025-gcp` which is also not removed during the upgrade. ``` $ apt-cache rdepends linux-headers-6.5.0-1025-gcp linux-headers-6.5.0-1025-gcp Reverse Depends: linux-image-6.5.0-1025-gcp $ apt-cache rdepends linux-image-6.5.0-1025-gcp linux-image-6.5.0-1025-gcp Reverse Depends: ``` Running `apt --fix-broken install` resolves the error. ``` $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following packages will be REMOVED: linux-headers-6.5.0-1025-gcp 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 27.9 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 83770 files and directories currently installed.) Removing linux-headers-6.5.0-1025-gcp (6.5.0-1025.27~22.04.1) ... $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ``` This issue was also observed after upgrading a jammy AWS instance to noble. ``` $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-6.5.0-1024-aws : Depends: linux-aws-6.5-headers-6.5.0-1024 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` [Test plan] + ## Jammy APT verification + To prepare the VMs, follow the following scheme: $ lxc launch ubuntu:jammy jammy-to-noble --vm $ lxc exec jammy-to-noble apt-mark lxd-agent-launcher # otherwise it resets To validate the apt change on jammy, - ubuntu@jammy-to-noble$ add-apt-repository -p proposed - ubuntu@jammy-to-noble$ apt install libapt-pkg6.0 # to upgrade libapt-pkg6.0 - ubuntu@jammy-to-noble$ do-release-upgrade + Edit /etc/update-manager/release-upgrades and set Prompt to "normal" + (since release upgrades to noble via the lts prompt are temporarily + blocked due to this bug) + + $ sudo do-release-upgrade + + After the reboot at the end, in the rebooted system, issue: + + $ sudo apt upgrade + + With the bug present, you will get an error like this: + $ sudo apt upgrade + Reading package lists... Done + Building dependency tree... Done + Reading state information... Done + You might want to run 'apt --fix-broken install' to correct these. + The following packages have unmet dependencies: + linux-headers-5.15.0-1065-kvm : Depends: linux-kvm-headers-5.15.0-1065 but it is not installable + E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). + + + ## Noble APT verification To validate the APT change on noble, we must rely on the test suite as we won't have a noble->oracular upgrade bug causing it, most likely. To validate an ubuntu-release-upgrader change, instead run: ubuntu@jammy-to-noble$ do-release-upgrade -p ubuntu@mantic-to-noble$ do-release-upgrade -p [Where problems could occur: APT SRU] For the APT change, the function in question is used in a small number of places: In APT library: - In the `upgrade` command and library function. Removals are already undone there before calling it so we never reach the new code path. - In the phased update implementation, during dist-upgrade. I expect a failure is lurking there that is fixed by this, but I haven't been able to write a reproducer to trigger it just yet. In aptitude: - The function is wrapped, but the wrapper never called In QApt: - QApt seems to rely on it for upgrading and doesn't seem to have any error checking of the return value. I expect it will read the er
[Touch-packages] [Bug 2078720] Re: Upgrading from jammy to noble results in a linux-headers package being in a broken state
** Description changed: (For APT SRU versioning, see https://wiki.ubuntu.com/AptUpdates) [Impact] Obsolete packages can be removed despite still having reverse dependencies installed, for example: Now that 24.04.1 has been released, 22.04 users are encouraged to upgrade to 24.04 via the `do-release-upgrade` command. This issue was seen whilst testing this upgrade path. Upgrading and later rebooting a jammy GCP instance results in `linux-headers-6.5.0-1025-gcp` being a broken state. ``` $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-6.5.0-1025-gcp : Depends: linux-gcp-6.5-headers-6.5.0-1025 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` `linux-gcp-6.5-headers-6.5.0-1025` is a dependency of `linux-image-6.5.0-1025-gcp` which is also not removed during the upgrade. ``` $ apt-cache rdepends linux-headers-6.5.0-1025-gcp linux-headers-6.5.0-1025-gcp Reverse Depends: linux-image-6.5.0-1025-gcp $ apt-cache rdepends linux-image-6.5.0-1025-gcp linux-image-6.5.0-1025-gcp Reverse Depends: ``` Running `apt --fix-broken install` resolves the error. ``` $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following packages will be REMOVED: linux-headers-6.5.0-1025-gcp 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 27.9 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 83770 files and directories currently installed.) Removing linux-headers-6.5.0-1025-gcp (6.5.0-1025.27~22.04.1) ... $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ``` This issue was also observed after upgrading a jammy AWS instance to noble. ``` $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-6.5.0-1024-aws : Depends: linux-aws-6.5-headers-6.5.0-1024 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` [Test plan] To prepare the VMs, follow the following scheme: - $ lxc launch ubuntu:jammy jammy-to-noble + $ lxc launch ubuntu:jammy jammy-to-noble --vm $ lxc exec jammy-to-noble apt-mark lxd-agent-launcher # otherwise it resets To validate the apt change on jammy, ubuntu@jammy-to-noble$ add-apt-repository -p proposed ubuntu@jammy-to-noble$ apt install libapt-pkg6.0 # to upgrade libapt-pkg6.0 ubuntu@jammy-to-noble$ do-release-upgrade To validate the APT change on noble, we must rely on the test suite as we won't have a noble->oracular upgrade bug causing it, most likely. To validate an ubuntu-release-upgrader change, instead run: ubuntu@jammy-to-noble$ do-release-upgrade -p ubuntu@mantic-to-noble$ do-release-upgrade -p [Where problems could occur: APT SRU] For the APT change, the function in question is used in a small number of places: In APT library: - In the `upgrade` command and library function. Removals are already undone there before calling it so we never reach the new code path. - In the phased update implementation, during dist-upgrade. I expect a failure is lurking there that is fixed by this, but I haven't been able to write a reproducer to trigger it just yet. In aptitude: - The function is wrapped, but the wrapper never called In QApt: - QApt seems to rely on it for upgrading and doesn't seem to have any error checking of the return value. I expect it will read the error [Where problems could occur: u-r-u SRU] Upgrades will now result in a consistent state, but may spend hours searching for obsolete software again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2078720 Title: Upgrading from jammy to noble results in a linux-headers package being in a broken state Status in apt package in Ubuntu: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-gcp package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Fix Committed Status in apt source package in Jammy: In Progress Status in linux-aws source package in Jammy: New Status in linux-gcp source package in Jammy: New Status in a
[Touch-packages] [Bug 1769297] Update Released
The verification of the Stable Release Update for initramfs-tools has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1769297
Title:
resume from hibernation broken when resume image is autodetected
(UUID= syntax used)
Status in initramfs-tools package in Ubuntu:
Fix Released
Status in initramfs-tools source package in Noble:
Fix Committed
Bug description:
[ Impact ]
I found a reason of non-functioning resume from hibernation when
resume partition/file is autodetected by intiramfs hook
/usr/share/initramfs-tools/hooks/resume.
Here is the scenario:
1) hook /usr/share/initramfs-tools/hooks/resume creates config
conf/conf.d/zz-resume-auto saved in initrd image, containing one variable:
RESUME=UUID=106238b0-707d-4422-866d-a7534da50702 in my case
2) during boot init script sets 'resume' variable to 'RESUME' value
from conf/conf.d/zz-resume-auto, then it executes local-premount
scripts including local-premount/resume
3) resuming script local-premount/resume
(/usr/share/initramfs-tools/scripts/local-premount/resume) tries to get resume
device major-minor numbers by these lines:
DEV=$(readlink ${resume})
DEV=/sys/class/block/${DEV##*/}/dev
if [ -r "$DEV" ]; then
read MAJMIN < "$DEV"
fi
4) next check fails and resume process silently aborts:
if [ -z "$MAJMIN" ]; then
exit 1
fi
Resuming script fails to get device major-minor because
resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- it's not resolved
into device path in init script.
Commonly mentioned workaround is to explicitly specify kernel
parameter resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- only in
this case init script resolves it to device path.
[ Test Plan ]
1. hibernate: `sudo systemctl hibernate`
2. resume from hibernate
3. `cat /sys/power/resume` should contain the major-minor of the swap
[ Other Info ]
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3
Uname: Linux 4.16.6-041606-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat May 5 11:32:31 2018
InstallationDate: Installed on 2018-03-27 (38 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
PackageArchitecture: all
SourcePackage: initramfs-tools
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769297/+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 2003027] Re: fq_codel qdisc compiled but not enabled on 22.10
This failed to build on arm64, whereas the previous version built, so it's a regression. Can somebody troubleshoot that failure please? Seems like a build-time test failure, so for now I triggered a new build attempt. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/2003027 Title: fq_codel qdisc compiled but not enabled on 22.10 Status in Ubuntu: Fix Released Status in procps package in Ubuntu: Fix Released Status in The Noble Numbat: Confirmed Status in procps source package in Noble: Fix Committed Status in The Oracular Oriole: Fix Released Status in procps source package in Oracular: Fix Released Bug description: [ Impact ] Starting with Ubuntu 22.10, the default qdisc regressed to pfifo_fast. This is due to a change we merged from Debian, removing systemd's /usr/lib/50-default.conf file. pfifo_fast does not prevent bufferbloat issues, severely degrading networking performance on Ubuntu systems. [ Test Plan ] On an Ubuntu VM, check that net.core.default_qdisc is set to 'fq_codel'. `tc qdisc show` should also confirm fq_codel is being used. halves@noble-vm:~$ sysctl net.core.default_qdisc net.core.default_qdisc = fq_codel halves@noble-vm:~$ tc qdisc show qdisc noqueue 0: dev lo root refcnt 2 qdisc mq 0: dev enp5s0 root qdisc fq_codel 0: dev enp5s0 parent :1 limit 10240p flows 1024 quantum 1514 target 5ms interval 100ms memory_limit 32Mb ecn drop_batch 64 [ Where Problems Could Occur ] Users relying on the default pfifo_fast qdisc could see different networking behavior. Although fq_codel should be an across-the-board improvement over pfifo_fast, we could monitor network latency stats and throughput to make sure no weird regressions arise from the qdisc scheduler. [ Other Info ] Instead of adding a sysctl.conf file, Debian has decided to change their default kernel configs to use fq_codel. This has the disadvantage of being "hidden" from end users, instead of being a queryable setting in e.g. /etc/sysctl.d/, and all kernel documentation still refers to pfifo_fast as being the default. Systemd's /usr/lib/50-default.conf file includes a lot of other settings that are either overruled elsewhere (e.g. from procps) or are entirely missing from our stable releases. Introducing a diff from Debian to ship this file only for the net.core.default_qdisc changes seems excessive, so having a dedicated place under procps where other similar toggles are already present seems like the more appropriate solution. -- [ Original Description ] fq_codel has been the default in ubuntu since #1436945 It is also now the default in debian. Somewhere between 22.04 and 22.10 though, it stopped being enabled by systemd? (it used to be enabled there via a sysctl), and thus 22.10 (I tried both ubuntu server and ubuntu studio) doesn't have it on. I rather *immediately* noticed this huge regression (I run my ethernet at 100Mbit, and thus immediately saw 400+ms latency) - and I hope it can be fixed in the next release? it can also be made the default via compiling it into the kernel as a kernel default. Aggh! death to fifos! root@localhost:~# sysctl -a | grep qdisc net.core.default_qdisc = pfifo_fast disc pfifo_fast 0: dev eth0 parent :1 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 Sent 5250 bytes 53 pkt (dropped 0, overlimits 0 requeues 0) backlog 0b 0p requeues 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2003027/+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 2078356] Re: python3 preinst failure to run pre-rtupdate hooks
We tried multiple things to reproduce this bug, to no avail.
My last attempt was to inject an actual error in one of the
/usr/share/python3/runtime.d/*.rtupdate scripts to see how the upgrade (or
reinstall) would behave, and it does as expected:
Preparing to unpack .../python3_3.12.3-0ubuntu2_amd64.deb ...
running python pre-rtupdate hooks for python3.12...
stdout: andreas was here
stderr: andreas was here
error running python pre-rtupdate hook byobu
running python failed-pre-rtupdate hook byobu
stdout: andreas was here
stderr: andreas was here
dpkg: error processing archive
/var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack):
new python3 package pre-installation script subprocess returned error exit
status 1
Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ...
Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ...
Errors were encountered while processing:
/var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
We can see that:
a) pre-rtupdate hooks are run ("running python pre-rtupdate hooks for
python3.12...")
b) stdout and stderr of the failing rdupdate script are shown ("andreas was
here")
c) there is an error message saying exactly which hook failed ("error running
python pre-rtupdate hook byobu")
From the logs we have seen so far attached to this bug, we only get (a)
in them. Not (b) or (c).
I also tried release upgrades from jammy to noble, desktop and server,
and python upgrades in ubuntu desktop noble, and also couldn't reproduce
the error.
I'll mark this bug as incomplete reflecting the status that we have
tried many different ways to understand and reproduce this bug, but
haven't been successful yet.
** Changed in: python3-defaults (Ubuntu)
Status: Confirmed => Incomplete
--
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/2078356
Title:
python3 preinst failure to run pre-rtupdate hooks
Status in python3-defaults package in Ubuntu:
Incomplete
Bug description:
# README first
If you are hit by this bug, please provide the information asked in
the comment #53 further down in this page, thanks
[ Original Description ]
running python pre-rtupdate hooks for python3.12...
dpkg: error processing archive
/var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack):
new python3 package pre-installation script subprocess returned error exit
status 3
Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ...
Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ...
Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ...
Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ...
Errors were encountered while processing:
/var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: python3 3.12.3-0ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
Uname: Linux 6.8.0-41-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 29 10:52:19 2024
InstallationDate: Installed on 2024-07-13 (47 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
SourcePackage: python3-defaults
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078600] Re: package python3-dev 3.10.6-1~22.04.1 failed to install/upgrade: 依赖关系问题 - 仍未被配置
Thanks for reporting this. Can you please run these commands and show the output: apt-cache policy asymptote python3 python3-minimal dpkg -L asymptote sudo apt -f install -- 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/2078600 Title: package python3-dev 3.10.6-1~22.04.1 failed to install/upgrade: 依赖关系问题 - 仍未被配置 Status in python3-defaults package in Ubuntu: New Bug description: when my pc start,the bug start ProblemType: Package DistroRelease: Ubuntu 22.04 Package: python3-dev 3.10.6-1~22.04.1 ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12 Uname: Linux 6.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Sep 1 08:59:13 2024 DpkgHistoryLog: Start-Date: 2024-09-01 08:58:07 Commandline: aptdaemon role='role-commit-packages' sender=':1.139' Upgrade: libext2fs2:amd64 (1.46.5-2ubuntu1.1, 1.46.5-2ubuntu1.2), libpython3-dev:amd64 (3.10.6-1~22.04, 3.10.6-1~22.04.1), python3-minimal:amd64 (3.10.6-1~22.04, 3.10.6-1~22.04.1), deepin-wine-helper:amd64 (5.3.16-1, 5.3.20-1), python3:amd64 (3.10.6-1~22.04, 3.10.6-1~22.04.1), libcom-err2:amd64 (1.46.5-2ubuntu1.1, 1.46.5-2ubuntu1.2), libcom-err2:i386 (1.46.5-2ubuntu1.1, 1.46.5-2ubuntu1.2), ubuntu-pro-client-l10n:amd64 (32.3.1~22.04, 33.2~22.04), python3-dev:amd64 (3.10.6-1~22.04, 3.10.6-1~22.04.1), libpython3-stdlib:amd64 (3.10.6-1~22.04, 3.10.6-1~22.04.1), logsave:amd64 (1.46.5-2ubuntu1.1, 1.46.5-2ubuntu1.2), ubuntu-advantage-tools:amd64 (32.3.1~22.04, 33.2~22.04), libss2:amd64 (1.46.5-2ubuntu1.1, 1.46.5-2ubuntu1.2), microsoft-edge-stable:amd64 (127.0.2651.105-1, 128.0.2739.54-1), e2fsprogs:amd64 (1.46.5-2ubuntu1.1, 1.46.5-2ubuntu1.2), ubuntu-pro-client:amd64 (32.3.1~22.04, 33.2~22.04) ErrorMessage: 依赖关系问题 - 仍未被配置 InstallationDate: Installed on 2024-04-09 (145 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) Python3Details: /usr/bin/python3.10, Python 3.10.12, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.12 SourcePackage: python3-defaults Title: package python3-dev 3.10.6-1~22.04.1 failed to install/upgrade: 依赖关系问题 - 仍未被配置 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078600/+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 2078356] Re: python3 preinst failure to run pre-rtupdate hooks
** Description changed: + # README first + + If you are hit by this bug, please provide the information asked in the + comment + https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/comments/53 + further down in this page, thanks + + + [ Original Description ] + running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): - new python3 package pre-installation script subprocess returned error exit status 3 + new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: - /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb + /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: # README first If you are hit by this bug, please provide the information asked in the - comment - https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/comments/53 - further down in this page, thanks - + comment comment #53 further down in this page, thanks [ Original Description ] running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: # README first If you are hit by this bug, please provide the information asked in the - comment comment #53 further down in this page, thanks + comment #53 further down in this page, thanks [ Original Description ] running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architec
[Touch-packages] [Bug 2078356] Re: python3 preinst failure to run pre-rtupdate hooks
> This bug has now affected (infected?) my third server which is running 22.04.4. Could you please get me the information from comment #53 about that system? -- 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/2078356 Title: python3 preinst failure to run pre-rtupdate hooks Status in python3-defaults package in Ubuntu: Confirmed Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2075337] Re: [SRU] py3clean fails when using alternate character set
Potential regression-update in https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in ubuntu-advantage-tools package in Ubuntu: New Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Released Status in dh-python source package in Noble: Invalid Status in python3-defaults source package in Noble: Fix Released Status in ubuntu-advantage-tools source package in Noble: Fix Released Bug description: [ Impact ] With the current version of python3-defaults in jammy and noble, packages which utilize py3compile and py3clean in their maintscripts (which is more or less any package which includes Python modules), and which also are affected by diversions installed by dpkg-divert, will fail to install/upgrade/remove on systems with non-UTF-8 locales, which include non-ASCII characters in their localized dpkg -L messages (and which therefore produce output that is not valid UTF-8). As this has the potential to break apt upgrade, the impact is quite severe (especially if this occurs during a dist-upgrade). However, the scope is probably *fairly* limited given this only affects systems with non-UTF-8 locales (something that has not been the default for many years), and which produce non-ASCII output (e.g. French characters with diacriticals) in their localized messages for dpkg -L. [ Rectification Plan ] Firstly, python3-defaults must be patched in oracular, noble, and jammy. doko has uploaded the fix upstream and synced this to oracular. Benjamin has sponsored the noble and jammy SRUs. Next, affected packages must be patched to include a "Breaks" line on earlier versions of python3-minimal (the python3-defaults binary package containing py3clean and py3compile). Packages which install Python modules are easily selected, but those affected by diversions are (computationally) impossible to select (see comment 18 for details). Thus, determining the set of affected packages was non-trivial, but Benjamin has kindly produced such a list by empirical means (see comment 24). These will be added to the ticket as they are uploaded. [ Known affected packages ] ``` $ for section in main restricted universe multiverse; do echo "noble $section:"; sqlite3 affected.sqlite3 "SELECT package, source FROM package_affected WHERE section = '$section' and install_affected = 1 AND (remove_affected = 1 OR remove_affected ISNULL) ORDER BY package;"; echo; done noble main: cloud-init|cloud-init nvme-stas|nvme-stas python3-rtslib-fb|python-rtslib-fb targetcli-fb|targetcli-fb ubiquity|ubiquity ubiquity-frontend-debconf|ubiquity ubiquity-frontend-gtk|ubiquity ubuntu-drivers-common|ubuntu-drivers-common ubuntu-pro-client|ubuntu-advantage-tools walinuxagent|walinuxagent noble restricted: noble universe: a2d|a2d apertium-apy|apertium-apy blueman|blueman borgmatic|borgmatic condor|condor cpupower-gui|cpupower-gui debomatic|debomatic dell-recovery|dell-recovery deluge-web|deluge depthcharge-tools|depthcharge-tools dhcpy6d|dhcpy6d dkimpy-milter|dkimpy-milter fenrir|fenrir galileo|galileo glances|glances graphite-carbon|graphite-carbon grokmirror|grokmirror guerillabackup|guerillabackup ionit|ionit jupyterhub|jupyterhub liquidctl|liquidctl localslackirc|localslackirc logdata-anomaly-miner|logdata-anomaly-miner lomiri|lomiri mailman3|mailman3 mailman3-full|mailman3 matrix-sydent|matrix-sydent mom|mom mopidy|mopidy mpd-sima|mpd-sima nordugrid-arc-arex|nordugrid-arc notus-scanner|notus-scanner nrpe-ng|nrpe-ng onionprobe|onionprobe openscap-daemon|openscap-daemon ospd-openvas|ospd-openvas pagekite|pagekite pagure|pagure pagure-ev-server|pagure pagure-milters|pagure pglistener|pglistener policyd-rate-limit|policyd-rate-limit postfix-mta-sts-resolver|postfix-mta-sts-resolver powa-collector|powa-collector prelude-correlator|prelude-correlator prometheus-pgbouncer-exporter|prometheus-pgbouncer-exporter prometheus-xmpp-alerts|prometheus-xmpp-alerts pyroman|pyroman python3-autopilot|autopilot python3-btchip|btchip-python python3-pyro5|pyro5 qweborf|weborf razercfg|razercfg sgt-launcher|sgt-launcher sms4you|sms4you supervisor|supervisor syncplay-server|syncplay timekpr-next|timekpr
[Touch-packages] [Bug 2078356] Re: python3 preinst failure to run pre-rtupdate hooks
I'm gonna tag this with regression-update, even though it's not yet clear what is going on, but clearly it is affecting some users (bug heat is 28 at the moment). Potential regression-update of https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2075337 ** Tags added: regression-update -- 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/2078356 Title: python3 preinst failure to run pre-rtupdate hooks Status in python3-defaults package in Ubuntu: Confirmed Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 preinst failure to run pre-rtupdate hooks
I tried even an ubuntu desktop, I still cannot reproduce this. To those affected, please provide the output of these commands, if you haven't already: - apt-cache policy python3 libpython3-stdlib python3-gdbm python3-lib2to3 python3-minimal - locale - dpkg -S /usr/share/python3/runtime.d/* - cat /var/lib/dpkg/info/python3.preinst - dpkg -S $(which py3compile) $(which py3clean) - sudo apt install -f -- 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/2078356 Title: python3 preinst failure to run pre-rtupdate hooks Status in python3-defaults package in Ubuntu: Confirmed Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 preinst failure to run pre-rtupdate hooks
** Summary changed: - python3 upgrade has unmet dependencies + python3 preinst failure to run pre-rtupdate hooks -- 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/2078356 Title: python3 preinst failure to run pre-rtupdate hooks Status in python3-defaults package in Ubuntu: Confirmed Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078489] Re: package python3 3.12.3-0ubuntu1 failed to install/upgrade: new python3 package pre-installation script subprocess returned error exit status 3
*** This bug is a duplicate of bug 2078356 *** https://bugs.launchpad.net/bugs/2078356 ** This bug has been marked a duplicate of bug 2078356 python3 upgrade has unmet dependencies -- 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/2078489 Title: package python3 3.12.3-0ubuntu1 failed to install/upgrade: new python3 package pre-installation script subprocess returned error exit status 3 Status in python3-defaults package in Ubuntu: Confirmed Bug description: After system rquired reboot to install upgrades ProblemType: Package DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 AptOrdering: python3-minimal:amd64: Install python3-minimal:amd64: Configure python3:amd64: Install libpython3-stdlib:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Aug 29 18:48:06 2024 DpkgTerminalLog: Preparing to unpack .../python3_3.12.3-0ubuntu2_amd64.deb ... running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 DuplicateSignature: package:python3:3.12.3-0ubuntu1 Preparing to unpack .../python3_3.12.3-0ubuntu2_amd64.deb ... running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 ErrorMessage: new python3 package pre-installation script subprocess returned error exit status 3 InstallationDate: Installed on 2024-07-13 (48 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.6ubuntu6.1 apt 2.7.14build2 SourcePackage: python3-defaults Title: package python3 3.12.3-0ubuntu1 failed to install/upgrade: new python3 package pre-installation script subprocess returned error exit status 3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078489/+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 2078356] Re: python3 upgrade has unmet dependencies
It doesn't look like it's the update itself, because as can be seen in https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/comments/33, reinstalling the non-update version also triggered it. I'm starting to think it could be one of the /usr/share/python3/runtime.d/*.rtupdate scripts that get executed, but I installed the same ones as listed in https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/comments/6 and still couldn't reproduce the bug. -- 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/2078356 Title: python3 preinst failure to run pre-rtupdate hooks Status in python3-defaults package in Ubuntu: Confirmed Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
You don't have /var/log/apt/history.log nor /var/log/apt/term.log? Just the rotated .1 versions? -- 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/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
Oh, and /var/log/dpkg.log too please -- 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/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
Ok, maybe the script is being called with redirection to a log file. That doesn't explain why you didn't have the script in place, but let's check some logs. Could you please attach the following to this bug: /var/log/apt/*.log /var/log/syslog output of "dmesg -T" -- 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/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
It's just not being executed, because we are not seeing the "set -x" output (which would be very noisy). Did you do something different to this system that you can recall? Install python from source, or packages from debian instead of ubuntu, or anywhere else? That kind of thing? -- 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/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
And there is no /var/lib/dpkg/info/python3.preinst now? -- 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/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
We should reinstall python3 to get things back to what they were, as much as possible. Run: sudo apt install --reinstall python3=3.12.3-0ubuntu1 And then, leave the system as is if there are no further errors. Maybe tomorrow someone has another idea to try. -- 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/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
ok, well, that's good. Means there is this fallback that works. I still don't know why the upgrade failed for you. What does /var/lib/dpkg/info/python3.preinst look like now? ls -la /var/lib/dpkg/info/python3.preinst cat /var/lib/dpkg/info/python3.preinst -- 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/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
The "-s" was a simulation :) I wanted to check which packages would be downgraded, and the list looks correct. So let's try it without the -s: sudo apt install python3-minimal=3.12.3-0ubuntu1 libpython3-stdlib=3.12.3-0ubuntu1 python3=3.12.3-0ubuntu1 -- 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/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
What's the output of this command: sudo apt install -s python3-minimal=3.12.3-0ubuntu1 libpython3-stdlib=3.12.3-0ubuntu1 python3=3.12.3-0ubuntu1 This would be a revert attempt to the previous version. -- 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/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
I'm baffled, you clearly have python3 installed, but no /var/lib/dpkg/info/python3.preinst and you had to create it by hand? What do you get with this: ls -la /var/lib/dpkg/info/python3*preinst And this: py3versions -i -- 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/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
> N: Unable to locate package python3-mininal Sorry, that was a typo on my part, it should have been python3-minimal -- 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/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
> Okay, created the file /var/lib/dpkg/info/python3.preinst and executed it. No, you shouldn't have done that. If you had to create it, something else is very wrong on your system. That comes from the python3 debian package. Did you manage to check what I asked in comment #14 above? -- 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/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
> That script does not exist on my system. (/var/lib/dpkg/info/python3.preinst) Huh, that's unexpected. Do you have the python3 package installed? dpkg -l python3 python3-minimal apt-cache policy python3 python3-mininal -- 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/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
Sorry, I should have been more clear. If you are willing to help debug this further, then please add "set -x" just below the existing "set -e" in /var/lib/dpkg/info/python3.preinst and then run "sudo apt -f install" again. It should output a lot more debugging information. After that, you can undo your change. -- 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/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
if you want, you could add a "set -x" to that script (/var/lib/dpkg/info/python3.preinst) and then run the apt -f install again -- 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/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
The preinst goes over those scripts in /usr/share/python3/runtime.d and executes them one by one. It's supposed to show the error if one of them fails, but I don't see that in your output... #! /bin/sh set -e # remove the python3 alternatives before installing our own python3 link update-alternatives --auto /usr/bin/python3 >/dev/null 2>&1 || true [ -L /usr/share/doc/python3/html ] || rm -rf /usr/share/doc/python3/html case "$1" in upgrade) oldv=$(echo $2 | sed 's/^\(...\).*/\1/') if [ "$DEBIAN_FRONTEND" != noninteractive ]; then echo "running python pre-rtupdate hooks for python3.12..." fi for hook in /usr/share/python3/runtime.d/*.rtupdate; do [ -x $hook ] || continue if ! $hook pre-rtupdate python$oldv python3.12; then hb=$(basename $hook .rtupdate) echo >&2 "error running python pre-rtupdate hook $hb" echo >&2 "running python failed-pre-rtupdate hook $hb" $hook failed-pre-rtupdate python$oldv python3.12 errors=yes break fi done [ -z "$errors" ] || exit 3 esac -- 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/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
I can't reproduce this, and I have the same files in /usr/share/python3/runtime.d. @waveform, any idea what's going on here? -- 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/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
What do you have in /usr/share/python3/runtime.d/? ls -la /usr/share/python3/runtime.d/ -- 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/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
Please show the full output of: sudo apt -f install -- 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/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2075988] Re: Add comments to default config to explain Ubuntu deltas
This is fix released for oracular: https://git.launchpad.net/ubuntu/+source/openssh/tree/sshd_config?h=applied/ubuntu/oracular- devel#n15 ** Also affects: openssh (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: openssh (Ubuntu Oracular) Importance: Low Status: Incomplete ** Changed in: openssh (Ubuntu Oracular) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2075988 Title: Add comments to default config to explain Ubuntu deltas Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Noble: New Status in openssh source package in Oracular: Fix Released Bug description: Hello, reading https://discourse.ubuntu.com/t/sshd-now-uses-socket- based-activation-ubuntu-22-10-and-later/30189/44 a great point is made here. Can we put some comments in the default config explaining the deltas we make? This would be the most visible place for end-users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2075988/+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 2075337] Re: [SRU] py3clean fails when using alternate character set
I verified ubuntu-pro-client from noble-proposed. First, reproducing the bug with old python3-minimal and current pro client (notice *** installed versions): root@n:~# apt-cache policy python3-minimal ubuntu-pro-client python3-minimal: Install�: 3.12.3-0ubuntu1 Candidat�: 3.12.3-0ubuntu2 Table de version�: 3.12.3-0ubuntu2 500 (phased 80%) 500 http://br.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 100 http://br.archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages *** 3.12.3-0ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status ubuntu-pro-client: Install�: 32.3.1~24.04 Candidat�: 32.3.1~24.04 Table de version�: 33.2~24.04.1 100 100 http://br.archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages *** 32.3.1~24.04 500 500 http://br.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 100 /var/lib/dpkg/status 31.2.3 500 500 http://br.archive.ubuntu.com/ubuntu noble/main amd64 Packages root@n:~# apt install ubuntu-pro-client --reinstall Lecture des listes de paquets... Fait Construction de l'arbre des d�pendances... Fait Lecture des informations d'�tat... Fait 0 mis � jour, 0 nouvellement install�s, 1 r�install�s, 0 � enlever et 57 non mis � jour. Il est n�cessaire de prendre 229 ko dans les archives. Apr�s cette op�ration, 0 o d'espace disque suppl�mentaires seront utilis�s. R�ception de�:1 http://br.archive.ubuntu.com/ubuntu noble-updates/main amd64 ubuntu-pro-client amd64 32.3.1~24.04 [229 kB] 229 ko r�ceptionn�s en 0s (2�031 ko/s) (Lecture de la base de donn�es... 34410 fichiers et r�pertoires d�j� install�s.) Pr�paration du d�paquetage de .../ubuntu-pro-client_32.3.1~24.04_amd64.deb ... Traceback (most recent call last): File "/usr/bin/py3clean", line 210, in main() File "/usr/bin/py3clean", line 196, in main pfiles = set(dpf.from_package(options.package)) ^^ File "/usr/share/python3/debpython/files.py", line 54, in from_package stdout = str(stdout, 'utf-8') UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 584: invalid continuation byte Now I upgrade pro-client to the noble-proposed version. What I expect is that python3-minimal will be pulled in due to pro's Breaks, and no backtrace: root@n:~# apt install ubuntu-pro-client -t noble-proposed Lecture des listes de paquets... Fait Construction de l'arbre des d�pendances... Fait Lecture des informations d'�tat... Fait Les paquets suppl�mentaires suivants seront install�s�: libpython3-stdlib python3 python3-minimal ubuntu-pro-client-l10n Paquets sugg�r�s�: python3-doc python3-tk python3-venv Les paquets suivants seront mis � jour�: libpython3-stdlib python3 python3-minimal ubuntu-pro-client ubuntu-pro-client-l10n 5 mis � jour, 0 nouvellement install�s, 0 � enlever et 86 non mis � jour. Il est n�cessaire de prendre 311 ko dans les archives. Apr�s cette op�ration, 12,3 ko d'espace disque suppl�mentaires seront utilis�s. Souhaitez-vous continuer�? [O/n] R�ception de�:1 http://br.archive.ubuntu.com/ubuntu noble-updates/main amd64 python3-minimal amd64 3.12.3-0ubuntu2 [27,4 kB] R�ception de�:2 http://br.archive.ubuntu.com/ubuntu noble-updates/main amd64 python3 amd64 3.12.3-0ubuntu2 [23,0 kB] R�ception de�:3 http://br.archive.ubuntu.com/ubuntu noble-updates/main amd64 libpython3-stdlib amd64 3.12.3-0ubuntu2 [10,0 kB] R�ception de�:4 http://br.archive.ubuntu.com/ubuntu noble-proposed/main amd64 ubuntu-pro-client-l10n amd64 33.2~24.04.1 [19,3 kB] R�ception de�:5 http://br.archive.ubuntu.com/ubuntu noble-proposed/main amd64 ubuntu-pro-client amd64 33.2~24.04.1 [231 kB] 311 ko r�ceptionn�s en 0s (2�900 ko/s) (Lecture de la base de donn�es... 34410 fichiers et r�pertoires d�j� install�s.) Pr�paration du d�paquetage de .../python3-minimal_3.12.3-0ubuntu2_amd64.deb ... D�paquetage de python3-minimal (3.12.3-0ubuntu2) sur (3.12.3-0ubuntu1) ... Param�trage de python3-minimal (3.12.3-0ubuntu2) ... (Lecture de la base de donn�es... 34410 fichiers et r�pertoires d�j� install�s.) Pr�paration du d�paquetage de .../python3_3.12.3-0ubuntu2_amd64.deb ... running python pre-rtupdate hooks for python3.12... D�paquetage de python3 (3.12.3-0ubuntu2) sur (3.12.3-0ubuntu1) ... Pr�paration du d�paquetage de .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... D�paquetage de libpython3-stdlib:amd64 (3.12.3-0ubuntu2) sur (3.12.3-0ubuntu1) ... Pr�paration du d�paquetage de .../ubuntu-pro-client-l10n_33.2~24.04.1_amd64.deb ... D�paquetage de ubuntu-pro-client-l10n (33.2~24.04.1) sur (32.3.1~24.04) ... Pr�paration du d�paquetage de .../ubuntu-pro-client_33.2~24.04.1_amd64.deb ... D�paquetage de ubuntu-pro-client (33.2~24.04.1) sur (32.3.1~24.04) ... Param�trage de libpython3-stdlib:amd64 (3.12.3-0ubuntu2) ... Param�trage de python3 (3.12.3-0ubuntu2)
[Touch-packages] [Bug 2075337] Update Released
The verification of the Stable Release Update for python3-defaults has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in ubuntu-advantage-tools package in Ubuntu: New Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Committed Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Committed Status in dh-python source package in Noble: Invalid Status in python3-defaults source package in Noble: Fix Released Status in ubuntu-advantage-tools source package in Noble: Fix Committed Bug description: [ Impact ] With the current version of python3-defaults in jammy and noble, packages which utilize py3compile and py3clean in their maintscripts (which is more or less any package which includes Python modules), and which also are affected by diversions installed by dpkg-divert, will fail to install/upgrade/remove on systems with non-UTF-8 locales, which include non-ASCII characters in their localized dpkg -L messages (and which therefore produce output that is not valid UTF-8). As this has the potential to break apt upgrade, the impact is quite severe (especially if this occurs during a dist-upgrade). However, the scope is probably *fairly* limited given this only affects systems with non-UTF-8 locales (something that has not been the default for many years), and which produce non-ASCII output (e.g. French characters with diacriticals) in their localized messages for dpkg -L. [ Rectification Plan ] Firstly, python3-defaults must be patched in oracular, noble, and jammy. doko has uploaded the fix upstream and synced this to oracular. Benjamin has sponsored the noble and jammy SRUs. Next, affected packages must be patched to include a "Breaks" line on earlier versions of python3-minimal (the python3-defaults binary package containing py3clean and py3compile). Packages which install Python modules are easily selected, but those affected by diversions are (computationally) impossible to select (see comment 18 for details). Thus, determining the set of affected packages was non-trivial, but Benjamin has kindly produced such a list by empirical means (see comment 24). These will be added to the ticket as they are uploaded. [ Known affected packages ] ``` $ for section in main restricted universe multiverse; do echo "noble $section:"; sqlite3 affected.sqlite3 "SELECT package, source FROM package_affected WHERE section = '$section' and install_affected = 1 AND (remove_affected = 1 OR remove_affected ISNULL) ORDER BY package;"; echo; done noble main: cloud-init|cloud-init nvme-stas|nvme-stas python3-rtslib-fb|python-rtslib-fb targetcli-fb|targetcli-fb ubiquity|ubiquity ubiquity-frontend-debconf|ubiquity ubiquity-frontend-gtk|ubiquity ubuntu-drivers-common|ubuntu-drivers-common ubuntu-pro-client|ubuntu-advantage-tools walinuxagent|walinuxagent noble restricted: noble universe: a2d|a2d apertium-apy|apertium-apy blueman|blueman borgmatic|borgmatic condor|condor cpupower-gui|cpupower-gui debomatic|debomatic dell-recovery|dell-recovery deluge-web|deluge depthcharge-tools|depthcharge-tools dhcpy6d|dhcpy6d dkimpy-milter|dkimpy-milter fenrir|fenrir galileo|galileo glances|glances graphite-carbon|graphite-carbon grokmirror|grokmirror guerillabackup|guerillabackup ionit|ionit jupyterhub|jupyterhub liquidctl|liquidctl localslackirc|localslackirc logdata-anomaly-miner|logdata-anomaly-miner lomiri|lomiri mailman3|mailman3 mailman3-full|mailman3 matrix-sydent|matrix-sydent mom|mom mopidy|mopidy mpd-sima|mpd-sima nordugrid-arc-arex|nordugrid-arc notus-scanner|notus-scanner nrpe-ng|nrpe-ng onionprobe|onionprobe openscap-daemon|openscap-daemon ospd-openvas|ospd-openvas pagekite|pagekite pagure|pagure pagure-ev-server|pagure pagure-milters|pagure pglistener|pglistener policyd-rate-limit|policyd-rate-limit postfix-mta-sts-resolver|postfix-mta-sts-resolver powa-collector|powa-collector prelude-correlator|prelude-corre
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
Hello Robie, or anyone else affected, Accepted ubuntu-advantage-tools into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/33.2~24.04.1 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- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. 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: ubuntu-advantage-tools (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in ubuntu-advantage-tools package in Ubuntu: New Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Committed Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Committed Status in dh-python source package in Noble: Invalid Status in python3-defaults source package in Noble: Fix Committed Status in ubuntu-advantage-tools source package in Noble: Fix Committed Bug description: [ Impact ] With the current version of python3-defaults in jammy and noble, packages which utilize py3compile and py3clean in their maintscripts (which is more or less any package which includes Python modules), and which also are affected by diversions installed by dpkg-divert, will fail to install/upgrade/remove on systems with non-UTF-8 locales, which include non-ASCII characters in their localized dpkg -L messages (and which therefore produce output that is not valid UTF-8). As this has the potential to break apt upgrade, the impact is quite severe (especially if this occurs during a dist-upgrade). However, the scope is probably *fairly* limited given this only affects systems with non-UTF-8 locales (something that has not been the default for many years), and which produce non-ASCII output (e.g. French characters with diacriticals) in their localized messages for dpkg -L. [ Rectification Plan ] Firstly, python3-defaults must be patched in oracular, noble, and jammy. doko has uploaded the fix upstream and synced this to oracular. Benjamin has sponsored the noble and jammy SRUs. Next, affected packages must be patched to include a "Breaks" line on earlier versions of python3-minimal (the python3-defaults binary package containing py3clean and py3compile). Packages which install Python modules are easily selected, but those affected by diversions are (computationally) impossible to select (see comment 18 for details). Thus, determining the set of affected packages was non-trivial, but Benjamin has kindly produced such a list by empirical means (see comment 24). These will be added to the ticket as they are uploaded. [ Known affected packages ] ``` $ for section in main restricted universe multiverse; do echo "noble $section:"; sqlite3 affected.sqlite3 "SELECT package, source FROM package_affected WHERE section = '$section' and install_affected = 1 AND (remove_affected = 1 OR remove_affected ISNULL) ORDER BY package;"; echo; done noble main: cloud-init|cloud-init nvme-stas|nvme-stas python3-rtslib-fb|python-rtslib-fb targetcli-fb|targetcli-fb ubiquity|ubiquity ubiquity-frontend-debconf|ubiquity ubiquity-frontend-gtk|ubiquity ubuntu-drivers-common|ubuntu-drivers-common ubuntu-pro-client|ubuntu-advantage-tools walinuxagent|walinuxagent noble restricted: noble universe: a2d|a2d apertium-apy|apertium-apy blueman|blueman borgmatic|borgmatic condor|condor cpupower-gui|cpupower-gui debomatic|debomatic dell-recovery|dell-recovery deluge-web|deluge depthcharge-tools|depthcharge-tool
[Touch-packages] [Bug 2060666] Update Released
The verification of the Stable Release Update for krb5 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/2060666 Title: [SRU] Memory leak in krb5 version 1.17 Status in krb5 package in Ubuntu: Fix Released Status in krb5 source package in Focal: Fix Released Bug description: [ Impact ] Commit https://github.com/krb5/krb5/commit/1cd2821c19b2b95e39d5fc2f451a035585a40fa5 altered the memory management of krb5_gss_inquire_cred(), introducing defcred to act as an owner pointer when the function must acquire a default credential. The commit neglected to update the code to release the default cred along the successful path. The old code does not trigger because cred_handle is now reassigned, so the default credential is leaked. Resulting gradual increase in memory usage (memory leak) and eventual crash. [ Test Plan ] Setup 3 VMs: 1. Windows Server act as Domain controller (AD) 2. Windows machine AD Joined with Ostress installed. (Ostress is part of RML utilities https://learn.microsoft.com/en-us/troubleshoot/sql/tools/replay-markup-language-utility) 3. SQL on Linux AD Joined ( configuration steps https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-ad-auth-adutil-tutorial?view=sql-server-ver16) On the Machine with OStress create a file (name it disconnect.ini) with the following content under the same folder “C:\Program Files\Microsoft Corporation\RMLUtils” where OStress is installed. disconnect.ini == [Connection Options] LoginTimeout=30 QuotedIdentifier=Off AutocommitMode=On DisconnectPct=100.0 MaxThreadErrors=0 [Query Options] NoSQLBindCol=Off NoResultDisplay=Off PrepareExecute=Off ExecuteAsync=Off RollbackOnCancel=Off QueryTimeout=0 QueryDelay=0 MaxRetries=0 BatchDisconnectPct=0.0 CancelPct=0.00 CancelDelay=0 CancelDelayMin=0 CursorType= CursorConcurrency= RowFetchDelay=0 [Replay Options] Sequencing Options=global sequence ::Sequencing Options=global sequence, dtc replay DTC Timeout= DTC Machine=(local) Playback Coordinator=(local) StartSeqNum= StopSeqNum= TimeoutFactor=1.0 Run the following command to start the load using Ostress, change Server name (-S) accordingly and the number of threads (-n) as needed. Start 4 different CMD consoles and use the following different commands for each CMD window: 1. ostress.exe -E -S -Q"select * from sys.all_objects" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log01 -T146 2. ostress.exe -E -S -Q"select * from sys.all_views" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log02 -T146 3. ostress.exe -E -S -Q"select * from sys.all_columns" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log03 -T146 4. ostress.exe -E -S -Q"select * from sys.all_parameters" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log04 -T146 After a run of about 5 hours, the memory usage for this is expected to be around 5G with the fix. Without the fix, it was observed that it reached around ~22G in 5 hours. Hence the increase in memory usage can be observed if the ostress.exe programs are let to run longer. [ Where problems could occur ] The fix may not fix the memory leak or could result in releasing the memory early in a different code path, and thus resulting in crashes. A mitigating fact is that the fix has been in Ubuntu since at least 22.04 and they do not exhibit any issues. Likewise I've previously provided the fix in a PPA https://launchpad.net/~pponnuvel/+archive/ubuntu/krb5-focal to user who's been hit by this issue. They've tested and confirmed it fixes the memory leak. [ Other Info ] The commit https://github.com/krb5/krb5/commit/098f874f3b50dd2c46c0a574677324b5f6f3a1a8 fixes the leak. The fix has been included in newer krb5 releases (Jammy, and Noble have the releases with the fix). Bionic doesn't have the commit the introduced the memory leak in the first place. So this will be a Focal-only backport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/2060666/+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 2060666] Re: [SRU] Memory leak in krb5 version 1.17
It passed now https://autopkgtest.ubuntu.com/packages/moonshot-gss- eap/focal/armhf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/2060666 Title: [SRU] Memory leak in krb5 version 1.17 Status in krb5 package in Ubuntu: Fix Released Status in krb5 source package in Focal: Fix Committed Bug description: [ Impact ] Commit https://github.com/krb5/krb5/commit/1cd2821c19b2b95e39d5fc2f451a035585a40fa5 altered the memory management of krb5_gss_inquire_cred(), introducing defcred to act as an owner pointer when the function must acquire a default credential. The commit neglected to update the code to release the default cred along the successful path. The old code does not trigger because cred_handle is now reassigned, so the default credential is leaked. Resulting gradual increase in memory usage (memory leak) and eventual crash. [ Test Plan ] Setup 3 VMs: 1. Windows Server act as Domain controller (AD) 2. Windows machine AD Joined with Ostress installed. (Ostress is part of RML utilities https://learn.microsoft.com/en-us/troubleshoot/sql/tools/replay-markup-language-utility) 3. SQL on Linux AD Joined ( configuration steps https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-ad-auth-adutil-tutorial?view=sql-server-ver16) On the Machine with OStress create a file (name it disconnect.ini) with the following content under the same folder “C:\Program Files\Microsoft Corporation\RMLUtils” where OStress is installed. disconnect.ini == [Connection Options] LoginTimeout=30 QuotedIdentifier=Off AutocommitMode=On DisconnectPct=100.0 MaxThreadErrors=0 [Query Options] NoSQLBindCol=Off NoResultDisplay=Off PrepareExecute=Off ExecuteAsync=Off RollbackOnCancel=Off QueryTimeout=0 QueryDelay=0 MaxRetries=0 BatchDisconnectPct=0.0 CancelPct=0.00 CancelDelay=0 CancelDelayMin=0 CursorType= CursorConcurrency= RowFetchDelay=0 [Replay Options] Sequencing Options=global sequence ::Sequencing Options=global sequence, dtc replay DTC Timeout= DTC Machine=(local) Playback Coordinator=(local) StartSeqNum= StopSeqNum= TimeoutFactor=1.0 Run the following command to start the load using Ostress, change Server name (-S) accordingly and the number of threads (-n) as needed. Start 4 different CMD consoles and use the following different commands for each CMD window: 1. ostress.exe -E -S -Q"select * from sys.all_objects" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log01 -T146 2. ostress.exe -E -S -Q"select * from sys.all_views" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log02 -T146 3. ostress.exe -E -S -Q"select * from sys.all_columns" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log03 -T146 4. ostress.exe -E -S -Q"select * from sys.all_parameters" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log04 -T146 After a run of about 5 hours, the memory usage for this is expected to be around 5G with the fix. Without the fix, it was observed that it reached around ~22G in 5 hours. Hence the increase in memory usage can be observed if the ostress.exe programs are let to run longer. [ Where problems could occur ] The fix may not fix the memory leak or could result in releasing the memory early in a different code path, and thus resulting in crashes. A mitigating fact is that the fix has been in Ubuntu since at least 22.04 and they do not exhibit any issues. Likewise I've previously provided the fix in a PPA https://launchpad.net/~pponnuvel/+archive/ubuntu/krb5-focal to user who's been hit by this issue. They've tested and confirmed it fixes the memory leak. [ Other Info ] The commit https://github.com/krb5/krb5/commit/098f874f3b50dd2c46c0a574677324b5f6f3a1a8 fixes the leak. The fix has been included in newer krb5 releases (Jammy, and Noble have the releases with the fix). Bionic doesn't have the commit the introduced the memory leak in the first place. So this will be a Focal-only backport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/2060666/+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 2060666] Re: [SRU] Memory leak in krb5 version 1.17
https://autopkgtest.ubuntu.com/packages/postgresql-12/focal/s390x is green now, and https://autopkgtest.ubuntu.com/packages/moonshot-gss- eap/focal/armhf got another tmpfail. I retried that one one more time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/2060666 Title: [SRU] Memory leak in krb5 version 1.17 Status in krb5 package in Ubuntu: Fix Released Status in krb5 source package in Focal: Fix Committed Bug description: [ Impact ] Commit https://github.com/krb5/krb5/commit/1cd2821c19b2b95e39d5fc2f451a035585a40fa5 altered the memory management of krb5_gss_inquire_cred(), introducing defcred to act as an owner pointer when the function must acquire a default credential. The commit neglected to update the code to release the default cred along the successful path. The old code does not trigger because cred_handle is now reassigned, so the default credential is leaked. Resulting gradual increase in memory usage (memory leak) and eventual crash. [ Test Plan ] Setup 3 VMs: 1. Windows Server act as Domain controller (AD) 2. Windows machine AD Joined with Ostress installed. (Ostress is part of RML utilities https://learn.microsoft.com/en-us/troubleshoot/sql/tools/replay-markup-language-utility) 3. SQL on Linux AD Joined ( configuration steps https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-ad-auth-adutil-tutorial?view=sql-server-ver16) On the Machine with OStress create a file (name it disconnect.ini) with the following content under the same folder “C:\Program Files\Microsoft Corporation\RMLUtils” where OStress is installed. disconnect.ini == [Connection Options] LoginTimeout=30 QuotedIdentifier=Off AutocommitMode=On DisconnectPct=100.0 MaxThreadErrors=0 [Query Options] NoSQLBindCol=Off NoResultDisplay=Off PrepareExecute=Off ExecuteAsync=Off RollbackOnCancel=Off QueryTimeout=0 QueryDelay=0 MaxRetries=0 BatchDisconnectPct=0.0 CancelPct=0.00 CancelDelay=0 CancelDelayMin=0 CursorType= CursorConcurrency= RowFetchDelay=0 [Replay Options] Sequencing Options=global sequence ::Sequencing Options=global sequence, dtc replay DTC Timeout= DTC Machine=(local) Playback Coordinator=(local) StartSeqNum= StopSeqNum= TimeoutFactor=1.0 Run the following command to start the load using Ostress, change Server name (-S) accordingly and the number of threads (-n) as needed. Start 4 different CMD consoles and use the following different commands for each CMD window: 1. ostress.exe -E -S -Q"select * from sys.all_objects" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log01 -T146 2. ostress.exe -E -S -Q"select * from sys.all_views" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log02 -T146 3. ostress.exe -E -S -Q"select * from sys.all_columns" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log03 -T146 4. ostress.exe -E -S -Q"select * from sys.all_parameters" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log04 -T146 After a run of about 5 hours, the memory usage for this is expected to be around 5G with the fix. Without the fix, it was observed that it reached around ~22G in 5 hours. Hence the increase in memory usage can be observed if the ostress.exe programs are let to run longer. [ Where problems could occur ] The fix may not fix the memory leak or could result in releasing the memory early in a different code path, and thus resulting in crashes. A mitigating fact is that the fix has been in Ubuntu since at least 22.04 and they do not exhibit any issues. Likewise I've previously provided the fix in a PPA https://launchpad.net/~pponnuvel/+archive/ubuntu/krb5-focal to user who's been hit by this issue. They've tested and confirmed it fixes the memory leak. [ Other Info ] The commit https://github.com/krb5/krb5/commit/098f874f3b50dd2c46c0a574677324b5f6f3a1a8 fixes the leak. The fix has been included in newer krb5 releases (Jammy, and Noble have the releases with the fix). Bionic doesn't have the commit the introduced the memory leak in the first place. So this will be a Focal-only backport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/2060666/+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 2067240] Re: [SRU] Add Quectel EM061K-GL/EM160/RM520N PID information to support WWAN LVFS
Hi Atlas, thanks for your verification. Following the request in comment #12, though: > If this package fixes the bug for you, please add a comment to this bug, > mentioning the version of the > package you tested, Could you please clarify the version of the package you tested? ** Tags removed: verification-done-jammy ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2067240 Title: [SRU] Add Quectel EM061K-GL/EM160/RM520N PID information to support WWAN LVFS Status in OEM Priority Project: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: Fix Committed Bug description: [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM061K-GL/EM160/RM520N PID information, and the modemmanger won't recognize these WWAN modems on some next-gen Lenovo laptops. (lp: #2045276) [ Test Plan ] Under Jammy environment, with latest linux-oem kernel installed, check output of `mmcli -L` to see if the modems are properly recognized. Modems to check: - EM061K-GL - EM160 - EM160 [ Where problems could occur ] EM160R-GL(1.22.0): https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1059/diffs EM061K-GL(1.22.0): https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1057/diffs RM520N-GL(1.22.0): https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1052/diffs https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1077/diffs All these changes are merged, and they only introduce new PIDs for initial supports, which do not affect existing ones. Noble contains these changes, so, only SRU jammy and mantic. [ Other Info ] These patches are proved work with the test version on my PPA: https://launchpad.net/~pseudoc/+archive/ubuntu/nate To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2067240/+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 2036467] Update Released
The verification of the Stable Release Update for e2fsprogs has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2036467 Title: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs Status in cloud-images: New Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Trusty: Won't Fix Status in e2fsprogs source package in Xenial: Won't Fix Status in e2fsprogs source package in Bionic: Won't Fix Status in e2fsprogs source package in Focal: Fix Committed Status in e2fsprogs source package in Jammy: Fix Released Status in e2fsprogs source package in Lunar: Won't Fix Status in e2fsprogs source package in Mantic: Won't Fix Status in e2fsprogs source package in Noble: Fix Released Status in e2fsprogs source package in Oracular: Fix Released Bug description: [Impact] This is a long running bug plaguing cloud-images, where on a rare occasion resize2fs would fail and the image would not resize to fit the entire disk. Online resizes would fail due to a superblock checksum mismatch, where the superblock in memory differs from what is currently on disk due to changes made to the image. $ resize2fs /dev/nvme1n1p1 resize2fs 1.47.0 (5-Feb-2023) resize2fs: Superblock checksum does not match superblock while trying to open /dev/nvme1n1p1 Couldn't find valid filesystem superblock. Changing the read of the superblock to Direct I/O solves the issue. [Testcase] Start an c5.large instance on AWS, and attach a 60gb gp3 volume for use as a scratch disk. Run the following script, courtesy of Krister Johansen and his team: #!/usr/bin/bash set -euxo pipefail while true do parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s sleep .5 mkfs.ext4 /dev/nvme1n1p1 mount -t ext4 /dev/nvme1n1p1 /mnt stress-ng --temp-path /mnt -D 4 & STRESS_PID=$! sleep 1 growpart /dev/nvme1n1 1 resize2fs /dev/nvme1n1p1 kill $STRESS_PID wait $STRESS_PID umount /mnt wipefs -a /dev/nvme1n1p1 wipefs -a /dev/nvme1n1 done Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test If you install the test packages, the race no longer occurs. [Where problems could occur] We are changing how resize2fs reads the superblock from underlying disks. If a regression were to occur, resize2fs could fail to resize offline or online volumes. As all cloud-images are online resized during their initial boot, this could have a large impact to public and private clouds should a regression occur. [Other info] Upstream mailing list discussion: https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/ https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/ This was fixed in the below commit upstream: commit 43a498e938887956f393b5e45ea6ac79cc5f4b84 Author: Theodore Ts'o Date: Thu, 15 Jun 2023 00:17:01 -0400 Subject: resize2fs: use Direct I/O when reading the superblock for online resizes Link: https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84 The commit has not been tagged to any release. All supported Ubuntu releases require this fix, and need to be published in standard non- ESM archives to be picked up in cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036467/+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 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs
The focal autopkgtests need work, lots of failed tests there: https://ubuntu-archive-team.ubuntu.com/proposed- migration/focal/update_excuses.html#e2fsprogs Looks like they all failed due to infrastructure problems (version="unknown" is the telltale). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2036467 Title: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs Status in cloud-images: New Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Trusty: Won't Fix Status in e2fsprogs source package in Xenial: Won't Fix Status in e2fsprogs source package in Bionic: Won't Fix Status in e2fsprogs source package in Focal: Fix Committed Status in e2fsprogs source package in Jammy: Fix Released Status in e2fsprogs source package in Lunar: Won't Fix Status in e2fsprogs source package in Mantic: Won't Fix Status in e2fsprogs source package in Noble: Fix Released Status in e2fsprogs source package in Oracular: Fix Released Bug description: [Impact] This is a long running bug plaguing cloud-images, where on a rare occasion resize2fs would fail and the image would not resize to fit the entire disk. Online resizes would fail due to a superblock checksum mismatch, where the superblock in memory differs from what is currently on disk due to changes made to the image. $ resize2fs /dev/nvme1n1p1 resize2fs 1.47.0 (5-Feb-2023) resize2fs: Superblock checksum does not match superblock while trying to open /dev/nvme1n1p1 Couldn't find valid filesystem superblock. Changing the read of the superblock to Direct I/O solves the issue. [Testcase] Start an c5.large instance on AWS, and attach a 60gb gp3 volume for use as a scratch disk. Run the following script, courtesy of Krister Johansen and his team: #!/usr/bin/bash set -euxo pipefail while true do parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s sleep .5 mkfs.ext4 /dev/nvme1n1p1 mount -t ext4 /dev/nvme1n1p1 /mnt stress-ng --temp-path /mnt -D 4 & STRESS_PID=$! sleep 1 growpart /dev/nvme1n1 1 resize2fs /dev/nvme1n1p1 kill $STRESS_PID wait $STRESS_PID umount /mnt wipefs -a /dev/nvme1n1p1 wipefs -a /dev/nvme1n1 done Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test If you install the test packages, the race no longer occurs. [Where problems could occur] We are changing how resize2fs reads the superblock from underlying disks. If a regression were to occur, resize2fs could fail to resize offline or online volumes. As all cloud-images are online resized during their initial boot, this could have a large impact to public and private clouds should a regression occur. [Other info] Upstream mailing list discussion: https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/ https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/ This was fixed in the below commit upstream: commit 43a498e938887956f393b5e45ea6ac79cc5f4b84 Author: Theodore Ts'o Date: Thu, 15 Jun 2023 00:17:01 -0400 Subject: resize2fs: use Direct I/O when reading the superblock for online resizes Link: https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84 The commit has not been tagged to any release. All supported Ubuntu releases require this fix, and need to be published in standard non- ESM archives to be picked up in cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036467/+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 2075337] Re: [SRU] py3clean fails when using alternate character set
Nice, is someone going to execute the test plan? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in ubuntu-advantage-tools package in Ubuntu: New Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Committed Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Committed Status in dh-python source package in Noble: Invalid Status in python3-defaults source package in Noble: Fix Committed Status in ubuntu-advantage-tools source package in Noble: New Bug description: [ Impact ] With the current version of python3-defaults in jammy and noble, packages which utilize py3compile and py3clean in their maintscripts (which is more or less any package which includes Python modules), and which also are affected by diversions installed by dpkg-divert, will fail to install/upgrade/remove on systems with non-UTF-8 locales, which include non-ASCII characters in their localized dpkg -L messages (and which therefore produce output that is not valid UTF-8). As this has the potential to break apt upgrade, the impact is quite severe (especially if this occurs during a dist-upgrade). However, the scope is probably *fairly* limited given this only affects systems with non-UTF-8 locales (something that has not been the default for many years), and which produce non-ASCII output (e.g. French characters with diacriticals) in their localized messages for dpkg -L. [ Rectification Plan ] Firstly, python3-defaults must be patched in oracular, noble, and jammy. doko has uploaded the fix upstream and synced this to oracular. Benjamin has sponsored the noble and jammy SRUs. Next, affected packages must be patched to include a "Breaks" line on earlier versions of python3-minimal (the python3-defaults binary package containing py3clean and py3compile). Packages which install Python modules are easily selected, but those affected by diversions are (computationally) impossible to select (see comment 18 for details). Thus, determining the set of affected packages was non-trivial, but Benjamin has kindly produced such a list by empirical means (see comment 24). These will be added to the ticket as they are uploaded. [ Known affected packages ] ``` $ for section in main restricted universe multiverse; do echo "noble $section:"; sqlite3 affected.sqlite3 "SELECT package, source FROM package_affected WHERE section = '$section' and install_affected = 1 AND (remove_affected = 1 OR remove_affected ISNULL) ORDER BY package;"; echo; done noble main: cloud-init|cloud-init nvme-stas|nvme-stas python3-rtslib-fb|python-rtslib-fb targetcli-fb|targetcli-fb ubiquity|ubiquity ubiquity-frontend-debconf|ubiquity ubiquity-frontend-gtk|ubiquity ubuntu-drivers-common|ubuntu-drivers-common ubuntu-pro-client|ubuntu-advantage-tools walinuxagent|walinuxagent noble restricted: noble universe: a2d|a2d apertium-apy|apertium-apy blueman|blueman borgmatic|borgmatic condor|condor cpupower-gui|cpupower-gui debomatic|debomatic dell-recovery|dell-recovery deluge-web|deluge depthcharge-tools|depthcharge-tools dhcpy6d|dhcpy6d dkimpy-milter|dkimpy-milter fenrir|fenrir galileo|galileo glances|glances graphite-carbon|graphite-carbon grokmirror|grokmirror guerillabackup|guerillabackup ionit|ionit jupyterhub|jupyterhub liquidctl|liquidctl localslackirc|localslackirc logdata-anomaly-miner|logdata-anomaly-miner lomiri|lomiri mailman3|mailman3 mailman3-full|mailman3 matrix-sydent|matrix-sydent mom|mom mopidy|mopidy mpd-sima|mpd-sima nordugrid-arc-arex|nordugrid-arc notus-scanner|notus-scanner nrpe-ng|nrpe-ng onionprobe|onionprobe openscap-daemon|openscap-daemon ospd-openvas|ospd-openvas pagekite|pagekite pagure|pagure pagure-ev-server|pagure pagure-milters|pagure pglistener|pglistener policyd-rate-limit|policyd-rate-limit postfix-mta-sts-resolver|postfix-mta-sts-resolver powa-collector|powa-collector prelude-correlator|prelude-correlator prometheus-pgbouncer-exporter|prometheus-pgbouncer-exporter prometheus-xmpp-alerts|prometheus-xmpp-alerts pyroman|pyroman python3-autopilot|autopilot python3-btchip|btchip-python python3-pyro5|pyro5 qweborf|weborf razercfg|razercfg sgt-launcher|sgt-launcher sms4you|sms4you supervisor|supervisor syncplay-server|syncplay timekpr-next|timekpr-next twms|twms ubiquity-frontend-kde|ubiquity vanguar
[Touch-packages] [Bug 2056768] Re: apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/run/systemd/sessions/"
** Tags added: server-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2056768 Title: apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/run/systemd/sessions/" Status in rsyslog package in Ubuntu: In Progress Status in rsyslog source package in Noble: Confirmed Bug description: There is an AppArmor regression in current noble. In cockpit we recently started to test on noble (to prevent the "major regressions after release" fiasco from 23.10 again). For some weird reason, rsyslog is installed *by default* [1] in the cloud images. That is a rather pointless waste of CPU and disk space, as it's an unnecessary running daemon and duplicates all the written logs. But more specifically, we noticed [2] an AppArmor rejection. Reproducer is simple: logger -p user.emerg --tag check-journal EMERGENCY_MESSAGE this causes type=1400 audit(1710168739.345:108): apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/run/systemd/sessions/" pid=714 comm=72733A6D61696E20513A526567 requested_mask="r" denied_mask="r" fsuid=102 ouid=0 Note that it doesn't actually fail, the "EMERGENCY_MESSAGE" does appear in the journal and also in /var/log/syslog. But it's some noise that triggers our (and presumbly other admin's) log detectors. rsyslog 8.2312.0-3ubuntu3 apparmor 4.0.0~alpha4-0ubuntu1 [1] https://cloud-images.ubuntu.com/daily/server/noble/current/noble-server-cloudimg-amd64.manifest [2] https://cockpit-logs.us-east-1.linodeobjects.com/pull-6048-20240311-125838-b465e9b2-ubuntu-stable-other-cockpit-project-cockpit/log.html#118 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2056768/+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 2056768] Re: apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/run/systemd/sessions/"
And once allowing reading the directory, the contents should also be
allowed:
[Sun Sep 1 16:00:46 2024] audit: type=1400 audit(1724157515.788:5238):
apparmor="DENIED" operation="open" class="file" profile="rsyslogd"
name="/run/systemd/sessions/2" pid=1873 comm=72733A6D61696E20513A526567
requested_mask="r" denied_mask="r" fsuid=102 ouid=0
So this is what I came up with:
--- a/debian/usr.sbin.rsyslogd
+++ b/debian/usr.sbin.rsyslogd
@@ -26,6 +26,11 @@ profile rsyslogd /usr/sbin/rsyslogd {
/etc/rsyslog.d/ r,
/etc/rsyslog.d/** r,
/{,var/}run/rsyslogd.pid{,.tmp} rwk,
+
+ # LP: #2056768
+ /{,var/}run/systemd/sessions/ r,
+ /{,var/}run/systemd/sessions/* r,
+
/var/spool/rsyslog/ r,
/var/spool/rsyslog/** rwk,
** Changed in: rsyslog (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/2056768
Title:
apparmor="DENIED" operation="open" class="file" profile="rsyslogd"
name="/run/systemd/sessions/"
Status in rsyslog package in Ubuntu:
In Progress
Status in rsyslog source package in Noble:
Confirmed
Bug description:
There is an AppArmor regression in current noble. In cockpit we
recently started to test on noble (to prevent the "major regressions
after release" fiasco from 23.10 again).
For some weird reason, rsyslog is installed *by default* [1] in the
cloud images. That is a rather pointless waste of CPU and disk space,
as it's an unnecessary running daemon and duplicates all the written
logs.
But more specifically, we noticed [2] an AppArmor rejection.
Reproducer is simple:
logger -p user.emerg --tag check-journal EMERGENCY_MESSAGE
this causes
type=1400 audit(1710168739.345:108): apparmor="DENIED"
operation="open" class="file" profile="rsyslogd"
name="/run/systemd/sessions/" pid=714 comm=72733A6D61696E20513A526567
requested_mask="r" denied_mask="r" fsuid=102 ouid=0
Note that it doesn't actually fail, the "EMERGENCY_MESSAGE" does
appear in the journal and also in /var/log/syslog. But it's some noise
that triggers our (and presumbly other admin's) log detectors.
rsyslog 8.2312.0-3ubuntu3
apparmor 4.0.0~alpha4-0ubuntu1
[1]
https://cloud-images.ubuntu.com/daily/server/noble/current/noble-server-cloudimg-amd64.manifest
[2]
https://cockpit-logs.us-east-1.linodeobjects.com/pull-6048-20240311-125838-b465e9b2-ubuntu-stable-other-cockpit-project-cockpit/log.html#118
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2056768/+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 2072574] Update Released
The verification of the Stable Release Update for ubuntu-settings has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2072574 Title: Drop obsolete evolution-data-server notify-with-tray override Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Noble: Fix Released Bug description: Impact -- Calendar notifications currently pop up a full app window instead of as a normal notification. The normal notifications respect the Do Not Disturb setting, but the full app window does not. Test Case 1 --- From Ubuntu Desktop… 1. Add your Google account to GNOME Settings > Online Accounts 2. Add a calendar event to Google Calendar with a notification in advance 3. When it is time for the notification, you should see a GNOME Shell notification. You can click on the notification to see the full Reminders window. Test Case 2 --- From Ubuntu Unity 24.04 LTS… 1. Open a terminal and run this command: sudo apt install gnome-online-accounts-gtk 2. Close the terminal 3. Add a calendar event to Google Calendar with a notification in advance 4. When it is time for the notification, you should see a notification pop-up. You can click OK on the notification to see the full Reminders window. What Could Go Wrong --- The ubuntu-settings package is shipped by default with Ubuntu Desktop, Ubuntu Unity, and Edubuntu. Edubuntu is practically the same as Ubuntu Desktop as far as the desktop experience goes with one additional GNOME Shell extension to sort the Show Apps view alphabetically. This is a small default change that can be easily changed (see Revert instructions below). I guess this could go bad if someone counts on getting event notifications even though they have turned on Do Not Disturb. I'm sorry but it is intended that Do Not Disturb not show notifications like this. Other Info -- I believe this override was originally added in 2011 for Unity's benefit LP: #757805 It was also helpful for GNOME in early GNOME 3 days with the unusual messaging tray that was later dropped. These days, GNOME Shell notifications work well, better than a separate popup window. Revert to Previous Behavior --- If you prefer the original Ubuntu 24.04 LTS behavior, do one of the following: 1. Run this in a terminal: gsettings set org.gnome.evolution-data-server.calendar notify-with-tray false 2. Or install Evolution. In ☰ > Edit > Preferences > Calendar and Tasks, turn on "Display Reminder window with notifications" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2072574/+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 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs
I retried the remaining failing autopkgtests. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2036467 Title: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs Status in cloud-images: New Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Trusty: Won't Fix Status in e2fsprogs source package in Xenial: Won't Fix Status in e2fsprogs source package in Bionic: Won't Fix Status in e2fsprogs source package in Focal: Fix Committed Status in e2fsprogs source package in Jammy: Fix Committed Status in e2fsprogs source package in Lunar: Won't Fix Status in e2fsprogs source package in Mantic: Won't Fix Status in e2fsprogs source package in Noble: Fix Committed Status in e2fsprogs source package in Oracular: Fix Released Bug description: [Impact] This is a long running bug plaguing cloud-images, where on a rare occasion resize2fs would fail and the image would not resize to fit the entire disk. Online resizes would fail due to a superblock checksum mismatch, where the superblock in memory differs from what is currently on disk due to changes made to the image. $ resize2fs /dev/nvme1n1p1 resize2fs 1.47.0 (5-Feb-2023) resize2fs: Superblock checksum does not match superblock while trying to open /dev/nvme1n1p1 Couldn't find valid filesystem superblock. Changing the read of the superblock to Direct I/O solves the issue. [Testcase] Start an c5.large instance on AWS, and attach a 60gb gp3 volume for use as a scratch disk. Run the following script, courtesy of Krister Johansen and his team: #!/usr/bin/bash set -euxo pipefail while true do parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s sleep .5 mkfs.ext4 /dev/nvme1n1p1 mount -t ext4 /dev/nvme1n1p1 /mnt stress-ng --temp-path /mnt -D 4 & STRESS_PID=$! sleep 1 growpart /dev/nvme1n1 1 resize2fs /dev/nvme1n1p1 kill $STRESS_PID wait $STRESS_PID umount /mnt wipefs -a /dev/nvme1n1p1 wipefs -a /dev/nvme1n1 done Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test If you install the test packages, the race no longer occurs. [Where problems could occur] We are changing how resize2fs reads the superblock from underlying disks. If a regression were to occur, resize2fs could fail to resize offline or online volumes. As all cloud-images are online resized during their initial boot, this could have a large impact to public and private clouds should a regression occur. [Other info] Upstream mailing list discussion: https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/ https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/ This was fixed in the below commit upstream: commit 43a498e938887956f393b5e45ea6ac79cc5f4b84 Author: Theodore Ts'o Date: Thu, 15 Jun 2023 00:17:01 -0400 Subject: resize2fs: use Direct I/O when reading the superblock for online resizes Link: https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84 The commit has not been tagged to any release. All supported Ubuntu releases require this fix, and need to be published in standard non- ESM archives to be picked up in cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036467/+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 2046486] Re: units with credentials fail in LXD containers
** Merge proposal unlinked: https://code.launchpad.net/~ahasenack/ubuntu/+source/samba/+git/samba/+merge/471168 -- 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/2046486 Title: units with credentials fail in LXD containers Status in cloud-images: Confirmed Status in lxd: New Status in lxd package in Ubuntu: Fix Committed Status in samba package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Triaged Bug description: Many units shipped by systemd use credentials in some way by default now (in v256). So this issue is now about much more than the original test case failure. For example, root@oracular:~# apt policy systemd systemd: Installed: 256-1ubuntu1 Candidate: 256-1ubuntu1 Version table: *** 256-1ubuntu1 100 100 http://archive.ubuntu.com/ubuntu oracular-proposed/main amd64 Packages 100 /var/lib/dpkg/status 255.4-1ubuntu8 500 500 http://archive.ubuntu.com/ubuntu oracular/main amd64 Packages root@oracular:~# for service in $(find /usr/lib/systemd/system -maxdepth 1 -name "systemd-*.service"); do grep -q "Credential.*=" "$service" && echo "$service"; done /usr/lib/systemd/system/systemd-sysusers.service /usr/lib/systemd/system/systemd-resolved.service /usr/lib/systemd/system/systemd-firstboot.service /usr/lib/systemd/system/systemd-network-generator.service /usr/lib/systemd/system/systemd-journald.service /usr/lib/systemd/system/systemd-sysctl.service /usr/lib/systemd/system/systemd-tmpfiles-setup-dev-early.service /usr/lib/systemd/system/systemd-tmpfiles-setup-dev.service /usr/lib/systemd/system/systemd-tmpfiles-setup.service /usr/lib/systemd/system/systemd-udev-load-credentials.service /usr/lib/systemd/system/systemd-tmpfiles-clean.service /usr/lib/systemd/system/systemd-networkd.service root@oracular:~# systemctl status systemd-sysusers.service systemd-resolved.service systemd-firstboot.service systemd-network-generator.service systemd-journald.service systemd-sysctl.service systemd-tmpfiles-setup-dev-early.service systemd-tmpfiles-setup-dev.service systemd-tmpfiles-setup.service systemd-udev-load-credentials.service systemd-tmpfiles-clean.service systemd-networkd.service ○ systemd-sysusers.service - Create System Users Loaded: loaded (/usr/lib/systemd/system/systemd-sysusers.service; static) Active: inactive (dead) Condition: start condition unmet at Mon 2024-06-24 18:58:48 UTC; 1min 0s ago ├─ ConditionNeedsUpdate=|/etc was not met └─ ConditionCredential=|sysusers.extra was not met Docs: man:sysusers.d(5) man:systemd-sysusers.service(8) × systemd-resolved.service - Network Name Resolution Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Mon 2024-06-24 18:58:49 UTC; 59s ago Invocation: b1aaa662750f48868fe3388e4524c462 Docs: man:systemd-resolved.service(8) man:org.freedesktop.resolve1(5) https://systemd.io/WRITING_NETWORK_CONFIGURATION_MANAGERS https://systemd.io/WRITING_RESOLVER_CLIENTS Process: 258 ExecStart=/usr/lib/systemd/systemd-resolved (code=exited, status=243/CREDENTIALS) Main PID: 258 (code=exited, status=243/CREDENTIALS) ○ systemd-firstboot.service - First Boot Wizard Loaded: loaded (/usr/lib/systemd/system/systemd-firstboot.service; static) Active: inactive (dead) Condition: start condition unmet at Mon 2024-06-24 18:58:48 UTC; 59s ago └─ ConditionFirstBoot=yes was not met Docs: man:systemd-firstboot(1) ○ systemd-network-generator.service - Generate network units from Kernel command line Loaded: loaded (/usr/lib/systemd/system/systemd-network-generator.service; disabled; preset: enabled) Active: inactive (dead) Docs: man:systemd-network-generator.service(8) × systemd-journald.service - Journal Service Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static) Drop-In: /usr/lib/systemd/system/systemd-journald.service.d └─nice.conf Active: failed (Result: exit-code) since Mon 2024-06-24 18:58:48 UTC; 1min 0s ago Invocation: 7caace7a15c749f3a86fb15fcfb94dff TriggeredBy: × systemd-journald-dev-log.socket × systemd-journald.socket ○ systemd-journald-audit.socket Docs: man:systemd-journald.service(8) man:journald.conf(5) Process: 124 ExecStart=/usr/lib/systemd/systemd-journald (code=exited, status=243/CREDENTIALS) Main PID: 124 (code=exited, status=243/CREDENTIALS) FD Store: 0 (limit: 4224) × systemd-sysctl.service - Apply Kernel Variables Loaded: loaded (/usr/lib/systemd/system/systemd-sysctl.
[Touch-packages] [Bug 1677863] Re: Missing dep8 tests
It migrated, closing bug. https://launchpad.net/ubuntu/+source/heimdal/7.8.git20221117.28daf24+dfsg-8ubuntu1 ** Changed in: heimdal (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 heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1677863 Title: Missing dep8 tests Status in heimdal package in Ubuntu: Fix Released Bug description: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 As of March 29, 2017, this source package did not contain dep8 tests in the current development release of Ubuntu, named Zesty. This was determined by running `pull-lp-source heimdal zesty` and then checking for the existence of 'debian/tests/' and 'debian/tests/control'. Test automation is essential to higher levels of quality and confidence in updates to packages. dep8 tests [1] specify how automatic testing can be integrated into packages and then run by package maintainers before new uploads. This defect is to report the absence of these tests and to report the opportunity as a potential item for development by both new and experienced contributors. [1] http://packaging.ubuntu.com/html/auto-pkg-test.html affects ubuntu/heimdal status new importance wishlist tag needs-dep8 - --- Joshua Powers Ubuntu Server Canonical Ltd -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJY3YANAAoJEIP8BxPaZgwlu24P/iJX01lyOO5vUdzYTOvjqNTF dGfAICBhOjkiHKMTa56e1VutrufBipgPZVdXAzou9fLb18SMBPH8SP5/iSk3GrCD 3IYIqY/+c+rQg/dVGWEpXOMpop8r+2d1IGarmy3PZuFvVJI34dskSkCBqW2OlHz+ unQ522qfDqfZ/8rq1xKspB/Vi7kbKV0uYenpgOhs5Vlb8nfWrHv1Zm+6lOnI42WJ r2+Hc1bb6snzKsYPgL6qigouHK4vsZjbWIugTaHalOQpm8R865Q8XSS+Skb2nGDp Ql2ULalPqERQRDOUtCpPaqZgB1iVlHApCRgH5baSh1a9WMraHoLlZLP/uRL6s4wC ThzeCGT2qJwSkESc/QE5iPtEx50+Kx8JVJgXxdjEArgVtHZERJ36U2FIzJE94uNG AiAOcvIjOTwHRqEQngPFtI+XskuKP2WeO5PbwgqgH51fi1LiNIovN1IALYZxsnhz 2qnorVpeJceVDXavgYiaWvPqiGh1EqXDIyqTdjT3r9cE+OjQMJV53SJk16wB6SyH 8E4GsWiazbSTvaAM5mWK7rFZh7vMcIDK8MpqVPxbgQrwV36DFXLyNVr/8eIvpO8G Gsk2UHxLdm4tPp7/Vkz9eBRhnP6fH6TTOpaKWPsn222m2LsnMS6gjXZMoIS4Pv0j KJoEHC3RRqOctkLd03Ck =mrOm -END PGP SIGNATURE- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1677863/+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 2074097] Re: DEP8 failing because of missing includedir support
It migrated, closing bug. https://launchpad.net/ubuntu/+source/heimdal/7.8.git20221117.28daf24+dfsg-8ubuntu1 ** Changed in: heimdal (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 heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2074097 Title: DEP8 failing because of missing includedir support Status in heimdal package in Ubuntu: Fix Released Bug description: The new DEP8 test I added to heimdal is failing because of hostname issues: 117s autopkgtest [13:23:24]: test kinit: [--- 117s ## Adding includedir directive to /etc/krb5.conf 117s 117s ## Creating /etc/krb5.conf.d/autopkgtest.conf 117s 117s ## Stoping heimdal-kdc.service and cleaning up DB directory 117s 117s ## Stashing key 117s kstash: hdb_add_master_key: unable to find realm of host autopkgtest 117s autopkgtest [13:23:24]: test kinit: ---] 1. https://autopkgtest.ubuntu.com/results/autopkgtest-oracular/oracular/amd64/h/heimdal/20240725_132342_8fd69@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2074097/+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 1677863] Re: Missing dep8 tests
New tests passing. Just waiting for it to migrate, and then this bug can be marked as fix released. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1677863 Title: Missing dep8 tests Status in heimdal package in Ubuntu: Fix Committed Bug description: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 As of March 29, 2017, this source package did not contain dep8 tests in the current development release of Ubuntu, named Zesty. This was determined by running `pull-lp-source heimdal zesty` and then checking for the existence of 'debian/tests/' and 'debian/tests/control'. Test automation is essential to higher levels of quality and confidence in updates to packages. dep8 tests [1] specify how automatic testing can be integrated into packages and then run by package maintainers before new uploads. This defect is to report the absence of these tests and to report the opportunity as a potential item for development by both new and experienced contributors. [1] http://packaging.ubuntu.com/html/auto-pkg-test.html affects ubuntu/heimdal status new importance wishlist tag needs-dep8 - --- Joshua Powers Ubuntu Server Canonical Ltd -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJY3YANAAoJEIP8BxPaZgwlu24P/iJX01lyOO5vUdzYTOvjqNTF dGfAICBhOjkiHKMTa56e1VutrufBipgPZVdXAzou9fLb18SMBPH8SP5/iSk3GrCD 3IYIqY/+c+rQg/dVGWEpXOMpop8r+2d1IGarmy3PZuFvVJI34dskSkCBqW2OlHz+ unQ522qfDqfZ/8rq1xKspB/Vi7kbKV0uYenpgOhs5Vlb8nfWrHv1Zm+6lOnI42WJ r2+Hc1bb6snzKsYPgL6qigouHK4vsZjbWIugTaHalOQpm8R865Q8XSS+Skb2nGDp Ql2ULalPqERQRDOUtCpPaqZgB1iVlHApCRgH5baSh1a9WMraHoLlZLP/uRL6s4wC ThzeCGT2qJwSkESc/QE5iPtEx50+Kx8JVJgXxdjEArgVtHZERJ36U2FIzJE94uNG AiAOcvIjOTwHRqEQngPFtI+XskuKP2WeO5PbwgqgH51fi1LiNIovN1IALYZxsnhz 2qnorVpeJceVDXavgYiaWvPqiGh1EqXDIyqTdjT3r9cE+OjQMJV53SJk16wB6SyH 8E4GsWiazbSTvaAM5mWK7rFZh7vMcIDK8MpqVPxbgQrwV36DFXLyNVr/8eIvpO8G Gsk2UHxLdm4tPp7/Vkz9eBRhnP6fH6TTOpaKWPsn222m2LsnMS6gjXZMoIS4Pv0j KJoEHC3RRqOctkLd03Ck =mrOm -END PGP SIGNATURE- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1677863/+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 2074097] Re: DEP8 failing because of missing includedir support
And the test is passing now. Marking as fix committed pending migration. ** Changed in: heimdal (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2074097 Title: DEP8 failing because of missing includedir support Status in heimdal package in Ubuntu: Fix Committed Bug description: The new DEP8 test I added to heimdal is failing because of hostname issues: 117s autopkgtest [13:23:24]: test kinit: [--- 117s ## Adding includedir directive to /etc/krb5.conf 117s 117s ## Creating /etc/krb5.conf.d/autopkgtest.conf 117s 117s ## Stoping heimdal-kdc.service and cleaning up DB directory 117s 117s ## Stashing key 117s kstash: hdb_add_master_key: unable to find realm of host autopkgtest 117s autopkgtest [13:23:24]: test kinit: ---] 1. https://autopkgtest.ubuntu.com/results/autopkgtest-oracular/oracular/amd64/h/heimdal/20240725_132342_8fd69@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2074097/+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 2074097] Re: DEP8 failing because of missing includedir support
Fixed in https://launchpad.net/ubuntu/+source/heimdal/7.8.git20221117.28daf24+dfsg-7ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2074097 Title: DEP8 failing because of missing includedir support Status in heimdal package in Ubuntu: Fix Committed Bug description: The new DEP8 test I added to heimdal is failing because of hostname issues: 117s autopkgtest [13:23:24]: test kinit: [--- 117s ## Adding includedir directive to /etc/krb5.conf 117s 117s ## Creating /etc/krb5.conf.d/autopkgtest.conf 117s 117s ## Stoping heimdal-kdc.service and cleaning up DB directory 117s 117s ## Stashing key 117s kstash: hdb_add_master_key: unable to find realm of host autopkgtest 117s autopkgtest [13:23:24]: test kinit: ---] 1. https://autopkgtest.ubuntu.com/results/autopkgtest-oracular/oracular/amd64/h/heimdal/20240725_132342_8fd69@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2074097/+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 2076542] Re: FTBFS with autoconf 2.72
** Bug watch added: Debian Bug tracker #1078494 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078494 ** Also affects: heimdal (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078494 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2076542 Title: FTBFS with autoconf 2.72 Status in heimdal package in Ubuntu: In Progress Status in heimdal package in Debian: Unknown Bug description: checking for gcc options needed to detect all undeclared functions... cannot detect configure: error: in '/home/ubuntu/git/packages/heimdal/heimdal': configure: error: cannot make gcc report undeclared builtins See 'config.log' for more details and configure:19563: gcc -c -g -O2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix-map=/home/ubuntu/git/packages/heimdal/heimdal=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fdebug-prefix-map=/home/ubuntu/git/packages/heimdal/heimdal=/usr/src/heimdal-7.8.git20221117.28daf24+dfsg-7ubuntu1 -fno-builtin -Wdate-time -D_FORTIFY_SOURCE=3 -D_LARGE_FILES= -D_FILE_OFFSET_BITS= conftest.c >&5 In file included from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, from /usr/include/limits.h:26, from /usr/lib/gcc/x86_64-linux-gnu/14/include/limits.h:210, from /usr/lib/gcc/x86_64-linux-gnu/14/include/syslimits.h:7, from /usr/lib/gcc/x86_64-linux-gnu/14/include/limits.h:34, from conftest.c:50: /usr/include/features.h:398:52: error: operator '&&' has no right operand 398 | #if defined _FILE_OFFSET_BITS && _FILE_OFFSET_BITS == 64 |^~ conftest.c:41:16: error: duplicate 'unsigned' 41 | #define size_t unsigned int |^~~~ conftest.c:41:25: error: two or more data types in declaration specifiers 41 | #define size_t unsigned int | ^~~ Looks like _FILE_OFFSET_BITS is empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2076542/+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 2076542] Re: FTBFS with autoconf 2.72
** Changed in: heimdal (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: heimdal (Ubuntu) Status: Triaged => In Progress ** Tags added: server-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2076542 Title: FTBFS with autoconf 2.72 Status in heimdal package in Ubuntu: In Progress Status in heimdal package in Debian: Unknown Bug description: checking for gcc options needed to detect all undeclared functions... cannot detect configure: error: in '/home/ubuntu/git/packages/heimdal/heimdal': configure: error: cannot make gcc report undeclared builtins See 'config.log' for more details and configure:19563: gcc -c -g -O2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix-map=/home/ubuntu/git/packages/heimdal/heimdal=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fdebug-prefix-map=/home/ubuntu/git/packages/heimdal/heimdal=/usr/src/heimdal-7.8.git20221117.28daf24+dfsg-7ubuntu1 -fno-builtin -Wdate-time -D_FORTIFY_SOURCE=3 -D_LARGE_FILES= -D_FILE_OFFSET_BITS= conftest.c >&5 In file included from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, from /usr/include/limits.h:26, from /usr/lib/gcc/x86_64-linux-gnu/14/include/limits.h:210, from /usr/lib/gcc/x86_64-linux-gnu/14/include/syslimits.h:7, from /usr/lib/gcc/x86_64-linux-gnu/14/include/limits.h:34, from conftest.c:50: /usr/include/features.h:398:52: error: operator '&&' has no right operand 398 | #if defined _FILE_OFFSET_BITS && _FILE_OFFSET_BITS == 64 |^~ conftest.c:41:16: error: duplicate 'unsigned' 41 | #define size_t unsigned int |^~~~ conftest.c:41:25: error: two or more data types in declaration specifiers 41 | #define size_t unsigned int | ^~~ Looks like _FILE_OFFSET_BITS is empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2076542/+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 2076542] [NEW] FTBFS with autoconf 2.72
Public bug reported: checking for gcc options needed to detect all undeclared functions... cannot detect configure: error: in '/home/ubuntu/git/packages/heimdal/heimdal': configure: error: cannot make gcc report undeclared builtins See 'config.log' for more details and configure:19563: gcc -c -g -O2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix-map=/home/ubuntu/git/packages/heimdal/heimdal=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fdebug-prefix-map=/home/ubuntu/git/packages/heimdal/heimdal=/usr/src/heimdal-7.8.git20221117.28daf24+dfsg-7ubuntu1 -fno-builtin -Wdate-time -D_FORTIFY_SOURCE=3 -D_LARGE_FILES= -D_FILE_OFFSET_BITS= conftest.c >&5 In file included from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, from /usr/include/limits.h:26, from /usr/lib/gcc/x86_64-linux-gnu/14/include/limits.h:210, from /usr/lib/gcc/x86_64-linux-gnu/14/include/syslimits.h:7, from /usr/lib/gcc/x86_64-linux-gnu/14/include/limits.h:34, from conftest.c:50: /usr/include/features.h:398:52: error: operator '&&' has no right operand 398 | #if defined _FILE_OFFSET_BITS && _FILE_OFFSET_BITS == 64 |^~ conftest.c:41:16: error: duplicate 'unsigned' 41 | #define size_t unsigned int |^~~~ conftest.c:41:25: error: two or more data types in declaration specifiers 41 | #define size_t unsigned int | ^~~ Looks like _FILE_OFFSET_BITS is empty ** Affects: heimdal (Ubuntu) Importance: High Status: Triaged ** Tags: ftbfs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2076542 Title: FTBFS with autoconf 2.72 Status in heimdal package in Ubuntu: Triaged Bug description: checking for gcc options needed to detect all undeclared functions... cannot detect configure: error: in '/home/ubuntu/git/packages/heimdal/heimdal': configure: error: cannot make gcc report undeclared builtins See 'config.log' for more details and configure:19563: gcc -c -g -O2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix-map=/home/ubuntu/git/packages/heimdal/heimdal=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fdebug-prefix-map=/home/ubuntu/git/packages/heimdal/heimdal=/usr/src/heimdal-7.8.git20221117.28daf24+dfsg-7ubuntu1 -fno-builtin -Wdate-time -D_FORTIFY_SOURCE=3 -D_LARGE_FILES= -D_FILE_OFFSET_BITS= conftest.c >&5 In file included from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, from /usr/include/limits.h:26, from /usr/lib/gcc/x86_64-linux-gnu/14/include/limits.h:210, from /usr/lib/gcc/x86_64-linux-gnu/14/include/syslimits.h:7, from /usr/lib/gcc/x86_64-linux-gnu/14/include/limits.h:34, from conftest.c:50: /usr/include/features.h:398:52: error: operator '&&' has no right operand 398 | #if defined _FILE_OFFSET_BITS && _FILE_OFFSET_BITS == 64 |^~ conftest.c:41:16: error: duplicate 'unsigned' 41 | #define size_t unsigned int |^~~~ conftest.c:41:25: error: two or more data types in declaration specifiers 41 | #define size_t unsigned int | ^~~ Looks like _FILE_OFFSET_BITS is empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2076542/+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 2074097] Re: DEP8 failing because of missing includedir support
** Summary changed: - DEP8 failing because of hostname issues + DEP8 failing because of missing includedir support -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2074097 Title: DEP8 failing because of missing includedir support Status in heimdal package in Ubuntu: Triaged Bug description: The new DEP8 test I added to heimdal is failing because of hostname issues: 117s autopkgtest [13:23:24]: test kinit: [--- 117s ## Adding includedir directive to /etc/krb5.conf 117s 117s ## Creating /etc/krb5.conf.d/autopkgtest.conf 117s 117s ## Stoping heimdal-kdc.service and cleaning up DB directory 117s 117s ## Stashing key 117s kstash: hdb_add_master_key: unable to find realm of host autopkgtest 117s autopkgtest [13:23:24]: test kinit: ---] 1. https://autopkgtest.ubuntu.com/results/autopkgtest-oracular/oracular/amd64/h/heimdal/20240725_132342_8fd69@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2074097/+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 2060666] Re: [SRU] Memory leak in krb5 version 1.17
Same patch as before, just with a new name ;) ** Tags removed: verification-done verification-done-focal ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/2060666 Title: [SRU] Memory leak in krb5 version 1.17 Status in krb5 package in Ubuntu: Fix Released Status in krb5 source package in Focal: Fix Committed Bug description: [ Impact ] Commit https://github.com/krb5/krb5/commit/1cd2821c19b2b95e39d5fc2f451a035585a40fa5 altered the memory management of krb5_gss_inquire_cred(), introducing defcred to act as an owner pointer when the function must acquire a default credential. The commit neglected to update the code to release the default cred along the successful path. The old code does not trigger because cred_handle is now reassigned, so the default credential is leaked. Resulting gradual increase in memory usage (memory leak) and eventual crash. [ Test Plan ] Setup 3 VMs: 1. Windows Server act as Domain controller (AD) 2. Windows machine AD Joined with Ostress installed. (Ostress is part of RML utilities https://learn.microsoft.com/en-us/troubleshoot/sql/tools/replay-markup-language-utility) 3. SQL on Linux AD Joined ( configuration steps https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-ad-auth-adutil-tutorial?view=sql-server-ver16) On the Machine with OStress create a file (name it disconnect.ini) with the following content under the same folder “C:\Program Files\Microsoft Corporation\RMLUtils” where OStress is installed. disconnect.ini == [Connection Options] LoginTimeout=30 QuotedIdentifier=Off AutocommitMode=On DisconnectPct=100.0 MaxThreadErrors=0 [Query Options] NoSQLBindCol=Off NoResultDisplay=Off PrepareExecute=Off ExecuteAsync=Off RollbackOnCancel=Off QueryTimeout=0 QueryDelay=0 MaxRetries=0 BatchDisconnectPct=0.0 CancelPct=0.00 CancelDelay=0 CancelDelayMin=0 CursorType= CursorConcurrency= RowFetchDelay=0 [Replay Options] Sequencing Options=global sequence ::Sequencing Options=global sequence, dtc replay DTC Timeout= DTC Machine=(local) Playback Coordinator=(local) StartSeqNum= StopSeqNum= TimeoutFactor=1.0 Run the following command to start the load using Ostress, change Server name (-S) accordingly and the number of threads (-n) as needed. Start 4 different CMD consoles and use the following different commands for each CMD window: 1. ostress.exe -E -S -Q"select * from sys.all_objects" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log01 -T146 2. ostress.exe -E -S -Q"select * from sys.all_views" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log02 -T146 3. ostress.exe -E -S -Q"select * from sys.all_columns" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log03 -T146 4. ostress.exe -E -S -Q"select * from sys.all_parameters" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log04 -T146 After a run of about 5 hours, the memory usage for this is expected to be around 5G with the fix. Without the fix, it was observed that it reached around ~22G in 5 hours. Hence the increase in memory usage can be observed if the ostress.exe programs are let to run longer. [ Where problems could occur ] The fix may not fix the memory leak or could result in releasing the memory early in a different code path, and thus resulting in crashes. A mitigating fact is that the fix has been in Ubuntu since at least 22.04 and they do not exhibit any issues. Likewise I've previously provided the fix in a PPA https://launchpad.net/~pponnuvel/+archive/ubuntu/krb5-focal to user who's been hit by this issue. They've tested and confirmed it fixes the memory leak. [ Other Info ] The commit https://github.com/krb5/krb5/commit/098f874f3b50dd2c46c0a574677324b5f6f3a1a8 fixes the leak. The fix has been included in newer krb5 releases (Jammy, and Noble have the releases with the fix). Bionic doesn't have the commit the introduced the memory leak in the first place. So this will be a Focal-only backport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/2060666/+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 2060666] Please test proposed package
Hello Ponnuvel, or anyone else affected, Accepted krb5 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/krb5/1.17-6ubuntu4.7 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- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. 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 krb5 in Ubuntu. https://bugs.launchpad.net/bugs/2060666 Title: [SRU] Memory leak in krb5 version 1.17 Status in krb5 package in Ubuntu: Fix Released Status in krb5 source package in Focal: Fix Committed Bug description: [ Impact ] Commit https://github.com/krb5/krb5/commit/1cd2821c19b2b95e39d5fc2f451a035585a40fa5 altered the memory management of krb5_gss_inquire_cred(), introducing defcred to act as an owner pointer when the function must acquire a default credential. The commit neglected to update the code to release the default cred along the successful path. The old code does not trigger because cred_handle is now reassigned, so the default credential is leaked. Resulting gradual increase in memory usage (memory leak) and eventual crash. [ Test Plan ] Setup 3 VMs: 1. Windows Server act as Domain controller (AD) 2. Windows machine AD Joined with Ostress installed. (Ostress is part of RML utilities https://learn.microsoft.com/en-us/troubleshoot/sql/tools/replay-markup-language-utility) 3. SQL on Linux AD Joined ( configuration steps https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-ad-auth-adutil-tutorial?view=sql-server-ver16) On the Machine with OStress create a file (name it disconnect.ini) with the following content under the same folder “C:\Program Files\Microsoft Corporation\RMLUtils” where OStress is installed. disconnect.ini == [Connection Options] LoginTimeout=30 QuotedIdentifier=Off AutocommitMode=On DisconnectPct=100.0 MaxThreadErrors=0 [Query Options] NoSQLBindCol=Off NoResultDisplay=Off PrepareExecute=Off ExecuteAsync=Off RollbackOnCancel=Off QueryTimeout=0 QueryDelay=0 MaxRetries=0 BatchDisconnectPct=0.0 CancelPct=0.00 CancelDelay=0 CancelDelayMin=0 CursorType= CursorConcurrency= RowFetchDelay=0 [Replay Options] Sequencing Options=global sequence ::Sequencing Options=global sequence, dtc replay DTC Timeout= DTC Machine=(local) Playback Coordinator=(local) StartSeqNum= StopSeqNum= TimeoutFactor=1.0 Run the following command to start the load using Ostress, change Server name (-S) accordingly and the number of threads (-n) as needed. Start 4 different CMD consoles and use the following different commands for each CMD window: 1. ostress.exe -E -S -Q"select * from sys.all_objects" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log01 -T146 2. ostress.exe -E -S -Q"select * from sys.all_views" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log02 -T146 3. ostress.exe -E -S -Q"select * from sys.all_columns" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log03 -T146 4. ostress.exe -E -S -Q"select * from sys.all_parameters" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log04 -T146 After a run of about 5 hours, the memory usage for this is expected to be around 5G with the fix. Without the fix, it was observed that it reached around ~22G in 5 hours. Hence the increase in memory usage can be observed if the ostress.exe programs are let to run longer. [ Where problems could occur ] The fix may not fix the memory leak or could result in releasing the memory early in a different code path, and thus resulting in crashes. A mitigating fact is that the fix has been in Ubuntu since at least 22.04 and they do not exhibit any issues. Likewise I've previously provided the fix in a PPA https://launchpad.net/~pponnuvel/+archive/ubuntu/krb5-focal to user who's been hit by this issue. They've tested and confirmed it fixes the memory leak. [ Other Info ] The com
[Touch-packages] [Bug 2066995] Update Released
The verification of the Stable Release Update for apport has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2066995 Title: /var/crash has perm 1777 (was: apport-gtk keeps prompting to report crashes in a loop) Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Noble: Fix Released Bug description: [ Impact ] On affected systems, Python crashes will be owned by the crashing group instead of whoopsie. This causes whoopsie to fail reading and uploading the crash report. So a lot of Python crashes were not reporting and keeping us blind. [ Test Plan ] 1. Reconstruct the problem by setting the permission of /var/crash to 1777. 2. Upgrade Apport to the fixed version 3. Verify that /var/crash has the permission 3777 after the update. 4. Run and crash a random Python script (needs to be from a Ubuntu package) 5. Verify that the Python crash was correctly uploaded. [ Where problems could occur ] The fix touched the /var/crash permission and the apport.service startup code. This might lead to failures on custom setup (despite using similar postinst code than whoopsie). This fix might still not address the initial bug report of reporting crashes in a loop. In this case a follow-up bug report should be started. [ Original report ] /var/crash has the following contents: -rw-r- 1 vorlon vorlon 107490 May 23 16:05 _usr_bin_gourmand.1000.crash -rw-rw-r-- 1 vorlon vorlon0 May 23 16:06 _usr_bin_gourmand.1000.upload -rw--- 1 whoopsie whoopsie 5 May 23 16:07 _usr_bin_gourmand.1000.uploaded -rw-r- 1 vorlon vorlon23647 May 23 13:57 _usr_bin_python-argcomplete-check-easy-install-script.1000.crash -rw-rw-r-- 1 vorlon vorlon0 May 23 13:59 _usr_bin_python-argcomplete-check-easy-install-script.1000.upload -rw--- 1 whoopsie whoopsie 5 May 23 13:59 _usr_bin_python-argcomplete-check-easy-install-script.1000.uploaded As seen, the .upload / .uploaded files were created within 2 minutes of each of the crashes. But after submitting the crash report for /usr/bin/python-argcomplete- check-easy-install-script, I left my desktop for a while. I came back to find at least TWENTY dialogs prompting me to submit the same crash report. The only way to stop the system from creating more prompts is to remove these files from disk. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: apport 2.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportLog: ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 23 16:06:43 2024 InstallationDate: Installed on 2019-12-23 (1613 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to noble on 2024-05-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2066995/+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 2067120] Update Released
The verification of the Stable Release Update for apport has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2067120 Title: apport-retrace crashed with subprocess.CalledProcessError in check_call(): Command '['dpkg', '-x', '/srv/vms/apport-retrace/Ubuntu 24.04/apt/var/cache/apt/archives//base-files_13ubuntu9_amd64.deb', '/tmp/apport_sandbox_zj9wto2z']' returned non-zero exit status 2. Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Noble: Fix Released Bug description: [ Impact ] I'm finding it impossible to retrace any crashes with the version of apport packaged in noble or with upstream commit id adfe3698731b69b0f19ca36ecca90d8e96001250. The retracing process ends with the following lines: Extracting downloaded debs... tar: ./lib: Cannot create symlink to ‘usr/lib’: File exists tar: Exiting with failure status due to previous errors dpkg-deb: error: tar subprocess returned error exit status 2 Traceback (most recent call last): File "/usr/bin/apport-retrace", line 696, in main() File "/usr/bin/apport-retrace", line 465, in main sandbox, cache, outdated_msg = apport.sandboxutils.make_sandbox( ^ File "/usr/lib/python3/dist-packages/apport/sandboxutils.py", line 227, in make_sandbox outdated_msg = packaging.install_packages( ^^^ File "/usr/lib/python3/dist-packages/apport/packaging_impl/apt_dpkg.py", line 1350, in install_packages subprocess.check_call(["dpkg", "-x", i.destfile, rootdir]) File "/usr/lib/python3.12/subprocess.py", line 413, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['dpkg', '-x', '/srv/vms/apport-retrace/Ubuntu 24.04/apt/var/cache/apt/archives//base-files_13ubuntu9_amd64.deb', '/tmp/apport_sandbox_zj9wto2z']' returned non-zero exit status 2. I've tried cleaning the cache, /srv/vms/apport-retrace/Ubuntu 24.04/, but the retracing process continues to fail. The crashes I'm trying to retrace have been uploaded to Launchpad and still have the coredumps attached but I'd be happy to subscribe an apport developer to them. [ Test Plan ] The fix for this bug adds four new system test cases. These system test cases are run in the autopkgtest. Check that those four test cases succeed on amd64 on autopkgtest. [ Where problems could occur ] The fix touches apport-retrace. This binary is not installed by default, but is used by us to retrace users reports and by users to retrace their own crashes. This fix might reveal new issues with apport-retrace and it will hopefully help retracing more bugs on Launchpad. This should lead to more bug reports. [ Other Info ] ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: apport-retrace 2.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset wl nvidia zfs ApportLog: ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 24 16:03:45 2024 ExecutablePath: /usr/bin/apport-retrace ExecutableTimestamp: 1713871810 InstallationDate: Installed on 2018-08-10 (2114 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterpreterPath: /usr/bin/python3.12 JournalErrors: -- No entries -- PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/apport-retrace -v -S /home/bdmurray/source-trees/daisy/watchtower-archive/ -C /srv/vms/apport-retrace --verbose --gdb-sandbox --auth /home/bdmurray/.launchpadlib/retracer-credentials-lpnet --confirm 2062390 ProcCwd: /home/bdmurray/source-trees/apport/apport Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonArgs: ['/usr/bin/apport-retrace', '-v', '-S', '/home/bdmurray/source-trees/daisy/watchtower-archive/', '-C', '/srv/vms/apport-retrace', '--verbose', '--gdb-sandbox', '--auth', '/home/bdmurray/.launchpadlib/retracer-credentials-lpnet', '--confirm', '2062390'] PythonDetails: N/A SourcePackage: apport Title: apport-retrace crashed with subprocess.CalledProcessError in check_call(): Command '['dpkg', '-x', '/srv/vms/apport-retrace/Ubuntu 24.04/apt/var/cache/
[Touch-packages] [Bug 2067775] Re: subiquity package-hook is outdated
Ah, I forgot the --override-freeze flag -- 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/2067775 Title: subiquity package-hook is outdated Status in apport package in Ubuntu: Fix Released Status in apport source package in Jammy: Fix Released Status in apport source package in Noble: Fix Released Bug description: [Impact] The Subiquity package hook in Apport has not been updated to collect the type of information we are typically interested in (e.g. /var/log/installer/\*). This means users who run `ubuntu-bug subiquity` from the terminal will not automatically collect relevant information to attach to their bug reports. This upload fixes this by updating Subiquity's package hook to collect logs and information typically used for debugging Subiquity bugs. This fix needs to be SRUd to Noble and Jammy so that users performing these installs can run `ubuntu-bug subiquity` and collect relevant information. [Test Plan] The test plan is focused on testing the behavior of apport within the live installation environment, where we primarily expect users to submit bug reports from. Thus the test plan is split into three different test plans: Two for Desktop images and one for Server. For Noble, all three test scenarios are relevant. For Jammy, it is only necessary to test Server since the Desktop installer for Jammy is not Subiquity based. Desktop - Manual: 1) Download the latest Noble Desktop ISO [1]. 2) Begin an installation using the media you downloaded. You may progress the install as far as you like, with the following restrictions: (1) At minimum you need wait for the first screen to show up and (2) at most you may allow the install to finish but do not allow the system to restart (you need to be in the live-environment to proceed). 3) Open a terminal (ctl + alt + t) 4) Enable proposed[4] and update apport 5) Run the following command "APPORT_LAUNCHPAD_INSTANCE=qastaging ubuntu-bug subiquity" 6) 4 authorization prompts will display, requesting access to collect information from the system. Allow all of them. 7) Inspect the fields of the report and ensure that none report "permission denied" or similar. 8) Click "Send" on the resulting dialog to send the report. Firefox will open up to finish filling out the bug information on launchpad. 9) Log in and enter anything as the title and hit continue. Click "No, I need to report a new bug" if necessary 10) Enter anything in the "further information section". Ensure that the field below this section, titled "This bug contains information that is", is marked "Private" by default. 11) You can now submit the bug and inspect the automatically filled description for further errors in the report. (Errors messages are typically short enough to show up in the body of the bug description while larger attachments with real information end up as attachments) Desktop - Automatic: 1) Download the latest Noble Desktop ISO [1]. 2) Begin an installation using the media you downloaded. You may progress the install as far as you like, with the following restrictions: (1) At minimum you need wait for the first screen to show up and (2) at most you may allow the install to finish but do not allow the system to restart (you need to be in the live-environment to proceed). 3) Open a terminal (ctl + alt + t) 4) Enable proposed[4] and update apport 5) Create a fake subiquity crash file: sudo printf "Package: subiquity\nProblemType: crash\n" > /var/crash/test.crash 6) authorize the collection of information 7) Inspect the generated data. Ensure: - The key LaunchpadPrivate exists - There are no "permission denied" errors - Do NOT submit the report Server (Jammy or Noble): 1) Download the latest Server ISO for the release you have chosen to verify (Noble[2] or Jammy[3]) 2) Begin an installation using the media you downloaded. You may progress the install as far as you like, with the following restrictions: (1) At minimum you need wait for the first screen to show up and (2) at most you may allow the install to finish but do not allow the system to restart (you need to be in the live-environment to proceed). 3) Enter the debug shell (F2 or ctrl+z) 4) Enable proposed[4] and update apport 5) Run the following command "sudo APPORT_LAUNCHPAD_INSTANCE=qastaging ubuntu-bug subiquity" (sudo is required) 6) Apport will ask for which matching application you want to report against. Select option 2, which should read "subiquity (1234 of snap /snap/subiquity/1234 of version $release_ver) deb package" 7) Now apport should ask how you want to proceed. Select "S: Send report" 8) Once the upload is complete, open the URL in a browser on another machine to complete the installation. 9) Log in and enter anything as the title and
[Touch-packages] [Bug 2067775] Update Released
The verification of the Stable Release Update for apport has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2067775 Title: subiquity package-hook is outdated Status in apport package in Ubuntu: Fix Released Status in apport source package in Jammy: Fix Released Status in apport source package in Noble: Fix Released Bug description: [Impact] The Subiquity package hook in Apport has not been updated to collect the type of information we are typically interested in (e.g. /var/log/installer/\*). This means users who run `ubuntu-bug subiquity` from the terminal will not automatically collect relevant information to attach to their bug reports. This upload fixes this by updating Subiquity's package hook to collect logs and information typically used for debugging Subiquity bugs. This fix needs to be SRUd to Noble and Jammy so that users performing these installs can run `ubuntu-bug subiquity` and collect relevant information. [Test Plan] The test plan is focused on testing the behavior of apport within the live installation environment, where we primarily expect users to submit bug reports from. Thus the test plan is split into three different test plans: Two for Desktop images and one for Server. For Noble, all three test scenarios are relevant. For Jammy, it is only necessary to test Server since the Desktop installer for Jammy is not Subiquity based. Desktop - Manual: 1) Download the latest Noble Desktop ISO [1]. 2) Begin an installation using the media you downloaded. You may progress the install as far as you like, with the following restrictions: (1) At minimum you need wait for the first screen to show up and (2) at most you may allow the install to finish but do not allow the system to restart (you need to be in the live-environment to proceed). 3) Open a terminal (ctl + alt + t) 4) Enable proposed[4] and update apport 5) Run the following command "APPORT_LAUNCHPAD_INSTANCE=qastaging ubuntu-bug subiquity" 6) 4 authorization prompts will display, requesting access to collect information from the system. Allow all of them. 7) Inspect the fields of the report and ensure that none report "permission denied" or similar. 8) Click "Send" on the resulting dialog to send the report. Firefox will open up to finish filling out the bug information on launchpad. 9) Log in and enter anything as the title and hit continue. Click "No, I need to report a new bug" if necessary 10) Enter anything in the "further information section". Ensure that the field below this section, titled "This bug contains information that is", is marked "Private" by default. 11) You can now submit the bug and inspect the automatically filled description for further errors in the report. (Errors messages are typically short enough to show up in the body of the bug description while larger attachments with real information end up as attachments) Desktop - Automatic: 1) Download the latest Noble Desktop ISO [1]. 2) Begin an installation using the media you downloaded. You may progress the install as far as you like, with the following restrictions: (1) At minimum you need wait for the first screen to show up and (2) at most you may allow the install to finish but do not allow the system to restart (you need to be in the live-environment to proceed). 3) Open a terminal (ctl + alt + t) 4) Enable proposed[4] and update apport 5) Create a fake subiquity crash file: sudo printf "Package: subiquity\nProblemType: crash\n" > /var/crash/test.crash 6) authorize the collection of information 7) Inspect the generated data. Ensure: - The key LaunchpadPrivate exists - There are no "permission denied" errors - Do NOT submit the report Server (Jammy or Noble): 1) Download the latest Server ISO for the release you have chosen to verify (Noble[2] or Jammy[3]) 2) Begin an installation using the media you downloaded. You may progress the install as far as you like, with the following restrictions: (1) At minimum you need wait for the first screen to show up and (2) at most you may allow the install to finish but do not allow the system to restart (you need to be in the live-environment to proceed). 3) Enter the debug shell (F2 or ctrl+z) 4) Enable proposed[4] and update apport 5) Run the following command "sudo APPORT_LAUNCHPAD_INSTANCE=qastaging ubuntu-bug subiquity" (sudo is required) 6) Apport w
[Touch-packages] [Bug 2067775] Re: subiquity package-hook is outdated
I released noble before, but I don't see a comment here. Maybe LP timed out (it did for another release I did earlier). I'll wait a bit, and if nothing shows up here, I'll just release noble again. -- 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/2067775 Title: subiquity package-hook is outdated Status in apport package in Ubuntu: Fix Released Status in apport source package in Jammy: Fix Released Status in apport source package in Noble: Fix Released Bug description: [Impact] The Subiquity package hook in Apport has not been updated to collect the type of information we are typically interested in (e.g. /var/log/installer/\*). This means users who run `ubuntu-bug subiquity` from the terminal will not automatically collect relevant information to attach to their bug reports. This upload fixes this by updating Subiquity's package hook to collect logs and information typically used for debugging Subiquity bugs. This fix needs to be SRUd to Noble and Jammy so that users performing these installs can run `ubuntu-bug subiquity` and collect relevant information. [Test Plan] The test plan is focused on testing the behavior of apport within the live installation environment, where we primarily expect users to submit bug reports from. Thus the test plan is split into three different test plans: Two for Desktop images and one for Server. For Noble, all three test scenarios are relevant. For Jammy, it is only necessary to test Server since the Desktop installer for Jammy is not Subiquity based. Desktop - Manual: 1) Download the latest Noble Desktop ISO [1]. 2) Begin an installation using the media you downloaded. You may progress the install as far as you like, with the following restrictions: (1) At minimum you need wait for the first screen to show up and (2) at most you may allow the install to finish but do not allow the system to restart (you need to be in the live-environment to proceed). 3) Open a terminal (ctl + alt + t) 4) Enable proposed[4] and update apport 5) Run the following command "APPORT_LAUNCHPAD_INSTANCE=qastaging ubuntu-bug subiquity" 6) 4 authorization prompts will display, requesting access to collect information from the system. Allow all of them. 7) Inspect the fields of the report and ensure that none report "permission denied" or similar. 8) Click "Send" on the resulting dialog to send the report. Firefox will open up to finish filling out the bug information on launchpad. 9) Log in and enter anything as the title and hit continue. Click "No, I need to report a new bug" if necessary 10) Enter anything in the "further information section". Ensure that the field below this section, titled "This bug contains information that is", is marked "Private" by default. 11) You can now submit the bug and inspect the automatically filled description for further errors in the report. (Errors messages are typically short enough to show up in the body of the bug description while larger attachments with real information end up as attachments) Desktop - Automatic: 1) Download the latest Noble Desktop ISO [1]. 2) Begin an installation using the media you downloaded. You may progress the install as far as you like, with the following restrictions: (1) At minimum you need wait for the first screen to show up and (2) at most you may allow the install to finish but do not allow the system to restart (you need to be in the live-environment to proceed). 3) Open a terminal (ctl + alt + t) 4) Enable proposed[4] and update apport 5) Create a fake subiquity crash file: sudo printf "Package: subiquity\nProblemType: crash\n" > /var/crash/test.crash 6) authorize the collection of information 7) Inspect the generated data. Ensure: - The key LaunchpadPrivate exists - There are no "permission denied" errors - Do NOT submit the report Server (Jammy or Noble): 1) Download the latest Server ISO for the release you have chosen to verify (Noble[2] or Jammy[3]) 2) Begin an installation using the media you downloaded. You may progress the install as far as you like, with the following restrictions: (1) At minimum you need wait for the first screen to show up and (2) at most you may allow the install to finish but do not allow the system to restart (you need to be in the live-environment to proceed). 3) Enter the debug shell (F2 or ctrl+z) 4) Enable proposed[4] and update apport 5) Run the following command "sudo APPORT_LAUNCHPAD_INSTANCE=qastaging ubuntu-bug subiquity" (sudo is required) 6) Apport will ask for which matching application you want to report against. Select option 2, which should read "subiquity (1234 of snap /snap/subiquity/1234 of version $release_ver) deb package" 7) Now apport should ask how you want to proceed. Select "S: Send report"
[Touch-packages] [Bug 2069360] Update Released
The verification of the Stable Release Update for apport has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2069360 Title: apport-autoreport.service fails if autoreporting is disabled Status in Apport: Fix Committed Status in apport package in Ubuntu: Fix Committed Status in apport source package in Noble: Fix Released Bug description: [ Impact ] apport-autoreport.service fails if auto-reporting is disabled: ``` $ systemctl status apport-autoreport.service × apport-autoreport.service - Process error reports when automatic reporting is enabled Loaded: loaded (/usr/lib/systemd/system/apport-autoreport.service; static) Active: failed (Result: exit-code) since Thu 2024-06-13 21:55:08 CEST; 1h 9min ago TriggeredBy: ● apport-autoreport.timer ● apport-autoreport.path Process: 1059564 ExecStart=/usr/share/apport/whoopsie-upload-all --timeout 20 (code=exited, status=1/FAILURE) Main PID: 1059564 (code=exited, status=1/FAILURE) CPU: 86ms Jun 13 21:55:08 host systemd[1]: Starting apport-autoreport.service - Process error reports when automatic reporting is enabled... Jun 13 21:55:08 host whoopsie-upload-all[1059564]: ERROR: whoopsie.path is not enabled Jun 13 21:55:08 host systemd[1]: apport-autoreport.service: Main process exited, code=exited, status=1/FAILURE Jun 13 21:55:08 host systemd[1]: apport-autoreport.service: Failed with result 'exit-code'. Jun 13 21:55:08 host systemd[1]: Failed to start apport-autoreport.service - Process error reports when automatic reporting is enabled. ``` This service failure might mislead user thinking that there is a problem. [ Test Plan ] 1. Disable auto-reporting in the system setting: * open gnome-control-center or unity-control-center * Switch to "Security & Privacy" panel * Select "Diagnosticts" tab * unselect "Send error reports to Canonical" 2. Produce a crash, e.g. by running divide-by-zero from chaos-marmosets 3. Check that apport-autoreport.service is failing as above 4. Upgrade Apport to the fixed version 5. Restart apport-autoreport.service 6. apport-autoreport.service should exit successfully [ Where problems could occur ] This code change touches the auto-reporting part. Failures there could lead to less bugs being forwarded to the error tracker. This might be noticeable when looking at the number of submissions. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2069360/+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 2072751] Update Released
The verification of the Stable Release Update for apport has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2072751 Title: The ubuntu-desktop-bootstrap hook isn't working Status in apport package in Ubuntu: Fix Committed Status in apport source package in Noble: Fix Released Bug description: * Impact The current ubuntu-desktop-bootstrap hook has some errors and isn't working properly as a result - it's reporting issues to https://launchpad.net/ubuntu-desktop- bootstrap which is the wrong project (bootstrap is the snap name but it's built from ubuntu-desktop-provision) - it's failing to attach the subiquity log since that one isn't user readable - the name of some of the curting files is incorrect * Test case - start a Noble desktop ISO - install the apport package update - do an installation, select custom partitioning and define a vfat partition to use for /boot (which is going to make the installer error out) - go through the other installer steps, keeping default - wait for the error screen to show - run $ ubuntu-bug ubuntu-desktop-installer - log into launchpad and submit the report The report should be sent against the ubuntu-desktop-provision project on launchpad and include ubuntu_bootstrap.log, subiquity-server- debug.log and curtin-install.log/curtin-error.tar * Regression potential The changes in the ubuntu-desktop-bootstrap hook and should impact only reporting against that component To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2072751/+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 2069360] Re: apport-autoreport.service fails if autoreporting is disabled
I got a committment that the oracular fix would be uploaded by tomorrow. -- 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/2069360 Title: apport-autoreport.service fails if autoreporting is disabled Status in Apport: Fix Committed Status in apport package in Ubuntu: Fix Committed Status in apport source package in Noble: Fix Committed Bug description: [ Impact ] apport-autoreport.service fails if auto-reporting is disabled: ``` $ systemctl status apport-autoreport.service × apport-autoreport.service - Process error reports when automatic reporting is enabled Loaded: loaded (/usr/lib/systemd/system/apport-autoreport.service; static) Active: failed (Result: exit-code) since Thu 2024-06-13 21:55:08 CEST; 1h 9min ago TriggeredBy: ● apport-autoreport.timer ● apport-autoreport.path Process: 1059564 ExecStart=/usr/share/apport/whoopsie-upload-all --timeout 20 (code=exited, status=1/FAILURE) Main PID: 1059564 (code=exited, status=1/FAILURE) CPU: 86ms Jun 13 21:55:08 host systemd[1]: Starting apport-autoreport.service - Process error reports when automatic reporting is enabled... Jun 13 21:55:08 host whoopsie-upload-all[1059564]: ERROR: whoopsie.path is not enabled Jun 13 21:55:08 host systemd[1]: apport-autoreport.service: Main process exited, code=exited, status=1/FAILURE Jun 13 21:55:08 host systemd[1]: apport-autoreport.service: Failed with result 'exit-code'. Jun 13 21:55:08 host systemd[1]: Failed to start apport-autoreport.service - Process error reports when automatic reporting is enabled. ``` This service failure might mislead user thinking that there is a problem. [ Test Plan ] 1. Disable auto-reporting in the system setting: * open gnome-control-center or unity-control-center * Switch to "Security & Privacy" panel * Select "Diagnosticts" tab * unselect "Send error reports to Canonical" 2. Produce a crash, e.g. by running divide-by-zero from chaos-marmosets 3. Check that apport-autoreport.service is failing as above 4. Upgrade Apport to the fixed version 5. Restart apport-autoreport.service 6. apport-autoreport.service should exit successfully [ Where problems could occur ] This code change touches the auto-reporting part. Failures there could lead to less bugs being forwarded to the error tracker. This might be noticeable when looking at the number of submissions. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2069360/+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 2072751] Re: The ubuntu-desktop-bootstrap hook isn't working
I got a committment that the oracular fix would be uploaded by tomorrow. -- 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/2072751 Title: The ubuntu-desktop-bootstrap hook isn't working Status in apport package in Ubuntu: Fix Committed Status in apport source package in Noble: Fix Committed Bug description: * Impact The current ubuntu-desktop-bootstrap hook has some errors and isn't working properly as a result - it's reporting issues to https://launchpad.net/ubuntu-desktop- bootstrap which is the wrong project (bootstrap is the snap name but it's built from ubuntu-desktop-provision) - it's failing to attach the subiquity log since that one isn't user readable - the name of some of the curting files is incorrect * Test case - start a Noble desktop ISO - install the apport package update - do an installation, select custom partitioning and define a vfat partition to use for /boot (which is going to make the installer error out) - go through the other installer steps, keeping default - wait for the error screen to show - run $ ubuntu-bug ubuntu-desktop-installer - log into launchpad and submit the report The report should be sent against the ubuntu-desktop-provision project on launchpad and include ubuntu_bootstrap.log, subiquity-server- debug.log and curtin-install.log/curtin-error.tar * Regression potential The changes in the ubuntu-desktop-bootstrap hook and should impact only reporting against that component To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2072751/+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 1974483] Update Released
The verification of the Stable Release Update for livecd-rootfs has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1974483 Title: autoinstall ssh:install-server:false is misleading in 22.04 Status in subiquity: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in livecd-rootfs source package in Jammy: Fix Committed Status in ubuntu-meta source package in Jammy: Fix Committed Bug description: [ Impact ] openssh-server is always installed to the target machine regardless of the user's explicit choice to not have it installed. Backporting the fix will allow image builds to pick up it up and become available for the next point release. The upload fixes the bug by removing ssh-import-id from the server- minimal seed and meta-package such that it's not part of the base layer copied over during install. [ Test Plan ] live images -- Test 1: 1. Download the latest server installer image from https://cdimage.ubuntu.com/ubuntu-server/jammy/daily-live/ 2. Perform a regular install using the image and on the "SSH configuration" screen make sure "Install OpenSSH server" is NOT selected. 3. Finish the install and reboot the machine. 4. Login to the rebooted machine using the credentials provided during install. 5. Using "apt-cache policy openssh-server" and "apt-cache policy ssh-import-id" confirm neither are installed. live images -- Test 2: - Perform Test 1 but instead opt-in to installing openssh-server and ensure it is installed in the target system. live-images -- Test 3: - Perform Test 2 but in a completely offline fashion. pre-installed images: - Download the latest preinstalled image from: https://cdimage.ubuntu.com/ubuntu-server/jammy/daily-preinstalled/ - Boot the image and, using the same commands as above, confirm openssh-server and ssh-import-id ARE installed [ Where problems could occur ] - openssh-server could be included in the build through other means than identified by the proposed upload, causing the package to be still installed by default. - openssh-server and ssh-import-id could fail to become part of the pool, prohibiting offline install of the packages. - Changes to the seeds could cause preinstalled images to lack the package. - The image build(s) may produce errors if they rely on openssh-server or ssh-import-id already being available in a layer in which it's now no longer included. (I can't say it's likely but it is worth mentioning) [ Other Info ] * I have built test images for ubuntu-cpc, both minimized and non-minimized, with my seed changes and verified those images will still correctly contain ssh-import-id and open-ssh-server [ Original Description] With 22.04, openssh-server is baked into the image curtin copies to the target. The ssh:install-server key no longer controls whether openssh-server gets installed. It should be easy enough to have the bit of code that installs openssh-server when the key is true also remove it when the key is false. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1974483/+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 1974483] Re: autoinstall ssh:install-server:false is misleading in 22.04
This is just one day short of the aging period of 7 days, and there is another livecd-rootfs upload in unapproved[0]. Given that livecd-rootfs is "a frequent target of SRUs as part of development of changes to image builds for the target series, and is not intended for general installation on end-user systems. The risk of user-affecting regression is lower as a result, because the impact of changes to this package to end users is mediated by way of image builds"[1] and all other checks are green, I'm releasing this one day earlier. 0. https://launchpadlibrarian.net/742542501/livecd-rootfs_2.765.46_source.changes 1. https://wiki.ubuntu.com/StableReleaseUpdates#livecd-rootfs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1974483 Title: autoinstall ssh:install-server:false is misleading in 22.04 Status in subiquity: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in livecd-rootfs source package in Jammy: Fix Committed Status in ubuntu-meta source package in Jammy: Fix Committed Bug description: [ Impact ] openssh-server is always installed to the target machine regardless of the user's explicit choice to not have it installed. Backporting the fix will allow image builds to pick up it up and become available for the next point release. The upload fixes the bug by removing ssh-import-id from the server- minimal seed and meta-package such that it's not part of the base layer copied over during install. [ Test Plan ] live images -- Test 1: 1. Download the latest server installer image from https://cdimage.ubuntu.com/ubuntu-server/jammy/daily-live/ 2. Perform a regular install using the image and on the "SSH configuration" screen make sure "Install OpenSSH server" is NOT selected. 3. Finish the install and reboot the machine. 4. Login to the rebooted machine using the credentials provided during install. 5. Using "apt-cache policy openssh-server" and "apt-cache policy ssh-import-id" confirm neither are installed. live images -- Test 2: - Perform Test 1 but instead opt-in to installing openssh-server and ensure it is installed in the target system. live-images -- Test 3: - Perform Test 2 but in a completely offline fashion. pre-installed images: - Download the latest preinstalled image from: https://cdimage.ubuntu.com/ubuntu-server/jammy/daily-preinstalled/ - Boot the image and, using the same commands as above, confirm openssh-server and ssh-import-id ARE installed [ Where problems could occur ] - openssh-server could be included in the build through other means than identified by the proposed upload, causing the package to be still installed by default. - openssh-server and ssh-import-id could fail to become part of the pool, prohibiting offline install of the packages. - Changes to the seeds could cause preinstalled images to lack the package. - The image build(s) may produce errors if they rely on openssh-server or ssh-import-id already being available in a layer in which it's now no longer included. (I can't say it's likely but it is worth mentioning) [ Other Info ] * I have built test images for ubuntu-cpc, both minimized and non-minimized, with my seed changes and verified those images will still correctly contain ssh-import-id and open-ssh-server [ Original Description] With 22.04, openssh-server is baked into the image curtin copies to the target. The ssh:install-server key no longer controls whether openssh-server gets installed. It should be easy enough to have the bit of code that installs openssh-server when the key is true also remove it when the key is false. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1974483/+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 2075337] Please test proposed package
Hello Robie, 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.1 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 dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Confirmed Status in ubuntu-advantage-tools package in Ubuntu: New Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Committed Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Committed Status in dh-python source package in Noble: Invalid Status in python3-defaults source package in Noble: Fix Committed Status in ubuntu-advantage-tools source package in Noble: New Bug description: [ Impact ] With the current version of python3-defaults in jammy and noble, packages which utilize py3compile and py3clean in their maintscripts (which is more or less any package which includes Python modules), and which also are affected by diversions installed by dpkg-divert, will fail to install/upgrade/remove on systems with non-UTF-8 locales, which include non-ASCII characters in their localized dpkg -L messages (and which therefore produce output that is not valid UTF-8). As this has the potential to break apt upgrade, the impact is quite severe (especially if this occurs during a dist-upgrade). However, the scope is probably *fairly* limited given this only affects systems with non-UTF-8 locales (something that has not been the default for many years), and which produce non-ASCII output (e.g. French characters with diacriticals) in their localized messages for dpkg -L. [ Rectification Plan ] Firstly, python3-defaults must be patched in oracular, noble, and jammy. doko has uploaded the fix upstream and synced this to oracular. Benjamin has sponsored the noble and jammy SRUs. Next, affected packages must be patched to include a "Breaks" line on earlier versions of python3-minimal (the python3-defaults binary package containing py3clean and py3compile). Packages which install Python modules are easily selected, but those affected by diversions are (computationally) impossible to select (see comment 18 for details). Thus, determining the set of affected packages was non-trivial, but Benjamin has kindly produced such a list by empirical means (see comment 24). These will be added to the ticket as they are uploaded. [ Known affected packages ] ``` $ for section in main restricted universe multiverse; do echo "noble $section:"; sqlite3 affected.sqlite3 "SELECT package, source FROM package_affected WHERE section = '$section' and install_affected = 1 AND (remove_affected = 1 OR remove_affected ISNULL) ORDER BY package;"; echo; done noble main: cloud-init|cloud-init nvme-stas|nvme-stas python3-rtslib-fb|python-rtslib-fb targetcli-fb|targetcli-fb ubiquity|ubiquity ubiquity-frontend-debconf|ubiquity ubiquity-frontend-gtk|ubiquity ubuntu-drivers-common|ubuntu-drivers-common ubuntu-pro-client|ubuntu-advantage-tools walinuxagent|walinuxagent noble restricted: noble universe: a2d|a2d apertium-apy|apertium-apy blueman|blueman borgmatic|borgmatic condor|condor cpupower-gui|cpupower-gui debomatic|debomatic dell-recovery|dell-recovery deluge-web|deluge depthcharge-tools|depthcharge-tools dhcpy6d|dhcpy6d dkimpy-milter|dkimpy-milter fenrir|fenrir galileo|galileo glances|glances graphit
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
Hello Robie, or anyone else affected, Accepted python3-defaults into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python3-defaults/3.12.3-0ubuntu2 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- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. 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 Noble) Status: Confirmed => Fix Committed ** Changed in: python3-defaults (Ubuntu Jammy) Status: Confirmed => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Confirmed Status in ubuntu-advantage-tools package in Ubuntu: New Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Committed Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Committed Status in dh-python source package in Noble: Invalid Status in python3-defaults source package in Noble: Fix Committed Status in ubuntu-advantage-tools source package in Noble: New Bug description: [ Impact ] With the current version of python3-defaults in jammy and noble, packages which utilize py3compile and py3clean in their maintscripts (which is more or less any package which includes Python modules), and which also are affected by diversions installed by dpkg-divert, will fail to install/upgrade/remove on systems with non-UTF-8 locales, which include non-ASCII characters in their localized dpkg -L messages (and which therefore produce output that is not valid UTF-8). As this has the potential to break apt upgrade, the impact is quite severe (especially if this occurs during a dist-upgrade). However, the scope is probably *fairly* limited given this only affects systems with non-UTF-8 locales (something that has not been the default for many years), and which produce non-ASCII output (e.g. French characters with diacriticals) in their localized messages for dpkg -L. [ Rectification Plan ] Firstly, python3-defaults must be patched in oracular, noble, and jammy. doko has uploaded the fix upstream and synced this to oracular. Benjamin has sponsored the noble and jammy SRUs. Next, affected packages must be patched to include a "Breaks" line on earlier versions of python3-minimal (the python3-defaults binary package containing py3clean and py3compile). Packages which install Python modules are easily selected, but those affected by diversions are (computationally) impossible to select (see comment 18 for details). Thus, determining the set of affected packages was non-trivial, but Benjamin has kindly produced such a list by empirical means (see comment 24). These will be added to the ticket as they are uploaded. [ Known affected packages ] ``` $ for section in main restricted universe multiverse; do echo "noble $section:"; sqlite3 affected.sqlite3 "SELECT package, source FROM package_affected WHERE section = '$section' and install_affected = 1 AND (remove_affected = 1 OR remove_affected ISNULL) ORDER BY package;"; echo; done noble main: cloud-init|cloud-init nvme-stas|nvme-stas python3-rtslib-fb|python-rtslib-fb targetcli-fb|targetcli-fb ubiquity|ubiquity ubiquity-frontend-debconf|ubiquity ubiquity-frontend-gtk|ubiquity ubuntu-drivers-common|ubuntu-drivers-common ubuntu-pro-client|ubuntu-advantage-tools walinuxagent|walinuxagent noble restricted: noble universe: a2d|a2d apertium-apy|apertium-apy blueman|blueman borgmatic|borgmatic condor|condor cpupower-gui|cpupower-gu
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
Hello Robie, or anyone else affected, Accepted cloud-init into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/24.2-0ubuntu1~24.04.2 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- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. 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: cloud-init (Ubuntu Noble) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Confirmed Status in ubuntu-advantage-tools package in Ubuntu: New Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Confirmed Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Committed Status in dh-python source package in Noble: Invalid Status in python3-defaults source package in Noble: Confirmed Status in ubuntu-advantage-tools source package in Noble: New Bug description: [ Impact ] With the current version of python3-defaults in jammy and noble, packages which utilize py3compile and py3clean in their maintscripts (which is more or less any package which includes Python modules), and which also are affected by diversions installed by dpkg-divert, will fail to install/upgrade/remove on systems with non-UTF-8 locales, which include non-ASCII characters in their localized dpkg -L messages (and which therefore produce output that is not valid UTF-8). As this has the potential to break apt upgrade, the impact is quite severe (especially if this occurs during a dist-upgrade). However, the scope is probably *fairly* limited given this only affects systems with non-UTF-8 locales (something that has not been the default for many years), and which produce non-ASCII output (e.g. French characters with diacriticals) in their localized messages for dpkg -L. [ Rectification Plan ] Firstly, python3-defaults must be patched in oracular, noble, and jammy. doko has uploaded the fix upstream and synced this to oracular. Benjamin has sponsored the noble and jammy SRUs. Next, affected packages must be patched to include a "Breaks" line on earlier versions of python3-minimal (the python3-defaults binary package containing py3clean and py3compile). Packages which install Python modules are easily selected, but those affected by diversions are (computationally) impossible to select (see comment 18 for details). Thus, determining the set of affected packages was non-trivial, but Benjamin has kindly produced such a list by empirical means (see comment 24). These will be added to the ticket as they are uploaded. [ Known affected packages ] ``` $ for section in main restricted universe multiverse; do echo "noble $section:"; sqlite3 affected.sqlite3 "SELECT package, source FROM package_affected WHERE section = '$section' and install_affected = 1 AND (remove_affected = 1 OR remove_affected ISNULL) ORDER BY package;"; echo; done noble main: cloud-init|cloud-init nvme-stas|nvme-stas python3-rtslib-fb|python-rtslib-fb targetcli-fb|targetcli-fb ubiquity|ubiquity ubiquity-frontend-debconf|ubiquity ubiquity-frontend-gtk|ubiquity ubuntu-drivers-common|ubuntu-drivers-common ubuntu-pro-client|ubuntu-advantage-tools walinuxagent|walinuxagent noble restricted: noble universe: a2d|a2d apertium-apy|apertium-apy blueman|blueman borgmatic|borgmatic condor|condor cpupower-gui|cpupower-gui debomatic|debomatic dell-recovery|dell-recovery deluge-web|deluge depthcharge-tools|d
[Touch-packages] [Bug 2069360] Re: apport-autoreport.service fails if autoreporting is disabled
What's the status of this in oracular? I don't see it in oracular- proposed, nor is it in 2.29.0-0ubuntu1 currently in oracular release. -- 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/2069360 Title: apport-autoreport.service fails if autoreporting is disabled Status in Apport: Fix Committed Status in apport package in Ubuntu: Fix Committed Status in apport source package in Noble: Fix Committed Bug description: [ Impact ] apport-autoreport.service fails if auto-reporting is disabled: ``` $ systemctl status apport-autoreport.service × apport-autoreport.service - Process error reports when automatic reporting is enabled Loaded: loaded (/usr/lib/systemd/system/apport-autoreport.service; static) Active: failed (Result: exit-code) since Thu 2024-06-13 21:55:08 CEST; 1h 9min ago TriggeredBy: ● apport-autoreport.timer ● apport-autoreport.path Process: 1059564 ExecStart=/usr/share/apport/whoopsie-upload-all --timeout 20 (code=exited, status=1/FAILURE) Main PID: 1059564 (code=exited, status=1/FAILURE) CPU: 86ms Jun 13 21:55:08 host systemd[1]: Starting apport-autoreport.service - Process error reports when automatic reporting is enabled... Jun 13 21:55:08 host whoopsie-upload-all[1059564]: ERROR: whoopsie.path is not enabled Jun 13 21:55:08 host systemd[1]: apport-autoreport.service: Main process exited, code=exited, status=1/FAILURE Jun 13 21:55:08 host systemd[1]: apport-autoreport.service: Failed with result 'exit-code'. Jun 13 21:55:08 host systemd[1]: Failed to start apport-autoreport.service - Process error reports when automatic reporting is enabled. ``` This service failure might mislead user thinking that there is a problem. [ Test Plan ] 1. Disable auto-reporting in the system setting: * open gnome-control-center or unity-control-center * Switch to "Security & Privacy" panel * Select "Diagnosticts" tab * unselect "Send error reports to Canonical" 2. Produce a crash, e.g. by running divide-by-zero from chaos-marmosets 3. Check that apport-autoreport.service is failing as above 4. Upgrade Apport to the fixed version 5. Restart apport-autoreport.service 6. apport-autoreport.service should exit successfully [ Where problems could occur ] This code change touches the auto-reporting part. Failures there could lead to less bugs being forwarded to the error tracker. This might be noticeable when looking at the number of submissions. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2069360/+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 2064399] Re: Merge cyrus-sasl2 from Debian unstable for oracular
ftbfs fixed, the package is a sync, closing bug. ** Changed in: cyrus-sasl2 (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 cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/2064399 Title: Merge cyrus-sasl2 from Debian unstable for oracular Status in cyrus-sasl2 package in Ubuntu: Fix Released Bug description: Upstream: tbd Debian: 2.1.28+dfsg1-6 Ubuntu: 2.1.28+dfsg1-5ubuntu3 Debian does new releases regularly, so it's likely there will be newer versions available before FF that we can pick up if this merge is done later in the cycle. If it turns out this needs a sync rather than a merge, please change the tag 'needs-merge' to 'needs-sync', and (optionally) update the title as desired. If this merge pulls in a new upstream version, also consider adding an entry to the Oracular Release Notes: https://discourse.ubuntu.com/c/release/38 ### New Debian Changes ### cyrus-sasl2 (2.1.28+dfsg1-6) unstable; urgency=medium * Team upload * Patch: Prevent six import (Closes: #1067425) -- Bastian Germann Thu, 21 Mar 2024 19:19:46 + cyrus-sasl2 (2.1.28+dfsg1-5) unstable; urgency=medium * Team upload * Fix implicit function declaration (Closes: #1066214) * Prevent linking via intersphinx (Closes: #1065436) * Extend the time_t format specifiers to long long (Closes: #1066811) -- Bastian Germann Wed, 20 Mar 2024 19:03:11 + cyrus-sasl2 (2.1.28+dfsg1-4) unstable; urgency=medium * Team upload * Clean docsrc/exts/themes (Closes: #1045111) * Drop gen-auth and saslfinger * Remove Uploaders who contributed more than a decade ago * Remove myself from Uploaders -- Bastian Germann Sat, 11 Nov 2023 22:17:13 +0100 cyrus-sasl2 (2.1.28+dfsg1-3) unstable; urgency=medium * Let libsasl2-dev depend on libssl-dev (Closes: #1042937) -- Bastian Germann Fri, 04 Aug 2023 00:35:18 +0200 cyrus-sasl2 (2.1.28+dfsg1-2) unstable; urgency=medium * Eliminate RSA-MD from binaries (Closes: #748061) -- Bastian Germann Tue, 01 Aug 2023 16:16:30 +0200 cyrus-sasl2 (2.1.28+dfsg1-1) unstable; urgency=medium * Exclude crypto-compat * New upstream version 2.1.28+dfsg1 * Get rid of BSD-4-clause-KTH * Use SPDX name for the primary license * Add Turkish translation (Closes: #1036910) [ Andreas Hasenack ] * d/t/saslauthd: fix test flakiness (Closes: #1036893) -- Bastian Germann Mon, 05 Jun 2023 23:24:14 +0200 cyrus-sasl2 (2.1.28+dfsg-11) unstable; urgency=medium [ Debian Janitor ] * Apply multi-arch hints. + cyrus-sasl2-doc: Add Multi-Arch: foreign. [ Bastian Germann ] * Add Romanian translation (Closes: #1031499) * Fix lintian depends-on-obsolete-package (lsb-base) * Add saslauthd.service (Closes: #981438) * Remove dh_installinit params * Install saslauthd.service similar to saslauthd.init * Drop old NEWS * Fix systemd-service-file-missing-documentation-key -- Bastian Germann Wed, 01 Mar 2023 00:52:04 +0100 cyrus-sasl2 (2.1.28+dfsg-10) unstable; urgency=medium [ Helmut Grohne ] * Explicitly B-D on libcrypt-dev (Closes: #1024644) -- Bastian Germann Tue, 22 Nov 2022 17:48:33 +0100 cyrus-sasl2 (2.1.28+dfsg-9) unstable; urgency=medium * d/watch: Scan GitHub release API [ Helmut Grohne ] * Depend on ABI-less libc-dev rather than libc6-dev (Closes: #1023838) -- Bastian Germann Fri, 11 Nov 2022 12:27:36 +0100 cyrus-sasl2 (2.1.28+dfsg-8) unstable; urgency=medium [ Andreas Hasenack ] * Add SASL channel binding support for GSSAPI and GSS-SPNEGO (LP: #1912256): - d/p/0034-channel-binding-gssapi-gss-spnego.patch: add SASL channel binding support for GSSAPI and GSS-SPNEGO - d/p/0035-Add-support-for-setting-max-ssf-0-to-GSS-SPNEGO-1.patch: allow setting maxssf to 0 when using GSS-SPNEGO inside SSL/TLS - d/p/0035-Add-support-for-setting-max-ssf-0-to-GSS-SPNEGO-2.patch: be more conformant to RFC4752 -- Bastian Germann Mon, 05 Sep 2022 14:30:39 +0200 cyrus-sasl2 (2.1.28+dfsg-7) unstable; urgency=medium * d/tests: Relicense to GPL-3 ### Old Ubuntu Delta ### cyrus-sasl2 (2.1.28+dfsg1-5ubuntu3) noble; urgency=medium * No-change rebuild for time_t transition. -- Sergio Durigan Junior Fri, 05 Apr 2024 15:59:59 -0400 cyrus-sasl2 (2.1.28+dfsg1-5ubuntu2) noble; urgency=medium * No-change rebuild for CVE-2024-3094 -- Steve Langasek Sun, 31 Mar 2024 07:31:27 + cyrus-sasl2 (2.1.28+dfsg1-5ubuntu1) noble; urgency=medium * Add Depends: python3-six -- Jeremy Bícha Thu, 21 Mar 2024 09:33:35 -0400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2064399/+subscriptio
[Touch-packages] [Bug 2075332] Re: FTBFS with gcc-14
Fixed: https://launchpad.net/ubuntu/+source/cyrus-sasl2/2.1.28+dfsg1-7
** Changed in: cyrus-sasl2 (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/2075332
Title:
FTBFS with gcc-14
Status in cyrus-sasl2 package in Ubuntu:
Fix Committed
Status in cyrus-sasl2 package in Debian:
New
Bug description:
https://launchpadlibrarian.net/741628620/buildlog_ubuntu-oracular-
amd64.cyrus-sasl2_2.1.28+dfsg1-6_BUILDING.txt.gz
In file included from ../../include/hmac-md5.h:7,
from ../../include/saslplug.h:11,
from ../../lib/common.c:60:
/usr/include/openssl/md5.h:49:27: note: declared here
49 | OSSL_DEPRECATEDIN_3_0 int MD5_Init(MD5_CTX *c);
| ^~~~
../../lib/common.c:2034:19: error: assignment to ‘void (*)(MD5_CTX *)’ {aka
‘void (*)(struct MD5state_st *)’} from incompatible pointer type ‘int
(*)(MD5_CTX *)’ {aka ‘int (*)(struct MD5state_st *)’}
[-Wincompatible-pointer-types]
2034 | utils->MD5Init = &MD5_Init;
| ^
../../lib/common.c:2035:3: warning: ‘MD5_Update’ is deprecated: Since OpenSSL
3.0 [-Wdeprecated-declarations]
2035 | utils->MD5Update= &MD5_Update;
| ^
/usr/include/openssl/md5.h:50:27: note: declared here
50 | OSSL_DEPRECATEDIN_3_0 int MD5_Update(MD5_CTX *c, const void *data,
size_t len);
| ^~
../../lib/common.c:2035:19: error: assignment to ‘void (*)(MD5_CTX *, const
unsigned char *, unsigned int)’ {aka ‘void (*)(struct MD5state_st *, const
unsigned char *, unsigned int)’} from incompatible pointer type ‘int
(*)(MD5_CTX *, const void *, size_t)’ {aka ‘int (*)(struct MD5state_st *, const
void *, long unsigned int)’} [-Wincompatible-pointer-types]
2035 | utils->MD5Update= &MD5_Update;
| ^
../../lib/common.c:2036:3: warning: ‘MD5_Final’ is deprecated: Since OpenSSL
3.0 [-Wdeprecated-declarations]
2036 | utils->MD5Final = &MD5_Final;
| ^
/usr/include/openssl/md5.h:51:27: note: declared here
51 | OSSL_DEPRECATEDIN_3_0 int MD5_Final(unsigned char *md, MD5_CTX *c);
| ^
../../lib/common.c:2036:19: error: assignment to ‘void (*)(unsigned char *,
MD5_CTX *)’ {aka ‘void (*)(unsigned char *, struct MD5state_st *)’} from
incompatible pointer type ‘int (*)(unsigned char *, MD5_CTX *)’ {aka ‘int
(*)(unsigned char *, struct MD5state_st *)’} [-Wincompatible-pointer-types]
2036 | utils->MD5Final = &MD5_Final;
| ^
../../lib/common.c: In function ‘_sasl_find_verifyfile_callback’:
../../lib/common.c:2165:5: warning: cast between incompatible function types
from ‘int (*)(void *, char *, int)’ to ‘int (*)(void)’ [-Wcast-function-type]
2165 | (sasl_callback_ft)&_sasl_verifyfile,
| ^
make[5]: *** [Makefile:608: common.lo] Error 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2075332/+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 2074097] Re: DEP8 failing because of hostname issues
Turns out the new DEP8 is correctly failing, because the debian upload of -6 actually failed to include the includedir patches, and that's what the new DEP8 test is looking for. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2074097 Title: DEP8 failing because of hostname issues Status in heimdal package in Ubuntu: Triaged Bug description: The new DEP8 test I added to heimdal is failing because of hostname issues: 117s autopkgtest [13:23:24]: test kinit: [--- 117s ## Adding includedir directive to /etc/krb5.conf 117s 117s ## Creating /etc/krb5.conf.d/autopkgtest.conf 117s 117s ## Stoping heimdal-kdc.service and cleaning up DB directory 117s 117s ## Stashing key 117s kstash: hdb_add_master_key: unable to find realm of host autopkgtest 117s autopkgtest [13:23:24]: test kinit: ---] 1. https://autopkgtest.ubuntu.com/results/autopkgtest-oracular/oracular/amd64/h/heimdal/20240725_132342_8fd69@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2074097/+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 2075332] Re: FTBFS with gcc-14
Fixed in debian:
cyrus-sasl2 (2.1.28+dfsg1-7) unstable; urgency=medium
.
* Team upload
* Harmonize MD5 signatures with OpenSSL (Closes: #1074899)
* Harmonize getsubopt casts with glibc
Should auto-sync soon.
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/2075332
Title:
FTBFS with gcc-14
Status in cyrus-sasl2 package in Ubuntu:
New
Status in cyrus-sasl2 package in Debian:
New
Bug description:
https://launchpadlibrarian.net/741628620/buildlog_ubuntu-oracular-
amd64.cyrus-sasl2_2.1.28+dfsg1-6_BUILDING.txt.gz
In file included from ../../include/hmac-md5.h:7,
from ../../include/saslplug.h:11,
from ../../lib/common.c:60:
/usr/include/openssl/md5.h:49:27: note: declared here
49 | OSSL_DEPRECATEDIN_3_0 int MD5_Init(MD5_CTX *c);
| ^~~~
../../lib/common.c:2034:19: error: assignment to ‘void (*)(MD5_CTX *)’ {aka
‘void (*)(struct MD5state_st *)’} from incompatible pointer type ‘int
(*)(MD5_CTX *)’ {aka ‘int (*)(struct MD5state_st *)’}
[-Wincompatible-pointer-types]
2034 | utils->MD5Init = &MD5_Init;
| ^
../../lib/common.c:2035:3: warning: ‘MD5_Update’ is deprecated: Since OpenSSL
3.0 [-Wdeprecated-declarations]
2035 | utils->MD5Update= &MD5_Update;
| ^
/usr/include/openssl/md5.h:50:27: note: declared here
50 | OSSL_DEPRECATEDIN_3_0 int MD5_Update(MD5_CTX *c, const void *data,
size_t len);
| ^~
../../lib/common.c:2035:19: error: assignment to ‘void (*)(MD5_CTX *, const
unsigned char *, unsigned int)’ {aka ‘void (*)(struct MD5state_st *, const
unsigned char *, unsigned int)’} from incompatible pointer type ‘int
(*)(MD5_CTX *, const void *, size_t)’ {aka ‘int (*)(struct MD5state_st *, const
void *, long unsigned int)’} [-Wincompatible-pointer-types]
2035 | utils->MD5Update= &MD5_Update;
| ^
../../lib/common.c:2036:3: warning: ‘MD5_Final’ is deprecated: Since OpenSSL
3.0 [-Wdeprecated-declarations]
2036 | utils->MD5Final = &MD5_Final;
| ^
/usr/include/openssl/md5.h:51:27: note: declared here
51 | OSSL_DEPRECATEDIN_3_0 int MD5_Final(unsigned char *md, MD5_CTX *c);
| ^
../../lib/common.c:2036:19: error: assignment to ‘void (*)(unsigned char *,
MD5_CTX *)’ {aka ‘void (*)(unsigned char *, struct MD5state_st *)’} from
incompatible pointer type ‘int (*)(unsigned char *, MD5_CTX *)’ {aka ‘int
(*)(unsigned char *, struct MD5state_st *)’} [-Wincompatible-pointer-types]
2036 | utils->MD5Final = &MD5_Final;
| ^
../../lib/common.c: In function ‘_sasl_find_verifyfile_callback’:
../../lib/common.c:2165:5: warning: cast between incompatible function types
from ‘int (*)(void *, char *, int)’ to ‘int (*)(void)’ [-Wcast-function-type]
2165 | (sasl_callback_ft)&_sasl_verifyfile,
| ^
make[5]: *** [Makefile:608: common.lo] Error 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2075332/+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 2046486] Re: units with credentials fail in LXD containers
** Merge proposal unlinked: https://code.launchpad.net/~ahasenack/ubuntu/+source/samba/+git/samba/+merge/470654 -- 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/2046486 Title: units with credentials fail in LXD containers Status in cloud-images: Confirmed Status in lxd: New Status in lxd package in Ubuntu: Fix Committed Status in samba package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Triaged Bug description: Many units shipped by systemd use credentials in some way by default now (in v256). So this issue is now about much more than the original test case failure. For example, root@oracular:~# apt policy systemd systemd: Installed: 256-1ubuntu1 Candidate: 256-1ubuntu1 Version table: *** 256-1ubuntu1 100 100 http://archive.ubuntu.com/ubuntu oracular-proposed/main amd64 Packages 100 /var/lib/dpkg/status 255.4-1ubuntu8 500 500 http://archive.ubuntu.com/ubuntu oracular/main amd64 Packages root@oracular:~# for service in $(find /usr/lib/systemd/system -maxdepth 1 -name "systemd-*.service"); do grep -q "Credential.*=" "$service" && echo "$service"; done /usr/lib/systemd/system/systemd-sysusers.service /usr/lib/systemd/system/systemd-resolved.service /usr/lib/systemd/system/systemd-firstboot.service /usr/lib/systemd/system/systemd-network-generator.service /usr/lib/systemd/system/systemd-journald.service /usr/lib/systemd/system/systemd-sysctl.service /usr/lib/systemd/system/systemd-tmpfiles-setup-dev-early.service /usr/lib/systemd/system/systemd-tmpfiles-setup-dev.service /usr/lib/systemd/system/systemd-tmpfiles-setup.service /usr/lib/systemd/system/systemd-udev-load-credentials.service /usr/lib/systemd/system/systemd-tmpfiles-clean.service /usr/lib/systemd/system/systemd-networkd.service root@oracular:~# systemctl status systemd-sysusers.service systemd-resolved.service systemd-firstboot.service systemd-network-generator.service systemd-journald.service systemd-sysctl.service systemd-tmpfiles-setup-dev-early.service systemd-tmpfiles-setup-dev.service systemd-tmpfiles-setup.service systemd-udev-load-credentials.service systemd-tmpfiles-clean.service systemd-networkd.service ○ systemd-sysusers.service - Create System Users Loaded: loaded (/usr/lib/systemd/system/systemd-sysusers.service; static) Active: inactive (dead) Condition: start condition unmet at Mon 2024-06-24 18:58:48 UTC; 1min 0s ago ├─ ConditionNeedsUpdate=|/etc was not met └─ ConditionCredential=|sysusers.extra was not met Docs: man:sysusers.d(5) man:systemd-sysusers.service(8) × systemd-resolved.service - Network Name Resolution Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Mon 2024-06-24 18:58:49 UTC; 59s ago Invocation: b1aaa662750f48868fe3388e4524c462 Docs: man:systemd-resolved.service(8) man:org.freedesktop.resolve1(5) https://systemd.io/WRITING_NETWORK_CONFIGURATION_MANAGERS https://systemd.io/WRITING_RESOLVER_CLIENTS Process: 258 ExecStart=/usr/lib/systemd/systemd-resolved (code=exited, status=243/CREDENTIALS) Main PID: 258 (code=exited, status=243/CREDENTIALS) ○ systemd-firstboot.service - First Boot Wizard Loaded: loaded (/usr/lib/systemd/system/systemd-firstboot.service; static) Active: inactive (dead) Condition: start condition unmet at Mon 2024-06-24 18:58:48 UTC; 59s ago └─ ConditionFirstBoot=yes was not met Docs: man:systemd-firstboot(1) ○ systemd-network-generator.service - Generate network units from Kernel command line Loaded: loaded (/usr/lib/systemd/system/systemd-network-generator.service; disabled; preset: enabled) Active: inactive (dead) Docs: man:systemd-network-generator.service(8) × systemd-journald.service - Journal Service Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static) Drop-In: /usr/lib/systemd/system/systemd-journald.service.d └─nice.conf Active: failed (Result: exit-code) since Mon 2024-06-24 18:58:48 UTC; 1min 0s ago Invocation: 7caace7a15c749f3a86fb15fcfb94dff TriggeredBy: × systemd-journald-dev-log.socket × systemd-journald.socket ○ systemd-journald-audit.socket Docs: man:systemd-journald.service(8) man:journald.conf(5) Process: 124 ExecStart=/usr/lib/systemd/systemd-journald (code=exited, status=243/CREDENTIALS) Main PID: 124 (code=exited, status=243/CREDENTIALS) FD Store: 0 (limit: 4224) × systemd-sysctl.service - Apply Kernel Variables Loaded: loaded (/usr/lib/systemd/system/systemd-sysctl.
[Touch-packages] [Bug 2073126] Re: More nuanced public key algorithm revocation
** Tags added: block-proposed-noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2073126 Title: More nuanced public key algorithm revocation Status in apt package in Ubuntu: Fix Committed Status in apt source package in Noble: Fix Committed Status in apt source package in Oracular: Fix Committed Bug description: (This is uploaded to noble as 2.8.1 per https://wiki.ubuntu.com/AptUpdates) [Impact] We have received feedback from users that use NIST-P256 keys for their repositories that are upset about receiving a warning. APT 2.8.0 in noble-proposed would bump the warning to an error, breaking them. We also revoked additional ECC curves, which may still be considered trusted, so we should not bump them to errors. Also existing users may have third-party repositories that use 1024-bit RSA keys and we have not adequately informed them yet perhaps. [Solution] Hence we will restore all elliptic curve keys of 256 or more bit to trusted: ">=rsa2048,ed25519,ed448,nistp256,nistp384,nistp512,brainpoolP256r1,brainpoolP320r1,brainpoolP384r1,brainpoolP512r1,secp256k1"; At the same time we will also introduce a more nuanced approach to revocations by introducing a 'next' level that issues a warning if the key is not allowed in it and a 'future' level that will issue an audit message with the --audit option. For the next level, we will set it to: ">=rsa2048,ed25519,ed448,nistp256,nistp384,nistp512" This means we restrict warnings to Brainpool curves and the secp256k1 key, which we have not received any feedback about them being used yet. For the future level, we will take a strong approach to best practices as it is only seen when explictly running with --audit and the intention is to highlight best practices. It will be set to ">=rsa3072,ed25519,ed448"; Which corresponds to the NIST recommendations for 2031 (and as little curves as possible). We are also introducing a mitigation for existing 24.04 systems to not upgrade the policy yet; by creating an apt.conf.d configuration file that temporarily allows the 1024-bit RSA keys if upgraded from apt 2.7.x; with the plan to remove them in 24.04.2. [Test plan] Tests are included in the library unit tests for parsing the specification strings; we have also included a test for the gpgv method to ensure that it produces the correct outcome for both 'next' and 'future' revoked keys. A spot check with a 1024-bit RSA repository and a 4096 RSA repository would still be nice. Check a clean install of apt/an upgrade from mantic vs an existing noble system: - An existing noble system should create /etc/apt/apt.conf.d/00-temporary-rsa1024 and continue to trust weak RSA signatures with a warning - Bootstrap a new noble with proposed enabled using e.g. mmdebstrap and check that this is not the case - Also check upgrading from mantic directly to proposed and ensure that 1024R repositories are rejected. [Where problems could occur] There could of course be bugs in the implementation of the new feature; this could result in verification of files failing. This also happens if you specify an invalid `next` or `future` string. There cannot be any false positives: The new levels are only *additional* checks, anything not in the `Assert-Pubkey-Algo` list is still revoked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2073126/+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 2060721] Re: APT 2.8.0: Promote weak key warnings to errors
** Tags added: block-proposed-noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2060721 Title: APT 2.8.0: Promote weak key warnings to errors Status in apt package in Ubuntu: Fix Released Status in apt source package in Noble: Fix Committed Bug description: ⚠️ Only land this in the release/updates pocket after PPAs have been resigned (This bumps the apt version to 2.8.0. APT uses the odd/even number system, with 2.7.x being the development series for 2.8, and this is the only change left for the 2.8 release, safe for some minor translation/test suite improvements) (Please also look at bug 2073126 for the follow-up changes to mitigate regression potential). [Impact] APT is currently just warning about keys that it should be rejecting to give Launchpad time to resign PPAs. This needs to be bumped to an error such that the crypto policy is fully implemented and we only trust keys that are still being trusted. #2055193 A warning provides some help right now to third-parties to fix their repositories, but it's not *safe*: A repository could have multiple signing keys and be signed by a good key now, then later, a previous key still in trusted.gpg.d could be revoked and we'd degrade to warnings, which, given that we update in the background automatically, the user may not see. Other fixes: - The test suite has been made less flaky in two places - Documentation translation has been unfuzzied for URL changes in 2.7.14 [Test plan] The vast regression test suite prevents regression in other components. Additional tests are: 1. (promotion to error) Take a repository that has a weak RSA key warning, upgrade apt and check that it is an error 2. (still valid) Check that the main Ubuntu repositories and/or resigned PPAs work correctly. We don't have any tests for the test changes or the documentation translation URL unfuzzying. [Where problems could occur] apt will start to fail updates of repositories with weak signing keys, but it will have warned users about that before. Given that it is still early in the cycle, and we only enable updates from 22.04.1 for 24.04.1, this seems the right tradeoff for future security. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2060721/+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 2067240] Re: [SRU] Add Quectel EM061K-GL/EM160/RM520N PID information to support WWAN LVFS
Hello Atlas, or anyone else affected, Accepted modemmanager into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/modemmanager/1.20.0-1~ubuntu22.04.4 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: modemmanager (Ubuntu Jammy) Status: Confirmed => 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 modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2067240 Title: [SRU] Add Quectel EM061K-GL/EM160/RM520N PID information to support WWAN LVFS Status in OEM Priority Project: Confirmed Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: Fix Committed Bug description: [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM061K-GL/EM160/RM520N PID information, and the modemmanger won't recognize these WWAN modems on some next-gen Lenovo laptops. (lp: #2045276) [ Test Plan ] Under Jammy environment, with latest linux-oem kernel installed, check output of `mmcli -L` to see if the modems are properly recognized. Modems to check: - EM061K-GL - EM160 - EM160 [ Where problems could occur ] EM160R-GL(1.22.0): https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1059/diffs EM061K-GL(1.22.0): https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1057/diffs RM520N-GL(1.22.0): https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1052/diffs https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1077/diffs All these changes are merged, and they only introduce new PIDs for initial supports, which do not affect existing ones. Noble contains these changes, so, only SRU jammy and mantic. [ Other Info ] These patches are proved work with the test version on my PPA: https://launchpad.net/~pseudoc/+archive/ubuntu/nate To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2067240/+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 2060666] Re: [SRU] Memory leak in krb5 version 1.17
There are many autopkgtest regressions listed at: https://ubuntu-archive-team.ubuntu.com/proposed- migration/focal/update_excuses.html#krb5 For now I have retried them. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/2060666 Title: [SRU] Memory leak in krb5 version 1.17 Status in krb5 package in Ubuntu: Fix Released Status in krb5 source package in Focal: Fix Committed Bug description: [ Impact ] Commit https://github.com/krb5/krb5/commit/1cd2821c19b2b95e39d5fc2f451a035585a40fa5 altered the memory management of krb5_gss_inquire_cred(), introducing defcred to act as an owner pointer when the function must acquire a default credential. The commit neglected to update the code to release the default cred along the successful path. The old code does not trigger because cred_handle is now reassigned, so the default credential is leaked. Resulting gradual increase in memory usage (memory leak) and eventual crash. [ Test Plan ] Setup 3 VMs: 1. Windows Server act as Domain controller (AD) 2. Windows machine AD Joined with Ostress installed. (Ostress is part of RML utilities https://learn.microsoft.com/en-us/troubleshoot/sql/tools/replay-markup-language-utility) 3. SQL on Linux AD Joined ( configuration steps https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-ad-auth-adutil-tutorial?view=sql-server-ver16) On the Machine with OStress create a file (name it disconnect.ini) with the following content under the same folder “C:\Program Files\Microsoft Corporation\RMLUtils” where OStress is installed. disconnect.ini == [Connection Options] LoginTimeout=30 QuotedIdentifier=Off AutocommitMode=On DisconnectPct=100.0 MaxThreadErrors=0 [Query Options] NoSQLBindCol=Off NoResultDisplay=Off PrepareExecute=Off ExecuteAsync=Off RollbackOnCancel=Off QueryTimeout=0 QueryDelay=0 MaxRetries=0 BatchDisconnectPct=0.0 CancelPct=0.00 CancelDelay=0 CancelDelayMin=0 CursorType= CursorConcurrency= RowFetchDelay=0 [Replay Options] Sequencing Options=global sequence ::Sequencing Options=global sequence, dtc replay DTC Timeout= DTC Machine=(local) Playback Coordinator=(local) StartSeqNum= StopSeqNum= TimeoutFactor=1.0 Run the following command to start the load using Ostress, change Server name (-S) accordingly and the number of threads (-n) as needed. Start 4 different CMD consoles and use the following different commands for each CMD window: 1. ostress.exe -E -S -Q"select * from sys.all_objects" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log01 -T146 2. ostress.exe -E -S -Q"select * from sys.all_views" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log02 -T146 3. ostress.exe -E -S -Q"select * from sys.all_columns" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log03 -T146 4. ostress.exe -E -S -Q"select * from sys.all_parameters" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log04 -T146 After a run of about 5 hours, the memory usage for this is expected to be around 5G with the fix. Without the fix, it was observed that it reached around ~22G in 5 hours. Hence the increase in memory usage can be observed if the ostress.exe programs are let to run longer. [ Where problems could occur ] The fix may not fix the memory leak or could result in releasing the memory early in a different code path, and thus resulting in crashes. A mitigating fact is that the fix has been in Ubuntu since at least 22.04 and they do not exhibit any issues. Likewise I've previously provided the fix in a PPA https://launchpad.net/~pponnuvel/+archive/ubuntu/krb5-focal to user who's been hit by this issue. They've tested and confirmed it fixes the memory leak. [ Other Info ] The commit https://github.com/krb5/krb5/commit/098f874f3b50dd2c46c0a574677324b5f6f3a1a8 fixes the leak. The fix has been included in newer krb5 releases (Jammy, and Noble have the releases with the fix). Bionic doesn't have the commit the introduced the memory leak in the first place. So this will be a Focal-only backport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/2060666/+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 2072574] Re: Drop obsolete evolution-data-server notify-with-tray override
Hello Jeremy, or anyone else affected, Accepted ubuntu-settings into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- settings/24.04.4 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- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. 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: ubuntu-settings (Ubuntu Noble) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2072574 Title: Drop obsolete evolution-data-server notify-with-tray override Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Noble: Fix Committed Bug description: Impact -- Calendar notifications currently pop up a full app window instead of as a normal notification. The normal notifications respect the Do Not Disturb setting, but the full app window does not. Test Case 1 --- From Ubuntu Desktop… 1. Add your Google account to GNOME Settings > Online Accounts 2. Add a calendar event to Google Calendar with a notification in advance 3. When it is time for the notification, you should see a GNOME Shell notification. You can click on the notification to see the full Reminders window. Test Case 2 --- From Ubuntu Unity 24.04 LTS… 1. Open a terminal and run this command: sudo apt install gnome-online-accounts-gtk 2. Close the terminal 3. Add a calendar event to Google Calendar with a notification in advance 4. When it is time for the notification, you should see a notification pop-up. You can click OK on the notification to see the full Reminders window. What Could Go Wrong --- The ubuntu-settings package is shipped by default with Ubuntu Desktop, Ubuntu Unity, and Edubuntu. Edubuntu is practically the same as Ubuntu Desktop as far as the desktop experience goes with one additional GNOME Shell extension to sort the Show Apps view alphabetically. This is a small default change that can be easily changed (see Revert instructions below). I guess this could go bad if someone counts on getting event notifications even though they have turned on Do Not Disturb. I'm sorry but it is intended that Do Not Disturb not show notifications like this. Other Info -- I believe this override was originally added in 2011 for Unity's benefit LP: #757805 It was also helpful for GNOME in early GNOME 3 days with the unusual messaging tray that was later dropped. These days, GNOME Shell notifications work well, better than a separate popup window. Revert to Previous Behavior --- If you prefer the original Ubuntu 24.04 LTS behavior, do one of the following: 1. Run this in a terminal: gsettings set org.gnome.evolution-data-server.calendar notify-with-tray false 2. Or install Evolution. In ☰ > Edit > Preferences > Calendar and Tasks, turn on "Display Reminder window with notifications" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2072574/+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
