[Touch-packages] [Bug 2063200] Re: useradd --extrausers --groups tries to lock /etc/group
The issue was introduced with https://github.com/shadow- maint/shadow/pull/237 Basically, the previous group validation was done using glibc's getgrid directly, which was presumably coping well with the RO status of /etc/group, but that poses consistency problems because you could add a local user to a network group. That PR changed this to only check the local /etc/group file contents manually instead. Sadly, it doesn't cope well with our extrausers feature on multiple levels: * The manual code fails hard if it can't lock the files * We presumably have local groups defined in multiple places, which the code doesn't allow for. A quickfix would be: * Move the validation to until *after* parsing all of the options * Revert back to the previous approach to validate groups if in extrausers mode A more involved fix would be to replace that with an approach that would check both /etc/group and the extrausers equivalent when validating groups, while silently ignoring locking failures. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/2063200 Title: useradd --extrausers --groups tries to lock /etc/group Status in shadow package in Ubuntu: New Bug description: On Ubuntu Core 24 calling the command line useradd --extrausers --groups somegroup somenewuser ... fails with: useradd: cannot lock /etc/group; try again later. It worked on 22.04. /etc is not writable. It also fails if somegroup is a group in extrausers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2063200/+subscriptions -- Mailing list: https://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 2063200] Re: useradd --extrausers --groups tries to lock /etc/group
** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/2063200 Title: useradd --extrausers --groups tries to lock /etc/group Status in shadow package in Ubuntu: New Bug description: On Ubuntu Core 24 calling the command line useradd --extrausers --groups somegroup somenewuser ... fails with: useradd: cannot lock /etc/group; try again later. It worked on 22.04. /etc is not writable. It also fails if somegroup is a group in extrausers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2063200/+subscriptions -- Mailing list: https://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 2063200] Re: useradd --extrausers --groups tries to lock /etc/group
Quick repro steps: ❯ lxc launch ubuntu-daily:noble shadow Creating shadow Starting shadow ❯ lxc exec shadow bash root@shadow:~# mv /etc /etc_write root@shadow:~# mkdir /etc root@shadow:~# mount -o bind,ro /etc_write /etc root@shadow:~# useradd --extrausers --groups somegroup somenewuser useradd: cannot lock /etc/group; try again later. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/2063200 Title: useradd --extrausers --groups tries to lock /etc/group Status in shadow package in Ubuntu: New Bug description: On Ubuntu Core 24 calling the command line useradd --extrausers --groups somegroup somenewuser ... fails with: useradd: cannot lock /etc/group; try again later. It worked on 22.04. /etc is not writable. It also fails if somegroup is a group in extrausers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2063200/+subscriptions -- Mailing list: https://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 2063200] Re: useradd --extrausers --groups tries to lock /etc/group
** Changed in: shadow (Ubuntu) Assignee: (unassigned) => Simon Chopin (schopin) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/2063200 Title: useradd --extrausers --groups tries to lock /etc/group Status in shadow package in Ubuntu: New Bug description: On Ubuntu Core 24 calling the command line useradd --extrausers --groups somegroup somenewuser ... fails with: useradd: cannot lock /etc/group; try again later. It worked on 22.04. /etc is not writable. It also fails if somegroup is a group in extrausers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2063200/+subscriptions -- Mailing list: https://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 2060962] Re: apport-bug: cli reports syntax warnings to user
** Also affects: apport-symptoms (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apport (Ubuntu)
Status: New => Invalid
** Description changed:
Apport version: 2.28.0-0ubuntu1
Ubuntu-Server 24.04 Beta amd64 (20240410.1)
- See attached screenshot for error.
+ /usr/share/apport/symptoms/_audio_data.py:123: SyntaxWarning: invalid escape
sequence '\['
+ m = re.search('Pin Default 0x(.*?): \[(.*?)\] (.*?) at (.*?) (.*)', line)
+ /usr/share/apport/symptoms/_audio_data.py:148: SyntaxWarning: invalid escape
sequence '\d'
+ m = re.search(' (\d+) \[(\w+)\s*\]: (.+)', card)
+ /usr/share/apport/symptoms/_audio_data.py:162: SyntaxWarning: invalid escape
sequence '\w'
+ m = re.match('^(\w+) #(\d+)', line)
+ /usr/share/apport/symptoms/_audio_data.py:171: SyntaxWarning: invalid escape
sequence '\w'
+ m = re.match('^\t(\w+.*?): (.*)', line)
+ /usr/share/apport/symptoms/_audio_data.py:177: SyntaxWarning: invalid escape
sequence '\w'
+ m = re.match('^\t(\w+.*?):', line)
+ /usr/share/apport/symptoms/_audio_data.py:182: SyntaxWarning: invalid escape
sequence '\w'
+ m = re.match('^\t\t(\w+.*?) = "(.*)"', line)
+ /usr/share/apport/symptoms/_audio_mixercontrol.py:29: SyntaxWarning: invalid
escape sequence '\['
+ m = re.search("\[([\-0-9.]+)dB\]", s)
+ /usr/share/apport/symptoms/_audio_mixercontrol.py:34: SyntaxWarning: invalid
escape sequence '\['
+ if re.search("\[on\]", s):
+ /usr/share/apport/symptoms/_audio_mixercontrol.py:36: SyntaxWarning: invalid
escape sequence '\['
+ if re.search("\[off\]", s):
+ /usr/share/apport/symptoms/_audio_mixercontrol.py:38: SyntaxWarning: invalid
escape sequence '\d'
+ m = re.search(" ?(\d+) ", s)
+ /usr/share/apport/symptoms/_audio_mixercontrol.py:41: SyntaxWarning: invalid
escape sequence '\['
+ m = re.search("\[([\-0-9.]+)%\]", s)
--
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/2060962
Title:
apport-bug: cli reports syntax warnings to user
Status in apport package in Ubuntu:
Invalid
Status in apport-symptoms package in Ubuntu:
New
Bug description:
Apport version: 2.28.0-0ubuntu1
Ubuntu-Server 24.04 Beta amd64 (20240410.1)
/usr/share/apport/symptoms/_audio_data.py:123: SyntaxWarning: invalid escape
sequence '\['
m = re.search('Pin Default 0x(.*?): \[(.*?)\] (.*?) at (.*?) (.*)', line)
/usr/share/apport/symptoms/_audio_data.py:148: SyntaxWarning: invalid escape
sequence '\d'
m = re.search(' (\d+) \[(\w+)\s*\]: (.+)', card)
/usr/share/apport/symptoms/_audio_data.py:162: SyntaxWarning: invalid escape
sequence '\w'
m = re.match('^(\w+) #(\d+)', line)
/usr/share/apport/symptoms/_audio_data.py:171: SyntaxWarning: invalid escape
sequence '\w'
m = re.match('^\t(\w+.*?): (.*)', line)
/usr/share/apport/symptoms/_audio_data.py:177: SyntaxWarning: invalid escape
sequence '\w'
m = re.match('^\t(\w+.*?):', line)
/usr/share/apport/symptoms/_audio_data.py:182: SyntaxWarning: invalid escape
sequence '\w'
m = re.match('^\t\t(\w+.*?) = "(.*)"', line)
/usr/share/apport/symptoms/_audio_mixercontrol.py:29: SyntaxWarning: invalid
escape sequence '\['
m = re.search("\[([\-0-9.]+)dB\]", s)
/usr/share/apport/symptoms/_audio_mixercontrol.py:34: SyntaxWarning: invalid
escape sequence '\['
if re.search("\[on\]", s):
/usr/share/apport/symptoms/_audio_mixercontrol.py:36: SyntaxWarning: invalid
escape sequence '\['
if re.search("\[off\]", s):
/usr/share/apport/symptoms/_audio_mixercontrol.py:38: SyntaxWarning: invalid
escape sequence '\d'
m = re.search(" ?(\d+) ", s)
/usr/share/apport/symptoms/_audio_mixercontrol.py:41: SyntaxWarning: invalid
escape sequence '\['
m = re.search("\[([\-0-9.]+)%\]", s)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2060962/+subscriptions
--
Mailing list: https://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 2059078] Re: proposed-migration for faketime 0.9.10-2.1ubuntu1
What now remains to be done is to heavily patch faketime to, when on armhf: 1/ use the proper symbols from glibc (e.g. __clock_gettime64 instead of __clock_gettime) 2/ expose those symbols instead of the legacy 32-bit ones. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/2059078 Title: proposed-migration for faketime 0.9.10-2.1ubuntu1 Status in bash package in Ubuntu: New Status in faketime package in Ubuntu: New Bug description: faketime 0.9.10-2.1ubuntu1 is stuck in -proposed with build failures on armhf. On armhf, the testsuite confusingly fails with a stack smash error. But this error happens in bash, which isn't even meant to be the process under test. Minimal reproducer: # LD_PRELOAD=./src/libfaketime.so.1 bash -c 'exit 0' *** stack smashing detected ***: terminated Aborted (core dumped) # Confusingly, ltrace shows different results for the newly-built binary than from one built without 64-bit time_t. # LD_PRELOAD=./src/libfaketime.so.1 ltrace --library '*faketime*' bash -c 'exit 0' bash->getrandom(0x1f3bf08, 1, 0x9683b0, 0) = 0xc8202 bash->getrandom(0xc8203, 0xf7fad53c, 1023, 0xf7eef801) = 0xc8202 *** stack smashing detected ***: terminated --- SIGABRT (Aborted) --- +++ killed by SIGABRT +++ # LD_PRELOAD=/usr/lib/arm-linux-gnueabihf/faketime/libfaketime.so.1 ltrace --library '*faketime*' bash -c 'exit 0' bash->gettimeofday(0x8b07a0, 0) = 0 bash->getpid() = 819717 bash->gettimeofday(0xffb88714, 0)= 0 bash->getpid() = 819717 bash->gettimeofday(0xffb8871c, 0)= 0 bash->getpid() = 819717 +++ exited (status 0) +++ # Unsetting -DFAKE_RANDOM in debian/rules does not fix the problem however. So simply loading the LD_PRELOAD library without executing it seems to be enough to break bash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2059078/+subscriptions -- Mailing list: https://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 2058769] Re: proposed-migration for click 0.5.2-2
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Description changed: - click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on armhf, - and possibly on all archs. + click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on ppc64el, + s390x. - armhf binary will be removed from the release pocket. + In order to be able to run the tests without all-proposed=1, glib 2.0 is + needed, which is why I marked it as affected. + + Excerpt of the test logs: + + ERROR: test_list_simple (click_package.tests.integration.test_list.TestList.test_list_simple) + -- + Traceback (most recent call last): + File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_list.py", line 29, in test_list_simple + self.click_install(path_to_click, name, user) + File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/helpers.py", line 99, in click_install + subprocess.check_call(cmd) + File "/usr/lib/python3.12/subprocess.py", line 413, in check_call + raise CalledProcessError(retcode, cmd) + subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', '--user=root', '--allow-unauthenticated', '/tmp/tmpqhzp18eh/com.ubuntu.verify-ok_1.0_all.click']' returned non-zero exit status 1. + + == + ERROR: test_debsig_install_valid_signature (click_package.tests.integration.test_signatures.TestSignatureVerification.test_debsig_install_valid_signature) + -- + Traceback (most recent call last): + File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py", line 207, in test_debsig_install_valid_signature + subprocess.check_call( + File "/usr/lib/python3.12/subprocess.py", line 413, in check_call + raise CalledProcessError(retcode, cmd) + subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', '--user=root', '/tmp/tmpymtfsjg9/org.example.debsig-valid-sig_1.0_all.click']' returned non-zero exit status 1. + + == + ERROR: test_debsig_install_can_install_with_sig_override (click_package.tests.integration.test_signatures.TestSignatureVerificationNoSignature.test_debsig_install_can_install_with_sig_override) + -- + Traceback (most recent call last): + File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py", line 164, in test_debsig_install_can_install_with_sig_override + subprocess.check_call( + File "/usr/lib/python3.12/subprocess.py", line 413, in check_call + raise CalledProcessError(retcode, cmd) + subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', '--allow-unauthenticated', '--user=root', '/tmp/tmpheysy9ze/org.example.debsig-no-sig_1.0_all.click']' returned non-zero exit status 1. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2058769 Title: proposed-migration for click 0.5.2-2 Status in click package in Ubuntu: New Status in glib2.0 package in Ubuntu: New Bug description: click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on ppc64el, s390x. In order to be able to run the tests without all-proposed=1, glib 2.0 is needed, which is why I marked it as affected. Excerpt of the test logs: ERROR: test_list_simple (click_package.tests.integration.test_list.TestList.test_list_simple) -- Traceback (most recent call last): File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_list.py", line 29, in test_list_simple self.click_install(path_to_click, name, user) File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/helpers.py", line 99, in click_install subprocess.check_call(cmd) File "/usr/lib/python3.12/subprocess.py", line 413, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', '--user=root', '--allow-unauthenticated', '/tmp/tmpqhzp18eh/com.ubuntu.verify-ok_1.0_all.click']' returned non-zero exit status 1. == ERROR: test_debsig_install_valid_signature (click_package.tests.integration.test_signatures.TestSignatureVerification.test_debsig_install_valid_signature) -- Traceback (most recent call last): File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py", line 207, in
[Touch-packages] [Bug 2059078] Re: proposed-migration for faketime 0.9.10-2.1ubuntu1
Oh, hang on. The bash build has apparently been uploaded just a day after the t64 gcc, which means gcc was presumably still building when the bash build started: gcc-13 armhf 13.2.0-13ubuntu1 (from the bash build logs) A bash rebuild should "fix" this somewhat. Well, at least a little bit. ** Also affects: bash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/2059078 Title: proposed-migration for faketime 0.9.10-2.1ubuntu1 Status in bash package in Ubuntu: New Status in faketime package in Ubuntu: New Bug description: faketime 0.9.10-2.1ubuntu1 is stuck in -proposed with build failures on armhf. On armhf, the testsuite confusingly fails with a stack smash error. But this error happens in bash, which isn't even meant to be the process under test. Minimal reproducer: # LD_PRELOAD=./src/libfaketime.so.1 bash -c 'exit 0' *** stack smashing detected ***: terminated Aborted (core dumped) # Confusingly, ltrace shows different results for the newly-built binary than from one built without 64-bit time_t. # LD_PRELOAD=./src/libfaketime.so.1 ltrace --library '*faketime*' bash -c 'exit 0' bash->getrandom(0x1f3bf08, 1, 0x9683b0, 0) = 0xc8202 bash->getrandom(0xc8203, 0xf7fad53c, 1023, 0xf7eef801) = 0xc8202 *** stack smashing detected ***: terminated --- SIGABRT (Aborted) --- +++ killed by SIGABRT +++ # LD_PRELOAD=/usr/lib/arm-linux-gnueabihf/faketime/libfaketime.so.1 ltrace --library '*faketime*' bash -c 'exit 0' bash->gettimeofday(0x8b07a0, 0) = 0 bash->getpid() = 819717 bash->gettimeofday(0xffb88714, 0)= 0 bash->getpid() = 819717 bash->gettimeofday(0xffb8871c, 0)= 0 bash->getpid() = 819717 +++ exited (status 0) +++ # Unsetting -DFAKE_RANDOM in debian/rules does not fix the problem however. So simply loading the LD_PRELOAD library without executing it seems to be enough to break bash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2059078/+subscriptions -- Mailing list: https://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 2052930] Re: liblocale-gettext-perl autopkgtests fail against glibc 2.39
** Changed in: glibc (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to liblocale-gettext-perl in Ubuntu. https://bugs.launchpad.net/bugs/2052930 Title: liblocale-gettext-perl autopkgtests fail against glibc 2.39 Status in glibc package in Ubuntu: Invalid Status in liblocale-gettext-perl package in Ubuntu: Fix Committed Bug description: The autopkgtests for liblocale-gettext-perl fail against glibc 2.39 with the following errors: autopkgtest [15:27:03]: test autodep8-perl-build-deps: [--- 243s t/bind.t ... 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:02 2024 243s # Current time GMT: Wed Feb 7 15:27:02 2024 243s # Using Test.pm version 1.31 243s ok 1 243s ok 243s t/frconvert.t .. 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:02 2024 243s # Current time GMT: Wed Feb 7 15:27:02 2024 243s # Using Test.pm version 1.31 243s not ok 1 243s # Failed test 1 in t/frconvert.t at line 22 243s # t/frconvert.t line 22 is: ok(0); 243s Failed 1/1 subtests 243s t/jaconvert.t .. 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s test 243s not ok 1 243s # Failed test 1 in t/jaconvert.t at line 23 243s # t/jaconvert.t line 23 is: ok(0); 243s Failed 1/1 subtests 243s t/raw.t 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s not ok 1 243s # Failed test 1 in t/raw.t at line 14 243s # t/raw.t line 14 is: ok(0); 243s Failed 1/1 subtests 243s t/use.t 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s ok 1 243s ok 243s 243s Test Summary Report 243s --- 243s t/frconvert.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s t/jaconvert.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s t/raw.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s Files=5, Tests=5, 1 wallclock secs ( 0.03 usr 0.01 sys + 0.09 cusr 0.07 csys = 0.20 CPU) 243s Result: FAIL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2052930/+subscriptions -- Mailing list: https://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 2052930] Re: liblocale-gettext-perl autopkgtests fail against glibc 2.39
It turns out the fix was already in the upstream repo as a PR for a while (couple of years?). I've submitted a Salsa MR to proactively address the issue before it shows up there: https://salsa.debian.org/perl-team/modules/packages/liblocale-gettext- perl/-/merge_requests/1 and I've uploaded the same changes in Ubuntu. ** Changed in: liblocale-gettext-perl (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to liblocale-gettext-perl in Ubuntu. https://bugs.launchpad.net/bugs/2052930 Title: liblocale-gettext-perl autopkgtests fail against glibc 2.39 Status in glibc package in Ubuntu: Triaged Status in liblocale-gettext-perl package in Ubuntu: Fix Committed Bug description: The autopkgtests for liblocale-gettext-perl fail against glibc 2.39 with the following errors: autopkgtest [15:27:03]: test autodep8-perl-build-deps: [--- 243s t/bind.t ... 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:02 2024 243s # Current time GMT: Wed Feb 7 15:27:02 2024 243s # Using Test.pm version 1.31 243s ok 1 243s ok 243s t/frconvert.t .. 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:02 2024 243s # Current time GMT: Wed Feb 7 15:27:02 2024 243s # Using Test.pm version 1.31 243s not ok 1 243s # Failed test 1 in t/frconvert.t at line 22 243s # t/frconvert.t line 22 is: ok(0); 243s Failed 1/1 subtests 243s t/jaconvert.t .. 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s test 243s not ok 1 243s # Failed test 1 in t/jaconvert.t at line 23 243s # t/jaconvert.t line 23 is: ok(0); 243s Failed 1/1 subtests 243s t/raw.t 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s not ok 1 243s # Failed test 1 in t/raw.t at line 14 243s # t/raw.t line 14 is: ok(0); 243s Failed 1/1 subtests 243s t/use.t 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s ok 1 243s ok 243s 243s Test Summary Report 243s --- 243s t/frconvert.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s t/jaconvert.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s t/raw.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s Files=5, Tests=5, 1 wallclock secs ( 0.03 usr 0.01 sys + 0.09 cusr 0.07 csys = 0.20 CPU) 243s Result: FAIL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2052930/+subscriptions -- Mailing list: https://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 2056561] Re: Libc6 bug in gvfs-udisk
Unless I'm missing something, the issue you're linking is about glib, not glibc. Reassigning the bug accordingly. ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: glibc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2056561 Title: Libc6 bug in gvfs-udisk Status in glib2.0 package in Ubuntu: New Status in glibc package in Ubuntu: Invalid Bug description: Hi, Please see https://gitlab.gnome.org/GNOME/glib/-/issues/3168, which is a result of https://gitlab.gnome.org/GNOME/glib/-/issues/3168, which is fixed but needs a backport or something. Thanks, tg ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: libc6 2.38-1ubuntu6.1 ProcVersionSignature: Ubuntu 6.5.0-25.25-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Fri Mar 8 15:15:39 2024 Dependencies: gcc-13-base 13.2.0-4ubuntu3 libc6 2.38-1ubuntu6.1 libgcc-s1 13.2.0-4ubuntu3 libidn2-0 2.3.4-1 libunistring2 1.0-2 InstallationDate: Installed on 2022-12-08 (456 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: glibc UpgradeStatus: Upgraded to mantic on 2023-10-01 (159 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2056561/+subscriptions -- Mailing list: https://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 2056196] [NEW] BT headset is disconnected when remotely changing from A2DP to HSP
Public bug reported: Release of Ubuntu: Noble Package Version: 5.72-0ubuntu1 My headset changed profile from A2DP to HSP as I received a phone call on my phone (the headset can connect to multiple BT devices). I'd expect the system to adapt to the new profile (add a new source, change the properties of the sink to signal that it's crappy now, etc...), but instead it completely disconnected the headset. I'd assume this line in the logs is the reason: mars 05 16:01:44 pug bluetoothd[2644]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: bluez 5.72-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Tue Mar 5 16:03:31 2024 InstallationDate: Installed on 2021-07-05 (974 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9310 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=UUID=6bfcd06c-aed1-4da7-949a-dffbf9878bda ro quiet splash i915.enable_psr=0 vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to noble on 2024-03-05 (0 days ago) dmi.bios.date: 12/19/2023 dmi.bios.release: 3.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.20.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.20.0:bd12/19/2023:br3.20:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 68:54:5A:94:85:F3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:20697414 acl:97 sco:328138 events:3546 errors:0 TX bytes:21468970 acl:107 sco:327713 commands:3406 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2056196 Title: BT headset is disconnected when remotely changing from A2DP to HSP Status in bluez package in Ubuntu: New Bug description: Release of Ubuntu: Noble Package Version: 5.72-0ubuntu1 My headset changed profile from A2DP to HSP as I received a phone call on my phone (the headset can connect to multiple BT devices). I'd expect the system to adapt to the new profile (add a new source, change the properties of the sink to signal that it's crappy now, etc...), but instead it completely disconnected the headset. I'd assume this line in the logs is the reason: mars 05 16:01:44 pug bluetoothd[2644]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands- Free Voice gateway: getpeername: Transport endpoint is not connected (107) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: bluez 5.72-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Tue Mar 5 16:03:31 2024 InstallationDate: Installed on 2021-07-05 (974 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9310 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=UUID=6bfcd06c-aed1-4da7-949a-dffbf9878bda ro quiet splash i915.enable_psr=0 vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to noble on 2024-03-05 (0 days ago) dmi.bios.date: 12/19/2023 dmi.bios.release: 3.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.20.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.20.0:bd12/19/2023:br3.20:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:54:5A:94:85:F3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:20697414 acl:97 sco:328138
[Touch-packages] [Bug 2056151] [NEW] systemd should create empty /etc/$program.conf.d directories
Public bug reported: As a header to all .conf files in systemd there's a comment saying # Entries in this file show the compile time defaults. Local configuration # should be created by either modifying this file (or a copy of it placed in # /etc/ if the original file is shipped in /usr/), or by creating "drop-ins" in # the /etc/systemd/user.conf.d/ directory. The latter is generally recommended. (with variations on the actual directory name, of course) Since the .d method is the recommended way, the systemd package should create the empty directory as a way to reduce friction and make it more even more discoverable to the user. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2056151 Title: systemd should create empty /etc/$program.conf.d directories Status in systemd package in Ubuntu: New Bug description: As a header to all .conf files in systemd there's a comment saying # Entries in this file show the compile time defaults. Local configuration # should be created by either modifying this file (or a copy of it placed in # /etc/ if the original file is shipped in /usr/), or by creating "drop-ins" in # the /etc/systemd/user.conf.d/ directory. The latter is generally recommended. (with variations on the actual directory name, of course) Since the .d method is the recommended way, the systemd package should create the empty directory as a way to reduce friction and make it more even more discoverable to the user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2056151/+subscriptions -- Mailing list: https://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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
We had a mitigation for this in glibc but the latest change from simply denying the unshare() call to allowing it but then denying anything requiring capabilities *presumably* broke the glibc test suite again. I'm only basing this from looking at the test logs, as I'm temporarily unable to run autopkgtests locally and am lacking the time to fix it. 2 classes of errors: 2770s FAIL: stdlib/tst-system 2770s original exit status 1 2770s error: test-container.c:1136: could not create a private mount namespace That one is clearly userns-related, as it's due to a failing mount() call right after unshare() 2770s FAIL: sunrpc/tst-svc_register 2770s original exit status 1 2770s error: xwrite.c:32: write of 12 bytes failed after 0: Operation not permitted 2770s error: 1 test failures I can't tell for sure what this one is about since this is your basic write() call and I don't have a stack trace at hand, but the EPERM would suggest that it's related. I think a first fix would be to amend the test script to disable the userns restriction entirely for the duration of the tests (using 'needs- sudo'), while I'll still need to patch the test suite eventually to handle this new failure mode gracefully and simply ignore the tests, akin to https://sourceware.org/pipermail/libc- alpha/2024-February/154754.html -- 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 akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released 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 freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Confirmed 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 marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Committed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released 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/ubuntu/+source/akonadiconsole/+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 2052930] Re: liblocale-gettext-perl autopkgtests fail against glibc 2.39
** Tags added: foundations-todo ** Changed in: glibc (Ubuntu) Assignee: (unassigned) => Simon Chopin (schopin) ** Changed in: glibc (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to liblocale-gettext-perl in Ubuntu. https://bugs.launchpad.net/bugs/2052930 Title: liblocale-gettext-perl autopkgtests fail against glibc 2.39 Status in glibc package in Ubuntu: Triaged Status in liblocale-gettext-perl package in Ubuntu: New Bug description: The autopkgtests for liblocale-gettext-perl fail against glibc 2.39 with the following errors: autopkgtest [15:27:03]: test autodep8-perl-build-deps: [--- 243s t/bind.t ... 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:02 2024 243s # Current time GMT: Wed Feb 7 15:27:02 2024 243s # Using Test.pm version 1.31 243s ok 1 243s ok 243s t/frconvert.t .. 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:02 2024 243s # Current time GMT: Wed Feb 7 15:27:02 2024 243s # Using Test.pm version 1.31 243s not ok 1 243s # Failed test 1 in t/frconvert.t at line 22 243s # t/frconvert.t line 22 is: ok(0); 243s Failed 1/1 subtests 243s t/jaconvert.t .. 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s test 243s not ok 1 243s # Failed test 1 in t/jaconvert.t at line 23 243s # t/jaconvert.t line 23 is: ok(0); 243s Failed 1/1 subtests 243s t/raw.t 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s not ok 1 243s # Failed test 1 in t/raw.t at line 14 243s # t/raw.t line 14 is: ok(0); 243s Failed 1/1 subtests 243s t/use.t 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s ok 1 243s ok 243s 243s Test Summary Report 243s --- 243s t/frconvert.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s t/jaconvert.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s t/raw.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s Files=5, Tests=5, 1 wallclock secs ( 0.03 usr 0.01 sys + 0.09 cusr 0.07 csys = 0.20 CPU) 243s Result: FAIL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2052930/+subscriptions -- Mailing list: https://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 2052930] [NEW] liblocale-gettext-perl autopkgtests fail against glibc 2.39
Public bug reported: The autopkgtests for liblocale-gettext-perl fail against glibc 2.39 with the following errors: autopkgtest [15:27:03]: test autodep8-perl-build-deps: [--- 243s t/bind.t ... 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:02 2024 243s # Current time GMT: Wed Feb 7 15:27:02 2024 243s # Using Test.pm version 1.31 243s ok 1 243s ok 243s t/frconvert.t .. 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:02 2024 243s # Current time GMT: Wed Feb 7 15:27:02 2024 243s # Using Test.pm version 1.31 243s not ok 1 243s # Failed test 1 in t/frconvert.t at line 22 243s # t/frconvert.t line 22 is: ok(0); 243s Failed 1/1 subtests 243s t/jaconvert.t .. 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s test 243s not ok 1 243s # Failed test 1 in t/jaconvert.t at line 23 243s # t/jaconvert.t line 23 is: ok(0); 243s Failed 1/1 subtests 243s t/raw.t 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s not ok 1 243s # Failed test 1 in t/raw.t at line 14 243s # t/raw.t line 14 is: ok(0); 243s Failed 1/1 subtests 243s t/use.t 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s ok 1 243s ok 243s 243s Test Summary Report 243s --- 243s t/frconvert.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s t/jaconvert.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s t/raw.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s Files=5, Tests=5, 1 wallclock secs ( 0.03 usr 0.01 sys + 0.09 cusr 0.07 csys = 0.20 CPU) 243s Result: FAIL ** Affects: glibc (Ubuntu) Importance: Undecided Status: Triaged ** Affects: liblocale-gettext-perl (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Also affects: liblocale-gettext-perl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to liblocale-gettext-perl in Ubuntu. https://bugs.launchpad.net/bugs/2052930 Title: liblocale-gettext-perl autopkgtests fail against glibc 2.39 Status in glibc package in Ubuntu: Triaged Status in liblocale-gettext-perl package in Ubuntu: New Bug description: The autopkgtests for liblocale-gettext-perl fail against glibc 2.39 with the following errors: autopkgtest [15:27:03]: test autodep8-perl-build-deps: [--- 243s t/bind.t ... 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:02 2024 243s # Current time GMT: Wed Feb 7 15:27:02 2024 243s # Using Test.pm version 1.31 243s ok 1 243s ok 243s t/frconvert.t .. 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:02 2024 243s # Current time GMT: Wed Feb 7 15:27:02 2024 243s # Using Test.pm version 1.31 243s not ok 1 243s # Failed test 1 in t/frconvert.t at line 22 243s # t/frconvert.t line 22 is: ok(0); 243s Failed 1/1 subtests 243s t/jaconvert.t .. 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s test 243s not ok 1 243s # Failed test 1 in t/jaconvert.t at line 23 243s # t/jaconvert.t line 23 is: ok(0); 243s Failed 1/1 subtests 243s t/raw.t 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s not ok 1 243s # Failed test 1 in t/raw.t at line 14 243s # t/raw.t line 14 is: ok(0); 243s Failed 1/1 subtests 243s t/use.t 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s ok 1 243s ok 243s 243s Test Summary Report 243s --- 243s t/frconvert.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s t/jaconvert.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s t/raw.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s Files=5,
[Touch-packages] [Bug 2051512] Re: apport ftbfs with Python 3.12 as the default
After further investigations into the gzip issue in python 3.12, it
turns out there was an undocumented change: it is now a buffered writer.
So the fire pattern used in the snippet above doesn't work
anymore, we now need to use it as a proper IO object instead.
I still think this should be reported upstream because of the
documentation issue, but I'll work on changing the apport code to Do The
Right 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/2051512
Title:
apport ftbfs with Python 3.12 as the default
Status in apport package in Ubuntu:
Confirmed
Status in python3-defaults package in Ubuntu:
New
Status in python3.12 package in Ubuntu:
New
Status in apport source package in Noble:
Confirmed
Status in python3-defaults source package in Noble:
New
Status in python3.12 source package in Noble:
New
Bug description:
[Description]
Python 3.12 gzip.GZipFile.write() outputs truncated data in some cases
(maybe all?)
[Test Plan]
Run the following script:
import gzip
import io
out = io.BytesIO()
gzip.GzipFile("foo", mode="wb", fileobj=out, mtime=0).write(b"FooFoo")
# print(out.getvalue())
print(gzip.decompress(out.getvalue()))
Expected output (as on Python 3.11):
FooFoo
Buggy output (tail end of the stack trace):
EOFError: Compressed file ended before the end-of-stream marker was reached
[Original report]
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
tests/run-linters --errors-only
Skipping mypy tests, mypy is not installed
Running pylint...
* Module apport-retrace
bin/apport-retrace:577:44: E0601: Using variable 'crashid' before assignment
(used-before-assignment)
make[1]: *** [debian/rules:23: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: binary] Error 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2051512/+subscriptions
--
Mailing list: https://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 2051512] Re: apport ftbfs with Python 3.12 as the default
** Also affects: python3.12 (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
-debian/rules override_dh_auto_test
+ [Description]
+
+ Python 3.12 gzip.GZipFile.write() outputs truncated data in some cases
+ (maybe all?)
+
+ [Test Plan]
+
+ Run the following script:
+
+ import gzip
+ import io
+ out = io.BytesIO()
+ gzip.GzipFile("foo", mode="wb", fileobj=out, mtime=0).write(b"FooFoo")
+ # print(out.getvalue())
+ print(gzip.decompress(out.getvalue()))
+
+ Expected output (as on Python 3.11):
+ FooFoo
+
+ Buggy output (tail end of the stack trace):
+ EOFError: Compressed file ended before the end-of-stream marker was reached
+
+ [Original report]
+
+ debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
tests/run-linters --errors-only
Skipping mypy tests, mypy is not installed
Running pylint...
* Module apport-retrace
bin/apport-retrace:577:44: E0601: Using variable 'crashid' before assignment
(used-before-assignment)
make[1]: *** [debian/rules:23: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: binary] Error 2
--
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/2051512
Title:
apport ftbfs with Python 3.12 as the default
Status in apport package in Ubuntu:
Confirmed
Status in python3-defaults package in Ubuntu:
New
Status in python3.12 package in Ubuntu:
New
Status in apport source package in Noble:
Confirmed
Status in python3-defaults source package in Noble:
New
Status in python3.12 source package in Noble:
New
Bug description:
[Description]
Python 3.12 gzip.GZipFile.write() outputs truncated data in some cases
(maybe all?)
[Test Plan]
Run the following script:
import gzip
import io
out = io.BytesIO()
gzip.GzipFile("foo", mode="wb", fileobj=out, mtime=0).write(b"FooFoo")
# print(out.getvalue())
print(gzip.decompress(out.getvalue()))
Expected output (as on Python 3.11):
FooFoo
Buggy output (tail end of the stack trace):
EOFError: Compressed file ended before the end-of-stream marker was reached
[Original report]
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
tests/run-linters --errors-only
Skipping mypy tests, mypy is not installed
Running pylint...
* Module apport-retrace
bin/apport-retrace:577:44: E0601: Using variable 'crashid' before assignment
(used-before-assignment)
make[1]: *** [debian/rules:23: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: binary] Error 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2051512/+subscriptions
--
Mailing list: https://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 2052494] Re: There is an error in the recording of timezones for some cities
Hi! Thank you for taking the time to report this. Could you confirm on which version of Ubuntu you're seeing this issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libtimezonemap in Ubuntu. https://bugs.launchpad.net/bugs/2052494 Title: There is an error in the recording of timezones for some cities Status in libtimezonemap package in Ubuntu: New Bug description: There is an error in the recording of timezones for some cities. Cities such as Zhanjiang are located in Guangdong Province, which is in the East 8 time zone, which is in the Asia/Shanghai time zone.but in the file timezonemap/src/data/cities15000.txt the city is recorded as being in East 6, the Asia/Urumqi time zone. Here is the modifications： == timezonemap/src/data/cities15000.txt 3054c3054 < 1784990 Zhanjiang Zhanjiang Chan-chiang,Chan-chiang-shih,Chankiang,Chzhan'czjan,Fort Bayard,Hsi-ying,Kwangchow,Kwangchowan,Kwangchowwan,Tram Giang,Trạm Giang,Tsamkong,ZHA,Zhanjiang,Zhanjiang Shi,zhan jiang,zhan jiang shi,Чжаньцзян,جاڭجياڭ شەھىرى,湛江,湛江市21.28145110.34271 P PPLA2 CN 30 637790 29 Asia/Shanghai 2012-01-18 --- > 1784990 Zhanjiang Zhanjiang Chan-chiang,Chan-chiang-shih,Chankiang,Chzhan'czjan,Fort Bayard,Hsi-ying,Kwangchow,Kwangchowan,Kwangchowwan,Tram Giang,Trạm Giang,Tsamkong,ZHA,Zhanjiang,Zhanjiang Shi,zhan jiang,zhan jiang shi,Чжаньцзян,جاڭجياڭ شەھىرى,湛江,湛江市21.28145110.34271 P PPLA2 CN 30 637790 29 Asia/Urumqi 2012-01-18 3108c3108 < 1787837 Xucheng Xucheng Hsu-wen,Hsu-wen-hsien,Hsü-wen,Hsü-wen-hsien,Suwen,Suwenyun,Tsuimen,Xucheng,Xucheng Jiedao,Xucheng Zhen,Xuwen,xu cheng,xu cheng jie dao,xu cheng zhen,徐城,徐城街道,徐城镇 20.32917110.16712 P PPLA3 CN 30 83267 75 Asia/Shanghai 2013-10-05 --- > 1787837 Xucheng Xucheng Hsu-wen,Hsu-wen-hsien,Hsü-wen,Hsü-wen-hsien,Suwen,Suwenyun,Tsuimen,Xucheng,Xucheng Jiedao,Xucheng Zhen,Xuwen,xu cheng,xu cheng jie dao,xu cheng zhen,徐城,徐城街道,徐城镇 20.32917110.16712 P PPLA3 CN 30 83267 75 Asia/Urumqi 2013-10-05 3318c3318 < 1800829 Wuchuan Wuchuan Hai-lu,Mei-lu-shih,Mei-mao,Meilu,Muiluk,Wuchuan,wu chuan,吴川 21.45713 110.76591 P PPL CN 30 104168 7 Asia/Shanghai 2012-01-18 --- > 1800829 Wuchuan Wuchuan Hai-lu,Mei-lu-shih,Mei-mao,Meilu,Muiluk,Wuchuan,wu chuan,吴川 21.45713 110.76591 P PPL CN 30 104168 7 Asia/Urumqi 2012-01-18 3364c3364 < 1804120 Lianjiang Lianjiang Lei-pei,Liancheng,Lianjiang,Lien-chiang,Lien-chiang-hsien,Limkong,Limkong-hsien,Lunkong,Shih-ch'eng,Shih-ch’eng,lian jiang,廉江 21.64673110.28172 P PPL CN 30 100341 46 Asia/Shanghai 2012-01-18 --- > 1804120 Lianjiang Lianjiang Lei-pei,Liancheng,Lianjiang,Lien-chiang,Lien-chiang-hsien,Limkong,Limkong-hsien,Lunkong,Shih-ch'eng,Shih-ch’eng,lian jiang,廉江 21.64673110.28172 P PPL CN 30 100341 46 Asia/Urumqi 2012-01-18 3432c3432 < 1806960 Huazhou Huazhou Fachow,Fahsien,Fu-ch'eng-chen,Fu-ch’eng-chen,Hau-hsien,Hua,Hua-chou,Hua-hsien,Huazhou 21.6110.58333 P PPL CN 30 91701 35 Asia/Shanghai 2012-01-18 --- > 1806960 Huazhou Huazhou Fachow,Fahsien,Fu-ch'eng-chen,Fu-ch’eng-chen,Hau-hsien,Hua,Hua-chou,Hua-hsien,Huazhou 21.6110.58333 P PPL CN 30 91701 35 Asia/Urumqi 2012-01-18 3484c3484 < 1810295 Gaozhou Gaozhou Gaozhou,Kao-chou,Kaochow,Kochow,Kochowfu,Mao-ming,Mao-ming-hsien,Mowming,gao zhou,高州21.93924110.84607 P PPL CN 30 166069 57 Asia/Shanghai 2012-01-18 --- > 1810295 Gaozhou Gaozhou Gaozhou,Kao-chou,Kaochow,Kochow,Kochowfu,Mao-ming,Mao-ming-hsien,Mowming,gao zhou,高州21.93924110.84607 P PPL CN 30 166069 57 Asia/Urumqi 2012-01-18 3507c3507 < 1812057 Xinyi Xinyi Dongzhen,Hsin-i,Tung-chen,Tung-chen-chen,Tung-chen-hsu,Tung-chen-hsü,Xinyi,xin yi,信宜22.37303110.94746 P PPL CN
[Touch-packages] [Bug 2049881] Re: pango1.0: FTBFS against glibc 2.39 snapshot
** Changed in: glibc (Ubuntu) Status: Triaged => Fix Released ** Changed in: pango1.0 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2049881 Title: pango1.0: FTBFS against glibc 2.39 snapshot Status in glibc package in Ubuntu: Fix Released Status in pango1.0 package in Ubuntu: Invalid Bug description: Hi, The package pango1.0 failed to build during the recent full archive test rebuild against a snapshot of the the development branch for the upcoming glibc 2.39, expected to land in Noble. This was subsequently confirmed locally against a more recent snapshot. Full logs for the FTBFS: https://launchpadlibrarian.net/706837188/buildlog_ubuntu-noble-amd64.pango1.0_1.51.0+ds-3_BUILDING.txt.gz Full report: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html PPA with glibc snapshot: https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc Snippet showing the failure: === 22/27 test: test-fonts start time: 10:25:39 duration: 0.11s result: exit status 1 command: G_TEST_SRCDIR=/<>/tests srcdir=/<>/tests LC_ALL=en_US.UTF-8 ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/pango G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MALLOC_PERTURB_=142 /<>/obj-x86_64-linux-gnu/tests/test-fonts -k --tap --- stdout --- TAP version 13 # random seed: R02Sd064b2e790c11a865b61afd5b0b7909d 1..4 # Start of fontsets tests ok 1 /fontsets/cantarell2 # Contents don't match expected contents # --- /tmp/.OQTQH22024-01-19 11:25:39.214546169 +0100 # +++ /tmp/.OSTQH22024-01-19 11:25:39.214546169 +0100 # @@ -4,7 +4,7 @@ # DejaVu Sans 20 # Noto Sans CJK JP 20 # Droid Sans Japanese 20 # -Cantarell 20 # +Cantarell 20 @wght=400 # Amiri 20 # DejaVu Sans Bold 20 # Font Awesome 5 Free Solid Heavy 20 # not ok 2 /fontsets/mono2 ok 3 /fontsets/cantarell # Contents don't match expected contents # --- /tmp/.X3URH22024-01-19 11:25:39.234546069 +0100 # +++ /tmp/.FJURH22024-01-19 11:25:39.234546069 +0100 # @@ -4,7 +4,7 @@ # DejaVu Sans 20 # Noto Sans CJK JP 20 # Droid Sans Japanese 20 # -Cantarell 20 # +Cantarell 20 @wght=400 # Amiri 20 # DejaVu Sans Bold 20 # Font Awesome 5 Free Solid Heavy 20 # not ok 4 /fontsets/mono # End of fontsets tests --- stderr --- (test program exited with status code 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2049881/+subscriptions -- Mailing list: https://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 2049881] Re: pango1.0: FTBFS against glibc 2.39 snapshot
So, after some fairly exhausting debugging, I kind of gave up on that bug, but as a last ditch effort I tried a rebuild against the latest snapshot (even though the changelog didn't seem particularly relevant), nd... Now it builds. I'm so tired. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2049881 Title: pango1.0: FTBFS against glibc 2.39 snapshot Status in glibc package in Ubuntu: Triaged Status in pango1.0 package in Ubuntu: New Bug description: Hi, The package pango1.0 failed to build during the recent full archive test rebuild against a snapshot of the the development branch for the upcoming glibc 2.39, expected to land in Noble. This was subsequently confirmed locally against a more recent snapshot. Full logs for the FTBFS: https://launchpadlibrarian.net/706837188/buildlog_ubuntu-noble-amd64.pango1.0_1.51.0+ds-3_BUILDING.txt.gz Full report: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html PPA with glibc snapshot: https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc Snippet showing the failure: === 22/27 test: test-fonts start time: 10:25:39 duration: 0.11s result: exit status 1 command: G_TEST_SRCDIR=/<>/tests srcdir=/<>/tests LC_ALL=en_US.UTF-8 ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/pango G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MALLOC_PERTURB_=142 /<>/obj-x86_64-linux-gnu/tests/test-fonts -k --tap --- stdout --- TAP version 13 # random seed: R02Sd064b2e790c11a865b61afd5b0b7909d 1..4 # Start of fontsets tests ok 1 /fontsets/cantarell2 # Contents don't match expected contents # --- /tmp/.OQTQH22024-01-19 11:25:39.214546169 +0100 # +++ /tmp/.OSTQH22024-01-19 11:25:39.214546169 +0100 # @@ -4,7 +4,7 @@ # DejaVu Sans 20 # Noto Sans CJK JP 20 # Droid Sans Japanese 20 # -Cantarell 20 # +Cantarell 20 @wght=400 # Amiri 20 # DejaVu Sans Bold 20 # Font Awesome 5 Free Solid Heavy 20 # not ok 2 /fontsets/mono2 ok 3 /fontsets/cantarell # Contents don't match expected contents # --- /tmp/.X3URH22024-01-19 11:25:39.234546069 +0100 # +++ /tmp/.FJURH22024-01-19 11:25:39.234546069 +0100 # @@ -4,7 +4,7 @@ # DejaVu Sans 20 # Noto Sans CJK JP 20 # Droid Sans Japanese 20 # -Cantarell 20 # +Cantarell 20 @wght=400 # Amiri 20 # DejaVu Sans Bold 20 # Font Awesome 5 Free Solid Heavy 20 # not ok 4 /fontsets/mono # End of fontsets tests --- stderr --- (test program exited with status code 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2049881/+subscriptions -- Mailing list: https://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 2049881] Re: pango1.0: FTBFS against glibc 2.39 snapshot
** Changed in: glibc (Ubuntu) Importance: Undecided => Critical ** Changed in: glibc (Ubuntu) Status: New => Triaged ** Changed in: glibc (Ubuntu) Assignee: (unassigned) => Simon Chopin (schopin) ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2049881 Title: pango1.0: FTBFS against glibc 2.39 snapshot Status in glibc package in Ubuntu: Triaged Status in pango1.0 package in Ubuntu: New Bug description: Hi, The package pango1.0 failed to build during the recent full archive test rebuild against a snapshot of the the development branch for the upcoming glibc 2.39, expected to land in Noble. This was subsequently confirmed locally against a more recent snapshot. Full logs for the FTBFS: https://launchpadlibrarian.net/706837188/buildlog_ubuntu-noble-amd64.pango1.0_1.51.0+ds-3_BUILDING.txt.gz Full report: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html PPA with glibc snapshot: https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc Snippet showing the failure: === 22/27 test: test-fonts start time: 10:25:39 duration: 0.11s result: exit status 1 command: G_TEST_SRCDIR=/<>/tests srcdir=/<>/tests LC_ALL=en_US.UTF-8 ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/pango G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MALLOC_PERTURB_=142 /<>/obj-x86_64-linux-gnu/tests/test-fonts -k --tap --- stdout --- TAP version 13 # random seed: R02Sd064b2e790c11a865b61afd5b0b7909d 1..4 # Start of fontsets tests ok 1 /fontsets/cantarell2 # Contents don't match expected contents # --- /tmp/.OQTQH22024-01-19 11:25:39.214546169 +0100 # +++ /tmp/.OSTQH22024-01-19 11:25:39.214546169 +0100 # @@ -4,7 +4,7 @@ # DejaVu Sans 20 # Noto Sans CJK JP 20 # Droid Sans Japanese 20 # -Cantarell 20 # +Cantarell 20 @wght=400 # Amiri 20 # DejaVu Sans Bold 20 # Font Awesome 5 Free Solid Heavy 20 # not ok 2 /fontsets/mono2 ok 3 /fontsets/cantarell # Contents don't match expected contents # --- /tmp/.X3URH22024-01-19 11:25:39.234546069 +0100 # +++ /tmp/.FJURH22024-01-19 11:25:39.234546069 +0100 # @@ -4,7 +4,7 @@ # DejaVu Sans 20 # Noto Sans CJK JP 20 # Droid Sans Japanese 20 # -Cantarell 20 # +Cantarell 20 @wght=400 # Amiri 20 # DejaVu Sans Bold 20 # Font Awesome 5 Free Solid Heavy 20 # not ok 4 /fontsets/mono # End of fontsets tests --- stderr --- (test program exited with status code 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2049881/+subscriptions -- Mailing list: https://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 2049881] Re: pango1.0: FTBFS against glibc 2.39 snapshot
I'm currently focused on cataloguing failures, but I'll try to investigate it if nobody has picked it up by then. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2049881 Title: pango1.0: FTBFS against glibc 2.39 snapshot Status in glibc package in Ubuntu: New Status in pango1.0 package in Ubuntu: New Bug description: Hi, The package pango1.0 failed to build during the recent full archive test rebuild against a snapshot of the the development branch for the upcoming glibc 2.39, expected to land in Noble. This was subsequently confirmed locally against a more recent snapshot. Full logs for the FTBFS: https://launchpadlibrarian.net/706837188/buildlog_ubuntu-noble-amd64.pango1.0_1.51.0+ds-3_BUILDING.txt.gz Full report: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html PPA with glibc snapshot: https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc Snippet showing the failure: === 22/27 test: test-fonts start time: 10:25:39 duration: 0.11s result: exit status 1 command: G_TEST_SRCDIR=/<>/tests srcdir=/<>/tests LC_ALL=en_US.UTF-8 ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/pango G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MALLOC_PERTURB_=142 /<>/obj-x86_64-linux-gnu/tests/test-fonts -k --tap --- stdout --- TAP version 13 # random seed: R02Sd064b2e790c11a865b61afd5b0b7909d 1..4 # Start of fontsets tests ok 1 /fontsets/cantarell2 # Contents don't match expected contents # --- /tmp/.OQTQH22024-01-19 11:25:39.214546169 +0100 # +++ /tmp/.OSTQH22024-01-19 11:25:39.214546169 +0100 # @@ -4,7 +4,7 @@ # DejaVu Sans 20 # Noto Sans CJK JP 20 # Droid Sans Japanese 20 # -Cantarell 20 # +Cantarell 20 @wght=400 # Amiri 20 # DejaVu Sans Bold 20 # Font Awesome 5 Free Solid Heavy 20 # not ok 2 /fontsets/mono2 ok 3 /fontsets/cantarell # Contents don't match expected contents # --- /tmp/.X3URH22024-01-19 11:25:39.234546069 +0100 # +++ /tmp/.FJURH22024-01-19 11:25:39.234546069 +0100 # @@ -4,7 +4,7 @@ # DejaVu Sans 20 # Noto Sans CJK JP 20 # Droid Sans Japanese 20 # -Cantarell 20 # +Cantarell 20 @wght=400 # Amiri 20 # DejaVu Sans Bold 20 # Font Awesome 5 Free Solid Heavy 20 # not ok 4 /fontsets/mono # End of fontsets tests --- stderr --- (test program exited with status code 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2049881/+subscriptions -- Mailing list: https://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 2049881] [NEW] pango1.0: FTBFS against glibc 2.39 snapshot
Public bug reported: Hi, The package pango1.0 failed to build during the recent full archive test rebuild against a snapshot of the the development branch for the upcoming glibc 2.39, expected to land in Noble. This was subsequently confirmed locally against a more recent snapshot. Full logs for the FTBFS: https://launchpadlibrarian.net/706837188/buildlog_ubuntu-noble-amd64.pango1.0_1.51.0+ds-3_BUILDING.txt.gz Full report: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html PPA with glibc snapshot: https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc Snippet showing the failure: === 22/27 test: test-fonts start time: 10:25:39 duration: 0.11s result: exit status 1 command: G_TEST_SRCDIR=/<>/tests srcdir=/<>/tests LC_ALL=en_US.UTF-8 ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/pango G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MALLOC_PERTURB_=142 /<>/obj-x86_64-linux-gnu/tests/test-fonts -k --tap --- stdout --- TAP version 13 # random seed: R02Sd064b2e790c11a865b61afd5b0b7909d 1..4 # Start of fontsets tests ok 1 /fontsets/cantarell2 # Contents don't match expected contents # --- /tmp/.OQTQH2 2024-01-19 11:25:39.214546169 +0100 # +++ /tmp/.OSTQH2 2024-01-19 11:25:39.214546169 +0100 # @@ -4,7 +4,7 @@ # DejaVu Sans 20 # Noto Sans CJK JP 20 # Droid Sans Japanese 20 # -Cantarell 20 # +Cantarell 20 @wght=400 # Amiri 20 # DejaVu Sans Bold 20 # Font Awesome 5 Free Solid Heavy 20 # not ok 2 /fontsets/mono2 ok 3 /fontsets/cantarell # Contents don't match expected contents # --- /tmp/.X3URH2 2024-01-19 11:25:39.234546069 +0100 # +++ /tmp/.FJURH2 2024-01-19 11:25:39.234546069 +0100 # @@ -4,7 +4,7 @@ # DejaVu Sans 20 # Noto Sans CJK JP 20 # Droid Sans Japanese 20 # -Cantarell 20 # +Cantarell 20 @wght=400 # Amiri 20 # DejaVu Sans Bold 20 # Font Awesome 5 Free Solid Heavy 20 # not ok 4 /fontsets/mono # End of fontsets tests --- stderr --- (test program exited with status code 1) ** Affects: glibc (Ubuntu) Importance: Undecided Status: New ** Affects: pango1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: test-rebuild-glibc-noble ** Also affects: glibc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2049881 Title: pango1.0: FTBFS against glibc 2.39 snapshot Status in glibc package in Ubuntu: New Status in pango1.0 package in Ubuntu: New Bug description: Hi, The package pango1.0 failed to build during the recent full archive test rebuild against a snapshot of the the development branch for the upcoming glibc 2.39, expected to land in Noble. This was subsequently confirmed locally against a more recent snapshot. Full logs for the FTBFS: https://launchpadlibrarian.net/706837188/buildlog_ubuntu-noble-amd64.pango1.0_1.51.0+ds-3_BUILDING.txt.gz Full report: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html PPA with glibc snapshot: https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc Snippet showing the failure: === 22/27 test: test-fonts start time: 10:25:39 duration: 0.11s result: exit status 1 command: G_TEST_SRCDIR=/<>/tests srcdir=/<>/tests LC_ALL=en_US.UTF-8 ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/pango G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MALLOC_PERTURB_=142 /<>/obj-x86_64-linux-gnu/tests/test-fonts -k --tap --- stdout --- TAP version 13 # random seed: R02Sd064b2e790c11a865b61afd5b0b7909d 1..4 # Start of fontsets tests ok 1 /fontsets/cantarell2 # Contents don't match expected contents # --- /tmp/.OQTQH22024-01-19 11:25:39.214546169 +0100 # +++ /tmp/.OSTQH22024-01-19 11:25:39.214546169 +0100 # @@ -4,7 +4,7 @@ # DejaVu Sans 20 # Noto Sans CJK JP 20 # Droid Sans Japanese 20 # -Cantarell 20 # +Cantarell 20 @wght=400 # Amiri 20 # DejaVu Sans Bold 20 # Font Awesome 5 Free Solid Heavy 20 # not ok 2 /fontsets/mono2 ok 3 /fontsets/cantarell # Contents don't match expected contents # --- /tmp/.X3URH22024-01-19 11:25:39.234546069 +0100 # +++ /tmp/.FJURH22024-01-19
[Touch-packages] [Bug 1568726] Re: iconv stdio buffering
** Also affects: glibc (Ubuntu) Importance: Undecided Status: New ** Changed in: glibc (Ubuntu) Status: New => Triaged ** Changed in: glibc (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1568726 Title: iconv stdio buffering Status in eglibc package in Ubuntu: Triaged Status in glibc package in Ubuntu: Triaged Bug description: Tool "iconv" suffers from the stdio buffering problem described here: https://stackoverflow.com/questions/14472179/how-do-i-perform-a- streaming-character-conversion Basically, when piping to iconv in an interactive session, output stutters. Tool "stdbuf" does not help. From the page above: "But it looks like iconv is managing the buffering internally itself - it's nothing to do with the Linux pipe buffer." Solutions are described in this page: http://www.pixelbeat.org/programming/stdio_buffering/ iconv should have a command-line switch to help. From the page above: "Note tail's stdout buffer would also have this problem, but tail -f calls fflush on the stdout stream when new data is received to alleviate this (as do tcpdump -l, grep --line-buffered and sed --unbuffered for example)." [known workaround] Use `recode` instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1568726/+subscriptions -- Mailing list: https://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 1568726] Re: iconv stdio buffering
Hi! Thanks for raising the issue. Given the relative complexity of the patch and the low number of affected people, I don't feel we should be shipping this as a Ubuntu- specific patch. It might be a better idea for you to raise the issue on the upstream ML, possibly amending the original patch to take the various review remarks into account? ** Description changed: Tool "iconv" suffers from the stdio buffering problem described here: https://stackoverflow.com/questions/14472179/how-do-i-perform-a- streaming-character-conversion Basically, when piping to iconv in an interactive session, output stutters. Tool "stdbuf" does not help. From the page above: "But it looks like iconv is managing the buffering internally itself - it's nothing to do with the Linux pipe buffer." Solutions are described in this page: http://www.pixelbeat.org/programming/stdio_buffering/ iconv should have a command-line switch to help. From the page above: "Note tail's stdout buffer would also have this problem, but tail -f calls fflush on the stdout stream when new data is received to alleviate this (as do tcpdump -l, grep --line-buffered and sed --unbuffered for example)." + + [known workaround] + Use `recode` instead. ** Changed in: eglibc (Ubuntu) Importance: Undecided => Low ** Changed in: eglibc (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1568726 Title: iconv stdio buffering Status in eglibc package in Ubuntu: Triaged Bug description: Tool "iconv" suffers from the stdio buffering problem described here: https://stackoverflow.com/questions/14472179/how-do-i-perform-a- streaming-character-conversion Basically, when piping to iconv in an interactive session, output stutters. Tool "stdbuf" does not help. From the page above: "But it looks like iconv is managing the buffering internally itself - it's nothing to do with the Linux pipe buffer." Solutions are described in this page: http://www.pixelbeat.org/programming/stdio_buffering/ iconv should have a command-line switch to help. From the page above: "Note tail's stdout buffer would also have this problem, but tail -f calls fflush on the stdout stream when new data is received to alleviate this (as do tcpdump -l, grep --line-buffered and sed --unbuffered for example)." [known workaround] Use `recode` instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1568726/+subscriptions -- Mailing list: https://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 2045250] Re: pam_lastlog doesn't handle localtime_r related errors properly
sarnold, good point!
Holger: I can't pretend speaking for the SRU team, but I'd be willing to
bet that having "the fix is trivial" as a test plan would result in the
SRU being trivially rejected :-).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/2045250
Title:
pam_lastlog doesn't handle localtime_r related errors properly
Status in Ubuntu on IBM z Systems:
New
Status in pam package in Ubuntu:
New
Status in pam package in Fedora:
Fix Released
Bug description:
The pam version(s) in Debian (checked buster) and Ubuntu (checked focal to
noble) are affected by
https://bugzilla.redhat.com/show_bug.cgi?id=2012871
Customers report a command going through PAM crashing for a given user.
A potential follow on issue can be that no ssh remote connections to an
affected server are possible anymore, esp. painful with headless systems (was
reported on a different distro).
This is caused by an issue in modules/pam_lastlog/pam_lastlog.c:
with tm = localtime_r(...) that can be NULL and needs to be handled.
There are two such cases in modules/pam_lastlog/pam_lastlog.c (here noble):
314- ll_time = last_login.ll_time;
315: if ((tm = localtime_r (_time, _buf)) != NULL) {
316- strftime (the_time, sizeof (the_time),
317- /* TRANSLATORS: "strftime options for date of last
login" */
--
574-
575- lf_time = utuser.ut_tv.tv_sec;
576: tm = localtime_r (_time, _buf);
577- strftime (the_time, sizeof (the_time),
578- /* TRANSLATORS: "strftime options for date of last login" */
Case 1 (line 315) is properly handled, but not case 2 (line 576).
The second case got fixed by:
https://github.com/linux-pam/linux-pam/commit/40c271164dbcebfc5304d0537a42fb42e6b6803c
This fix should be included in Ubuntu (and Debian).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2045250/+subscriptions
--
Mailing list: https://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 2033422] Re: openssl: backport to jammy "clear method store / query cache confusion"
Reviewed and uploaded. For the particular patch series attached to this very bug, I'm seeing the patchset as two distincts parts. First are a few optimization patches by being more selective in flushing some caches, whereas the second part are behaviour changes that belong more in the realm of fixes than optimization. Given the nature of those fixes (e.g. "Complete the cleanup of an algorithm in OSSL_METHOD_STORE"), I'm *assuming* that they were hidden by the previous aggressive flushing, especially since they originate from the same PR (https://github.com/openssl/openssl/pull/18151) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2033422 Title: openssl: backport to jammy "clear method store / query cache confusion" Status in openssl package in Ubuntu: New Status in openssl source package in Jammy: In Progress Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [ATTENTION] This SRU contains THREE changes which are listed in the section below. [Meta] This bug is part of a series of three bugs for a single SRU. This ( #2033422 ) is the "central" bug with the global information and debdiff. This SRU addresses three issues with Jammy's openssl version: - http://pad.lv/1994165: ignored SMIME signature errors - http://pad.lv/2023545: imbca engine dumps core - http://pad.lv/2033422: very high CPU usage for concurrent TLS connections (this one) The SRU information has been added to the three bug reports and I am attaching the debdiff here only for all three. All the patches have been included in subsequent openssl 3.0.x releases which in turn have been included in subsequent Ubuntu releases. There has been no report of issues when updating to these Ubuntu releases. I have rebuilt the openssl versions and used abi-compliance-checker to compare the ABIs of the libraries in jammy and the one for the SRU. Both matched completely (FYI, mantic's matched completely too). I have also pushed the code to git (without any attempt to make it git-ubuntu friendly). https://code.launchpad.net/~adrien-n/ubuntu/+source/openssl/+git/openssl/+ref/jammy- sru I asked Brian Murray about phasing speed and he concurs a slow roll-out is probably better for openssl. There is a small uncertainty because a security update could come before the phasing is over, effectively fast-forwarding the SRU. Still, unless there is already a current pre-advisory, this is probably better than a 10% phasing which is over after only a couple days anyway. NB: at the moment openssl doesn't phase slowly so this needs to be implemented. [Impact] Severely degraded performance for concurrent operations compared to openssl 1.1. The performance is so degraded that some workloads fail due to timeouts or insufficient resources (noone magically has 5 times more machines). As a consequence, a number of people use openssl 1.1 instead and do not get security updates. [Test plan] Rafael Lopez has shared a simple benchmarks in http://pad.lv/2009544 with https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2009544/+attachment/5690224/+files/main.py . To test, follow these steps: - run "time python3 main.py" # using the aforementioned main.py script - apt install -t jammy-proposed libssl3 - run "time python3 main.py" - compare the runtimes for the two main.py runs You can run this on x86_64, Raspberry Pi 4 or any machine, and get a very large speed-up in all cases. The improvements are not architecture-dependant. Using this changeset, I get the following numbers for ten runs on my laptop: 3.0.2: real 2m5.567s user 4m3.948s sys 2m0.233s this SRU: real 0m23.966s user 2m35.687s sys 0m1.920s As can be easily seen, the speed-up is massive: system time is divided by 60 and overall wall clock time is roughly five times lower. In http://pad.lv/2009544 , Rafael also shared his performance numbers and they are relatable to these. He used slightly different versions (upstreams rather than patched with cherry-picks) but at least one of the version used does not include other performance change. He also used different hardware and this performance issue seems to depend on the number of CPUs available but also obtained a performance several times better. Results on a given machine vary also very little across runs (less than 2% variation on runs of size 10). They are also very similar on a Raspberry Pi 4 (8GB). The benchmark uses https://www.google.com/humans.txt which takes around 130ms to download on my machine but I modified the script to download something only 20ms away. Results are so close to the ones using humans.txt that they are within the error margin. This is consistent with the high-concurrency in the
[Touch-packages] [Bug 2044159] Re: Ubuntu-bug triggers an error cloud-init run data not found on system. Unable to add cloud-specific data
Hi! Thank you for filing a bug and contributing to Ubuntu. We're able to partially confirm this bug by simply having cloud-init installed on our system and running `ubuntu-bug libc6`, which will start off by printing 'cloud-init run data not found on system. Unable to add cloud-specific data.' on stderr. However, this didn't prevent us from filing bugs, either on a GUI environment or in a terminal-only chroot. Could you give us more details about the cases where it prevented you from filing a bug? ** Changed in: apport (Ubuntu) Status: Confirmed => Incomplete -- 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/2044159 Title: Ubuntu-bug triggers an error cloud-init run data not found on system. Unable to add cloud-specific data Status in apport package in Ubuntu: Incomplete Bug description: Ubuntu-desktop 24.04 development branch @ 21/11/2023 When filing individual bugs from terminal using ubuntu-bug package i'm getting an error: cloud-init run data not found on system. Unable to add cloud-specific data wich in some cases prevents me to file the bug ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: apport 2.27.0-0ubuntu6 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportLog: ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 21 18:06:19 2023 InstallationDate: Installed on 2023-11-09 (12 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) PackageArchitecture: all ProcEnviron: LANG=nl_NL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: apport UpgradeStatus: Upgraded to noble on 2023-11-09 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2044159/+subscriptions -- Mailing list: https://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 2006981] Re: apport-gtk crashed with signal 5 in g_log_writer_default()
Little bit of data here. For some reason glib2.0 is thinking we're in a GDB context and so is spitting out a SIGTRAP rather than the expected SIGABRT, see https://sources.debian.org/src/glib2.0/2.78.3-1/glib/gmessages.c/#L556 Now, why is it aborting I'm not too sure. The stack trace gives us a hint, as it seems it's failing to detect a graphical environment. Did the crash appear spontaneously on the desktop, or were you trying to report another bug? ** Changed in: apport (Ubuntu) Status: Confirmed => Incomplete -- 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/2006981 Title: apport-gtk crashed with signal 5 in g_log_writer_default() Status in apport package in Ubuntu: Incomplete Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: I can´t provide any other information other than what was collected. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: apport-gtk 2.24.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 640:1000:124:9017369:2023-02-10 20:09:56.662793636 -0300:2023-02-10 20:09:57.662793636 -0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash 640:1000:124:1463707:2023-02-10 20:09:58.698746919 -0300:2023-02-10 20:09:59.698746919 -0300:/var/crash/_usr_bin_kwin_x11.1000.crash 640:1000:124:633811:2023-02-10 20:09:59.986718177 -0300:2023-02-10 20:10:00.986718177 -0300:/var/crash/_usr_bin_xembedsniproxy.1000.crash 640:1000:124:653094:2023-02-10 20:10:01.258690357 -0300:2023-02-10 20:10:02.258690357 -0300:/var/crash/_usr_bin_gmenudbusmenuproxy.1000.crash 640:1000:124:990:2023-02-10 20:10:05.770595073 -0300:2023-02-10 20:10:06.770595073 -0300:/var/crash/_usr_share_apport_apport-gtk.1000.crash CurrentDesktop: KDE Date: Fri Feb 10 20:10:04 2023 ExecutablePath: /usr/share/apport/apport-gtk InterpreterPath: /usr/bin/python3.11 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonDetails: N/A Signal: 5 SourcePackage: apport StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: apport-gtk crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2006981/+subscriptions -- Mailing list: https://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 2046474] Re: Ubuntu-bug in terminal few errors
Hi again!
Thanks for filing the multiple detailed bugs, this is greatly
appreciated as it makes triaging much easier!
In this instance, I'm closing this as Invalid since this output isn't
directly apport/ubuntu-bug related, it's the output of some tools we're
invoking under the hood, and/or GTK being its verbose self. There isn't
much we can do about it.
Cheers!
** Changed in: apport (Ubuntu)
Status: New => Invalid
--
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/2046474
Title:
Ubuntu-bug in terminal few errors
Status in apport package in Ubuntu:
Invalid
Bug description:
Ubuntu-bug in terminal few errors
ubuntu-bug -w
update.go:85: cannot change mount namespace according to change mount
(/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none
bind,ro 0 0): cannot open directory "/var/lib": permission denied
update.go:85: cannot change mount namespace according to change mount
(/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0):
cannot open directory "/var/lib": permission denied
update.go:85: cannot change mount namespace according to change mount
(/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none
bind,ro 0 0): cannot open directory "/var/lib": permission denied
Gtk-Message: 18:43:25.874: Failed to load module
"window-decorations-gtk-module"
Gtk-Message: 18:43:25.874: Failed to load module "colorreload-gtk-module"
kng@kng-300E5EV-300E4EV-270E5EV-270E4EV:~$ ATTENTION: default value of option
mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
[ERROR glean_core] Error setting metrics feature config: Json(Error("EOF
while parsing a value", line: 1, column: 0))
ALSA lib conf.c:4120:(snd_config_update_r) Cannot access file
/usr/share/alsa/alsa.conf
ALSA lib seq.c:935:(snd_seq_open_noupdate) Unknown SEQ default
[Parent 10803, IPC I/O Parent] WARNING: process 11194 exited on signal 9:
file
/build/firefox/parts/firefox/build/ipc/chromium/src/base/process_util_posix.cc:266
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apport 2.20.11-0ubuntu82.5
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CrashReports:
640:1000:125:10103500:2023-12-14 16:45:11.104133895 +0200:2023-12-14
16:45:07.048100891 +0200:/var/crash/_usr_bin_kwin_x11.1000.crash
640:1000:125:7629821:2023-12-14 15:37:52.752158527 +0200:2023-12-14
15:37:50.912875521 +0200:/var/crash/_usr_bin_dolphin.1000.crash
CurrentDesktop: KDE
Date: Thu Dec 14 19:16:42 2023
InstallationDate: Installed on 2021-03-10 (1009 days ago)
InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to jammy on 2023-05-08 (220 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2046474/+subscriptions
--
Mailing list: https://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 2048112] Re: Ubuntu-bug ask for password to find out that bug is for snap app and gives info where to report. Instead it should save resources and check that first
Hi, thanks for taking the time to report this issue and contributing to Ubuntu :) I confirmed this issue (along with the one with firefox snap vs deb). This is a bit bigger of an issue, as it means some non-privileged users won't be able to report issues (or at least would give up as soon as the prompt comes up), thus marking as Medium. ** Changed in: apport (Ubuntu) Status: New => Triaged ** Changed in: apport (Ubuntu) Importance: Undecided => Medium ** Summary changed: - Ubuntu-bug ask for password to find out that bug is for snap app and gives info where to report. Instead it should save resources and check that first + Ubuntu-bug prompts for admin password before selecting the target package -- 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/2048112 Title: Ubuntu-bug prompts for admin password before selecting the target package Status in apport package in Ubuntu: Triaged Bug description: Ubuntu-bug ask for password to find out that bug is for snap app and gives info where to report. Instead it should save resources and check that first and password not needed to give just info of another bug reporting location ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu82.5 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Jan 4 21:15:17 2024 InstallationDate: Installed on 2024-01-04 (0 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2048112/+subscriptions -- Mailing list: https://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 2047999] Re: Ubuntu-bug thinks i have 2 firefox installed
Hi, thanks for taking the time to report this issue and contributing to Ubuntu :) I just confirmed on my system. Since the number of transitional packages is fairly small, I think we should just maintain a hardcoded list in Apport and hide the .deb by default (with maybe a way to override this?) Marking as Low priority, since this is IMHO something of a papercut (still annoying, though!) ** Changed in: apport (Ubuntu) Status: New => Triaged ** Changed in: apport (Ubuntu) Importance: Undecided => Low ** Summary changed: - Ubuntu-bug thinks i have 2 firefox installed + ubuntu-bug shows both the snap and the transitional deb -- 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/2047999 Title: ubuntu-bug shows both the snap and the transitional deb Status in apport package in Ubuntu: Triaged Bug description: Make 22.04.3 usb live make ubuntu-bug firefox it says cant- its snap app learn how to update snap sudo snap refresh sudo snap refresh ubuntu-bug firefox see screenshot- asks about 2 different snaps why previous is not removed? why before it said that snap cant be reported? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu82.5 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportLog: ERROR: apport (pid 7549) Thu Jan 4 03:01:09 2024: called for pid 1362, signal 6, core limit 0, dump mode 1 ERROR: apport (pid 7549) Thu Jan 4 03:01:09 2024: executable: /usr/lib/systemd/systemd-journald (command line "/lib/systemd/systemd-journald") ERROR: apport (pid 7549) Thu Jan 4 03:01:09 2024: wrote report /var/crash/_usr_lib_systemd_systemd-journald.0.crash ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470.2 CrashReports: 640:0:124:308838:2024-01-04 03:01:09.572926187 +:2024-01-04 03:01:09.480938425 +:/var/crash/_usr_lib_systemd_systemd-journald.0.crash CurrentDesktop: KDE Date: Thu Jan 4 03:59:27 2024 LiveMediaBuild: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2047999/+subscriptions -- Mailing list: https://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 2033422] Re: openssl: backport to jammy "clear method store / query cache confusion"
** Changed in: openssl (Ubuntu Jammy) Assignee: Adrien Nader (adrien-n) => Simon Chopin (schopin) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2033422 Title: openssl: backport to jammy "clear method store / query cache confusion" Status in openssl package in Ubuntu: New Status in openssl source package in Jammy: In Progress Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [ATTENTION] This SRU contains THREE changes which are listed in the section below. [Meta] This bug is part of a series of three bugs for a single SRU. This ( #2033422 ) is the "central" bug with the global information and debdiff. This SRU addresses three issues with Jammy's openssl version: - http://pad.lv/1994165: ignored SMIME signature errors - http://pad.lv/2023545: imbca engine dumps core - http://pad.lv/2033422: very high CPU usage for concurrent TLS connections (this one) The SRU information has been added to the three bug reports and I am attaching the debdiff here only for all three. All the patches have been included in subsequent openssl 3.0.x releases which in turn have been included in subsequent Ubuntu releases. There has been no report of issues when updating to these Ubuntu releases. I have rebuilt the openssl versions and used abi-compliance-checker to compare the ABIs of the libraries in jammy and the one for the SRU. Both matched completely (FYI, mantic's matched completely too). I have also pushed the code to git (without any attempt to make it git-ubuntu friendly). https://code.launchpad.net/~adrien-n/ubuntu/+source/openssl/+git/openssl/+ref/jammy- sru I asked Brian Murray about phasing speed and he concurs a slow roll-out is probably better for openssl. There is a small uncertainty because a security update could come before the phasing is over, effectively fast-forwarding the SRU. Still, unless there is already a current pre-advisory, this is probably better than a 10% phasing which is over after only a couple days anyway. NB: at the moment openssl doesn't phase slowly so this needs to be implemented. [Impact] Severely degraded performance for concurrent operations compared to openssl 1.1. The performance is so degraded that some workloads fail due to timeouts or insufficient resources (noone magically has 5 times more machines). As a consequence, a number of people use openssl 1.1 instead and do not get security updates. [Test plan] Rafael Lopez has shared a simple benchmarks in http://pad.lv/2009544 with https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2009544/+attachment/5690224/+files/main.py . To test, follow these steps: - run "time python3 main.py" # using the aforementioned main.py script - apt install -t jammy-proposed libssl3 - run "time python3 main.py" - compare the runtimes for the two main.py runs You can run this on x86_64, Raspberry Pi 4 or any machine, and get a very large speed-up in all cases. The improvements are not architecture-dependant. Using this changeset, I get the following numbers for ten runs on my laptop: 3.0.2: real 2m5.567s user 4m3.948s sys 2m0.233s this SRU: real 0m23.966s user 2m35.687s sys 0m1.920s As can be easily seen, the speed-up is massive: system time is divided by 60 and overall wall clock time is roughly five times lower. In http://pad.lv/2009544 , Rafael also shared his performance numbers and they are relatable to these. He used slightly different versions (upstreams rather than patched with cherry-picks) but at least one of the version used does not include other performance change. He also used different hardware and this performance issue seems to depend on the number of CPUs available but also obtained a performance several times better. Results on a given machine vary also very little across runs (less than 2% variation on runs of size 10). They are also very similar on a Raspberry Pi 4 (8GB). The benchmark uses https://www.google.com/humans.txt which takes around 130ms to download on my machine but I modified the script to download something only 20ms away. Results are so close to the ones using humans.txt that they are within the error margin. This is consistent with the high-concurrency in the benchmark which both saturates CPU, and "hides" latencies that are relatively low. Finally, there are positive reports on github. Unfortunately they are not always completely targeted at these patches only and therefore I will not link directly to them but they have also been encouraging. [Where problems could occur] The change is spread over several patches which touch the internals of openssl. As such, the engine and pro
[Touch-packages] [Bug 2044104] Re: [UBUNTU 20.04] chzdev -e is rebuilding initramfs even with zdev:early=0 set
Tagging this to discuss this during the Foundations weekly meeting ** Tags added: rls-ff-incoming rls-jj-incoming -- 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/2044104 Title: [UBUNTU 20.04] chzdev -e is rebuilding initramfs even with zdev:early=0 set Status in Ubuntu on IBM z Systems: New Status in initramfs-tools package in Ubuntu: New Status in s390-tools package in Ubuntu: New Bug description: Versions: Ubuntu 20.04.5 s390-tools version 2.12.0-0ubuntu3.7.s390x Ubuntu 22.04.2 s390-tools version 2.20.0-0ubuntu3.2.s390x When I configure a zfcp LUN persistently via chzdev, the initrd is being rebuilt even with parameter zdev:early=0 root@a8315003:~# chzdev -e zfcp-lun 0.0.1803:0x500507630910d430:0x40194092 zdev:early=0 zFCP LUN 0.0.1803:0x500507630910d430:0x40194092 configured Note: The initial RAM-disk must be updated for these changes to take effect: - zFCP LUN 0.0.1803:0x500507630910d430:0x40194092 update-initramfs: Generating /boot/initrd.img-5.15.0-60-generic I: The initramfs will attempt to resume from /dev/dasdb1 I: (UUID=e70ecb80-4d1e-4074-9cda-ce231ad6e698) I: Set the RESUME variable to override this. Using config file '/etc/zipl.conf' Building bootmap in '/boot' Adding IPL section 'ubuntu' (default) Preparing boot device: dasda (c00a). Done. root@a8315003:~# == Comment: - Thorsten Diehl - 2023-03-01 06:55:47 == @BOE-dev This behaviour is unexpected. https://www.ibm.com/docs/en/linux-on-systems?topic=commands-chzdev says: Activating a device early during the boot process Use the zdev:early device attribute to activate a device early during the boot process and to override any existing auto-configuration with a persistent device configuration. zdev:early=1 The device is activated during the initial RAM disc phase according to the persistent configuration. zdev:early=0 The device is activated as usual during the boot process. This is the default. If auto-configuration data is present, the device is activated during the initial RAM disc phase according to the auto-configuration. I can't interprete a SCSI LUN as a device with auto configuration data. (At least, if the zfcp device hasn't NPIV enabled) == Comment: #5 - Peter Oberparleiter - 2023-03-01 11:18:28 == (In reply to comment #2) > @BOE-dev > This behaviour is unexpected. > https://www.ibm.com/docs/en/linux-on-systems?topic=commands-chzdev says: > Activating a device early during the boot process > > Use the zdev:early device attribute to activate a device early during the > boot process and to override any existing auto-configuration with a > persistent device configuration. > > zdev:early=1 > The device is activated during the initial RAM disc phase according to > the persistent configuration. > > zdev:early=0 > The device is activated as usual during the boot process. This is the > default. If auto-configuration data is present, the device is activated > during the initial RAM disc phase according to the auto-configuration. The documentation is incorrect for Ubuntu. Canonical specifically builds zdev in a way that every change to persistent device configuration causes an update to the initial RAM-disk. See also: https://bugzilla.linux.ibm.com/show_bug.cgi?id=187578#c35 https://github.com/ibm-s390-linux/s390-tools/commit/7dd03eaeecdd0e2674f145aca34be1275d291bd8 > I can't interprete a SCSI LUN as a device with auto configuration data. (At > least, if the zfcp device hasn't NPIV enabled) This is related to auto-configuration as implemented for DPM. == Comment: #6 - Thorsten Diehl - 2023-03-03 12:41:44 == So, IIUC, chzdev is built for Ubuntu with ZDEV_ALWAYS_UPDATE_INITRD=1, which make the parameter zdev:early=0 ineffective. Correct? If you confirm, you may also close this bug. Not nice - then we have to find an alternate solution. == Comment: #7 - Peter Oberparleiter - 2023-03-07 06:48:07 == (In reply to comment #6) > So, IIUC, chzdev is built for Ubuntu with ZDEV_ALWAYS_UPDATE_INITRD=1, which > make the parameter zdev:early=0 ineffective. Correct? > If you confirm, you may also close this bug. > > Not nice - then we have to find an alternate solution. chzdev -p on Ubuntu will by default rebuild the initrd. This is intended behavior by Canonical and controlled by the ZDEV_ALWAYS_UPDATE_INITRD build-time switch. You can suppress it by adding option --no-root-update to the command line. Specifying zdev:early=0 to chzdev has exactly the effect that it is supposed to have: it tells zdev not to enable that device during initrd processing, resulting in the corresponding udev rule not being copied to the initrd [1]. Unfortunately there is another Ubuntu-initrd script
Re: [Touch-packages] [Bug 2041830] Re: /usr/bin/gdb:6:dump_core:internal_vproblem:internal_verror:internal_error_loc:objfile::text_section_offset
How about directly sending a SIGSEGV or a SIGABRT to a working teamviewer process using kill(1) ? That's what I usually do when I test apport crash reporting code, this might trigger the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2041830 Title: /usr/bin/gdb:6:dump_core:internal_vproblem:internal_verror:internal_error_loc:objfile::text_section_offset Status in gdb package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gdb. This problem was most recently seen with package version 14.0.50.20230907-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e052ff0ad61743594bf64a85ca1e18b6e353025d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2041830/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1962549] Re: openssl cms -decrypt doesn't work properly when using an engine
> I don't know why LP expired this bug since you commented after I changed > the its status... AFAIK, LP will not switch back the status to anything after a comment has been left. That makes sense, as it wouldn't know what the new status is supposed to be. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1962549 Title: openssl cms -decrypt doesn't work properly when using an engine Status in openssl package in Ubuntu: New Bug description: I'm using: bsci@ip-10-132-42-225:~/test$ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 bsci@ip-10-132-42-225:~/test$ apt-cache policy openssl openssl: Installed: 1.1.1f-1ubuntu2.10 Candidate: 1.1.1f-1ubuntu2.10 Version table: *** 1.1.1f-1ubuntu2.10 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.1f-1ubuntu2.8 500 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 1.1.1f-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages I have a private EC key held in a TPM 2.0 platform hierarchy. I'm encrypting a message like this: openssl cms -encrypt -in message.txt -out message.cipher transport.pem Here, transport.pem is the cert. for the EC key held in the TPM. I'm attempting to decrypt like this: openssl cms -decrypt -in message.cipher -out /dev/stdout -inkey 0x8181 -keyform engine -engine tpm2tss -recip transport.pem Instead of seeing the original message text, I'm getting the following error: engine "tpm2tss" set. Error decrypting CMS using private key 139626757388096:error:1010107D:elliptic curve routines:ecdh_simple_compute_key:missing private key:../crypto/ec/ecdh_ossl.c:61: It seems that the code is expecting the actual private key instead of using the key held in the TPM? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1962549/+subscriptions -- Mailing list: https://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 2023545] Re: [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate
A version containing a fix for this has been uploaded to the Jammy queue to be processed by the SRU team. Thanks, Adrien :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2023545 Title: [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate Status in Ubuntu on IBM z Systems: In Progress Status in openssl package in Ubuntu: In Progress Status in openssl source package in Jammy: In Progress Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [Meta] This bug is part of a series of four bugs for a single SRU. The "central" bug with the global information and debdiff is http://pad.lv/2033422 [Impact] Openssl using an engine dumps core upon certificate creation; other operations are probably affected too. Overall, engines are likely mostly unusable. [Test plan] An engine is needed to test the fix and I don't think we have many in the archive. This complicates reproducing the issue. I have been relying on user reports which have been very detailled and helpful. The issue has also been reported independently and with another engine (devcrypto). The issue is fixed in openssl 3.0.8 which landed in lunar. [Where problems could occur] I don't pretend to understand the lifecycle of providers in openssl3 but the patch is simple and has been widely tested by now, including on ubuntu. Thus, I see little chance an unexpected problem would occur with it. [Patches] The patches come directly from upstream and apply cleanly. https://github.com/openssl/openssl/issues/18578 * https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy- sru-0001-Release-the-drbg-in-the-global-default-context- befor.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0 === Original description === openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem -keyout __key.pem --subj '/CN=US' ---Problem Description--- OpenSSL with ibmca engine configured dumps core when creating a new certificate. # openssl engine (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support # openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem -keyout __key.pem --subj '/CN=US' Segmentation fault (core dumped) # journalctl Jun 07 13:06:08 SYSTEM kernel: User process fault: interruption code 003b ilc:2 in libc.so.6[3ffae08+1ca000] Jun 07 13:06:08 SYSTEM kernel: Failing address: TEID: 0800 Jun 07 13:06:08 SYSTEM kernel: Fault in primary space mode while using user ASCE. Jun 07 13:06:08 SYSTEM kernel: AS:9c2941c7 R3:0024 Jun 07 13:06:08 SYSTEM kernel: CPU: 2 PID: 2344 Comm: openssl Kdump: loaded Not tainted 5.15.0-73-generic #80-Ubuntu Jun 07 13:06:08 SYSTEM kernel: Hardware name: IBM 3931 A01 703 (z/VM 7.3.0) Jun 07 13:06:08 SYSTEM kernel: User PSW : 070500018000 03ffae11c708 Jun 07 13:06:08 SYSTEM kernel:R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:0 PM:0 RI:0 EA:3 Jun 07 13:06:08 SYSTEM kernel: User GPRS: 0007 03ffae11c6f0 02aa3289f9d0 Jun 07 13:06:08 SYSTEM kernel:02aa1825980f 02aa3289f9d0 02aa328a4300 Jun 07 13:06:08 SYSTEM kernel:03ffae870720 03ffae657128 02aa03ff Jun 07 13:06:08 SYSTEM kernel:03ffae24dd10 03ffae657120 03ffae437c22 03ffec2fe000 Jun 07 13:06:08 SYSTEM kernel: User Code: 03ffae11c6fc: b90400b2 lgr%r11,%r2 03ffae11c700: 4700bc0,0 #03ffae11c704: b24f00a0ear%r10,%a0 >03ffae11c708: 58102018l%r1,24(%r2) 03ffae11c70c: ebaa002dsllg%r10,%r10,32 03ffae11c712: b24f00a1ear%r10,%a1 03ffae11c716: 5910a0d0c%r1,208(%r10) 03ffae11c71a: a7840033brc8,03ffae11c780 Jun 07 13:06:08 SYSTEM kernel: Last Breaking-Event-Address: Jun 07 13:06:08 SYSTEM kernel: [<03ffae33242c>] 0x3ffae33242c Jun 07 13:06:08 SYSTEM systemd[1]: Started Process Core Dump (PID 2345/UID 0). Jun 07 13:06:08 SYSTEM systemd-coredump[2350]: Process 2344 (openssl) of user 0 dumped core.
[Touch-packages] [Bug 1994165] Re: CMS_final: do not ignore CMS_dataFinal result
A version containing a fix for this has been uploaded to the Jammy queue to be processed by the SRU team. Thanks, Adrien :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1994165 Title: CMS_final: do not ignore CMS_dataFinal result Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Jammy: In Progress Status in openssl source package in Kinetic: Won't Fix Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [Meta] This bug is part of a series of four bugs for a single SRU. The "central" bug with the global information and debdiff is http://pad.lv/2033422 [Impact] S/MIME signature can fail silently The commit by upstream propagates the return code of some functions rather than ignore it. [Test plan] This issue is not very simple to reproduce because "openssl cms" cannot be used to do so. This has to be done with the openssl API instead. At least the bug reportere here and the one on openssl's bug tracker have confirmed the patch solves the issue. Additionally, the bug reporter here has tested the PPA that contains the patche and validated it. Finally, I read through the patch attentively. [Where problems could occur] At this point it is unlikely an error would appear. The openssl bug tracker mentions nothing related to this patch which landed more than a year ago. The patch is simple and doesn't change the code logic. [Patches] The patches come directly from upstream and apply cleanly. https://github.com/openssl/openssl/pull/18876 * https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0001-REGRESSION-CMS_final-do-not-ignore-CMS_dataFinal-res.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0 * https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0002-Handle-SMIME_crlf_copy-return-code.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0 === Original description === https://github.com/openssl/openssl/pull/18876 The CMS_dataFinal result is important as signature may fail, however, it is ignored while returning success from CMS_final. Please add this fix to The openssl 3.0.2 "Jammy Jellyfish (supported)" Thanks Upstream commit: ``` commit 67c0460b89cc1b0644a1a59af78284dfd8d720af Author: Alon Bar-Lev Date: Tue Jul 26 15:17:06 2022 +0300 Handle SMIME_crlf_copy return code Currently the SMIME_crlf_copy result is ignored in all usages. It does return failure when memory allocation fails. This patch handles the SMIME_crlf_copy return code in all occurrences. Signed-off-by: Alon Bar-Lev Reviewed-by: Tomas Mraz Reviewed-by: Paul Dale Reviewed-by: Hugo Landau (Merged from https://github.com/openssl/openssl/pull/18876) ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1994165/+subscriptions -- Mailing list: https://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 2033422] Re: openssl: backport to jammy "clear method store / query cache confusion"
A version containing a fix for this has been uploaded to the Jammy queue to be processed by the SRU team. Thanks, Adrien :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2033422 Title: openssl: backport to jammy "clear method store / query cache confusion" Status in openssl package in Ubuntu: New Status in openssl source package in Jammy: In Progress Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [ATTENTION] This SRU contains FOUR changes which are listed in the section below. [Meta] This bug is part of a series of four bugs for a single SRU. This ( #2033422 ) is the "central" bug with the global information and debdiff. This SRU addresses four issues with Jammy's openssl version: - http://pad.lv/1994165: ignored SMIME signature errors - http://pad.lv/2023545: imbca engine dumps core - http://pad.lv/2033422: very high CPU usage for concurrent TLS connections The SRU information has been added to the four bug reports and I am attaching the debdiff here only for all four. All the patches have been included in subsequent openssl 3.0.x releases which in turn have been included in subsequent Ubuntu releases. There has been no report of issues when updating to these Ubuntu releases. I have rebuilt the openssl versions and used abi-compliance-checker to compare the ABIs of the libraries in jammy and the one for the SRU. Both matched completely (FYI, mantic's matched completely too). I have also pushed the code to git (without any attempt to make it git-ubuntu friendly). https://code.launchpad.net/~adrien-n/ubuntu/+source/openssl/+git/openssl/+ref/jammy- sru I asked Brian Murray about phasing speed and he concurs a slow roll-out is probably better for openssl. There is a small uncertainty because a security update could come before the phasing is over, effectively fast-forwarding the SRU. Still, unless there is already a current pre-advisory, this is probably better than a 10% phasing which is over after only a couple days anyway. NB: at the moment openssl doesn't phase slowly so this needs to be implemented. [Impact] Severely degraded performance for concurrent operations compared to openssl 1.1. The performance is so degraded that some workloads fail due to timeouts or insufficient resources (noone magically has 5 times more machines). As a consequence, a number of people use openssl 1.1 instead and do not get security updates. [Test plan] Rafael Lopez has shared a simple benchmarks in http://pad.lv/2009544 with https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2009544/+attachment/5690224/+files/main.py . To test, follow these steps: - run "time python3 main.py" # using the aforementioned main.py script - apt install -t jammy-proposed libssl3 - run "time python3 main.py" - compare the runtimes for the two main.py runs You can run this on x86_64, Raspberry Pi 4 or any machine, and get a very large speed-up in all cases. The improvements are not architecture-dependant. Using this changeset, I get the following numbers for ten runs on my laptop: 3.0.2: real 2m5.567s user 4m3.948s sys 2m0.233s this SRU: real 0m23.966s user 2m35.687s sys 0m1.920s As can be easily seen, the speed-up is massive: system time is divided by 60 and overall wall clock time is roughly five times lower. In http://pad.lv/2009544 , Rafael also shared his performance numbers and they are relatable to these. He used slightly different versions (upstreams rather than patched with cherry-picks) but at least one of the version used does not include other performance change. He also used different hardware and this performance issue seems to depend on the number of CPUs available but also obtained a performance several times better. Results on a given machine vary also very little across runs (less than 2% variation on runs of size 10). They are also very similar on a Raspberry Pi 4 (8GB). The benchmark uses https://www.google.com/humans.txt which takes around 130ms to download on my machine but I modified the script to download something only 20ms away. Results are so close to the ones using humans.txt that they are within the error margin. This is consistent with the high-concurrency in the benchmark which both saturates CPU, and "hides" latencies that are relatively low. Finally, there are positive reports on github. Unfortunately they are not always completely targeted at these patches only and therefore I will not link directly to them but they have also been encouraging. [Where problems could occur] The change is spread over several patches which touch the internals of openssl. As such, the engine and provider functionality could be broken by these
[Touch-packages] [Bug 2033422] Re: openssl: backport to jammy "clear method store / query cache confusion"
In addition, could the test plan maybe be edited to answer the following question? "How can one validate that the package in -proposed addresses the issue?" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2033422 Title: openssl: backport to jammy "clear method store / query cache confusion" Status in openssl package in Ubuntu: New Status in openssl source package in Jammy: In Progress Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [ATTENTION] This SRU contains FOUR changes which are listed in the section below. [Meta] This bug is part of a series of four bugs for a single SRU. This ( #2033422 ) is the "central" bug with the global information and debdiff. This SRU addresses four issues with Jammy's openssl version: - http://pad.lv/1990216: Blowfish OFB/CFB decryption - http://pad.lv/1994165: ignored SMIME signature errors - http://pad.lv/2023545: imbca engine dumps core - http://pad.lv/2033422: very high CPU usage for concurrent TLS connections The SRU information has been added to the four bug reports and I am attaching the debdiff here only for all four. All the patches have been included in subsequent openssl 3.0.x releases which in turn have been included in subsequent Ubuntu releases. There has been no report of issues when updating to these Ubuntu releases. I have rebuilt the openssl versions and used abi-compliance-checker to compare the ABIs of the libraries in jammy and the one for the SRU. Both matched completely (FYI, mantic's matched completely too). The patch related to blowfish presents an annoying situation: jammy's openssl creates incompatible files and cannot read other files but fixing it will lead to files created on jammy so far to become unreadable. Fortunately, blowfish is long-deprecated and applications can be improved to handle this situation if the need arises in practice. This is stated in the SRU information in the bug and in d/changelog. The current situation in Jammy could be a security issue but due to the aforementioned deprecation, the low usage of blowfish and the fact that upstream didn't consider this worthy of a security notice, we (this includes the security team) chose not to pursue that path either. I have also pushed the code to git (without any attempt to make it git-ubuntu friendly). https://code.launchpad.net/~adrien-n/ubuntu/+source/openssl/+git/openssl/+ref/jammy- sru I asked Brian Murray about phasing speed and he concurs a slow roll-out is probably better for openssl. There is a small uncertainty because a security update could come before the phasing is over, effectively fast-forwarding the SRU. Still, unless there is already a current pre-advisory, this is probably better than a 10% phasing which is over after only a couple days anyway. NB: at the moment openssl doesn't phase slowly so this needs to be implemented. [Impact] Severely degraded performance for concurrent operations compared to openssl 1.1. The performance is so degraded that some workloads fail due to timeouts or insufficient resources (noone magically has 5 times more machines). As a consequence, a number of people use openssl 1.1 instead and do not get security updates. [Test plan] Rafael Lopez has shared a simple benchmarks in http://pad.lv/2009544 with https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2009544/+attachment/5690224/+files/main.py . Using this, I get the following numbers on my laptop: 3.0.2: real 2m5.567s user 4m3.948s sys 2m0.233s this SRU: real 0m23.966s user 2m35.687s sys 0m1.920s As can be easily seen, the speed-up is massive: system time is divided by 60 and overall wall clock time is roughly five times lower. In http://pad.lv/2009544 , Rafael also shared his performance numbers and they are relatable to these. He used slightly different versions (upstreams rather than patched with cherry-picks) but at least one of the version used does not include other performance change. He also used different hardware and this performance issue seems to depend on the number of CPUs available but also obtained a performance several times better. Results on a given machine vary also very little across runs (less than 2% variation on runs of size 10). They are also very similar on a Raspberry Pi 4 (8GB). The benchmark uses https://www.google.com/humans.txt which takes around 130ms to download on my machine but I modified the script to download something only 20ms away. Results are so close to the ones using humans.txt that they are within the error margin. This is consistent with the high-concurrency in the benchmark which both saturates CPU, and "hides" latencies that are relatively low. Finally, there are
[Touch-packages] [Bug 1990216] Re: backport fix for "OpenSSL 3 cannot decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or CFB modes" to Jammy
I'm very much against uploading this fix as an SRU. While it is a shame
that we have interop problems with the rest of the world, fixing this in
Jammy right now means we *will* break production for anyone that stores
Blowfish-encrypted data.
Doing `apt upgrade` on a production server is supposed to be a fairly
routine affair, whereas running into the interop issue means someone
somewhere did a dist-upgrade, changed some configuration, wrote new
code, or installed a new system, all of which are actions where the user
*should* expect possible breakage.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1990216
Title:
backport fix for "OpenSSL 3 cannot decrypt data encrypted with OpenSSL
1.1 with blowfish in OFB or CFB modes" to Jammy
Status in openssl package in Ubuntu:
Fix Released
Status in openssl source package in Jammy:
In Progress
Status in openssl source package in Lunar:
Fix Released
Bug description:
=== SRU information ===
[Meta]
This bug is part of a series of four bugs for a single SRU.
The "central" bug with the global information and debdiff is
http://pad.lv/2033422
[Impact]
Decryption for Blowfish with OFB and CFB modes fails due to using a key
shorter than expected by default.
Encryption will also use a key shorter than expected.
Exchange of encrypted data from/to Jammy using BF OFB/CFB will therefore lead
to decryption issues.
[Test plan]
On Focal, run the following and copy the output to your clipboard
for cipher in bf-cbc bf-cfb bf-ecb bf-ofb; do echo "Test with ${cipher}"
| openssl enc -${cipher} -k test -pbkdf2 -out "pouet.${cipher}"; done
tar c pouet.bf-* | xz | base64 -w 60
You can also run this on Lunar or Mantic if you add "-provider legacy
-provider default" to the "openssl enc" invocation.
On Jammy, run the following and paste your clipboard
base64 -d | xz -d | tar x
for cipher in bf-cbc bf-cfb bf-ecb bf-ofb; do openssl enc -d -provider
legacy -provider default -${cipher} -k test -pbkdf2 -d -in "pouet.${cipher}";
done
Only "Test with bf-cbc" and "Test with bf-ecb" will be properly
decrypted: the other two will result in garbage on screen.
Here is the result of the enc + tar + xz + base64 on Focal (works with
Lunar/Mantic too but you need to added ):
/Td6WFoAAATm1rRGAgAhARYAAAB0L+Wj4Cf/ARBdADgbyxDlZ/1Xd7bAmZw7
8pbqQTu5j8StVybo1p1B2ydBc5VcodF6fu0hEp801tvirgSFNMSAHk5HMN/w
hCgU1BIr/nK51g3A3Lkdv7QNbaUw2ux1AmO/MpCLKLffCB9ElFZH4tuOS5AR
m9CJMzi6LQOw9wytGKm2IK3Ph7WpU6JQ/3HJilffQwHbFLnukiWGpLNO5v0O
D/4AJikrU9iemfChT0jXDbIRZ8a8VpVhJqu0u6eYOheVTqmSRiHHpIC/p1VA
ecFb0mACF/TQhjxcMUWGSGO/mtof+VaLiyg0KB87GKlChfwXTEvgbNuP9hmu
GL64VhX568Oy9EakSxlcXiIRk14kJKv0MdHQqY1R22wAACzqSr/nzpwqAAGs
AoBQAACjzq5WscRn+wIABFla
Here is the same but from Jammy if you want to test encryption on
Jammy and decryption on Lunar/Mantic:
/Td6WFoAAATm1rRGAgAhARYAAAB0L+Wj4Cf/ARFdADgbyxDlZ/1Xd7bAmZw7
8pbqQTu5j8StVybo1p1B2ydBc1zK4HR2g3CiLJet+R++nZy/gph6RscQ6hI3
HySjdDOFRfjIVttiNK3DvRsZb37r8SXkj/JCYWicZGjWPZxVE3OAZhEed5qe
jrFv871QAbm4jVGD4oIc4cOb5V/xDN7KWgwEzpWQy6+tcfPm3KLPQvULx56N
2qQf60hP//p5EXS3RpCitUsrGUoYzTynjOUIRy2yCmgZDh62RmchUshyWePa
k0nEYlDbl5/dSHXbWEWESqW+QDj136MZRwQRY+QC4MvLXg2Bo8H+Dl/xvNDF
/5J4layZdFlh76lWOtFRVoIbX6JtpAP34g4zx1422GSNAABRzyqPdCqX
1AABrQKAUAAABh3ynbHEZ/sCAARZWg==
The contents are expected to be different due to the use of
randomness. Don't try to compare the base64 outputs: I'm only using
them to ease testing across containers.
[Where problems could occur]
This patch makes openssl match the documented default (see "man openssl-enc"
and search for "Blowfish" for instance) and fixes decryption from an up-to-date
Jammy to pretty much everything else, but it also create an issue for data
encrypted on Jammy without this patch and Jammy with this patch.
There are two possible cases: encrypted data being streamed across
this boundary or data at rest being transferred or read later.
Streaming is probably not an issue in practice because it's rather the
current situation that has been an issue and it's easy to remedy by
updating everything (which is relatively few machines since that's
only Jammy and not any other OS or distribution).
Data at rest is more annoying since updating Jammy will make it
impossible to read the data again without updates to other pieces of
software. That sounds like a really bad thing and it kind of is but at
the same, the benefits are much larger than the issues. Indeed, there
is already an incompatibility at the moment between Jammy and
everything else and the more time passes by, the more such problematic
files can be created. Luckily very few people are using blowfish
nowadays and it's not even enabled by default anymore
[Touch-packages] [Bug 2033422] Re: openssl: backport to jammy "clear method store / query cache confusion"
I am not going to upload this, because I'm widely uncomfortable with bug 1990216 (details there). In addition, I have a few superficial suggestions for aesthetics: * Use lpX subdirectories in d/patches rather than add a prefix to the patchname * Add a Bug-Ubuntu field with a LP URL to each patch to make it even easier to go back to the relevant bug -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2033422 Title: openssl: backport to jammy "clear method store / query cache confusion" Status in openssl package in Ubuntu: New Status in openssl source package in Jammy: In Progress Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [ATTENTION] This SRU contains FOUR changes which are listed in the section below. [Meta] This bug is part of a series of four bugs for a single SRU. This ( #2033422 ) is the "central" bug with the global information and debdiff. This SRU addresses four issues with Jammy's openssl version: - http://pad.lv/1990216: Blowfish OFB/CFB decryption - http://pad.lv/1994165: ignored SMIME signature errors - http://pad.lv/2023545: imbca engine dumps core - http://pad.lv/2033422: very high CPU usage for concurrent TLS connections The SRU information has been added to the four bug reports and I am attaching the debdiff here only for all four. All the patches have been included in subsequent openssl 3.0.x releases which in turn have been included in subsequent Ubuntu releases. There has been no report of issues when updating to these Ubuntu releases. I have rebuilt the openssl versions and used abi-compliance-checker to compare the ABIs of the libraries in jammy and the one for the SRU. Both matched completely (FYI, mantic's matched completely too). The patch related to blowfish presents an annoying situation: jammy's openssl creates incompatible files and cannot read other files but fixing it will lead to files created on jammy so far to become unreadable. Fortunately, blowfish is long-deprecated and applications can be improved to handle this situation if the need arises in practice. This is stated in the SRU information in the bug and in d/changelog. The current situation in Jammy could be a security issue but due to the aforementioned deprecation, the low usage of blowfish and the fact that upstream didn't consider this worthy of a security notice, we (this includes the security team) chose not to pursue that path either. I have also pushed the code to git (without any attempt to make it git-ubuntu friendly). https://code.launchpad.net/~adrien-n/ubuntu/+source/openssl/+git/openssl/+ref/jammy- sru I asked Brian Murray about phasing speed and he concurs a slow roll-out is probably better for openssl. There is a small uncertainty because a security update could come before the phasing is over, effectively fast-forwarding the SRU. Still, unless there is already a current pre-advisory, this is probably better than a 10% phasing which is over after only a couple days anyway. NB: at the moment openssl doesn't phase slowly so this needs to be implemented. [Impact] Severely degraded performance for concurrent operations compared to openssl 1.1. The performance is so degraded that some workloads fail due to timeouts or insufficient resources (noone magically has 5 times more machines). As a consequence, a number of people use openssl 1.1 instead and do not get security updates. [Test plan] Rafael Lopez has shared a simple benchmarks in http://pad.lv/2009544 with https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2009544/+attachment/5690224/+files/main.py . Using this, I get the following numbers on my laptop: 3.0.2: real 2m5.567s user 4m3.948s sys 2m0.233s this SRU: real 0m23.966s user 2m35.687s sys 0m1.920s As can be easily seen, the speed-up is massive: system time is divided by 60 and overall wall clock time is roughly five times lower. In http://pad.lv/2009544 , Rafael also shared his performance numbers and they are relatable to these. He used slightly different versions (upstreams rather than patched with cherry-picks) but at least one of the version used does not include other performance change. He also used different hardware and this performance issue seems to depend on the number of CPUs available but also obtained a performance several times better. Results on a given machine vary also very little across runs (less than 2% variation on runs of size 10). They are also very similar on a Raspberry Pi 4 (8GB). The benchmark uses https://www.google.com/humans.txt which takes around 130ms to download on my machine but I modified the script to download something only 20ms away. Results are so close to the ones using humans.txt
[Touch-packages] [Bug 2038650] Re: crash reports not sent to the Error Tracker
Verified in a fresh Lunar VM. ** Tags removed: verification-needed verification-needed-lunar ** Tags added: verification-done verification-done-lunar -- 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/2038650 Title: crash reports not sent to the Error Tracker Status in apport package in Ubuntu: Fix Released Status in apport source package in Lunar: Fix Committed Status in apport source package in Mantic: Fix Released Bug description: [ Impact ] Crash reports aren't sent in when going through the UI, unless the user looks at the crash details. [ Test Plan ] 0) Make sure that error reporting is set to manual in the system settings (in Privacy screen) 1) Launch xeyes 2) pkill -11 xeyes 3) Click send in the apport dialog. DO NOT look at the details of the report. 4) ls -lh /var/crash/*xeyes* There should be 3 files: -rw-r- 1 bdmurray whoopsie 3370567 Oct 6 11:53 _usr_bin_xeyes.1000.crash -rw-rw-r-- 1 bdmurray bdmurray0 Oct 6 11:53 _usr_bin_xeyes.1000.upload -rw--- 1 whoopsie whoopsie 37 Oct 6 11:53 _usr_bin_xeyes.1000.uploaded [ Where problems could occur ] If the patch is wrong, we actually see similar bugs for other UI paths, e.g. ticking the "Remember this" box, etc. I tried to cover them during manual testing but I might have missed some. [ Other Info ] If possible I'd like for us not to wait too long for this to mature in -proposed, as this would affect crashes during the upgrade. [ Original report ] From what I can tell when I click the send button to send a crash report to the Error Tracker the crash doesn't actually get sent. My testing process follows: 1) Launch xeyes 2) pkill -11 xeyes 3) Click send in the apport dialog 4) ls -lh /var/crash I would expect there to be three files in /var/crash: -rw-r- 1 bdmurray whoopsie 3370567 Oct 6 11:53 _usr_bin_xeyes.1000.crash -rw-rw-r-- 1 bdmurray bdmurray0 Oct 6 11:53 _usr_bin_xeyes.1000.upload -rw--- 1 whoopsie whoopsie 37 Oct 6 11:53 _usr_bin_xeyes.1000.uploaded However, after step #4 I'm only seeing the .crash file and not a .upload or .uploaded. I was able to get the .upload and .uploaded files created if I chose to "View Report" and then click "Send". It's worth noting though that I did notice the size of the .crash file increase after clicking "Send" so some post-processing was done. ProblemType: BugDistroRelease: Ubuntu 23.10 Package: apport 2.27.0-0ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1000:123:20944237:2023-10-06 12:10:47.809248208 +0100:2023-10-06 12:11:23.340030509 +0100:/var/crash/_usr_bin_mpv.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 12:12:46 2023 InstallationDate: Installed on 2022-01-07 (637 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2038650/+subscriptions -- Mailing list: https://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 2038650] Re: crash reports not sent to the Error Tracker
We've agreed with Benjamin that the current fix is probably the way to go for the SRU, while we work on the overall design to make this less fragile (which would probably be way too much invasive for an SRU). ** Description changed: - From what I can tell when I click the send button to send a crash report - to the Error Tracker the crash doesn't actually get sent. My testing - process follows: + [ Impact ] + + Crash reports aren't sent in when going through the UI, unless the user + looks at the crash details. + + [ Test Plan ] + + 0) Make sure that error reporting is set to manual in the system settings (in Privacy screen) + 1) Launch xeyes + 2) pkill -11 xeyes + 3) Click send in the apport dialog. DO NOT look at the details of the report. + 4) ls -lh /var/crash/*xeyes* + + There should be 3 files: + + -rw-r- 1 bdmurray whoopsie 3370567 Oct 6 11:53 _usr_bin_xeyes.1000.crash + -rw-rw-r-- 1 bdmurray bdmurray0 Oct 6 11:53 _usr_bin_xeyes.1000.upload + -rw--- 1 whoopsie whoopsie 37 Oct 6 11:53 _usr_bin_xeyes.1000.uploaded + + [ Where problems could occur ] + + If the patch is wrong, we actually see similar bugs for other UI paths, + e.g. ticking the "Remember this" box, etc. I tried to cover them during + manual testing but I might have missed some. + + [ Other Info ] + + If possible I'd like for us not to wait too long for this to mature in -proposed, as this would affect crashes during the upgrade. + + [ Original report ] + From what I can tell when I click the send button to send a crash report to the Error Tracker the crash doesn't actually get sent. My testing process follows: 1) Launch xeyes 2) pkill -11 xeyes 3) Click send in the apport dialog 4) ls -lh /var/crash I would expect there to be three files in /var/crash: -rw-r- 1 bdmurray whoopsie 3370567 Oct 6 11:53 _usr_bin_xeyes.1000.crash -rw-rw-r-- 1 bdmurray bdmurray0 Oct 6 11:53 _usr_bin_xeyes.1000.upload -rw--- 1 whoopsie whoopsie 37 Oct 6 11:53 _usr_bin_xeyes.1000.uploaded However, after step #4 I'm only seeing the .crash file and not a .upload or .uploaded. I was able to get the .upload and .uploaded files created if I chose to "View Report" and then click "Send". It's worth noting though that I did notice the size of the .crash file increase after clicking "Send" so some post-processing was done. - ProblemType: Bug - DistroRelease: Ubuntu 23.10 + ProblemType: BugDistroRelease: Ubuntu 23.10 Package: apport 2.27.0-0ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1000:123:20944237:2023-10-06 12:10:47.809248208 +0100:2023-10-06 12:11:23.340030509 +0100:/var/crash/_usr_bin_mpv.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 12:12:46 2023 InstallationDate: Installed on 2022-01-07 (637 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) - PackageArchitecture: all - SourcePackage: apport + PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: apport (Ubuntu Lunar) Assignee: Benjamin Drung (bdrung) => Simon Chopin (schopin) -- 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/2038650 Title: crash reports not sent to the Error Tracker Status in apport package in Ubuntu: Fix Released Status in apport source package in Lunar: Confirmed Status in apport source package in Mantic: Fix Released Bug description: [ Impact ] Crash reports aren't sent in when going through the UI, unless the user looks at the crash details. [ Test Plan ] 0) Make sure that error reporting is set to manual in the system settings (in Privacy screen) 1) Launch xeyes 2) pkill -11 xeyes 3) Click send in the apport dialog. DO NOT look at the details of the report. 4) ls -lh /var/crash/*xeyes* There should be 3 files: -rw-r- 1 bdmurray whoopsie 3370567 Oct 6 11:53 _usr_bin_xeyes.1000.crash -rw-rw-r-- 1 bdmurray bdmurray0 Oct 6 11:53 _usr_bin_xeyes.1000.upload -rw--- 1 whoopsie whoopsie 37 Oct 6 11:53 _usr_bin_xeyes.1000.uploaded [ Where problems could occur ] If the patch is wrong, we actually see similar bugs for other UI paths, e.g. ticking the "Remember this" box, etc. I tried to cover them during manual testing but I might have missed some. [ Other Info ] If possible I'd like for us not to wait too long for this to mature in -proposed, as this would affect crashes during the upgrade. [ Original report ] From what I can tell when I click the send button to send a crash report to th
[Touch-packages] [Bug 2038650] Re: crash reports not sent to the Error Tracker
Looking at the code it seems to be affecting Lunar as well. I'm spinning up a VM to confirm it (LXD containers are being difficult for this) ** Changed in: apport (Ubuntu) Status: In Progress => Fix Committed ** Also affects: apport (Ubuntu Mantic) Importance: High Assignee: Simon Chopin (schopin) Status: Fix Committed ** Also affects: apport (Ubuntu Lunar) Importance: Undecided Status: New -- 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/2038650 Title: crash reports not sent to the Error Tracker Status in apport package in Ubuntu: Fix Committed Status in apport source package in Lunar: New Status in apport source package in Mantic: Fix Committed Bug description: From what I can tell when I click the send button to send a crash report to the Error Tracker the crash doesn't actually get sent. My testing process follows: 1) Launch xeyes 2) pkill -11 xeyes 3) Click send in the apport dialog 4) ls -lh /var/crash I would expect there to be three files in /var/crash: -rw-r- 1 bdmurray whoopsie 3370567 Oct 6 11:53 _usr_bin_xeyes.1000.crash -rw-rw-r-- 1 bdmurray bdmurray0 Oct 6 11:53 _usr_bin_xeyes.1000.upload -rw--- 1 whoopsie whoopsie 37 Oct 6 11:53 _usr_bin_xeyes.1000.uploaded However, after step #4 I'm only seeing the .crash file and not a .upload or .uploaded. I was able to get the .upload and .uploaded files created if I chose to "View Report" and then click "Send". It's worth noting though that I did notice the size of the .crash file increase after clicking "Send" so some post-processing was done. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: apport 2.27.0-0ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1000:123:20944237:2023-10-06 12:10:47.809248208 +0100:2023-10-06 12:11:23.340030509 +0100:/var/crash/_usr_bin_mpv.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 12:12:46 2023 InstallationDate: Installed on 2022-01-07 (637 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2038650/+subscriptions -- Mailing list: https://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 2038650] Re: crash reports not sent to the Error Tracker
This was caused by the addition of this feature: https://github.com/canonical/apport/pull/131 It broke an assumption that Dependencies was only added by the late stage info collection, and said collection also had some other side- effects that were relied upon to trigger the upload. I'll create a hotfix patch for it this afternoon to unlock the situation, and we'll work on a less fragile approach when Benjamin comes back from PTO. ** Changed in: apport (Ubuntu) Status: New => In Progress -- 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/2038650 Title: crash reports not sent to the Error Tracker Status in apport package in Ubuntu: In Progress Bug description: From what I can tell when I click the send button to send a crash report to the Error Tracker the crash doesn't actually get sent. My testing process follows: 1) Launch xeyes 2) pkill -11 xeyes 3) Click send in the apport dialog 4) ls -lh /var/crash I would expect there to be three files in /var/crash: -rw-r- 1 bdmurray whoopsie 3370567 Oct 6 11:53 _usr_bin_xeyes.1000.crash -rw-rw-r-- 1 bdmurray bdmurray0 Oct 6 11:53 _usr_bin_xeyes.1000.upload -rw--- 1 whoopsie whoopsie 37 Oct 6 11:53 _usr_bin_xeyes.1000.uploaded However, after step #4 I'm only seeing the .crash file and not a .upload or .uploaded. I was able to get the .upload and .uploaded files created if I chose to "View Report" and then click "Send". It's worth noting though that I did notice the size of the .crash file increase after clicking "Send" so some post-processing was done. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: apport 2.27.0-0ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1000:123:20944237:2023-10-06 12:10:47.809248208 +0100:2023-10-06 12:11:23.340030509 +0100:/var/crash/_usr_bin_mpv.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 12:12:46 2023 InstallationDate: Installed on 2022-01-07 (637 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2038650/+subscriptions -- Mailing list: https://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 2035337] Re: dh-python: Cannot exclude deliberately embedded .egg-info from the clean step
** Also affects: pastedeploy (Ubuntu) Importance: Undecided Status: New -- 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/2035337 Title: dh-python: Cannot exclude deliberately embedded .egg-info from the clean step Status in dh-python package in Ubuntu: New Status in pastedeploy package in Ubuntu: New Status in pastescript package in Ubuntu: Fix Released Status in dh-python package in Debian: New Bug description: Imported from Debian bug http://bugs.debian.org/1051837: Source: dh-python Version: 6.20230825 Severity: normal X-Debbugs-Cc: scho...@ubuntu.com We have a FTBFS on src:pastescript because its test suite embeds a FakePlugin Python package, including its .egg-info, and the recent change to the dh-python clean: target breaks that package. While we can work around it by temporarily renaming the problematic directory before the dh_clean call, it would be nicer to have an explicit mechanism to exclude some paths from the clean analysis. -- System Information: Debian Release: bookworm/sid APT prefers lunar-updates APT policy: (500, 'lunar-updates'), (500, 'lunar-security'), (500, 'lunar'), (100, 'lunar-proposed'), (100, 'lunar-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.2.0-32-generic (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/2035337/+subscriptions -- Mailing list: https://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 2035337] [NEW] dh-python: Cannot exclude deliberately embedded .egg-info from the clean step
Public bug reported: Imported from Debian bug http://bugs.debian.org/1051837: Source: dh-python Version: 6.20230825 Severity: normal X-Debbugs-Cc: scho...@ubuntu.com We have a FTBFS on src:pastescript because its test suite embeds a FakePlugin Python package, including its .egg-info, and the recent change to the dh-python clean: target breaks that package. While we can work around it by temporarily renaming the problematic directory before the dh_clean call, it would be nicer to have an explicit mechanism to exclude some paths from the clean analysis. -- System Information: Debian Release: bookworm/sid APT prefers lunar-updates APT policy: (500, 'lunar-updates'), (500, 'lunar-security'), (500, 'lunar'), (100, 'lunar-proposed'), (100, 'lunar-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.2.0-32-generic (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information ** Affects: dh-python (Ubuntu) Importance: Undecided Status: New ** Affects: pastescript (Ubuntu) Importance: Undecided Status: New ** Affects: dh-python (Debian) Importance: Undecided Status: New ** Tags: ftbfs ** Bug watch added: Debian Bug tracker #1051837 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051837 ** Changed in: dh-python (Debian) Remote watch: None => Debian Bug tracker #1051837 ** Tags added: ftbfs ** Also affects: pastescript (Ubuntu) Importance: Undecided Status: New -- 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/2035337 Title: dh-python: Cannot exclude deliberately embedded .egg-info from the clean step Status in dh-python package in Ubuntu: New Status in pastescript package in Ubuntu: New Status in dh-python package in Debian: New Bug description: Imported from Debian bug http://bugs.debian.org/1051837: Source: dh-python Version: 6.20230825 Severity: normal X-Debbugs-Cc: scho...@ubuntu.com We have a FTBFS on src:pastescript because its test suite embeds a FakePlugin Python package, including its .egg-info, and the recent change to the dh-python clean: target breaks that package. While we can work around it by temporarily renaming the problematic directory before the dh_clean call, it would be nicer to have an explicit mechanism to exclude some paths from the clean analysis. -- System Information: Debian Release: bookworm/sid APT prefers lunar-updates APT policy: (500, 'lunar-updates'), (500, 'lunar-security'), (500, 'lunar'), (100, 'lunar-proposed'), (100, 'lunar-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.2.0-32-generic (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/2035337/+subscriptions -- Mailing list: https://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 2024950] Re: add support for Green Linux, fork linux mint
Hi, I'm sorry, I'm not entirely sure I understood that correctly, but if you're looking for the apport sources, you can find them there: https://github.com/canonical/apport -- 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/2024950 Title: add support for Green Linux, fork linux mint Status in Apport: Triaged Status in apport package in Ubuntu: Incomplete Bug description: oscillation@oscillation-NEO-M114:~$ ubuntu-bug gnome-software *** Collecting information about the problem The collected information can be sent to developers to improve the application. This may take a few minutes. ... *** A problem in gnome-software Unable to report a problem: It looks like this is an unofficial Green package. Try again after updating the indexes of available packages. If this does not help, then remove the relevant third-party packages and try again. To continue, press any key... There are no pending crash messages. Try the --help key. kolab@kolab-NEO-M114:~$ nala show apart Package: import Version: 2.20.11-0ubuntu82.5 koljab@koljab-NEO-M114:~$ cat /etc/os-release NAME="Green Linux" VERSION="21.2 (Victoria)" ID=linuxmint ID_LIKE="ubuntu debian" PRETTY_NAME="Green Linux 21.2 Cinnamon 64-bit" VERSION_ID="21" HOME_URL="https://greenlinux.ru/; SUPPORT_URL="https://forum.linuxmint.su/; BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/ru/latest/; PRIVACY_POLICY_URL="https://greenlinux.ru/; VERSION_CODENAME=victoria UBUNTU_CODENAME=jammy koljab@koljab-NEO-M114:~$ --- ProblemType: Bug ApportLog: ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 640:1000:1000:88955:2023-06-20 14:14:04.299071363 +0300:2023-06-20 14:14:04.299071363 +0300:/var/crash/_usr_share_cinnamon_cinnamon-settings_xlet-settings.py.1000.crash 640:1000:1000:44330:2023-06-24 09:55:41.470598469 +0300:2023-06-24 09:55:41.470598469 +0300:/var/crash/_usr_bin_cinnamon-subprocess-wrapper.1000.crash CurrentDesktop: X-Cinnamon DistroRelease: Green Linux 21 InstallationDate: Installed on 2023-06-09 (15 days ago) InstallationMedia: Green Linux 21.1.1 "Victoria" (20230512) NonfreeKernelModules: nvidia_modeset nvidia Package: apport 2.20.11-0ubuntu82.5 [origin: Ubuntu] PackageArchitecture: all Tags: third-party-packages victoria Uname: Linux 6.3.9-x64v3-xanmod1 x86_64 UnreportableReason: Похоже, это неофициальный пакет Green. Повторите попытку после обновления индексов доступных пакетов. Если это не помогает, тогда удалите соответствующие сторонние пакеты и попробуйте ещё раз. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2024950/+subscriptions -- Mailing list: https://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 2025563] Re: System can not shutdown if system has multiple VROC RAID arrays
Hi, Thanks for the patch. I took care of the LP metadata for the bug (targetting the proper series), and unsubscribe ubuntu-sponsors since it's not ready for upload yet. Please resubscribe ubuntu-sponsors once you feel it's ready for upload. @enr0n can you chime in on this, do we have things pending for a Jammy SRU on systemd? ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Kinetic) Status: New => Fix Released ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released ** Changed in: systemd (Ubuntu Jammy) Importance: Undecided => Critical -- 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/2025563 Title: System can not shutdown if system has multiple VROC RAID arrays Status in OEM Priority Project: Invalid Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: New Status in systemd source package in Kinetic: Fix Released Bug description: [ Impact ] The system can not shutdown if the system has multiple VROC RAID arrays. Intel has fixed it in systemd v251 [1]. Need to cherry-pick the commit to ubuntu-jammy systemd 249.11-0ubuntu3.9. [1] The commit fixes the issue: commit 3a3b022d2cc112803ea7b9beea98bbcad110368a Author: Mariusz Tkaczyk Date: Tue Mar 29 12:49:54 2022 +0200 shutdown: get only active md arrays. Current md_list_get() implementation filters all block devices, started from "md*". This is ambiguous because list could contain: - partitions created upon md device (mdXpY) - external metadata container- specific type of md array. For partitions there is no issue, because they aren't handle STOP_ARRAY ioctl sent later. It generates misleading errors only. Second case is more problematic because containers are not locked in kernel. They are stopped even if container member array is active. For that reason reboot or shutdown flow could be blocked because metadata manager cannot be restarted after switch root on shutdown. Add filters to remove partitions and containers from md_list. Partitions can be excluded by DEVTYPE. Containers are determined by MD_LEVEL property, we are excluding all with "container" value. Signed-off-by: Mariusz Tkaczyk [ Test Plan ] 1. Build two VROC RAID. One RAID 0 for System volume, another RAID 10 for Data volume. 2. Install system on System volume. 3. Update systemd. 4. Reboot the system. 5. Verify if the system can reboot. [ Where problems could occur ] Low, upstream fix. [ Scope ] Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2025563/+subscriptions -- Mailing list: https://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 2024950] Re: add support for Green Linux, fork linux mint
I'll reiterate my point: the issue being discussed is a Green Linux issue, this should be discussed wherever that distribution does its development, and investigated by its developers. For the `apport` Ubuntu package this is completely out of scope. I'll also clarify our position as upstream Apport developers: our primary target is Ubuntu. While we are completely open to the idea of merging some code to make it easier for other distributions to use apport, it is expected for those distributions to do the actual integration themselves. -- 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/2024950 Title: add support for Green Linux, fork linux mint Status in Apport: Triaged Status in apport package in Ubuntu: Incomplete Bug description: oscillation@oscillation-NEO-M114:~$ ubuntu-bug gnome-software *** Collecting information about the problem The collected information can be sent to developers to improve the application. This may take a few minutes. ... *** A problem in gnome-software Unable to report a problem: It looks like this is an unofficial Green package. Try again after updating the indexes of available packages. If this does not help, then remove the relevant third-party packages and try again. To continue, press any key... There are no pending crash messages. Try the --help key. kolab@kolab-NEO-M114:~$ nala show apart Package: import Version: 2.20.11-0ubuntu82.5 koljab@koljab-NEO-M114:~$ cat /etc/os-release NAME="Green Linux" VERSION="21.2 (Victoria)" ID=linuxmint ID_LIKE="ubuntu debian" PRETTY_NAME="Green Linux 21.2 Cinnamon 64-bit" VERSION_ID="21" HOME_URL="https://greenlinux.ru/; SUPPORT_URL="https://forum.linuxmint.su/; BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/ru/latest/; PRIVACY_POLICY_URL="https://greenlinux.ru/; VERSION_CODENAME=victoria UBUNTU_CODENAME=jammy koljab@koljab-NEO-M114:~$ --- ProblemType: Bug ApportLog: ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 640:1000:1000:88955:2023-06-20 14:14:04.299071363 +0300:2023-06-20 14:14:04.299071363 +0300:/var/crash/_usr_share_cinnamon_cinnamon-settings_xlet-settings.py.1000.crash 640:1000:1000:44330:2023-06-24 09:55:41.470598469 +0300:2023-06-24 09:55:41.470598469 +0300:/var/crash/_usr_bin_cinnamon-subprocess-wrapper.1000.crash CurrentDesktop: X-Cinnamon DistroRelease: Green Linux 21 InstallationDate: Installed on 2023-06-09 (15 days ago) InstallationMedia: Green Linux 21.1.1 "Victoria" (20230512) NonfreeKernelModules: nvidia_modeset nvidia Package: apport 2.20.11-0ubuntu82.5 [origin: Ubuntu] PackageArchitecture: all Tags: third-party-packages victoria Uname: Linux 6.3.9-x64v3-xanmod1 x86_64 UnreportableReason: Похоже, это неофициальный пакет Green. Повторите попытку после обновления индексов доступных пакетов. Если это не помогает, тогда удалите соответствующие сторонние пакеты и попробуйте ещё раз. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2024950/+subscriptions -- Mailing list: https://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 2024950] Re: add support for Green Linux, fork linux mint
Hi, Thanks for taking the time to report the issue. I've tried to reproduce the issue in Ubuntu in a fresh Jammy VM, without success, and the provided logs don't really help us out. However, it appears you're not using Ubuntu, but rather a derivative. While we'd probably welcome patches in the upstream apport project to help integration, this is probably *not* a Ubuntu problem. You need to report the issue with your distribution, and have them investigate it. Thus, I'm marking the issue as Invalid in Ubuntu, and opening an issue in the upstream tracker instead. ** Also affects: apport Importance: Undecided Status: New ** Changed in: apport Status: New => Triaged ** Changed in: apport Importance: Undecided => Wishlist -- 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/2024950 Title: add support for Green Linux, fork linux mint Status in Apport: Triaged Status in apport package in Ubuntu: Incomplete Bug description: oscillation@oscillation-NEO-M114:~$ ubuntu-bug gnome-software *** Collecting information about the problem The collected information can be sent to developers to improve the application. This may take a few minutes. ... *** A problem in gnome-software Unable to report a problem: It looks like this is an unofficial Green package. Try again after updating the indexes of available packages. If this does not help, then remove the relevant third-party packages and try again. To continue, press any key... There are no pending crash messages. Try the --help key. kolab@kolab-NEO-M114:~$ nala show apart Package: import Version: 2.20.11-0ubuntu82.5 koljab@koljab-NEO-M114:~$ cat /etc/os-release NAME="Green Linux" VERSION="21.2 (Victoria)" ID=linuxmint ID_LIKE="ubuntu debian" PRETTY_NAME="Green Linux 21.2 Cinnamon 64-bit" VERSION_ID="21" HOME_URL="https://greenlinux.ru/; SUPPORT_URL="https://forum.linuxmint.su/; BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/ru/latest/; PRIVACY_POLICY_URL="https://greenlinux.ru/; VERSION_CODENAME=victoria UBUNTU_CODENAME=jammy koljab@koljab-NEO-M114:~$ --- ProblemType: Bug ApportLog: ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 640:1000:1000:88955:2023-06-20 14:14:04.299071363 +0300:2023-06-20 14:14:04.299071363 +0300:/var/crash/_usr_share_cinnamon_cinnamon-settings_xlet-settings.py.1000.crash 640:1000:1000:44330:2023-06-24 09:55:41.470598469 +0300:2023-06-24 09:55:41.470598469 +0300:/var/crash/_usr_bin_cinnamon-subprocess-wrapper.1000.crash CurrentDesktop: X-Cinnamon DistroRelease: Green Linux 21 InstallationDate: Installed on 2023-06-09 (15 days ago) InstallationMedia: Green Linux 21.1.1 "Victoria" (20230512) NonfreeKernelModules: nvidia_modeset nvidia Package: apport 2.20.11-0ubuntu82.5 [origin: Ubuntu] PackageArchitecture: all Tags: third-party-packages victoria Uname: Linux 6.3.9-x64v3-xanmod1 x86_64 UnreportableReason: Похоже, это неофициальный пакет Green. Повторите попытку после обновления индексов доступных пакетов. Если это не помогает, тогда удалите соответствующие сторонние пакеты и попробуйте ещё раз. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2024950/+subscriptions -- Mailing list: https://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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts
This has been re-broken in the glibc package when upstream changed the name of the actual ld.so binary, thus escaping the stripping exception. I've fixed this in the git tree in preparation of the mantic upload. There's currently a Jammy SRU in -proposed, I won't supersede it for this fix since there's a workaround (installing the -dbg package). However, I'll make sure to include it in the next upload :). ** Also affects: gdb (Ubuntu Mantic) Importance: High Status: Fix Released ** Also affects: glibc (Ubuntu Mantic) Importance: Undecided Status: Fix Released ** Also affects: gdb (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: glibc (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: gdb (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: glibc (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: gdb (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: glibc (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: glibc (Ubuntu Mantic) Importance: Undecided => High ** Changed in: glibc (Ubuntu Mantic) Status: Fix Released => In Progress ** Changed in: glibc (Ubuntu Lunar) Status: New => Won't Fix ** Changed in: glibc (Ubuntu Kinetic) Status: New => Won't Fix ** Changed in: glibc (Ubuntu Jammy) Importance: Undecided => High ** Changed in: glibc (Ubuntu Jammy) Status: New => Triaged ** Changed in: gdb (Ubuntu Jammy) Status: New => Fix Released ** Changed in: gdb (Ubuntu Kinetic) Status: New => Fix Released ** Changed in: gdb (Ubuntu Lunar) Status: New => Fix Released ** Changed in: glibc (Ubuntu Jammy) Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1927192 Title: gdb ftbfs on armhf, testsuite timeouts Status in gdb: Fix Released Status in gdb package in Ubuntu: Fix Released Status in glibc package in Ubuntu: In Progress Status in gdb source package in Focal: Fix Released Status in glibc source package in Focal: Fix Released Status in gdb source package in Groovy: Won't Fix Status in glibc source package in Groovy: Won't Fix Status in gdb source package in Hirsute: Won't Fix Status in glibc source package in Hirsute: Won't Fix Status in gdb source package in Impish: Fix Released Status in glibc source package in Impish: Fix Released Status in gdb source package in Jammy: Fix Released Status in glibc source package in Jammy: Triaged Status in gdb source package in Kinetic: Fix Released Status in glibc source package in Kinetic: Won't Fix Status in gdb source package in Lunar: Fix Released Status in glibc source package in Lunar: Won't Fix Status in gdb source package in Mantic: Fix Released Status in glibc source package in Mantic: In Progress Bug description: [Impact] * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is not installed. [Test Plan] * Check that ld.so is not stripped on armhf: $ /lib/*/ld-2.31.so libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not stripped * Check that ld.so is stripped on amd64: $ file /lib/x86_64-linux-gnu/ld-2.31.so /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped [Where problems could occur] * The fix is not stripping ld.so on armhf. Not stripping it comes with a notable increase in file size and it may be performance critical 109K stripped vs 1.3M unstripped. Accidentally ld.so could be left unstripped on other architectures, but the test plan covers checking that, at least on amd64. Other than those not stripping ld.so should not cause any issue. [Original Bug Text] see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1927192/+subscriptions -- Mailing list: https://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 1983359] Re: [SRU] hwrng drivers missing in initrd.img
Hi, Thanks for adressing Steve's comments, I uploaded the Jammy debdiff, it's now in the SRU queue. I also unsubscribe ubuntu-sponsors, so if by any chance there's a need to revisit this upload do remember to subscribe it again :) -- 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/1983359 Title: [SRU] hwrng drivers missing in initrd.img Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Jammy: In Progress Status in initramfs-tools source package in Kinetic: Fix Released Bug description: [Impact] The initialization of the entropy buffer of the urandom device is critical for security. When booting Jammy 22.04.1 on QEMU riscv64 I see the following warnings: [ 14.654546] random: lvm: uninitialized urandom read (4 bytes read) [ 15.247995] random: lvm: uninitialized urandom read (2 bytes read) [ 22.484719] random: lvm: uninitialized urandom read (4 bytes read) [ 43.161846] random: lvmconfig: uninitialized urandom read (4 bytes read) [ 48.862281] random: lvm: uninitialized urandom read (4 bytes read) Module virtio-rng.ko is missing in initrd.img. Adding virtio_rng to /etc/initramfs-tools/modules avoids the warnings. Hardware RNG drivers should generally be included in the initrd to provide early entropy. [Test case] To reproduce the issue: Install the prerequisites: sudo apt-get update sudo apt-get install opensbi qemu-system-misc u-boot-qemu Download https://old- releases.ubuntu.com/releases/22.04.1/ubuntu-22.04.1-preinstalled- server-riscv64+unmatched.img.xz. Decompress it with xz -d ubuntu-22.04.1-preinstalled-server-riscv64+unmatched.img.xz Run it in QEMU with qemu-system-riscv64 \ -machine virt -nographic -m 2048 -smp 4 \ -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin \ -kernel /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf \ -device virtio-net-device,netdev=eth0 -netdev user,id=eth0 \ -device virtio-rng-pci \ -drive file=ubuntu-22.04.1-preinstalled-server-riscv64+unmatched.img,format=raw,if=virtio You can log into the system with user ubuntu, password ubuntu after seeing the message "Cloud-init v. 22.2-0ubuntu1~22.04.3 finished" Run 'sudo dmesg | grep 'uninitialized urandom' To test the fix: Update the initramfs-tools package. Run 'update-initramfs -k $(uname -r) -u' with MODULES=most (defined in /etc/initramfs-tools/initramfs.conf or in /etc/initramfs- tools/conf.d/*.conf) Unpack the initrd with 'unmkinitramfs /boot/initrd.img-$(uname -r)' Check that [main/]lib/modules/$(uname -r)/kernel/drivers/char/hw_random/ exists and contains kernel modules. When running on QEMU the relevant module is virtio-rng.ko. Reboot and check the kernel log by running 'sudo dmesg | grep 'uninitialized urandom'. [Where problems could occur] Adding more drivers increases the size of the initrd. The larger initrd might not fit onto the boot partition. The total size of hw_random drivers on amd64 is less than 150 KiB so this seem improbable. [Other Info] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1983359/+subscriptions -- Mailing list: https://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 1983359] Re: [SRU] hwrng drivers missing in initrd.img
** Changed in: initramfs-tools (Ubuntu Jammy) Status: Confirmed => In Progress -- 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/1983359 Title: [SRU] hwrng drivers missing in initrd.img Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Jammy: In Progress Status in initramfs-tools source package in Kinetic: Fix Released Bug description: [Impact] The initialization of the entropy buffer of the urandom device is critical for security. When booting Jammy 22.04.1 on QEMU riscv64 I see the following warnings: [ 14.654546] random: lvm: uninitialized urandom read (4 bytes read) [ 15.247995] random: lvm: uninitialized urandom read (2 bytes read) [ 22.484719] random: lvm: uninitialized urandom read (4 bytes read) [ 43.161846] random: lvmconfig: uninitialized urandom read (4 bytes read) [ 48.862281] random: lvm: uninitialized urandom read (4 bytes read) Module virtio-rng.ko is missing in initrd.img. Adding virtio_rng to /etc/initramfs-tools/modules avoids the warnings. Hardware RNG drivers should generally be included in the initrd to provide early entropy. [Test case] To reproduce the issue: Install the prerequisites: sudo apt-get update sudo apt-get install opensbi qemu-system-misc u-boot-qemu Download https://old- releases.ubuntu.com/releases/22.04.1/ubuntu-22.04.1-preinstalled- server-riscv64+unmatched.img.xz. Decompress it with xz -d ubuntu-22.04.1-preinstalled-server-riscv64+unmatched.img.xz Run it in QEMU with qemu-system-riscv64 \ -machine virt -nographic -m 2048 -smp 4 \ -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin \ -kernel /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf \ -device virtio-net-device,netdev=eth0 -netdev user,id=eth0 \ -device virtio-rng-pci \ -drive file=ubuntu-22.04.1-preinstalled-server-riscv64+unmatched.img,format=raw,if=virtio You can log into the system with user ubuntu, password ubuntu after seeing the message "Cloud-init v. 22.2-0ubuntu1~22.04.3 finished" Run 'sudo dmesg | grep 'uninitialized urandom' To test the fix: Update the initramfs-tools package. Run 'update-initramfs -k $(uname -r) -u' with MODULES=most (defined in /etc/initramfs-tools/initramfs.conf or in /etc/initramfs- tools/conf.d/*.conf) Unpack the initrd with 'unmkinitramfs /boot/initrd.img-$(uname -r)' Check that [main/]lib/modules/$(uname -r)/kernel/drivers/char/hw_random/ exists and contains kernel modules. When running on QEMU the relevant module is virtio-rng.ko. Reboot and check the kernel log by running 'sudo dmesg | grep 'uninitialized urandom'. [Where problems could occur] Adding more drivers increases the size of the initrd. The larger initrd might not fit onto the boot partition. The total size of hw_random drivers on amd64 is less than 150 KiB so this seem improbable. [Other Info] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1983359/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 2023165] Re: carbon-cache not starting because python3-openssl throws error _lib.OpenSSL_add_all_algorithms()
Quoting Thomas Hoffmann (2023-06-07 16:39:03) > The repo file /usr/lib/python3/dist-packages/OpenSSL/crypto.py has the same > reference to OpenSSL_add_all_algorithms but it doesn't seem to cause a > problem. That's because it uses the distro python3-cryptography, which provides the problematic function. > @Simon: I also removed "cryptography" via pip because it was installed from > the Repo and by pip. > Not sure which program caused it, but everything is fine now. > > Thank you very much for your quick help! > Much appreciated! You're welcome :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2023165 Title: carbon-cache not starting because python3-openssl throws error _lib.OpenSSL_add_all_algorithms() Status in openssl package in Ubuntu: Invalid Bug description: 1) ubuntu release: We are using Ubuntu 22.04 LTS: Description:Ubuntu 22.04.2 LTS Release:22.04 2) packages: We have the following packages installed: graphite-carbon/jammy,jammy,now 1.1.7-1 all python3-openssl/jammy,jammy,now 21.0.0-1 all OpenSSL: OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022) 3) Expected result The carbon cache should start if all dependent packages are from the same repository. 4) observed issue Since the last OpenSSL update this week via the ubuntu repository, the carbon-cache service is not starting any more. The error message is: Jun 7 09:22:59 icinga2 systemd[1]: Starting Graphite Carbon Cache... Jun 7 09:23:00 icinga2 carbon-cache[191566]: Traceback (most recent call last): Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/bin/carbon-cache", line 28, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from carbon.util import run_twistd_plugin # noqa Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/lib/python3/dist-packages/carbon/util.py", line 19, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import SSL Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/local/lib/python3.10/dist-packages/OpenSSL/__init__.py", line 8, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import crypto, SSL Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/local/lib/python3.10/dist-packages/OpenSSL/crypto.py", line 3268, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: _lib.OpenSSL_add_all_algorithms() Jun 7 09:23:00 icinga2 carbon-cache[191566]: AttributeError: module 'lib' has no attribute 'OpenSSL_add_all_algorithms' According to https://levelup.gitconnected.com/fix-attributeerror-module-lib-has-no-attribute-openssl-521a35d83769 the python module pyopenssl needs to be > 22.1.0 Ubuntu 22.04 LTS ships with version 22.0.0. It seems, that the python3-openssl is not working well with the most recent openSSL version of Ubuntu 22.04. I could update pyopenssl with pip but this might break the update mechanism of apt. Any suggestions are appreciated, thanks! If I can provide further information, just let me know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2023165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 2023165] Re: carbon-cache not starting because python3-openssl throws error _lib.OpenSSL_add_all_algorithms()
Hi, In addition to what Adrien asks, could you show us the version of python3-cryptography you're using? The bindings used by pyOpenSSL are actually provided by the cryptography package. Also, could you make sure you don't have a local version of said code in /usr/local, similar to your PyOpenSSL install? Thanks in advance :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2023165 Title: carbon-cache not starting because python3-openssl throws error _lib.OpenSSL_add_all_algorithms() Status in openssl package in Ubuntu: New Bug description: 1) ubuntu release: We are using Ubuntu 22.04 LTS: Description:Ubuntu 22.04.2 LTS Release:22.04 2) packages: We have the following packages installed: graphite-carbon/jammy,jammy,now 1.1.7-1 all python3-openssl/jammy,jammy,now 21.0.0-1 all OpenSSL: OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022) 3) Expected result The carbon cache should start if all dependent packages are from the same repository. 4) observed issue Since the last OpenSSL update this week via the ubuntu repository, the carbon-cache service is not starting any more. The error message is: Jun 7 09:22:59 icinga2 systemd[1]: Starting Graphite Carbon Cache... Jun 7 09:23:00 icinga2 carbon-cache[191566]: Traceback (most recent call last): Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/bin/carbon-cache", line 28, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from carbon.util import run_twistd_plugin # noqa Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/lib/python3/dist-packages/carbon/util.py", line 19, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import SSL Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/local/lib/python3.10/dist-packages/OpenSSL/__init__.py", line 8, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import crypto, SSL Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/local/lib/python3.10/dist-packages/OpenSSL/crypto.py", line 3268, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: _lib.OpenSSL_add_all_algorithms() Jun 7 09:23:00 icinga2 carbon-cache[191566]: AttributeError: module 'lib' has no attribute 'OpenSSL_add_all_algorithms' According to https://levelup.gitconnected.com/fix-attributeerror-module-lib-has-no-attribute-openssl-521a35d83769 the python module pyopenssl needs to be > 22.1.0 Ubuntu 22.04 LTS ships with version 22.0.0. It seems, that the python3-openssl is not working well with the most recent openSSL version of Ubuntu 22.04. I could update pyopenssl with pip but this might break the update mechanism of apt. Any suggestions are appreciated, thanks! If I can provide further information, just let me know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2023165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 2016021] Re: icu FTBFS on lunar
Quoting Steven R. Loomis (2023-04-12 17:30:25)
> What ICU is this? I can't tell which version from here. Your analysis
That'd be 72.1-3ubuntu1, now ubuntu2 with this patch. This bug was
mostly for reference for the folks in the Ubuntu release team since
we're in feature freeze, almost at final freeze. I uploaded the fix
directly afterward. That's my bad, I should have been more explicit
about that :)
> sounds reasonable, may have to ignore the tests (there's a logKnownIssue
> mechanism) - put the following before the failing test case:
>
> if
> (logKnownIssue("https://bugs.launchpad.net/ubuntu/+source/icu/+bug/2016021;,
> "tzdata issue")) {
> return;
> }
Given that icu is a regular in our FTBFS reports due to tzdata updates,
we might indeed end up doing so, but in general I'd rather adapt the
tests to the specificities of the distro than disable them altogether.
Thanks for the tip though, much appreciated!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to icu in Ubuntu.
https://bugs.launchpad.net/bugs/2016021
Title:
icu FTBFS on lunar
Status in icu package in Ubuntu:
Confirmed
Bug description:
During the last test rebuild, it was noticed that icu failed to build
from source, with the following failures in the test suite:
-
| *** FAILING TEST SUMMARY FOR: intltest
TestAliasedNames
TestCanonicalID
TimeZoneTest
format
| *** END FAILING TEST SUMMARY FOR: intltest
The issue is related to the recent tzdata updates: not only the usual
batch of changes made to reflect the current state of the world, but
also changes made to have a better data set for pre-1970 dates.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/icu/+bug/2016021/+subscriptions
--
Mailing list: https://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 2016021] [NEW] icu FTBFS on lunar
Public bug reported: During the last test rebuild, it was noticed that icu failed to build from source, with the following failures in the test suite: - | *** FAILING TEST SUMMARY FOR: intltest TestAliasedNames TestCanonicalID TimeZoneTest format | *** END FAILING TEST SUMMARY FOR: intltest The issue is related to the recent tzdata updates: not only the usual batch of changes made to reflect the current state of the world, but also changes made to have a better data set for pre-1970 dates. ** Affects: icu (Ubuntu) Importance: High Status: Confirmed ** Tags: ftbfs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/2016021 Title: icu FTBFS on lunar Status in icu package in Ubuntu: Confirmed Bug description: During the last test rebuild, it was noticed that icu failed to build from source, with the following failures in the test suite: - | *** FAILING TEST SUMMARY FOR: intltest TestAliasedNames TestCanonicalID TimeZoneTest format | *** END FAILING TEST SUMMARY FOR: intltest The issue is related to the recent tzdata updates: not only the usual batch of changes made to reflect the current state of the world, but also changes made to have a better data set for pre-1970 dates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/2016021/+subscriptions -- Mailing list: https://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 2013211] [NEW] Forward-port security fixes to Lunar
Public bug reported: There's been a bunch of security patches to the Kinetic version of vim, those need to be applied to Lunar as well: * CVE-2033-0433 * CVE-2023-1170 * CVE-2023-1175 * CVE-2023-1264 In addition, the following only affect the version in Lunar: * CVE-2023-0512 * CVE-2023-1127 ** Affects: vim (Ubuntu) Importance: Critical Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/2013211 Title: Forward-port security fixes to Lunar Status in vim package in Ubuntu: In Progress Bug description: There's been a bunch of security patches to the Kinetic version of vim, those need to be applied to Lunar as well: * CVE-2033-0433 * CVE-2023-1170 * CVE-2023-1175 * CVE-2023-1264 In addition, the following only affect the version in Lunar: * CVE-2023-0512 * CVE-2023-1127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2013211/+subscriptions -- Mailing list: https://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 2006954] Re: openssl: merge unstable's 3.0.8-1
Uploaded, thanks! ** Changed in: openssl (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2006954 Title: openssl: merge unstable's 3.0.8-1 Status in openssl package in Ubuntu: Fix Committed Bug description: Openssl 3.0.8 has been released. Unstable now contains 3.0.8-1 which we can merge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2006954/+subscriptions -- Mailing list: https://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 2004264] Re: FTBFS against glibc 2.37
The issue has been fixed upstream just before the final 2.37 release, thus closing this. ** Changed in: libunistring (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/2004264 Title: FTBFS against glibc 2.37 Status in GLibC: Unknown Status in libunistring package in Ubuntu: Fix Released Bug description: Hi, During a mass rebuild of Lunar, the package libunistring failed to build against a snapshot of the upcoming glibc 2.37, while building fine using 2.36 as present in the archive. https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20221215-lunar-glibc-2.37-lunar.html https://launchpadlibrarian.net/644139079/buildlog_ubuntu-lunar-amd64.libunistring_1.0-2_BUILDING.txt.gz I was able to reproduce this when building against my latest snapshot (done this morning), published in this PPA: https://launchpad.net/~schopin/+archive/ubuntu/glibc-2.37-snapshot/+packages The failing tests appear to be test-strncat and test-u8-strncat. To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/2004264/+subscriptions -- Mailing list: https://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 2004264] Re: FTBFS against glibc 2.37
The failure is in a gnulib test. I've bisected it to the following glibc upstream commit: https://sourceware.org/git/?p=glibc.git;a=commit;h=642933158e7cf072d873231b1a9bb03291f2b989 The issue has been reported upstream. ** Bug watch added: Sourceware.org Bugzilla #30065 https://sourceware.org/bugzilla/show_bug.cgi?id=30065 ** Also affects: libunistring via https://sourceware.org/bugzilla/show_bug.cgi?id=30065 Importance: Unknown Status: Unknown ** Project changed: libunistring => glibc -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/2004264 Title: FTBFS against glibc 2.37 Status in GLibC: Unknown Status in libunistring package in Ubuntu: New Bug description: Hi, During a mass rebuild of Lunar, the package libunistring failed to build against a snapshot of the upcoming glibc 2.37, while building fine using 2.36 as present in the archive. https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20221215-lunar-glibc-2.37-lunar.html https://launchpadlibrarian.net/644139079/buildlog_ubuntu-lunar-amd64.libunistring_1.0-2_BUILDING.txt.gz I was able to reproduce this when building against my latest snapshot (done this morning), published in this PPA: https://launchpad.net/~schopin/+archive/ubuntu/glibc-2.37-snapshot/+packages The failing tests appear to be test-strncat and test-u8-strncat. To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/2004264/+subscriptions -- Mailing list: https://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 2004264] [NEW] FTBFS against glibc 2.37
Public bug reported: Hi, During a mass rebuild of Lunar, the package libunistring failed to build against a snapshot of the upcoming glibc 2.37, while building fine using 2.36 as present in the archive. https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20221215-lunar-glibc-2.37-lunar.html https://launchpadlibrarian.net/644139079/buildlog_ubuntu-lunar-amd64.libunistring_1.0-2_BUILDING.txt.gz I was able to reproduce this when building against my latest snapshot (done this morning), published in this PPA: https://launchpad.net/~schopin/+archive/ubuntu/glibc-2.37-snapshot/+packages The failing tests appear to be test-strncat and test-u8-strncat. ** Affects: libunistring (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/2004264 Title: FTBFS against glibc 2.37 Status in libunistring package in Ubuntu: New Bug description: Hi, During a mass rebuild of Lunar, the package libunistring failed to build against a snapshot of the upcoming glibc 2.37, while building fine using 2.36 as present in the archive. https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20221215-lunar-glibc-2.37-lunar.html https://launchpadlibrarian.net/644139079/buildlog_ubuntu-lunar-amd64.libunistring_1.0-2_BUILDING.txt.gz I was able to reproduce this when building against my latest snapshot (done this morning), published in this PPA: https://launchpad.net/~schopin/+archive/ubuntu/glibc-2.37-snapshot/+packages The failing tests appear to be test-strncat and test-u8-strncat. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunistring/+bug/2004264/+subscriptions -- Mailing list: https://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 2003548] Re: Merge Debian unstable's p11-kit 0.24.1-2
Uploaded, thanks :) ** Changed in: p11-kit (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to p11-kit in Ubuntu. https://bugs.launchpad.net/bugs/2003548 Title: Merge Debian unstable's p11-kit 0.24.1-2 Status in p11-kit package in Ubuntu: Fix Committed Bug description: This is a merge of Debian unstable's 0.24.1-2 as 0.24.1-2ubuntu1. A PPA is available at https://launchpad.net/~adrien-n/+archive/ubuntu/p11-kit-merge-0.24.1-2 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/2003548/+subscriptions -- Mailing list: https://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 2002819] [NEW] dh-python: Deps guarded by (python3 << 3.X) break python-3.(X-1) use
Public bug reported: Imported from Debian bug http://bugs.debian.org/1028603: Package: dh-python Version: 5.20221001 Severity: normal X-Debbugs-Cc: scho...@ubuntu.com For instance, pylint has "tomli>=1.1.0;python_version<'3.11'" in its pyproject.toml, which is translated as "python3-tomli (>= 1.1.0) | python3 (>= 3.11)". This means that if we have python == 3.11 but still have python3.10 in the archive, any code that iterates over all supported archive risks failing simply due to the tomli module missing. This is currently happening in the distro-info autopkgtests for the python3-defaults migration from unstable to testing (and also in Ubuntu). I'll probably be adding tomli as a test dependency in Ubuntu as a stopgap, but I figured someone might think of a better long-term solution to the issue. -- System Information: Debian Release: bookworm/sid APT prefers kinetic-updates APT policy: (500, 'kinetic-updates'), (500, 'kinetic-security'), (500, 'kinetic'), (400, 'kinetic-proposed'), (100, 'kinetic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.19.0-29-generic (SMP w/24 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dh-python depends on: ii python33.10.6-1 ii python3-distutils 3.10.7-1 dh-python recommends no packages. Versions of packages dh-python suggests: ii dpkg-dev 1.21.9ubuntu1 pn flit ii libdpkg-perl 1.21.9ubuntu1 pn python3-build pn python3-installer ii python3-tomli 2.0.1-1 -- no debconf information ** Affects: dh-python (Ubuntu) Importance: Undecided Status: New ** Affects: dh-python (Debian) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #1028603 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028603 ** Changed in: dh-python (Debian) Remote watch: None => Debian Bug tracker #1028603 -- 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/2002819 Title: dh-python: Deps guarded by (python3 << 3.X) break python-3.(X-1) use Status in dh-python package in Ubuntu: New Status in dh-python package in Debian: New Bug description: Imported from Debian bug http://bugs.debian.org/1028603: Package: dh-python Version: 5.20221001 Severity: normal X-Debbugs-Cc: scho...@ubuntu.com For instance, pylint has "tomli>=1.1.0;python_version<'3.11'" in its pyproject.toml, which is translated as "python3-tomli (>= 1.1.0) | python3 (>= 3.11)". This means that if we have python == 3.11 but still have python3.10 in the archive, any code that iterates over all supported archive risks failing simply due to the tomli module missing. This is currently happening in the distro-info autopkgtests for the python3-defaults migration from unstable to testing (and also in Ubuntu). I'll probably be adding tomli as a test dependency in Ubuntu as a stopgap, but I figured someone might think of a better long-term solution to the issue. -- System Information: Debian Release: bookworm/sid APT prefers kinetic-updates APT policy: (500, 'kinetic-updates'), (500, 'kinetic-security'), (500, 'kinetic'), (400, 'kinetic-proposed'), (100, 'kinetic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.19.0-29-generic (SMP w/24 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dh-python depends on: ii python33.10.6-1 ii python3-distutils 3.10.7-1 dh-python recommends no packages. Versions of packages dh-python suggests: ii dpkg-dev 1.21.9ubuntu1 pn flit ii libdpkg-perl 1.21.9ubuntu1 pn python3-build pn python3-installer ii python3-tomli 2.0.1-1 -- no debconf information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/2002819/+subscriptions -- Mailing list: https://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 2002660] [NEW] networkx incompatible with numpy 1.24
Public bug reported:
The nipype autopkgtests have started failing with the following stack
trace:
ERROR collecting pipeline/plugins/tests/test_tools.py _
/usr/lib/python3.10/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
:1050: in _gcd_import
???
:1027: in _find_and_load
???
:992: in _find_and_load_unlocked
???
:241: in _call_with_frames_removed
???
:1050: in _gcd_import
???
:1027: in _find_and_load
???
:992: in _find_and_load_unlocked
???
:241: in _call_with_frames_removed
???
:1050: in _gcd_import
???
:1027: in _find_and_load
???
:1006: in _find_and_load_unlocked
???
:688: in _load_unlocked
???
:883: in exec_module
???
:241: in _call_with_frames_removed
???
nipype/pipeline/plugins/__init__.py:5: in
from .debug import DebugPlugin
nipype/pipeline/plugins/debug.py:7: in
import networkx as nx
/usr/lib/python3/dist-packages/networkx/__init__.py:115: in
import networkx.readwrite
/usr/lib/python3/dist-packages/networkx/readwrite/__init__.py:15: in
from networkx.readwrite.graphml import *
/usr/lib/python3/dist-packages/networkx/readwrite/graphml.py:314: in
class GraphML(object):
/usr/lib/python3/dist-packages/networkx/readwrite/graphml.py:346: in GraphML
(np.int, "int"), (np.int8, "int"),
/usr/lib/python3/dist-packages/numpy/__init__.py:284: in __getattr__
raise AttributeError("module {!r} has no attribute "
E AttributeError: module 'numpy' has no attribute 'int'
The problematic code is in the networkx package, and seems to have been
fixed in
https://github.com/networkx/networkx/commit/207147ee179554a33f10f25032054d3e01f96188
(which is in 2.5 onwards).
Debian currently ships with 2.8.8, we might want to merge?
This is currently blocking the python3-defaults transition.
** Affects: networkx (Ubuntu)
Importance: Undecided
Status: New
** Affects: nipype (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: python3-defaults (Ubuntu)
Importance: Undecided
Status: New
** Tags: update-excuse
** Tags added: update-excuse
** Also affects: nipype (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nipype (Ubuntu)
Status: New => Invalid
** Also affects: python3-defaults (Ubuntu)
Importance: Undecided
Status: New
--
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/2002660
Title:
networkx incompatible with numpy 1.24
Status in networkx package in Ubuntu:
New
Status in nipype package in Ubuntu:
Invalid
Status in python3-defaults package in Ubuntu:
New
Bug description:
The nipype autopkgtests have started failing with the following stack
trace:
ERROR collecting pipeline/plugins/tests/test_tools.py
_
/usr/lib/python3.10/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
:1050: in _gcd_import
???
:1027: in _find_and_load
???
:992: in _find_and_load_unlocked
???
:241: in _call_with_frames_removed
???
:1050: in _gcd_import
???
:1027: in _find_and_load
???
:992: in _find_and_load_unlocked
???
:241: in _call_with_frames_removed
???
:1050: in _gcd_import
???
:1027: in _find_and_load
???
:1006: in _find_and_load_unlocked
???
:688: in _load_unlocked
???
:883: in exec_module
???
:241: in _call_with_frames_removed
???
nipype/pipeline/plugins/__init__.py:5: in
from .debug import DebugPlugin
nipype/pipeline/plugins/debug.py:7: in
import networkx as nx
/usr/lib/python3/dist-packages/networkx/__init__.py:115: in
import networkx.readwrite
/usr/lib/python3/dist-packages/networkx/readwrite/__init__.py:15: in
from networkx.readwrite.graphml import *
/usr/lib/python3/dist-packages/networkx/readwrite/graphml.py:314: in
class GraphML(object):
/usr/lib/python3/dist-packages/networkx/readwrite/graphml.py:346: in GraphML
(np.int, "int"), (np.int8, "int"),
/usr/lib/python3/dist-packages/numpy/__init__.py:284: in __getattr__
raise AttributeError("module {!r} has no attribute "
E AttributeError: module 'numpy' has no attribute 'int'
The problematic code is in the networkx package, and seems to have
been fixed in
https://github.com/networkx/networkx/commit/207147ee179554a33f10f25032054d3e01f96188
(which is in 2.5 onwards).
Debian currently ships with 2.8.8, we might want to merge?
This is currently blocking the python3-defaults transition.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/networkx/+bug/2002660/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 2002355] Re: package libssl-dev 3.0.2-0ubuntu1.7 [modified: usr/include/openssl/aes.h usr/include/openssl/asn1.h usr/include/openssl/asn1_mac.h usr/include/openssl/asn1t.h usr/in
Hi! Seeing this line: Unpacking libssl-dev:i386 (3.0.2-0ubuntu1.7) over (1.0.1f-1ubuntu2.27) makes me think you either are trying to upgrade directly from Trusty (which would be weird given your install medium is Jammy), or have third-party packages on your system, most likely installed through a third-party repository (e.g. PPA), or manually. Either way, this is not something we can support, so I'm closing this as Invalid. Your best bet moving forward is to uninstall libssl-dev:amd64 and libssl-dev:i386 temporarily, and then reinstall them from the official archive. ** Changed in: openssl (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2002355 Title: package libssl-dev 3.0.2-0ubuntu1.7 [modified: usr/include/openssl/aes.h usr/include/openssl/asn1.h usr/include/openssl/asn1_mac.h usr/include/openssl/asn1t.h usr/include/openssl/bio.h usr/include/openssl/blowfish.h usr/include/openssl/bn.h usr/include/openssl/buffer.h usr/include/openssl/camellia.h usr/include/openssl/cast.h usr/include/openssl/cmac.h usr/include/openssl/cms.h usr/include/openssl/comp.h usr/include/openssl/conf.h usr/include/openssl/conf_api.h usr/include/openssl/crypto.h usr/include/openssl/des.h usr/include/openssl/dh.h usr/include/openssl/dsa.h usr/include/openssl/dtls1.h usr/include/openssl/e_os2.h usr/include/openssl/ebcdic.h usr/include/openssl/ec.h usr/include/openssl/ecdh.h usr/include/openssl/ecdsa.h usr/include/openssl/engine.h usr/include/openssl/err.h usr/include/openssl/evp.h usr/include/openssl/hmac.h usr/include/openssl/lhash.h usr/include/openssl/md4.h usr/include/openssl/md5.h usr/include/openssl/modes.h usr/include/openssl/obj_mac.h usr/include/openssl/objects.h usr/include/openssl/ocsp.h usr/include/openssl/opensslv.h usr/include/openssl/ossl_typ.h usr/include/openssl/pem.h usr/include/openssl/pem2.h usr/include/openssl/pkcs12.h usr/include/openssl/pkcs7.h usr/include/openssl/rand.h usr/include/openssl/rc2.h usr/include/openssl/rc4.h usr/include/openssl/ripemd.h usr/include/openssl/rsa.h usr/include/openssl/safestack.h usr/include/openssl/seed.h usr/include/openssl/sha.h usr/include/openssl/srp.h usr/include/openssl/srtp.h usr/include/openssl/ssl.h usr/include/openssl/ssl2.h usr/include/openssl/ssl3.h usr/include/openssl/stack.h usr/include/openssl/symhacks.h usr/include/openssl/tls1.h usr/include/openssl/ts.h usr/include/openssl/txt_db.h usr/include/openssl/ui.h usr/include/openssl/whrlpool.h usr/include/openssl/x509.h usr/include/openssl/x509_vfy.h usr/include/openssl/x509v3.h] failed to install/upgrade: trying to overwrite shared '/usr/include/openssl/aes.h', which is different from other instances of package libssl-dev:i386 Status in openssl package in Ubuntu: Invalid Bug description: openssl lib ProblemType: Package DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: libssl-dev:i386: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Jan 10 00:43:30 2023 DpkgTerminalLog: Preparing to unpack .../libssl-dev_3.0.2-0ubuntu1.7_i386.deb ... Unpacking libssl-dev:i386 (3.0.2-0ubuntu1.7) over (1.0.1f-1ubuntu2.27) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/libssl-dev_3.0.2-0ubuntu1.7_i386.deb (--unpack): trying to overwrite shared '/usr/include/openssl/aes.h', which is different from other instances of package libssl-dev:i386 ErrorMessage: trying to overwrite shared '/usr/include/openssl/aes.h', which is different from other instances of package libssl-dev:i386 InstallationDate: Installed on 2023-01-03 (5 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: openssl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2002355/+subscriptions -- Mailing list: https://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 1983200] Re: package libc6 2.35-0ubuntu3 failed to install/upgrade: new libc6:amd64 package pre-installation script subprocess returned error exit status 255
Looking at the logs, this bug seems rather to be in /usr/share/perl5/Debconf/Db.pm, which is in debconf. Reassigning it there. ** Also affects: debconf (Ubuntu) Importance: Undecided Status: New ** Changed in: glibc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1983200 Title: package libc6 2.35-0ubuntu3 failed to install/upgrade: new libc6:amd64 package pre-installation script subprocess returned error exit status 255 Status in debconf package in Ubuntu: New Status in glibc package in Ubuntu: Invalid Bug description: I have an error there. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libc6 2.35-0ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Jul 31 11:39:05 2022 ErrorMessage: new libc6:amd64 package pre-installation script subprocess returned error exit status 255 InstallationDate: Installed on 2022-07-29 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.6 SourcePackage: glibc Title: package libc6 2.35-0ubuntu3 failed to install/upgrade: new libc6:amd64 package pre-installation script subprocess returned error exit status 255 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1983200/+subscriptions -- Mailing list: https://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 1995601] Re: tzdata 2022f ICU data update
** Tags added: fr-2936
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1995601
Title:
tzdata 2022f ICU data update
Status in tzdata package in Ubuntu:
Triaged
Status in tzdata source package in Focal:
New
Status in tzdata source package in Jammy:
New
Status in tzdata source package in Kinetic:
New
Status in tzdata source package in Lunar:
Triaged
Bug description:
The ICU data we embed in tzdata was out of sync on the 2022f-0ubuntu1
upload, still matching the 2022e data instead. It's been updated
upstream, so we need to do another round of SRUs for it:
https://github.com/unicode-org/icu-
data/commit/ad9d2568d02b2130f1ba34f876fc82cad32c522f
The following Python script should work with the update and crash on
obsolete data:
from datetime import datetime
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Chihuahua"))
before = datetime(2022, 10, 1)
after = datetime(2022, 11, 2)
assert(tz.utcoffset(before) == tz.utcoffset(after))
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1995601/+subscriptions
--
Mailing list: https://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 1995601] [NEW] tzdata 2022f ICU data update
Public bug reported:
The ICU data we embed in tzdata was out of sync on the 2022f-0ubuntu1
upload, still matching the 2022e data instead. It's been updated
upstream, so we need to do another round of SRUs for it:
https://github.com/unicode-org/icu-
data/commit/ad9d2568d02b2130f1ba34f876fc82cad32c522f
The following Python script should work with the update and crash on
obsolete data:
from datetime import datetime
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Chihuahua"))
before = datetime(2022, 10, 1)
after = datetime(2022, 11, 2)
assert(tz.utcoffset(before) == tz.utcoffset(after))
** Affects: tzdata (Ubuntu)
Importance: High
Status: Triaged
** Affects: tzdata (Ubuntu Focal)
Importance: Undecided
Status: New
** Affects: tzdata (Ubuntu Jammy)
Importance: Undecided
Status: New
** Affects: tzdata (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Affects: tzdata (Ubuntu Lunar)
Importance: High
Status: Triaged
** Tags: foundations-todo
** Also affects: tzdata (Ubuntu Lunar)
Importance: High
Status: Triaged
** Also affects: tzdata (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: tzdata (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: tzdata (Ubuntu Kinetic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1995601
Title:
tzdata 2022f ICU data update
Status in tzdata package in Ubuntu:
Triaged
Status in tzdata source package in Focal:
New
Status in tzdata source package in Jammy:
New
Status in tzdata source package in Kinetic:
New
Status in tzdata source package in Lunar:
Triaged
Bug description:
The ICU data we embed in tzdata was out of sync on the 2022f-0ubuntu1
upload, still matching the 2022e data instead. It's been updated
upstream, so we need to do another round of SRUs for it:
https://github.com/unicode-org/icu-
data/commit/ad9d2568d02b2130f1ba34f876fc82cad32c522f
The following Python script should work with the update and crash on
obsolete data:
from datetime import datetime
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Chihuahua"))
before = datetime(2022, 10, 1)
after = datetime(2022, 11, 2)
assert(tz.utcoffset(before) == tz.utcoffset(after))
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1995601/+subscriptions
--
Mailing list: https://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 1995209] Re: tzdata 2022f release
All verifications done (except for ICU data which wasn't ready) on bionic, focal, jammy and kinetic using fresh LXC containers and the instructions from https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984 adjusted for the new data updates. ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done verification-done-bionic verification-done-focal verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1995209 Title: tzdata 2022f release Status in tzdata package in Ubuntu: New Status in tzdata source package in Xenial: New Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Kinetic: Fix Committed Status in tzdata source package in Lunar: New Bug description: New timezone data, with the following timezones impacted: - Mexico will no longer observe DST except near the US border. Chihuahua moves to year-round -06 on 2022-10-30. - Fiji no longer observes DST. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1995209/+subscriptions -- Mailing list: https://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 1982583] Re: Fix for zlib CRC32 optimization for s390x
Folded into the LP #1990379 uploads to Jammy, Kinetic and Lunar. ** Also affects: zlib (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: zlib (Ubuntu Kinetic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1982583 Title: Fix for zlib CRC32 optimization for s390x Status in Ubuntu on IBM z Systems: In Progress Status in zlib package in Ubuntu: In Progress Status in zlib source package in Jammy: New Status in zlib source package in Kinetic: New Bug description: SRU Justification: -- [ Impact ] * There were two issues identified in the current zlib CRC32 optimization for s390x implementation: * 1) s390_crc32_vx() signature mismatch which causes a warning * 2) '-DS390_CRC32_VX' was not added to SFLAGS which results in vectorization being enabled only in the static library. * The fixes are quite small and affect each only one line: * 1) by using unsigned longs instead of uint32_t in s390_crc32_vx declaration * 2) by add line 'SFLAGS="$SFLAGS -DS390_CRC32_VX"' [ Test Plan ] * An affected Ubuntu release ([20.04], 22.04 and 22.10) installed on a z15/LinuxONE III or newer system is needed. * Then it's possible to test the updated package with the help of a small test program (in C) that checks for s390_crc32_vx() signature mismatches. * The bug reporter has a set of s390x-specific tests that will be executed. * Test will be done by IBM. [ Where problems could occur ] * The fixes are each limited to one line, hence there are not many issues to expect, other than: * Typos (e.g. in the flags), mixing of CFLAGS and SFLAGS, * in case the changed data type in s390_crc32_vx is causing issues inside of s390_crc32_vx or in other parts of the code. * Structural and syntactical issues can be identified with a test build that was done for all affected Ubuntu releases and for all major archs: https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379+lp1982583 [ Other Info ] * This bug (LP#1982583) is solved in combination with LP#1990379, so that only one package update is needed. However, LP#1990379 also affects Focal, but this bug only Jammy and Kinetic. * To fix LP#1990379 also for focal the debdiff mentioned there is needed, too. __ 'zlib CRC32 optimization for s390x works only in a static library' I've discovered two issues in lp1932010-ibm-z-add-vectorized- crc32-implementation.patch: 1) s390_crc32_vx() signature mismatch, resulting in a warning. 2) -DS390_CRC32_VX is not added to SFLAGS, resulting in vectorization being enabled only in the static library. I've attached the updated patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982583/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990379] Re: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used
Uploaded to Lunar, Kinetic, Jammy and Focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1990379 Title: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used Status in Ubuntu on IBM z Systems: In Progress Status in zlib package in Ubuntu: In Progress Status in zlib source package in Focal: Triaged Status in zlib source package in Jammy: Triaged Status in zlib source package in Kinetic: In Progress Bug description: SRU Justification: -- [ Impact ] * The zlib function inflate() does not update strm.adler in case DFLTCC is used. * This issue was exposed by Java Certification Kit (JCK) running on z15 hardware and newer and impacts all JDK versions (8,11,17, etc.) that use the system default settings. * The JCK failure impacts the ability to certify Java SDKs on this platform/Linux-distribution combination. * On top the incorrect alder32 result may cause functional issues with Java applications that depend on the result. [ Test Plan ] * An affected Ubuntu release (20.04, 22.04 and 22.10) installed on a z15/LinuxONE III or newer system is needed. * Then it's possible to test the updated package with the help of a small test program (in C) that makes use of the zlib1g library or run the Java Certification Kit. * Test will be done by IBM. [ Where problems could occur ] * The patch is a one-line change: https://launchpadlibrarian.net/626003193/410-lp1990379.patch and there are not many issues to expect. * There could be a potential problem with the adler field in the strm struct. For example in case the struct is not as assumed or contains and unexpected value, which would then ripple through the other fields, too. * Structural changes could be identified with a test build that was done for all affected Ubuntu releases and for all major architectures: https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379 [ Other Info ] * The patch itself is the same for all zlib version in 20.04, 22.04 and 22.10 - no further adjustments were needed. * This bug (LP#1990379) is solved in combination with LP#1982583, so that only one package update is needed. However, this bug affects Kinetic, jammy and Focal, but LP#1982583 only Jammy and Kinetic. * The debdiffs for Kinetic and Jammy should be taken from LP#1982583, and the remaining debdiff for Focal from here. __ == Comment: #0 - Ilya Leoshkevich - 2022-09-21 05:02:24 == inflate() does not update strm.adler if DFLTCC is used. Found with a JDK test. zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349 Updated zlib PR: https://github.com/madler/zlib/pull/410 zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920 zlib diff: https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620 Ubuntu 20.04 and later need to be fixed. --- External link: https://warthogs.atlassian.net/browse/PEI-28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969671] Re: Misspelled Ukrainian cities in tzdata
As for verification, I verified this using the following command in LXC containers: ❯ LANG=C timedatectl list-timezones | grep Kyiv Europe/Kyiv This worked in all containers. ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-jammy ** Tags added: verification-done verification-done-bionic verification-done-focal verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1969671 Title: Misspelled Ukrainian cities in tzdata Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Bug description: When user is prompted to choose a city in the region 'Europe' they have a choice of 4 cities in Ukraine: 23. Kiev -> should be Kyiv 46. Simferopol - > OK 54. Uzhgorod -> should be Uzhhorod 62. Zaporozhye -> should be Zaporizhzhia The 'should be' variant is the only correct transliteration from Ukrainian into English. Possible useful pieces of ubuntu-bug report (run in a headless ubuntu/latest docker image): DistroRelease: Ubuntu 20.04 Package: tzdata 2022a-0ubuntu0.20.04 Tags: focal PackageArchitecture: all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1969671/+subscriptions -- Mailing list: https://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 1733346] Re: package keyboard-configuration 1.166ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Changed in: console-setup (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1733346 Title: package keyboard-configuration 1.166ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in console-setup package in Ubuntu: Incomplete Bug description: no idee, the bug was displayed after i loged in ... ProblemType: Package DistroRelease: Ubuntu 17.10 Package: keyboard-configuration 1.166ubuntu7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.4 Architecture: amd64 Date: Sun Nov 19 21:10:16 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-11-19 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: console-setup Title: package keyboard-configuration 1.166ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to artful on 2017-11-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1733346/+subscriptions -- Mailing list: https://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 1969671] Re: Misspelled Ukrainian cities in tzdata
I retried chrony and it passed :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1969671 Title: Misspelled Ukrainian cities in tzdata Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Bug description: When user is prompted to choose a city in the region 'Europe' they have a choice of 4 cities in Ukraine: 23. Kiev -> should be Kyiv 46. Simferopol - > OK 54. Uzhgorod -> should be Uzhhorod 62. Zaporozhye -> should be Zaporizhzhia The 'should be' variant is the only correct transliteration from Ukrainian into English. Possible useful pieces of ubuntu-bug report (run in a headless ubuntu/latest docker image): DistroRelease: Ubuntu 20.04 Package: tzdata 2022a-0ubuntu0.20.04 Tags: focal PackageArchitecture: all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1969671/+subscriptions -- Mailing list: https://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 1992692] Re: tzdata 2022e release
Both regressions were retried and succeeded.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1992692
Title:
tzdata 2022e release
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Trusty:
Fix Released
Status in tzdata source package in Xenial:
Fix Released
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Jammy:
Fix Committed
Bug description:
New timezone data, with the following timezones impacted:
- Palestine transitions are now Saturdays at 02:00. This means 2022 falls
back 10-29 at 02:00, not 10-28 at 01:00.
- Simplify three Ukraine zones into one.
- Jordan and Syria switch from +02/+03 with DST to year-round +03.
icu update to 2022e: https://unicode-
org.atlassian.net/browse/ICU-22178
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Asia/Gaza | grep 'Oct.*2022'
-> should indicate Oct 29, not Oct 28
2) zdump -v Asia/Damascus | tail
-> last dates should be in 2022, not in 2499
[Test Case for releases >= 20.04 LTS]
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
1) sudo apt-get install python3-icu
2) Run the following python script:
from datetime import datetime
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("Asia/Gaza"))
always_before = datetime(2022, 10, 1)
now_before = datetime(2022, 10, 29)
always_after = datetime(2022, 11, 1)
assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
The assertions would crash on 2022c.
[Test Case for releases <= 20.04 LTS]
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and
earlier releases. Subsequently, these should be checked for using the following:
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1992692/+subscriptions
--
Mailing list: https://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 1968845] Re: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot
** Changed in: dbus (Ubuntu) Status: Invalid => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1968845 Title: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot Status in dbus package in Ubuntu: Triaged Bug description: Upgrading on a virtual machine from 20.04 to 22.04. I have had this happen twice now, I got one upgrade done without this bug. Basically the package installation stops at dbus package asking for a reboot as it was unable to upgrade as dbus-daemon was running. And rebooting at this stage obviously will cause a non-functioning system. Added a screenshot of the upgrade window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1968845/+subscriptions -- Mailing list: https://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 1993991] Re: package linux-image-5.15.0-52-generic 5.15.0-52.58 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Hi, Looking into the Df.txt logs, I see this: /dev/sdb6 210872 170420 23468 88% /boot You probably don't have enough space on your /boot for the new kernel. Could you try freeing some space on it or resizing it? ** Changed in: initramfs-tools (Ubuntu) Status: New => Incomplete -- 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/1993991 Title: package linux-image-5.15.0-52-generic 5.15.0-52.58 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Incomplete Bug description: s ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lucrece1826 F pulseaudio /dev/snd/controlC1: lucrece1826 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Sun Oct 23 09:59:11 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2022-10-15 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp8s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-52-generic root=UUID=55ba579c-246e-43a7-a4fc-eb1591e7cc04 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7 RfKill: SourcePackage: initramfs-tools Title: package linux-image-5.15.0-52-generic 5.15.0-52.58 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: 990FX Extreme9 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd03/29/2016:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn990FXExtreme9:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1993991/+subscriptions -- Mailing list: https://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 1992692] Re: tzdata 2022e release
Hi, I verified the 2022e-0ubuntu0.XX.04.0 packages on jammy, focal and
bionic using fresh LXC containers. I'll look into the autopkgtest
regressions as well.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-jammy
** Tags added: verification-done verification-done-bionic
verification-done-focal verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1992692
Title:
tzdata 2022e release
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Trusty:
Fix Released
Status in tzdata source package in Xenial:
Fix Released
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Jammy:
Fix Committed
Bug description:
New timezone data, with the following timezones impacted:
- Palestine transitions are now Saturdays at 02:00. This means 2022 falls
back 10-29 at 02:00, not 10-28 at 01:00.
- Simplify three Ukraine zones into one.
- Jordan and Syria switch from +02/+03 with DST to year-round +03.
icu update to 2022e: https://unicode-
org.atlassian.net/browse/ICU-22178
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Asia/Gaza | grep 'Oct.*2022'
-> should indicate Oct 29, not Oct 28
2) zdump -v Asia/Damascus | tail
-> last dates should be in 2022, not in 2499
[Test Case for releases >= 20.04 LTS]
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
1) sudo apt-get install python3-icu
2) Run the following python script:
from datetime import datetime
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("Asia/Gaza"))
always_before = datetime(2022, 10, 1)
now_before = datetime(2022, 10, 29)
always_after = datetime(2022, 11, 1)
assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
The assertions would crash on 2022c.
[Test Case for releases <= 20.04 LTS]
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and
earlier releases. Subsequently, these should be checked for using the following:
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1992692/+subscriptions
--
Mailing list: https://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 1992692] Re: tzdata 2022e release
** Description changed:
New timezone data, with the following timezones impacted:
- Palestine transitions are now Saturdays at 02:00. This means 2022 falls
back 10-29 at 02:00, not 10-28 at 01:00.
- Simplify three Ukraine zones into one.
- Jordan and Syria switch from +02/+03 with DST to year-round +03.
icu update to 2022e: https://unicode-org.atlassian.net/browse/ICU-22178
+
+ Verification is done with 'zdump'. The first timezone that gets changed
+ in the updated package is dumped with 'zdump -v
+ $region/$timezone_that_changed' (this needs to be greped for in
+ /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
+ compared to the same output after the updated package got installed. If
+ those are different the verification is considered done.
+
+ [Test Case for all releases]
+ 1) zdump -v Asia/Gaza | grep 'Oct.*2022'
+ -> should indicate Oct 29, not Oct 28
+ 2) zdump -v Asia/Damascus | tail
+ -> last dates should be in 2022, not in 2499
+
+ [Test Case for releases >= 20.04 LTS]
+
+ For releases with ICU timezone data verification is done using the following
with dates before and after the change:
+ 1) sudo apt-get install python3-icu
+ 2) Run the following python script:
+
+ from datetime import datetime
+ from icu import ICUtzinfo, TimeZone
+ tz = ICUtzinfo(TimeZone.createTimeZone("Asia/Gaza"))
+ always_before = datetime(2022, 10, 1)
+ now_before = datetime(2022, 10, 29)
+ always_after = datetime(2022, 11, 1)
+ assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
+ assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
+
+ The assertions would crash on 2022c.
+
+ [Test Case for releases <= 20.04 LTS]
+
+ Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and
earlier releases. Subsequently, these should be checked for using the following:
+ diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
+
+ Nothing should be returned by the above command.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1992692
Title:
tzdata 2022e release
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Bionic:
New
Status in tzdata source package in Focal:
New
Status in tzdata source package in Jammy:
New
Bug description:
New timezone data, with the following timezones impacted:
- Palestine transitions are now Saturdays at 02:00. This means 2022 falls
back 10-29 at 02:00, not 10-28 at 01:00.
- Simplify three Ukraine zones into one.
- Jordan and Syria switch from +02/+03 with DST to year-round +03.
icu update to 2022e: https://unicode-
org.atlassian.net/browse/ICU-22178
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Asia/Gaza | grep 'Oct.*2022'
-> should indicate Oct 29, not Oct 28
2) zdump -v Asia/Damascus | tail
-> last dates should be in 2022, not in 2499
[Test Case for releases >= 20.04 LTS]
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
1) sudo apt-get install python3-icu
2) Run the following python script:
from datetime import datetime
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("Asia/Gaza"))
always_before = datetime(2022, 10, 1)
now_before = datetime(2022, 10, 29)
always_after = datetime(2022, 11, 1)
assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
The assertions would crash on 2022c.
[Test Case for releases <= 20.04 LTS]
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and
earlier releases. Subsequently, these should be checked for using the following:
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1992692/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990379] Re: [FFe][UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used
** Summary changed: - [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used + [FFe][UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1990379 Title: [FFe][UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used Status in Ubuntu on IBM z Systems: In Progress Status in zlib package in Ubuntu: In Progress Status in zlib source package in Focal: In Progress Status in zlib source package in Jammy: In Progress Status in zlib source package in Kinetic: In Progress Bug description: SRU Justification: -- [ Impact ] * The zlib function inflate() does not update strm.adler in case DFLTCC is used. * This issue was exposed by Java Certification Kit (JCK) running on z15 hardware and newer and impacts all JDK versions (8,11,17, etc.) that use the system default settings. * The JCK failure impacts the ability to certify Java SDKs on this platform/Linux-distribution combination. * On top the incorrect alder32 result may cause functional issues with Java applications that depend on the result. [ Test Plan ] * An affected Ubuntu release (20.04, 22.04 and 22.10) installed on a z15/LinuxONE III or newer system is needed. * Then it's possible to test the updated package with the help of a small test program (in C) that makes use of the zlib1g library or run the Java Certification Kit. * Test will be done by IBM. [ Where problems could occur ] * The patch is a one-line change: https://launchpadlibrarian.net/626003193/410-lp1990379.patch and there are not many issues to expect. * There could be a potential problem with the adler field in the strm struct. For example in case the struct is not as assumed or contains and unexpected value, which would then ripple through the other fields, too. * Structural changes could be identified with a test build that was done for all affected Ubuntu releases and for all major architectures: https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379 [ Other Info ] * The patch itself is the same for all zlib version in 20.04, 22.04 and 22.10 - no further adjustments were needed. * This bug (LP#1990379) is solved in combination with LP#1982583, so that only one package update is needed. However, this bug affects Kinetic, jammy and Focal, but LP#1982583 only Jammy and Kinetic. * The debdiffs for Kinetic and Jammy should be taken from LP#1982583, and the remaining debdiff for Focal from here. __ == Comment: #0 - Ilya Leoshkevich - 2022-09-21 05:02:24 == inflate() does not update strm.adler if DFLTCC is used. Found with a JDK test. zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349 Updated zlib PR: https://github.com/madler/zlib/pull/410 zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920 zlib diff: https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620 Ubuntu 20.04 and later need to be fixed. --- External link: https://warthogs.atlassian.net/browse/PEI-28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901723] Re: backport Refactor BN_R_NO_INVERSE logic in internal functions
Reading the upstream bugs, this might still be worth backporting, but since python-cryptography has implemented a workaround and it's been sitting here for a while this isn't critical. ** Changed in: openssl (Ubuntu) Importance: Undecided => Medium ** Changed in: openssl (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1901723 Title: backport Refactor BN_R_NO_INVERSE logic in internal functions Status in openssl package in Ubuntu: Triaged Bug description: backport Refactor BN_R_NO_INVERSE logic in internal functions https://github.com/openssl/openssl/commit/35bb0e44c6168facbb3acedbc7d4f2dcbdd65224 https://github.com/openssl/openssl/issues/12129 https://github.com/pyca/cryptography/issues/5521#issuecomment-717293145 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1901723/+subscriptions -- Mailing list: https://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 1991829] Re: machinectl read-only does not work
** Changed in: systemd (Ubuntu Kinetic) Status: New => Triaged -- 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/1991829 Title: machinectl read-only does not work Status in systemd package in Ubuntu: Triaged Status in systemd source package in Focal: New Status in systemd source package in Jammy: New Status in systemd source package in Kinetic: Triaged Bug description: [impact] machinectl read-only does not work [test case] On a system where the systemd machines dir is *not* on a btrfs volume (e.g. it's on a normal ext4 fs), create an image 'test' and then: $ sudo machinectl image-status test test Type: directory Path: /var/lib/machines/test Hostname: ubuntu OS: Ubuntu 20.04.5 LTS RO: writable Created: Wed 2022-10-05 13:41:15 EDT; 34s ago $ sudo machinectl read-only test Could not mark image read-only: Access denied [regression potential] failure marking images ro or rw [scope] this is needed in all releases that include machinectl this is fixed upstream by 137d162c42ed858613afc3d7493d08d4ae6d5c1b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1991829/+subscriptions -- Mailing list: https://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 1991761] Re: Backport packages for 22.04.2 HWE stack
** Tags added: foundations-triage-discuss -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1991761 Title: Backport packages for 22.04.2 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-15 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in directx-headers source package in Jammy: New Status in libdrm source package in Jammy: New Status in llvm-toolchain-15 source package in Jammy: New Status in mesa source package in Jammy: New Bug description: WIP directx-headers libdrm llvm-15 mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1991761/+subscriptions -- Mailing list: https://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 1991598] Re: laptop not reliably going to sleep when lid closed on battery power
Looking at the attached journal logs, there's a lot of Yubikey service activity between the lid closed and lid opened lines. Do you use a third-party package to handle your Yubikey, by any chance? ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1991598 Title: laptop not reliably going to sleep when lid closed on battery power Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: I have the shell configured to lock the screen when I close the lid and go to sleep after 20 idle minutes on battery power. Immediately before I opened my laptop and unlocked it to submit this bug, the laptop was unplugged from battery power and sitting with the lid closed for hours and never went to sleep. When I opened the lid I found it locked as it should have been, so that's apparently not the issue. The issue is that it just never went to sleep even though it was idle for hours. This is a regression from Jammy. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 3 21:24:57 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (1144 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 43.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-09-24 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991598/+subscriptions -- Mailing list: https://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 1977630] Re: machinectl pull-tar/pull-raw Operation not permitted
** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu Jammy) Importance: Undecided => High ** Changed in: systemd (Ubuntu Jammy) Status: New => Triaged ** Tags added: foundations-triage-discuss -- 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/1977630 Title: machinectl pull-tar/pull-raw Operation not permitted Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Triaged Bug description: [impact] machinectl pull-tar does not work, ever [test case] see comment 2 [regression potential] problems/failures during pull-tar operation [scope] needed only in j fixed (indirectly) by upstream commit referenced in original description, which is included in v250, so fixed already in k pull-tar does not fail on f; no fix needed there [original description] There is a bug in systemd 249, where one can't pull any images. This was fixed in version 250, and never got backported. (FIX: https://github.com/systemd/systemd/commit/c40d82abf7b23803aa7394a7a7e24c40c32af851) Hopefully this can be addressed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-container 249.11-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 4 04:51:42 2022 InstallationDate: Installed on 2022-06-01 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1977630/+subscriptions -- Mailing list: https://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 1955804] Re: make and make test fail
Marking this as invalid, as the correct way to install libcap2 in Ubuntu would be to use the package manager to do so, e.g. `apt install libcap2`. Glad that the issue was eventually resolved, though :) ** Changed in: libcap2 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1955804 Title: make and make test fail Status in libcap2 package in Ubuntu: Invalid Bug description: Hello, make and make test fail like the printscreen following : CGO_LDFLAGS_ALLOW="-Wl,-wrap,.+" CGO_CFLAGS="-I/home/ubuntu/programs/libcap-2.32/libcap/include" CGO_LDFLAGS="-L/home/ubuntu/programs/libcap-2.32/libcap" GOPATH="/home/ubuntu/programs/libcap-2.32/go" go install libcap/psx go install: version is required when current directory is not in a module Try 'go install libcap/psx@latest' to install the latest version make[1]: *** [Makefile:37 : pkg/linux_amd64/libcap/psx.a] Erreur 1 make[1] : on quitte le répertoire « /home/ubuntu/programs/libcap-2.32/go » make: *** [Makefile:13 : all] Erreur 2 root@ubuntu-ThinkPad-X250:/home/ubuntu/programs/libcap-2.32# go install libcap/psx@latest go install: libcap/psx@latest: malformed module path "libcap/psx": missing dot in first path element root@ubuntu-ThinkPad-X250:/home/ubuntu/programs/libcap-2.32# thank you in advance to help myself fully install your program, Regards. Dorian ROSSE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1955804/+subscriptions -- Mailing list: https://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 1899103] Re: libpam-cap causes PAM applications to crash
** Changed in: libcap2 (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1899103 Title: libpam-cap causes PAM applications to crash Status in libcap2 package in Ubuntu: Triaged Bug description: Install ocserv and setup for PAM authentication. On second connection, ocserv crashes due to a double free in PAM. Repro steps: 1. Create Dockerfile that installs ocserv + libpam-cap ``` FROM ubuntu:20.04 RUN apt update && apt install -y ocserv libpam-cap && apt autoremove && apt clean COPY server-cert.pem /etc/ssl/ocserv_test.cert COPY server-key.pem /etc/ssl/ocserv_test.key COPY ca-cert.pem /etc/ssl/certs/ssl-cert-snakeoil.pem COPY ocserv.conf /etc/ocserv/ocserv.conf RUN useradd test RUN echo "test\ntest" | passwd test ENV MALLOC_CHECK_=3 CMD ocserv -f -d 1 ``` 2. Build container: ``` sudo docker build -t ocserv:20.04 . ``` 3. Launch container: ``` docker run -p 443:443/tcp -p 443:443/udp -it --rm --device /dev/net/tun --cap-add net_admin ocserv:20.04 ``` 4. From another console, connect / disconnect: ``` while true; do echo test | openconnect https://localhost -u test --passwd-on-stdin --servercert pin-sha256:qBLVTyoXiFdn+0pW+eSGqnVCEnMbLigVf5vAl1ZewW4= --background && sleep 2 && pkill openconnect && sleep 2;done ``` 5. ocserv crashes: free(): invalid pointer ocserv[8]: main: main-sec-mod-cmd.c:106: command socket for sec-mod closed ocserv[8]: main: main.c:1179: error in command from sec-mod ocserv[8]: main: termination request received; waiting for children to die For more details see: https://gitlab.com/openconnect/ocserv/-/issues/361 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1899103/+subscriptions -- Mailing list: https://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 1991771] Re: [FFe] Update to 3.0.6
** Patch added: "openssl.diff" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1991771/+attachment/5621368/+files/openssl.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1991771 Title: [FFe] Update to 3.0.6 Status in openssl package in Ubuntu: Confirmed Bug description: There's an upcoming security release for OpenSSL according to https://mta.openssl.org/pipermail/openssl- users/2022-October/015477.html The timing is somewhat unfortunate given our own release schedule. The current version of openssl in kinetic, 3.0.5-2ubuntu1, is actually a snapshot of the 3.0 branch ahead of 3.0.5 (inherited from Debian during the last merge). Sadly, they don't have a proper changelog (even partial) for the upcoming release yet, but I'll attach the diff and shortlog between our current version and the current state of the branch to get an idea of what's to come. As usual for their 3.0 point releases, it's not just security fixes but general bugfixes as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1991771/+subscriptions -- Mailing list: https://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 1991771] [NEW] [FFe] Update to 3.0.6
Public bug reported: There's an upcoming security release for OpenSSL according to https://mta.openssl.org/pipermail/openssl-users/2022-October/015477.html The timing is somewhat unfortunate given our own release schedule. The current version of openssl in kinetic, 3.0.5-2ubuntu1, is actually a snapshot of the 3.0 branch ahead of 3.0.5 (inherited from Debian during the last merge). Sadly, they don't have a proper changelog (even partial) for the upcoming release yet, but I'll attach the diff and shortlog between our current version and the current state of the branch to get an idea of what's to come. As usual for their 3.0 point releases, it's not just security fixes but general bugfixes as well. ** Affects: openssl (Ubuntu) Importance: High Status: Confirmed ** Attachment added: "openssl.shortlog" https://bugs.launchpad.net/bugs/1991771/+attachment/5621367/+files/openssl.shortlog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1991771 Title: [FFe] Update to 3.0.6 Status in openssl package in Ubuntu: Confirmed Bug description: There's an upcoming security release for OpenSSL according to https://mta.openssl.org/pipermail/openssl- users/2022-October/015477.html The timing is somewhat unfortunate given our own release schedule. The current version of openssl in kinetic, 3.0.5-2ubuntu1, is actually a snapshot of the 3.0 branch ahead of 3.0.5 (inherited from Debian during the last merge). Sadly, they don't have a proper changelog (even partial) for the upcoming release yet, but I'll attach the diff and shortlog between our current version and the current state of the branch to get an idea of what's to come. As usual for their 3.0 point releases, it's not just security fixes but general bugfixes as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1991771/+subscriptions -- Mailing list: https://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 1991067] Re: p11-kit 0.24.1-1ubuntu1 induces FTBFS in gnutls
Thanks, uploaded :) ** Changed in: p11-kit (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to p11-kit in Ubuntu. https://bugs.launchpad.net/bugs/1991067 Title: p11-kit 0.24.1-1ubuntu1 induces FTBFS in gnutls Status in p11-kit package in Ubuntu: Fix Committed Bug description: Patches added in 0.24.1-1ubuntu1 prevent gnutls from building. Upstream has indicated that an additional change should have been included as mentioned at https://github.com/p11-glue/p11-kit/issues/419#issuecomment-1259353294 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/1991067/+subscriptions -- Mailing list: https://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 1991067] Re: p11-kit 0.24.1-1ubuntu1 induces FTBFS in gnutls
** Changed in: p11-kit (Ubuntu) Assignee: (unassigned) => Simon Chopin (schopin) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to p11-kit in Ubuntu. https://bugs.launchpad.net/bugs/1991067 Title: p11-kit 0.24.1-1ubuntu1 induces FTBFS in gnutls Status in p11-kit package in Ubuntu: In Progress Bug description: Patches added in 0.24.1-1ubuntu1 prevent gnutls from building. Upstream has indicated that an additional change should have been included as mentioned at https://github.com/p11-glue/p11-kit/issues/419#issuecomment-1259353294 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/1991067/+subscriptions -- Mailing list: https://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 1621801] Re: package p11-kit-modules:i386 0.23.2-5~ubuntu16.04.1 failed to install/upgrade: package p11-kit-modules:i386 0.23.2-3 cannot be configured because p11-kit-modules:amd
Marking as Won't Fix as this was reported for a series that's now unsupported (Xenial) ** Changed in: p11-kit (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to p11-kit in Ubuntu. https://bugs.launchpad.net/bugs/1621801 Title: package p11-kit-modules:i386 0.23.2-5~ubuntu16.04.1 failed to install/upgrade: package p11-kit-modules:i386 0.23.2-3 cannot be configured because p11-kit-modules:amd64 is at a different version (0.23.2-5~ubuntu16.04.1) Status in p11-kit package in Ubuntu: Won't Fix Bug description: Crashes every time the machine is restarted. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: p11-kit-modules:i386 0.23.2-5~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Sep 7 14:53:00 2016 DuplicateSignature: package:p11-kit-modules:i386:0.23.2-5~ubuntu16.04.1 Setting up libfontembed1:amd64 (1.8.3-2ubuntu3.1) ... dpkg: error processing package p11-kit-modules:amd64 (--configure): package p11-kit-modules:amd64 0.23.2-5~ubuntu16.04.1 cannot be configured because p11-kit-modules:i386 is at a different version (0.23.2-3) ErrorMessage: package p11-kit-modules:i386 0.23.2-3 cannot be configured because p11-kit-modules:amd64 is at a different version (0.23.2-5~ubuntu16.04.1) InstallationDate: Installed on 2016-04-12 (149 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: p11-kit Title: package p11-kit-modules:i386 0.23.2-5~ubuntu16.04.1 failed to install/upgrade: package p11-kit-modules:i386 0.23.2-3 cannot be configured because p11-kit-modules:amd64 is at a different version (0.23.2-5~ubuntu16.04.1) UpgradeStatus: Upgraded to xenial on 2016-08-14 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/1621801/+subscriptions -- Mailing list: https://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 1991067] Re: p11-kit 0.24.1-1ubuntu1 induces FTBFS in gnutls
** Changed in: p11-kit (Ubuntu) Status: New => Triaged ** Changed in: p11-kit (Ubuntu) Importance: Undecided => High ** Changed in: p11-kit (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to p11-kit in Ubuntu. https://bugs.launchpad.net/bugs/1991067 Title: p11-kit 0.24.1-1ubuntu1 induces FTBFS in gnutls Status in p11-kit package in Ubuntu: In Progress Bug description: Patches added in 0.24.1-1ubuntu1 prevent gnutls from building. Upstream has indicated that an additional change should have been included as mentioned at https://github.com/p11-glue/p11-kit/issues/419#issuecomment-1259353294 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/1991067/+subscriptions -- Mailing list: https://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 1989969] Re: autopkgtest TEST-36-NUMAPOLICY failure on ppc64el
** Changed in: systemd (Ubuntu) Status: Triaged => Fix Committed -- 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/1989969 Title: autopkgtest TEST-36-NUMAPOLICY failure on ppc64el Status in systemd package in Ubuntu: Fix Committed Bug description: In Kinetic, TEST-36-NUMAPOLICY from upstream-2 fails very frequently on ppc64el. See for example: https://autopkgtest.ubuntu.com/results/autopkgtest- kinetic/kinetic/ppc64el/s/systemd/20220908_195425_da51e@/log.gz, and the full kinetic ppc64el history: https://autopkgtest.ubuntu.com/packages/systemd/kinetic/ppc64el. It has passed on very few occasions. I have tried to debug this locally but have gotten very little useful information (i.e. not enough to open an upstream bug). For now it is probably best to denylist this test on ppc64el. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1989969/+subscriptions -- Mailing list: https://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 1990187] Re: systemd-resolved recommends libnss-resolve in kinetic, pulls it into minimal system where it was explicitly excluded before
** Changed in: systemd (Ubuntu) Status: Triaged => Fix Committed -- 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/1990187 Title: systemd-resolved recommends libnss-resolve in kinetic, pulls it into minimal system where it was explicitly excluded before Status in systemd package in Ubuntu: Fix Committed Bug description: In kinetic, systemd-resolved now Recommends: libnss-resolve, pulling it into the ubuntu-minimal seed. In the past we briefly had libnss-resolve seeded (between xenial and bionic LTSes but not in any LTS) but it was removed because: - it was redundant; /etc/resolv.conf was consistent and correct. - its presence could mask wrong DNS configuration resulting in difficult-to-debug differences in behavior between applications that did use nss_resolved via /etc/nsswitch.conf and those that did not (examples: i386 binaries that could not use nss_resolved because it was not installed; statically-linked go implementations that parsed /etc/resolve.conf directly and did not load NSS modules) This new recommends was noticed specifically because of some broken kinetic container images where /etc/resolv.conf was broken (empty) and *some* applications still worked via nss but others failed by trying to use the DNS protocol directly. (I.e.: 2nd point above) I believe systemd-resolved should drop its recommends on libnss- resolve for Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990187/+subscriptions -- Mailing list: https://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 1990278] Re: systemd-resolved not included in Ubuntu bootstrap
** Changed in: systemd (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1990278 Title: systemd-resolved not included in Ubuntu bootstrap Status in systemd package in Ubuntu: Fix Committed Bug description: By default, i.e. with no --variant specified, debootstrap will only pull in packages with Priority: required or important. Before the systemd-resolved package split, resolved would be included because it was shipped with the systemd binary package, which is Priority: important. Currently there is no Priority: set on systemd-resolved, so it is not included with the deafult Ubuntu bootstrap. The systemd-resolved package should have Priority: important to fix this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
