[Bug 1975669] [NEW] USB devices are not working on Raspberry pi zero 2 with arm64 image
Public bug reported: [Summary] USB devices are not working on Raspberry pi zero 2 with arm64 image. I have tried following devices with adapters: rpiz2 micro usb -> usb type-c -> usb type-c storage rpiz2 micro usb -> usb type-c -> usb type-a -> usb type-a storage rpiz2 micro usb -> usb type-c -> usb type-c ethernet dongle rpiz2 micro usb -> usb type-c -> usb type-a -> usb type-a ethernet dongle I have checked both 20.04 and 22.04, all these devices work fine with armhf images but not work with arm64 images. And all these devices work fine on Raspberry pi 3a+ with armhf and arm64 images [Steps to reproduce] 1. Flash image to SD card 2. Boot into system 3. Check usb device with lsusb [Expected result] All usb devices are working fine. [Actual result] USB devices are not working on Raspberry pi zero 2 with arm64 image. [Additional information] SKU: Raspberry pi zero 2 Kernel: 5.15.0-1008-raspi ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-raspi 5.15.0.1008.8 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 25 04:00 seq crw-rw 1 root audio 116, 33 May 25 04:00 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-1008-raspi. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown Date: Wed May 25 06:36:24 2022 ImageMediaBuild: 20220419 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 BCM2708 FB ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:6A:C0:29 vc_mem.mem_base=0x1ec0 vc_mem.mem_size=0x2000 console=ttyS0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-1008-raspi N/A linux-backports-modules-5.15.0-1008-raspi N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-raspi StagingDrivers: bcm2835_codec bcm2835_isp bcm2835_v4l2 vc_sm_cma bcm2835_mmal_vchiq snd_bcm2835 UpgradeStatus: No upgrade log present (probably fresh install) acpidump: ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image jammy raspi-image staging uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975669 Title: USB devices are not working on Raspberry pi zero 2 with arm64 image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1975669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956177] Re: battery not detected by ACPI
Seems like BATD is not correct? Can someone please run $ sudo acpidbg -b 'ex \_SB_.PCI0.LPCB.EC0_.BATD' and attach its value? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956177 Title: battery not detected by ACPI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975670] [NEW] execsnoop-bpfcc gives error and doesn't work in Turkish locale
Public bug reported:
In terminal, after the "sudo execsnoop-bpfcc":
error: unknown argument '-discard-value-names'; did you mean
'-discard-value-names'?
Traceback (most recent call last):
File "/usr/sbin/execsnoop-bpfcc", line 227, in
b = BPF(text=bpf_text)
File "/usr/lib/python3/dist-packages/bcc/__init__.py", line 364, in __init__
raise Exception("Failed to compile BPF module %s" % (src_file or ""))
Exception: Failed to compile BPF module
But if I use "LC_ALL=C" environment variable before command "sudo
LC_ALL=C execsnoop-bpfcc" will work without any problem. This issue
causes another program (like "system76-scheduler") which calls this
function to use much higher cpu clock time.
** Affects: bpfcc (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/1975670
Title:
execsnoop-bpfcc gives error and doesn't work in Turkish locale
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bpfcc/+bug/1975670/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973638] Re: gnome-shell 42 leaks tens of megabytes with every screenshot
https://gitlab.gnome.org/GNOME/gjs/-/merge_requests/746 ** Also affects: gjs (Ubuntu) Importance: Undecided Status: New ** Changed in: gjs (Ubuntu) Importance: Undecided => High ** Changed in: gjs (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/1973638 Title: gnome-shell 42 leaks tens of megabytes with every screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1973638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen
My "prime suspect" is this commit: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/kernel/module.c?h=Ubuntu-4.15.0-177.186&id=3879f4364139acb2bd3932e6a15994f109c49d6b Also see Linus' comments when this patch was submitted to the mainline kernel: https://www.spinics.net/lists/kernel/msg4223720.html "that might be a big deal slowing things down at boot time. [...] Comments? Maybe this is a "just apply it, see if somebody screams" situation?" From what I understand, other measures taken in the kernel and modules make this issue no longer occur, so my hypothesis is that this may not have caused issues in the current kernel. So the mistake was that Canonical backported this commit to a very old kernel version that kernel.org no longer maintains... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973167 Title: linux-image-4.15.0-177-generic freezes on the welcome screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975673] [NEW] libgpg-error/1.45-2 fails autopkgtest on i386
Public bug reported: The failure was introduced by this change in Debian: https://salsa.debian.org/debian/libgpg-error/-/commit/0c11fe4ae16c2800e13758ff1ee64c561354e628 It started to fail for i386 on autopkgtest.u.c: https://autopkgtest.ubuntu.com/packages/libgpg-error/kinetic/i386 https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/i386/libg/libgpg-error/20220523_114919_e3142@/log.gz The relevant log is this: ``` The following packages have unmet dependencies: builddeps:/tmp/autopkgtest.VMjBik/1-autopkgtest-satdep.dsc:i386 : Depends: gcc-mingw-w64-x86-64:i386 but it is not installable E: Unable to correct problems, you have held broken packages. win64 FAIL badpkg [...] autopkgtest [11:49:03]: summary win32 SKIP Test lists explicitly supported architectures, but the current architecture amd64 isn't listed. win64 FAIL badpkg blame: libgpg-error badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. build PASS ``` As can be seen, the i386/win32 test is skipped while amd64/win64 is executed and fails with "badpkg" error due to not being able to install "gcc-mingw-w64-x86-64:i386". = Even if that can be fixed (https://code.launchpad.net/~ubuntu-release/autopkgtest/+git/development/+merge/423176), the "win64" test is skipped now and "win32" executed, "win32" fails with a "badpkg" error, which probably needs solving in the archive. $ PYTHONPATH=lib/ runner/autopkgtest libgpg-error --apt-pocket=proposed=src:libgpg-error -a i386 -U -- qemu /data/autopkgtest-kinetic-amd64.img [...] win64 SKIP Test lists explicitly supported architectures, but the current architecture i386 isn't listed. [...] The following packages have unmet dependencies: builddeps:/tmp/autopkgtest.8Maso6/1-autopkgtest-satdep.dsc:i386 : Depends: gcc-mingw-w64-i686:i386 but it is not installable Depends: wine32:i386 but it is not going to be installed E: Unable to correct problems, you have held broken packages. win32 FAIL badpkg blame: libgpg-error badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. Full log: https://paste.ubuntu.com/p/JYHrJpMGbn/ ** Affects: libgpg-error (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Merge proposal linked: https://code.launchpad.net/~ubuntu-release/autopkgtest/+git/development/+merge/423176 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975673 Title: libgpg-error/1.45-2 fails autopkgtest on i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgpg-error/+bug/1975673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967013] Re: Bionic update: upstream stable patchset 2022-03-29
This commit is suspected to cause issues for many users: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/kernel/module.c?h=Ubuntu-4.15.0-177.186&id=3879f4364139acb2bd3932e6a15994f109c49d6b Please see this bug ticket: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967013 Title: Bionic update: upstream stable patchset 2022-03-29 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Invalid => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux-oem-5.14 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Kinetic) Status: New => Invalid ** Tags added: 13 5. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975675] [NEW] GUI problem from {Online Accounts} Google Microsoft and {Ubuntu Desktop Guide}
Public bug reported:
raspberry pi 4 (8GB memory, USB SSD boot) ubuntu 64 with 2 monitors
Description:Ubuntu 22.04 LTS
Release:22.04
Seems like the GUI for {Online Accounts} Google Microsoft and {Ubuntu Desktop
Guide} can't render themselves correctly. Meanwhile, the Firefox can play
YouTube on 2 monitors without any problem.
Please refer to the attached snapshot.
apt-cache policy
Package files:
100 /var/lib/dpkg/status
release a=now
500 http://ports.ubuntu.com/ubuntu-ports jammy-security/universe arm64 Packages
release
v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=universe,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy-security/restricted arm64
Packages
release
v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=restricted,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy-security/main arm64 Packages
release v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=main,b=arm64
origin ports.ubuntu.com
100 http://ports.ubuntu.com/ubuntu-ports jammy-backports/universe arm64
Packages
release
v=22.04,o=Ubuntu,a=jammy-backports,n=jammy,l=Ubuntu,c=universe,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe arm64 Packages
release
v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=universe,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/restricted arm64
Packages
release
v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=restricted,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages
release v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=main,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy/multiverse arm64 Packages
release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=multiverse,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy/universe arm64 Packages
release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=universe,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy/restricted arm64 Packages
release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=restricted,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages
release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=main,b=arm64
origin ports.ubuntu.com
Pinned packages:
librados2 -> 17.2.0-0ubuntu0.22.04.1 with priority 1
crimson-osd -> 17.2.0-0ubuntu0.22.04.1 with priority 1
ec2-instance-connect -> 1.1.14-0ubuntu1.1 with priority 1
python3-etcd3gw -> 0.2.5-1ubuntu1.22.04.1 with priority 1
budgie-control-center-data -> 1.0.1-2ubuntu2 with priority 1
xdg-desktop-portal-tests -> 1.14.3-0ubuntu2.22.04.1 with priority 1
budgie-desktop -> 10.6.1-1ubuntu1~22.04 with priority 1
python-etcd3gw-doc -> 0.2.5-1ubuntu1.22.04.1 with priority 1
ceph-volume -> 17.2.0-0ubuntu0.22.04.1 with priority 1
evolution-dev -> 3.44.1-0ubuntu1 with priority 1
libbudgietheme0 -> 10.6.1-1ubuntu1~22.04 with priority 1
rbd-fuse -> 17.2.0-0ubuntu0.22.04.1 with priority 1
ceph-mgr-modules-core -> 17.2.0-0ubuntu0.22.04.1 with priority 1
libgtk-4-common -> 4.6.3+ds1-0ubuntu1 with priority 1
ceph-grafana-dashboards -> 17.2.0-0ubuntu0.22.04.1 with priority 1
gir1.2-clutter-gst-3.0 -> 3.0.27-2ubuntu1 with priority 1
libgail-3-dev -> 3.24.33-1ubuntu2 with priority 1
libgail-3-doc -> 3.24.33-1ubuntu2 with priority 1
ceph-resource-agents -> 17.2.0-0ubuntu0.22.04.1 with priority 1
ceph-base -> 17.2.0-0ubuntu0.22.04.1 with priority 1
libsqlite3-mod-ceph-dev -> 17.2.0-0ubuntu0.22.04.1 with priority 1
libjson-c-dev -> 0.15-3~ubuntu1.22.04.1 with priority 1
libjson-c-doc -> 0.15-3~ubuntu1.22.04.1 with priority 1
xdg-desktop-portal-dev -> 1.14.3-0ubuntu2.22.04.1 with priority 1
gstreamer1.0-clutter-3.0 -> 3.0.27-2ubuntu1 with priority 1
python3-ceph-common -> 17.2.0-0ubuntu0.22.04.1 with priority 1
librbd1 -> 17.2.0-0ubuntu0.22.04.1 with priority 1
gir1.2-budgie-1.0 -> 10.6.1-1ubuntu1~22.04 with priority 1
libraven0 -> 10.6.1-1ubuntu1~22.04 with priority 1
librgw2 -> 17.2.0-0ubuntu0.22.04.1 with priority 1
libusb-1.0-0-dev -> 2:1.0.25-1ubuntu2 with priority 1
libclutter-gst-3.0-dev -> 3.0.27-2ubuntu1 with priority 1
libclutter-gst-3.0-doc -> 3.0.27-2ubuntu1 with priority 1
ceph-mgr-cephadm -> 17.2.0-0ubuntu0.22.04.1 with priority 1
libcephfs-dev -> 17.2.0-0ubuntu0.22.04.1 with priority 1
budgie-control-center -> 1.0.1-2ubuntu2 with priority 1
ceph-common -> 17.2.0-0ubuntu0.22.04.1 with priority 1
libusb-1.0-doc -> 2:1.0.25-1ubuntu2 with priority 1
libcephfs-jni -> 17.2.0-0ubuntu0.22.04.1 with priority 1
evolution-plugins -> 3.44.1-0ubuntu1 wit
[Bug 1975399] Re: FATAL FwdState::noteDestinationsEnd exception: opening()
Hi Bryce, Thank you for the prompt response. I wasn't able to reproduce the crashes with a script yet, however, I have been able to isolate the issue a bit more. It seems like it only happens when ssl-bump is used - I'm using the newly introduced squid-openssl package. I've attached a config file which is based on the following entry in Squid's FAQ and didn't cause the same crashes in squid 4.x (compiled with openssl): https://wiki.squid-cache.org/SquidFaq/WindowsUpdate Using this config requires the squid-openssl package and the below commands must be executed before starting the service, otherwise squid gets stuck in a crash loop: --- /usr/lib/squid/security_file_certgen -c -s /var/spool/squid/ssl_db -M 4MB && chown -R proxy:proxy /var/spool/squid/ssl_db --- If I set the proxy config on my Windows laptop to point at the squid proxy running with the attached config on Ubuntu 22.04, squid crashes and restarts as soon as I try to open Outlook or Word. I cannot reproduce this issue with a config where ssl-bump is not used, even when using the squid-openssl package. I tried using a Python script to simultaneously call some of the https URLs that I found in the logs, but squid didn't crash that way. I'll try reproducing it using an app on an Ubuntu desktop VM and keep trying with the script as well. ** Attachment added: "sample squid config" https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1975399/+attachment/5592813/+files/squid.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975399 Title: FATAL FwdState::noteDestinationsEnd exception: opening() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1975399/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Description changed: + [Impact] + + + [Fix] + + + [Test] + + + [Where problems could occur] + + [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 - # selftests: net: test_vxlan_under_vrf.sh - # Checking HV connectivity [ OK ] - # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] - not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 - + # selftests: net: test_vxlan_under_vrf.sh + # Checking HV connectivity [ OK ] + # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] + not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959548] Re: [22.04 FEAT] zcrypt DD: Exploitation Support of new IBM Z Crypto Hardware (s390-tools part)
** Description changed: + SRU Justification: + == + + [Impact] + + * This in a hardware enablement SRU, +and mainly adds support for CryptoExpress 8S adapters +to the s390-tools package. + + * With that the new options 'show_serialnumbers', +'--accelonly', '--ccaonly' and '--ep11only' +are introduced to the lszcrypt tool. + + * In addition lszcrypt now supports the checkstop state +of a crypto card, that is provided by the 'chkstop' +attribute in the sysfs of newer kernels. + + * And lszcrypt now shows the AP bus msg size limit capability, +which is needed for new adapter cards. + + * New codes for zcryptstats are needed as well. + + [Test Plan] + + * Prepare an IBM z16 LPAR with Ubuntu 22.04 (incl. this patch) +that has an CryptoExpress 8S adapter attached to it +and at least one crypto domain online and available. + + * Call 'lszcrypt -V' and check the 2nd column called 'type' +and the last column called 'driver'. + + * If both have entries that start with "cex8..." then the new +CryptoExpress 8S driver is active and the new card is detected +and can be used (and the new features exploited). + + * If the driver listed there is older than 'cex8', +than the new card is probably detected as an older type +and it runs in toleration mode only. + + * Try and test the new options. + + * Run zcryptstats and with that make use of the new codes +(which actually means add CEX8S support for zcryptstats). + + * And finally extending lszcrypt's capabilities and +make it aware of CEX8S. + + [Where problems could occur] + + * The new declarations, initializations or the scan for the serial numbers +of the devices could fail, which would lead to a non-working +or even erroneous new '-s' option. + + * The new filter mechanism could be broken and now incorrect +resources, but this would be limited to the new options +'--cardonly' and '--queueonly'. + + * The same applies to the new options +'--accelonly', '--ccaonly' and '--ep11only'. + + * The handling of the new chkstop state can be confusing or might be +broken, which may lead to wrong state representations. + + * The new AP bus msg size limit mights be incorrectly calculated, +which leads to a wrong size and with that certain feature not to work. + + * The new zcryptstats might come with wrong or mixed codes, +which would lead to wrong and misleading statistics, +or even break zcryptstats. + + * Regarding the lszcrypt capability extension there is no danger +since an existing case statement is extended and the case content +reused unchanged. + + * All this is s390x specific, and only affects the handling for +CryptoExpress 8S adapters. It won't have an impact on CPACF. + + [Other Info] + + * The net CEX8S support is provided by commits bcbb6fca and b16a6d4f. +All others can be considered as pre-requisites. + + __ + zcrypt DD: Exploitation Support of new IBM Z Crypto Hardware - s390-tools part ** Changed in: s390-tools (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Frank Heimes (fheimes) ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959548 Title: [22.04 FEAT] zcrypt DD: Exploitation Support of new IBM Z Crypto Hardware (s390-tools part) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974097] Re: KSystemLog only launches if run from a terminal - attempting to run from the application menu or from KRunner silently fails
*** This bug is a duplicate of bug 1965439 *** https://bugs.launchpad.net/bugs/1965439 ** This bug has been marked a duplicate of bug 1965439 applications can no longer launch when called by kdesu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974097 Title: KSystemLog only launches if run from a terminal - attempting to run from the application menu or from KRunner silently fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ksystemlog/+bug/1974097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968318] Re: [sru] ceph 17.2.0 (Quincy) release
focal-yoga/proposed == Totals == Ran: 182 tests in 1541.3454 sec. - Passed: 167 - Skipped: 12 - Expected Fail: 0 - Unexpected Success: 0 - Failed: 3 Sum of execute time for each test: 1522.4674 sec. same three failures -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968318 Title: [sru] ceph 17.2.0 (Quincy) release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1968318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967286] Re: KSystemLog is not launched
*** This bug is a duplicate of bug 1965439 *** https://bugs.launchpad.net/bugs/1965439 ** This bug is no longer a duplicate of bug 1962455 Unable to authenticate to KSystemLog graphical app Kubuntu Jammy ** This bug has been marked a duplicate of bug 1965439 applications can no longer launch when called by kdesu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967286 Title: KSystemLog is not launched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1967286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964439] Re: KSystemLog does not launch from Application Launcher menu
*** This bug is a duplicate of bug 1965439 *** https://bugs.launchpad.net/bugs/1965439 ** This bug is no longer a duplicate of bug 1962455 Unable to authenticate to KSystemLog graphical app Kubuntu Jammy ** This bug has been marked a duplicate of bug 1965439 applications can no longer launch when called by kdesu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964439 Title: KSystemLog does not launch from Application Launcher menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1964439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962455] Re: Unable to authenticate to KSystemLog graphical app Kubuntu Jammy
*** This bug is a duplicate of bug 1965439 *** https://bugs.launchpad.net/bugs/1965439 ** This bug has been marked a duplicate of bug 1965439 applications can no longer launch when called by kdesu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962455 Title: Unable to authenticate to KSystemLog graphical app Kubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ksystemlog/+bug/1962455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975460] Re: ubuntu 22.04 kernel 5.15.0.x iwlwifi cannot load firmware, wifi card does not work: Intel Corporation Wireless 7260
Thanks for the bug report. Can you test the kernel from here: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15/ Specifically: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15/amd64/linux-image-unsigned-5.15.0-051500-generic_5.15.0-051500.202110312130_amd64.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15/amd64/linux-modules-5.15.0-051500-generic_5.15.0-051500.202110312130_amd64.deb And post the output of dmesg? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975460 Title: ubuntu 22.04 kernel 5.15.0.x iwlwifi cannot load firmware, wifi card does not work: Intel Corporation Wireless 7260 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965439] Re: software-properties-qt can no longer launch when called by kdesu
** No longer affects: software-properties (Ubuntu) ** No longer affects: software-properties (Ubuntu Impish) ** No longer affects: software-properties (Ubuntu Jammy) ** No longer affects: policykit-1 (Ubuntu Impish) ** No longer affects: policykit-1 (Ubuntu Jammy) ** No longer affects: policykit-1 (Ubuntu) ** Summary changed: - software-properties-qt can no longer launch when called by kdesu + applications can no longer launch when called by kdesu ** Also affects: ubuntustudio-default-settings via https://bugs.kde.org/show_bug.cgi?id=452532 Importance: Unknown Status: Unknown ** No longer affects: ubuntustudio-default-settings ** No longer affects: ubuntustudio-default-settings (Ubuntu Impish) ** No longer affects: sudo (Ubuntu Impish) ** No longer affects: kubuntu-settings (Ubuntu Impish) ** No longer affects: kdesu (Ubuntu Impish) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: applications can no longer launch when called by kdesu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975678] [NEW] Netplan generates the wrong YAML value when setting activation-mode=off
Public bug reported:
When setting activation-mode=off on Ubuntu 20.04/Ubuntu Core 20, netplan
generates the incorrect value in the YAML file (activation-mode: false),
causing it to fail due to incorrect syntax.
$ sudo netplan set ethernets.eth0.activation-mode=off
Traceback (most recent call last):
File "/usr/sbin/netplan", line 23, in
netplan.main()
File "/usr/share/netplan/netplan/cli/core.py", line 50, in main
self.run_command()
File "/usr/share/netplan/netplan/cli/utils.py", line 247, in run_command
self.func()
File "/usr/share/netplan/netplan/cli/commands/set.py", line 55, in run
self.run_command()
File "/usr/share/netplan/netplan/cli/utils.py", line 247, in run_command
self.func()
File "/usr/share/netplan/netplan/cli/commands/set.py", line 126, in
command_set
self.write_file(subtree, hint + '.yaml', self.root_dir)
File "/usr/share/netplan/netplan/cli/commands/set.py", line 193, in write_file
libnetplan.netplan_parse(tmpp)
File "/usr/share/netplan/netplan/libnetplan.py", line 64, in netplan_parse
raise Exception(err.contents.message.decode('utf-8'))
Exception: /tmp/netplan-set_o73ewgp4/etc/netplan/50-cloud-init.yaml:4:24: Error
in network definition: Value of 'activation-mode' needs to be 'manual' or 'off'
activation-mode: false
^
** Affects: netplan.io (Ubuntu)
Importance: Medium
Status: Triaged
** Affects: netplan.io (Ubuntu Focal)
Importance: Medium
Status: Triaged
** Affects: netplan.io (Ubuntu Impish)
Importance: Undecided
Status: New
** Affects: netplan.io (Ubuntu Jammy)
Importance: Undecided
Status: New
** Affects: netplan.io (Ubuntu Kinetic)
Importance: Medium
Status: Triaged
** Tags: rls-ff-incoming rls-kk-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975678
Title:
Netplan generates the wrong YAML value when setting activation-
mode=off
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1975678/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975678] Re: Netplan generates the wrong YAML value when setting activation-mode=off
** Also affects: netplan.io (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Kinetic) 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/1975678 Title: Netplan generates the wrong YAML value when setting activation- mode=off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1975678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975678] Re: Netplan generates the wrong YAML value when setting activation-mode=off
** Description changed:
- When setting activation-mode=off, netplan generates the incorrect value
- in the YAML file (activation-mode: false), causing it to fail due to
- incorrect syntax.
+ When setting activation-mode=off on Ubuntu 20.04/Ubuntu Core 20, netplan
+ generates the incorrect value in the YAML file (activation-mode: false),
+ causing it to fail due to incorrect syntax.
$ sudo netplan set ethernets.eth0.activation-mode=off
Traceback (most recent call last):
- File "/usr/sbin/netplan", line 23, in
- netplan.main()
- File "/usr/share/netplan/netplan/cli/core.py", line 50, in main
- self.run_command()
- File "/usr/share/netplan/netplan/cli/utils.py", line 247, in run_command
- self.func()
- File "/usr/share/netplan/netplan/cli/commands/set.py", line 55, in run
- self.run_command()
- File "/usr/share/netplan/netplan/cli/utils.py", line 247, in run_command
- self.func()
- File "/usr/share/netplan/netplan/cli/commands/set.py", line 126, in
command_set
- self.write_file(subtree, hint + '.yaml', self.root_dir)
- File "/usr/share/netplan/netplan/cli/commands/set.py", line 193, in
write_file
- libnetplan.netplan_parse(tmpp)
- File "/usr/share/netplan/netplan/libnetplan.py", line 64, in netplan_parse
- raise Exception(err.contents.message.decode('utf-8'))
+ File "/usr/sbin/netplan", line 23, in
+ netplan.main()
+ File "/usr/share/netplan/netplan/cli/core.py", line 50, in main
+ self.run_command()
+ File "/usr/share/netplan/netplan/cli/utils.py", line 247, in run_command
+ self.func()
+ File "/usr/share/netplan/netplan/cli/commands/set.py", line 55, in run
+ self.run_command()
+ File "/usr/share/netplan/netplan/cli/utils.py", line 247, in run_command
+ self.func()
+ File "/usr/share/netplan/netplan/cli/commands/set.py", line 126, in
command_set
+ self.write_file(subtree, hint + '.yaml', self.root_dir)
+ File "/usr/share/netplan/netplan/cli/commands/set.py", line 193, in
write_file
+ libnetplan.netplan_parse(tmpp)
+ File "/usr/share/netplan/netplan/libnetplan.py", line 64, in netplan_parse
+ raise Exception(err.contents.message.decode('utf-8'))
Exception: /tmp/netplan-set_o73ewgp4/etc/netplan/50-cloud-init.yaml:4:24:
Error in network definition: Value of 'activation-mode' needs to be 'manual' or
'off'
- activation-mode: false
-^
+ activation-mode: false
+ ^
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975678
Title:
Netplan generates the wrong YAML value when setting activation-
mode=off
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1975678/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975678] Re: Netplan generates the wrong YAML value when setting activation-mode=off
** Changed in: netplan.io (Ubuntu Kinetic) Status: New => Triaged ** Changed in: netplan.io (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: netplan.io (Ubuntu Focal) Status: New => Triaged ** Changed in: netplan.io (Ubuntu Focal) Importance: Undecided => Medium ** Tags added: rls-ff-incoming rls-kk-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975678 Title: Netplan generates the wrong YAML value when setting activation- mode=off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1975678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970957] Re: suspend problem
L13 Yoga Gen 2 is also affected, both in X11 and Wayland. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970957 Title: suspend problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Summary changed: - test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) + test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975678] Re: Netplan generates the wrong YAML value when setting activation-mode=off
This seems to be due to the (old) Python YAML parser being in conflict
with libnetplan's actual C YAML parser.
Apparently pyyaml interprets "off" as a boolean ('False') by default in
yaml.safe_load(value) (`set_tree = self.parse_key(key,
yaml.safe_load(value))`), while it is supposed to be an actual string
("off") for activation-mode.
Looks like it was broken ever since netplan set was introduced (v0.101)
and just recently got fixed via
https://github.com/canonical/netplan/pull/254
(https://github.com/canonical/netplan/commit/bdb4f9846c8f40275c09a28bed04d8436cbbeffc
to be specific)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975678
Title:
Netplan generates the wrong YAML value when setting activation-
mode=off
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1975678/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975678] Re: Netplan generates the wrong YAML value when setting activation-mode=off
A quick workaround seems to be quoting the parameters like this: netplan set "ethernets.eth0.activation-mode='off'" ** Changed in: netplan.io (Ubuntu Kinetic) Importance: Medium => Low ** Changed in: netplan.io (Ubuntu Focal) Importance: Medium => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975678 Title: Netplan generates the wrong YAML value when setting activation- mode=off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1975678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975675] Re: GUI problem from {Online Accounts} Google Microsoft and {Ubuntu Desktop Guide}
*** This bug is a duplicate of bug 1924251 ***
https://bugs.launchpad.net/bugs/1924251
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975675
Title:
GUI problem from {Online Accounts} Google Microsoft and {Ubuntu
Desktop Guide}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1975675/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input
Oh please remove all the "acpi*" kernel parameters which mess with the ACPI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971933 Title: [Regression] Unable to wake laptop using trackpad input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975675] Re: GUI problem from {Online Accounts} Google Microsoft and {Ubuntu Desktop Guide}
*** This bug is a duplicate of bug 1924251 ***
https://bugs.launchpad.net/bugs/1924251
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1924251, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.
** Package changed: xorg (Ubuntu) => ubuntu
** This bug has been marked a duplicate of bug 1924251
Embedded browser display corruption under Wayland on Pi desktop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975675
Title:
GUI problem from {Online Accounts} Google Microsoft and {Ubuntu
Desktop Guide}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1975675/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970943] Re: OpenVPN connection fails with smartcard provided private key; please update pkcs11-helper
Hey there, I have performed the following steps to test the proposed fix: 1) removed self-compiled pkcs11-helper version 1.29.0 from my system (hotfix) 2) tried to connect to an OpenVPN with smartcard authentification => failed as expected 3) enabled jammy-proposed 4) installed libpkcs11-helper1 1.28-1ubuntu0.22.04.1 5) tried to connect to an OpenVPN with smartcard authentification => connection succeeded I therefore conclude that this update fixes the issue; thanks! ** Tags removed: verification-needed-jammy ** 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/1970943 Title: OpenVPN connection fails with smartcard provided private key; please update pkcs11-helper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pkcs11-helper/+bug/1970943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975673] Re: libgpg-error/1.45-2 fails autopkgtest on i386
I think there's another problem: it fails to install gcc-mingw-w64-i686 because autopkgtest tries to install gcc-mingw-w64-i686:i386 which does not exist since it only exists as gcc-mingw-w64-i686:all. I added :all to the test dependency, and then it works, the test passes correctly on i386 \o/ But I'll come up with the proper patch in autopkgtest: it should try :$arch first and then :all in case it does not work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975673 Title: libgpg-error/1.45-2 fails autopkgtest on i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgpg-error/+bug/1975673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975566] Re: radeon / amdgpu bad performance or panics
aiui the radv vulkan driver requires amdgpu kernel driver, so I don't know how you could have it working before the upgrade. the default driver for SI cards is radeon, that won't change so essentially we don't support vulkan on those -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975566 Title: radeon / amdgpu bad performance or panics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1975566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975669] Re: USB devices are not working on Raspberry pi zero 2 with arm64 image
Works fine for me: $ cat /proc/device-tree/model Raspberry Pi Zero 2 Rev 1.0 $ uname -a Linux rpi-zero2-rev1d0-2c3c 5.15.0-1008-raspi #8-Ubuntu SMP PREEMPT Thu May 19 11:58:51 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux $ lsusb Bus 001 Device 002: ID 2357:0601 TP-Link UE300 10/100/1000 LAN (ethernet mode) [Realtek RTL8153] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975669 Title: USB devices are not working on Raspberry pi zero 2 with arm64 image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1975669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974056] Re: iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless-bitwise_0 fails on s390x
--- Comment From boris.m...@de.ibm.com 2022-05-25 04:39 EDT--- Description by Canonical (LP#1974056): command17 FAIL stderr: W: [FAILED] ././testcases/nft-only/0009-needless- bitwise_0: expected 0 but got 1 this can be reproduced with: pull-lp-source iptables cd iptables-1.8.7/ chmod +x ./iptables/tests/shell/testcases/iptables/0007-zero-counters_0 cd iptables/tests/shell sudo ./run-tests.sh --host ** Tags added: architecture-s39064 bugnameltc-198367 severity-high targetmilestone-inin2204 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974056 Title: iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless- bitwise_0 fails on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/iptables/+bug/1974056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Description changed: [Impact] + The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: + Running 'make run_tests -C net TEST_PROGS=test_vxlan_under_vrf.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' + make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' + make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install + make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' +INSTALL ./usr/include + make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' + TAP version 13 + 1..1 + # selftests: net: test_vxlan_under_vrf.sh + # Checking HV connectivity[ OK ] + # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] + not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 [Fix] + * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test + * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case + The first patch can be cherry-picked to Impish 5.13 and F-oem-5.14. + + Note that this test is not failing on F-oem-5.14, but it's better to + have it applied to reduce the maintenance cost. + + After the first patch was applied, we will need the second patch to solve the another failure on Impish 5.13, which we made it an expected failure (XFAIL) with SAUCE patches: + Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] [Test] + Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test can pass without any issue: [Where problems could occur] [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959548] Re: [22.04 FEAT] zcrypt DD: Exploitation Support of new IBM Z Crypto Hardware (s390-tools part)
** Description changed: SRU Justification: == [Impact] - * This in a hardware enablement SRU, -and mainly adds support for CryptoExpress 8S adapters -to the s390-tools package. + * This in a hardware enablement SRU, + and mainly adds support for CryptoExpress 8S adapters + to the s390-tools package. - * With that the new options 'show_serialnumbers', -'--accelonly', '--ccaonly' and '--ep11only' -are introduced to the lszcrypt tool. + * With that the new options 'show_serialnumbers', + '--accelonly', '--ccaonly' and '--ep11only' + are introduced to the lszcrypt tool. - * In addition lszcrypt now supports the checkstop state -of a crypto card, that is provided by the 'chkstop' -attribute in the sysfs of newer kernels. + * In addition lszcrypt now supports the checkstop state + of a crypto card, that is provided by the 'chkstop' + attribute in the sysfs of newer kernels. - * And lszcrypt now shows the AP bus msg size limit capability, -which is needed for new adapter cards. + * And lszcrypt now shows the AP bus msg size limit capability, + which is needed for new adapter cards. - * New codes for zcryptstats are needed as well. + * New codes for zcryptstats are needed as well. [Test Plan] - * Prepare an IBM z16 LPAR with Ubuntu 22.04 (incl. this patch) -that has an CryptoExpress 8S adapter attached to it -and at least one crypto domain online and available. + * Prepare an IBM z16 LPAR with Ubuntu 22.04 (incl. this patch) + that has an CryptoExpress 8S adapter attached to it + and at least one crypto domain online and available. - * Call 'lszcrypt -V' and check the 2nd column called 'type' -and the last column called 'driver'. + * Call 'lszcrypt -V' and check the 2nd column called 'type' + and the last column called 'driver'. - * If both have entries that start with "cex8..." then the new -CryptoExpress 8S driver is active and the new card is detected -and can be used (and the new features exploited). + * If both have entries that start with "cex8..." then the new + CryptoExpress 8S driver is active and the new card is detected + and can be used (and the new features exploited). - * If the driver listed there is older than 'cex8', -than the new card is probably detected as an older type -and it runs in toleration mode only. + * If the driver listed there is older than 'cex8', + than the new card is probably detected as an older type + and it runs in toleration mode only. - * Try and test the new options. + * Try and test the new options. - * Run zcryptstats and with that make use of the new codes -(which actually means add CEX8S support for zcryptstats). + * Run zcryptstats and with that make use of the new codes + (which actually means add CEX8S support for zcryptstats). - * And finally extending lszcrypt's capabilities and -make it aware of CEX8S. + * And finally extending lszcrypt's capabilities and + make it aware of CEX8S. [Where problems could occur] - * The new declarations, initializations or the scan for the serial numbers -of the devices could fail, which would lead to a non-working -or even erroneous new '-s' option. + * The new declarations, initializations or the scan for the serial numbers + of the devices could fail, which would lead to a non-working + or even erroneous new '-s' option. - * The new filter mechanism could be broken and now incorrect -resources, but this would be limited to the new options -'--cardonly' and '--queueonly'. + * The new filter mechanism could be broken and now incorrect + resources, but this would be limited to the new options + '--cardonly' and '--queueonly'. - * The same applies to the new options -'--accelonly', '--ccaonly' and '--ep11only'. + * The same applies to the new options + '--accelonly', '--ccaonly' and '--ep11only'. - * The handling of the new chkstop state can be confusing or might be -broken, which may lead to wrong state representations. + * The handling of the new chkstop state can be confusing or might be + broken, which may lead to wrong state representations. - * The new AP bus msg size limit mights be incorrectly calculated, -which leads to a wrong size and with that certain feature not to work. + * The new AP bus msg size limit mights be incorrectly calculated, + which leads to a wrong size and with that certain feature not to work. - * The new zcryptstats might come with wrong or mixed codes, -which would lead to wrong and misleading statistics, -or even break zcryptstats. + * The new zcryptstats might come with wrong or mixed codes, + which would lead to wrong and misleading statistics, + or even break zcryptstats. - * Regarding the lszcrypt capability extension there is no danger -since an existing case statement is extended and the case c
[Bug 1871148] Re: services start before apparmor profiles are loaded
$ systemctl status snapd.apparmor ○ snapd.apparmor.service - Load AppArmor profiles managed internally by snapd Loaded: loaded (/lib/systemd/system/snapd.apparmor.service; disabled; vendor preset: enabled) Active: inactive (dead) I do NOT remember having manually disabled this service. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871148 Title: services start before apparmor profiles are loaded To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Description changed: [Impact] The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: - Running 'make run_tests -C net TEST_PROGS=test_vxlan_under_vrf.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' - make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' - make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install - make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' -INSTALL ./usr/include - make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' - TAP version 13 - 1..1 - # selftests: net: test_vxlan_under_vrf.sh - # Checking HV connectivity[ OK ] - # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] - not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 + Running 'make run_tests -C net TEST_PROGS=test_vxlan_under_vrf.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' + make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' + make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install + make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' + INSTALL ./usr/include + make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' + TAP version 13 + 1..1 + # selftests: net: test_vxlan_under_vrf.sh + # Checking HV connectivity[ OK ] + # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] + not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test - * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case + * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case The first patch can be cherry-picked to Impish 5.13 and F-oem-5.14. Note that this test is not failing on F-oem-5.14, but it's better to have it applied to reduce the maintenance cost. After the first patch was applied, we will need the second patch to solve the another failure on Impish 5.13, which we made it an expected failure (XFAIL) with SAUCE patches: Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] [Test] Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test can pass without any issue: - + Checking HV connectivity [ OK ] + Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] + Check VM connectivity through VXLAN (underlay in a VRF)[ OK ] [Where problems could occur] + Change limit to test cases, should not have any real impact to kernel functions. But if these fixes are incorrect we will see failures in our regression-testing report. The worst scenario is getting false-negative results. [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 ** Description changed: [Impact] The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: - Running 'make run_tests -C net TEST_PROGS=test_vxlan_under_vrf.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' - make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' - make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install - make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' - INSTALL ./usr/include - make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' - TAP version 13 - 1..1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity[ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case The first patch can be cherry-picked to Impish 5.13 and F-oem-5.14. Note that this test is not failing on F-oem-5.14, but it's better to have it applied to reduce the maintenance cost. After the first patch was applied, we will need the second patch to solve the another failure on Impish 5.13, which we made it an expected failure (XFAIL) with SAUCE patches: Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] [Test] Patch tested on Impish 5.13 and F-
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Description changed: [Impact] The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity[ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case - The first patch can be cherry-picked to Impish 5.13 and F-oem-5.14. + The first patch (e7e4785f) can be cherry-picked to Impish 5.13 and + F-oem-5.14. Note that this test is not failing on F-oem-5.14, but it's better to have it applied to reduce the maintenance cost. After the first patch was applied, we will need the second patch on Impish 5.13 to solve the another failure, which we made it an expected failure (XFAIL) with SAUCE patches: Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] - F-oem-5.14 has already got this one applied. + The second patch (b50d3b46) can be cherry-picked with must be applied + with -C2 due to our SAUCE patches. F-oem-5.14 has already got this one + applied. [Test] Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test can pass without any issue: Checking HV connectivity [ OK ] Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] Check VM connectivity through VXLAN (underlay in a VRF)[ OK ] [Where problems could occur] Change limit to test cases, should not have any real impact to kernel functions. But if these fixes are incorrect we will see failures in our regression-testing report. The worst scenario is getting false-negative results. [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967116] Re: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes
I have tested the kernel 5.15.0-32.33 with the patches mentioned in bug description. Looks good. ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967116 Title: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975566] Re: radeon / amdgpu bad performance or panics
Before the upgrade it was an Intel GPU. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975566 Title: radeon / amdgpu bad performance or panics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1975566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960119] Re: [22.04 FEAT] Add new CPU-MF Counters for new IBM Z Hardware - s390-tools part
A test build in PPA was done and is available here: https://launchpad.net/~fheimes/+archive/ubuntu/lp1960119 ** Changed in: ubuntu-z-systems Status: New => In Progress ** Changed in: s390-tools (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/1960119 Title: [22.04 FEAT] Add new CPU-MF Counters for new IBM Z Hardware - s390-tools part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1960119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972853] Re: [MIR] lib*-perl
Review for Package: libindirect-perl [Summary] MIR team ACK This does not need a security review List of specific binary packages to be promoted to main: libindirect-perl Specific binary packages built, but NOT to be promoted to main: n/a [Duplication] There is no other package in main providing the same functionality. [Dependencies] OK: - no other Dependencies to MIR due to this - no -dev/-debug/-doc packages that need exclusion - No dependencies in main that are only superficially tested requiring more tests now. Problems: None [Embedded sources and static linking] OK: - no embedded source present - no static linking - does not have odd Built-Using entries - not a go package, no extra constraints to consider in that regard - No vendoring used, all Built-Using are in main Problems: None [Security] - history of CVEs does not look concerning - does not run a daemon as root - does not use webkit1,2 - does not use lib*v8 directly - does not open a port/socket - does not process arbitrary web content - does not use centralized online accounts - does not integrate arbitrary javascript into the desktop - does not deal with system authentication (eg, pam), etc) - does not deal with security attestation (secure boot, tpm, signatures) Problems: - does parse data formats (usually code in the current use, but not arbitrary and low attack surface) [Common blockers] OK: - does not FTBFS currently - does have a test suite that runs at build time - test suite fails will fail the build upon error. - does have a test suite that runs as autopkgtest - no special HW needed - no new python2 dependency Problems: None [Packaging red flags] OK: - Ubuntu does not carry a delta - symbols tracking not applicable for this kind of code. - d/watch is present and looks ok - Debian/Ubuntu update history is slow (matching upstream) - the current release is packaged - promoting this does not seem to cause issues for MOTUs that so far maintained the package - no massive Lintian warnings - d/rules is rather clean - It is not on the lto-disabled list Problems: - Upstream update history is slow, not sure how much we can rely on it. Those kind of packages often are without being a problem, but we have to be clear this seems like a non (much) active upstream. [Upstream red flags] OK: - no Errors/warnings during the build - no incautious use of malloc/sprintf (perl only) - no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH - no use of user nobody - no use of setuid - no important open bugs (crashers, etc) in Debian or Ubuntu - no dependency on webkit, qtwebkit, seed or libgoa-* - not part of the UI for extra checks - no translation present, but none needed for this case Problems: None ** Changed in: libindirect-perl (Ubuntu) Status: Confirmed => 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/1972853 Title: [MIR] lib*-perl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libindirect-perl/+bug/1972853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972853] Re: [MIR] lib*-perl
Review for Package: libobject-pad-perl [Summary] MIR team ACK This does not need a security review List of specific binary packages to be promoted to main: libobject-pad-perl Specific binary packages built, but NOT to be promoted to main: n/a [Duplication] There is no other package in main providing the same functionality. [Dependencies] OK: - no other Dependencies to MIR due to this - no -dev/-debug/-doc packages that need exclusion - No dependencies in main that are only superficially tested requiring more tests now. Problems: None [Embedded sources and static linking] OK: - no embedded source present - no static linking - does not have odd Built-Using entries - not a go package, no extra constraints to consider in that regard - No vendoring used, all Built-Using are in main Problems: None [Security] - history of CVEs does not look concerning - does not run a daemon as root - does not use webkit1,2 - does not use lib*v8 directly - does not open a port/socket - does not process arbitrary web content - does not use centralized online accounts - does not integrate arbitrary javascript into the desktop - does not deal with system authentication (eg, pam), etc) - does not deal with security attestation (secure boot, tpm, signatures) Problems: - does parse data formats (usually code in the current use, but not arbitrary and low attack surface) [Common blockers] OK: - does not FTBFS currently - does have a test suite that runs at build time - test suite fails will fail the build upon error. - does have a test suite that runs as autopkgtest - no special HW needed - no new python2 dependency Problems: None [Packaging red flags] OK: - Ubuntu does not carry a delta - symbols tracking not applicable for this kind of code. - d/watch is present and looks ok - Debian/Ubuntu update history is slow (matching upstream) - the current release is packaged - promoting this does not seem to cause issues for MOTUs that so far maintained the package - no massive Lintian warnings - d/rules is rather clean - It is not on the lto-disabled list Problems: - Upstream update history is slow, not sure how much we can rely on it. Those kind of packages often are without being a problem, but we have to be clear this seems like a non (much) active upstream. [Upstream red flags] OK: - no Errors/warnings during the build - no incautious use of malloc/sprintf (perl only) - no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH - no use of user nobody - no use of setuid - no important open bugs (crashers, etc) in Debian or Ubuntu - no dependency on webkit, qtwebkit, seed or libgoa-* - not part of the UI for extra checks - no translation present, but none needed for this case Problems: None ** Changed in: libobject-pad-perl (Ubuntu) Status: Confirmed => 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/1972853 Title: [MIR] lib*-perl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libindirect-perl/+bug/1972853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972853] Re: [MIR] lib*-perl
Review for Package: libunicode-escape-perl [Summary] MIR team NACK (outdated, unmaintained, alternatives in main) Unless there is a very strong explanation why this can't be done with the better alternatives this is a NACK. This does not need a security review List of specific binary packages to be promoted to main: libunicode-escape-perl Specific binary packages built, but NOT to be promoted to main: n/a Required TODOs: - give it a reasonable evaluation please if the alternate modules already in main like libunicode-utf8-perl might be sufficient for what the new dependency needs from libunicode-escape-perl. Modern perl also supports unicode natively are we sure this isn't just a (very) old dependency here? Also 0.0.2 since 2011, given there are alternatives I'm really not convinced we should use this. Recommended TODOs: - The package should get a team bug subscriber before being promoted [Duplication] There is no other package in main providing the same functionality. There are many similar ones though, like libstring-escape-perl for general string escaping. And libunicode-utf8-perl for encode/decode of unicode. Both are already in main. Also modern perl supports unicode directly, do we really need this? CPAN even has more https://metacpan.org/pod/Encode::Escape::Unicode there might be a proliferation going on, but all except the perl-integrated one have not seen updates in years. And if this would not be needed, then libunicode-string-perl also would not be needed to bepromoted/supported. I'll add a check for that as required TODO to ensure we are not just re-adding the same function. Especially since most of these libs seem outdated or at least rarely updated, it is better to carry fewer. [Dependencies] OK: - no other Dependencies to MIR due to this - no -dev/-debug/-doc packages that need exclusion - No dependencies in main that are only superficially tested requiring more tests now. Problems: None [Embedded sources and static linking] OK: - no embedded source present - no static linking - does not have odd Built-Using entries - not a go package, no extra constraints to consider in that regard - No vendoring used, all Built-Using are in main Problems: None [Security] - history of CVEs does not look concerning - does not run a daemon as root - does not use webkit1,2 - does not use lib*v8 directly - does not open a port/socket - does not process arbitrary web content - does not use centralized online accounts - does not integrate arbitrary javascript into the desktop - does not deal with system authentication (eg, pam), etc) - does not deal with security attestation (secure boot, tpm, signatures) Problems: - does parse data formats (usually docs in the current use, but not arbitrary and low attack surface) [Common blockers] OK: - does not FTBFS currently - does have a test suite that runs at build time - test suite fails will fail the build upon error. - does have a test suite that runs as autopkgtest - no special HW needed - no new python2 dependency Problems: None [Packaging red flags] OK: - Ubuntu does not carry a delta - symbols tracking not applicable for this kind of code. - d/watch is present and looks ok - Debian/Ubuntu update history is slow (matching upstream) - the current release is packaged - promoting this does not seem to cause issues for MOTUs that so far maintained the package - no massive Lintian warnings - d/rules is rather clean - It is not on the lto-disabled list Problems: - Upstream update history is slow, not sure how much we can rely on it. Those kind of packages often are without being a problem, but we have to be clear this seems like a non (much) active upstream. This package in particular 0.0.2 since 2011, given there are alternatives now I'm really not convinced we should use this. [Upstream red flags] OK: - no Errors/warnings during the build - no incautious use of malloc/sprintf (perl only) - no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH - no use of user nobody - no use of setuid - no important open bugs (crashers, etc) in Debian or Ubuntu - no dependency on webkit, qtwebkit, seed or libgoa-* - not part of the UI for extra checks - no translation present, but none needed for this case Problems: None ** Changed in: libunicode-escape-perl (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972853 Title: [MIR] lib*-perl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libindirect-perl/+bug/1972853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972853] Re: [MIR] lib*-perl
Review for Package: libxs-parse-sublike-perl [Summary] MIR team ACK under the constraint to resolve the below listed required TODOs and as much as possible having a look at the recommended TODOs. This does not need a security review List of specific binary packages to be promoted to main: libxs-parse-sublike-perl Specific binary packages built, but NOT to be promoted to main: n/a Required TODOs: - the autopkgtest is broken since forever on all but armhf, please fix this Recommended TODOs: - The package should get a team bug subscriber before being promoted [Duplication] There is no other package in main providing the same functionality. [Dependencies] OK: - no other Dependencies to MIR due to this - no -dev/-debug/-doc packages that need exclusion - No dependencies in main that are only superficially tested requiring more tests now. Problems: None [Embedded sources and static linking] OK: - no embedded source present - no static linking - does not have odd Built-Using entries - not a go package, no extra constraints to consider in that regard - No vendoring used, all Built-Using are in main Problems: None [Security] - history of CVEs does not look concerning - does not run a daemon as root - does not use webkit1,2 - does not use lib*v8 directly - does not open a port/socket - does not process arbitrary web content - does not use centralized online accounts - does not integrate arbitrary javascript into the desktop - does not deal with system authentication (eg, pam), etc) - does not deal with security attestation (secure boot, tpm, signatures) Problems: - does parse data formats (usually code in the current use, but not arbitrary and low attack surface) [Common blockers] OK: - does not FTBFS currently - does have a test suite that runs at build time - test suite fails will fail the build upon error. - does have a test suite that runs as autopkgtest - no special HW needed - no new python2 dependency Problems: - the current autopkgtest fails and does so since impish which is why it isn't flagged. But this might represent an underlying problem with not only the test but the program, we should fix this before considering it ready. [Packaging red flags] OK: - Ubuntu does not carry a delta - symbols tracking not applicable for this kind of code. - d/watch is present and looks ok - Debian/Ubuntu update history is slow (matching upstream) - the current release is packaged - promoting this does not seem to cause issues for MOTUs that so far maintained the package - no massive Lintian warnings - d/rules is rather clean - It is not on the lto-disabled list Problems: - Upstream update history is slow, not sure how much we can rely on it. Those kind of packages often are without being a problem, but we have to be clear this seems like a non (much) active upstream. [Upstream red flags] OK: - no Errors/warnings during the build - no incautious use of malloc/sprintf (perl only) - no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH - no use of user nobody - no use of setuid - no important open bugs (crashers, etc) in Debian or Ubuntu - no dependency on webkit, qtwebkit, seed or libgoa-* - not part of the UI for extra checks - no translation present, but none needed for this case Problems: None ** Changed in: libxs-parse-sublike-perl (Ubuntu) Status: Confirmed => Incomplete ** Changed in: libindirect-perl (Ubuntu) Assignee: Christian Ehrhardt (paelzer) => (unassigned) ** Changed in: libobject-pad-perl (Ubuntu) Assignee: Christian Ehrhardt (paelzer) => (unassigned) ** Changed in: libunicode-escape-perl (Ubuntu) Assignee: Christian Ehrhardt (paelzer) => (unassigned) ** Changed in: libunicode-string-perl (Ubuntu) Assignee: Christian Ehrhardt (paelzer) => (unassigned) ** Changed in: libxs-parse-sublike-perl (Ubuntu) Assignee: Christian Ehrhardt (paelzer) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972853 Title: [MIR] lib*-perl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libindirect-perl/+bug/1972853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972853] Re: [MIR] lib*-perl
Review for Package: libunicode-string-perl [Summary] MIR team NACK (indirectly, since libunicode-escape-perl got a NACK) Once resolved there this can be re-considere. In that case it would be a usual ack under constraint to resolve the required todos below. This does not need a security review List of specific binary packages to be promoted to main: libunicode-string-perl Specific binary packages built, but NOT to be promoted to main: n/a Notes: Required TODOs: - give it a reasonable evaluation please if the need for this from the depending package might nowadays be fulfillable with perls native unicode support that it has. Recommended TODOs: - The package should get a team bug subscriber before being promoted [Duplication] There is no other package in main providing the same functionality. But that is only true if one insists on the old style handling. Newer perl supports unicode and the package states that itself: "These modules predate native Unicode support inside Perl. Normally, the integrated Perl Unicode support and modules such as Encode should be used instead of these modules." We should avoid picking this up by accident, unless the dependency triggering this does strictly need one of the few special features here it should be better to get rid of the dependency to this old module. Please start those checks at libunicode-escape-perl which has a similar problem and if that isn't needed then libunicode-string-perl is not needed either. [Dependencies] OK: - no other Dependencies to MIR due to this - no -dev/-debug/-doc packages that need exclusion - No dependencies in main that are only superficially tested requiring more tests now. Problems: None [Embedded sources and static linking] OK: - no embedded source present - no static linking - does not have odd Built-Using entries - not a go package, no extra constraints to consider in that regard - No vendoring used, all Built-Using are in main Problems: None [Security] - history of CVEs does not look concerning - does not run a daemon as root - does not use webkit1,2 - does not use lib*v8 directly - does not open a port/socket - does not process arbitrary web content - does not use centralized online accounts - does not integrate arbitrary javascript into the desktop - does not deal with system authentication (eg, pam), etc) - does not deal with security attestation (secure boot, tpm, signatures) Problems: - does parse data formats (usually docs in the current use, but not arbitrary and low attack surface) [Common blockers] OK: - does not FTBFS currently - does have a test suite that runs at build time - test suite fails will fail the build upon error. - does have a test suite that runs as autopkgtest - no special HW needed - no new python2 dependency Problems: None [Packaging red flags] OK: - Ubuntu does not carry a delta - symbols tracking not applicable for this kind of code. - d/watch is present and looks ok - Debian/Ubuntu update history is slow (matching upstream) - the current release is packaged - promoting this does not seem to cause issues for MOTUs that so far maintained the package - no massive Lintian warnings - d/rules is rather clean - It is not on the lto-disabled list Problems: - Upstream update history is slow, not sure how much we can rely on it. Those kind of packages often are without being a problem, but we have to be clear this seems like a non (much) active upstream. [Upstream red flags] OK: - no Errors/warnings during the build - no incautious use of malloc/sprintf (perl only) - no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH - no use of user nobody - no use of setuid - no important open bugs (crashers, etc) in Debian or Ubuntu - no dependency on webkit, qtwebkit, seed or libgoa-* - not part of the UI for extra checks - no translation present, but none needed for this case Problems: None ** Changed in: libunicode-string-perl (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972853 Title: [MIR] lib*-perl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libindirect-perl/+bug/1972853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959548] Re: [22.04 FEAT] zcrypt DD: Exploitation Support of new IBM Z Crypto Hardware (s390-tools part)
A test build in PPA was done and is available here: https://launchpad.net/~fheimes/+archive/ubuntu/lp1959548 ** Changed in: ubuntu-z-systems Status: Incomplete => In Progress ** Changed in: s390-tools (Ubuntu) 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/1959548 Title: [22.04 FEAT] zcrypt DD: Exploitation Support of new IBM Z Crypto Hardware (s390-tools part) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Description changed: [Impact] - The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: + test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests + will fail on 5.13 kernel with: - # selftests: net: test_vxlan_under_vrf.sh - # Checking HV connectivity[ OK ] - # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] - not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 + # selftests: net: test_vxlan_under_vrf.sh + # Checking HV connectivity [ OK ] + # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] + not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case The first patch (e7e4785f) can be cherry-picked to Impish 5.13 and F-oem-5.14. Note that this test is not failing on F-oem-5.14, but it's better to have it applied to reduce the maintenance cost. - After the first patch was applied, we will need the second patch on Impish 5.13 to solve the another failure, which we made it an expected failure (XFAIL) with SAUCE patches: - Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] + After the first patch was applied, we will need the second patch on + Impish 5.13 to solve the another failure, which we made it an expected + failure (XFAIL) with SAUCE patches: + Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] - The second patch (b50d3b46) can be cherry-picked with must be applied - with -C2 due to our SAUCE patches. F-oem-5.14 has already got this one - applied. + The second patch (b50d3b46) can be cherry-picked to Impish 5.13 but + must be applied with -C2 due to our SAUCE patches. F-oem-5.14 has + already got this one applied. [Test] - Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test can pass without any issue: - Checking HV connectivity [ OK ] - Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] - Check VM connectivity through VXLAN (underlay in a VRF)[ OK ] + With the patched test_vxlan_under_vrf.sh test, it can pass on Impish + 5.13 and F-oem-5.14 without any issue: + Checking HV connectivity [ OK ] + Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] + Check VM connectivity through VXLAN (underlay in a VRF) [ OK ] [Where problems could occur] - Change limit to test cases, should not have any real impact to kernel functions. But if these fixes are incorrect we will see failures in our regression-testing report. The worst scenario is getting false-negative results. + Change limit to test cases, should not have any real impact to any + kernel functions. But if these fixes are incorrect we will see + failures in our regression-testing report. The worst scenario is + getting false-negative results. + [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input
Didn't Work. --- I removed acpi_os parameters, updated grub with update-grub, rebooted, touchpad still does not wakeup device, and, $ pwd /sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00/power $ ls -la total 0 drwxr-xr-x 2 root root0 May 25 14:55 . drwxr-xr-x 4 root root0 May 25 14:34 .. -rw-r--r-- 1 root root 4096 May 25 14:55 async -rw-r--r-- 1 root root 4096 May 25 14:55 autosuspend_delay_ms -rw-r--r-- 1 root root 4096 May 25 14:55 control -r--r--r-- 1 root root 4096 May 25 14:55 runtime_active_kids -r--r--r-- 1 root root 4096 May 25 14:55 runtime_active_time -r--r--r-- 1 root root 4096 May 25 14:55 runtime_enabled -r--r--r-- 1 root root 4096 May 25 14:55 runtime_status -r--r--r-- 1 root root 4096 May 25 14:55 runtime_suspended_time -r--r--r-- 1 root root 4096 May 25 14:55 runtime_usage ** Attachment added: "updated grub" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+attachment/5592829/+files/grub -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971933 Title: [Regression] Unable to wake laptop using trackpad input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975685] [NEW] Wifi hotspot does not work when band A is selected
Public bug reported: I'm using a built-in RTL8822BE WiFi adapter on a Ryzen 7 system. When I create a hotspot by opening the GNOME settings app, opening the WiFi settings page and selecting "Turn on hotspot..." from the drop-down menu, everything works fine. If I then open nm-connection-editor and edit the connection to select band A (5GHz), the hotspot fails to start. If I then open the connection editor again and switch back to automatic band selection, the hotspot works again. When it fails, this appears in syslog: May 25 10:21:30 frog NetworkManager[815]: [1653470490.8638] device (wlo1): Activation: starting connection 'Hotspot' (514f603b-25e2-4c1e-9220-7b77ed966ff5) May 25 10:21:30 frog NetworkManager[815]: [1653470490.8643] device (wlo1): supplicant interface state: completed -> disconnected May 25 10:21:30 frog NetworkManager[815]: [1653470490.8653] device (wlo1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') May 25 10:21:30 frog NetworkManager[815]: [1653470490.8676] device (wlo1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') May 25 10:21:30 frog NetworkManager[815]: [1653470490.8783] device (wlo1): Activation: (wifi) access point 'Hotspot' has security, but secrets are required. May 25 10:21:30 frog NetworkManager[815]: [1653470490.8783] device (wlo1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') May 25 10:21:30 frog NetworkManager[815]: [1653470490.8800] device (wlo1): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') May 25 10:21:30 frog NetworkManager[815]: [1653470490.8810] device (wlo1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') May 25 10:21:30 frog NetworkManager[815]: [1653470490.8883] device (wlo1): Activation: (wifi) connection 'Hotspot' has security, and secrets exist. No new secrets needed. May 25 10:21:30 frog wpa_supplicant[866]: wlo1: Failed to start AP functionality May 25 10:21:56 frog NetworkManager[815]: [1653470516.1521] device (wlo1): Activation: (wifi) Hotspot network creation took too long, failing activation May 25 10:21:56 frog NetworkManager[815]: [1653470516.1522] device (wlo1): state change: config -> failed (reason 'supplicant-timeout', sys-iface-state: 'managed') May 25 10:21:56 frog NetworkManager[815]: [1653470516.1526] device (wlo1): Activation: failed for connection 'Hotspot' May 25 10:21:56 frog wpa_supplicant[866]: wlo1: CTRL-EVENT-DSCP-POLICY clear_all May 25 10:21:56 frog NetworkManager[815]: [1653470516.1530] device (wlo1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') May 25 10:21:56 frog wpa_supplicant[866]: wlo1: Reject scan trigger since one is already pending May 25 10:21:59 frog wpa_supplicant[866]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN I'm guessing that NetworkManager is getting the way it drives wpa_supplicant wrong when the 5GHz band is selected, but it's only a guess. Ubuntu version is: tkcook@frog:~$ lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 NetworkManager version is: tkcook@frog:~$ apt-cache policy network-manager-gnome network-manager-gnome: Installed: 1.24.0-1ubuntu3 Candidate: 1.24.0-1ubuntu3 Version table: *** 1.24.0-1ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager-gnome 1.24.0-1ubuntu3 Uname: Linux 5.18.0 x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 25 10:29:37 2022 InstallationDate: Installed on 2021-08-27 (270 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: network-manager-applet UpgradeStatus: Upgraded to jammy on 2022-05-05 (19 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled disabled ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975685 Title: Wifi hotspot does not work when band A is selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1975685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta-aws-5.4/5.4.0.1075.57)
All autopkgtests for the newly accepted linux-meta-aws-5.4 (5.4.0.1075.57) for bionic have finished running. The following regressions have been reported in tests triggered by the package: systemd/237-3ubuntu10.53 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-aws-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975687] [NEW] Please enable delayacct by default
Public bug reported: Recent kernel commit disabled delayacct by default (see here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e4042ad492357fa995921376462b04a025dd53b6), which partially breaks "iotop". Please change grub kernel command line to re-enable delayacct by default. Alternatively, please revert the commit above. Ubuntu version affected (via "lsb_release -rd"): Description:Ubuntu 22.04 LTS Release:22.04 ** Affects: linux-meta (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/1975687 Title: Please enable delayacct by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1975687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975576] Re: [SRU] Connect to WPA3 failed - Secrets were required, but not provided
** Changed in: netplan.io (Ubuntu Focal) Status: New => Triaged ** Changed in: netplan.io (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: netplan.io (Ubuntu Jammy) Status: New => Triaged ** Changed in: netplan.io (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975576 Title: [SRU] Connect to WPA3 failed - Secrets were required, but not provided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1975576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975688] [NEW] Accessing squashfs with lzma compression is ~16% slower in 5.15 when compared to 5.4, on an RPi3 B+
Public bug reported:
On the server image on an RPi3 B+, I run this script:
```
#!/bin/bash -eu
mount_and_read()
{
local snap=$1
local mnt_d=$2
mount "$snap" "$mnt_d"
# We should not use /dev/null here, see
#
https://unix.stackexchange.com/questions/512362/why-does-tar-appear-to-skip-file-contents-when-output-file-is-dev-null
tar -cO "$mnt_d"/ > /dev/zeros
}
snap_d=$(mktemp -d)
for i in {1..3}; do
sync && echo 3 > /proc/sys/vm/drop_caches
time mount_and_read "$1" "$snap_d"
umount "$snap_d"
done
rmdir "$snap_d"
```
With these commands:
$ sudo mount -t tmpfs -o size=400M tmpfs tmpfs/
$ cd tmpfs
$ snap download core22
$ sudo ../measure-snap-mnt.sh core22_169.snap
I get these results on 20.04:
real0m21.667s
user0m0.302s
sys 0m20.299s
real0m21.650s
user0m0.351s
sys 0m20.417s
real0m21.718s
user0m0.285s
sys 0m20.528s
On 22.04 server image:
real0m25.084s
user0m0.407s
sys 0m23.778s
real0m25.064s
user0m0.397s
sys 0m23.768s
real0m25.051s
user0m0.369s
sys 0m23.803s
Which is a considerable difference. This affects snaps compressed with
xz, and although these measurements are for server the bigger impact is
on UC images, where the boot time increases considerably because of
this.
** Affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Accessing squashfs with lzma compression is ~16% slower in 5.15 when compared
to 5.4
+ Accessing squashfs with lzma compression is ~16% slower in 5.15 when compared
to 5.4, on an RPi3 B+
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975688
Title:
Accessing squashfs with lzma compression is ~16% slower in 5.15 when
compared to 5.4, on an RPi3 B+
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1975688/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
https://lists.ubuntu.com/archives/kernel-team/2022-May/130587.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975391] Re: Subiquity crashes if the hd contains a previous Proxmox PVE install
Ok, thank you. If I encounter the error again or manage to reproduce it, I'll post the logs here then! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975391 Title: Subiquity crashes if the hd contains a previous Proxmox PVE install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1975391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973041] Re: llvm-toolchain-13: please backport Risc-V .insn directive support
Refreshed version of the same thing, with the merge fixed, adding Replaces/Breaks fields due to the Ubuntu/Debian divergence on which package ships the new static libraries. I used the dh-exec mechanism for the i386 exception as it is what is used in the current Salsa 13 branch for their grpc-unable architectures, thus it'll eventually reduce the delta. The .insn patch has been forwarded to Debian: https://salsa.debian.org/pkg-llvm-team/llvm- toolchain/-/merge_requests/89 ** Patch added: "llvm-13.debdiff" https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-13/+bug/1973041/+attachment/5592872/+files/llvm-13.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973041 Title: llvm-toolchain-13: please backport Risc-V .insn directive support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-13/+bug/1973041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975616] Re: [UBUNTU 20.04] Several "failed assertion in udev" messages causing unexpected errors in the system
** Also affects: ubuntu-z-systems 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/1975616 Title: [UBUNTU 20.04] Several "failed assertion in udev" messages causing unexpected errors in the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1975616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975616] Re: [UBUNTU 20.04] Several "failed assertion in udev" messages causing unexpected errors in the system
Thanks for raising this. Please let me mention a few observations: - The kernel that is in use is (significantly) outdated: 5.4.0-80-generic (Jul 9 17:41:33 UTC 2021), there is a delta of about 20 missed kernel updates. - And the system as a whole is outdated as well, since it reports "20.04.2 LTS". Please notice that every new point release replaces the previous one and with that makes it obsolete and no longer supported. We are btw. currently at 20.04.4 (20.04.5 will come in August). On top a system needs to receive regular (functional and security) updates, for example with the help of: sudo apt update sudo apt upgrade An up-to-date system will obviously have lot's of mlx5 kernel fixes as well as systemd, udev and other user-land patches included. - So please reproduce this with the latest levels, on an up-to-date system. Otherwise time and effort might be wasted at both parties on hunting down bugs that are potentially already fixed. I'm also reading that "this is a customer machine", in such a case it's preferred to open a SalesForce ticket (for support cases) rather than a Launchpad bug (for development tasks). And without crash/dump files one can only roughly assume what might happen. A first brief investigation of some of the messages, seem to point to a potential problem of the hw-fw/driver combination. So please also double-check if the firmware of the RoCE/Mellanox adapter is on the very latest fw level. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: ubuntu-z-systems Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975616 Title: [UBUNTU 20.04] Several "failed assertion in udev" messages causing unexpected errors in the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1975616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872984] Re: RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic
I experienced the bug on my Lenovo IdeaPad L340-17IWL with Ubuntu 20.04 up to date and a Realtech rtw_8821ce. I spend hours to try to find a setting, practicing the Computer Assisted Waste of Time. I bought an external wifi dongle with another Realtech 81... chip (I've not it at hand now) and experienced also the failure of the wifi after some times. As said by delfi above. I still experience the bug after a while after a fresh install of Ubuntu 22.04. More than 2 years that the bug is known... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872984 Title: RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871148] Re: services start before apparmor profiles are loaded
Oh, this is interesting! Then, Etienne, my suggestion is the following: re-enable the snapd.apparmor service, and if that (as I expect) fixes the bug, let's stop discussing this issue here, and instead open a separate issue about the service being disabled. It may be that something went wrong during the upgrade to Jammy. If we file this as a separate bug, we might be able to see if other people have met the same issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871148 Title: services start before apparmor profiles are loaded To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975691] [NEW] Remvoe SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests
Public bug reported: [Impact] test_vxlan_under_vrf.sh should not be failing anymore (except if it's a config related issue) with patches submitted for I-5.13 / F-oem-5.14 in bug 1871015 We should remove the SAUCE patches that mark "vxlan_under_vrf" failure as expected failure to catch regressions in the future. [Fix] Revert the following patches: * UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non-default VRF an expected failure * UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail [Test] [Where problems could occur] Change limit to test cases, should not have any real impact to any kernel functions. We may see failures reported from this test in our SRU regression-testing report in the future, but it means we're doing the right thing. ** Affects: ubuntu-kernel-tests Importance: Undecided Assignee: Po-Hsu Lin (cypressyew) Status: In Progress ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (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/1975691 Title: Remvoe SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1975691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975690] [NEW] kernel 5.13.0-41 and 5.13.0-44 do not boot
Public bug reported: the kernel updates for linux Mint 5.13.0.41 then 5.13.0-44 do not boot. Nothing on the screen or journalctl. I tried to add debug=vc and break=top on the boot line with nothing else. I also tried to use the root='hd0,gpt6' syntax instead of root=UUID=... but the file system is seen because if I replace initrd.img-5.13.0-44-generic by a copy of initrd.img-5.13.0-40-generic I have some display 5.13.0-40 works fine, and the root, debug and break options work fine in it. ubuntu-bug does not work saying linux-image-5.13.0-40-generic is not an official package and no crash report I join files for lspci -vnvn ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: boot initrd kernel ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1975690/+attachment/5592873/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970957] Re: suspend problem
On my X1 Carbon I seem to have solved the issue by: 1. changing the BIOS so the Sleep State is in mode "Linux" as opposed to "Windows and Linux" 2. using Xorg instead of Wayland. -> When you log in, before inserting the password, click on the cog on the bottom right and choose the "Ubuntu on Xorg" option. YMMV, but since I lost a day I wrote my solution here in case it helps someone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970957 Title: suspend problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973564] Re: File dialog doesn't return current filter in Ubuntu 20.04
Hello Ted, or anyone else affected, Accepted xdg-desktop-portal into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xdg- desktop-portal/1.6.0-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- 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. ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973564 Title: File dialog doesn't return current filter in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1973564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973564] Please test proposed package
Hello Ted, or anyone else affected, Accepted xdg-desktop-portal-gtk into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xdg- desktop-portal-gtk/1.6.0-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- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973564 Title: File dialog doesn't return current filter in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1973564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964983] Re: IPU6 camera has no function on Andrews MLK
SRU v7: https://lists.ubuntu.com/archives/kernel- team/2022-May/130591.html (jammy) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964983 Title: IPU6 camera has no function on Andrews MLK To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1964983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
SRU v7: https://lists.ubuntu.com/archives/kernel- team/2022-May/130591.html (jammy) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1955383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958006] Re: multiple UBSAN warnings in Intel IPU6 camera driver at boot
SRU v7: https://lists.ubuntu.com/archives/kernel- team/2022-May/130591.html (jammy) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958006 Title: multiple UBSAN warnings in Intel IPU6 camera driver at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947127] Fix included in openstack/neutron 19.3.0
This issue was fixed in the openstack/neutron 19.3.0 release. ** Changed in: cloud-archive/xena Status: Confirmed => 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/1947127 Title: [SRU] Some DNS extensions not working with OVN To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1947127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Description changed: [Impact] test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 + Note that this test is not failing on F-oem-5.14 / J-oem-5.17, but + it's better to have corresponding patches applied to reduce the + maintenance cost in the future. + [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case - The first patch (e7e4785f) can be cherry-picked to Impish 5.13 and - F-oem-5.14. + First patch (e7e4785f): + - Can be cherry-picked to Impish 5.13 + - Can be cherry-picked to F-oem-5.14. + Second patch (b50d3b46): + - Can be cherry-picked to Impish 5.13 (-C2 is required while + applying it due to our SAUCE patches) + - F-oem-5.14 has already got this one applied. + - Can be cherry-picked to J-oem-5.17 - Note that this test is not failing on F-oem-5.14, but it's better to - have it applied to reduce the maintenance cost. - - After the first patch was applied, we will need the second patch on - Impish 5.13 to solve the another failure, which we made it an expected + The reason why we need the second patch is that after the first one + got applied, we will see another failure, which we made it an expected failure (XFAIL) with SAUCE patches: Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] - The second patch (b50d3b46) can be cherry-picked to Impish 5.13 but - must be applied with -C2 due to our SAUCE patches. F-oem-5.14 has - already got this one applied. - [Test] With the patched test_vxlan_under_vrf.sh test, it can pass on Impish - 5.13 and F-oem-5.14 without any issue: + 5.13, F-oem-5.14 and J-oem-5.17 without any issue: Checking HV connectivity [ OK ] Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] Check VM connectivity through VXLAN (underlay in a VRF) [ OK ] [Where problems could occur] Change limit to test cases, should not have any real impact to any kernel functions. But if these fixes are incorrect we will see failures in our regression-testing report. The worst scenario is getting false-negative results. - [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975578] Re: NetworkManager does not push search domains to systemd-resolved
** Description changed: Search domains defined in a NetworkManager connection are not pushed to systemd-resolved. + + DISTRIB_ID=Ubuntu + DISTRIB_RELEASE=22.04 + DISTRIB_CODENAME=jammy + DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" + PRETTY_NAME="Ubuntu 22.04 LTS" + NAME="Ubuntu" + VERSION_ID="22.04" + VERSION="22.04 LTS (Jammy Jellyfish)" + VERSION_CODENAME=jammy + ID=ubuntu + ID_LIKE=debian + UBUNTU_CODENAME=jammy ** Description changed: Search domains defined in a NetworkManager connection are not pushed to systemd-resolved. DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian UBUNTU_CODENAME=jammy + + Details: + DNS search domains can be set per NetworkManager connection. In my case it looks like this: + + nmcli con show MyConnection | grep ipv4.dns-search + ipv4.dns-search: mydomain.at,org.mydomain.at,linux.mydomain.at + + Afaik NetworkManager should push them to systemd-resolved automatically. + But this does not happen. The entries do not make it to + /etc/resolv.conf. + + (If I do it manually with resolvectl, it works.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975578 Title: NetworkManager does not push search domains to systemd-resolved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969342] Re: running dpdk-testpmd shows "Failed to execute command of OP_SET_RSS_HENA" in vm with intree driver on ubuntu-22.04
we have learned that the in-tree ice driver support for OP_SET_RSS_HENA has never been upstreamed, so we will track this issue as a future requirement, and will revisit this issue once the in-tree ice driver support for OP_SET_RSS_HENA has been upstreamed and backported. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969342 Title: running dpdk-testpmd shows "Failed to execute command of OP_SET_RSS_HENA" in vm with intree driver on ubuntu-22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1969342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975690] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1975690 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975578] Re: NetworkManager does not push search domains to systemd-resolved
** Description changed: Search domains defined in a NetworkManager connection are not pushed to systemd-resolved. DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian UBUNTU_CODENAME=jammy + NetworkManager -V + 1.36.4 + Details: DNS search domains can be set per NetworkManager connection. In my case it looks like this: nmcli con show MyConnection | grep ipv4.dns-search ipv4.dns-search: mydomain.at,org.mydomain.at,linux.mydomain.at Afaik NetworkManager should push them to systemd-resolved automatically. But this does not happen. The entries do not make it to /etc/resolv.conf. (If I do it manually with resolvectl, it works.) ** Description changed: Search domains defined in a NetworkManager connection are not pushed to systemd-resolved. DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian UBUNTU_CODENAME=jammy NetworkManager -V 1.36.4 + resolvectl --version + systemd 249 (249.11-0ubuntu3.1) + +PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS -OPENSSL +ACL +BLKID +CURL +ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP -LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified + Details: DNS search domains can be set per NetworkManager connection. In my case it looks like this: nmcli con show MyConnection | grep ipv4.dns-search ipv4.dns-search: mydomain.at,org.mydomain.at,linux.mydomain.at Afaik NetworkManager should push them to systemd-resolved automatically. But this does not happen. The entries do not make it to /etc/resolv.conf. (If I do it manually with resolvectl, it works.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975578 Title: NetworkManager does not push search domains to systemd-resolved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1970957] Re: suspend problem
On my X1 Carbon 10th Gen, I can confirm my 'sleep state' in UEFI/BIOS is set to "Linux" - as per lenovo's instructions, and I use Xorg exlsuively - via Ubuntu Mate. I can confirm that this mitigates the problem, but still occurs occasionally. HTH - Original message - From: bigblackcar <1970...@bugs.launchpad.net> To: lauri...@fastmail.fm Subject: [Bug 1970957] Re: suspend problem Date: Wednesday, 25 May 2022 8:33 PM On my X1 Carbon I seem to have solved the issue by: 1. changing the BIOS so the Sleep State is in mode "Linux" as opposed to "Windows and Linux" 2. using Xorg instead of Wayland. -> When you log in, before inserting the password, click on the cog on the bottom right and choose the "Ubuntu on Xorg" option. YMMV, but since I lost a day I wrote my solution here in case it helps someone. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1970957 Title: suspend problem Status in linux package in Ubuntu: Confirmed Bug description: I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok intermittently. Some times it works fine, other times the computer does not enter the suspend mode (the screen gets blank, but the machine is still running and the ThinPad led is on, and there is no way out... no response from keyboard or mouse... the only solution is to switch off manually hitting and holding the power button), other times the machine does not wakes up from suspension mode. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 10:53:59 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leoca 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20KQ000EBR Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2018 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R0PET42W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KQ000EBR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480: dmi.product.family: ThinkPad E480 dmi.product.name: 20KQ000EBR dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480 dmi.product.version: ThinkPad E480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970957 Title: suspend problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
V2 https://lists.ubuntu.com/archives/kernel-team/2022-May/130594.html ** Description changed: [Impact] test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 Note that this test is not failing on F-oem-5.14 / J-oem-5.17, but it's better to have corresponding patches applied to reduce the maintenance cost in the future. [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case First patch (e7e4785f): - Can be cherry-picked to Impish 5.13 - Can be cherry-picked to F-oem-5.14. Second patch (b50d3b46): - Can be cherry-picked to Impish 5.13 (-C2 is required while applying it due to our SAUCE patches) - F-oem-5.14 has already got this one applied. - - Can be cherry-picked to J-oem-5.17 The reason why we need the second patch is that after the first one got applied, we will see another failure, which we made it an expected failure (XFAIL) with SAUCE patches: Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] [Test] With the patched test_vxlan_under_vrf.sh test, it can pass on Impish - 5.13, F-oem-5.14 and J-oem-5.17 without any issue: + 5.13 and F-oem-5.14 without any issue: Checking HV connectivity [ OK ] Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] Check VM connectivity through VXLAN (underlay in a VRF) [ OK ] [Where problems could occur] Change limit to test cases, should not have any real impact to any kernel functions. But if these fixes are incorrect we will see failures in our regression-testing report. The worst scenario is getting false-negative results. [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 ** Description changed: [Impact] test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: - # selftests: net: test_vxlan_under_vrf.sh - # Checking HV connectivity [ OK ] - # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] - not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 + # selftests: net: test_vxlan_under_vrf.sh + # Checking HV connectivity [ OK ] + # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] + not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 - Note that this test is not failing on F-oem-5.14 / J-oem-5.17, but - it's better to have corresponding patches applied to reduce the - maintenance cost in the future. + Note that this test is not failing on F-oem-5.14 but it's better to + have corresponding patches applied to reduce the maintenance cost + in the future. [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case First patch (e7e4785f): - - Can be cherry-picked to Impish 5.13 - - Can be cherry-picked to F-oem-5.14. + - Can be cherry-picked to Impish 5.13 + - Can be cherry-picked to F-oem-5.14. Second patch (b50d3b46): - - Can be cherry-picked to Impish 5.13 (-C2 is required while - applying it due to our SAUCE patches) - - F-oem-5.14 has already got this one applied. + - Can be cherry-picked to Impish 5.13 (-C2 is required while + applying it due to our SAUCE patches) + - F-oem-5.14 has already got this one applied. The reason why we need the second patch is that after the first one got applied, we will see another failure, which we made it an expected failure (XFAIL) with SAUCE patches: - Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] + Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] [Test] With the patched test_vxlan_under_vrf.sh test, it can pass on Impish 5.13 and F-oem-5.14 without any issue: - Checking HV connectivity [ OK ] - Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] - Check VM connectivity through VXLAN (underlay in a VRF) [ OK ] + Checking HV connectivity [ OK ] + Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] + Check VM connectivity through VXLAN (underlay in a VRF) [ OK ] [Where problems could occur] Change limit to test cases, should not have any real impact to any kernel functions. But if these fixes are incorrect we will see failures in our regression-testing report. The worst scenario is getting
[Bug 1973839] Re: 5.15.0-30-generic : SSBD mitigation results in "unchecked MSR access error: WRMSR to 0x48 (tried to write 0x0000000000000004)" and flood of kernel traces in some cloud providers
Which cloud is in use and what the instance type is? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973839 Title: 5.15.0-30-generic : SSBD mitigation results in "unchecked MSR access error: WRMSR to 0x48 (tried to write 0x0004)" and flood of kernel traces in some cloud providers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973296] Re: [UBUNTU 20.04] OpenCryptoki >= 3.13 with upgraded EP11 host library - Dilithium support not available
Hello bugproxy, or anyone else affected, Accepted opencryptoki into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/opencryptoki/3.16.0+dfsg-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. 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: opencryptoki (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-impish ** Changed in: opencryptoki (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973296 Title: [UBUNTU 20.04] OpenCryptoki >= 3.13 with upgraded EP11 host library - Dilithium support not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1973296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973296] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted opencryptoki into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/opencryptoki/3.17.0+dfsg+20220202.b40982e-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: opencryptoki (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973296 Title: [UBUNTU 20.04] OpenCryptoki >= 3.13 with upgraded EP11 host library - Dilithium support not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1973296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973296] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted opencryptoki into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/opencryptoki/3.13.0+dfsg-0ubuntu5.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973296 Title: [UBUNTU 20.04] OpenCryptoki >= 3.13 with upgraded EP11 host library - Dilithium support not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1973296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973296] Re: [UBUNTU 20.04] OpenCryptoki >= 3.13 with upgraded EP11 host library - Dilithium support not available
Accepted, but please adjust your Test Plan to actually test the previous missing *functionality* of opencryptoki+EP11+Dilithium from a user's perspective. This means something like "verify that a user can use their token to authenticate against X" rather than "verify that the library supports X". Just checking that it's detected and _might_ work is insufficient, IMHO. Because if it turns out that a further patch is needed to make it actually work for users, we shouldn't be pushing updates multiple times to unaffected users because we didn't test the stack all the way through. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973296 Title: [UBUNTU 20.04] OpenCryptoki >= 3.13 with upgraded EP11 host library - Dilithium support not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1973296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965123] Re: Active launchers area pixels (corners) missing
I have this issue on an Intel graphic laptop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965123 Title: Active launchers area pixels (corners) missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input
OK, so the laptop doesn't use s2idle, it's using S3 instead. Please perform a kernel bisection [1] to find the regression commit. [1] https://wiki.ubuntu.com/Kernel/KernelBisection -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971933 Title: [Regression] Unable to wake laptop using trackpad input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975690] Re: kernel 5.13.0-41 and 5.13.0-44 do not boot
apport information ** Tags added: apport-collected una ** Description changed: the kernel updates for linux Mint 5.13.0.41 then 5.13.0-44 do not boot. Nothing on the screen or journalctl. I tried to add debug=vc and break=top on the boot line with nothing else. I also tried to use the root='hd0,gpt6' syntax instead of root=UUID=... but the file system is seen because if I replace initrd.img-5.13.0-44-generic by a copy of initrd.img-5.13.0-40-generic I have some display 5.13.0-40 works fine, and the root, debug and break options work fine in it. ubuntu-bug does not work saying linux-image-5.13.0-40-generic is not an official package and no crash report I join files for lspci -vnvn + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.24 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: sauvard1402 F pulseaudio + /dev/snd/pcmC0D0p: sauvard1402 F...m pulseaudio + /dev/snd/controlC1: sauvard1402 F pulseaudio + CasperMD5CheckResult: skip + DistroRelease: Linux Mint 20.3 + InstallationDate: Installed on 2019-12-23 (883 days ago) + InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 + IwConfig: + lono wireless extensions. + + enp2s0no wireless extensions. + MachineType: Gigabyte Technology Co., Ltd. B560 HD3 + Package: linux (not installed) + ProcEnviron: + LANGUAGE=fr_FR + TERM=xterm-256color + PATH=(custom, no user) + LANG=C + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=42eeb43d-120a-4438-a3c4-d924632552c8 ro quiet splash + ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-5.13.0-40-generic N/A + linux-backports-modules-5.13.0-40-generic N/A + linux-firmware 1.187.31 + RfKill: + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no + Tags: una + Uname: Linux 5.13.0-40-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 11/03/2021 + dmi.bios.release: 5.19 + dmi.bios.vendor: American Megatrends International, LLC. + dmi.bios.version: F10 + dmi.board.asset.tag: Default string + dmi.board.name: B560 HD3 + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: Default string + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF10:bd11/03/2021:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnB560HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560HD3:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: + dmi.product.family: B560 MB + dmi.product.name: B560 HD3 + dmi.product.sku: Default string + dmi.product.version: Default string + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592874/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975690] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592875/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975690] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592876/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975690] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592877/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975690] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592879/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975690] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592880/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975690] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592878/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975690] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592881/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975690] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592883/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975690] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592882/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975690] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592884/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975690] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592885/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975690] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592886/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975690] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592888/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
