[Bug 1964975] [NEW] can we update to 1.8.0 for Ubuntu 22.04
Public bug reported: With OpenSSL 3 deprectaing a lot of the internal interfaces, could we get this updated for the proper OpenSSL 3 API integrations? - https://github.com/tpm2-software/tpm2-pkcs11/releases/tag/1.8.0-rc0 ** Affects: tpm2-pkcs11 (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/1964975 Title: can we update to 1.8.0 for Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpm2-pkcs11/+bug/1964975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964973] Re: python-b2sdk: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
** Changed in: python-b2sdk (Debian)
Status: New => Confirmed
** Changed in: python-b2sdk (Debian)
Importance: Undecided => Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964973
Title:
python-b2sdk: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p "3.10 3.9" returned exit code 13
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-b2sdk/+bug/1964973/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964973] Re: python-b2sdk: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
There is a fix for this upstream [1], but it involves upgrading the
logfury dependency, and python3-logfury in Debian is too old.
[1] https://github.com/Backblaze/b2-sdk-python/issues/288
** Bug watch added: github.com/Backblaze/b2-sdk-python/issues #288
https://github.com/Backblaze/b2-sdk-python/issues/288
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964973
Title:
python-b2sdk: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p "3.10 3.9" returned exit code 13
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-b2sdk/+bug/1964973/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964976] [NEW] gnome-remote-desktop is not listening on port 5900, no sign of why
Public bug reported: With all current packages from jammy, gnome-remote-desktop is not listening on port 5900. Lsof doesn't show it listening on that port, attempting to connect to that port yields connection refused), with no indication of why. There are no errors matching the pattern "gnome- remote-desktop" in /var/log/syslog, "journalctl --user --unit gnome- remote-desktop" doesn't show any errors, "systemctl status --user gnome- remote-desktop" shows that it is running, my settings show that screen sharing is enabled, this used to work, and I haven't changed anything since it did. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-remote-desktop 42~rc-1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 10:49:08 2022 InstallationDate: Installed on 2019-01-02 (1167 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-remote-desktop UpgradeStatus: Upgraded to jammy on 2022-02-20 (22 days ago) ** Affects: gnome-remote-desktop (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964976 Title: gnome-remote-desktop is not listening on port 5900, no sign of why To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1964976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964977] [NEW] pki segmentation fault on openssl plugin
Public bug reported: Found while generating certificates ``` ipsec pki --gen --size 4096 --outform pem Segmentation fault (core dumped) ``` upon reviewing the core dump it looks like when the openssl plugin is being unloaded there is a locking issue? ``` (gdb) bt #0 __pthread_rwlock_rdlock_full64 (abstime=0x0, clockid=0, rwlock=0x0) at ./nptl/pthread_rwlock_common.c:298 #1 ___pthread_rwlock_rdlock (rwlock=0x0) at ./nptl/pthread_rwlock_rdlock.c:26 #2 0x7efd494ccdad in CRYPTO_THREAD_read_lock () from /lib/x86_64-linux-gnu/libcrypto.so.3 #3 0x7efd494c0306 in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.3 #4 0x7efd494d3245 in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.3 #5 0x7efd494d468c in OSSL_PROVIDER_unload () from /lib/x86_64-linux-gnu/libcrypto.so.3 #6 0x7efd49768e71 in ?? () from /usr/lib/ipsec/plugins/libstrongswan-openssl.so #7 0x7efd49e91142 in plugin_entry_destroy (entry=0x55a207162140) at plugins/plugin_loader.c:209 #8 0x7efd49e93461 in unload (this=this@entry=0x55a207123c40) at plugins/plugin_loader.c:1344 #9 0x7efd49e934cd in destroy (this=0x55a207123c40) at plugins/plugin_loader.c:1432 #10 0x7efd49e7a2f8 in library_deinit () at /build/strongswan-0cV2DU/strongswan-5.9.5/src/libstrongswan/library.c:167 #11 0x7efd49c65495 in __run_exit_handlers (status=0, listp=0x7efd49e39838 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at ./stdlib/exit.c:113 #12 0x7efd49c65610 in __GI_exit (status=) at ./stdlib/exit.c:143 #13 0x7efd49c49d97 in __libc_start_call_main (main=main@entry=0x55a205ea88e0 , argc=argc@entry=4, argv=argv@entry=0x7ffdfe6010e8) at ../sysdeps/nptl/libc_start_call_main.h:74 #14 0x7efd49c49e40 in __libc_start_main_impl (main=0x55a205ea88e0 , argc=4, argv=0x7ffdfe6010e8, init=, fini=, rtld_fini=, stack_end=0x7ffdfe6010d8) at ../csu/libc-start.c:392 #15 0x55a205eaad25 in _start () ``` related: https://github.com/openssl/openssl/issues/15915 and even better, it looks like it was fixed upstream a couple weeks ago: https://github.com/strongswan/strongswan/commit/3eecd40cec6415fc033f8d9141ab652047e71524 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: strongswan-pki 5.9.5-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 10:46:07 2022 InstallationDate: Installed on 2022-03-03 (11 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: strongswan UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: strongswan (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964977 Title: pki segmentation fault on openssl plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1964977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964794] Re: Faulty linux-firmware upgrade
*** This bug is a duplicate of bug 1964814 *** https://bugs.launchpad.net/bugs/1964814 Hello, i'm having the same problem on my system aswell. 22.04 - unfortunatly i did try to follow #Achim Behrens advice to remove, delete /lib/firmware/ath11k/WCN6855/hw2.1 manually and the update will work - but unfortunatly i didn't have this path this file didn't exist. What could i do or what should i do in order to fix this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964794 Title: Faulty linux-firmware upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1964794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964814] Re: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1
** 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/1964814 Title: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964136] Re: Settings item not shown in System menu
** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964136 Title: Settings item not shown in System menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960387] Re: fprintd crashed with SIGSEGV in log_v() from usbi_log() from libusb_unref_device()
** Changed in: libusb (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) ** Tags removed: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960387 Title: fprintd crashed with SIGSEGV in log_v() from usbi_log() from libusb_unref_device() To manage notifications about this bug go to: https://bugs.launchpad.net/libusb/+bug/1960387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964682] Re: IBus not starting properly at login to wayland with gnome-shell 42
** Changed in: ibus (Ubuntu) Status: In Progress => Fix Committed ** Changed in: ibus (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964682 Title: IBus not starting properly at login to wayland with gnome-shell 42 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963715] Re: error: failed to register the EFI boot entry: Operation not permitted.
Heinrich, we always install both EFI and BIOS grub on PCs because of the prevalence of firmware that can be configured to do either, or even present as BIOS when booted from external media but then require EFI for internal disks. ** Package changed: grub (Ubuntu) => grub2 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963715 Title: error: failed to register the EFI boot entry: Operation not permitted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1963715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958148] Re: mkinitramfs is too slow
I have uploaded the agreed changes (attached) to jammy. ** Patch added: "initramfs-tools_0.140ubuntu13.diff" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+attachment/5569316/+files/initramfs-tools_0.140ubuntu13.diff ** Changed in: initramfs-tools (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/1958148 Title: mkinitramfs is too slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+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-raspi/5.13.0.1021.26)
All autopkgtests for the newly accepted linux-meta-raspi (5.13.0.1021.26) for impish have finished running. The following regressions have been reported in tests triggered by the package: systemd/unknown (arm64) v4l2loopback/0.12.5-1ubuntu3 (arm64) xtrx-dkms/unknown (arm64) dm-writeboost/unknown (arm64) adv-17v35x/unknown (arm64) libvpoll-eventfd/unknown (arm64) lime-forensics/unknown (arm64) jool/unknown (arm64) langford/unknown (arm64) zfs-linux/unknown (arm64) glibc/unknown (arm64) lxc/unknown (arm64) wireguard-linux-compat/unknown (arm64) r8168/unknown (arm64) ddcci-driver-linux/unknown (arm64) snapd/unknown (arm64) digimend-dkms/unknown (arm64) gost-crypto/unknown (arm64) bbswitch/unknown (arm64) backport-iwlwifi-dkms/unknown (arm64) acpi-call/unknown (arm64) lttng-modules/unknown (arm64) evdi/unknown (arm64) openrazer/unknown (arm64) dpdk-kmods/unknown (arm64) 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/impish/update_excuses.html#linux-meta-raspi [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 1332541] Re: wrong mask
Seems to be correct, what netmask would you expect? ** Changed in: sipcalc (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/1332541 Title: wrong mask To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sipcalc/+bug/1332541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964814] Re: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1
thanks Allan! For me a simple : rm /lib/firmware/ath11k/WCN6855/hw2.1 is all that was needed before restarting the update process. The result is that before the failed upgrade it looked like this : lrwxrwxrwx 1 root root 5 Feb 17 08:51 hw2.1 -> hw2.0 and after the successful upgrade it now looks like this : drwxr-xr-x 2 root root 6 Mär 15 15:34 . lrwxrwxrwx 1 root root 17 Mär 14 11:40 amss.bin -> ../hw2.0/amss.bin lrwxrwxrwx 1 root root 20 Mär 14 11:40 board-2.bin -> ../hw2.0/board-2.bin lrwxrwxrwx 1 root root 15 Mär 14 11:40 m3.bin -> ../hw2.0/m3.bin lrwxrwxrwx 1 root root 18 Mär 14 11:40 regdb.bin -> ../hw2.0/regdb.bin which at first glance is the same -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964814 Title: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962585] Re: tracker-extract-3 crashed with signal 31 in __GI___ioctl()
** Changed in: tracker-miners (Ubuntu) Importance: Medium => High ** Changed in: tracker-miners (Ubuntu) Assignee: (unassigned) => Jeremy Bicha (jbicha) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962585 Title: tracker-extract-3 crashed with signal 31 in __GI___ioctl() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1962585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963758] Re: cups-browsed crashed with SIGSEGV in timeout_free()
the duplicate points to https://errors.ubuntu.com/problem/d72f427fb753b2fef2f19bf721ed46a11e7ab5b3 which isn't a new issue and has low enough reports at the moment, Nick could you give some context on why you think it's a rls issue? ** Changed in: cups-filters (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/1963758 Title: cups-browsed crashed with SIGSEGV in timeout_free() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1963758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15
We just realized that we had DFLTCC support in 20.04, so we need to put this fix there as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961427 Title: zlib: compressBound() returns an incorrect result on z15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1961427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964978] [NEW] OS not recognizing dell laptop touchpad
Public bug reported: Laptop: Dell Precision 5540 After installing ubuntu, my touchpad worked only for a few days and then stopped working totally. And it hasn't worked in a long time now. I started looking a little bit more into it today and I think it might be a problem with the kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-35-generic 5.13.0-35.40~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 16:13:46 2022 InstallationDate: Installed on 2021-01-20 (418 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "The content of: "/proc/bus/input/devices"" https://bugs.launchpad.net/bugs/1964978/+attachment/5569320/+files/devices -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964978 Title: OS not recognizing dell laptop touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1964978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964545] Re: 42beta: moving mouse as screen is fading to screensaver prevents input to shell
Do you use x11 or wayland session? Could you add your journalctl log after seeing the issue? ** Changed in: gnome-shell (Ubuntu Jammy) Status: New => Incomplete ** Changed in: gnome-shell (Ubuntu Jammy) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964545 Title: 42beta: moving mouse as screen is fading to screensaver prevents input to shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964442] Re: [jammy Regression] signing a changes file in gnome-terminal sends keys to the terminal
Thank you for your bug report. Is that in a standard Ubuntu session, under x11 or wayland? could you attach the journalctl log from around the time of the problem? ** Changed in: gnome-terminal (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-terminal (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/1964442 Title: [jammy Regression] signing a changes file in gnome-terminal sends keys to the terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1964442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961955] Re: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream
@Sujith, what do you mean there, pulled from where? there is no such line upstream... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961955 Title: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1961955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964979] [NEW] Jammy server installer unable to set IPv4 static nor switch back to DHCP
Public bug reported: I found that the jammy-live-server-2022-03-10-amd64.iso is not able to set up the NIC to use IPv4 Static, nor be switched back to DHCP once Static addressing has been attempted. I started an UbuntuForums thread here to seek confirmation if it sounded like there was a defect, or if I was entering incorrect input. Unable to select manual IPv4 during attempted installation of 22.04 Jammy https://ubuntuforums.org/showthread.php?t=2472852 The settings I put in for Manual IPv4 are as follows: Subnet: 10.10.10.0/24 Address: 10.10.10.9 Gateway: 10.10.10.1 Name server: 10.10.10.10 Pushing Save blanked out the name server field, and it never finishes the "Applying changes" step. We have a Class C IPv4 subnet. Addresses 10.10.10.1 through 10.10.10.254 I tried adjusting back to DHCP vs manual... now it also no longer picks up an address from our DHCP server. The spinning "Applying changes" attempting to test DHCP again. ** Affects: live-build (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/1964979 Title: Jammy server installer unable to set IPv4 static nor switch back to DHCP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/1964979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964541] Re: 42beta: Cannot re-arrange Firefox browser tabs
Daniel, could you check on this one? ** Changed in: firefox (Ubuntu Jammy) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964541 Title: 42beta: Cannot re-arrange Firefox browser tabs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964841] Re: Hold libhandy in jammy-proposed until we update gnome-control-center
** Changed in: libhandy-1 (Ubuntu) Status: New => In Progress ** Changed in: libhandy-1 (Ubuntu) Assignee: (unassigned) => Jeremy Bicha (jbicha) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964841 Title: Hold libhandy in jammy-proposed until we update gnome-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhandy-1/+bug/1964841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964496] Re: [GS 42] display switching key does not work
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Changed in: gnome-shell (Ubuntu) Importance: Low => High ** Tags added: rls-jj-incomng ** Tags removed: rls-jj-incomng ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964496 Title: [GS 42] display switching key does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15
** Also affects: zlib (Ubuntu Focal)
Importance: Undecided
Status: New
** Description changed:
SRU Justification:
==
[Impact]
* zlib: compressBound() returns an incorrect result on IBM z15 hardware.
* Passing the result of compressBound() to compress() results
in an error code.
* This is because compressBound() is not adjusted for DFLTCC.
[Fix]
* Adjust compressBound() for DFLTCC like it's already done
for deflateBound().
* Since zlib project does not accept patches at the moment,
the fix has been integrated into the DFLTCC pull request:
https://github.com/madler/zlib/pull/410
The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
* The fix extracted out of the above is:
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff
[Test Plan]
* An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
with Ubuntu Server 21.10 (or 22.04).
* A test can be done based on the following C test program:
#include
#include
#include
int main() {
Bytef in_buf[128], out_buf[1024];
for (size_t i = 0; i < sizeof(in_buf); i++)
in_buf[i] = rand();
uLongf dest_len = compressBound(sizeof(in_buf));
assert(dest_len <= sizeof(out_buf));
int ret = compress(out_buf, &dest_len,
in_buf, sizeof(in_buf));
assert(ret == Z_OK);
}
* The test needs to be done by IBM, due to the requirements
for the special z15 hardware.
* A successful test was just completed, based on the version in jammy-
proposed, which is at the same code level that the impish version this
SRU is targeted for.
[Where problems could occur]
* If the adjustment of compressBound() for DFLTCC is done
erroneously the issue can still be present or in worst case
even affect Z systems other than z15 only.
* The compression can become errorneous with the new changes,
e.g. in compressBound.
* Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
(incl. the bit definitions), may cause various and unforseen defects.
* Any build time issues that might have been introduced by this patch
can be identified by a test build; this was done and is available here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427
[Other Info]
- * Only impish and jammy are affected.
+ * Ubuntu jammy, impish and focal are affected.
__
Description: zlib: compressBound() returns an incorrect result on z15
Symptom: Passing the result of compressBound() to compress()
results in an error code.
Problem: compressBound() is not adjusted for DFLTCC.
Solution: Adjust compressBound() for DFLTCC like it's already done
for deflateBound(). Since zlib project does not accept
patches at the moment, the fix has been integrated into
the DFLTCC pull request:
https://github.com/madler/zlib/pull/410
The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
Reproduction: z15 only:
#include
#include
#include
int main() {
Bytef in_buf[128], out_buf[1024];
for (size_t i = 0; i < sizeof(in_buf); i++)
in_buf[i] = rand();
uLongf dest_len = compressBound(sizeof(in_buf));
assert(dest_len <= sizeof(out_buf));
int ret = compress(out_buf, &dest_len,
in_buf, sizeof(in_buf));
assert(ret == Z_OK);
}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961427
Title:
zlib: compressBound() returns an incorrect result on z15
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1961427/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954683] Re: grub is missing secure boot support for compressed kernels (our arm64 kernels)
** Changed in: grub2 (Ubuntu Impish) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954683 Title: grub is missing secure boot support for compressed kernels (our arm64 kernels) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1954683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958523] Re: [amdgpu] Static-noise-like effect
I have following kernels installed: - 5.13.0-35-generic - 5.14.0-1024-oem - 5.14.0-1027-oem Kernel 5.13 does not work. The other two do work. I see the problem on Lenovo Ideapad 320. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958523 Title: [amdgpu] Static-noise-like effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964979] Re: Jammy server installer unable to set IPv4 static nor switch back to DHCP
** Package changed: live-build (Ubuntu) => subiquity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964979 Title: Jammy server installer unable to set IPv4 static nor switch back to DHCP To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1964979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964814] Re: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1
** Changed in: linux-firmware (Ubuntu Jammy) Status: Fix Committed => 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/1964814 Title: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961995] Re: black screen after login
On check boot logs. Boot logs are incomplete and unreadable. After a few boots ubuntu finally loads desktop. ** Package changed: ubuntu => ubuntu-advantage-desktop-daemon (Ubuntu) ** Changed in: ubuntu-advantage-desktop-daemon (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961995 Title: black screen after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-desktop-daemon/+bug/1961995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964600] Re: [MIR] gnome-bluetooth3
** Changed in: gnome-bluetooth3 (Ubuntu) Assignee: (unassigned) => Ioanna Alifieraki (joalif) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964600 Title: [MIR] gnome-bluetooth3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth3/+bug/1964600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957932] Re: [MIR] rustc, cargo
On Fri, Mar 11, 2022 at 10:17:47AM -, Simon Chopin wrote:
> @sbeattie there's some context on those various fields in
> https://github.com/cpaelzer/ubuntu-mir/pull/3
Thanks for this.
> Basically X-Cargo-Built-Using should be folded into Built-Using.
I agree with this, but is there a plan to land this in jammy?
If not, our tooling needs to compensate.
> There has been no talk of automating detection of packages that ought
> to have those fields, but that does sound like a good idea.
I think something needs to be in place, or there runs the risk of things
needing to pick up updates that don't get them applied.
> However, in the case of rustc and any future main package built using
> Rust, there are going to be vendored dependencies that are not packaged
> at all. It doesn't seem like a good idea to me to document those in the
> same fields as the dependencies that are separately packaged but
> statically linked, which is why I proposed shipping the Cargo.lock file.
>
> If you'd prefer, we could instead ship it in another field, maybe
> X-Vendored-Sources (as mentioned before, Built-Using seems out of scope
> for that).
It would be great if we could get this information as a field in the
Packages info (modulo concerns about size explosion as the set of
packaged rust software expands). I agree that it is not appropriate
for Built-Using; X-Vendored-Sources sounds great (if only we could
get this incorporated across more language ecosystems!). It would
probably be beneficial to have both the field in the packages metadata
list as well as the Cargo.lock file, to be able to identify which
crate versions were incorporated in superseded versions, if need be.
> For instance, using this small Python snippet, I get this for
> the Cargo.lock file shipped in rustc (Jammy):
>
> $ zcat Cargo.lock.gz | python3 -c "import toml; import sys; print(',
> '.join(f\"{p['name']}/{p['version']}\" for p in
> toml.load(sys.stdin)['package'] if 'source' in p))"
Thanks for this, lots to chew on here. Quite a few rust crates have
at least two versions of themselves in the list, which based on reading,
seems to be normal in the ecosystem, but then leads to issues like:
crossbeam-utils/0.7.2
crossbeam-utils/0.8.5
while the latter was patched to address CVE-2022-23639 in the current
jammy packaging, the former (in vendor/crossbeam-utils-0.7.2) was not.
While upstream crossbeam-utils yanked all of the 0.8.x versions < 0.8.7,
but there doesn't appear to be a fixed version of 0.7.x from upstream.
That's somewhat concerning about the ecosystem as a whole.
> The 'if source in p' statement filters out crates that are internal to
> rustc. Surprinsingly, the remaining rustc-* crates are separately
> packaged forks of existing crates.
That is also less than ideal.
> Would the security team feel more comfortable with this?
Yes, I think so.
Thanks!
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-23639
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957932
Title:
[MIR] rustc, cargo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1957932/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964828] Re: ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook s
*** This bug is a duplicate of bug 1963697 *** https://bugs.launchpad.net/bugs/1963697 ** This bug has been marked a duplicate of bug 1963697 Ubiquity crashes Kubuntu Jammy after selecting "install Kubuntu" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964828 Title: ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist- packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general- hooks/ubuntu.py", line 81, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1016, in attach_casper_md5check check = json.loads(report['CasperMD5json']) File "/usr/lib/python3.10/collections/__init__.py", line 1102, in __getitem__ raise KeyError(key) KeyError: 'CasperMD5json' kubuntu@kubuntu:~$ Gtk-Message: 21:22:43.923: Failed to load module "colorreload-gtk-module" ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1964828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954683] Re: grub is missing secure boot support for compressed kernels (our arm64 kernels)
I have updated the Impact and Test Plan to provide an end-to-end testing of secure boot on arm64. ** Description changed: [Impact] - Compressed kernels as we have on arm64 cause grub to fail in two ways: + arm64 systems currently cannot have their grub updated when booted in secure boot mode, despite booting fine, as the postinst runs grub-check-signatures and grub-check-signatures does not handle the compressed kernels used on arm64. - 1. In all versions, grub-check-signatures will fail to verify the - binaries using sbverify, complain about that in debconf, and then abort - the installation/upgrade of grub-efi-arm64-signed, kernel and grub - upgrades can hence not be installed on secure boot systems. - - 2. In 2.06, the verifiers framework runs before any decompression, - causing the kernels to fail verification, as it tries to verify the - compressed data. In grub 2.04, we manually verified the file after we - had opened it (hence after all filters). - - The rest of the SRU template only refers to point 1, as point 2 only - applies to the development series jammy. + It seems the cloud images only ship unsigned grub at the moment, but + there may be other images shipping signed boot stack that customers + would expect to work (and then fail during a grub update) and we can + also consider this hardware enablement of arm64 secure boot. [Attack plan] 1. Modify grub-check-signatures to optionally decompress kernels before passing them to sbverify 2. Modify grub to either a) verify after decompress b) disable shim_lock verifier on arm64, and only use the rhboot We do not know if this is a long-term solution, we really should migrate back to kernels that are proper EFI executables themselves such that we can use standard EFI functions to run them as well. [Test plan] - On a secure boot ARM64 VM: + 1. Grab an arm64 cloud image + 2. Boot in qemu, WITHOUT SECURE BOOT (AAVMF_VARS.fd): Install grub-efi-arm64-signed shim-signed if not already installed + 3. Reboot in secure mode (using AAVMF_VARS.ms.fd) + 4. See that the system boots + 5. apt install --reinstall grub-efi-arm64-signed, observe failure message about unsigned kernels + 6. apt install grub-efi-arm64-signed/focal-proposed, observe success + 6. Install another signed kernel, observe success (*) - 1) Run grub-check-signatures to ensure it verifies the kernels successfully - 2) Install kernel upgrade and reboot into it + shim/grub may need to be launched manually in qemu as MS variables place + the EFI shell first in the boot order, select the boot entry for the + disk from the interrupt menu, or do FS0:, followed by + \EFI\BOOT\BOOTAA64.EFI in the EFI shell to launch it. + + (*) Surprisingly maybe, kernel upgrades are not affected as they do not + call grub-check-signatures, so installing an unsigned kernel still + succeeds, however, this is not a regression from this patch. [Where problems could occur] We only modify the grub-check-signatures script in the SRU to add decompression. This could change the behavior of the script, and introduce new bugs that cause false positives or false negatives. + + [Other info: Impact; 2.06-only, not relevant for SRU] + In 2.06, the verifiers framework runs before any decompression, causing the kernels to fail verification, as it tries to verify the compressed data. In grub 2.04, we manually verified the file after we had opened it (hence after all filters). ** Changed in: grub2 (Ubuntu Focal) 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/1954683 Title: grub is missing secure boot support for compressed kernels (our arm64 kernels) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1954683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948507] Re: TypeError when computing QOS feature name
** Also affects: cinder (Ubuntu) Importance: Undecided Status: New ** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/yoga Importance: Undecided Status: New ** Changed in: cloud-archive/yoga Status: New => Triaged ** Changed in: cloud-archive/yoga Importance: Undecided => High ** Also affects: cinder (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: cinder (Ubuntu Jammy) Status: New => Triaged ** Changed in: cinder (Ubuntu Jammy) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948507 Title: TypeError when computing QOS feature name To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1948507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964982] [NEW] [FFe] KDE frameworks 5.92.0 into Jammy archive
Public bug reported: This bug report is a Feature Freeze Exception request on behalf of the Kubuntu team for KDE Frameworks 5.92.0 (updated from 5.91.0). Announcement and changelog: https://kde.org/announcements/frameworks/5/5.92.0/ As is usual with a KDE Frameworks release, this is a mixture of new some new features and incremental important bugfixes. Please note that most of the new KDE Frameworks features are not going to be effective yet, since we are not updating to major versions of KDE's Plasma or KDE's Applications. So this is, in practice, largely like a bugfix release. We currently have this staged in https://launchpad.net/~kubuntu- ppa/+archive/ubuntu/staging- frameworks/+packages?field.name_filter=&field.status_filter=published&field.series_filter=jammy if you wish to inspect the packages. We also have testers that have been running a system with this staged update and have reported no problems. I/we also commit to fixing any issue that might be inadvertently introduced with this update. The following packages form the KDE Frameworks set: attica-kf5 baloo-kf5 bluez-qt breeze-icons extra-cmake-modules frameworkintegration kactivities-kf5 kactivities-stats kapidox karchive kauth kbookmarks kcalcore kcmutils kcodecs kcompletion kconfig kconfigwidgets kcontacts kcoreaddons kcrash kdav kdbusaddons kdeclarative kded kdelibs4support kdesignerplugin kdesu kdewebkit kdnssd-kf5 kdoctools kemoticons kfilemetadata-kf5 kglobalaccel kguiaddons kholidays khtml ki18n kiconthemes kidletime kimageformats kinit kio kirigami2 kitemmodels kitemviews kjobwidgets kjs kjsembed kmediaplayer knewstuff knotifications knotifyconfig kpackage kparts kpeople kplotting kpty kquickcharts kross krunner kservice ksyntax-highlighting ktexteditor ktextwidgets kunitconversion kwallet-kf5 kwayland kwidgetsaddons kwindowsystem kxmlgui kxmlrpcclient modemmanager-qt networkmanager-qt oxygen-icons5 plasma-framework prison-kf5 purpose qqc2-desktop-style solid sonnet syndication threadweaver ** Affects: plasma-framework (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/1964982 Title: [FFe] KDE frameworks 5.92.0 into Jammy archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-framework/+bug/1964982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952763] Re: [SRU] manilaclient.common.apiclient.exceptions.Forbidden: Access was denied to this resource. (HTTP 403)
Fix proposed to branch: master Review: https://review.opendev.org/c/openstack/charm-manila/+/833847 ** Changed in: charm-manila 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/1952763 Title: [SRU] manilaclient.common.apiclient.exceptions.Forbidden: Access was denied to this resource. (HTTP 403) To manage notifications about this bug go to: https://bugs.launchpad.net/charm-manila/+bug/1952763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961300] Re: linux-azure: Fix NUMA node assignment when kernel boots with custom NUMA topology
** Changed in: linux-azure (Ubuntu Focal) Status: Fix Committed => 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/1961300 Title: linux-azure: Fix NUMA node assignment when kernel boots with custom NUMA topology To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1961300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840560] Re: "error: can't find command hwmatch" during grub
Removing wrong block-proposed-* tags, these were never uploaded on their own, so there is nothing to block. ** Tags removed: block-proposed-focal block-proposed-hirsute block- proposed-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840560 Title: "error: can't find command hwmatch" during grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1840560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940112] Re: missing dependency of qemu-efi-aarch64 when testing arm platforms
** Tags added: servcert-216 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940112 Title: missing dependency of qemu-efi-aarch64 when testing arm platforms To manage notifications about this bug go to: https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1940112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963758] Re: cups-browsed crashed with SIGSEGV in timeout_free()
Sorry, I meant to comment this already: The context which I experienced this crash was during a dist-upgrade from impish to jammy (`do-release-upgrade --devel-release` in a fresh impish VM). It appeared that cups-browsed crashing resulted in gnome- shell crashing too. This killed the upgrade process, and left my VM in a bad state (gnome-shell would not start etc.). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963758 Title: cups-browsed crashed with SIGSEGV in timeout_free() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1963758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964983] [NEW] IPU6 camera has no function on Andrews MLK
Public bug reported: The new platform uses yet another ov sensor OV02C10. Prerequisites: * kernel fix: https://github.com/intel/ipu6-drivers/commit/778819bef3d8ac8d6b24342372e006b7b43e381e * ipu fw: TBD. * libcamhal: https://github.com/intel/ipu6-camera-hal/commit/b9b56de11de70b7c4520595176e4831bacf4a7fe ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: High Assignee: You-Sheng Yang (vicamo) Status: Incomplete ** Affects: linux-oem-5.17 (Ubuntu) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Tags: oem-priority originate-from-1951907 somerville ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu) Importance: Undecided => High ** Changed in: linux-oem-5.17 (Ubuntu) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete ** Changed in: linux-firmware (Ubuntu) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Tags added: oem-priority originate-from-1951907 somerville -- 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
Re: [Bug 1964814] Re: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1
Thanks bernstein also I have solved with yours: sudo rm /lib/firmware/ath11k/WCN6855/hw2.1 after: sudo apt-get update && sudo apt-get dist-upgrade -y Il 15.03.2022 16:11 bernstein ha scritto: > thanks Allan! For me a simple : > > rm /lib/firmware/ath11k/WCN6855/hw2.1 > > is all that was needed before restarting the update process. > > The result is that before the failed upgrade it looked like this : > > lrwxrwxrwx 1 root root 5 Feb 17 08:51 hw2.1 -> hw2.0 > > and after the successful upgrade it now looks like this : > > drwxr-xr-x 2 root root 6 Mär 15 15:34 . > lrwxrwxrwx 1 root root 17 Mär 14 11:40 amss.bin -> ../hw2.0/amss.bin > lrwxrwxrwx 1 root root 20 Mär 14 11:40 board-2.bin -> ../hw2.0/board-2.bin > lrwxrwxrwx 1 root root 15 Mär 14 11:40 m3.bin -> ../hw2.0/m3.bin > lrwxrwxrwx 1 root root 18 Mär 14 11:40 regdb.bin -> ../hw2.0/regdb.bin > > which at first glance is the same > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1964926). > https://bugs.launchpad.net/bugs/1964814 [1] > > Title: > linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1 > > Status in linux-firmware package in Ubuntu: > Fix Committed > Status in linux-firmware source package in Jammy: > Fix Committed > > Bug description: > linux-firmware fails to upgrade with: > > unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg- > new': No such file or directory > > $ sudo apt dist-upgrade > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > Calculating upgrade... Done > The following packages will be upgraded: > linux-firmware > 1 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade. > Need to get 0 B/238 MB of archives. > After this operation, 24.9 MB of additional disk space will be used. > Do you want to continue? [Y/n] y > (Reading database ... 272091 files and directories currently installed.) > Preparing to unpack .../linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb ... > Unpacking linux-firmware (20220314.gitcd01f857-0ubuntu1) over (20220302.gitee0667aa-0ubuntu1) ... > dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): > unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory > No apport report written because the error message indicates an issue on the local system > update-initramfs: Generating /boot/initrd.img-5.15.0-23-generic > I: The initramfs will attempt to resume from /dev/dm-2 > I: (/dev/mapper/vgubuntu-swap_1) > I: Set the RESUME variable to override this. > update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic > I: The initramfs will attempt to resume from /dev/dm-2 > I: (/dev/mapper/vgubuntu-swap_1) > I: Set the RESUME variable to override this. > Errors were encountered while processing: > /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964814/+subscriptions [2] Voucher MISE per P.IVA e PMI: fino a 2500€ per la Banda Ultralarga. https://www.tiscali.it/business/prodotti/voucher/?r=TS0A00025&dm=link&p=tiscali&utm_source=tiscali&utm_medium=link&utm_campaign=voucherbusiness&utm_content=voucherbusiness&wt_np=tiscali.link.footermail.voucher.business.btb. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964814 Title: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964136] Re: Settings item not shown in System menu
This bug was fixed in the package gnome-shell - 42~beta-1ubuntu2 --- gnome-shell (42~beta-1ubuntu2) jammy; urgency=medium * Add patch to restore Settings item in system menu, because we're using the older gnome-control-center.desktop) (LP: #1964136) -- Jeremy Bicha Thu, 10 Mar 2022 09:01:53 -0500 ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => 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/1964136 Title: Settings item not shown in System menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964122] Re: Cannot connect to router with admin page over TLS v1.0
Glad that you figured out a workaround, and thanks for documenting it here! ** Changed in: firefox (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964122 Title: Cannot connect to router with admin page over TLS v1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15
Let me check if the patch applies to the focal version, too. A separate debdiff is needed for focal anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961427 Title: zlib: compressBound() returns an incorrect result on z15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1961427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960340] Re: gnu-efi sets a wrong number of symbols in the COFF header
This bug was fixed in the package gnu-efi - 3.0.13+git20210716.269ef9d-2ubuntu1 --- gnu-efi (3.0.13+git20210716.269ef9d-2ubuntu1) jammy; urgency=medium * Set NumberOfSymbols to zero in COFF header (LP: #1960340) -- Alfonso Sanchez-Beato Tue, 08 Feb 2022 18:12:16 +0100 ** Changed in: gnu-efi (Ubuntu) Status: Fix Committed => 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/1960340 Title: gnu-efi sets a wrong number of symbols in the COFF header To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnu-efi/+bug/1960340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960585] Re: gnome-shell crashed with SIGSEGV in maybe_update_frame_info() from notify_view_crtc_presented() from meta_kms_page_flip_data_flipped() from flush_callbacks() from callback_idle()
This bug was fixed in the package mutter - 42~beta-1ubuntu2 --- mutter (42~beta-1ubuntu2) jammy; urgency=medium * debian/patches: Skip monitor-size tests that may fail on autopkgtest -- Marco Trevisan (Treviño) Mon, 14 Mar 2022 02:27:21 +0100 ** Changed in: mutter (Ubuntu) Status: Fix Committed => 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/1960585 Title: gnome-shell crashed with SIGSEGV in maybe_update_frame_info() from notify_view_crtc_presented() from meta_kms_page_flip_data_flipped() from flush_callbacks() from callback_idle() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1960585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942702] Re: Ubuntu Dock "Show Applications" button: click target doesn't extend to screen edges
This bug was fixed in the package yaru-theme - 22.04.1 --- yaru-theme (22.04.1) jammy; urgency=medium [ Marco Trevisan (Treviño) ] * New upstream release * open-pr-on-changes: Include gnome-shell icons * GNOME Shell 42 theme sync * dock: Update CSS to support dash-to-dock 71+, and move most styling here (LP: #1942702) * debian/control: Set Breaks on older GNOME Shell versions * gnome-shell: Add a note on recent Yaru changes [ Paul Kepinski ] * Add Cinnamon theme upstream fetch * Add GTK mate and mate-dark variants into master * Add application-x-sms-rom fullcolor icon * Add border on OSD panels * Add cinnamon variants * Add dock styles to GS hc variant * Add folder-visting-symbolic icon * Add gtksourceview mate and mate-dark variants * Add icon theme variant support * Add metacity mate and mate-dark variants * Add missing Evince icons * Add missing GTK3 render-assets script * Add missing characters icons * Add missing classes on power-profile-*-symbolic icons * Add missing eog icon * Add missing gcc symbolic icons * Add missing todo symbolics icons * Add missing yelp icons * Add new GS screen-privacy-icons * Add new upstream symbolics * Add new upstream vpn symbolics * Add org.gnome.Usage-symbolic symlink symbolic icon * Add preferences-desktop-keyboard icon * Add review-symbolic icon * Add selection-mode-symbolic icon * Add some symlinks * Add support for GS42 - upstream sync * Add system-* action fullcolor icons * Doc update * Drop GDM purple background * Drop depracated vars * Drop grey scale assets * Drop grey selected rows * Drop outdated communitheme-snap files * Drop treeview grey selected row tweak * Fix GH actions branches * Fix Gnome Shell assets * Fix Gtk3 headerbar radius * Fix Gtk4 mate dark assets symlink * Fix Yaru-dark gtk2 assets * Fix applications-system icons * Fix broken duplicated config-users icon symlink * Fix evince branch name * Fix find-location-symbolic crooked path * Fix index.theme flavour overwriting * Fix mate-dark gtk4 variant * Fix meson warning * Fix metacity mate variant * Fix notifications states look * Fix padlock-open-symbolic icon * Fix render assets script * Fix slider backdrop look * Fix transparent guake notebook headerbar * Force meson options to true in build CI * Get some icons from mate branch * Gnome shell sync slide handle * Gnome shell upstream sync 3328 * Gtk3 fix treeview progressbar * Gtk4 fix radius * Include Mate apps styling in master * Increase windowcontrols button size * Make MATE panel dark * Mimic Gtk3 switch with gtk4 ones * Optimize assets * Provide :checked state for buttons * Remove Cinnamon orange close assets * Remove adaptive margins for preferences * Remove shadow on normal buttons * Rename Gtk-3.20 into Gtk-3.0 * Rename Suru to Yaru * Render Gtk2 assets * Render Gtk2 dark assets * Render Gtk3 and Gtk4 assets * Render assets-external * Replace aubergine by orange in some icons * Replace ls by find * Revert close button to upstream look * Revert last commit * Revert upstream border-radius * Rework .window-caption * Set mate flavour false by default * Sort symbolic action listing * Split cinnamon shell theme from variants * Symlink ups to uninterruptible-power-supply (symbolic) * Sync GS with upstream * Sync Gnome Shell with upstream * Sync Gtk3 + Libhandy + GS with Gtk4 radii * Sync Gtk3 light headerbar bg with Gtk4 * Sync Gtk3 with upstream * Sync Libadwaita with upstream * Sync Mate variants assets * Sync _defaults with upstream * Sync check assets with upstream * Sync filemanager-app icon * Sync gtk4 with upstream * Sync icon theme with upstream * Sync image-missing-symbolic with upstream * Sync symbolic icons with upstream * Update CONTRIBUTING screenshots * Update README * Use $button_radius for popover * Use $success instead of $suggested * Use exported accent for red close button [ Muqtadir ] * add pre-installed apps to list * sync symbolics for #3057 #3058 #3059 * add symlink app-remove-symbolic.svg * fix toggles for hc * added camera symbolics * missing-symbolics part2: multimedia * missing-symbolics part2: generic-symbols * update disabled-symbolics * fix screen-privacy-disabled-symbolic.svg * add missing-icons-symbolics-part2: time * add gnome-shell-start * improve OSK-symbolics * refine battery-symbolics: * fix classes in legacy-icons * phosh: auth_sim_icon * phosh symbolics + missing symbolics * symlink org.gnome.Shell.Extensions-symbolic.svg * debian/changelog: * add 22x22/categories to yaru-theme-icon.install * update session overrides * update changelog * sync GNOME-Shell resources * issue no #3221 add instructions for debian files * mate: add panel-icons * icons: modify meson and deb files * remove orange in window_controls assets
[Bug 1947467] Re: GNOME 40 wayland-session exiting fullscreen doesn't restore original size & position
This bug was fixed in the package mutter - 42~beta-1ubuntu2 --- mutter (42~beta-1ubuntu2) jammy; urgency=medium * debian/patches: Skip monitor-size tests that may fail on autopkgtest -- Marco Trevisan (Treviño) Mon, 14 Mar 2022 02:27:21 +0100 ** Changed in: mutter (Ubuntu) Status: Fix Committed => 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/1947467 Title: GNOME 40 wayland-session exiting fullscreen doesn't restore original size & position To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1947467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933996] Re: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]
This bug was fixed in the package mutter - 42~beta-1ubuntu2 --- mutter (42~beta-1ubuntu2) jammy; urgency=medium * debian/patches: Skip monitor-size tests that may fail on autopkgtest -- Marco Trevisan (Treviño) Mon, 14 Mar 2022 02:27:21 +0100 ** Changed in: mutter (Ubuntu) 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/1933996 Title: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1933996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917939] Re: Windows maximise underneath dock after monitor sleep
This bug was fixed in the package mutter - 42~beta-1ubuntu2 --- mutter (42~beta-1ubuntu2) jammy; urgency=medium * debian/patches: Skip monitor-size tests that may fail on autopkgtest -- Marco Trevisan (Treviño) Mon, 14 Mar 2022 02:27:21 +0100 ** Changed in: mutter (Ubuntu) Status: Fix Committed => 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/1917939 Title: Windows maximise underneath dock after monitor sleep To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1917939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930567] Re: Popup menus don't appear at all if opened close to inter-monitor boundaries in Wayland sessions
This bug was fixed in the package mutter - 42~beta-1ubuntu2 --- mutter (42~beta-1ubuntu2) jammy; urgency=medium * debian/patches: Skip monitor-size tests that may fail on autopkgtest -- Marco Trevisan (Treviño) Mon, 14 Mar 2022 02:27:21 +0100 ** Changed in: mutter (Ubuntu) Status: Fix Committed => 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/1930567 Title: Popup menus don't appear at all if opened close to inter-monitor boundaries in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1930567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830637] Re: Keyboard layout LED stays on after first toggle
This bug was fixed in the package mutter - 42~beta-1ubuntu2 --- mutter (42~beta-1ubuntu2) jammy; urgency=medium * debian/patches: Skip monitor-size tests that may fail on autopkgtest -- Marco Trevisan (Treviño) Mon, 14 Mar 2022 02:27:21 +0100 ** Changed in: mutter (Ubuntu) Status: Fix Committed => 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/1830637 Title: Keyboard layout LED stays on after first toggle To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1830637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934243] Re: thunderbird drag-n-drop move messages fails on Wayland
Joe, this sounds like a different issue from the one originally reported here. A cursory glance at the upstream bugs for drag'n'drop didn't find matching issues. Paul & Joe: would you mind filing upstream bug reports at https://bugzilla.mozilla.org/enter_bug.cgi?product=Thunderbird, and sharing the links to them here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934243 Title: thunderbird drag-n-drop move messages fails on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1934243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964984] [NEW] Fix OOB handling RX packets in heavy traffic
Public bug reported: SRU Justification: [Impact] This is reproducible on systems which already have heavy background traffic. On top of that, the user issues one of the 2 docker pulls below: docker pull nvcr.io/ea-doca-hbn/hbn/hbn:latest OR docker pull gitlab-master.nvidia.com:5005/dl/dgx/tritonserver:22.02-py3-qa The second one is a very large container (17GB) When they run docker pull, the OOB interface stops being pingable, the docker pull is interrupted for a very long time (>3mn) or times out. [Fix] * Update the RX_CQE_CI before updating the RX_PI to avoid a race condition where we wrongly inform HW that there is space for the WQE. * disable the RX DMA while we are handling incoming packets to avoid overflow. [Test Case] * Created a script which loops 200 times and does a docker pull in each loop: docker pull nvcr.io/ea-doca-hbn/hbn/hbn:latest OR docker pull gitlab-master.nvidia.com:5005/dl/dgx/tritonserver:22.02-py3-qa [Regression Potential] * This could result in slower handling since we are disabling/enabling the DMA periodically. * Although this fix has been tested by the people who opened the bug, QA needs to thoroughly test it to make sure it is not reproducible. ** Affects: linux-bluefield (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/1964984 Title: Fix OOB handling RX packets in heavy traffic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1964984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942619] Re: WARNING: ... decide_link_settings+0x1ab/0x1d0 [amdgpu]
I've been running the ubuntu generic kernel (5.13.0-28-generic) for the last 33 days without the issue reoccurring, so I think this can be closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942619 Title: WARNING: ... decide_link_settings+0x1ab/0x1d0 [amdgpu] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903289] Re: [FFE] Power guest secure boot with static keys: GRUB2 portion
** Tags removed: targetmilestone-inin2104 ** Tags added: targetmilestone-inin2210 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903289 Title: [FFE] Power guest secure boot with static keys: GRUB2 portion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903288] Re: Power guest secure boot with static keys: kernel portion
** Tags removed: targetmilestone-inin2104 ** Tags added: targetmilestone-inin2210 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903288 Title: Power guest secure boot with static keys: kernel portion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948507] Re: TypeError when computing QOS feature name
** Changed in: cloud-archive Status: Triaged => 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/1948507 Title: TypeError when computing QOS feature name To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1948507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964827] Re: zfs-linux upstream at 2.1.3, jammy has 2.1.2
Here's a ppa with working packages: https://launchpad.net/~satadru- umich/+archive/ubuntu/zfs-experimental -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964827 Title: zfs-linux upstream at 2.1.3, jammy has 2.1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964987] [NEW] FFe: Sync tomcat9 9.0.31-1~deb10u6 (universe) from Debian buster (security)
Public bug reported: Please sync tomcat9 9.0.31-1~deb10u6 (universe) from Debian buster (security) Explanation of FeatureFreeze exception: The Ubuntu package does not have any ubuntu specific patches added after FeatureFreeze in focal However Debian package has bugfixes and security updates which does not exist in the Ubuntu package. Changelog entries since current focal version 9.0.31-1: tomcat9 (9.0.31-1~deb10u6) buster-security; urgency=high * Team upload. * CVE-2021-30640: Fix NullPointerException. If no userRoleAttribute is specified in the user's Realm configuration its default value will be null. This will cause a NPE in the methods doFilterEscaping and doAttributeValueEscaping. This is upstream bug https://bz.apache.org/bugzilla/show_bug.cgi?id=65308 * Fix CVE-2021-41079: Apache Tomcat did not properly validate incoming TLS packets. When Tomcat was configured to use NIO+OpenSSL or NIO2+OpenSSL for TLS, a specially crafted packet could be used to trigger an infinite loop resulting in a denial of service. -- Markus Koschany Sat, 25 Sep 2021 22:17:13 +0200 tomcat9 (9.0.31-1~deb10u5) buster-security; urgency=high * Team upload. * Fix CVE-2021-30640: A vulnerability in the JNDI Realm of Apache Tomcat allows an attacker to authenticate using variations of a valid user name and/or to bypass some of the protection provided by the LockOut Realm. * Fix CVE-2021-33037: Apache Tomcat did not correctly parse the HTTP transfer-encoding request header in some circumstances leading to the possibility to request smuggling when used with a reverse proxy. Specifically: - Tomcat incorrectly ignored the transfer encoding header if the client declared it would only accept an HTTP/1.0 response; - Tomcat honoured the identify encoding; and - Tomcat did not ensure that, if present, the chunked encoding was the final encoding. (Closes: #991046) -- Markus Koschany Sat, 07 Aug 2021 18:25:15 +0200 tomcat9 (9.0.31-1~deb10u4) buster-security; urgency=medium * CVE-2021-25122 * CVE-2021-25329 -- Moritz Mühlenhoff Mon, 12 Apr 2021 16:45:06 +0200 tomcat9 (9.0.31-1~deb10u3) buster-security; urgency=medium * Fixed CVE-2020-13943: HTTP/2 request mix-up. If an HTTP/2 client exceeded the agreed maximum number of concurrent streams for a connection (in violation of the HTTP/2 protocol), it was possible that a subsequent request made on that connection could contain HTTP headers - including HTTP/2 pseudo headers - from a previous request rather than the intended headers. This could lead to users seeing responses for unexpected resources. * Fixed CVE-2020-17527: HTTP/2 request header mix-up. It was discovered that Apache Tomcat could re-use an HTTP request header value from the previous stream received on an HTTP/2 connection for the request associated with the subsequent stream. While this would most likely lead to an error and the closure of the HTTP/2 connection, it is possible that information could leak between requests. -- Emmanuel Bourg Tue, 19 Jan 2021 23:31:47 +0100 ** Affects: tomcat9 (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/1964987 Title: FFe: Sync tomcat9 9.0.31-1~deb10u6 (universe) from Debian buster (security) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat9/+bug/1964987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794841] Re: flash-kernel still using u-boot for Raspberry Pi
Ha! This aged well! I finally managed to switch us away from using u-boot (at least on the classic images, Ubuntu Pi for Server and Desktop, though not on Core) during the Groovy (20.10) release, but somehow managed to forget about closing this bug! ** Changed in: flash-kernel (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794841 Title: flash-kernel still using u-boot for Raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1794841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940112] Re: missing dependency of qemu-efi-aarch64 when testing arm platforms
** Changed in: plainbox-provider-checkbox Milestone: None => 0.64.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940112 Title: missing dependency of qemu-efi-aarch64 when testing arm platforms To manage notifications about this bug go to: https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1940112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897286] Re: package libc6:amd64 2.31-0ubuntu9.1 failed to install/upgrade: package libc6:amd64 is already installed and configured
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dpkg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897286 Title: package libc6:amd64 2.31-0ubuntu9.1 failed to install/upgrade: package libc6:amd64 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1897286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964496] Re: [GS 42] display switching key does not work
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5217 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5217 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5217 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged ** Tags added: upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964496 Title: [GS 42] display switching key does not work To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1964496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964496] Re: [GS 42] display switching key does not work
I've just tested: same issue in xorg, fyi. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964496 Title: [GS 42] display switching key does not work To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1964496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962309] Re: flash-kernel doesn't properly support Pi Zero 2
*** This bug is a duplicate of bug 1928314 *** https://bugs.launchpad.net/bugs/1928314 Effectively a duplicate of LP: #1928314 which has a longer explanation :) ** This bug has been marked a duplicate of bug 1928314 Wrong DTB chosen for Raspberry Pi Compute Module 4 (all.db) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962309 Title: flash-kernel doesn't properly support Pi Zero 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1962309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928314] Re: Wrong DTB chosen for Raspberry Pi Compute Module 4 (all.db)
Sorry, but this is a bit of a mis-understanding. The situation on the Pi is a bit more complicated than this: There's long been an expectation in the Raspberry Pi community (driven largely by Raspbian's upgrade strategy on the release of new Pi models) that one can move an SD card from Pi to Pi (obviously this doesn't *exactly* apply to those Compute Module models with eMMC, but it's still relevant to this issue so bear with me :). Historically, flash-kernel had a baked in assumption that each board in its database had one dtb (and *only* one dtb) associated with it. That dtb was to be baked into the u-boot setup and copied to ... wherever it needed to be copied (typically a boot partition of some kind). However, that doesn't work for the Raspberry Pi where users expected to be able take their existing SD card working on, say, a Pi 3B, "sudo apt update; sudo apt upgrade", move that card to their shiny new Pi 4B, and boot it up (this was an explicitly supported upgrade path on Raspbian (as it then was) that we also wanted to support on Ubuntu). Obviously in this case, it's no good just copying the dtb for the board that flash-kernel finds itself on because tomorrow, it might be expected to boot on an entirely different model. That's why, at some point in 20.10 release (I think?), I introduced the "Method: pi" clause to our flash-kernel entries for the Raspberry Pi. Firstly, this dropped u-boot from the boot chain (the u-boot binaries still get copied, but they're not expected to be used by default -- they're only there for those that still need them for some reason). Secondly, it tells flash-kernel to *ignore* the DTB-Id and just copy *all* the dtbs it finds to the boot partition. Why is the DTB-Id entry still there if it's not used? Unfortunately, flash-kernel still has an assumption in several places that each database entry has to have some DTB-Id specified. Removing that assumption would have enlarged our delta significantly without much purpose. In other words, you are absolutely correct that the entry lists the "wrong" dtb for the CM4, but because "Method: pi" is also in that entry, it doesn't actually matter. All the dtbs (including those for the pi 2, 3, and Zero 2) get copied in this instance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928314 Title: Wrong DTB chosen for Raspberry Pi Compute Module 4 (all.db) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1928314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928314] Re: Wrong DTB chosen for Raspberry Pi Compute Module 4 (all.db)
Come to think of it, I've got some bits I need to do on flash-kernel anyway, and this could do with a comment in the database to prevent this sort of misunderstanding in future (seems it's already come up elsewhere -- LP: #1962309), so I'll try and clean this up at the same time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928314 Title: Wrong DTB chosen for Raspberry Pi Compute Module 4 (all.db) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1928314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928314] Re: Wrong DTB chosen for Raspberry Pi Compute Module 4 (all.db)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: flash-kernel (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928314 Title: Wrong DTB chosen for Raspberry Pi Compute Module 4 (all.db) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1928314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912316] Re: log_check / kernel_tainted test from ubuntu_boot failed on Intel Cloud node grumman (failed with flag 2048)
Found with xenial/fips:4.4.0-1072.78 on node fili. ** Tags added: sru-20220221 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912316 Title: log_check / kernel_tainted test from ubuntu_boot failed on Intel Cloud node grumman (failed with flag 2048) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1912316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899248] Re: mysql server crashes during install/update: Error: Unable to shut down server with process id X
** Merge proposal linked: https://code.launchpad.net/~lvoytek/ubuntu/+source/mysql-8.0/+git/mysql-8.0/+merge/416902 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899248 Title: mysql server crashes during install/update: Error: Unable to shut down server with process id X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1899248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964969] Re: mysql error log always contains errors with mysqlx when installing/upgrading
** Merge proposal linked: https://code.launchpad.net/~lvoytek/ubuntu/+source/mysql-8.0/+git/mysql-8.0/+merge/414368 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964969 Title: mysql error log always contains errors with mysqlx when installing/upgrading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1964969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1957932] Re: [MIR] rustc, cargo
Before even starting to address the various points further, I must ask whether they're showstopper for the *rustc* MIR. I ask because some of the concerns raised here are irrelevant for rustc itself. For instance, the X-Cargo-Built-Using is not only not used by the rustc packaging at all, it would also not be used by Rust packages entering main since, under the proposed amended rules, those packages would first vendor all their dependencies. We intend to implement all tooling changes that are required for a wider Rust ecosystem support in main, but this starts with having the compiler! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957932 Title: [MIR] rustc, cargo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1957932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899248] Re: mysql server crashes during install/update: Error: Unable to shut down server with process id X
** Merge proposal unlinked: https://code.launchpad.net/~lvoytek/ubuntu/+source/mysql-8.0/+git/mysql-8.0/+merge/414368 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899248 Title: mysql server crashes during install/update: Error: Unable to shut down server with process id X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1899248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899248] Re: mysql server crashes during install/update: Error: Unable to shut down server with process id X
** Merge proposal linked: https://code.launchpad.net/~lvoytek/ubuntu/+source/mysql-8.0/+git/mysql-8.0/+merge/416904 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899248 Title: mysql server crashes during install/update: Error: Unable to shut down server with process id X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1899248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964969] Re: mysql error log always contains errors with mysqlx when installing/upgrading
** Merge proposal linked: https://code.launchpad.net/~lvoytek/ubuntu/+source/mysql-8.0/+git/mysql-8.0/+merge/416904 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964969 Title: mysql error log always contains errors with mysqlx when installing/upgrading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1964969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964990] [NEW] Rotate to 2021v1 signing key
Public bug reported: This bug report will be used to track rotating classic kernel signing to 2021v1 signing key. ** Affects: linux (Ubuntu) Importance: Undecided Status: Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964990 Title: Rotate to 2021v1 signing key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964990] 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 1964990 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/1964990 Title: Rotate to 2021v1 signing key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964990] Re: Rotate to 2021v1 signing key
** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964990 Title: Rotate to 2021v1 signing key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904890] Re: [SRU] Please merge flash-kernel 3.103 from Debian unstable
** Changed in: flash-kernel (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904890 Title: [SRU] Please merge flash-kernel 3.103 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1904890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893491] Re: groovy arm64 raspi: Unsupported platform. dpkg: error processing package flash-kernel (--configure):
I suspect this was down to one of the newer revisions of the Pi board (the rev 1.4 4B?) appearing during the cycle. This was fixed at some point during the Groovy release though, firstly by adding the explicit "rev 1.4" entry, and later by adding the "Raspberry Pi *" wildcard entry (in 3.100ubuntu3). I'll set this to "Fix Released" but if you're still having the issue, please do set it back to "New" and I'll dig into it. ** Changed in: flash-kernel (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893491 Title: groovy arm64 raspi: Unsupported platform. dpkg: error processing package flash-kernel (--configure): To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1893491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948507] Re: TypeError when computing QOS feature name
This bug was fixed in the package cinder - 2:19.0.0+git2022030310.b49fb59a6-0ubuntu2~cloud0 --- cinder (2:19.0.0+git2022030310.b49fb59a6-0ubuntu2~cloud0) focal-yoga; urgency=medium . * New update for the Ubuntu Cloud Archive. . cinder (2:19.0.0+git2022030310.b49fb59a6-0ubuntu2) jammy; urgency=medium . * d/p/fix-qos-computation.patch: Cherry-pick from upstream review to fix TypeError exception when generating QOS feature name (LP: #1948507). ** Changed in: cloud-archive Status: Fix Committed => 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/1948507 Title: TypeError when computing QOS feature name To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1948507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948507] Re: TypeError when computing QOS feature name
This bug was fixed in the package cinder - 2:19.0.0+git2022030310.b49fb59a6-0ubuntu2~cloud0 --- cinder (2:19.0.0+git2022030310.b49fb59a6-0ubuntu2~cloud0) focal-yoga; urgency=medium . * New update for the Ubuntu Cloud Archive. . cinder (2:19.0.0+git2022030310.b49fb59a6-0ubuntu2) jammy; urgency=medium . * d/p/fix-qos-computation.patch: Cherry-pick from upstream review to fix TypeError exception when generating QOS feature name (LP: #1948507). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948507 Title: TypeError when computing QOS feature name To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1948507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944508] Re: [FFE] [P10] CAS : last kernel not auto booted
Withdrawing as FFe (and unsubscribing the Ubuntu Release Team), since it will not arrive in time. New plan is to target this for 22.10, with the option to potentially get it in to 22.04.1. ** Tags added: kk-release ** Summary changed: - [FFE] [P10] CAS : last kernel not auto booted + [P10] CAS : last kernel not auto booted -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944508 Title: [P10] CAS : last kernel not auto booted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1944508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904024] Re: package flash-kernel 3.98ubuntu12 failed to install/upgrade: installed flash-kernel package post-installation script subprocess returned error exit status 1 when installing on a Rasp
The SRU of 3.103 to focal (LP: #1904890) on 2021-01-28 (one day after @grudzinski-gmail's comment) should have fixed this. I'll set this to Fix Released for now as I'm *fairly* confident this is indeed fixed, but if you're still having this issue please do set it back to "New" and I'll dig into it. ** Changed in: flash-kernel (Ubuntu) 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/1904024 Title: package flash-kernel 3.98ubuntu12 failed to install/upgrade: installed flash-kernel package post-installation script subprocess returned error exit status 1 when installing on a Raspberry Pi 400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1904024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903288] Re: Power guest secure boot with static keys: kernel portion
** Tags added: kk-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903288 Title: Power guest secure boot with static keys: kernel portion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382034] Re: FFe: Sync modem-manager-gui 0.0.17.1-1 (universe) from Debian unstable (main)
** Changed in: modem-manager-gui (Baltix) Status: Triaged => Fix Released ** Changed in: baltix-default-settings Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382034 Title: FFe: Sync modem-manager-gui 0.0.17.1-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1382034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903289] Re: [FFE] Power guest secure boot with static keys: GRUB2 portion
Withdrawing as FFe (and unsubscribing the Ubuntu Release Team), since it will not arrive in time. New plan is to target this for 22.10, with the option to potentially get it in to 22.04.1. ** Tags added: kk-release ** Summary changed: - [FFE] Power guest secure boot with static keys: GRUB2 portion + Power guest secure boot with static keys: GRUB2 portion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903289 Title: Power guest secure boot with static keys: GRUB2 portion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964132] Re: [FFe] webkit2gtk additionally built with libsoup3 support
** Description changed: Request --- - Add the new libsoup3-using packages in webkit2gtk + 1. Add the new libsoup3-using packages in webkit2gtk + + 2. Build Epiphany with the new webkit2gtk 4.1 API built with libsoup3 Why Needed -- Our webkit2gtk packaging is built with libsoup2 (webkitgtk's 4.0 API). Debian's packaging recently added additional packages built with libsoup3 (webkitgtk's 4.1 API); these should not affect the existing libsoup2 packages. The libsoup2 > libsoup3 transition is a big one and will not happen for 22.04 LTS; I am hoping we can finish it for main by 23.04 but I haven't looked into it yet. It's expected that GNOME 43 will try to switch to libsoup3. Having webkit2gtk with libsoup3 support in 22.04 LTS will make it easier for newer versions of the GNOME Web Browser (epiphany) to run on this release. It also will make it easier to create snaps of GNOME 43 apps using a core22 base. My instinct is that we want libsoup3 and the new webkit+libsoup3 packages to stay in universe for 22.04 LTS and then Main Inclusion can be recommended for 22.10. It is not intended for any traditional (.deb) packages in 22.04 LTS itself to use these new packages except epiphany. I already uploaded the webkit2gtk merge/sync with this change. If this FFe is rejected, I can undo the addition. What Changed See above Build Test -- https://launchpad.net/ubuntu/+source/webkit2gtk/2.35.90-1ubuntu1 Install Test Not done yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964132 Title: [FFe] webkit2gtk additionally built with libsoup3 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1964132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921398] Re: No dns resolution after closing a vpn/sstp connection
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ppp (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921398 Title: No dns resolution after closing a vpn/sstp connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1921398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964992] [NEW] ZFS ignores ARC sizes below allmem/32
Public bug reported: [Impact] ZFS ignores tunable "zfs_arc_max" due to it being below allmem/32 threshold. This prevents users from properly restraining ARC sizes, and can cause increased memory contention in some systems. [Test Plan] 1. Deploy test system with ZFS storage and 32GB RAM 2. Add ARC tunables to /etc/modprobe.d/99-zfs-arc.conf # cat /etc/modprobe.d/99-zfs-arc.conf options zfs zfs_arc_min=536870912 options zfs zfs_arc_max=966367641 3. Reboot system 4. Verify ARC sizes through "arc_summary" # arc_summary | grep -A3 "ARC size" ARC size (current): < 0.1 %1.3 MiB Target size (adaptive): 100.0 % 15.7 GiB Min size (hard limit): 3.2 % 512.0 MiB Max size (high water): 31:1 15.7 GiB For a 32GB test system, we should be able to set max ARC sizes below 1GB. [Fix] This has been fixed by upstream commit: - 36a6e2335c45 "Don't ignore zfs_arc_max below allmem/32" The commit has been introduced in upstream zfs-2.0.0, so it's needed for Bionic and Focal. Releases starting with Impish already have this commit by default: $ git describe --contains 36a6e2335c45 zfs-2.0.0-rc1~332 $ rmadison zfs-linux zfs-linux | 0.7.5-1ubuntu15| bionic | source zfs-linux | 0.7.5-1ubuntu16.12 | bionic-updates | source zfs-linux | 0.8.3-1ubuntu12| focal | source zfs-linux | 0.8.3-1ubuntu12.9 | focal-security | source zfs-linux | 0.8.3-1ubuntu12.13 | focal-updates | source zfs-linux | 0.8.3-1ubuntu12.14 | focal-proposed | source zfs-linux | 2.0.6-1ubuntu2 | impish | source zfs-linux | 2.0.6-1ubuntu2.1 | impish-updates | source zfs-linux | 2.1.2-1ubuntu3 | jammy | source [Regression Potential] The introduced commit essentially removes the limitation of setting ARC tunables below allmem/32, and re-arranges the order of how some of the tunables are parsed. Regressions would possibly show up as other tunables being ignored or not being set correctly due to parsing errors. We should validate whether other ARC related tunables are still being set correctly, and whether ZFS is using the set values for the ARC memory thresholds. ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: zfs-linux (Ubuntu Bionic) Importance: Medium Assignee: Heitor Alves de Siqueira (halves) Status: Confirmed ** Affects: zfs-linux (Ubuntu Focal) Importance: Medium Assignee: Heitor Alves de Siqueira (halves) Status: Confirmed ** Tags: sts ** Changed in: zfs-linux (Ubuntu) Status: New => Fix Released ** Also affects: zfs-linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: zfs-linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: zfs-linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: zfs-linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: zfs-linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: zfs-linux (Ubuntu Bionic) Assignee: (unassigned) => Heitor Alves de Siqueira (halves) ** Changed in: zfs-linux (Ubuntu Focal) Assignee: (unassigned) => Heitor Alves de Siqueira (halves) ** Description changed: [Impact] - ZFS ignores tunable "zfs_arc_max" due to it being below allmem/32 - threshold. This prevents users from properly restraining ARC sizes, and can - cause increased memory contention in some systems. + ZFS ignores tunable "zfs_arc_max" due to it being below allmem/32 threshold. This prevents users from properly restraining ARC sizes, and can cause increased memory contention in some systems. [Test Plan] 1. Deploy test system with ZFS storage and 32GB RAM 2. Add ARC tunables to /etc/modprobe.d/99-zfs-arc.conf -# cat /etc/modprobe.d/99-zfs-arc.conf -options zfs zfs_arc_min=536870912 -options zfs zfs_arc_max=966367641 + # cat /etc/modprobe.d/99-zfs-arc.conf + options zfs zfs_arc_min=536870912 + options zfs zfs_arc_max=966367641 3. Reboot system 4. Verify ARC sizes through "arc_summary" -# arc_summary | grep -A3 "ARC size" -ARC size (current): < 0.1 %1.3 MiB -Target size (adaptive): 100.0 % 15.7 GiB -Min size (hard limit): 3.2 % 512.0 MiB -Max size (high water): 31:1 15.7 GiB + # arc_summary | grep -A3 "ARC size" + ARC size (current): < 0.1 %1.3 MiB + Target size (adaptive): 100.0 % 15.7 GiB + Min size (hard limit): 3.2 % 512.0 MiB + Max size (high water): 31:1 15.7 GiB For
[Bug 1964993] [NEW] package linux-firmware 20220302.gitee0667aa-0ubuntu1 failed to install/upgrade: »/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new« kann nicht geöffnet werden: Datei oder Verze
*** This bug is a duplicate of bug 1964814 *** https://bugs.launchpad.net/bugs/1964814 Public bug reported: The package "linux-firmware" couldn't be upgraded to the latest version due to a missing file. The missing file is "/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new", and it is unknown to me, how that file can be added back. I wasn't aware of its existence until now either. I'm afraid I can't give any further details as a result. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220302.gitee0667aa-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: goji 1721 F pulseaudio /dev/snd/controlC2: goji 1721 F pulseaudio /dev/snd/controlC1: goji 1721 F pulseaudio CasperMD5CheckResult: pass Date: Tue Mar 15 18:48:33 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 ErrorMessage: »/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new« kann nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden InstallationDate: Installed on 2022-03-14 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: ASUS System Product Name PackageArchitecture: all ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=2469e4aa-8428-4ea5-be72-a1cd737d0033 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.2, python3-minimal, 3.10.1-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu5 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 20220302.gitee0667aa-0ubuntu1 failed to install/upgrade: »/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new« kann nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2021 dmi.bios.release: 4.7 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0407 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z690M-PLUS D4 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0407:bd09/11/2021:br4.7:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ690M-PLUSD4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package dpkg jammy linux-firmware -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964993 Title: package linux-firmware 20220302.gitee0667aa-0ubuntu1 failed to install/upgrade: »/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg- new« kann nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1964974] [NEW] gufw doesn't start (ValueError: invalid literal for int() with base 10: 'WARN:)
Hi, Please, try updating your Ubuntu :) Best regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964974 Title: gufw doesn't start (ValueError: invalid literal for int() with base 10: 'WARN:) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gui-ufw/+bug/1964974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756752] Re: flash-kernel fails with Unsupported platform on Cubieboard
If this is still an issue, can you provide the output of "cat /proc/device-tree/model" ? ** Changed in: flash-kernel (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/1756752 Title: flash-kernel fails with Unsupported platform on Cubieboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1756752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1090594] Re: kernel install: flash-kernel is sometimes never executed
I believe the analysis that this was caused by both kernel *and* f-k being updated in the same apt run was spot on. Furthermore, I *think* this was fixed in 3.98ubuntu10 which caused flash-kernel to (attempt to) run on every call to postinst maintscript, not just those involving a trigger (because pending triggers can be dropped on package upgrades. I'll set this to "Fix Released" as I'm fairly confident this is already fixed, but do feel free to set this back to "New" if it's still a issue. ** Changed in: flash-kernel (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1090594 Title: kernel install: flash-kernel is sometimes never executed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1090594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964993] Re: package linux-firmware 20220302.gitee0667aa-0ubuntu1 failed to install/upgrade: »/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new« kann nicht geöffnet werden: Datei oder Verzeic
*** This bug is a duplicate of bug 1964814 *** https://bugs.launchpad.net/bugs/1964814 ** This bug has been marked a duplicate of bug 1964814 linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964993 Title: package linux-firmware 20220302.gitee0667aa-0ubuntu1 failed to install/upgrade: »/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg- new« kann nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
