[Canonical-ubuntu-qa] [Bug 2036730] Re: autopkgtest ignores --architecture flag
Hello Heinrich, or anyone else affected, Accepted livecd-rootfs into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd- rootfs/2.765.33 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done-jammy ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu. https://bugs.launchpad.net/bugs/2036730 Title: autopkgtest ignores --architecture flag Status in autopkgtest package in Ubuntu: Incomplete Status in livecd-rootfs package in Ubuntu: Fix Released Status in autopkgtest source package in Focal: New Status in livecd-rootfs source package in Focal: Won't Fix Status in autopkgtest source package in Jammy: New Status in livecd-rootfs source package in Jammy: Fix Committed Status in autopkgtest source package in Lunar: New Status in livecd-rootfs source package in Lunar: Fix Released Status in autopkgtest source package in Mantic: New Status in livecd-rootfs source package in Mantic: Fix Released Bug description: Description --- The cloud images produced by livecd-rootfs do not properly configure the tty for armhf and subsequently the terminal output is not available. Test Case - 1) Run `autopkgtest-buildvm-ubuntu-cloud -v --arch armhf --release mantic` substituting the release name as appropriate 2) Observe the last console message `EFI stub: Exiting boot services...` With a cloud image build with the livecd-rootfs version in -proposed you'll see much more output from `autopkgtest-buildvm-ubuntu-cloud` including cloud-init configuring the system. Regression Potential The serial console is being set to ttyS0 differently that it was for architectures other than arm64 or armhf. However, this has been in place in noble for an extended period of time and has not cause any regressions for those architectures. Original Description On an arm64 as well as on amd64 I saw this behavior: $ autopkgtest-buildvm-ubuntu-cloud -v --arch armhf --release mantic $ autopkgtest -U --apt-pocket=proposed -a armhf -s *.dsc -- qemu autopkgtest-mantic-armhf.img autopkgtest [13:18:32]: starting date and time: 2023-09-20 13:18:32+0200 autopkgtest [13:18:32]: version 5.28ubuntu1 autopkgtest [13:18:32]: host mcbin; command line: /usr/bin/autopkgtest -U --apt-pocket=proposed -a armhf -s forensics-all_3.47.dsc -- qemu autopkgtest-mantic-armhf.img qemu-system-aarch64: terminating on signal 15 from pid 3520 (/usr/bin/python3) : failure: timed out waiting for 'login prompt on serial console' autopkgtest [13:19:33]: ERROR: testbed failure: unexpected eof from the testbed When trying to boot into the image on an arm64 system with qemu-system-aarch64 \ -machine virt -accel kvm -m 4G -smp 4 -cpu host,aarch64=off -nographic \ -object rng-random,filename=/dev/urandom,id=rng0 \ -device virtio-rng-pci,rng=rng0,id=rng-device0 \ -drive if=pflash,format=raw,unit=0,read-only=on,file=/usr/share/AAVMF/AAVMF32_CODE.fd \ -device virtio-net-pci,netdev=eth0 \ -netdev user,id=eth0,hostfwd=tcp::8022-:22 \ -drive file=autopkgtest-mantic-armhf.img,if=virtio,format=qcow2 the last messages displayed are EFI stub: Booting Linux Kernel... EFI stub: Entering in SVC mode with MMU enabled EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... qemu-system-aarch64 seems to be close to idling at less than 0.5 % CPU load. So booting obviously stalled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2036730/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubsc
[Canonical-ubuntu-qa] [Bug 2036730] Please test proposed package
Hello Heinrich, or anyone else affected, Accepted livecd-rootfs into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd- rootfs/2.765.34 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu. https://bugs.launchpad.net/bugs/2036730 Title: autopkgtest ignores --architecture flag Status in autopkgtest package in Ubuntu: Incomplete Status in livecd-rootfs package in Ubuntu: Fix Released Status in autopkgtest source package in Focal: New Status in livecd-rootfs source package in Focal: Won't Fix Status in autopkgtest source package in Jammy: New Status in livecd-rootfs source package in Jammy: Fix Committed Status in autopkgtest source package in Lunar: New Status in livecd-rootfs source package in Lunar: Fix Released Status in autopkgtest source package in Mantic: New Status in livecd-rootfs source package in Mantic: Fix Released Bug description: Description --- The cloud images produced by livecd-rootfs do not properly configure the tty for armhf and subsequently the terminal output is not available. Test Case - 1) Run `autopkgtest-buildvm-ubuntu-cloud -v --arch armhf --release mantic` substituting the release name as appropriate 2) Observe the last console message `EFI stub: Exiting boot services...` With a cloud image build with the livecd-rootfs version in -proposed you'll see much more output from `autopkgtest-buildvm-ubuntu-cloud` including cloud-init configuring the system. Regression Potential The serial console is being set to ttyS0 differently that it was for architectures other than arm64 or armhf. However, this has been in place in noble for an extended period of time and has not cause any regressions for those architectures. Original Description On an arm64 as well as on amd64 I saw this behavior: $ autopkgtest-buildvm-ubuntu-cloud -v --arch armhf --release mantic $ autopkgtest -U --apt-pocket=proposed -a armhf -s *.dsc -- qemu autopkgtest-mantic-armhf.img autopkgtest [13:18:32]: starting date and time: 2023-09-20 13:18:32+0200 autopkgtest [13:18:32]: version 5.28ubuntu1 autopkgtest [13:18:32]: host mcbin; command line: /usr/bin/autopkgtest -U --apt-pocket=proposed -a armhf -s forensics-all_3.47.dsc -- qemu autopkgtest-mantic-armhf.img qemu-system-aarch64: terminating on signal 15 from pid 3520 (/usr/bin/python3) : failure: timed out waiting for 'login prompt on serial console' autopkgtest [13:19:33]: ERROR: testbed failure: unexpected eof from the testbed When trying to boot into the image on an arm64 system with qemu-system-aarch64 \ -machine virt -accel kvm -m 4G -smp 4 -cpu host,aarch64=off -nographic \ -object rng-random,filename=/dev/urandom,id=rng0 \ -device virtio-rng-pci,rng=rng0,id=rng-device0 \ -drive if=pflash,format=raw,unit=0,read-only=on,file=/usr/share/AAVMF/AAVMF32_CODE.fd \ -device virtio-net-pci,netdev=eth0 \ -netdev user,id=eth0,hostfwd=tcp::8022-:22 \ -drive file=autopkgtest-mantic-armhf.img,if=virtio,format=qcow2 the last messages displayed are EFI stub: Booting Linux Kernel... EFI stub: Entering in SVC mode with MMU enabled EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... qemu-system-aarch64 seems to be close to idling at less than 0.5 % CPU load. So booting obviously stalled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2036730/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launch
[Canonical-ubuntu-qa] [Bug 2051593] Re: Cross arch testing: AttributeError: 'builtin_function_or_method' object has no attribute 'split'
Please provide an clear Test Case and describe the possible Regression
Potential for this bug in the bug description [1].
[1] https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
** Also affects: autopkgtest (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: autopkgtest (Ubuntu Mantic)
Status: New => Incomplete
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/2051593
Title:
Cross arch testing: AttributeError: 'builtin_function_or_method'
object has no attribute 'split'
Status in autopkgtest package in Ubuntu:
Fix Released
Status in autopkgtest source package in Mantic:
Incomplete
Bug description:
autopkgtest can traceback when running cross-arch tests due to wrong
variable name:
autopkgtest [22:44:13]: ERROR: unexpected error:
Traceback (most recent call last):
File "/usr/bin/autopkgtest", line 902, in main
testbed.open()
File "/usr/share/autopkgtest/lib/adt_testbed.py", line 178, in open
self._opened(pl)
File "/usr/share/autopkgtest/lib/adt_testbed.py", line 345, in _opened
for var in vars.split('\n'):
^^
AttributeError: 'builtin_function_or_method' object has no attribute 'split'
qemu-system-x86_64: terminating on signal 15 from pid 1681994
(/usr/bin/python3)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2051593/+subscriptions
--
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2049737] Re: autopkgtest schroot fails with network access
Please provide an clear Test Case and describe the possible Regression Potential for this bug in the bug description [1]. [1] https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template ** Also affects: debootstrap (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: autopkgtest (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: autopkgtest (Ubuntu Mantic) Status: New => Incomplete -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu. https://bugs.launchpad.net/bugs/2049737 Title: autopkgtest schroot fails with network access Status in autopkgtest package in Ubuntu: Fix Released Status in debootstrap package in Ubuntu: Invalid Status in autopkgtest source package in Mantic: Incomplete Status in debootstrap source package in Mantic: New Bug description: on armhf, the schroot test was skipped previously, because it fails to create the tarball. 222s autopkgtest [16:35:34]: test schroot: [--- 224s mknod: /var/lib/schroot/unpack/tmp.b5GEblfCFW/test-dev-null: Operation not permitted 224s E: Cannot install into target '/var/lib/schroot/unpack/tmp.b5GEblfCFW' mounted with noexec or nodev 224s E: Error running debootstrap at /usr/bin/sbuild-createchroot line 438. 224s SKIP: Unable to create chroot testing-armhf-sbuild 224s autopkgtest [16:35:36]: test schroot: ---] 227s schroot SKIP exit status 77 and marked as skippable https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/armhf/a/autopkgtest/20240117_163550_48058@/log.gz now, with debootstrap/1.0.134ubuntu1, it can create tarball, so the test continues. 385s autopkgtest [09:09:35]: test schroot: [--- 685s I: Base system installed successfully. ... 688s I: Please add any additional APT sources to /var/lib/schroot/unpack/tmp.oMtNMr6H6p/etc/apt/sources.list 688s I: schroot chroot configuration written to /etc/schroot/chroot.d/testing-armhf-sbuild-kd1HCC. 688s I: Please rename and modify this file as required. 688s mkdir /etc/sbuild/chroot However the tests fail to recognize the http proxy, so it fails with 757s Err:1 http://deb.debian.org/debian testing InRelease 757s Cannot initiate the connection to deb.debian.org:80 (2a04:4e42:82::644). - connect (101: Network is unreachable) Could not connect to deb.debian.org:80 (146.75.74.132), connection timed out https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/armhf/a/autopkgtest/20240117_113326_23e69@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2049737/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2009191] Re: autopkgtest: Specifying --apt-pocket causes wrong unwanted pinning to default release
Please provide an clear Test Case and describe the possible Regression Potential for this bug in the bug description [1]. I see a possible test case in comment #1, but I'd like it to be made clear that this is what is expected to be performed to verify the upload. [1] https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template ** Also affects: autopkgtest (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: autopkgtest (Ubuntu Mantic) Status: New => Incomplete -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu. https://bugs.launchpad.net/bugs/2009191 Title: autopkgtest: Specifying --apt-pocket causes wrong unwanted pinning to default release Status in autopkgtest package in Ubuntu: Fix Released Status in autopkgtest source package in Mantic: Incomplete Status in autopkgtest package in Debian: Fix Released Bug description: Imported from Debian bug http://bugs.debian.org/1032314: Package: autopkgtest Severity: normal X-Debbugs-Cc: par...@debian.org Adding a pocket via --apt-pocket= causes the _get_default_release() function to be called. This is needed to construct the sources.list entry for the pocket, which will be in the form of: deb - ... The _get_default_release() function caches the detected default release in the default_release variable, which is the same variable used to store the --apt-default-release= value. This has no effect when only one test is present in d/t/control, but when more than one test is present the tests after the first will have unwanted/wrong pinning (as if --apt-default-release was specified). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2009191/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2036604] Re: Synchronous Exception when booting VMs via qemu-efi-aarch64
Hello Heinrich, or anyone else affected,
Accepted shim into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/shim/15.8-0ubuntu1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: shim (Ubuntu Jammy)
Status: New => Fix Committed
** Tags added: verification-needed verification-needed-jammy
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/2036604
Title:
Synchronous Exception when booting VMs via qemu-efi-aarch64
Status in cloud-images:
New
Status in autopkgtest package in Ubuntu:
Confirmed
Status in edk2 package in Ubuntu:
Fix Released
Status in qemu package in Ubuntu:
Confirmed
Status in shim package in Ubuntu:
Fix Released
Status in shim source package in Jammy:
Fix Committed
Status in edk2 package in Debian:
Fix Released
Bug description:
I try to create an autopkgtest VM on an arm64 system with
autopkgtest-buildvm-ubuntu-cloud -v --release mantic
or on an amd64 system with
autopkgtest-buildvm-ubuntu-cloud --arch arm64 -v --release mantic
In both cases I get:
Found linux image: /boot/vmlinuz-6.5.0-5-generic
Found initrd image: /boot/initrd.img-6.5.0-5-generic
Found linux image: /boot/vmlinuz-6.3.0-7-generic
Found initrd image: /boot/initrd.img-6.3.0-7-generic
Found linux image: /boot/vmlinuz-6.2.0-20-generic
Found initrd image: /boot/initrd.img-6.2.0-20-generic
Warning: os-prober will not be executed to detect other bootable partitions.
BdsDxe: loading Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x5,0x0)
BdsDxe: starting Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x5,0x0)
Synchronous Exception at 0x5C328000
Synchronous Exception at 0x5C328000
^A^Cqemu-system-aarch64: terminating on signal 2
Traceback (most recent call last):
/var/crash has no entries.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: qemu-system-arm 1:8.0.4+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic aarch64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu2
Architecture: arm64
CasperMD5CheckResult: pass
CloudArchitecture: aarch64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Tue Sep 19 15:37:20 2023
InstallationDate: Installed on 2021-08-17 (763 days ago)
InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Alpha arm64 (20210813)
KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND
Lspci-vt:
-[:00]-+-00.0 NVIDIA Corporation GK208B [GeForce GT 730]
\-00.1 NVIDIA Corporation GK208 HDMI/DP Audio Controller
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: qemu
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
dmi.bios.date: Mar 26 2020
dmi.bios.release: 1.0
dmi.bios.vendor: EFI Development Kit II / Marvell
dmi.bios.version: EDK II
dmi.board.name: Armada 8040 MacchiatoBin
dmi.board.vendor: SolidRun
dmi.board.version: Rev. 1.3
dmi.chassis.type: 2
dmi.chassis.vendor: SolidRun
dmi.chassis.version: Rev. 1.3
dmi.modalias:
dmi:bvnEFIDevelopmentKitII/Marvell:bvrEDKII:bdMar262020:br1.0:svnSolidRun:pnArmada8040MacchiatoBin:pvrRev.1.3:rvnSolidRun:rnArmada8040MacchiatoBin:rvrRev.1.3:cvnSolidRun:ct2:cvrRev.1.3:sku:
dmi.product.name: Armada 8040 MacchiatoBin
dmi.product.version: Rev. 1.3
dmi.sys.vendor: SolidRun
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2036604/+subscriptions
--
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to : canonical-ubuntu-qa@lists.launchpad.ne
[Canonical-ubuntu-qa] [Bug 2036604] Please test proposed package
Hello Heinrich, or anyone else affected,
Accepted shim-signed into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/shim-signed/1.51.4
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/2036604
Title:
Synchronous Exception when booting VMs via qemu-efi-aarch64
Status in cloud-images:
New
Status in autopkgtest package in Ubuntu:
Confirmed
Status in edk2 package in Ubuntu:
Fix Released
Status in qemu package in Ubuntu:
Confirmed
Status in shim package in Ubuntu:
Fix Released
Status in shim source package in Jammy:
Fix Committed
Status in edk2 package in Debian:
Fix Released
Bug description:
I try to create an autopkgtest VM on an arm64 system with
autopkgtest-buildvm-ubuntu-cloud -v --release mantic
or on an amd64 system with
autopkgtest-buildvm-ubuntu-cloud --arch arm64 -v --release mantic
In both cases I get:
Found linux image: /boot/vmlinuz-6.5.0-5-generic
Found initrd image: /boot/initrd.img-6.5.0-5-generic
Found linux image: /boot/vmlinuz-6.3.0-7-generic
Found initrd image: /boot/initrd.img-6.3.0-7-generic
Found linux image: /boot/vmlinuz-6.2.0-20-generic
Found initrd image: /boot/initrd.img-6.2.0-20-generic
Warning: os-prober will not be executed to detect other bootable partitions.
BdsDxe: loading Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x5,0x0)
BdsDxe: starting Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x5,0x0)
Synchronous Exception at 0x5C328000
Synchronous Exception at 0x5C328000
^A^Cqemu-system-aarch64: terminating on signal 2
Traceback (most recent call last):
/var/crash has no entries.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: qemu-system-arm 1:8.0.4+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic aarch64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu2
Architecture: arm64
CasperMD5CheckResult: pass
CloudArchitecture: aarch64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Tue Sep 19 15:37:20 2023
InstallationDate: Installed on 2021-08-17 (763 days ago)
InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Alpha arm64 (20210813)
KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND
Lspci-vt:
-[:00]-+-00.0 NVIDIA Corporation GK208B [GeForce GT 730]
\-00.1 NVIDIA Corporation GK208 HDMI/DP Audio Controller
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: qemu
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
dmi.bios.date: Mar 26 2020
dmi.bios.release: 1.0
dmi.bios.vendor: EFI Development Kit II / Marvell
dmi.bios.version: EDK II
dmi.board.name: Armada 8040 MacchiatoBin
dmi.board.vendor: SolidRun
dmi.board.version: Rev. 1.3
dmi.chassis.type: 2
dmi.chassis.vendor: SolidRun
dmi.chassis.version: Rev. 1.3
dmi.modalias:
dmi:bvnEFIDevelopmentKitII/Marvell:bvrEDKII:bdMar262020:br1.0:svnSolidRun:pnArmada8040MacchiatoBin:pvrRev.1.3:rvnSolidRun:rnArmada8040MacchiatoBin:rvrRev.1.3:cvnSolidRun:ct2:cvrRev.1.3:sku:
dmi.product.name: Armada 8040 MacchiatoBin
dmi.product.version: Rev. 1.3
dmi.sys.vendor: SolidRun
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2036604/+subscriptions
--
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2036604] Re: Synchronous Exception when booting VMs via qemu-efi-aarch64
Hello Heinrich, or anyone else affected,
Accepted shim-signed into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/shim-signed/1.51.4
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Also affects: shim-signed (Ubuntu)
Importance: Undecided
Status: New
** Changed in: shim-signed (Ubuntu)
Status: New => Fix Committed
** Changed in: shim-signed (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/2036604
Title:
Synchronous Exception when booting VMs via qemu-efi-aarch64
Status in cloud-images:
New
Status in autopkgtest package in Ubuntu:
Confirmed
Status in edk2 package in Ubuntu:
Fix Released
Status in qemu package in Ubuntu:
Confirmed
Status in shim package in Ubuntu:
Fix Released
Status in shim-signed package in Ubuntu:
Fix Committed
Status in shim source package in Focal:
Fix Committed
Status in shim-signed source package in Focal:
Fix Committed
Status in shim source package in Jammy:
Fix Committed
Status in shim-signed source package in Jammy:
Fix Committed
Status in edk2 package in Debian:
Fix Released
Bug description:
I try to create an autopkgtest VM on an arm64 system with
autopkgtest-buildvm-ubuntu-cloud -v --release mantic
or on an amd64 system with
autopkgtest-buildvm-ubuntu-cloud --arch arm64 -v --release mantic
In both cases I get:
Found linux image: /boot/vmlinuz-6.5.0-5-generic
Found initrd image: /boot/initrd.img-6.5.0-5-generic
Found linux image: /boot/vmlinuz-6.3.0-7-generic
Found initrd image: /boot/initrd.img-6.3.0-7-generic
Found linux image: /boot/vmlinuz-6.2.0-20-generic
Found initrd image: /boot/initrd.img-6.2.0-20-generic
Warning: os-prober will not be executed to detect other bootable partitions.
BdsDxe: loading Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x5,0x0)
BdsDxe: starting Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x5,0x0)
Synchronous Exception at 0x5C328000
Synchronous Exception at 0x5C328000
^A^Cqemu-system-aarch64: terminating on signal 2
Traceback (most recent call last):
/var/crash has no entries.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: qemu-system-arm 1:8.0.4+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic aarch64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu2
Architecture: arm64
CasperMD5CheckResult: pass
CloudArchitecture: aarch64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Tue Sep 19 15:37:20 2023
InstallationDate: Installed on 2021-08-17 (763 days ago)
InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Alpha arm64 (20210813)
KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND
Lspci-vt:
-[:00]-+-00.0 NVIDIA Corporation GK208B [GeForce GT 730]
\-00.1 NVIDIA Corporation GK208 HDMI/DP Audio Controller
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: qemu
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
dmi.bios.date: Mar 26 2020
dmi.bios.release: 1.0
dmi.bios.vendor: EFI Development Kit II / Marvell
dmi.bios.version: EDK II
dmi.board.name: Armada 8040 MacchiatoBin
dmi.board.vendor: SolidRun
dmi.board.version: Rev. 1.3
dmi.chassis.type: 2
dmi.chassis.vendor: SolidRun
dmi.chassis.version: Rev. 1.3
dmi.modalias:
dmi:bvnEFIDevelopmentKitII/Marvell:bvrEDKII:bdMar262020:br1.0:svnSolidRun:pnArmada8040MacchiatoBin:pvrRev.1.3:rvnSolidRun:rnArmada8040MacchiatoBin:rvrRev.1.3:cvnSolidRun:ct2:cvr
[Canonical-ubuntu-qa] [Bug 2036604] Re: Synchronous Exception when booting VMs via qemu-efi-aarch64
Hello Heinrich, or anyone else affected,
Accepted shim into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/shim/15.8-0ubuntu1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: shim (Ubuntu Focal)
Status: New => Fix Committed
** Tags added: verification-needed-focal
** Changed in: shim-signed (Ubuntu Focal)
Status: New => Fix Committed
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/2036604
Title:
Synchronous Exception when booting VMs via qemu-efi-aarch64
Status in cloud-images:
New
Status in autopkgtest package in Ubuntu:
Confirmed
Status in edk2 package in Ubuntu:
Fix Released
Status in qemu package in Ubuntu:
Confirmed
Status in shim package in Ubuntu:
Fix Released
Status in shim-signed package in Ubuntu:
Fix Committed
Status in shim source package in Focal:
Fix Committed
Status in shim-signed source package in Focal:
Fix Committed
Status in shim source package in Jammy:
Fix Committed
Status in shim-signed source package in Jammy:
Fix Committed
Status in edk2 package in Debian:
Fix Released
Bug description:
I try to create an autopkgtest VM on an arm64 system with
autopkgtest-buildvm-ubuntu-cloud -v --release mantic
or on an amd64 system with
autopkgtest-buildvm-ubuntu-cloud --arch arm64 -v --release mantic
In both cases I get:
Found linux image: /boot/vmlinuz-6.5.0-5-generic
Found initrd image: /boot/initrd.img-6.5.0-5-generic
Found linux image: /boot/vmlinuz-6.3.0-7-generic
Found initrd image: /boot/initrd.img-6.3.0-7-generic
Found linux image: /boot/vmlinuz-6.2.0-20-generic
Found initrd image: /boot/initrd.img-6.2.0-20-generic
Warning: os-prober will not be executed to detect other bootable partitions.
BdsDxe: loading Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x5,0x0)
BdsDxe: starting Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x5,0x0)
Synchronous Exception at 0x5C328000
Synchronous Exception at 0x5C328000
^A^Cqemu-system-aarch64: terminating on signal 2
Traceback (most recent call last):
/var/crash has no entries.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: qemu-system-arm 1:8.0.4+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic aarch64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu2
Architecture: arm64
CasperMD5CheckResult: pass
CloudArchitecture: aarch64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Tue Sep 19 15:37:20 2023
InstallationDate: Installed on 2021-08-17 (763 days ago)
InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Alpha arm64 (20210813)
KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND
Lspci-vt:
-[:00]-+-00.0 NVIDIA Corporation GK208B [GeForce GT 730]
\-00.1 NVIDIA Corporation GK208 HDMI/DP Audio Controller
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: qemu
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
dmi.bios.date: Mar 26 2020
dmi.bios.release: 1.0
dmi.bios.vendor: EFI Development Kit II / Marvell
dmi.bios.version: EDK II
dmi.board.name: Armada 8040 MacchiatoBin
dmi.board.vendor: SolidRun
dmi.board.version: Rev. 1.3
dmi.chassis.type: 2
dmi.chassis.vendor: SolidRun
dmi.chassis.version: Rev. 1.3
dmi.modalias:
dmi:bvnEFIDevelopmentKitII/Marvell:bvrEDKII:bdMar262020:br1.0:svnSolidRun:pnArmada8040MacchiatoBin:pvrRev.1.3:rvnSolidRun:rnArmada8040MacchiatoBin:rvrRev.1.3:cvnSolidRun:ct2:cvrRev.1.3:sku:
dmi.product.name: Armada 8040 Macc
[Canonical-ubuntu-qa] [Bug 2036604] Please test proposed package
Hello Heinrich, or anyone else affected,
Accepted shim-signed into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/shim-signed/1.40.10
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/2036604
Title:
Synchronous Exception when booting VMs via qemu-efi-aarch64
Status in cloud-images:
New
Status in autopkgtest package in Ubuntu:
Confirmed
Status in edk2 package in Ubuntu:
Fix Released
Status in qemu package in Ubuntu:
Confirmed
Status in shim package in Ubuntu:
Fix Released
Status in shim-signed package in Ubuntu:
Fix Committed
Status in shim source package in Focal:
Fix Committed
Status in shim-signed source package in Focal:
Fix Committed
Status in shim source package in Jammy:
Fix Committed
Status in shim-signed source package in Jammy:
Fix Committed
Status in edk2 package in Debian:
Fix Released
Bug description:
I try to create an autopkgtest VM on an arm64 system with
autopkgtest-buildvm-ubuntu-cloud -v --release mantic
or on an amd64 system with
autopkgtest-buildvm-ubuntu-cloud --arch arm64 -v --release mantic
In both cases I get:
Found linux image: /boot/vmlinuz-6.5.0-5-generic
Found initrd image: /boot/initrd.img-6.5.0-5-generic
Found linux image: /boot/vmlinuz-6.3.0-7-generic
Found initrd image: /boot/initrd.img-6.3.0-7-generic
Found linux image: /boot/vmlinuz-6.2.0-20-generic
Found initrd image: /boot/initrd.img-6.2.0-20-generic
Warning: os-prober will not be executed to detect other bootable partitions.
BdsDxe: loading Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x5,0x0)
BdsDxe: starting Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x5,0x0)
Synchronous Exception at 0x5C328000
Synchronous Exception at 0x5C328000
^A^Cqemu-system-aarch64: terminating on signal 2
Traceback (most recent call last):
/var/crash has no entries.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: qemu-system-arm 1:8.0.4+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic aarch64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu2
Architecture: arm64
CasperMD5CheckResult: pass
CloudArchitecture: aarch64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Tue Sep 19 15:37:20 2023
InstallationDate: Installed on 2021-08-17 (763 days ago)
InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Alpha arm64 (20210813)
KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND
Lspci-vt:
-[:00]-+-00.0 NVIDIA Corporation GK208B [GeForce GT 730]
\-00.1 NVIDIA Corporation GK208 HDMI/DP Audio Controller
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: qemu
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
dmi.bios.date: Mar 26 2020
dmi.bios.release: 1.0
dmi.bios.vendor: EFI Development Kit II / Marvell
dmi.bios.version: EDK II
dmi.board.name: Armada 8040 MacchiatoBin
dmi.board.vendor: SolidRun
dmi.board.version: Rev. 1.3
dmi.chassis.type: 2
dmi.chassis.vendor: SolidRun
dmi.chassis.version: Rev. 1.3
dmi.modalias:
dmi:bvnEFIDevelopmentKitII/Marvell:bvrEDKII:bdMar262020:br1.0:svnSolidRun:pnArmada8040MacchiatoBin:pvrRev.1.3:rvnSolidRun:rnArmada8040MacchiatoBin:rvrRev.1.3:cvnSolidRun:ct2:cvrRev.1.3:sku:
dmi.product.name: Armada 8040 MacchiatoBin
dmi.product.version: Rev. 1.3
dmi.sys.vendor: SolidRun
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2036604/+subscriptions
[Canonical-ubuntu-qa] [Bug 1981485] Re: deb2snap.json contains gnome-3-34-1804 in the seeded section
Hello Brian, or anyone else affected, Accepted ubuntu-release-upgrader into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:22.04.12 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-release-upgrader (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1981485 Title: deb2snap.json contains gnome-3-34-1804 in the seeded section Status in ubuntu-release-upgrader package in Ubuntu: In Progress Status in ubuntu-release-upgrader source package in Jammy: Fix Committed Status in ubuntu-release-upgrader source package in Kinetic: In Progress Bug description: During an upgrade from Ubuntu 20.04 to Ubuntu 22.04 I noticed the following in the log: 2022-07-12 12:11:02,144 DEBUG install of snap firefox succeeded 2022-07-12 12:11:02,735 DEBUG refresh of snap gnome-3-34-1804 failed 2022-07-12 12:11:03,372 DEBUG refresh of snap gtk-common-themes succeeded The refresh of the snap gnome-3-34-1804 failed because there is no ubuntu-22.04 channel for it. I don't think the snap is needed any longer and it should switch from the "seeded" section to the "unseeded" section in deb2snap.json. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1981485/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 1981611] Re: conf file prompt during upgrade from Focal to Jammy
Hello Brian, or anyone else affected, Accepted speech-dispatcher into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/speech- dispatcher/0.11.1-1ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: speech-dispatcher (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1981611 Title: conf file prompt during upgrade from Focal to Jammy Status in speech-dispatcher package in Ubuntu: Fix Committed Status in speech-dispatcher source package in Jammy: Fix Committed Bug description: * Impact A conffile prompt is displayed on upgrade * Test Case upgrade speech-dispatcher from the focal to the jammy-proposed version, there should be no conffile prompt * Regression potential the change only remove a .mainscript line to remove the conffile, if the change was incorrect the prompt could still be there or a an old conffile could be not removed on upgrade - I was performing a distribution upgrade of an Ubuntu Desktop install of Ubuntu 20.04 to Ubuntu 22.04 when I encountered a debconf prompt regarding a speech-dispatcher config file which I had not modified. From /var/log/dist-upgrade/apt-term.log: Setting up speech-dispatcher (0.11.1-1) ...^M Installing new version of config file /etc/speech-dispatcher/modules/cicero.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/dtk-generic.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/epos-generic.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/espeak-mbrola-generic.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/espeak-ng-mbrola-generic.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/espeak-ng.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/espeak.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/festival.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/flite.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/llia_phon-generic.conf ...^M ^M Configuration file '/etc/speech-dispatcher/modules/mary-generic.conf'^M ==> Deleted (by you or by a script) since installation.^M ==> Package distributor has shipped an updated version.^M What would you like to do about it ? Your options are:^M Y or I : install the package maintainer's version^M N or O : keep your currently-installed version^M D : show the differences between the versions^M Z : start a shell to examine the situation^M The default action is to keep your current version.^M *** mary-generic.conf (Y/I/N/O/D/Z) [default=N] ? n^M Installing new version of config file /etc/speech-dispatcher/modules/swift-generic.conf ...^M Installing new version of config file /etc/speech-dispatcher/speechd.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/mary-generic.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/espeak-generic.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/pico-generic.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/ivona.conf ...^M speech-dispatcherd.service is a disabled or a static unit not running, not starting it.^M Removing obsolete conffile /etc/speech-dispatcher/modules/baratinoo.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/ibmtts.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/kali.conf ...^M To manage notifications about this bug go to: https://bugs.launch
[Canonical-ubuntu-qa] [Bug 1981485] Update Released
The verification of the Stable Release Update for ubuntu-release- upgrader has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1981485 Title: deb2snap.json contains gnome-3-34-1804 in the seeded section Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in ubuntu-release-upgrader source package in Jammy: Fix Released Status in ubuntu-release-upgrader source package in Kinetic: Fix Released Bug description: [Description] The snap gnome-3-34-1804 is no longer seeded in Ubuntu 22.04 but the distribution upgrade process is not aware of this and will leave the snap installed after the upgrade. [Test Plan] Test 1 -- Using the dist-upgrader tarball from http://archive.ubuntu.com/ubuntu/dists/jammy-proposed/main/dist-upgrader-all/current/ on an Ubuntu 20.04 LTS system upgrade to Ubuntu 22.04 LTS. (Using the tarball is necessary because one cannot use 'do-release-upgrade -d and -p' simultaneously.) The tarball should be manually extracted into /tmp/ and the file (or symlink) named 'jammy' should be executed. After the upgrade completes the snap gnome-3-34-1804 should no long be installed. (Check out output of snap list and also check /var/log/dist-upgrade/main.log for the message "removing snap gnome-3-34-1804".) Test 2 -- Complete the same test as above but before upgrading install the slack snap. After the upgrade completes gnome-3-34-1804 should still be installed and the slack snap should still launch. [Regression Potential] Other snaps may depend on the gnome-3-34-1804 snap (slack for instance) and removing gnome-3-34-1804 would then make those snaps unusable. Subsequently, the test plan involves installing the slack snap and then upgrading and ensuring it still launches. Original Description During an upgrade from Ubuntu 20.04 to Ubuntu 22.04 I noticed the following in the log: 2022-07-12 12:11:02,144 DEBUG install of snap firefox succeeded 2022-07-12 12:11:02,735 DEBUG refresh of snap gnome-3-34-1804 failed 2022-07-12 12:11:03,372 DEBUG refresh of snap gtk-common-themes succeeded The refresh of the snap gnome-3-34-1804 failed because there is no ubuntu-22.04 channel for it. I don't think the snap is needed any longer and it should switch from the "seeded" section to the "unseeded" section in deb2snap.json. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1981485/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 1981611] Update Released
The verification of the Stable Release Update for speech-dispatcher has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1981611 Title: conf file prompt during upgrade from Focal to Jammy Status in speech-dispatcher package in Ubuntu: Fix Released Status in speech-dispatcher source package in Jammy: Fix Released Bug description: * Impact A conffile prompt is displayed on upgrade * Test Case upgrade speech-dispatcher from the focal to the jammy-proposed version, there should be no conffile prompt * Regression potential the change only remove a .mainscript line to remove the conffile, if the change was incorrect the prompt could still be there or a an old conffile could be not removed on upgrade - I was performing a distribution upgrade of an Ubuntu Desktop install of Ubuntu 20.04 to Ubuntu 22.04 when I encountered a debconf prompt regarding a speech-dispatcher config file which I had not modified. From /var/log/dist-upgrade/apt-term.log: Setting up speech-dispatcher (0.11.1-1) ...^M Installing new version of config file /etc/speech-dispatcher/modules/cicero.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/dtk-generic.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/epos-generic.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/espeak-mbrola-generic.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/espeak-ng-mbrola-generic.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/espeak-ng.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/espeak.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/festival.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/flite.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/llia_phon-generic.conf ...^M ^M Configuration file '/etc/speech-dispatcher/modules/mary-generic.conf'^M ==> Deleted (by you or by a script) since installation.^M ==> Package distributor has shipped an updated version.^M What would you like to do about it ? Your options are:^M Y or I : install the package maintainer's version^M N or O : keep your currently-installed version^M D : show the differences between the versions^M Z : start a shell to examine the situation^M The default action is to keep your current version.^M *** mary-generic.conf (Y/I/N/O/D/Z) [default=N] ? n^M Installing new version of config file /etc/speech-dispatcher/modules/swift-generic.conf ...^M Installing new version of config file /etc/speech-dispatcher/speechd.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/mary-generic.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/espeak-generic.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/pico-generic.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/ivona.conf ...^M speech-dispatcherd.service is a disabled or a static unit not running, not starting it.^M Removing obsolete conffile /etc/speech-dispatcher/modules/baratinoo.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/ibmtts.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/kali.conf ...^M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1981611/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes
Dimitri thank you for the upload! I'd like to accept it soonish, but since this SRU bug is missing the usual Test Case, Impact and Regression Potential, could you fill that up before I accept it? I'd like to know more about the fix that you performed, what it changes and what could go wrong with it. -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to Ubuntu Manual Tests. https://bugs.launchpad.net/bugs/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in Ubuntu Manual Tests: New Status in Release Notes for Ubuntu: Fix Released Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in zsys package in Ubuntu: Invalid Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1993318/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 1939537] Re: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases
Hello Po-Hsu, or anyone else affected, Accepted lxc into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxc/3.0.3-0ubuntu1~18.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: lxc (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Canonical Platform QA Team, which is subscribed to ubuntu-kernel-tests. https://bugs.launchpad.net/bugs/1939537 Title: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Confirmed Status in lxc source package in Bionic: Fix Committed Bug description: Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic Are now failing with: ERROR: Couldn't find a matching image. This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1939537/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test)
Hello Kleber, or anyone else affected, Accepted lxc into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxc/3.0.3-0ubuntu1~18.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: lxc (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Canonical Platform QA Team, which is subscribed to ubuntu-kernel-tests. https://bugs.launchpad.net/bugs/1886790 Title: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test) Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Bionic: Fix Committed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz The failing test seems to be: FAIL: lxc-tests: lxc-test-device-add-remove (0s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... --- This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note that this testcase is successful on Focal with the same kernel version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886790/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 1939537] Update Released
The verification of the Stable Release Update for lxc has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Canonical Platform QA Team, which is subscribed to ubuntu-kernel-tests. https://bugs.launchpad.net/bugs/1939537 Title: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Confirmed Status in lxc source package in Bionic: Fix Released Bug description: [ Impact ] * The following tests fail as they try to use inexistent LXC images: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic * Having them fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for these tests. [ Test Plan ] * Run the affected tests on an affected series (e.g. Bionic). * The tests should pass. [ Where problems could occur ] * The regression risk is very low and the changes only affect the tests so the regression scope is minimal. [Other info] Original bug report: Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic Are now failing with: ERROR: Couldn't find a matching image. This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1939537/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 1886790] Update Released
The verification of the Stable Release Update for lxc has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Canonical Platform QA Team, which is subscribed to ubuntu-kernel-tests. https://bugs.launchpad.net/bugs/1886790 Title: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test) Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Bionic: Fix Released Bug description: [ Impact ] * The device_add_remove_test test fails on the affected series (e.g. Bionic). * Having the test fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for this test. [ Test Plan ] * Run the affected test on an affected series (e.g. Bionic). * The test should pass. [ Where problems could occur ] * The regression risk is very low, and the changes only affect the tests, so the regression scope is minimal. [ Other Info ] Upstream drop of network_latency: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c3082a674f46fe49383b157882c41dfabaa37113 Related to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587 Original bug report: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz The failing test seems to be: FAIL: lxc-tests: lxc-test-device-add-remove (0s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... --- This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note that this testcase is successful on Focal with the same kernel version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886790/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 1910312] Update Released
The verification of the Stable Release Update for glibc has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Canonical Platform QA Team, which is subscribed to ubuntu-kernel-tests. https://bugs.launchpad.net/bugs/1910312 Title: semctl09 from ubuntu_ltp_syscalls failed on X / F-oem-5.6 / F-oracle-5.4 Status in ubuntu-kernel-tests: Triaged Status in glibc package in Ubuntu: Fix Released Status in glibc source package in Focal: Fix Committed Bug description: [ Impact ] * This affects the LTP test plan as it fails one of its IPC semctl tests: semctl09 (https://git.launchpad.net/~canonical-kernel- team/+git/ltp/tree/testcases/kernel/syscalls/ipc/semctl/semctl09.c?h=sru) [ Test Plan ] * Clone https://git.launchpad.net/~canonical-kernel-team/+git/ltp/tree/?h=sru on the sru branch * Compile and run https://git.launchpad.net/~canonical-kernel-team/+git/ltp/tree/testcases/kernel/syscalls/ipc/semctl/semctl09.c?h=sru * Test should pass, reporting no failed checks. * The change also includes a regression test which can be compiled and verified (see tst-sysvsem-linux.c). [ Where problems could occur ] * The regression risk should be very low as the fix only adds SEM_STAT_ANY as a new semctl command while treating it exactly as SEM_STAT. [ Other Info ] Original bug report: This is a new test case. Test output: startup='Tue Jan 5 19:38:52 2021' tst_test.c:1261: TINFO: Timeout per run is 0h 05m 00s semctl09.c:67: TINFO: Test SYS_semctl syscall semctl09.c:132: TINFO: Test SEM_STAT_ANY with nobody user semctl09.c:154: TPASS: SEM_INFO returned valid index 10 to semid 10 semctl09.c:164: TPASS: Counted used = 1 semctl09.c:112: TPASS: semset_cnt = 1 semctl09.c:119: TPASS: sen_cnt = 2 semctl09.c:132: TINFO: Test SEM_STAT_ANY with root user semctl09.c:154: TPASS: SEM_INFO returned valid index 10 to semid 10 semctl09.c:164: TPASS: Counted used = 1 semctl09.c:112: TPASS: semset_cnt = 1 semctl09.c:119: TPASS: sen_cnt = 2 tst_test.c:1261: TINFO: Timeout per run is 0h 05m 00s semctl09.c:70: TINFO: Test libc semctl() semctl09.c:132: TINFO: Test SEM_STAT_ANY with nobody user semctl09.c:148: TFAIL: SEM_STAT_ANY doesn't pass the buffer specified by the caller to kernel semctl09.c:132: TINFO: Test SEM_STAT_ANY with root user semctl09.c:148: TFAIL: SEM_STAT_ANY doesn't pass the buffer specified by the caller to kernel Summary: passed 8 failed 2 broken 0 skipped 0 warnings 0 tag=semctl09 stime=1609875532 dur=0 exit=exited stat=1 core=no cu=0 cs=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1910312/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
