[Bug 1909734] Re: TPM PCR checking will fail if the all characters are 0
** Description changed: [Impact] * TPM PCR0 differs from reconstruction, if your PCR0 contains one (or more) zero byte(s) then the PCR0 will mismatch. (zero byte(s) be ignored) [Test Plan] * run $ fwupdmgr get-devices ... └─System Firmware: Device ID: c8489035f8df6f87a1a3cd1baff36129262a5ac1 Current version: 92.1.0 Minimum Version: 0.0.1 Vendor: HP (DMI:HP) Update Error: TPM PCR0 differs from reconstruction, please see https://github.com/fwupd/fwupd/wiki/TPM-PCR0-differs-from-reconstruction GUID: 116180f2-105d-4ab2-809e-7fabed71217b will get the failed. * already tried on bug1891966 bug1893018 bug1896855 bug1897674 bug1899914 bug1902835 bug1903660 bug1909539 bug1910197 bug1914335 bug1918600 bug1918866 bug1919270 bug1919424 bug1920714 and this patch could solve the error. [Where problems could occur] * the all zero PCR0 is invalid, the original logic is to check whether a byte is zero. If zero then skip. It cause the PCR0 will potentially miss some valid zero byte. (e.g. 0x0C>>00<<62898247F8FE3085960E5B0270E7667B6F7D4CAE17A503950499D45B4116) * this patch will not skip zero byte. Instead, add a flag to check whether all bytes are zero. * for this change, it makes sense and didn't see any potential regression. --- In some of HP platforms, the TPM PCR checking will fail on focal ubuntu $ fwupdmgr get-devices ... └─System Firmware: Device ID: c8489035f8df6f87a1a3cd1baff36129262a5ac1 Current version: 92.1.0 Minimum Version: 0.0.1 Vendor: HP (DMI:HP) Update Error: TPM PCR0 differs from reconstruction, please see https://github.com/fwupd/fwupd/wiki/TPM-PCR0-differs-from-reconstruction GUID: 116180f2-105d-4ab2-809e-7fabed71217b Device Flags: • Internal device • Updatable • Requires AC power • Needs a reboot after installation • Cryptographic hash verification is available • Device is usable for the duration of the update Update Error: TPM PCR0 differs from reconstruction, please see https://github.com/fwupd/fwupd/wiki/TPM-PCR0-differs-from-reconstruction --- This issue is fixed by upstream commit https://github.com/fwupd/fwupd/pull/2394/commits/e265dd1d8687965bee77259ef3482b09b92033c1 + + X-HWE-Bug: Bug #1931189 ** Tags added: originate-from-1931189 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909734 Title: TPM PCR checking will fail if the all characters are 0 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1909734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929449] Re: do not allow upgrades to hirsute for Apple hardware
> This is now being addressed via bug 1931112. Thanks for letting us know about the issues with this quirk! 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/1929449 Title: do not allow upgrades to hirsute for Apple hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1929449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930188] Re: Acer Aspire 5 sound driver issues
Glad to know it won't take too long to be available in ubuntu. This is a very popular budget laptop so many ubuntu users will be happy when the sound driver issues are fixed and everything works smoothly. Will wait patiently for a notification from this thread that the fixes are now available officially in ubuntu also really appreciate this being fixed so quickly that I expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)
Oh, I simply meant using the 'ip' command, like (in my example): $ ip a | grep enP1 6: enP1p0s0: mtu 1500 qdisc mq state UP group default qlen 1000 $ sudo ip link add link enP1p0s0 name enP1p0s0.1234 type vlan id 1234 $ sudo ip addr add 192.168.1.201/24 dev enP1p0s0 $ sudo ip addr add 192.168.1.202/24 dev enP1p0s0.1234 $ sudo ip link set dev enP1p0s0 up $ sudo ip link set dev enP1p0s0.1234 up $ ip a -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930641] Re: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2
LibreOffice looks like the main offender. ** Also affects: libreoffice (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/1930641 Title: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1930641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931104] Re: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-proposed
There is another fix in master that belongs to https://bugzilla.mozilla.org/show_bug.cgi?id=1566124 - I've bumped my PPA build to include both as it is worth a try if this fixes the current ppc64 issues in v3.66. Build of 3.66-1ubuntu1~impishppa2 started, later on I'll let the autopkgtests run. ** Bug watch added: Mozilla Bugzilla #1566124 https://bugzilla.mozilla.org/show_bug.cgi?id=1566124 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931104 Title: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish- proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1931104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777708] Re: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time in Xorg sessions
** Summary changed: - Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time + Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time in Xorg sessions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/108 Title: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931018] Re: Keyboard layout switch freezes
I'm guessing this is related to bug 108, even if you only have one keyboard. It sounds related. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Tags added: i18n -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931018 Title: Keyboard layout switch freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1931018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930976] Re: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers
** Tags added: nvidia ** Package changed: xorg (Ubuntu) => linux-hwe-5.8 (Ubuntu) ** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930976 Title: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1930976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926236] Re: Fix The sound has noise while audio volume is maximum
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926236 Title: Fix The sound has noise while audio volume is maximum To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930903] Re: Frequent kernel oops related to nvidia / nv_drm_master_set
** Tags added: nvidia ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-460 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930903 Title: Frequent kernel oops related to nvidia / nv_drm_master_set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1930903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930925] Re: Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM
** Summary changed: - Ubuntu 20.04 doesn't work with moidern KVMs + Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Tags added: kvm ** Summary changed: - Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM + Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM switch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930925 Title: Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM switch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931104] Re: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-proposed
I was able to verify that a merge of 3.66 would on Ubuntu trigger the very same bug that Debian has blocking the dogtag-pki test on powerpc64. => https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train- ppa-service-4577/impish/ppc64el/d/dogtag- pki/20210608_031158_a9d4a@/log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931104 Title: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish- proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1931104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)
Just booted the kernel from #64 without the parameter - downloads suffer from slow speeds, ethtool reports rx_errors and rx_crc_errors again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927925 Title: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1927925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931196] Re: no
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: 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/1931196 Title: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1931196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931196] [NEW] no
Public bug reported: no ** Affects: ubuntu Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931196 Title: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1931196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
Hi Evan, The kernel team have built all of the kernels for this SRU cycle, and have placed them into -proposed for verification. We now need to do some thorough testing and make sure that Raid10 arrays function with good performance, ensure data integrity and make sure we won't be introducing any regressions when these kernels are released in two weeks time. I would really appreciate it if you could help test and verify these kernels function as intended. Instructions to Install: 1) cat << EOF | sudo tee /etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list # Enable Ubuntu proposed archive deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed main universe EOF 2) sudo apt update For 21.04 / Hirsute: 3) sudo apt install linux-image-5.11.0-20-generic linux-modules-5.11.0-20-generic \ linux-modules-extra-5.11.0-20-generic linux-headers-5.11.0-20-generic For 20.10 / Groovy: 3) sudo apt install linux-image-5.8.0-56-generic linux-modules-5.8.0-56-generic \ linux-modules-extra-5.8.0-56-generic linux-headers-5.8.0-56-generic For 20.04 / Focal: 3) sudo apt install linux-image-5.4.0-75-generic linux-modules-5.4.0-75-generic \ linux-modules-extra-5.4.0-75-generic linux-headers-5.4.0-75-generic For 18.04 / Bionic: For the 5.4 Bionic HWE Kernel: 3) sudo apt install linux-image-5.4.0-75-generic linux-modules-5.4.0-75-generic \ linux-modules-extra-5.4.0-75-generic linux-headers-5.4.0-75-generic For the 4.15 Bionic GA Kernel: 3) sudo apt install linux-image-4.15.0-145-generic linux-modules-4.15.0-145-generic \ linux-modules-extra-4.15.0-145-generic linux-headers-4.15.0-145-generic 4) sudo reboot 5) uname -rv You may need to modify your grub configuration to boot the correct kernel. If you need help, read these instructions: https://paste.ubuntu.com/p/XrTzWPPnWJ/ I am running the -proposed kernel on my cloud instance with my /home directory on a Raid10 array made up of 4x NVMe devices, and things are looking okay. I will be performing my detailed regression testing against these kernels tomorrow, and I will write back with the results then. Please help test these kernels in -proposed, and let me know how they go. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896578 Title: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930868] Re: Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197
The current firmware-sof version 1.6.1-2 can't replace the sof-firmware in our linux-firmware package. At least an important firmware file is missing in the firmware-sof. I have wrote an email to debian maintainer, he told me he is planning a higher version (1.7), once the 1.7 is ready, we could remove the sof- firmware in the linux-firmware and use the firmware-sof package. Below is the reply from the maintainer: Hi Hui, I hadn't realised that's how it worked So I had prepared a 1.7 version a month ago: https://salsa.debian.org/mpearson/firmware-sof/-/commit/fdce28e87c495ab69c1cdfaaff19bc7aff70af5f But I wasn't able to get this uploaded as there was a freeze on so the debian maintainer who has been helping me wouldn't take it. I'll see if that's possible now (and likely have to update to the latest...) Mark -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930868 Title: Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1930868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907262] Re: raid10: discard leads to corrupted file system
Hi Thimo, The kernel team have built all of the kernels for this SRU cycle, and have placed them into -proposed for verification. We now need to do some thorough testing and make sure that Raid10 arrays function with good performance, ensure data integrity and make sure we won't be introducing any regressions when these kernels are released in two weeks time. I would really appreciate it if you could help test and verify these kernels function as intended. Instructions to Install: 1) cat << EOF | sudo tee /etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list # Enable Ubuntu proposed archive deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed main universe EOF 2) sudo apt update For 21.04 / Hirsute: 3) sudo apt install linux-image-5.11.0-20-generic linux-modules-5.11.0-20-generic \ linux-modules-extra-5.11.0-20-generic linux-headers-5.11.0-20-generic For 20.10 / Groovy: 3) sudo apt install linux-image-5.8.0-56-generic linux-modules-5.8.0-56-generic \ linux-modules-extra-5.8.0-56-generic linux-headers-5.8.0-56-generic For 20.04 / Focal: 3) sudo apt install linux-image-5.4.0-75-generic linux-modules-5.4.0-75-generic \ linux-modules-extra-5.4.0-75-generic linux-headers-5.4.0-75-generic For 18.04 / Bionic: For the 5.4 Bionic HWE Kernel: 3) sudo apt install linux-image-5.4.0-75-generic linux-modules-5.4.0-75-generic \ linux-modules-extra-5.4.0-75-generic linux-headers-5.4.0-75-generic For the 4.15 Bionic GA Kernel: 3) sudo apt install linux-image-4.15.0-145-generic linux-modules-4.15.0-145-generic \ linux-modules-extra-4.15.0-145-generic linux-headers-4.15.0-145-generic 4) sudo reboot 5) uname -rv You may need to modify your grub configuration to boot the correct kernel. If you need help, read these instructions: https://paste.ubuntu.com/p/XrTzWPPnWJ/ I am running the -proposed kernel on my cloud instance with my /home directory on a Raid10 array made up of 4x NVMe devices, and things are looking okay. I will be performing my detailed regression testing against these kernels tomorrow, and I will write back with the results then. Please help test these kernels in -proposed, and let me know how they go. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907262 Title: raid10: discard leads to corrupted file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930188] Re: Acer Aspire 5 sound driver issues
The kernel patch: https://mailman.alsa-project.org/pipermail/alsa-devel/2021-June/185823.html The PA MR: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/577 Once they are accepted by upstream, will backport them to ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930640] Re: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object
Confirmed everything appears to be working. We can consider this closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930640 Title: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1930640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1928787] Re: package libreoffice-common 1:6.4.6-0ubuntu0.20.04.1 failed to install/upgrade: unable to open '/usr/lib/libreoffice/share/template/common/presnt/Progress.otp.dpkg-new': Operation
Yes, it appears so. Thank you. On 6/7/21 1:53 PM, Heather Ellsworth wrote: > Looks successful to me! Please let us know if you hit any other issues. > > ** Changed in: libreoffice (Ubuntu) > Status: New => Invalid > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928787 Title: package libreoffice-common 1:6.4.6-0ubuntu0.20.04.1 failed to install/upgrade: unable to open '/usr/lib/libreoffice/share/template/common/presnt/Progress.otp.dpkg- new': Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1928787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905157] Re: package zfsutils-linux 0.8.3-1ubuntu12.4 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1
[Expired for zfs-linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: zfs-linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905157 Title: package zfsutils-linux 0.8.3-1ubuntu12.4 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1905157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909025] Re: Distribution upgrader crashes with note: an unresolved problem occured while calculating the upgrade
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909025 Title: Distribution upgrader crashes with note: an unresolved problem occured while calculating the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1909025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909360] Re: Unable to upgrade from Ubuntu 18.04 to 20.04
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909360 Title: Unable to upgrade from Ubuntu 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1909360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909401] Re: Impossible to upgrade from 18.04 to 20.04.1
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909401 Title: Impossible to upgrade from 18.04 to 20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1909401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909391] Re: don't updated to Ubuntu 20.04
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909391 Title: don't updated to Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1909391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922980] Re: It's incompatible with my router.
[Expired for rtl8821ce (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rtl8821ce (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922980 Title: It's incompatible with my router. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1922980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923109] Re: Power daemon does not sense when AC adapter is plugged and shuts the machine down
[Expired for Ubuntu because there has been no activity for 60 days.] ** Changed in: ubuntu Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923109 Title: Power daemon does not sense when AC adapter is plugged and shuts the machine down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1923109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930304] Re: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze
Thanks. I can't yet see a crash, and I don't have the hardware to reproduce the issue, but I can see that you have a number of unsupported extensions. So first please try disabling (in the Extensions app) or uninstalling all but the three default Ubuntu extensions. Then log in again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930304 Title: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930655] Re: Qualcomm Device [17cb:1101] subsystem [1a56:a501]: ath11k: Failed to bring up Bluetooth: hci0: command 0xfc00 tx timeout
** Tags added: hwe-bluetooth ihv-qualcomm-atheros -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930655 Title: Qualcomm Device [17cb:1101] subsystem [1a56:a501]: ath11k: Failed to bring up Bluetooth: hci0: command 0xfc00 tx timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1930655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931193] [NEW] typecatcher crashes on launch
Public bug reported:
I recently upgraded to hirsute 21.04 and just discovered typecatcher
doesn't launch. A couple of web searches implies some deprecated python
issues; I don't know what version python I was running in Ubuntu 20.10.
This is what I see when trying to launch it from a terminal:
~$ typecatcher
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/typecatcher_lib/Application.py", line
30, in on_activate
self.window = TypeCatcherWindow.TypeCatcherWindow()
File "/usr/lib/python3/dist-packages/typecatcher_lib/Window.py", line 47, in
__new__
builder = get_builder('TypeCatcherWindow')
File "/usr/lib/python3/dist-packages/typecatcher_lib/helpers.py", line 44, in
get_builder
builder.add_from_file(ui_filename)
File "/usr/lib/python3/dist-packages/typecatcher_lib/Builder.py", line 86, in
add_from_file
ele_widgets = tree.getiterator("object")
AttributeError: 'ElementTree' object has no attribute 'getiterator'
~$
~$ python --version
Python 2.7.18
~$
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: typecatcher 0.3-1.2
ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
Uname: Linux 5.11.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 7 22:40:36 2021
InstallationDate: Installed on 2018-10-20 (961 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: typecatcher
UpgradeStatus: Upgraded to hirsute on 2021-05-12 (26 days ago)
** Affects: typecatcher (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931193
Title:
typecatcher crashes on launch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/typecatcher/+bug/1931193/+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.4/5.4.0.1037.39)
All autopkgtests for the newly accepted linux-meta-raspi-5.4 (5.4.0.1037.39) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fwts/unknown (arm64) systemd/237-3ubuntu10.47 (arm64) lxc/3.0.3-0ubuntu1~18.04.1 (arm64) dpdk/unknown (arm64) zfs-linux/0.7.5-1ubuntu16.11 (arm64) adv-17v35x/unknown (arm64) bbswitch/0.8-4ubuntu1 (arm64) glibc/unknown (arm64) xtables-addons/unknown (arm64) linux-raspi-5.4/unknown (arm64) acpi-call/1.1.0-4 (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/bionic/update_excuses.html#linux-meta-raspi-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901582]
@Nate : is there a new issue for Wayland switch user functionality as this one is resolved? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901582 Title: 'Switch user' not available in application launcher after upgrade to 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/plasma-desktop/+bug/1901582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901582]
I don't know, sorry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901582 Title: 'Switch user' not available in application launcher after upgrade to 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/plasma-desktop/+bug/1901582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
This should also fix the problem for some people in Wayland sessions: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1834 It is in mutter release 40.1 and future release 3.38.5. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1890772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851992] Re: Lock screen not locking upon resume (org.gnome.desktop.lockdown disable-lock-screen set to true for some reason)
Jose, that looks like a different problem. Please open a new bug by running: ubuntu-bug gnome-shell -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851992 Title: Lock screen not locking upon resume (org.gnome.desktop.lockdown disable-lock-screen set to true for some reason) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883174] Re: Some (or all) desktop icons are missing
Ubuntu 21.04 does not use the package this bug is about, it uses a different extension for desktop icons. So that's why the behaviour in 21.04 is different to previous releases. Unfortunately for API reasons we are unable to backport the same extension from 21.04 to 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: Some (or all) desktop icons are missing To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834967] Re: Windows in Activities might be partially off screen
A similar problem can be seen in 21.04 as a result of bug 1922353. To make sure you're not just seeing bug 1922353 check that you can still interact with the windows. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834967 Title: Windows in Activities might be partially off screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-dock/+bug/1834967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836858] Re: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background
Yeah the problem seems to be getting worse in recent Ubuntu releases and is more obvious on more laptops. That's good for testing at least. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836858 Title: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/1836858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905322] Re: LibreOffice crashes under load.
NO it's NOT cluttering up the system, and it has benefit (far more benefit than my suggestion of occasional testing.. then forgetting to test for it every again which is a risk with occasional testing, esp. for me anyway). My concern was to avoid you becoming burnt out... > It breaks every time, so you may have not triggered it properly. Yes I do believe I didn't trigger it 'correctly'.. and have no doubt the issue is real, my comment was more my belief that it was as Heather (@hellsworth) had said in describing it as a "super corner case" (won't impact many end-users; ie. low priority). (I'll test for it again with Lubuntu... then once I've triggered it can re-try the same steps with Ubuntu... Taking it upstream would be what I'd see as greatest chance for fix (fastest way anyway); my issue with LMDE is I believe it's based on debian stable; ie. older software; I use debian testing frequently in testing issues found in lubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905322 Title: LibreOffice crashes under load. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1905322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931112] Autopkgtest regression report (ubuntu-release-upgrader/1:21.04.13)
All autopkgtests for the newly accepted ubuntu-release-upgrader (1:21.04.13) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: ubuntu-release-upgrader/1:21.04.13 (arm64, s390x, ppc64el, armhf) 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/hirsute/update_excuses.html#ubuntu-release-upgrader [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/1931112 Title: Apple vendor quirk check for LP#1928434 incorrectly fails on all non- DMI hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1931112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780341] Re: squid should default to more human friendly timestamps
** Branch linked: lp:~hloeung/ubuntu-repository-cache/squid-logging- human-sensible-timestamps -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780341 Title: squid should default to more human friendly timestamps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1780341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883840] Re: Double free in DCCP module causing kernel panic
Hello Hadar, I'm sorry for the trouble. These have been fixed: https://ubuntu.com/security/notices/USN-4577-1 https://ubuntu.com/security/notices/USN-4576-1 https://ubuntu.com/security/notices/USN-4578-1 https://ubuntu.com/security/notices/USN-4579-1 https://ubuntu.com/security/notices/USN-4580-1 This page is regenerated by a cronjob, it should be fixed eventually: https://ubuntu.com/security/CVE-2020-16119 Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883840 Title: Double free in DCCP module causing kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931180] Re: package openvswitch-testcontroller 2.13.3-0ubuntu0.20.04.1 failed to install/upgrade: installed openvswitch-testcontroller package post-installation script subprocess returned error
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931180 Title: package openvswitch-testcontroller 2.13.3-0ubuntu0.20.04.1 failed to install/upgrade: installed openvswitch-testcontroller package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1931180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931180] [NEW] package openvswitch-testcontroller 2.13.3-0ubuntu0.20.04.1 failed to install/upgrade: installed openvswitch-testcontroller package post-installation script subprocess returned erro
Public bug reported: don't know ProblemType: Package DistroRelease: Ubuntu 20.04 Package: openvswitch-testcontroller 2.13.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 27 11:29:07 2021 ErrorMessage: installed openvswitch-testcontroller package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-04-21 (47 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: openvswitch Title: package openvswitch-testcontroller 2.13.3-0ubuntu0.20.04.1 failed to install/upgrade: installed openvswitch-testcontroller package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931180 Title: package openvswitch-testcontroller 2.13.3-0ubuntu0.20.04.1 failed to install/upgrade: installed openvswitch-testcontroller package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1931180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1388491]
Great! You solved it! I tested again and it is ok in Version: 7.2.0.0.alpha1+ / LibreOffice Community Build ID: ec629c5ee22d02f99d66a5cf975ce239876b7f4d CPU threads: 4; OS: Linux 5.8; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1388491 Title: [upstream] calc: "Cut" and "Paste special" -> "Transpose" affects other cells To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1388491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931179] [NEW] /usr/lib/python3/dist-packages/genshi/filters/i18n.py:352: SyntaxWarning: "is not" with a literal. Did you mean "!="?
Public bug reported: $ sudo apt install python3-genshi Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: doc-base python-genshi-doc The following NEW packages will be installed: python3-genshi 0 upgraded, 1 newly installed, 0 to remove and 44 not upgraded. Need to get 121 kB of archives. After this operation, 914 kB of additional disk space will be used. Get:1 http://192.168.0.27/ubuntu focal/main amd64 python3-genshi all 0.7.3-0ubuntu3 [121 kB] Fetched 121 kB in 0s (3,179 kB/s) Selecting previously unselected package python3-genshi. (Reading database ... 229776 files and directories currently installed.) Preparing to unpack .../python3-genshi_0.7.3-0ubuntu3_all.deb ... Unpacking python3-genshi (0.7.3-0ubuntu3) ... Setting up python3-genshi (0.7.3-0ubuntu3) ... /usr/lib/python3/dist-packages/genshi/filters/i18n.py:352: SyntaxWarning: "is not" with a literal. Did you mean "!="? assert numeral is not '', "at least pass the numeral param" Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python3-genshi 0.7.3-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101 Uname: Linux 5.4.0-71-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_71_79_generic_77 lkp_Ubuntu_5_4_0_71_79_generic_76 zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 8 01:16:44 2021 Dependencies: PackageArchitecture: all ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: genshi UpgradeStatus: Upgraded to focal on 2020-01-24 (500 days ago) ** Affects: genshi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931179 Title: /usr/lib/python3/dist-packages/genshi/filters/i18n.py:352: SyntaxWarning: "is not" with a literal. Did you mean "!="? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/genshi/+bug/1931179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892484] Re: Screen Sharing option is missing in 20.10, but exists in 20.04.
This is happening again with ubuntu 21.04. I have vino installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892484 Title: Screen Sharing option is missing in 20.10, but exists in 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930422] Re: thermald_1.9.1-1ubuntu0.4_amd64 breaks system
I wish fan control worked. I release v2.4.6 with the changes. This is in master branch with tag v2.4.6. There are three commits on top of v2.4.5 to address this issue. Please try. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930422 Title: thermald_1.9.1-1ubuntu0.4_amd64 breaks system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1930422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931178] [NEW] apt-key fails when POSIXLY_CORRECT environmental variable is set
Public bug reported: apt-key fails when the POSIXLY_CORRECT environmental variable is set. This is due to chmod acting differently with POSIXLY_CORRECT set: chmod tries to use `--` as a parameter with this variable. This prevents some third-party utilities, like pmrun, from using apt- key. --- chmod with POSIXLY_CORRECT unset succeeds with the following commands: ``` touch testfile chmod 0644 -- testfile echo $? ``` The final command prints "0". (This is what the apt-key script expects to happen.) --- chmod with POSIXLY_CORRECT set fails with the following commands: ``` export POSIXLY_CORRECT= touch testfile chmod 0644 -- testfile echo $? ``` The final two commands print these two lines, respectively: """ chmod: cannot access '--': No such file or directory 1 """ (This is unexpected for the apt-key script.) --- As such, when a third party utility that sets the POSIXLY_CORRECT environmental variable, like pmrun, tries to run apt-key, it will fail. Example use similar to what the reporting customer tried: `cat some-repo-key.gpg | pmrun apt-key add -` The chmod examples are run on an up-to-date Bionic container, /usr/bin/apt-key has `chmod -- path` commands at line 338 and line 499: GNU coreutils package version 8.28-1ubuntu1 apt package version 1.6.13 ** Affects: apt (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/1931178 Title: apt-key fails when POSIXLY_CORRECT environmental variable is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1931178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931101] Re: Installation error: mobiml2xhtml.py hasn´t been converted from python v2 to v3
** Changed in: bookworm (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931101 Title: Installation error: mobiml2xhtml.py hasn´t been converted from python v2 to v3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bookworm/+bug/1931101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931171] Re: kernel_lockdown(7) describes removed SysRq for lifting lockdown
** Changed in: manpages (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931171 Title: kernel_lockdown(7) describes removed SysRq for lifting lockdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/1931171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818593] Re: PS data generated on Ubuntu 16.04 is larger than on Ubuntu 14.04
This is not a bug. The variation in the output size depends on the -dCompressPages flag. Versions 9.01 .. 9.14 have it on by default for smaller output files. Versions 9.15 .. 9.54.0 have it off by default for higher compatibility with buggy PS interpreters. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818593 Title: PS data generated on Ubuntu 16.04 is larger than on Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1818593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930640] Re: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object
After a little more digging, I believe part of my issue with the boto3+s3 option was that I was still using the full URL rather than just the bucket name, so rather than: boto3+s3://BUCKET_NAME/folder I was still using: boto3+s3://s3-us-west-2.amazonaws.com/BUCKET_NAME/folder So this appears to be working and I'm seeing files show up in S3 and nothing has produced an error so far after six hours (and counting) of backing up. Although it's still weird that the old S3 URL of s3://s3-us- west-2.amazonaws.com/BUCKET_NAME/folder that works in the 0.7.19 version of Duplicity with Python 2.7 was able to use the old S3 URL, but the new one on 0.8.19 (and 0.8.11) didn't seem to jive with it. But since the boto3+s3://bucket_name works with the multipart chunking, I'll just stick with this instead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930640 Title: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1930640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928360] Re: Switch to Fcitx 5 for Chinese
This bug was fixed in the package im-config - 0.47-1 --- im-config (0.47-1) experimental; urgency=medium * Team upload * Bug script tweaks [ Shengjing Zhu ] * Change IM_MODULE env for fcitx5 to "fcitx" (closes: #977203, LP: #1928360) -- Gunnar Hjalmarsson Mon, 07 Jun 2021 09:38:38 +0200 ** Changed in: im-config (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/1928360 Title: Switch to Fcitx 5 for Chinese To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931176] [NEW] Crashed while installing with ZFS on 6TB disk
Public bug reported: Very early in the installation process. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.10 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckMismatches: ./casper/initrd CasperMD5CheckResult: skip CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 7 16:52:13 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.10 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931176 Title: Crashed while installing with ZFS on 6TB disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1931176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926748] Re: regression in xenial updates - grub2 cannot handle new arm64 relocations
Hello Dimitri, or anyone else affected, Accepted grub2-unsigned into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/grub2-unsigned/2.04-1ubuntu44.1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: grub2-unsigned (Ubuntu Xenial) Status: New => 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/1926748 Title: regression in xenial updates - grub2 cannot handle new arm64 relocations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1926748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930742] Please test proposed package
Hello Steve, or anyone else affected, Accepted grub2-unsigned into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/grub2-unsigned/2.04-1ubuntu44.1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930742 Title: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1930742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931112] Re: Apple vendor quirk check for LP#1928434 incorrectly fails on all non-DMI hardware
I tested the upgrade on an Ubuntu 20.10 system on which I had bind mounted an empty directory to /sys/class/dmi (sudo mount -o ro,bind dmi /sys/class/dmi). With the version of the release upgrader in -updates I was not able to upgrade to Ubuntu 21.04. Testing the version of the release upgrader in -proposed I was able to upgrade to Ubuntu 21.04. ubuntu@assured-caribou:/tmp/ubuntu-release-upgrader-cqvcwbjy$ cat DistUpgradeVersion.py VERSION = '21.04.13' ubuntu@assured-caribou:/tmp/ubuntu-release-upgrader-cqvcwbjy$ ls -lh /sys/class/dmi/ total 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931112 Title: Apple vendor quirk check for LP#1928434 incorrectly fails on all non- DMI hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1931112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928950] Re: ThinkPad X250 boot failure with kernel 5.4.0-73-generic (Linux Mint 19.3)
Still boot failure with kernel 5.4.0.75-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928950 Title: ThinkPad X250 boot failure with kernel 5.4.0-73-generic (Linux Mint 19.3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931171] Re: kernel_lockdown(7) describes removed SysRq for lifting lockdown
** Changed in: manpages (Ubuntu Impish) Status: New => In Progress ** Changed in: manpages (Ubuntu Hirsute) Status: New => Confirmed ** Changed in: manpages (Ubuntu Impish) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: manpages (Ubuntu Hirsute) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931171 Title: kernel_lockdown(7) describes removed SysRq for lifting lockdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/1931171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926748] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted grub2-signed into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/grub2-signed/1.167~16.04.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926748 Title: regression in xenial updates - grub2 cannot handle new arm64 relocations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1926748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926748] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted grub2-unsigned into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/grub2-unsigned/2.04-1ubuntu44.1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: grub2-signed (Ubuntu Xenial) Status: New => Fix Committed ** Tags removed: verification-done-xenial ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926748 Title: regression in xenial updates - grub2 cannot handle new arm64 relocations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1926748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926748] Re: regression in xenial updates - grub2 cannot handle new arm64 relocations
Hello Dimitri, or anyone else affected, Accepted grub2-signed into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/grub2-signed/1.167~18.04.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: grub2-signed (Ubuntu Bionic) Status: New => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-bionic ** Changed in: grub2-unsigned (Ubuntu Bionic) Status: New => 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/1926748 Title: regression in xenial updates - grub2 cannot handle new arm64 relocations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1926748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930742] Please test proposed package
Hello Steve, or anyone else affected, Accepted grub2-signed into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/grub2-signed/1.167~16.04.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930742 Title: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1930742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930742] Please test proposed package
Hello Steve, or anyone else affected, Accepted grub2-unsigned into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/grub2-unsigned/2.04-1ubuntu44.1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-failed-xenial ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930742 Title: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1930742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930742] Please test proposed package
Hello Steve, or anyone else affected, Accepted grub2-signed into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/grub2-signed/1.167~18.04.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930742 Title: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1930742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931112] Re: Apple vendor quirk check for LP#1928434 incorrectly fails on all non-DMI hardware
$ cat DistUpgradeVersion.py VERSION = '21.04.13' Test repeated using this version of the hirsute.tar.gz, and as expected both the TUI and Gtk3 versions provide the error that upgrades are not possible at this time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931112 Title: Apple vendor quirk check for LP#1928434 incorrectly fails on all non- DMI hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1931112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875066] Re: Missing NM-icon for established vpn-connections
Not working for me either even after an icon cache refresh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875066 Title: Missing NM-icon for established vpn-connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1875066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816544] Re: Menu don't show correctly.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sweethome3d (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/1816544 Title: Menu don't show correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sweethome3d/+bug/1816544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931171] [NEW] kernel_lockdown(7) describes removed SysRq for lifting lockdown
Public bug reported: [Impact] Documentation tells users they can lift lockdown locally via a SysRq, when in fact we do not support this (confirmed w/ @sforshee on kernel team). [Test Case] man kernel_lockdown - look for documentation of the SysRq feature. [Fix] https://github.com/alejandro-colomar/man-pages/commit/09df87e9ee3e1a429a2c1709dfd16ec8ff0f616 [Where Problems Could Occur] The only potential problem I can see is the corner case risk there is with any update - maybe the build environment has changed in some way that introduces a regression elsewhere in the package? /me waves hands. ** Affects: manpages (Ubuntu) Importance: Undecided Status: New ** Affects: manpages (Ubuntu Hirsute) Importance: Undecided Status: New ** Affects: manpages (Ubuntu Impish) Importance: Undecided Status: New ** Affects: manpages (Debian) Importance: Unknown Status: Unknown ** Also affects: manpages (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: manpages (Ubuntu Hirsute) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #989580 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989580 ** Also affects: manpages (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989580 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931171 Title: kernel_lockdown(7) describes removed SysRq for lifting lockdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/1931171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926960] Re: OpenSSL 1.1.1g function EC_KEY_set_group() causes illegal instruction SIGILL in file crypto/ec/ec_key:477
** Description changed: + [Impact] + The ibmca engine global state gets destroyed if the engine is loaded multiple times. This happens, e.g., during a git clone via https where first git-remote-https loads the engine and initializes it, and the libcurl loads the engine a second time, does not initialize it, but then destroy its second copy. During destruction, OpenSSL calls into the ibmca_destroy function when then manipulates global state that is shared with the first engine (the one loaded by git-remote-https which is still actively used). + + [Test Case] + I was able to build this package into a ppa and got the IBM team to confirm this problem was resolved for hirsute, groovy and focal see comment #2 and #3 + Another verification test will be done (as part of the SRU process) again by the IBM team. + + [What could go wrong] + Given this is an IBM component and that is happens on IBM hardware it is unlikely to affect anyone else. Also this problem was resolved initially upstream on April 28th and has been since included in Impish. the patch set applies cleanly on each version of ubuntu impacted (Hirsute, Groovy and Focal.) + + + [Original Description] + + Problem Description: - Loading and initializing the OpenSSL configuration twice causes ibmca to prematurely destroy global data. + Loading and initializing the OpenSSL configuration twice causes ibmca to prematurely destroy global data. This then causes crashes in applications that do this. It might happen if an application first initializes OpenSSls libcrypto and then libssl. - Solution: Please backport https://github.com/juergenchrist/openssl-ibmca/commit/40928425d848827fa8427d677e37178ab3b57e50 to fix this problem. focal (20.04LTS) (libs): 2.1.0-0ubuntu1 [ports]: s390x groovy (20.10) (libs): 2.1.1-0ubuntu1 [ports]: s390x hirsute (21.04) (libs): 2.1.1-0ubuntu1 [ports]: s390x git commit applies here cleanly. - impish (libs): 2.1.2-0ubuntu1 [ports]: s390x git commit should already be contained in this. So no need for another patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926960 Title: OpenSSL 1.1.1g function EC_KEY_set_group() causes illegal instruction SIGILL in file crypto/ec/ec_key:477 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1926960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931138] Re: Firefox 89.0 broke a lot of things
*** This bug is a duplicate of bug 1930982 *** https://bugs.launchpad.net/bugs/1930982 ** This bug has been marked a duplicate of bug 1930982 Firefox 89: webrender breaks videos on Raspberry Pi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931138 Title: Firefox 89.0 broke a lot of things To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1930422] Re: thermald_1.9.1-1ubuntu0.4_amd64 breaks system
yes desktop/tower pc with ubuntu 20.04 lts desktop cooling_device0-4 (out of 21) type = fan all five cur_state were set at 0 changed them to various values between 0-1 made no difference to fans On 07/06/2021 20:36, Srinivas Pandruvada wrote: > Thanks for the comment. > I would like to know something more about this system? > - Is this a desktop? > - Do you see any entry where /sys/class/thermal/cooling_device*/type = fan? > If you see can you control fan speed via > /sys/class/thermal/cooling_device*/cur_state > > I will cleanup the change and upload one final version before I merge > and release. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930422 Title: thermald_1.9.1-1ubuntu0.4_amd64 breaks system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1930422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931166] Re: Focal update: v5.4.124 upstream stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.124 upstream stable release + from git://git.kernel.org/ -v5.4.124 upstream stable release -from git://git.kernel.org/ + ALSA: hda/realtek: Headphone volume is controlled by Front mixer + ALSA: usb-audio: scarlett2: Fix device hang with ehci-pci + ALSA: usb-audio: scarlett2: Improve driver startup messages + cifs: set server->cipher_type to AES-128-CCM for SMB3.0 + NFSv4: Fix a NULL pointer dereference in pnfs_mark_matching_lsegs_return() + iommu/vt-d: Fix sysfs leak in alloc_iommu() + perf intel-pt: Fix sample instruction bytes + perf intel-pt: Fix transaction abort handling + perf scripts python: exported-sql-viewer.py: Fix copy to clipboard from Top Calls by elapsed Time report + perf scripts python: exported-sql-viewer.py: Fix Array TypeError + perf scripts python: exported-sql-viewer.py: Fix warning display + proc: Check /proc/$pid/attr/ writes against file opener + net: hso: fix control-request directions + ath10k: Validate first subframe of A-MSDU before processing the list + dm snapshot: properly fix a crash when an origin has no snapshots + drm/amdgpu/vcn1: add cancel_delayed_work_sync before power gate + drm/amdgpu/vcn2.0: add cancel_delayed_work_sync before power gate + drm/amdgpu/vcn2.5: add cancel_delayed_work_sync before power gate + selftests/gpio: Use TEST_GEN_PROGS_EXTENDED + selftests/gpio: Move include of lib.mk up + selftests/gpio: Fix build when source tree is read only + kgdb: fix gcc-11 warnings harder + Documentation: seccomp: Fix user notification documentation + serial: core: fix suspicious security_locked_down() call + misc/uss720: fix memory leak in uss720_probe + thunderbolt: dma_port: Fix NVM read buffer bounds and offset issue + mei: request autosuspend after sending rx flow control + staging: iio: cdc: ad7746: avoid overwrite of num_channels + iio: gyro: fxas21002c: balance runtime power in error path + iio: adc: ad7768-1: Fix too small buffer passed to iio_push_to_buffers_with_timestamp() + iio: adc: ad7124: Fix missbalanced regulator enable / disable on error. + iio: adc: ad7124: Fix potential overflow due to non sequential channel numbers + iio: adc: ad7793: Add missing error code in ad7793_setup() + serial: 8250_pci: Add support for new HPE serial device + serial: 8250_pci: handle FL_NOIRQ board flag + USB: trancevibrator: fix control-request direction + USB: usbfs: Don't WARN about excessively large memory allocations + serial: tegra: Fix a mask operation that is always true + serial: sh-sci: Fix off-by-one error in FIFO threshold register setting + serial: rp2: use 'request_firmware' instead of 'request_firmware_nowait' + USB: serial: ti_usb_3410_5052: add startech.com device id + USB: serial: option: add Telit LE910-S1 compositions 0x7010, 0x7011 + USB: serial: ftdi_sio: add IDs for IDS GmbH Products + USB: serial: pl2303: add device id for ADLINK ND-6530 GC + thermal/drivers/intel: Initialize RW trip to THERMAL_TEMP_INVALID + usb: dwc3: gadget: Properly track pending and queued SG + usb: gadget: udc: renesas_usb3: Fix a race in usb3_start_pipen() + net: usb: fix memory leak in smsc75xx_bind + spi: spi-geni-qcom: Fix use-after-free on unbind + Bluetooth: cmtp: fix file refcount when cmtp_attach_device fails + fs/nfs: Use fatal_signal_pending instead of signal_pending + NFS: fix an incorrect limit in filelayout_decode_layout() + NFS: Fix an Oopsable condition in __nfs_pageio_add_request() + NFS: Don't corrupt the value of pg_bytes_written in nfs_do_recoalesce() + NFSv4: Fix v4.0/v4.1 SEEK_DATA return -ENOTSUPP when set NFS_V4_2 config + drm/meson: fix shutdown crash when component not probed + net/mlx5e: Fix multipath lag activation + net/mlx5e: Fix nullptr in add_vlan_push_action() + net/mlx4: Fix EEPROM dump support + Revert "net:tipc: Fix a double free in tipc_sk_mcast_rcv" + tipc: wait and exit until all work queues are done + tipc: skb_linearize the head skb when reassembling msgs + spi: spi-fsl-dspi: Fix a resource leak in an error handling path + net: dsa: mt7530: fix VLAN traffic
[Bug 1928259] Re: Package upgrade won't restart services
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/nfs-utils/+git/nfs-utils/+merge/403835 ** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/nfs-utils/+git/nfs-utils/+merge/403836 ** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/nfs-utils/+git/nfs-utils/+merge/403837 ** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/nfs-utils/+git/nfs-utils/+merge/403838 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928259 Title: Package upgrade won't restart services To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1928259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928259] Re: Package upgrade won't restart services
** Description changed: [Impact] In order to get the fixes provided by a package update, the affected services shipped in it need to be restarted. When that restart does not happen, the system remains running the old binaries with the bug(s). This bug was found while testing the fix for #1927745, which affected rpc.gssd, one of the services shipped in nfs-common. Without the restart, systems that installed the update are still affected by the bug. [Test Plan] To make the test simple, we are not going to mount an NFSv4 share using kerberos. We are just going to have a minimal configuration that gets rpc.gssd running to demonstrate the before and after of this bug. For a more thorough testing, which includes actually mounting an NFSv4 export with kerberos, follow the test instructions of bug #1927745, and you will see that the manual restart included because of this bug here, after the package is updated, is no longer needed. + TEST (A) # create a VM for the affected ubuntu release under test, login and run: sudo touch /etc/krb5.keytab sudo chmod 0600 /etc/krb5.keytab # install nfs-common sudo apt install nfs-common -y # note message about nfs-utils.service being disabled/static: nfs-utils.service is a disabled or a static unit, not starting it. # Manually start rpc-gssd. It will start, but since we have an empty # krb5.keytab file, it won't work. That's ok, we are not actually going to # mount nfsv4 systemctl start rpc-gssd.service # Check it's running, and make note of its pid: pidof rpc.gssd 2994 # reinstall nfs-common sudo apt install --reinstall nfs-common # note rpc-gssd wasn't restarted pidof rpc.gssd 2994 - # install the fixed nfs-common package: - sudo apt install nfs-commont + # install the fixed nfs-common package. Notice the message about starting a disabled or static unit no longer appears: + sudo apt install nfs-common # this time, rpc.gssd is restarted pidof rpc.gssd 5000 + + + TEST (B) + This test is to confirm no new services are started after the fixed package is installed for the first time. + + # create a VM for the affected ubuntu release under test, login and run: + sudo touch /etc/krb5.keytab + sudo chmod 0600 /etc/krb5.keytab + + # install nfs-common that has the bug + sudo apt install nfs-common -y + + # take a snapshot of running processes + pstree > pstree.old + + # purge the nfs-common package + sudo apt purge nfs-common -y + + # install the new nfs-common package + sudo apt purge nfs-common -y + + # take a new pstree snapshot and compare with the old one + pstree > pstree.new + diff -u pstree.old pstree.new + + Should be no difference. + [Where problems could occur] Also known as "I'm doing an unconditional start in postinst, what could go wrong": - start services that were not started with the previous package on first install - systemd behavior change or bug and suddenly PartOf units also react to "start", instead of just "restart" and "stop" as documented - starting services that are not configured, and start fails, breaking postinst (but we have the proverbial || true to avoid that) [Other Info] This fix is a bit awkward, but I think it's in line with the SRU spirit of doing the least unpredictable change, and one that is simple and can be better understood. See the linked MP for an explanation of this fix, why it works, and other tests I did: https://code.launchpad.net/~ahasenack/ubuntu/+source/nfs-utils/+git/nfs-utils/+merge/403288 [Original Description] Upgrading the nfs-common debian package will not restart its services. Specifically, the package tries to restart "nfs-utils.service", which is a "fake" service meant to coordinate all the other daemons that make up a modern NFS server. This service, however, as it is, cannot be enabled: $ sudo systemctl enable nfs-utils.service The unit files have no installation config (WantedBy, RequiredBy, Also, Alias settings in the [Install] section, and DefaultInstance for template units). This means they are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). 4) In case of template units, the unit is meant to be enabled with some instance name specified Granted, d/rules of the nfs-utils package doesn't even try: dh_systemd_enable -p nfs-common nfs-client.target dh_systemd_enable -p nfs-kernel-server nfs-server.service dh_installinit -pnfs-common -R dh_systemd_start -p nfs-common --restart-after-upgrade nfs-utils.service
[Bug 1931138] Re: Firefox 89.0 broke a lot of things
Confirmed that setting gfx.webrender.force-disabled to True solve the problem Perhaps this Bug 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/1931138 Title: Firefox 89.0 broke a lot of things To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931166] [NEW] Focal update: v5.4.124 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.124 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931166 Title: Focal update: v5.4.124 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915536] Re: one grub
** Changed in: grub2-unsigned (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: grub2-unsigned (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: grub2-unsigned (Ubuntu Focal) 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/1915536 Title: one grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1915536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927219] Re: context deadline exceeded: unknown in containerd with latest runc version
The containerd regressions in Focal and Bionic were already sorted out, the tests are passing now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927219 Title: context deadline exceeded: unknown in containerd with latest runc version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/runc/+bug/1927219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927219] Re: context deadline exceeded: unknown in containerd with latest runc version
I've been trying to find a fix for the golang-github-containers- common/0.33.4+ds1-1 regression in Hirsute but without success so far. However, the issue seems to be unrelated to this runc SRU, it is a compilation issue in one of its components: # github.com/containers/storage/pkg/devicemapper ../../../go-build3064824172/b263/_cgo_export.c:21:13: error: variable ‘_cgoexp_ebd00b0772db_StorageDevmapperLogCallback’ redeclared as function 21 | extern void _cgoexp_ebd00b0772db_StorageDevmapperLogCallback(void *); | ^ ../../../go-build3064824172/b263/cgo-generated-wrappers:1:5: note: previously declared here lto1: fatal error: errors during merging of translation units compilation terminated. Due to that, I'd ask the SRU team to ignore this regression for now and not block this SRU just because of it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927219 Title: context deadline exceeded: unknown in containerd with latest runc version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/runc/+bug/1927219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929106] Re: runc -v empty output
All comments regarding the reported regressions were added to LP #1927219 and they apply here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929106 Title: runc -v empty output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/runc/+bug/1929106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931112] Re: Apple vendor quirk check for LP#1928434 incorrectly fails on all non-DMI hardware
Disregard, I tested 21.04.12, and I will retest 21.04.13 when available. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931112 Title: Apple vendor quirk check for LP#1928434 incorrectly fails on all non- DMI hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1931112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921143] Re: efivarfs_set_variable: writing to fd 7 failed: Invalid argument.
** Package changed: grub2-unsigned (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/1921143 Title: efivarfs_set_variable: writing to fd 7 failed: Invalid argument. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1921143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928701] Re: update-grub does not run on kernel updates
*** This bug is a duplicate of bug 1928674 *** https://bugs.launchpad.net/bugs/1928674 ** This bug has been marked a duplicate of bug 1928674 grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928701 Title: update-grub does not run on kernel updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1928701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926713] Re: package grub-efi-amd64 2.04-1ubuntu44 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 127
> /etc/grub.d/bin/grubcfg_proxy: error while loading shared libraries: > libcrypto.so.1.0.0: cannot open shared object file: No such file or directory > Hittade Windows Boot Manager på /dev/sda1@/efi/Microsoft/Boot/bootmgfw.efi > dpkg: error processing package grub-efi-amd64 (--configure): > installed grub-efi-amd64 package post-installation script subprocess > returned error exit status 127 What is /etc/grub.d/bin/grubcfg_proxy? This file doesn't exist in Ubuntu. And you have put it in a path on your system such that you must be able to execute it in order for update-grub to succeed. And it depends on an obsolete version of libcrypto. You will need to fix your local configuration to not be blocked on this broken, third-party executable. ** Changed in: grub2-unsigned (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/1926713 Title: package grub-efi-amd64 2.04-1ubuntu44 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1926713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] Comment bridged from LTC Bugzilla
--- Comment From mario.alberto.gali...@ibm.com 2021-06-07 16:13 EDT--- Just executed netplan try and netplan apply and take snapshot of journalctl. It is attached now! - The configuration has not being touched for long time - Correct is the only one presenting this problem - Correct all of the host has RoCe v2.X installed Could you explain what do you mean with setup the vLan using the IP commands? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931112] Re: Apple vendor quirk check for LP#1928434 incorrectly fails on all non-DMI hardware
The original quirk from LP: #1929449 continues to decline upgrade for Apple hardware, as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931112 Title: Apple vendor quirk check for LP#1928434 incorrectly fails on all non- DMI hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1931112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926748] Re: regression in xenial updates - grub2 cannot handle new arm64 relocations
** Also affects: grub2-unsigned (Ubuntu) Importance: Undecided Status: New ** Changed in: grub2-unsigned (Ubuntu) Status: New => Invalid ** Also affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Changed in: grub2-signed (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926748 Title: regression in xenial updates - grub2 cannot handle new arm64 relocations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1926748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922234] Re: Grub doesn't update kernel version
*** This bug is a duplicate of bug 1928674 *** https://bugs.launchpad.net/bugs/1928674 ** This bug has been marked a duplicate of bug 1928674 grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922234 Title: Grub doesn't update kernel version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1922234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928259] Re: Package upgrade won't restart services
** Description changed: [Impact] In order to get the fixes provided by a package update, the affected services shipped in it need to be restarted. When that restart does not happen, the system remains running the old binaries with the bug(s). This bug was found while testing the fix for #1927745, which affected rpc.gssd, one of the services shipped in nfs-common. Without the restart, systems that installed the update are still affected by the bug. [Test Plan] To make the test simple, we are not going to mount an NFSv4 share using kerberos. We are just going to have a minimal configuration that gets rpc.gssd running to demonstrate the before and after of this bug. # create a VM for the affected ubuntu release under test, login and run: - sudo touch /etc/krb5.keytab + sudo touch /etc/krb5.keytab sudo chmod 0600 /etc/krb5.keytab # install nfs-common sudo apt install nfs-common -y - # note message about nfs-utils.service being disabled/static: + # note message about nfs-utils.service being disabled/static: nfs-utils.service is a disabled or a static unit, not starting it. - # Manually start rpc-gssd. It will start, but since we have an empty - # krb5.keytab file, it won't work. That's ok, we are not actually going to - # mount nfsv4 + # Manually start rpc-gssd. It will start, but since we have an empty + # krb5.keytab file, it won't work. That's ok, we are not actually going to + # mount nfsv4 systemctl start rpc-gssd.service - # Check it's running, and make note of its pid: - pidof rpc.gssd - 2994 + # Check it's running, and make note of its pid: + pidof rpc.gssd + 2994 - # reinstall nfs-common + # reinstall nfs-common sudo apt install --reinstall nfs-common - # note rpc-gssd wasn't restarted - pidof rpc.gssd - 2994 + # note rpc-gssd wasn't restarted + pidof rpc.gssd + 2994 - # install the fixed nfs-common package: - sudo apt install nfs-commont - - # this time, rpc.gssd is restarted - pidof rpc.gssd - 5000 + # install the fixed nfs-common package: + sudo apt install nfs-commont + # this time, rpc.gssd is restarted + pidof rpc.gssd + 5000 [Where problems could occur] - - * Think about what the upload changes in the software. Imagine the change is - wrong or breaks something else: how would this show up? - - * It is assumed that any SRU candidate patch is well-tested before - upload and has a low overall risk of regression, but it's important - to make the effort to think about what ''could'' happen in the - event of a regression. - - * This must '''never''' be "None" or "Low", or entirely an argument as to why - your upload is low risk. - - * This both shows the SRU team that the risks have been considered, - and provides guidance to testers in regression-testing the SRU. + Also known as "I'm doing an unconditional start in postinst, what could go wrong": + - start services that were not started with the previous package on first install + - systemd behavior change or bug and suddenly PartOf units also react to "start", instead of just "restart" and "stop" as documented + - starting services that are not configured, and start fails, breaking postinst (but we have the proverbial || true to avoid that) [Other Info] + This fix is a bit awkward, but I think it's in line with the SRU spirit of doing the least unpredictable change, and one that is simple and can be better understood. - * Anything else you think is useful to include - * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board - * and address these questions in advance + See the linked MP for an explanation of this fix, why it works, and other tests I did: + https://code.launchpad.net/~ahasenack/ubuntu/+source/nfs-utils/+git/nfs-utils/+merge/403288 + [Original Description] Upgrading the nfs-common debian package will not restart its services. Specifically, the package tries to restart "nfs-utils.service", which is a "fake" service meant to coordinate all the other daemons that make up a modern NFS server. This service, however, as it is, cannot be enabled: $ sudo systemctl enable nfs-utils.service The unit files have no installation config (WantedBy, RequiredBy, Also, Alias settings in the
[Bug 1928674] Re: grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: grub2-signed (Ubuntu Trusty) 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/1928674 Title: grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1928674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] joutnalctl
--- Comment (attachment only) From mario.alberto.gali...@ibm.com 2021-06-07 16:08 EDT--- ** Attachment added: "joutnalctl" https://bugs.launchpad.net/bugs/1929657/+attachment/5502963/+files/dump-of-journalctl.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930742] Re: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable
Launched c6g.metal, a1.metal, and t4g.medium instance with Xenial (20210429) on upgrade of all three I got the following error: grub-install: error: relocation 0x113 is not implemented yet. Failed: grub-install --target=arm64-efi WARNING: Bootloader is not properly installed, system may not be bootable Log: https://paste.ubuntu.com/p/khgMBYH86N/ Script: https://paste.ubuntu.com/p/cnTHCd8hGQ/ Marking verification verification-failed-xenial ** Tags removed: verification-needed-xenial ** Tags added: verification-failed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930742 Title: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1930742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931112] Re: Apple vendor quirk check for LP#1928434 incorrectly fails on all non-DMI hardware
Hello Alyssa, or anyone else affected, Accepted ubuntu-release-upgrader into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /ubuntu-release-upgrader/1:21.04.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-release-upgrader (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931112 Title: Apple vendor quirk check for LP#1928434 incorrectly fails on all non- DMI hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1931112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928259] Re: Package upgrade won't restart services
** Description changed: [Impact] + In order to get the fixes provided by a package update, the affected services shipped in it need to be restarted. When that restart does not happen, the system remains running the old binaries with the bug(s). - * An explanation of the effects of the bug on users and - - * justification for backporting the fix to the stable release. - - * In addition, it is helpful, but not required, to include an -explanation of how the upload fixes this bug. + This bug was found while testing the fix for #1927745, which affected + rpc.gssd, one of the services shipped in nfs-common. Without the + restart, systems that installed the update are still affected by the + bug. [Test Plan] + To make the test simple, we are not going to mount an NFSv4 share using kerberos. We are just going to have a minimal configuration that gets rpc.gssd running to demonstrate the before and after of this bug. - * detailed instructions how to reproduce the bug + # create a VM for the affected ubuntu release under test, login and run: + sudo touch /etc/krb5.keytab + sudo chmod 0600 /etc/krb5.keytab - * these should allow someone who is not familiar with the affected -package to reproduce the bug and verify that the updated package fixes -the problem. + # install nfs-common + sudo apt install nfs-common -y - * if other testing is appropriate to perform before landing this update, -this should also be described here. + # note message about nfs-utils.service being disabled/static: + nfs-utils.service is a disabled or a static unit, not starting it. + + # Manually start rpc-gssd. It will start, but since we have an empty + # krb5.keytab file, it won't work. That's ok, we are not actually going to + # mount nfsv4 + systemctl start rpc-gssd.service + + # Check it's running, and make note of its pid: + pidof rpc.gssd + 2994 + + # reinstall nfs-common + sudo apt install --reinstall nfs-common + + # note rpc-gssd wasn't restarted + pidof rpc.gssd + 2994 + + # install the fixed nfs-common package: + sudo apt install nfs-commont + + # this time, rpc.gssd is restarted + pidof rpc.gssd + 5000 + [Where problems could occur] - * Think about what the upload changes in the software. Imagine the change is -wrong or breaks something else: how would this show up? + * Think about what the upload changes in the software. Imagine the change is + wrong or breaks something else: how would this show up? - * It is assumed that any SRU candidate patch is well-tested before -upload and has a low overall risk of regression, but it's important -to make the effort to think about what ''could'' happen in the -event of a regression. + * It is assumed that any SRU candidate patch is well-tested before + upload and has a low overall risk of regression, but it's important + to make the effort to think about what ''could'' happen in the + event of a regression. - * This must '''never''' be "None" or "Low", or entirely an argument as to why -your upload is low risk. + * This must '''never''' be "None" or "Low", or entirely an argument as to why + your upload is low risk. - * This both shows the SRU team that the risks have been considered, -and provides guidance to testers in regression-testing the SRU. + * This both shows the SRU team that the risks have been considered, + and provides guidance to testers in regression-testing the SRU. [Other Info] - - * Anything else you think is useful to include - * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board - * and address these questions in advance + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance [Original Description] Upgrading the nfs-common debian package will not restart its services. Specifically, the package tries to restart "nfs-utils.service", which is a "fake" service meant to coordinate all the other daemons that make up a modern NFS server. This service, however, as it is, cannot be enabled: $ sudo systemctl enable nfs-utils.service The unit files have no installation
[Bug 1931077] Re: emergency shell ignores all keyboard input
Ideally, I'd wish it not to stop sshd when /boot/efi becomes unavailable. Or at least bring back the services it stopped when the emergency shell is canceled. More practically, and more on topic to the original reason for this bug report, I'd like it if stopping the emergency shell would print a message on the console, so the instructions to press Enter or Ctrl-D do not appear to still be relevant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931077 Title: emergency shell ignores all keyboard input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1931077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930917] Re: Latest isc-dhcp-server rejects proper dhcpd.conf
Thanks for reporting the issue! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930917 Title: Latest isc-dhcp-server rejects proper dhcpd.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1930917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
