[Bug 2070371] Re: [VROC] [Ub 24.04] mdadm: grow for R0 not start - missing patch
Yes, it is currently under the SRU review process for 24.04 : https://launchpad.net/ubuntu/noble/+queue?queue_state=1&queue_text=mdadm ** Changed in: mdadm (Ubuntu Noble) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070371 Title: [VROC] [Ub 24.04] mdadm: grow for R0 not start - missing patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2070371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069821] Re: [VROC] [Ub 24.04] mdadm: buffer overflow detected
Hello Mauricio and all, Thanks Mauricio for this precious feedback I did the necessary work required by this feedback and the new package has been uploaded for SRU review : https://launchpad.net/ubuntu/noble/+queue?queue_state=1&queue_text=mdadm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069821 Title: [VROC] [Ub 24.04] mdadm: buffer overflow detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2069821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 2073525] Re: [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids
** Changed in: kobuk Status: New => In Progress ** Changed in: kobuk Assignee: (unassigned) => Hector CAO (hectorcao) ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2073525 Title: [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids Status in The Kobuk project: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Noble: Fix Committed Bug description: Public bug of https://bugs.launchpad.net/bugs/2073432 [ Impact ] The QAT kernel driver require those for For Sierra forest and Granite rapids hardware. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/qat_402xx.bin https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/qat_402xx_mmp.bin [ Test Plan ] cpa_sample_code supplied with qatlib and the Linux kernel can be run to validate the firmware. [ Where problems could occur ] QAT not working on those platform. [ Other Info ] * Requested by intel, compatible on kernel since 6.4, mantic doesn't apply as EOL. To manage notifications about this bug go to: https://bugs.launchpad.net/kobuk/+bug/2073525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Bug 2073525] Re: [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids
** Changed in: kobuk Status: New => In Progress ** Changed in: kobuk Assignee: (unassigned) => Hector CAO (hectorcao) ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073525 Title: [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids To manage notifications about this bug go to: https://bugs.launchpad.net/kobuk/+bug/2073525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 2073525] Re: [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids
That is what i did for the validation of this issue: Release : 24.04 --- CPU --- Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 45 bits physical, 48 bits virtual Byte Order: Little Endian CPU(s): 288 On-line CPU(s) list:0-287 Vendor ID:GenuineIntel Model name: Intel(R) Xeon(R) 6780E linux-firmware: --- Installed: 20240318.git3b128b60-0ubuntu2.2 Candidate: 20240318.git3b128b60-0ubuntu2.2 Version table: *** 20240318.git3b128b60-0ubuntu2.2 500 500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 100 /var/lib/dpkg/status 20240318.git3b128b60-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages Boot dmesg: [ 16.503031] 4xxx :01:00.0: Direct firmware load for qat_402xx_mmp.bin failed with error -2 [ 16.503037] 4xxx :01:00.0: Failed to load MMP firmware qat_402xx_mmp.bin [ 16.505161] 4xxx :01:00.0: Resetting device qat_dev0 [ 16.752318] 4xxx :0b:00.0: Direct firmware load for qat_402xx_mmp.bin failed with error -2 [ 16.752323] 4xxx :0b:00.0: Failed to load MMP firmware qat_402xx_mmp.bin [ 16.754252] 4xxx :0b:00.0: Resetting device qat_dev0 [ 17.256825] 4xxx :81:00.0: Direct firmware load for qat_402xx_mmp.bin failed with error -2 [ 17.256837] 4xxx :81:00.0: Failed to load MMP firmware qat_402xx_mmp.bin [ 17.259506] 4xxx :81:00.0: Resetting device qat_dev0 [ 17.370148] 4xxx :8b:00.0: Direct firmware load for qat_402xx_mmp.bin failed with error -2 [ 17.370157] 4xxx :8b:00.0: Failed to load MMP firmware qat_402xx_mmp.bin [ 17.372417] 4xxx :8b:00.0: Resetting device qat_dev0 Install the package in proposed --- linux-firmware: --- Installed: 20240318.git3b128b60-0ubuntu2.3 Candidate: 20240318.git3b128b60-0ubuntu2.3 Version table: *** 20240318.git3b128b60-0ubuntu2.3 100 100 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages 100 /var/lib/dpkg/status 20240318.git3b128b60-0ubuntu2.2 500 500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 20240318.git3b128b60-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages Dmesg --- [ 17.288876] 4xxx :01:00.0: qat_dev0 started 9 acceleration engines [ 17.468869] 4xxx :0b:00.0: qat_dev1 started 9 acceleration engines [ 17.700878] 4xxx :81:00.0: qat_dev2 started 9 acceleration engines [ 17.878875] 4xxx :8b:00.0: qat_dev3 started 9 acceleration engines List of the PCI devices: --- ubuntu@cessna-726624:~$ lspci -d :4944 -k 01:00.0 Co-processor: Intel Corporation 4xxx Series QAT (rev 20) Subsystem: Intel Corporation 4xxx Series QAT Kernel driver in use: 4xxx Kernel modules: qat_4xxx 0b:00.0 Co-processor: Intel Corporation 4xxx Series QAT (rev 20) Subsystem: Intel Corporation 4xxx Series QAT Kernel driver in use: 4xxx Kernel modules: qat_4xxx 81:00.0 Co-processor: Intel Corporation 4xxx Series QAT (rev 20) Subsystem: Intel Corporation 4xxx Series QAT Kernel driver in use: 4xxx Kernel modules: qat_4xxx 8b:00.0 Co-processor: Intel Corporation 4xxx Series QAT (rev 20) Subsystem: Intel Corporation 4xxx Series QAT Kernel driver in use: 4xxx Kernel modules: qat_4xxx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2073525 Title: [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids Status in The Kobuk project: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Noble: Fix Committed Bug description: Public bug of https://bugs.launchpad.net/bugs/2073432 [ Impact ] The QAT kernel driver require those for For Sierra forest and Granite rapids hardware. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/qat_402xx.bin https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/qat_402xx_mmp.bin [ Test Plan ] cpa_sample_code supplied with qatlib and the Linux kernel can be run to validate the firmware. [ Where problems could occur ] QAT not working on those platform. [ Other Info ] * Requested by intel, compatible on kernel since 6.4, mantic doesn't apply as EOL. To manage notifications about this bug go to: https://bugs.launchpad.net/kobuk/+bug/2073525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Bug 2073525] Re: [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids
That is what i did for the validation of this issue: Release : 24.04 --- CPU --- Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 45 bits physical, 48 bits virtual Byte Order: Little Endian CPU(s): 288 On-line CPU(s) list:0-287 Vendor ID:GenuineIntel Model name: Intel(R) Xeon(R) 6780E linux-firmware: --- Installed: 20240318.git3b128b60-0ubuntu2.2 Candidate: 20240318.git3b128b60-0ubuntu2.2 Version table: *** 20240318.git3b128b60-0ubuntu2.2 500 500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 100 /var/lib/dpkg/status 20240318.git3b128b60-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages Boot dmesg: [ 16.503031] 4xxx :01:00.0: Direct firmware load for qat_402xx_mmp.bin failed with error -2 [ 16.503037] 4xxx :01:00.0: Failed to load MMP firmware qat_402xx_mmp.bin [ 16.505161] 4xxx :01:00.0: Resetting device qat_dev0 [ 16.752318] 4xxx :0b:00.0: Direct firmware load for qat_402xx_mmp.bin failed with error -2 [ 16.752323] 4xxx :0b:00.0: Failed to load MMP firmware qat_402xx_mmp.bin [ 16.754252] 4xxx :0b:00.0: Resetting device qat_dev0 [ 17.256825] 4xxx :81:00.0: Direct firmware load for qat_402xx_mmp.bin failed with error -2 [ 17.256837] 4xxx :81:00.0: Failed to load MMP firmware qat_402xx_mmp.bin [ 17.259506] 4xxx :81:00.0: Resetting device qat_dev0 [ 17.370148] 4xxx :8b:00.0: Direct firmware load for qat_402xx_mmp.bin failed with error -2 [ 17.370157] 4xxx :8b:00.0: Failed to load MMP firmware qat_402xx_mmp.bin [ 17.372417] 4xxx :8b:00.0: Resetting device qat_dev0 Install the package in proposed --- linux-firmware: --- Installed: 20240318.git3b128b60-0ubuntu2.3 Candidate: 20240318.git3b128b60-0ubuntu2.3 Version table: *** 20240318.git3b128b60-0ubuntu2.3 100 100 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages 100 /var/lib/dpkg/status 20240318.git3b128b60-0ubuntu2.2 500 500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 20240318.git3b128b60-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages Dmesg --- [ 17.288876] 4xxx :01:00.0: qat_dev0 started 9 acceleration engines [ 17.468869] 4xxx :0b:00.0: qat_dev1 started 9 acceleration engines [ 17.700878] 4xxx :81:00.0: qat_dev2 started 9 acceleration engines [ 17.878875] 4xxx :8b:00.0: qat_dev3 started 9 acceleration engines List of the PCI devices: --- ubuntu@cessna-726624:~$ lspci -d :4944 -k 01:00.0 Co-processor: Intel Corporation 4xxx Series QAT (rev 20) Subsystem: Intel Corporation 4xxx Series QAT Kernel driver in use: 4xxx Kernel modules: qat_4xxx 0b:00.0 Co-processor: Intel Corporation 4xxx Series QAT (rev 20) Subsystem: Intel Corporation 4xxx Series QAT Kernel driver in use: 4xxx Kernel modules: qat_4xxx 81:00.0 Co-processor: Intel Corporation 4xxx Series QAT (rev 20) Subsystem: Intel Corporation 4xxx Series QAT Kernel driver in use: 4xxx Kernel modules: qat_4xxx 8b:00.0 Co-processor: Intel Corporation 4xxx Series QAT (rev 20) Subsystem: Intel Corporation 4xxx Series QAT Kernel driver in use: 4xxx Kernel modules: qat_4xxx -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073525 Title: [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids To manage notifications about this bug go to: https://bugs.launchpad.net/kobuk/+bug/2073525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069821] Re: [VROC] [Ub 24.04] mdadm: buffer overflow detected
** Changed in: mdadm (Ubuntu Noble) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069821 Title: [VROC] [Ub 24.04] mdadm: buffer overflow detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2069821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070371] Re: [VROC] [Ub 24.04] mdadm: grow for R0 not start - missing patch
** Description changed: + [ Impact ] + + This bug prevents users from successfully reshaping/growing a RAID array + Indeed, at the reshaping operation, for external array, mdadm might miss + the mdmon daemon up and running event because mdadm only runs and check + if it is running without waiting. + + This fix introduces a timed_wait operation that allows mdadm to wait for + 5 seconds the mdmon running event and minimizes the risk of missing it. + + [ Test Plan ] + + Steps to reproduce: 1. Create RAID volume e.g.: # mdadm -C /dev/md/imsm0 -e imsm -n 2 /dev/nvme0n1 /dev/nvme1n1 -R # mdadm -C /dev/md/MyVolume -l0 -n 2 /dev/nvme[0-1]n1 -R 2. Add additional drive(s) to an IMSM array using command e.g.: # mdadm --add /dev/md/imsm0 /dev/nvme2n1 3. Execute grow command on array with additional drives: # mdadm --grow /dev/md/imsm0 --raid-devices=N 4. Wait for reshape start on given volume # cat /proc/mdstat Expected result: Reshape started successfully, no errors reported - Actual result: Reshape didn't start on given volume - It is already fixed in mdadm. Please add those patches to mdadm: + [ Where problems could occur ] + + The change only affects the Grow/Reshape operation of mdadm + and i do not expect problems to occur in other places. + + [ Other Info ] + + This fix has been already merged upstreamed: - https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=b0f4e8e30f38d83f7e3f53d01d72d4cb3b4d42d7 - https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=aa1cc5815d2b14a8b47add18cfaa8264e19c10ce + + The fix is in the second commit, the first commit is a dependency of the + second commit and it is only about a minor change in a function + signature. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070371 Title: [VROC] [Ub 24.04] mdadm: grow for R0 not start - missing patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2070371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077862] Re: adduser autopkgtests failed due to shadow 1:4.15.3-3ubuntu2 in 24.10 proposed
I run the ADT for adduser in 24.10 against the version 4.13+dfsg1-4ubuntu5 of shadow and also have the failure for the test : debian/tests/f/valid_username.t I assume that the ADT failure is not solely caused by the merge of new version for shadow, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077862 Title: adduser autopkgtests failed due to shadow 1:4.15.3-3ubuntu2 in 24.10 proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2077862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Touch-packages] [Bug 2077862] Re: adduser autopkgtests failed due to shadow 1:4.15.3-3ubuntu2 in 24.10 proposed
I run the ADT for adduser in 24.10 against the version 4.13+dfsg1-4ubuntu5 of shadow and also have the failure for the test : debian/tests/f/valid_username.t I assume that the ADT failure is not solely caused by the merge of new version for shadow, -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/2077862 Title: adduser autopkgtests failed due to shadow 1:4.15.3-3ubuntu2 in 24.10 proposed Status in adduser package in Ubuntu: New Status in shadow package in Ubuntu: New Bug description: ADT of adduser fails due to the merge of shadow on 24.10 to the version 1:4.15.3-3ubuntu2 in 24.10 Logs of the ADT : https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- oracular/oracular/amd64/a/adduser/20240814_214718_33c7b@/log.gz The failing tests: --- 650s Test Summary Report 650s --- 650s debian/tests/f/valid_username.t (Wstat: 5120 (exited 20) Tests: 669 Failed: 20) 650s Failed tests: 209-212, 214-217, 245-248, 250-253, 321-324 650s Non-zero exit status: 20 650s Files=20, Tests=2631, 142 wallclock secs ( 0.44 usr 0.11 sys + 79.95 cusr 41.69 csys = 122.19 CPU) 650s Result: FAIL Logs: --- 670s # Failed test 'command success: /usr/sbin/adduser --quiet --ingroup nogroup --system --disabled-password --home '/home/\}' --allow-all-names '\}'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '82' 670s # expected: '0' 670s 670s # Failed test 'user exists: \}' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 247. 670s # got: undef 670s # expected: anything else 670s 670s # Failed test 'path exists: /home/\}' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 176. 670s 670s # Failed test 'command success: /usr/sbin/deluser --quiet --remove-home '\}'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '12' 670s # expected: '0' 670s 670s # Failed test 'command success: /usr/sbin/adduser --quiet --ingroup nogroup --system --disabled-password --home '/home/\}' '\}'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '82' 670s # expected: '0' 670s 670s # Failed test 'user exists: \}' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 247. 670s # got: undef 670s # expected: anything else 670s 670s # Failed test 'path exists: /home/\}' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 176. 670s 670s # Failed test 'command success: /usr/sbin/deluser --quiet --remove-home '\}'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '12' 670s # expected: '0' 670s 670s # Failed test 'command success: /usr/sbin/adduser --quiet --ingroup nogroup --system --disabled-password --home '/home/DOMAIN\user' --allow-all-names 'DOMAIN\user'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '82' 670s # expected: '0' 670s 670s # Failed test 'user exists: DOMAIN\user' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 247. 670s # got: undef 670s # expected: anything else 670s 670s # Failed test 'path exists: /home/DOMAIN\user' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 176. 670s 670s # Failed test 'command success: /usr/sbin/deluser --quiet --remove-home 'DOMAIN\user'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '12' 670s # expected: '0' 670s 670s # Failed test 'command success: /usr/sbin/adduser --quiet --ingroup nogroup --system --disabled-password --home '/home/DOMAIN\user' 'DOMAIN\user'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '82' 670s # expected: '0' 670s 670s # Failed test 'user exists: DOMAIN\user' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 247. 670s # got: undef 670s # expected: anything else 670s 670s # Failed test 'path exists: /home/DOMAIN\user' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 176. 670s 670s # Failed test 'command success: /usr/sbin/deluser --quiet --remove-home 'DOMAIN\user'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '12' 670s # expected: '0' 670s 670s # Failed test 'command success: /usr/sbin/adduser --quiet --ingroup nogroup --system --disabled-password --home "/home/'c4\$h\\M0n3y\"'==>@" --allow-all-names "'c4\$h\\M0n3y\"'==>@"' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '82' 670s # expected: '0' 670s 670s # Failed test 'user exists: 'c4$h\M0n3y"'==>@' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 247. 670s #
[Bug 2077862] Re: adduser autopkgtests failed due to shadow 1:4.15.3-3ubuntu2 in 24.10 proposed
** Description changed: - ADT of adduser fails due to the merge of shadow to the version + ADT of adduser fails due to the merge of shadow on 24.10 to the version 1:4.15.3-3ubuntu2 in 24.10 Logs of the ADT : https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- oracular/oracular/amd64/a/adduser/20240814_214718_33c7b@/log.gz The failing tests: - - debian/tests/f/valid_username.t + --- + + 650s Test Summary Report + 650s --- + 650s debian/tests/f/valid_username.t (Wstat: 5120 (exited 20) Tests: 669 Failed: 20) + 650s Failed tests: 209-212, 214-217, 245-248, 250-253, 321-324 + 650s Non-zero exit status: 20 + 650s Files=20, Tests=2631, 142 wallclock secs ( 0.44 usr 0.11 sys + 79.95 cusr 41.69 csys = 122.19 CPU) + 650s Result: FAIL Logs: + --- 670s # Failed test 'command success: /usr/sbin/adduser --quiet --ingroup nogroup --system --disabled-password --home '/home/\}' --allow-all-names '\}'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '82' 670s # expected: '0' 670s 670s # Failed test 'user exists: \}' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 247. 670s # got: undef 670s # expected: anything else 670s 670s # Failed test 'path exists: /home/\}' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 176. 670s 670s # Failed test 'command success: /usr/sbin/deluser --quiet --remove-home '\}'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '12' 670s # expected: '0' 670s 670s # Failed test 'command success: /usr/sbin/adduser --quiet --ingroup nogroup --system --disabled-password --home '/home/\}' '\}'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '82' 670s # expected: '0' 670s 670s # Failed test 'user exists: \}' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 247. 670s # got: undef 670s # expected: anything else 670s 670s # Failed test 'path exists: /home/\}' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 176. 670s 670s # Failed test 'command success: /usr/sbin/deluser --quiet --remove-home '\}'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '12' 670s # expected: '0' 670s 670s # Failed test 'command success: /usr/sbin/adduser --quiet --ingroup nogroup --system --disabled-password --home '/home/DOMAIN\user' --allow-all-names 'DOMAIN\user'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '82' 670s # expected: '0' 670s 670s # Failed test 'user exists: DOMAIN\user' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 247. 670s # got: undef 670s # expected: anything else 670s 670s # Failed test 'path exists: /home/DOMAIN\user' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 176. 670s 670s # Failed test 'command success: /usr/sbin/deluser --quiet --remove-home 'DOMAIN\user'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '12' 670s # expected: '0' 670s 670s # Failed test 'command success: /usr/sbin/adduser --quiet --ingroup nogroup --system --disabled-password --home '/home/DOMAIN\user' 'DOMAIN\user'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '82' 670s # expected: '0' 670s 670s # Failed test 'user exists: DOMAIN\user' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 247. 670s # got: undef 670s # expected: anything else 670s 670s # Failed test 'path exists: /home/DOMAIN\user' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 176. 670s 670s # Failed test 'command success: /usr/sbin/deluser --quiet --remove-home 'DOMAIN\user'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '12' 670s # expected: '0' 670s 670s # Failed test 'command success: /usr/sbin/adduser --quiet --ingroup nogroup --system --disabled-password --home "/home/'c4\$h\\M0n3y\"'==>@" --allow-all-names "'c4\$h\\M0n3y\"'==>@"' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '82' 670s # expected: '0' 670s 670s # Failed test 'user exists: 'c4$h\M0n3y"'==>@' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 247. 670s # got: undef 670s # expected: anything else 670s 670s # Failed test 'path exists: /home/'c4$h\M0n3y"'==>@' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 176. 670s 670s # Failed test 'command success: /usr/sbin/deluser --quiet --remove-home "'c4\$h\\M0n3y\"'==>@"' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '12' 670s # expected: '0' 670s # Looks like you failed 20 tests of 669. -- You received this
[Touch-packages] [Bug 2077862] Re: adduser autopkgtests failed due to shadow 1:4.15.3-3ubuntu2 in 24.10 proposed
** Description changed: - ADT of adduser fails due to the merge of shadow to the version + ADT of adduser fails due to the merge of shadow on 24.10 to the version 1:4.15.3-3ubuntu2 in 24.10 Logs of the ADT : https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- oracular/oracular/amd64/a/adduser/20240814_214718_33c7b@/log.gz The failing tests: - - debian/tests/f/valid_username.t + --- + + 650s Test Summary Report + 650s --- + 650s debian/tests/f/valid_username.t (Wstat: 5120 (exited 20) Tests: 669 Failed: 20) + 650s Failed tests: 209-212, 214-217, 245-248, 250-253, 321-324 + 650s Non-zero exit status: 20 + 650s Files=20, Tests=2631, 142 wallclock secs ( 0.44 usr 0.11 sys + 79.95 cusr 41.69 csys = 122.19 CPU) + 650s Result: FAIL Logs: + --- 670s # Failed test 'command success: /usr/sbin/adduser --quiet --ingroup nogroup --system --disabled-password --home '/home/\}' --allow-all-names '\}'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '82' 670s # expected: '0' 670s 670s # Failed test 'user exists: \}' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 247. 670s # got: undef 670s # expected: anything else 670s 670s # Failed test 'path exists: /home/\}' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 176. 670s 670s # Failed test 'command success: /usr/sbin/deluser --quiet --remove-home '\}'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '12' 670s # expected: '0' 670s 670s # Failed test 'command success: /usr/sbin/adduser --quiet --ingroup nogroup --system --disabled-password --home '/home/\}' '\}'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '82' 670s # expected: '0' 670s 670s # Failed test 'user exists: \}' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 247. 670s # got: undef 670s # expected: anything else 670s 670s # Failed test 'path exists: /home/\}' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 176. 670s 670s # Failed test 'command success: /usr/sbin/deluser --quiet --remove-home '\}'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '12' 670s # expected: '0' 670s 670s # Failed test 'command success: /usr/sbin/adduser --quiet --ingroup nogroup --system --disabled-password --home '/home/DOMAIN\user' --allow-all-names 'DOMAIN\user'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '82' 670s # expected: '0' 670s 670s # Failed test 'user exists: DOMAIN\user' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 247. 670s # got: undef 670s # expected: anything else 670s 670s # Failed test 'path exists: /home/DOMAIN\user' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 176. 670s 670s # Failed test 'command success: /usr/sbin/deluser --quiet --remove-home 'DOMAIN\user'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '12' 670s # expected: '0' 670s 670s # Failed test 'command success: /usr/sbin/adduser --quiet --ingroup nogroup --system --disabled-password --home '/home/DOMAIN\user' 'DOMAIN\user'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '82' 670s # expected: '0' 670s 670s # Failed test 'user exists: DOMAIN\user' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 247. 670s # got: undef 670s # expected: anything else 670s 670s # Failed test 'path exists: /home/DOMAIN\user' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 176. 670s 670s # Failed test 'command success: /usr/sbin/deluser --quiet --remove-home 'DOMAIN\user'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '12' 670s # expected: '0' 670s 670s # Failed test 'command success: /usr/sbin/adduser --quiet --ingroup nogroup --system --disabled-password --home "/home/'c4\$h\\M0n3y\"'==>@" --allow-all-names "'c4\$h\\M0n3y\"'==>@"' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '82' 670s # expected: '0' 670s 670s # Failed test 'user exists: 'c4$h\M0n3y"'==>@' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 247. 670s # got: undef 670s # expected: anything else 670s 670s # Failed test 'path exists: /home/'c4$h\M0n3y"'==>@' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 176. 670s 670s # Failed test 'command success: /usr/sbin/deluser --quiet --remove-home "'c4\$h\\M0n3y\"'==>@"' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '12' 670s # expected: '0' 670s # Looks like you failed 20 tests of 669. -- You received this
[Touch-packages] [Bug 2077862] [NEW] adduser autopkgtests failed due to shadow 1:4.15.3-3ubuntu2 in 24.10 proposed
Public bug reported: ADT of adduser fails due to the merge of shadow to the version 1:4.15.3-3ubuntu2 in 24.10 Logs of the ADT : https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- oracular/oracular/amd64/a/adduser/20240814_214718_33c7b@/log.gz The failing tests: - debian/tests/f/valid_username.t Logs: 670s # Failed test 'command success: /usr/sbin/adduser --quiet --ingroup nogroup --system --disabled-password --home '/home/\}' --allow-all-names '\}'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '82' 670s # expected: '0' 670s 670s # Failed test 'user exists: \}' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 247. 670s # got: undef 670s # expected: anything else 670s 670s # Failed test 'path exists: /home/\}' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 176. 670s 670s # Failed test 'command success: /usr/sbin/deluser --quiet --remove-home '\}'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '12' 670s # expected: '0' 670s 670s # Failed test 'command success: /usr/sbin/adduser --quiet --ingroup nogroup --system --disabled-password --home '/home/\}' '\}'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '82' 670s # expected: '0' 670s 670s # Failed test 'user exists: \}' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 247. 670s # got: undef 670s # expected: anything else 670s 670s # Failed test 'path exists: /home/\}' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 176. 670s 670s # Failed test 'command success: /usr/sbin/deluser --quiet --remove-home '\}'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '12' 670s # expected: '0' 670s 670s # Failed test 'command success: /usr/sbin/adduser --quiet --ingroup nogroup --system --disabled-password --home '/home/DOMAIN\user' --allow-all-names 'DOMAIN\user'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '82' 670s # expected: '0' 670s 670s # Failed test 'user exists: DOMAIN\user' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 247. 670s # got: undef 670s # expected: anything else 670s 670s # Failed test 'path exists: /home/DOMAIN\user' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 176. 670s 670s # Failed test 'command success: /usr/sbin/deluser --quiet --remove-home 'DOMAIN\user'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '12' 670s # expected: '0' 670s 670s # Failed test 'command success: /usr/sbin/adduser --quiet --ingroup nogroup --system --disabled-password --home '/home/DOMAIN\user' 'DOMAIN\user'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '82' 670s # expected: '0' 670s 670s # Failed test 'user exists: DOMAIN\user' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 247. 670s # got: undef 670s # expected: anything else 670s 670s # Failed test 'path exists: /home/DOMAIN\user' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 176. 670s 670s # Failed test 'command success: /usr/sbin/deluser --quiet --remove-home 'DOMAIN\user'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '12' 670s # expected: '0' 670s 670s # Failed test 'command success: /usr/sbin/adduser --quiet --ingroup nogroup --system --disabled-password --home "/home/'c4\$h\\M0n3y\"'==>@" --allow-all-names "'c4\$h\\M0n3y\"'==>@"' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '82' 670s # expected: '0' 670s 670s # Failed test 'user exists: 'c4$h\M0n3y"'==>@' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 247. 670s # got: undef 670s # expected: anything else 670s 670s # Failed test 'path exists: /home/'c4$h\M0n3y"'==>@' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 176. 670s 670s # Failed test 'command success: /usr/sbin/deluser --quiet --remove-home "'c4\$h\\M0n3y\"'==>@"' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '12' 670s # expected: '0' 670s # Looks like you failed 20 tests of 669. ** Affects: adduser (Ubuntu) Importance: Undecided Status: New ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Also affects: adduser (Ubuntu) Importance: Undecided Status: New ** Description changed: - ADT of adduser fails due to the merge of shadow on 24.10 to the version + ADT of adduser fails due to the merge of shadow to the version 1:4.15.3-3ubuntu2 in 24.10 Logs of the ADT : https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- oracular/oracular/amd64/a/adduser/20240814_214718_33c7b@/log.gz The failing tests: - debian/tests/f/valid_username.t Logs:
[Bug 2077862] [NEW] adduser autopkgtests failed due to shadow 1:4.15.3-3ubuntu2 in 24.10 proposed
Public bug reported: ADT of adduser fails due to the merge of shadow to the version 1:4.15.3-3ubuntu2 in 24.10 Logs of the ADT : https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- oracular/oracular/amd64/a/adduser/20240814_214718_33c7b@/log.gz The failing tests: - debian/tests/f/valid_username.t Logs: 670s # Failed test 'command success: /usr/sbin/adduser --quiet --ingroup nogroup --system --disabled-password --home '/home/\}' --allow-all-names '\}'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '82' 670s # expected: '0' 670s 670s # Failed test 'user exists: \}' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 247. 670s # got: undef 670s # expected: anything else 670s 670s # Failed test 'path exists: /home/\}' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 176. 670s 670s # Failed test 'command success: /usr/sbin/deluser --quiet --remove-home '\}'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '12' 670s # expected: '0' 670s 670s # Failed test 'command success: /usr/sbin/adduser --quiet --ingroup nogroup --system --disabled-password --home '/home/\}' '\}'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '82' 670s # expected: '0' 670s 670s # Failed test 'user exists: \}' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 247. 670s # got: undef 670s # expected: anything else 670s 670s # Failed test 'path exists: /home/\}' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 176. 670s 670s # Failed test 'command success: /usr/sbin/deluser --quiet --remove-home '\}'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '12' 670s # expected: '0' 670s 670s # Failed test 'command success: /usr/sbin/adduser --quiet --ingroup nogroup --system --disabled-password --home '/home/DOMAIN\user' --allow-all-names 'DOMAIN\user'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '82' 670s # expected: '0' 670s 670s # Failed test 'user exists: DOMAIN\user' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 247. 670s # got: undef 670s # expected: anything else 670s 670s # Failed test 'path exists: /home/DOMAIN\user' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 176. 670s 670s # Failed test 'command success: /usr/sbin/deluser --quiet --remove-home 'DOMAIN\user'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '12' 670s # expected: '0' 670s 670s # Failed test 'command success: /usr/sbin/adduser --quiet --ingroup nogroup --system --disabled-password --home '/home/DOMAIN\user' 'DOMAIN\user'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '82' 670s # expected: '0' 670s 670s # Failed test 'user exists: DOMAIN\user' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 247. 670s # got: undef 670s # expected: anything else 670s 670s # Failed test 'path exists: /home/DOMAIN\user' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 176. 670s 670s # Failed test 'command success: /usr/sbin/deluser --quiet --remove-home 'DOMAIN\user'' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '12' 670s # expected: '0' 670s 670s # Failed test 'command success: /usr/sbin/adduser --quiet --ingroup nogroup --system --disabled-password --home "/home/'c4\$h\\M0n3y\"'==>@" --allow-all-names "'c4\$h\\M0n3y\"'==>@"' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '82' 670s # expected: '0' 670s 670s # Failed test 'user exists: 'c4$h\M0n3y"'==>@' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 247. 670s # got: undef 670s # expected: anything else 670s 670s # Failed test 'path exists: /home/'c4$h\M0n3y"'==>@' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 176. 670s 670s # Failed test 'command success: /usr/sbin/deluser --quiet --remove-home "'c4\$h\\M0n3y\"'==>@"' 670s # at debian/tests/lib/AdduserTestsCommon.pm line 50. 670s # got: '12' 670s # expected: '0' 670s # Looks like you failed 20 tests of 669. ** Affects: adduser (Ubuntu) Importance: Undecided Status: New ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Also affects: adduser (Ubuntu) Importance: Undecided Status: New ** Description changed: - ADT of adduser fails due to the merge of shadow on 24.10 to the version + ADT of adduser fails due to the merge of shadow to the version 1:4.15.3-3ubuntu2 in 24.10 Logs of the ADT : https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- oracular/oracular/amd64/a/adduser/20240814_214718_33c7b@/log.gz The failing tests: - debian/tests/f/valid_username.t Logs:
[Kernel-packages] [Bug 2073525] Re: [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids
** Also affects: kobuk Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2073525 Title: [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids Status in The Kobuk project: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Confirmed Status in linux-firmware source package in Noble: Confirmed Bug description: Public bug of https://bugs.launchpad.net/bugs/2073432 [ Impact ] The QAT kernel driver require those for For Sierra forest and Granite rapids hardware. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/qat_402xx.bin https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/qat_402xx_mmp.bin [ Test Plan ] cpa_sample_code supplied with qatlib and the Linux kernel can be run to validate the firmware. [ Where problems could occur ] QAT not working on those platform. [ Other Info ] * Requested by intel, compatible on kernel since 6.4, mantic doesn't apply as EOL. To manage notifications about this bug go to: https://bugs.launchpad.net/kobuk/+bug/2073525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Bug 2073525] Re: [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids
** Also affects: kobuk Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073525 Title: [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids To manage notifications about this bug go to: https://bugs.launchpad.net/kobuk/+bug/2073525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069821] Re: [VROC] [Ub 24.04] mdadm: buffer overflow detected
@bktan1 : this feedback is mostly applied to Noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069821 Title: [VROC] [Ub 24.04] mdadm: buffer overflow detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2069821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069821] Re: [VROC] [Ub 24.04] mdadm: buffer overflow detected
** Changed in: mdadm (Ubuntu Noble) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069821 Title: [VROC] [Ub 24.04] mdadm: buffer overflow detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2069821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076898] Re: Numeric name is accepted as valid username for useradd/groupadd
A fix is uploaded at: https://launchpad.net/~hectorcao/+archive/ubuntu/lp2076898 The MR : https://code.launchpad.net/~hectorcao/ubuntu/+source/shadow/+git/shadow/+merge/471145 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076898 Title: Numeric name is accepted as valid username for useradd/groupadd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2076898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Touch-packages] [Bug 2076898] Re: Numeric name is accepted as valid username for useradd/groupadd
A fix is uploaded at: https://launchpad.net/~hectorcao/+archive/ubuntu/lp2076898 The MR : https://code.launchpad.net/~hectorcao/ubuntu/+source/shadow/+git/shadow/+merge/471145 -- 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/2076898 Title: Numeric name is accepted as valid username for useradd/groupadd Status in shadow package in Ubuntu: In Progress Bug description: Pure numeric names (example 0, 100) should be considered as invalid group and user names The command useradd and groupadd must refuse them This is not the case in the latest version of shadow : 1:4.15.3-3ubuntu1 When we issue: $ useradd 0 The command succeeds instead of failing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2076898/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2076898] Re: Numeric name is accepted as valid username for useradd/groupadd
the bug is a regression introduced when we merge the debian version 1:4.15.3-3 as part of LP issue https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2073338 at this merge, we dropped the patch 506_relaxed_usernames.patch thinking that the patch has been integrated in debian but this patch is actually a modified version of the original patch in Debian to disallow purely numeric user/group names we must keep this behavior that is Ubuntu-only -- 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/2076898 Title: Numeric name is accepted as valid username for useradd/groupadd Status in shadow package in Ubuntu: In Progress Bug description: Pure numeric names (example 0, 100) should be considered as invalid group and user names The command useradd and groupadd must refuse them This is not the case in the latest version of shadow : 1:4.15.3-3ubuntu1 When we issue: $ useradd 0 The command succeeds instead of failing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2076898/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Bug 2076898] Re: Numeric name is accepted as valid username for useradd/groupadd
the bug is a regression introduced when we merge the debian version 1:4.15.3-3 as part of LP issue https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2073338 at this merge, we dropped the patch 506_relaxed_usernames.patch thinking that the patch has been integrated in debian but this patch is actually a modified version of the original patch in Debian to disallow purely numeric user/group names we must keep this behavior that is Ubuntu-only -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076898 Title: Numeric name is accepted as valid username for useradd/groupadd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2076898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Touch-packages] [Bug 2076898] [NEW] Numeric name is accepted as valid username for useradd/groupadd
Public bug reported: Pure numeric names (example 0, 100) should be considered as invalid group and user names The command useradd and groupadd must refuse them This is not the case in the latest version of shadow : 1:4.15.3-3ubuntu1 When we issue: $ useradd 0 The command succeeds instead of failing. ** Affects: shadow (Ubuntu) Importance: Undecided Assignee: Hector CAO (hectorcao) Status: In Progress ** Changed in: shadow (Ubuntu) Status: New => In Progress ** Changed in: shadow (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) -- 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/2076898 Title: Numeric name is accepted as valid username for useradd/groupadd Status in shadow package in Ubuntu: In Progress Bug description: Pure numeric names (example 0, 100) should be considered as invalid group and user names The command useradd and groupadd must refuse them This is not the case in the latest version of shadow : 1:4.15.3-3ubuntu1 When we issue: $ useradd 0 The command succeeds instead of failing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2076898/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Bug 2076898] [NEW] Numeric name is accepted as valid username for useradd/groupadd
Public bug reported: Pure numeric names (example 0, 100) should be considered as invalid group and user names The command useradd and groupadd must refuse them This is not the case in the latest version of shadow : 1:4.15.3-3ubuntu1 When we issue: $ useradd 0 The command succeeds instead of failing. ** Affects: shadow (Ubuntu) Importance: Undecided Assignee: Hector CAO (hectorcao) Status: In Progress ** Changed in: shadow (Ubuntu) Status: New => In Progress ** Changed in: shadow (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076898 Title: Numeric name is accepted as valid username for useradd/groupadd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2076898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 2073525] Re: [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids
** Changed in: linux-firmware (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2073525 Title: [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Noble: New Bug description: Public bug of https://bugs.launchpad.net/bugs/2073432 [ Impact ] The QAT kernel driver require those for For Sierra forest and Granite rapids hardware. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/qat_402xx.bin https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/qat_402xx_mmp.bin [ Test Plan ] cpa_sample_code supplied with qatlib and the Linux kernel can be run to validate the firmware. [ Where problems could occur ] QAT not working on those platform. [ Other Info ] * Requested by intel, compatible on kernel since 6.4, mantic doesn't apply as EOL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2073525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Bug 2073525] Re: [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids
** Changed in: linux-firmware (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073525 Title: [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2073525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076403] Re: Please merge mdadm 4.3+20240723-2 into Oracular
** Changed in: mdadm (Ubuntu) Status: New => In Progress ** Changed in: mdadm (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076403 Title: Please merge mdadm 4.3+20240723-2 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2076403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076403] Re: Please merge mdadm 4.3+20240723-2 into Oracular
With this merge, these Ubuntu patches are dropped: - d/p/lp2069821/: mdadm: buffer overflow detected (LP #2069821) This patch has been integrated in mdadm upstream - d/p/lp2070371/: mdadm: wait for mdmon when it is started via systemd (LP #2070371) This patch has been integrated in mdadm upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076403 Title: Please merge mdadm 4.3+20240723-2 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2076403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076403] [NEW] Please merge mdadm 4.3+20240723-2 into Oracular
Public bug reported: A new version 4.3+20240723-2 has been released in Debian Testing Please merge it into Oracular since we are close to feature freeze ** Affects: mdadm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076403 Title: Please merge mdadm 4.3+20240723-2 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2076403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070371] Re: [VROC] [Ub 24.04] mdadm: grow for R0 not start - missing patch
** Changed in: mdadm (Ubuntu Noble) Status: New => In Progress ** Changed in: mdadm (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070371 Title: [VROC] [Ub 24.04] mdadm: grow for R0 not start - missing patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2070371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069821] Re: [VROC] [Ub 24.04] mdadm: buffer overflow detected
** Changed in: mdadm (Ubuntu Noble) Status: New => In Progress ** Changed in: mdadm (Ubuntu Noble) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069821 Title: [VROC] [Ub 24.04] mdadm: buffer overflow detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2069821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070371] Re: [VROC] [Ub 24.04] mdadm: grow for R0 not start - missing patch
@ktanska : Thanks, do you mind telling on which Ubuntu release you tested the fix ? Noble 24.04 ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070371 Title: [VROC] [Ub 24.04] mdadm: grow for R0 not start - missing patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2070371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075496] Re: Bump version to new upstream release 2021.12.1
** No longer affects: kobuk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075496 Title: Bump version to new upstream release 2021.12.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipp-crypto/+bug/2075496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075498] Re: Bump version to new upstream release 1.6.1
MR : https://code.launchpad.net/~hectorcao/ubuntu/+source/qatengine/+git/qatengine/+merge/470472 Upstream changes --- Refactor QAT_HW & QAT_SW RSA code with bug fixes - 85fa710 Bug Fixes, README update and Version bump to v1.6.0 - ba2035c Fix issue with make depend for QAT_SW - 4cf7a99 QAT_HW GCM Memleak fix & bug fixes - c59b117 QAT2.0 FreeBSD14 intree driver support - 9150b9a Fix OpenSSL 3.2 compatibility issues - e26bd77 Optimize hex dump logging - f65ec52 Clear job tlv on error - e6dc386 QAT_HW RSA Encrypt and Decrypt provider support - 782cff3 QAT_HW AES-CCM Provider support - a95d1a0 Add ECDH keymgmt support for provider - a8dd7d1 Fix QAT_HW SM2 memory leak - 1061d9f Enable qaeMemFreeNonZeroNUMA() for qatlib - 388800e Fix polling issue for the process that doesn't have QAT_HW instance - 3a1fca3 Fix SHA3 qctx initialization issue & potential memleak - b5df752 Fix compilation error in SM2 with qat_contig_mem - 65c5fba Update year in copyright information to 2024 - 9be30e0 The upstream diff is mostly bugfixes and small refactoring. Nothing relevant from the packaging standpoint Build --- A build of the package is available at: https://launchpad.net/~hectorcao/+archive/ubuntu/ubuntu-contrib/+packages Tests --- Package installation and upgrade path have been tested successfully on Oracular ** Tags added: pe-sponsoring-request ubuntu-sponsors ** No longer affects: kobuk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075498 Title: Bump version to new upstream release 1.6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qatengine/+bug/2075498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075498] [NEW] Bump version to new upstream release 1.6.1
Public bug reported: A new upstream version is available : https://github.com/intel/QAT_Engine/releases/tag/v1.6.1 We would like to have this version in Oracular Oriole 24.10 ** Affects: kobuk Importance: Undecided Assignee: Hector CAO (hectorcao) Status: In Progress ** Affects: qatengine (Ubuntu) Importance: Undecided Assignee: Hector CAO (hectorcao) Status: In Progress ** Changed in: qatengine (Ubuntu) Status: New => In Progress ** Changed in: qatengine (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) ** Also affects: kobuk Importance: Undecided Status: New ** Changed in: kobuk Status: New => In Progress ** Changed in: kobuk Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075498 Title: Bump version to new upstream release 1.6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kobuk/+bug/2075498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075496] Re: Bump version to new upstream release 2021.12.1
MR: https://code.launchpad.net/~hectorcao/ubuntu/+source/ipp- crypto/+git/ipp-crypto/+merge/470442 Upstream Changes --- Here is the upstream changelog from the previous version (2021.10.0) - Added FIPS_CUSTOM_IPPCP_API_HEADER build flag to support FIPS self-tests for a specific use case when Custom Library Tool is used with custom prefix for IPPCP API. - Added single-buffer implementation of Leighton-Micali Hash-Based Signatures(LMS) algorithm, verification part. - Added support of Clang 16.0 compiler for Linux. - Added examples of AES-GCM Encryption/Decryption usage. - AES-GCM algorithm with Intel® Advanced Vector Extensions 2 (Intel® AVX2) vector extensions of Intel® AES New Instructions (Intel® AES-NI) was optimized. - Minimal supported BoringSSL version was increased to 45cf810d tag. I did take a look at the upstream diff and did not see anything relevant for the packaging perspective. Test build --- The new package is built successfully and available for testing at: https://launchpad.net/~hectorcao/+archive/ubuntu/ubuntu-contrib/+packages Tests --- I have validated that the package can be installed successfully. I also verified that we can do successful upgrade from the current version. ** Also affects: kobuk Importance: Undecided Status: New ** Changed in: kobuk Status: New => In Progress ** Changed in: kobuk Assignee: (unassigned) => Hector CAO (hectorcao) ** Tags added: ubuntu-sponsors ** Tags added: pe-sponsoring-request -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075496 Title: Bump version to new upstream release 2021.12.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kobuk/+bug/2075496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075496] [NEW] Bump version to new upstream release 2021.12.1
Public bug reported: New upstream version is available at : https://github.com/intel/ipp- crypto/releases/tag/ippcp_2021.12.1 We would like to have this version for Oracular Oriole 24.10 ** Affects: ipp-crypto (Ubuntu) Importance: Undecided Assignee: Hector CAO (hectorcao) Status: In Progress ** Changed in: ipp-crypto (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) ** Changed in: ipp-crypto (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075496 Title: Bump version to new upstream release 2021.12.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipp-crypto/+bug/2075496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070371] Re: [VROC] [Ub 24.04] mdadm: grow for R0 not start - missing patch
Hello @ktanska and affected users, A test package with the fix is available in this PPA: https://launchpad.net/~hectorcao/+archive/ubuntu/2069821/ Could you help on confirming the fix ? Thanks, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070371 Title: [VROC] [Ub 24.04] mdadm: grow for R0 not start - missing patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2070371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069821] Re: [VROC] [Ub 24.04] mdadm: buffer overflow detected
Hello @ktanska and affected users, A test package with the fix is available in this PPA: https://launchpad.net/~hectorcao/+archive/ubuntu/2069821/ Could you help on confirming the fix ? Thanks, ** Description changed: - Mdadm throws buffer-overflow sometimes, it depends on the building environment. - It happens when mdadm is built with FORFTIFY_SOURCE=3 (as it is done in Ubuntu 24.04). + [ Impact ] - Buffer-overflow is detected for many commands in this case: + mdadm crashes sporadically with error *** buffer overflow detected *** + at some invokations: + - mdadm --detail-pl - mdadm -CR /dev/md0 -l1 -n2 /dev/nvme0n1 /dev/nvme1n1 *** buffer overflow detected ***: terminated Aborted (core dumped) - It is fixed in mdadm upstream - please apply this patch to mdadm package and rebuilt it. + [ Test Plan ] + + - Install mdadm + - Have 2 disks to create a RAID devices + - Issue this command several times: + + + [ Where problems could occur ] + + The fix is very small and basically it replaces the unsafe functions call + to sprintf by calling snprintf for Intel platforms (platform_intel.c) + I do not expect high regression risk. + + [ Other Info ] + + mdadm is built with FORTIFY_SOURCE=3 (as it is done in Ubuntu 24.04). + and it uses the unsafe function sprintf() that will cause the + buffer-overflow error + + + It is fixed in mdadm upstream: https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=827e1870f320545796d907f50af594e901399417 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069821 Title: [VROC] [Ub 24.04] mdadm: buffer overflow detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2069821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069821] Re: [VROC] [Ub 24.04] mdadm: buffer overflow detected
** Changed in: mdadm (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069821 Title: [VROC] [Ub 24.04] mdadm: buffer overflow detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2069821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070371] Re: [VROC] [Ub 24.04] mdadm: grow for R0 not start - missing patch
** Changed in: mdadm (Ubuntu Noble) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070371 Title: [VROC] [Ub 24.04] mdadm: grow for R0 not start - missing patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2070371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070371] Re: [VROC] [Ub 24.04] mdadm: grow for R0 not start - missing patch
** Changed in: mdadm (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070371 Title: [VROC] [Ub 24.04] mdadm: grow for R0 not start - missing patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2070371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069821] Re: [VROC] [Ub 24.04] mdadm: buffer overflow detected
** Changed in: mdadm (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069821 Title: [VROC] [Ub 24.04] mdadm: buffer overflow detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2069821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073338] Re: Please merge shadow 1:4.15.3-2 into Oracular
Delta conflicts resolution --- 1) login.defs file Up to the current version, debian ships the /etc/login.defs file from debian/login.defs file Ubuntu has some direct modifications on it d/login.defs: Enable private home directories by default debian/login.defs: Update documentation of USERGROUPS_ENAB/UMASK In the new version, debian ships the file from upstream source (etc/logins.defs) Debian applies the changes on the files through debian patches Ubuntu will have to do the same. However, several points that are worth to be mentioned: The patch debian/login.defs: Update documentation of USERGROUPS_ENAB/UMASK can be dropped because upstream integrated the change For the patch d/login.defs: Enable private home directories by default Up to the current version, Debian lets the HOME_MODE variable commented and Ubuntu sets the variable to 0750 as part of the patch: d/login.defs: Enable private home directories by default but in the new version, Debian does not let the variable commented anymore and sets the variable value to 0700; to keep the current Ubuntu behavior I created a patch to set the variable value to 0750 2) The patch Fix ftbfs with -Werror=implicit-function-declaration can be dropped because the package can be built successfully without it 3) Several current patches (extrausers) have to be updated due to conflict resolution: 1010_extrausers.patch Minor conflict resolution in defines.h since it is heavily modified in the new version 1015_add_zsys_support.patch Minor conflict resolution in src/useradd.c; in the function create_home 1011_extrausers_toggle.patch Minor conflict resolution in defines.h since it is heavily modified in the new version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073338 Title: Please merge shadow 1:4.15.3-2 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2073338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073338] [NEW] Please merge shadow 1:4.15.3-2 into Oracular
Public bug reported: Current debian version in Oracular: 1:4.13+dfsg1 (upstream version 4.13) New version 1:4.15.3-2 has been released in Debian unstable (upstream version 4.15) 4.15 is the current supported stable version of upstream ** Affects: shadow (Ubuntu) Importance: Undecided Assignee: Hector CAO (hectorcao) Status: In Progress ** Changed in: shadow (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) ** Changed in: shadow (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073338 Title: Please merge shadow 1:4.15.3-2 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2073338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Tags removed: verification-needed verification-needed-jammy verification-needed-mantic ** Tags added: verification-done verification-done-mantic ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
Hi, The package in proposed is tested successfully on mantic ! Hardware: --- ubuntu@dell-g15-5520-c29798:~$ inxi -G Graphics: Device-1: Intel Alder Lake-P Integrated Graphics driver: i915 v: kernel Device-2: NVIDIA GA107BM [GeForce RTX 3050 Mobile] driver: nouveau v: kernel Device-3: Microdia Integrated_Webcam_HD driver: uvcvideo type: USB Display: server: X.org v: 1.21.1.7 with: Xwayland v: 23.2.0 driver: gpu: i915 tty: 221x55 resolution: 1920x1080 Mantic package version: 1.27.1-1 I can reproduce the bug by resizing/reducing the terminal window I installed the proposed version : 1.27.1-1ubuntu0.1 I cannot reproduce the bug while using the same manipulations on the terminal window. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
Hi, The package in proposed is tested successfully on jammy ! Hardware: --- ubuntu@ubuntu:~$ inxi -G Graphics: Device-1: Intel driver: i915 v: kernel Device-2: NVIDIA driver: nvidia v: 515.86.01 Device-3: Microdia Integrated_Webcam_FHD type: USB driver: uvcvideo Display: server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.1 driver: X: loaded: modesetting,nvidia unloaded: fbdev,nouveau,vesa gpu: i915 tty: 188x46 resolution: 1920x1080 Jammy package version: 1.26-2 I can reproduce the bug by resizing/reducing the terminal window I installed the proposed version : 1.26-2ubuntu0.1 I cannot reproduce the bug while using the same manipulations on the terminal window. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069232] Re: Missing measurements on confidential computing platforms (Intel TDX)
@mkukri and @juliank Thanks so much for the feedback and work Now, i would like to ask if we can consider to SRU it to 24.04 because we are having CC story for 24.04 with our Kobuk project -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069232 Title: Missing measurements on confidential computing platforms (Intel TDX) To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/2069232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069232] [NEW] Missing measurements on confidential computing platforms (Intel TDX)
Public bug reported: When we run a Confidential VM with grub bootlodaer on Intel TDX platform, the module tpm is not loaded and boot measurements are not done for the guest VM. This bug will prevent grub of doing measurements on confidential computing platform (the bug has been confirmed on Intel TDX). This lack of measurements will break the remote attestation See upstream bug : https://savannah.gnu.org/bugs/?65821 Upstream fix : https://git.savannah.gnu.org/cgit/grub.git/commit/?id=86df79275d065d87f4de5c97e456973e8b4a649c ** Affects: grub Importance: Unknown Status: Unknown ** Affects: kobuk Importance: Medium Assignee: Hector CAO (hectorcao) Status: Confirmed ** Affects: grub2 (Ubuntu) Importance: Undecided Assignee: Hector CAO (hectorcao) Status: Confirmed ** Changed in: grub2 (Ubuntu) Status: New => Confirmed ** Changed in: grub2 (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) ** Bug watch added: GNU Savannah Bug Tracker #65821 http://savannah.gnu.org/bugs/?65821 ** Also affects: grub via http://savannah.gnu.org/bugs/?65821 Importance: Unknown Status: Unknown ** Also affects: kobuk Importance: Undecided Status: New ** Changed in: kobuk Status: New => Confirmed ** Changed in: kobuk Importance: Undecided => Medium ** Changed in: kobuk Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069232 Title: Missing measurements on confidential computing platforms (Intel TDX) To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/2069232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068627] Re: IMA Hashes keep changing on every reboot (PCR10)
Thanks can you give more details on your setup for "trusted boot and attestation" ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068627 Title: IMA Hashes keep changing on every reboot (PCR10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2068627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068627] Re: IMA Hashes keep changing on every reboot (PCR10)
I see only a change in the order of the measurements but not on the measurement values, for example, drm.ko has the exact hash value for both boots -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068627 Title: IMA Hashes keep changing on every reboot (PCR10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2068627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059352] Re: paramiko 2.12.0-2ubuntu4 fails autopkgtests on all architectures
** Changed in: paramiko (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059352 Title: paramiko 2.12.0-2ubuntu4 fails autopkgtests on all architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/paramiko/+bug/2059352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961118] Re: Fails on unusual mounted filesystems
** Changed in: efitools (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) ** Changed in: efitools (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961118 Title: Fails on unusual mounted filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/efitools/+bug/1961118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059352] Re: paramiko 2.12.0-2ubuntu4 fails autopkgtests on all architectures
On noble, i can confirm that the patch mentioned by @chriscoulson fixes the issue (Patch link : https://github.com/paramiko/paramiko/commit/d71046151d9904df467ff72709585cde39cdd4ca) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059352 Title: paramiko 2.12.0-2ubuntu4 fails autopkgtests on all architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/paramiko/+bug/2059352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059352] Re: paramiko 2.12.0-2ubuntu4 fails autopkgtests on all architectures
The tests run fine for paramiko devel (oracular) ** Changed in: paramiko (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059352 Title: paramiko 2.12.0-2ubuntu4 fails autopkgtests on all architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/paramiko/+bug/2059352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[PATCH v1 1/1] Fix missing measurements on confidential computing enabled platform
The measurements for confidential computing has been introduced in the commit
4c76565b6 (efi/tpm: Add EFI_CC_MEASUREMENT_PROTOCOL support). Recently
this patch 30708dfe3 (tpm: Disable the tpm verifier if the TPM device
is not present) has been introduced to optimize the memory usage when
TPM device is not available on the platform. This patch will prevent the
tpm module to be loaded on confidential computing platform (for example
Intel TDX) where no TPM device is available.
In this patch, we propose to load the tpm module for this use case
by generalizing the tpm feature detection in order to cover CC platforms.
Basically, do we it by detecting the availability of the EFI protocol
EFI_CC_MEASUREMENT_PROTOCOL.
Fixes bug : https://savannah.gnu.org/bugs/?65821
Signed-off-by: Hector Cao
---
grub-core/commands/efi/tpm.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/grub-core/commands/efi/tpm.c b/grub-core/commands/efi/tpm.c
index f250c30db..40845af7a 100644
--- a/grub-core/commands/efi/tpm.c
+++ b/grub-core/commands/efi/tpm.c
@@ -292,6 +292,13 @@ grub_tpm_present (void)
{
grub_efi_handle_t tpm_handle;
grub_efi_uint8_t protocol_version;
+ grub_efi_cc_protocol_t *cc;
+
+ /* if confidential computing measurement protocol is enabled
+ we consider TPM is present */
+ cc = grub_efi_locate_protocol (&cc_measurement_guid, NULL);
+ if (cc != NULL)
+return 1;
if (!grub_tpm_handle_find (&tpm_handle, &protocol_version))
return 0;
--
2.39.2
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
[PATCH v1 0/1] Fix missing measurements on confidential computing enabled platform
Changes from v0: - Add SOB line - Compliant with grub coding style Hector Cao (1): Fix missing measurements on confidential computing enabled platform grub-core/commands/efi/tpm.c | 7 +++ 1 file changed, 7 insertions(+) -- 2.39.2 ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
[Bug 1551074] Re: "No efivarfs filesystem is mounted" error when running efi-readvar
** Changed in: efitools (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551074 Title: "No efivarfs filesystem is mounted" error when running efi-readvar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/efitools/+bug/1551074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Fix missing measurements on confidential computing enabled platform
This patch fixes : https://savannah.gnu.org/bugs/?65821
Commit message:
Fix missing measurements on confidential computing enabled platform
The measurements for confidential computing has been introduced in the
commit
4c76565b6 (efi/tpm: Add EFI_CC_MEASUREMENT_PROTOCOL support). Recently
this patch 30708dfe3 (tpm: Disable the tpm verifier if the TPM device
is not present) has been introduced to optimize the memory usage when
TPM device is not available on the platform. This patch will prevent the
tpm module to be loaded on confidential computing platform (for example
Intel TDX) where no TPM device is available.
In this patch, we propose to load the tpm module for this use case
by generalizing the tpm feature detection in order to cover CC
platforms.
Basically, do we it by detecting the availability of the EFI protocol
EFI_CC_MEASUREMENT_PROTOCOL.
Changelog:
tpm: load tpm module on CC platforms even without tpm device
--
Hector CAO
Software Engineer – Partner Engineering Team
hector@canonical.com
https://launc <https://launchpad.net/~hectorcao>hpad.net/~hectorcao
<https://launchpad.net/~hectorcao>
<https://launchpad.net/~hectorcao>
From ff55be406c68ae0ed4d352838749cd3e89051b82 Mon Sep 17 00:00:00 2001
From: Hector Cao
Date: Fri, 31 May 2024 12:09:28 +
Subject: [PATCH] Fix missing measurements on confidential computing enabled
platform
The measurements for confidential computing has been introduced in the commit
4c76565b6 (efi/tpm: Add EFI_CC_MEASUREMENT_PROTOCOL support). Recently
this patch 30708dfe3 (tpm: Disable the tpm verifier if the TPM device
is not present) has been introduced to optimize the memory usage when
TPM device is not available on the platform. This patch will prevent the
tpm module to be loaded on confidential computing platform (for example
Intel TDX) where no TPM device is available.
In this patch, we propose to load the tpm module for this use case
by generalizing the tpm feature detection in order to cover CC platforms.
Basically, do we it by detecting the availability of the EFI protocol
EFI_CC_MEASUREMENT_PROTOCOL.
---
grub-core/commands/efi/tpm.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/grub-core/commands/efi/tpm.c b/grub-core/commands/efi/tpm.c
index f250c30db..386ea3d66 100644
--- a/grub-core/commands/efi/tpm.c
+++ b/grub-core/commands/efi/tpm.c
@@ -292,6 +292,13 @@ grub_tpm_present (void)
{
grub_efi_handle_t tpm_handle;
grub_efi_uint8_t protocol_version;
+ grub_efi_cc_protocol_t *cc;
+
+ // if confidential computing measurement protocol is enabled
+ // we consider TPM is present
+ cc = grub_efi_locate_protocol (&cc_measurement_guid, NULL);
+ if (cc != NULL)
+return 1;
if (!grub_tpm_handle_find (&tpm_handle, &protocol_version))
return 0;
--
2.43.0
[PATCH] Fix missing measurements on confidential computing enabled platform
The measurements for confidential computing has been introduced in the commit
4c76565b6 (efi/tpm: Add EFI_CC_MEASUREMENT_PROTOCOL support). Recently
this patch 30708dfe3 (tpm: Disable the tpm verifier if the TPM device
is not present) has been introduced to optimize the memory usage when
TPM device is not available on the platform. This patch will prevent the
tpm module to be loaded on confidential computing platform (for example
Intel TDX) where no TPM device is available.
In this patch, we propose to load the tpm module for this use case
by generalizing the tpm feature detection in order to cover CC platforms.
Basically, do we it by detecting the availability of the EFI protocol
EFI_CC_MEASUREMENT_PROTOCOL.
Fixes bug : https://savannah.gnu.org/bugs/?65821
---
grub-core/commands/efi/tpm.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/grub-core/commands/efi/tpm.c b/grub-core/commands/efi/tpm.c
index f250c30db..386ea3d66 100644
--- a/grub-core/commands/efi/tpm.c
+++ b/grub-core/commands/efi/tpm.c
@@ -292,6 +292,13 @@ grub_tpm_present (void)
{
grub_efi_handle_t tpm_handle;
grub_efi_uint8_t protocol_version;
+ grub_efi_cc_protocol_t *cc;
+
+ // if confidential computing measurement protocol is enabled
+ // we consider TPM is present
+ cc = grub_efi_locate_protocol (&cc_measurement_guid, NULL);
+ if (cc != NULL)
+return 1;
if (!grub_tpm_handle_find (&tpm_handle, &protocol_version))
return 0;
--
2.39.2
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
[bug #65821] Missing measurements on confidential computing platforms (Intel TDX)
URL: <https://savannah.gnu.org/bugs/?65821> Summary: Missing measurements on confidential computing platforms (Intel TDX) Group: GNU GRUB Submitter: hectorcao Submitted: Fri 31 May 2024 11:14:31 AM UTC Category: Security Severity: Major Priority: 5 - Normal Item Group: Hardware-specific Status: None Privacy: Public Assigned to: None Originator Name: Hector CAO Originator Email: Open/Closed: Open Release: Git master Release: Discussion Lock: Any Reproducibility: Every Time Planned Release: None ___ Follow-up Comments: --- Date: Fri 31 May 2024 11:14:31 AM UTC By: Hector Cao When we run a Confidential VM with grub bootlodaer on Intel TDX platform. The module tpm is not loaded and boot measurements are not done for the guest VM. ___ Reply to this item at: <https://savannah.gnu.org/bugs/?65821> ___ Message sent via Savannah https://savannah.gnu.org/
[Bug 2048895] Re: [needs-packaging] Intel quickassist (QAT) : qatlib
** Changed in: ubuntu-release-notes Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2048895 Title: [needs-packaging] Intel quickassist (QAT) : qatlib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2048895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048938] Re: [needs-packaging] Intel quickassist (QAT) : openssl QAT engine
** Changed in: ubuntu-release-notes Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2048938 Title: [needs-packaging] Intel quickassist (QAT) : openssl QAT engine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2048938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048950] Re: [needs-packaging] Intel quickassist (QAT) : zip compression library and application utility
** Changed in: ubuntu-release-notes Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2048950 Title: [needs-packaging] Intel quickassist (QAT) : zip compression library and application utility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2048950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066061] Re: Please merge paramiko 3.4.0-1 into Oracular
The folowing Ubuntu changes are dropped: - SECURITY UPDATE: Prefix truncation attack on BPP - debian/patches/CVE-2023-48795-*.patch: implement strict key exchange. - CVE-2023-48795 These changes are backports from upstream and the new debian version contains these commits. Per consequence, no need anymore to apply them - debian/patches/remove_six.patch This patch is dropped since it is in upstream - debian/patches/fix_test_on_armhf.patch This patch is dropped because the file tests/test_transport.py is changed in the new version and this patch is not application neither necessary ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-48795 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066061 Title: Please merge paramiko 3.4.0-1 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/paramiko/+bug/2066061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066061] Re: Please merge paramiko 3.4.0-1 into Oracular
The merge request : https://code.launchpad.net/~hectorcao/ubuntu/+source/paramiko/+git/paramiko/+merge/466111 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066061 Title: Please merge paramiko 3.4.0-1 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/paramiko/+bug/2066061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066061] Re: Please merge paramiko 3.4.0-1 into Oracular
** Changed in: paramiko (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) ** Changed in: paramiko (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066061 Title: Please merge paramiko 3.4.0-1 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/paramiko/+bug/2066061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066061] [NEW] Please merge paramiko 3.4.0-1 into Oracular
Public bug reported: paramiko Fri May 3 21:50:49 2024 Below now follows the report of the automated merge of the Ubuntu changes to the paramiko source package against the new Debian version. Here are the particulars of the three versions of paramiko that were chosen for the merge. The base is the newest version that is a common ancestor of both the Ubuntu and Debian packages. It may be of a different upstream version, but that's not usually a problem. The files are the source package itself, and the patch from the common base to that version. base: 2.12.0-2 paramiko_2.12.0-2.dsc paramiko_2.12.0.orig.tar.xz paramiko_2.12.0-2.debian.tar.xz ubuntu: 2.12.0-2ubuntu4 paramiko_2.12.0-2ubuntu4.dsc paramiko_2.12.0.orig.tar.xz paramiko_2.12.0-2ubuntu4.debian.tar.xz base -> ubuntu paramiko_2.12.0-2ubuntu4.patch debian: 3.4.0-1 paramiko_3.4.0-1.dsc paramiko_3.4.0.orig.tar.xz paramiko_3.4.0-1.debian.tar.xz base -> debian paramiko_3.4.0-1.patch Generated Result Due to conflict or error, it was not possible to automatically create a source package. Instead the result of the merge has been placed into the following tar file which you will need to turn into a source package once the problems have been resolved. paramiko_3.4.0-1ubuntu1.src.tar.gz Conflicts = In one or more cases, there were different changes made in both Ubuntu and Debian to the same file; these are known as conflicts. It is not possible for these to be automatically resolved, so this source needs human attention. Those files marked with 'C ' contain diff3 conflict markers, which can be resolved using the text editor of your choice. Those marked with 'C*' could not be merged that way, so you will find .UBUNTU and .DEBIAN files instead and should choose one of them or a combination of both, moving it to the real filename and deleting the other. C debian/patches/series ** Affects: paramiko (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066061 Title: Please merge paramiko 3.4.0-1 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/paramiko/+bug/2066061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065883] Re: Please merge wget 1.24.5-1 into Oracular
The merge request : https://code.launchpad.net/~hectorcao/ubuntu/+source/wget/+git/wget/+merge/466063 The new package has been built and available at : https://launchpad.net/~hectorcao/+archive/ubuntu/lp2065883 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065883 Title: Please merge wget 1.24.5-1 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/2065883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065883] Re: Please merge wget 1.24.5-1 into Oracular
** Changed in: wget (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) ** Changed in: wget (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065883 Title: Please merge wget 1.24.5-1 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/2065883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065883] [NEW] Please merge wget 1.24.5-1 into Oracular
Public bug reported: Debian has new release of wget at version 1.24.5-1 Merge this new release to Oracular ** Affects: wget (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065883 Title: Please merge wget 1.24.5-1 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/2065883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061324] Re: Error when re-building package from source
Right, thanks @racb, this issue does not affect the development release, I put it to Invalid ** Changed in: intel-gpu-tools (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061324 Title: Error when re-building package from source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Launchpad-reviewers] [Merge] ~tchavadar/launchpad-buildd:use-ubuntu-images-deb into launchpad-buildd:master
The unmerged commits list seems strange, perhaps is it work to rebase properly on https://code.launchpad.net/~launchpad/launchpad-buildd/+git/launchpad-buildd/+ref/master ? -- https://code.launchpad.net/~tchavadar/launchpad-buildd/+git/launchpad-buildd/+merge/464761 Your team Launchpad code reviewers is requested to review the proposed merge of ~tchavadar/launchpad-buildd:use-ubuntu-images-deb into launchpad-buildd:master. ___ Mailing list: https://launchpad.net/~launchpad-reviewers Post to : launchpad-reviewers@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-reviewers More help : https://help.launchpad.net/ListHelp
[Bug 2062164] Re: test binary in share doc folder
** Changed in: qatzip (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062164 Title: test binary in share doc folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qatzip/+bug/2062164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062164] Re: test binary in share doc folder
The fix is uploaded here : https://launchpad.net/~hectorcao/+archive/ubuntu/lp-2062164 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062164 Title: test binary in share doc folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qatzip/+bug/2062164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062164] [NEW] test binary in share doc folder
Public bug reported: The qzip-test binary is installed in /usr/share/doc/qatzip. Per consequence, it will be compressed and marked as not executable. Usually the sample, test binaries of a package should be installed in /usr/share/ ** Affects: qatzip (Ubuntu) Importance: Undecided Assignee: Hector CAO (hectorcao) Status: In Progress ** Changed in: qatzip (Ubuntu) Status: New => In Progress ** Changed in: qatzip (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062164 Title: test binary in share doc folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qatzip/+bug/2062164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Description changed: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): - tools/intel_gpu_top: Fix clients header width when no clients - tools/intel_gpu_top: Fix client layout on first sample period - tools/intel_gpu_top: Optimise interactive display a bit - tools/intel_gpu_top: Handle narrow terminals more gracefully + tools/intel_gpu_top: Fix clients header width when no clients + tools/intel_gpu_top: Fix client layout on first sample period + tools/intel_gpu_top: Optimise interactive display a bit + tools/intel_gpu_top: Handle narrow terminals more gracefully + + NOTES: + For Noble, all the 4 patches will be backported + For Mantic, Jammy, only "tools/intel_gpu_top: Handle narrow terminals more gracefully" will be backported because the others are not applicable to Jammy/Mantic (related to refactoring that happened after Mantic release) [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Description changed: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): - tools/intel_gpu_top: Fix clients header width when no clients - tools/intel_gpu_top: Fix client layout on first sample period - tools/intel_gpu_top: Optimise interactive display a bit - tools/intel_gpu_top: Handle narrow terminals more gracefully + tools/intel_gpu_top: Fix clients header width when no clients + tools/intel_gpu_top: Fix client layout on first sample period + tools/intel_gpu_top: Optimise interactive display a bit + tools/intel_gpu_top: Handle narrow terminals more gracefully + + NOTES: + For Noble, all the 4 patches will be backported + For Mantic, Jammy, only "tools/intel_gpu_top: Handle narrow terminals more gracefully" will be backported because the others are not applicable to Jammy/Mantic (related to refactoring that happened after Mantic release) [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: Fix Released Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: In Progress Status in intel-gpu-tools source package in Noble: Fix Released Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): tools/intel_gpu_top: Fix clients header width when no clients tools/intel_gpu_top: Fix client layout on first sample period tools/intel_gpu_top: Optimise interactive display a bit tools/intel_gpu_top: Handle narrow terminals more gracefully NOTES: For Noble, all the 4 patches will be backported For Mantic, Jammy, only "tools/intel_gpu_top: Handle narrow terminals more gracefully" will be backported because the others are not applicable to Jammy/Mantic (related to refactoring that happened after Mantic release) [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it cr
[Ubuntu-x-swat] [Bug 2061324] Re: Error when re-building package from source
build fix is usually not accepted in SRU, this fix will be part of https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314 ** Changed in: intel-gpu-tools (Ubuntu Jammy) Status: New => In Progress ** Changed in: intel-gpu-tools (Ubuntu Jammy) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/2061324 Title: Error when re-building package from source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061324] Re: Error when re-building package from source
build fix is usually not accepted in SRU, this fix will be part of
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314
** Changed in: intel-gpu-tools (Ubuntu Jammy)
Status: New => In Progress
** Changed in: intel-gpu-tools (Ubuntu Jammy)
Assignee: (unassigned) => Hector CAO (hectorcao)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2061324
Title:
Error when re-building package from source
Status in intel-gpu-tools package in Ubuntu:
In Progress
Status in intel-gpu-tools source package in Jammy:
In Progress
Bug description:
[ Impact ]
Impossible to build the package from source on Ubuntu 22.04, users will get
this error:
```
int main(void) {
void *a = (void*) &memfd_create;
long long b = (long long) a;
return (int) b;
}
Compiler stdout:
Compiler stderr:
Checking for function "memfd_create" : YES
Configuring config.h using configuration
../lib/meson.build:155:4: ERROR: Function does not take positional arguments.
dh_auto_configure: error: cd build && LC_ALL=C.UTF-8 meson ..
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dtests=disabled returned
exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/home/ubuntu/hector/intel-gpu-tools-1.26'
make: *** [debian/rules:39: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
```
The problem comes from the bad call to meson function underscorify in
lib/meson.build
This problem has been fixed upstream:
963917a3565466832a3b2fc22e9285d34a0bf944
lib/meson.build: Fix underscorify call
f.underscorify() is correct, f.underscorify(f) is an error that later
meson versions don't like at all.
The proposed fix for Ubuntu consists of backporting this patch.
[ Test Plan ]
Build the package from source on Ubuntu 22.04
The build command is : dpkg-buildpackage -us -uc -b
Ubuntu release : Jammy 22.04
Meson version : 0.61.2
[ Where problems could occur ]
The problem occurs only at build process
[ Other Info ]
This issue only happens at build and has been fixed upstream.
It is safe to have it in SRU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Description changed: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): - tools/intel_gpu_top: Fix clients header width when no clients - tools/intel_gpu_top: Fix client layout on first sample period - tools/intel_gpu_top: Optimise interactive display a bit - tools/intel_gpu_top: Handle narrow terminals more gracefully + tools/intel_gpu_top: Fix clients header width when no clients + tools/intel_gpu_top: Fix client layout on first sample period + tools/intel_gpu_top: Optimise interactive display a bit + tools/intel_gpu_top: Handle narrow terminals more gracefully + + NOTES: + For Noble, all the 4 patches will be backported + For Mantic, Jammy, only "tools/intel_gpu_top: Handle narrow terminals more gracefully" will be backported because the others are not applicable to Jammy/Mantic (related to refactoring that happened after Mantic release) [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061324] Re: Error when re-building package from source
build fix is usually not accepted in SRU, this fix will be part of https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314 ** Changed in: intel-gpu-tools (Ubuntu Jammy) Status: New => In Progress ** Changed in: intel-gpu-tools (Ubuntu Jammy) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061324 Title: Error when re-building package from source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Changed in: intel-gpu-tools (Ubuntu Mantic) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: Fix Released Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: In Progress Status in intel-gpu-tools source package in Noble: Fix Released Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): tools/intel_gpu_top: Fix clients header width when no clients tools/intel_gpu_top: Fix client layout on first sample period tools/intel_gpu_top: Optimise interactive display a bit tools/intel_gpu_top: Handle narrow terminals more gracefully [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Changed in: intel-gpu-tools (Ubuntu Mantic) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Changed in: intel-gpu-tools (Ubuntu Mantic) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Changed in: intel-gpu-tools (Ubuntu Mantic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Changed in: intel-gpu-tools (Ubuntu Mantic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Changed in: intel-gpu-tools (Ubuntu Mantic) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: Fix Released Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: In Progress Status in intel-gpu-tools source package in Noble: Fix Released Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): tools/intel_gpu_top: Fix clients header width when no clients tools/intel_gpu_top: Fix client layout on first sample period tools/intel_gpu_top: Optimise interactive display a bit tools/intel_gpu_top: Handle narrow terminals more gracefully [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
debdiff for noble ** Attachment removed: "intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765600/+files/intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz ** Attachment added: "intel-gpu-tools_1.28-1ubuntu0.1_1.28-1ubuntu2.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765627/+files/intel-gpu-tools_1.28-1ubuntu0.1_1.28-1ubuntu2.diff.gz -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
debdiff for noble ** Attachment removed: "intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765600/+files/intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz ** Attachment added: "intel-gpu-tools_1.28-1ubuntu0.1_1.28-1ubuntu2.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765627/+files/intel-gpu-tools_1.28-1ubuntu0.1_1.28-1ubuntu2.diff.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: New Status in intel-gpu-tools source package in Noble: In Progress Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): tools/intel_gpu_top: Fix clients header width when no clients tools/intel_gpu_top: Fix client layout on first sample period tools/intel_gpu_top: Optimise interactive display a bit tools/intel_gpu_top: Handle narrow terminals more gracefully [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
debdiff for noble ** Attachment removed: "intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765600/+files/intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz ** Attachment added: "intel-gpu-tools_1.28-1ubuntu0.1_1.28-1ubuntu2.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765627/+files/intel-gpu-tools_1.28-1ubuntu0.1_1.28-1ubuntu2.diff.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049714] Re: [RPL-P] igt-gpu-tool enablement
** Changed in: intel-gpu-tools (Ubuntu Noble) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049714 Title: [RPL-P] igt-gpu-tool enablement To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Ubuntu-x-swat] [Bug 2049714] Re: [RPL-P] igt-gpu-tool enablement
** Changed in: intel-gpu-tools (Ubuntu Noble) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/2049714 Title: [RPL-P] igt-gpu-tool enablement To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049714/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049714] Re: [RPL-P] igt-gpu-tool enablement
** Changed in: intel-gpu-tools (Ubuntu Noble) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/2049714 Title: [RPL-P] igt-gpu-tool enablement Status in intel: Fix Released Status in The Kobuk project: In Progress Status in intel-gpu-tools package in Ubuntu: Fix Released Status in intel-gpu-tools source package in Noble: Fix Released Bug description: [Description] igt-gpu-tool enabling for Raptor Lake-P [Hardware Information] Architecture: Intel Platform(s): Raptor Lake-P Date HW is expected at Canonical: Component(s): itg-gpu-tool [Software Information] Target Version: 22.04 Target Kernel: Commit IDs / External Links: https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/commit/1b32bcdb2d9965090234739aba891a90743e01c4 [Business Justification] [Testing guidance] [External ID] To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
debdiff for Noble ** Attachment added: "intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765600/+files/intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
debdiff for Noble ** Attachment added: "intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765600/+files/intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: New Status in intel-gpu-tools source package in Noble: In Progress Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): tools/intel_gpu_top: Fix clients header width when no clients tools/intel_gpu_top: Fix client layout on first sample period tools/intel_gpu_top: Optimise interactive display a bit tools/intel_gpu_top: Handle narrow terminals more gracefully [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
The fixed is available for Noble at : https://launchpad.net/~hectorcao/+archive/ubuntu/lp-1949314 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
debdiff for Noble ** Attachment added: "intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765600/+files/intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
The fixed is available for Noble at : https://launchpad.net/~hectorcao/+archive/ubuntu/lp-1949314 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: New Status in intel-gpu-tools source package in Noble: In Progress Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): tools/intel_gpu_top: Fix clients header width when no clients tools/intel_gpu_top: Fix client layout on first sample period tools/intel_gpu_top: Optimise interactive display a bit tools/intel_gpu_top: Handle narrow terminals more gracefully [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
