[Bug 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
Hi Evan, Great to hear things are looking good for you and that the block discard performance is there. If possible, keep running the kernel from -proposed for a bit longer, just to make sure nothing comes up on longer runs. I spent some time today performing verification on all the kernels in -proposed, testing block discard performance [1], and also running through the regression testcase from LP #1907262 [2]. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578 [2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262 All kernels performed as expected, with block discard on 4x 1.9TB NVMe disks on an i3.8xlarge AWS instance taking 3-4 seconds, and the consistency checks performed returned clean disks, with no filesystem or data corruption. I have documented my tests in my verification messages: Hirsute: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/comments/26 Groovy: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/comments/27 Focal: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/comments/28 Bionic: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/comments/29 I have marked the launchpad bug as verified for all releases. I'm still running my own testing, with my /home directory being on a Raid10 array on a Google Cloud instance, and it has no issues. If things keep going well, we should see a release to -updates around the 21st of June, give or take a few days if any CVEs turn up. 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 1907262] Re: raid10: discard leads to corrupted file system
Hi Thimo, Thanks for letting me know, and great to hear that things are working as expected. I'll check in with you in one week's time, to double check things are still going okay. I spent some time today performing verification on all the kernels in -proposed, testing block discard performance [1], and also running through the regression testcase from LP #1907262 [2]. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578 [2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262 All kernels performed as expected, with block discard on 4x 1.9TB NVMe disks on an i3.8xlarge AWS instance taking 3-4 seconds, and the consistency checks performed returned clean disks, with no filesystem or data corruption. I have documented my tests in my verification messages: Hirsute: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/comments/26 Groovy: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/comments/27 Focal: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/comments/28 Bionic: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/comments/29 I have marked the launchpad bug as verified for all releases. I'm still running my own testing, with my /home directory being on a Raid10 array on a Google Cloud instance, and it has no issues. If things keep going well, we should see a release to -updates around the 21st of June, give or take a few days if any CVEs turn up. 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 1931630] Re: Linux images for virtual machines with unset `CONFIG_MAGIC_SYSRQ` cause `10-magic-sysrq.conf` to fail
In #ubuntu-ser...@irc.libera.chat I was told to move this issue to *linux-image-kvm*. How can I do that? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931630 Title: Linux images for virtual machines with unset `CONFIG_MAGIC_SYSRQ` cause `10-magic-sysrq.conf` to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1931630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931455] Re: open-iscsi fails to create nodes directory
Hi, First of all there are two services - and maybe outlining the difference and the reasoning will help here. # Reasons It is fair to say that probably >99% of the users are not using open- iscsi and therefore having the daemon started on install (and it is default installed for cases that need it on start to connect to their data) would mean that millions of system would consume a little bit of memory and cpu. This is a matter of scale, so it might not matter for me or you on your system, but on millions of nodes that adds up to power & space consumption. # Two Services There is: a) ● iscsid.service - iSCSI initiator daemon (iscsid) Loaded: loaded (/lib/systemd/system/iscsid.service; disabled; vendor preset: enabled) Active: inactive (dead) TriggeredBy: ● iscsid.socket Docs: man:iscsid(8) This one you can see is socket activated, that means by default it also isn't started but the iscsiadm command mentioned by Simon will find the socket, then it is transparently started and will work. Again to have it off by default, but working right away. That is enough to probe & configure iscsi - you don't need more than that extra socket provided by systemd. b) ● open-iscsi.service - Login to default iSCSI targets Loaded: loaded (/lib/systemd/system/open-iscsi.service; enabled; vendor preset: enabled) Active: inactive (dead) Condition: start condition failed at Mon 2021-06-07 06:44:26 UTC; 3 days ago Docs: man:iscsiadm(8) man:iscsid(8) This one is responsible to log into configured targets, and as long as none are configured there is no reason to start it, hence the conditions. I'd be concerned if targets were configured and it would not start, but that isn't the case here. As presented here I guess it is not a problem, but I'm open for discussion. If one thinks that this clarification was very helpful let us know, because then maybe we should make it part of the official docs that Simon pointed to. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931455 Title: open-iscsi fails to create nodes directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1931455/+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
Performing verification for Bionic. I'm going to do three rounds of verification. The first is the testcase from this bug, showing block discard performance. The second is running through the regression reproducer from bug 1907262. The third will be results from my testing with my /home directory on a cloud instance with Raid10 backed disks, 3x customer testing and 2x community user testing. This will be in a separate comment closer to the release date once I have collected results. Starting with the testcase for this bug. I started a i3.8xlarge instance on AWS, enabled -proposed and installed 4.15.0-145-generic. From there, I ran through the testcase of making a Raid10 array, and formatting it with xfs, and block discard performance was excellent: https://paste.ubuntu.com/p/Sr8tR9yhRd/ It took 3.2 seconds to format the array with xfs, and 1.0 seconds for a fstrim, as opposed to the 20 minutes it took beforehand. Performance with block discard is excellent. Moving onto the second testcase, the regression reproducer from bug 1907262. I started a n1-standard-2 VM on Google Cloud, and attached 2x NVMe scratch disks. I enabled -proposed and installed 4.15.0-145-generic. I ran through the testcase of making a Raid10 array, doing consistency checks, ensuring that mismatch count is 0, creating a file, deleting it, performing a fstrim, and more consistency checks, then taking the raid array down and bringing up one disk at a time, and performing a fsck.ext4. All disks came back clean: https://paste.ubuntu.com/p/h8gTd4JQ8Y/ Since the block discard performance is there, and there is no apparent data corruption going on after a fstrim, I will mark this verified for Bionic. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
Performing verification for Focal. I'm going to do three rounds of verification. The first is the testcase from this bug, showing block discard performance. The second is running through the regression reproducer from bug 1907262. The third will be results from my testing with my /home directory on a cloud instance with Raid10 backed disks, 3x customer testing and 2x community user testing. This will be in a separate comment closer to the release date once I have collected results. Starting with the testcase for this bug. I started a i3.8xlarge instance on AWS, enabled -proposed and installed 5.4.0-75-generic. From there, I ran through the testcase of making a Raid10 array, and formatting it with xfs, and block discard performance was excellent: https://paste.ubuntu.com/p/mdQ6Wjr4yK/ It took 6.6 seconds to format the array with xfs, and 3.8 seconds for a fstrim, as opposed to the 20 minutes it took beforehand. Performance with block discard is excellent. Moving onto the second testcase, the regression reproducer from bug 1907262. I started a n1-standard-2 VM on Google Cloud, and attached 2x NVMe scratch disks. I enabled -proposed and installed 5.4.0-75-generic. I ran through the testcase of making a Raid10 array, doing consistency checks, ensuring that mismatch count is 0, creating a file, deleting it, performing a fstrim, and more consistency checks, then taking the raid array down and bringing up one disk at a time, and performing a fsck.ext4. All disks came back clean: https://paste.ubuntu.com/p/jFHW26kcCK/ Since the block discard performance is there, and there is no apparent data corruption going on after a fstrim, I will mark this verified for Focal. ** 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/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 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
Performing verification for Groovy. I'm going to do three rounds of verification. The first is the testcase from this bug, showing block discard performance. The second is running through the regression reproducer from bug 1907262. The third will be results from my testing with my /home directory on a cloud instance with Raid10 backed disks, 3x customer testing and 2x community user testing. This will be in a separate comment closer to the release date once I have collected results. Starting with the testcase for this bug. I started a i3.8xlarge instance on AWS, enabled -proposed and installed 5.8.0-56-generic. From there, I ran through the testcase of making a Raid10 array, and formatting it with xfs, and block discard performance was excellent: https://paste.ubuntu.com/p/GGXfjCHfDR/ It took 5.7 seconds to format the array with xfs, and 2.3 seconds for a fstrim, as opposed to the 20 minutes it took beforehand. Performance with block discard is excellent. Moving onto the second testcase, the regression reproducer from bug 1907262. I started a n1-standard-2 VM on Google Cloud, and attached 2x NVMe scratch disks. I enabled -proposed and installed 5.8.0-56-generic. I ran through the testcase of making a Raid10 array, doing consistency checks, ensuring that mismatch count is 0, creating a file, deleting it, performing a fstrim, and more consistency checks, then taking the raid array down and bringing up one disk at a time, and performing a fsck.ext4. All disks came back clean: https://paste.ubuntu.com/p/75xWd4Z3NZ/ Since the block discard performance is there, and there is no apparent data corruption going on after a fstrim, I will mark this verified for Groovy. ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- 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 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
Performing verification for Hirsute. I'm going to do three rounds of verification. The first is the testcase from this bug, showing block discard performance. The second is running through the regression reproducer from bug 1907262. The third will be results from my testing with my /home directory on a cloud instance with Raid10 backed disks, 3x customer testing and 2x community user testing. This will be in a separate comment closer to the release date once I have collected results. Starting with the testcase for this bug. I started a i3.8xlarge instance on AWS, enabled -proposed and installed 5.11.0-20-generic. From there, I ran through the testcase of making a Raid10 array, and formatting it with xfs, and block discard performance was excellent: https://paste.ubuntu.com/p/X5sdCGT78Y/ It took 4.6 seconds to format the array with xfs, and 2.8 seconds for a fstrim, as opposed to the 20 minutes it took beforehand. Performance with block discard is excellent. Moving onto the second testcase, the regression reproducer from bug 1907262. I started a n1-standard-2 VM on Google Cloud, and attached 2x NVMe scratch disks. I enabled -proposed and installed 5.11.0-20-generic. I ran through the testcase of making a Raid10 array, doing consistency checks, ensuring that mismatch count is 0, creating a file, deleting it, performing a fstrim, and more consistency checks, then taking the raid array down and bringing up one disk at a time, and performing a fsck.ext4. All disks came back clean: https://paste.ubuntu.com/p/Xy6CPCQXZN/ Since the block discard performance is there, and there is no apparent data corruption going on after a fstrim, I will mark this verified for Hirsute. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- 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 1931665] Re: HP EliteBook 845 G7 (Cezanne) S0iX not available due to the lack of amdgpu firmware for green_sardine
** Changed in: linux-firmware (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-firmware (Ubuntu Hirsute) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931665 Title: HP EliteBook 845 G7 (Cezanne) S0iX not available due to the lack of amdgpu firmware for green_sardine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1931665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929444] Re: SD card initialization on insertion fails
https://lkml.org/lkml/2021/6/7/416 is accepted upstream. I'll backport it when it's in linux-next. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929444 Title: SD card initialization on insertion fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931671] [NEW] Not able to upgrade from 18.04 to 20.04.
Public bug reported: not able to upgrade from 18.04 to 20.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.29 [origin: unknown] ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CrashDB: ubuntu Date: Fri Jun 11 09:49:05 2021 InstallationDate: Installed on 2019-01-21 (871 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2021-06-11 (0 days ago) VarLogDistupgradeAptlog: Log time: 2021-06-11 09:47:08.750332 Log time: 2021-06-11 09:48:11.515500 Log time: 2021-06-11 09:49:04.763424 Log time: 2021-06-11 09:49:07.569591 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931671 Title: Not able to upgrade from 18.04 to 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1931671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809205] Re: lubuntu 19.04 daily qa - opening menu from panel on display2 but menu appears on display1
[Expired for lxqt-panel (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lxqt-panel (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/1809205 Title: lubuntu 19.04 daily qa - opening menu from panel on display2 but menu appears on display1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-panel/+bug/1809205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913872] Re: No update 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/1913872 Title: No update to Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1913872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923328] Re: xrdp wants to remove lubuntu-desktop on lubuntu
[Expired for xrdp (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xrdp (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/1923328 Title: xrdp wants to remove lubuntu-desktop on lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1923328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923332] Re: Screen froze on boot
[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/1923332 Title: Screen froze on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1923332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
Can you give me the dmesg from boot? I can at least know how the HID do the input mapping. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931665] Re: HP EliteBook 845 G7 (Cezanne) S0iX not available due to the lack of amdgpu firmware for green_sardine
> For the purpose of an SRU to fix the pointed problem, we should only touch the Cezanne firmware (cherry-pick commit 15003b062125921d3b51256af5583c16a955db2b) ** Also affects: linux-firmware (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Focal) 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/1931665 Title: HP EliteBook 845 G7 (Cezanne) S0iX not available due to the lack of amdgpu firmware for green_sardine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1931665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931665] [NEW] HP EliteBook 845 G7 (Cezanne) S0iX not available due to the lack of amdgpu firmware for green_sardine
Public bug reported: OS: Ubuntu 20.04.2 Linux kernel: 5.10.0-1027-oem Linux firmware: 1.187.12 Device: HP EliteBook 845 G7 (Cezanne) Even though the soix changes have been merged with 5.10.0-1027-oem, AMD Cezanne amdgpu firmware files are not present in in Ubuntu linux- firmware 1.187.12. With the above packages, resume breaks. No error message in dmesg. If I replace /lib/firmware with contents from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-20210511.tar.gz, suspend/resume works. During suspend, LCD backlight, fan & keyboard backlight turns off. After resume, everything is back to normal. No errors regarding AMD GPU. The current Ubuntu linux-firmware package is two months old & there are lots of amdgpu & radeon commits after that. Prefer a generic update to the latest fw package. If its AMD Cezanne specific, the fw file names prefix is "green_sardine". This is a public bug for landing for bug 1929104. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Assignee: You-Sheng Yang (vicamo) Status: New ** Affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Hirsute) Importance: Undecided Status: New ** Tags: hwe-graphics ihv-amd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931665 Title: HP EliteBook 845 G7 (Cezanne) S0iX not available due to the lack of amdgpu firmware for green_sardine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1931665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927866] Re: Root filesystem becomes readonly frequenty freezing system
Ran into this again. Was connected to power, closed lid, disconnected from power, kept for a while. Opened, logged in, opened browser, started working on an email and boom. Crashed. Isn't there anything we can do to get more logging on this? Mount an external usb drive as /var/log? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927866 Title: Root filesystem becomes readonly frequenty freezing system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1426838] Re: Unable to select language which defaults to french
It looks like Debian fixed this bug a number of years ago: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787479 ** Bug watch added: Debian Bug tracker #787479 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787479 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1426838 Title: Unable to select language which defaults to french To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/optgeo/+bug/1426838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931660] [NEW] PANIC at zfs_znode.c:339:zfs_znode_sa_init()
Public bug reported: I'm seeing a non-deterministic panic in the ZFS code. Last boot, this occurred in systemd-udevd, resulting in a failed boot. The boot before that, firefox hit the same thing, and this boot it looks like it's hit an Evolution component. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.11.0-18-generic 5.11.0-18.19+21.10.1 ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 4988 F pulseaudio /dev/snd/controlC1: chris 4988 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 11:49:47 2021 InstallationDate: Installed on 2021-05-13 (28 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_z8j7yc@/vmlinuz-5.11.0-18-generic root=ZFS=rpool/ROOT/ubuntu_z8j7yc ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.198 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-05-13 (28 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session ** Attachment added: "dmesg from previous boot showing PANIC" https://bugs.launchpad.net/bugs/1931660/+attachment/5503919/+files/broken.dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931660 Title: PANIC at zfs_znode.c:339:zfs_znode_sa_init() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931612] Re: Print dialog box shows same printer twice
** Package changed: ubuntu => cups (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931612 Title: Print dialog box shows same printer twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1931612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929147] Re: fix system hang with 5.10 kernel + RX540 on RKL platform
** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929147 Title: fix system hang with 5.10 kernel + RX540 on RKL platform To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1929147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930275] Re: [nvidia] System does not wake up after suspend
Thanks. That indeed just shows a sleeping system. No evidence of waking up. This is probably a driver or kernel issue and since Ubuntu 20.10 is about to reach end-of-life I suggest upgrading to Ubuntu 21.04 which has a very different kernel. Or if you want a release with a long lifecycle then install 20.04 instead. Please let us know if 21.04 or 20.04 has the same bug so as to avoid this bug closing next month. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930275 Title: [nvidia] System does not wake up after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931475] Re: Ubuntu only stable in safe graphics mode
Those logs are from kernel 5.10.0-1029-oem so reassigning... ** Package changed: linux (Ubuntu) => linux-oem-5.10 (Ubuntu) ** Summary changed: - Ubuntu only stable in safe graphics mode + [i915] [Comet Lake] Ubuntu only stable in safe graphics mode ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931475 Title: [i915] [Comet Lake] Ubuntu only stable in safe graphics mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931475/+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
Unmarking as a duplicate of bug 1930733. It doesn't look like the same issue. Bas, please remember to follow the instructions in comment #4. ** This bug is no longer a duplicate of bug 1930733 Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI -- 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 1931547] Re: DisplayLink displays are black after Mesa update
Nobody was talking about skipping 20.04, only 20.10 which reaches end- of-life next month. https://wiki.ubuntu.com/Releases Anyway, I'm not working on this bug so it's not up to me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931547 Title: DisplayLink displays are black after Mesa update To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1931547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920836] Re: Show Extended Security Maintenence status
** Changed in: software-properties (Ubuntu) Importance: Undecided => High ** Changed in: software-properties (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838334] Re: aeskeyfind problem with constraints results
** Changed in: aeskeyfind (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838334 Title: aeskeyfind problem with constraints results To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aeskeyfind/+bug/1838334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929533] Re: [needs-packaging] jpegqs (jpeg-quantsmooth)
** Changed in: debian Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929533 Title: [needs-packaging] jpegqs (jpeg-quantsmooth) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1929533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931649] Re: alsa: the output volume can't be adjusted on the Lenovo machines with Bass speaker
** Description changed: - this bug is for tracking purpose. + [Impact] + Users could adjust the speaker's output volume from UI, but the sound + doesn't change with the user's adjustment. + + [Fix] + Backport 2 upstream patches, these patches are merged to 5.8.0-generic + with stable update, but not in 5.6-oem yet. + + [Test] + run amixer contents | grep DAC1, we could see the DAC1 mixer control + is found, adjust the speaker's volume from gnome-sound-setting, then + play some sound, we could hear the sound's volume is changed with our + adjustment. + + + [Where problems could occur] + This could possibly introduce the speaker output doesn't work anymore + on lenovo machines with dual speakers, but this posibility is very low, + I have tested the patches on 3 different lenovo machines with dual + speakers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931649 Title: alsa: the output volume can't be adjusted on the Lenovo machines with Bass speaker To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1931649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931540] Re: Latest 3.20210608.0ubuntu0.21.04.1 update in hirsute makes iwlwifi restarting in a loop
I have forwarded this report upstream to Intel https://github.com/intel /Intel-Linux-Processor-Microcode-Data-Files/issues/56 ** Bug watch added: github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues #56 https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/56 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931540 Title: Latest 3.20210608.0ubuntu0.21.04.1 update in hirsute makes iwlwifi restarting in a loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1931540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931649] [NEW] alsa: the output volume can't be adjusted on the Lenovo machines with Bass speaker
Public bug reported: this bug is for tracking purpose. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-oem-5.6 (Ubuntu) Importance: High Assignee: Hui Wang (hui.wang) Status: Triaged ** Affects: linux-oem-5.6 (Ubuntu Focal) Importance: High Status: Triaged ** Tags: oem-priority originate-from-1931433 sutton ** Package changed: linux (Ubuntu) => linux-oem-5.6 (Ubuntu) ** Changed in: linux-oem-5.6 (Ubuntu) Importance: Undecided => High ** Changed in: linux-oem-5.6 (Ubuntu) Status: New => Triaged ** Also affects: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: New => Triaged ** Tags added: oem-priority originate-from-1931433 sutton -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931649 Title: alsa: the output volume can't be adjusted on the Lenovo machines with Bass speaker To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1931649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931618] Re: openscap 1.3.4 rebase+merge from sid
The debdiff appears to be missing a lot of changes from 1.2.17 in impish to 1.3.4 - it should be against the current version in impish, not the 1.3.4-1 version in Debian. Also the debian/changelog then should include entries for the intervening releases in Ubuntu. See attached for a version of this merge that I did myself which should hopefully give you more of an idea of what is normally expected. ** Patch added: "openscap_1.3.4-1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/openscap/+bug/1931618/+attachment/5503900/+files/openscap_1.3.4-1ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931618 Title: openscap 1.3.4 rebase+merge from sid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openscap/+bug/1931618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921632] Re: build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later
@Herczeg, What is your machine, Dell or HP? If non-audio part is broken with -20 kernel, you could file a new bug against it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921632 Title: build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
This is a terrible bug. 16.3.1 needs to be pulled from the repositories immediately. This will cause all Ussuri OpenStack deployments on Bionic to be completely down. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921632] Re: build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later
I went ahead and tested 5.11.0-19 and 5.11.0.20, neither of them works. 5.11.0-19 does not boot to GUI at all, 5.11.0-20 has no audio and touchpad broken. I'm currently on a self-built 5.11.0-17 where the only change is the two soundwire configs and this works amazing. What has happened to -19 and -20 kernels besides the config change? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921632 Title: build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931637] Re: Groovy update: upstream stable patchset 2021-06-10
** Changed in: linux (Ubuntu Groovy) Status: In Progress => 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/1931637 Title: Groovy update: upstream stable patchset 2021-06-10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910200] Re: aws: network performance regression due to initial TCP receive buffer size change
** Changed in: linux-aws (Ubuntu Groovy) 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/1910200 Title: aws: network performance regression due to initial TCP receive buffer size change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1910200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832021] Re: Checksum drop of metadata traffic on isolated networks with DPDK
** Description changed: [Impact] When an isolated network using provider networks for tenants (meaning without virtual routers: DVR or network node), metadata access occurs in the qdhcp ip netns rather than the qrouter netns. The following options are set in the dhcp_agent.ini file: force_metadata = True enable_isolated_metadata = True VMs on the provider tenant network are unable to access metadata as packets are dropped due to checksum. [Test Plan] 1. Create an OpenStack deployment with DPDK options enabled and 'enable- local-dhcp-and-metadata: true' in neutron-openvswitch. A sample, simple 3 node bundle can be found here[1]. 2. Create an external flat network and subnet: openstack network show dpdk_net || \ - openstack network create --provider-network-type flat \ ---provider-physical-network physnet1 dpdk_net \ ---external + openstack network create --provider-network-type flat \ + --provider-physical-network physnet1 dpdk_net \ + --external openstack subnet show dpdk_net || \ - openstack subnet create --allocation-pool start=10.230.58.100,end=10.230.58.200 \ - --subnet-range 10.230.56.0/21 --dhcp --gateway 10.230.56.1 \ - --dns-nameserver 10.230.56.2 \ - --ip-version 4 --network dpdk_net dpdk_subnet + openstack subnet create --allocation-pool start=10.230.58.100,end=10.230.58.200 \ + --subnet-range 10.230.56.0/21 --dhcp --gateway 10.230.56.1 \ + --dns-nameserver 10.230.56.2 \ + --ip-version 4 --network dpdk_net dpdk_subnet - - 3. Create an instance attached to that network. The instance must have a flavor that uses huge pages. + 3. Create an instance attached to that network. The instance must have a + flavor that uses huge pages. openstack flavor create --ram 8192 --disk 50 --vcpus 4 m1.dpdk openstack flavor set m1.dpdk --property hw:mem_page_size=large openstack server create --wait --image xenial --flavor m1.dpdk --key- name testkey --network dpdk_net i1 4. Log into the instance host and check the instance console. The instance will hang into the boot and show the following message: 2020-11-20 09:43:26,790 - openstack.py[DEBUG]: Failed reading optional path http://169.254.169.254/openstack/2015-10-15/user_data due to: HTTPConnectionPool(host='169.254.169.254', port=80): Read timed out. (read timeout=10.0) 5. Apply the fix in all computes, restart the DHCP agents in all computes and create the instance again. 6. No errors should be shown and the instance quickly boots. - [Where problems could occur] * This change is only touched if datapath_type and ovs_use_veth. Those settings are mostly used for DPDK environments. The core of the fix is to toggle off checksum offload done by the DHCP namespace interfaces. This will have the drawback of adding some overhead on the packet processing for DHCP traffic but given DHCP does not demand too much data, this should be a minor proble. * Future changes on the syntax of the ethtool command could cause regressions - [Other Info] - * None + * None + QUEENS VERIFICATION DONE + + 1 - Followed through the process above and confirmed that after installing the package the problems are solved. + 2 - Testing output can be seen here: https://paste.ubuntu.com/p/mM22nBsSG2/ + [1] https://gist.github.com/sombrafam/e0741138773e444960eb4aeace6e3e79 ** Tags removed: verification-needed-bionic ** Tags added: verification-bionic-done ** Description changed: [Impact] When an isolated network using provider networks for tenants (meaning without virtual routers: DVR or network node), metadata access occurs in the qdhcp ip netns rather than the qrouter netns. The following options are set in the dhcp_agent.ini file: force_metadata = True enable_isolated_metadata = True VMs on the provider tenant network are unable to access metadata as packets are dropped due to checksum. [Test Plan] 1. Create an OpenStack deployment with DPDK options enabled and 'enable- local-dhcp-and-metadata: true' in neutron-openvswitch. A sample, simple 3 node bundle can be found here[1]. 2. Create an external flat network and subnet: openstack network show dpdk_net || \ openstack network create --provider-network-type flat \ --provider-physical-network physnet1 dpdk_net \ --external openstack subnet show dpdk_net || \ openstack subnet create --allocation-pool start=10.230.58.100,end=10.230.58.200 \ --subnet-range 10.230.56.0/21 --dhcp --gateway 10.230.56.1 \ --dns-nameserver
[Bug 1931171] Re: kernel_lockdown(7) describes removed SysRq for lifting lockdown
This bug was fixed in the package manpages - 5.10-1ubuntu1 --- manpages (5.10-1ubuntu1) impish; urgency=medium * kernel_lockdown.7: Remove description of unsupported lockdown lift mechanism via SysRq. LP: #1931171. -- dann frazier Thu, 10 Jun 2021 13:18:47 -0600 ** Changed in: manpages (Ubuntu Impish) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/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 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
Great, thanks for giving it a try. I will release it now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
yay ! I tried it on to systems and it seems to work! Thank you! From: boun...@canonical.com on behalf of Marc Deslauriers <1931...@bugs.launchpad.net> Sent: Thursday, June 10, 2021 2:56 PM To: Kleinhesselink, Dirk Subject: [Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 OK, I believe I've found the cause of the second regression. I have uploaded an update to the security team PPA for building here: https://urldefense.com/v3/__https://launchpad.net/*ubuntu-security-__;fg!!LQC6Cpwp!-xxo6MC08dOrzpLvj2yja3mS7p4Q2SNViwL0cG4Nmp6WbE4_XjuAImUYstcaQbyuYgDggAS0$ proposed/+archive/ubuntu/ppa/+packages The actual binary package is located here: https://urldefense.com/v3/__https://launchpad.net/*ubuntu-security-proposed/*archive/ubuntu/ppa/*build/21682985/*files/rpcbind_0.2.3-0.6ubuntu0.18.04.4_amd64.deb__;fisrKw!!LQC6Cpwp!-xxo6MC08dOrzpLvj2yja3mS7p4Q2SNViwL0cG4Nmp6WbE4_XjuAImUYstcaQbyuYgZhH3Xf$ Since I can't seem to reproduce this second regression easily, could someone please check if that binary package solves the issue in their environment? If so, I'll push it as a second regression update. Thanks, and sorry for these issues. -- You received this bug notification because you are subscribed to a duplicate bug report (1931616). https://urldefense.com/v3/__https://bugs.launchpad.net/bugs/1931507__;!!LQC6Cpwp!-xxo6MC08dOrzpLvj2yja3mS7p4Q2SNViwL0cG4Nmp6WbE4_XjuAImUYstcaQbyuYqe3WlTE$ Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 Status in rpcbind package in Ubuntu: Fix Released Bug description: Failure with new rpcbind version. Reverting to the previous version fixes it. Bad: rpcbind_0.2.3-0.6ubuntu0.18.04.2_amd64.deb Good: rpcbind_0.2.3-0.6ubuntu0.18.04.1_amd64.deb $ journalctl -u rpcbind.service Jun 09 23:41:00 MYSYSTEM systemd[1]: Started RPC bind portmap service. Jun 09 23:41:30 MYSYSTEM rpcbind[25504]: rpcbind: pmap_prot.c:50: xdr_pmap: Assertion `regs != NULL' failed. Jun 09 23:41:30 MYSYSTEM systemd[1]: rpcbind.service: Main process exited, code=killed, status=6/ABRT Jun 09 23:41:30 MYSYSTEM systemd[1]: rpcbind.service: Failed with result 'signal'. Jun 09 23:41:30 MYSYSTEM systemd[1]: rpcbind.service: Service hold-off time over, scheduling restart. Jun 09 23:41:30 MYSYSTEM systemd[1]: rpcbind.service: Scheduled restart job, restart counter is at 477. Jun 09 23:41:30 MYSYSTEM systemd[1]: Stopped RPC bind portmap service. $ lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 $ uname -a Linux MYSYSTEM 5.4.0-1044-gcp #47~18.04.2-Ubuntu SMP Mon May 17 03:48:15 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux $ apt-cache policy rpcbind rpcbind: Installed: 0.2.3-0.6ubuntu0.18.04.1 Candidate: 0.2.3-0.6ubuntu0.18.04.2 Version table: 0.2.3-0.6ubuntu0.18.04.2 500 500 https://urldefense.com/v3/__http://us-east1.gce.archive.ubuntu.com/ubuntu__;!!LQC6Cpwp!-xxo6MC08dOrzpLvj2yja3mS7p4Q2SNViwL0cG4Nmp6WbE4_XjuAImUYstcaQbyuYli0XcDn$ bionic-updates/main amd64 Packages 500 https://urldefense.com/v3/__http://security.ubuntu.com/ubuntu__;!!LQC6Cpwp!-xxo6MC08dOrzpLvj2yja3mS7p4Q2SNViwL0cG4Nmp6WbE4_XjuAImUYstcaQbyuYuqsuQs7$ bionic-security/main amd64 Packages *** 0.2.3-0.6ubuntu0.18.04.1 100 100 /var/lib/dpkg/status 0.2.3-0.6 500 500 https://urldefense.com/v3/__http://us-east1.gce.archive.ubuntu.com/ubuntu__;!!LQC6Cpwp!-xxo6MC08dOrzpLvj2yja3mS7p4Q2SNViwL0cG4Nmp6WbE4_XjuAImUYstcaQbyuYli0XcDn$ bionic/main amd64 Packages To manage notifications about this bug go to: https://urldefense.com/v3/__https://bugs.launchpad.net/ubuntu/*source/rpcbind/*bug/1931507/*subscriptions__;Kysr!!LQC6Cpwp!-xxo6MC08dOrzpLvj2yja3mS7p4Q2SNViwL0cG4Nmp6WbE4_XjuAImUYstcaQbyuYv2KmZIr$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
NIS (ypbind, ypserv, yppasswdd, ypxferd) and NFS (nfslock, mountd, nfs) From: boun...@canonical.com on behalf of Marc Deslauriers <1931...@bugs.launchpad.net> Sent: Thursday, June 10, 2021 2:29 PM To: Kleinhesselink, Dirk Subject: [Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 I'm investigating the second crash. What services are being run on the servers that are still crashing after the update? -- You received this bug notification because you are subscribed to a duplicate bug report (1931616). https://urldefense.com/v3/__https://bugs.launchpad.net/bugs/1931507__;!!LQC6Cpwp!7_Th_o6sv4zq6PxvRe43NhwF6O9SK_Ihk0cpZJQ3ORRIEAcZcoJZ0F5MSMaAnjerNxtnX_7d$ Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 Status in rpcbind package in Ubuntu: Fix Released Bug description: Failure with new rpcbind version. Reverting to the previous version fixes it. Bad: rpcbind_0.2.3-0.6ubuntu0.18.04.2_amd64.deb Good: rpcbind_0.2.3-0.6ubuntu0.18.04.1_amd64.deb $ journalctl -u rpcbind.service Jun 09 23:41:00 MYSYSTEM systemd[1]: Started RPC bind portmap service. Jun 09 23:41:30 MYSYSTEM rpcbind[25504]: rpcbind: pmap_prot.c:50: xdr_pmap: Assertion `regs != NULL' failed. Jun 09 23:41:30 MYSYSTEM systemd[1]: rpcbind.service: Main process exited, code=killed, status=6/ABRT Jun 09 23:41:30 MYSYSTEM systemd[1]: rpcbind.service: Failed with result 'signal'. Jun 09 23:41:30 MYSYSTEM systemd[1]: rpcbind.service: Service hold-off time over, scheduling restart. Jun 09 23:41:30 MYSYSTEM systemd[1]: rpcbind.service: Scheduled restart job, restart counter is at 477. Jun 09 23:41:30 MYSYSTEM systemd[1]: Stopped RPC bind portmap service. $ lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 $ uname -a Linux MYSYSTEM 5.4.0-1044-gcp #47~18.04.2-Ubuntu SMP Mon May 17 03:48:15 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux $ apt-cache policy rpcbind rpcbind: Installed: 0.2.3-0.6ubuntu0.18.04.1 Candidate: 0.2.3-0.6ubuntu0.18.04.2 Version table: 0.2.3-0.6ubuntu0.18.04.2 500 500 https://urldefense.com/v3/__http://us-east1.gce.archive.ubuntu.com/ubuntu__;!!LQC6Cpwp!7_Th_o6sv4zq6PxvRe43NhwF6O9SK_Ihk0cpZJQ3ORRIEAcZcoJZ0F5MSMaAnjerN4XdIAoG$ bionic-updates/main amd64 Packages 500 https://urldefense.com/v3/__http://security.ubuntu.com/ubuntu__;!!LQC6Cpwp!7_Th_o6sv4zq6PxvRe43NhwF6O9SK_Ihk0cpZJQ3ORRIEAcZcoJZ0F5MSMaAnjerN4pvi876$ bionic-security/main amd64 Packages *** 0.2.3-0.6ubuntu0.18.04.1 100 100 /var/lib/dpkg/status 0.2.3-0.6 500 500 https://urldefense.com/v3/__http://us-east1.gce.archive.ubuntu.com/ubuntu__;!!LQC6Cpwp!7_Th_o6sv4zq6PxvRe43NhwF6O9SK_Ihk0cpZJQ3ORRIEAcZcoJZ0F5MSMaAnjerN4XdIAoG$ bionic/main amd64 Packages To manage notifications about this bug go to: https://urldefense.com/v3/__https://bugs.launchpad.net/ubuntu/*source/rpcbind/*bug/1931507/*subscriptions__;Kysr!!LQC6Cpwp!7_Th_o6sv4zq6PxvRe43NhwF6O9SK_Ihk0cpZJQ3ORRIEAcZcoJZ0F5MSMaAnjerNx3YKEEC$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
OK, I believe I've found the cause of the second regression. I have uploaded an update to the security team PPA for building here: https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa/+packages The actual binary package is located here: https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/21682985/+files/rpcbind_0.2.3-0.6ubuntu0.18.04.4_amd64.deb Since I can't seem to reproduce this second regression easily, could someone please check if that binary package solves the issue in their environment? If so, I'll push it as a second regression update. Thanks, and sorry for these issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
Besides the standard system services Related to rpcbind * nfs-kernel-server Not related to rpcbind * nagios-nrpe-server * bacula-fd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931637] Re: Groovy update: upstream stable patchset 2021-06-10
** Changed in: linux (Ubuntu Groovy)
Status: New => In Progress
** Changed in: linux (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** 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:
+ upstream stable patchset 2021-06-10
+ from git://git.kernel.org/
-upstream stable patchset 2021-06-10
-from git://git.kernel.org/
+ KEYS: trusted: Fix memory leak on object td
+ tpm: fix error return code in tpm2_get_cc_attrs_tbl()
+ tpm, tpm_tis: Extend locality handling to TPM2 in tpm_tis_gen_interrupt()
+ tpm, tpm_tis: Reserve locality in tpm_tis_resume()
+ KVM: x86/mmu: Remove the defunct update_pte() paging hook
+ PM: runtime: Fix unpaired parent child_count for force_resume
+ kvm: Cap halt polling at kvm->max_halt_poll_ns
+ ath11k: fix thermal temperature read
+ fs: dlm: fix debugfs dump
+ tipc: convert dest node's address to network order
+ ASoC: Intel: bytcr_rt5640: Enable jack-detect support on Asus T100TAF
+ net: stmmac: Set FIFO sizes for ipq806x
+ ASoC: rsnd: core: Check convert rate in rsnd_hw_params
+ Bluetooth: Fix incorrect status handling in LE PHY UPDATE event
+ i2c: bail out early when RDWR parameters are wrong
+ ALSA: hdsp: don't disable if not enabled
+ ALSA: hdspm: don't disable if not enabled
+ ALSA: rme9652: don't disable if not enabled
+ ALSA: bebob: enable to deliver MIDI messages for multiple ports
+ Bluetooth: Set CONF_NOT_COMPLETE as l2cap_chan default
+ Bluetooth: initialize skb_queue_head at l2cap_chan_create()
+ net/sched: cls_flower: use ntohs for struct flow_dissector_key_ports
+ net: bridge: when suppression is enabled exclude RARP packets
+ Bluetooth: check for zapped sk before connecting
+ powerpc/32: Statically initialise first emergency context
+ net: hns3: remediate a potential overflow risk of bd_num_list
+ ip6_vti: proper dev_{hold|put} in ndo_[un]init methods
+ ASoC: Intel: bytcr_rt5640: Add quirk for the Chuwi Hi8 tablet
+ ice: handle increasing Tx or Rx ring sizes
+ Bluetooth: btusb: Enable quirk boolean flag for Mediatek Chip.
+ i2c: Add I2C_AQ_NO_REP_START adapter quirk
+ MIPS: Loongson64: Use _CACHE_UNCACHED instead of _CACHE_UNCACHED_ACCELERATED
+ coresight: Do not scan for graph if none is present
+ IB/hfi1: Correct oversized ring allocation
+ mac80211: clear the beacon's CRC after channel switch
+ pinctrl: samsung: use 'int' for register masks in Exynos
+ rtw88: 8822c: add LC calibration for RTL8822C
+ mt76: mt7615: support loading EEPROM for MT7613BE
+ mt76: mt76x0: disable GTK offloading
+ mt76: mt7915: fix txpower init for TSSI off chips
+ virtiofs: fix userns
+ cuse: prevent clone
+ iwlwifi: pcie: make cfg vs. trans_cfg more robust
+ powerpc/mm: Add cond_resched() while removing hpte mappings
+ ASoC: rsnd: call rsnd_ssi_master_clk_start() from rsnd_ssi_init()
+ Revert "iommu/amd: Fix performance counter initialization"
+ iommu/amd: Remove performance counter pre-initialization test
+ drm/amd/display: Force vsync flip when reconfiguring MPCC
+ selftests: Set CC to clang in lib.mk if LLVM is set
+ kconfig: nconf: stop endless search loops
+ ALSA: hda/realtek: Add quirk for Lenovo Ideapad S740
+ ASoC: Intel: sof_sdw: add quirk for new ADL-P Rvp
+ ALSA: hda/hdmi: fix race in handling acomp ELD notification at resume
+ sctp: Fix out-of-bounds warning in sctp_process_asconf_param()
+ flow_dissector: Fix out-of-bounds warning in __skb_flow_bpf_to_target()
+ powerpc/smp: Set numa node before updating mask
+ ASoC: rt286: Generalize support for ALC3263 codec
+ ethtool: ioctl: Fix out-of-bounds warning in store_link_ksettings_for_user()
+ net: sched: tapr: prevent cycle_time == 0 in parse_taprio_schedule
+ samples/bpf: Fix broken tracex1 due to kprobe argument change
+ powerpc/pseries: Stop calling printk in rtas_stop_self()
+ drm/amd/display: fixed divide by zero kernel crash during dsc enablement
+ drm/amd/display: add handling for hdcp2 rx id list validation
+ drm/amdgpu: Add mem
[Bug 1931506] Re: Display wakes up after locking screen (backlight on, black screen)
Probably AMDGPU related after som research. Maybe the wrong place then? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931506 Title: Display wakes up after locking screen (backlight on, black screen) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1931506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
I'm investigating the second crash. What services are being run on the servers that are still crashing after the update? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
I posted this on the NVIDIA forums, but thought it might be helpful to cross-post here. --- I just tried the 460 server driver solution. This did not work for me and I still have the display port bug. I have an AMD 3800X, 64 gb ram, rtx 2080 super, fresh install of Ubuntu 20.04 kernel 5.8.0-55, with 3 identical 4K monitors, (1 on HDMI, 2 on DP). The opensource driver continues to work just fine, but we need CUDA for our science to continue. Here are the outputs from nvidia-smi, uname -r, and xrandr. Note that all monitors should have 4K options. ''' (base) x@x:~$ nvidia-smi Wed Jun 9 17:18:16 2021 +-+ | NVIDIA-SMI 460.73.01Driver Version: 460.73.01CUDA Version: 11.2 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 GeForce RTX 208... Off | :0E:00.0 On | N/A | | 0% 45CP517W / 250W |702MiB / 7981MiB | 1% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 918 G /usr/lib/xorg/Xorg198MiB | |0 N/A N/A 1466 G /usr/lib/xorg/Xorg349MiB | |0 N/A N/A 1603 G /usr/bin/gnome-shell 137MiB | |0 N/A N/A 2014 G gnome-control-center2MiB | +-+ (base) x@x:~$ uname -r 5.8.0-55-generic (base) x@x:~$ (base) x@x:~$ xrandr Screen 0: minimum 8 x 8, current 7680 x 2160, maximum 32767 x 32767 DP-0 disconnected (normal left inverted right x axis y axis) DP-1 connected 1920x1080+3840+0 (normal left inverted right x axis y axis) 1110mm x 620mm 1920x1080 60.00 + 59.9429.97* 23.98 1680x1050 59.95 1440x900 59.89 1360x768 60.02 1280x1024 75.0260.02 1280x960 60.00 1280x800 59.81 1280x720 60.0059.9429.9723.98 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.32 720x480 59.94 640x480 75.0072.8159.9459.93 HDMI-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 800mm x 450mm 3840x2160 30.00*+ 59.9429.9723.9823.98 4096x2160 59.9429.9724.0023.98 1920x1080 60.0059.9429.9723.98 1680x1050 59.95 1440x900 59.89 1360x768 60.02 1280x1024 75.0260.02 1280x960 60.00 1280x800 59.81 1280x720 60.0059.9429.9723.98 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.32 720x480 59.94 640x480 75.0072.8159.9459.93 DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 disconnected (normal left inverted right x axis y axis) DP-5 connected 1920x1080+5760+0 (normal left inverted right x axis y axis) 800mm x 450mm 1920x1080 60.00*+ 59.9429.9723.98 1680x1050 59.95 1440x900 59.89 1360x768 60.02 1280x1024 75.0260.02 1280x960 60.00 1280x800 59.81 1280x720 60.0059.9429.9723.98 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.32 720x480 59.94 640x480 75.0072.8159.9459.93 USB-C-0 disconnected (normal left inverted right x axis y axis) ''' I tried the nvidia-driver-460-server solution. Sadly it did not work for me. The display port connected monitor resolutions are not correct with the 460.73.01 driver version showing 1080p when they should be 4K. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930733 Title: Kernel oops with the 460.80 and 465.27
[Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
Just installed the upgrade and same as Dirk Kleinhesselink it doesn't work. rpcbind keeps crashing apt-cache policy rpcbind rpcbind: Installiert: 0.2.3-0.6ubuntu0.18.04.3 Installationskandidat: 0.2.3-0.6ubuntu0.18.04.3 Versionstabelle: *** 0.2.3-0.6ubuntu0.18.04.3 500 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.2.3-0.6 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages Jun 10 23:03:09 mysystem rpcbind[12674]: free(): invalid pointer Jun 10 23:03:09 mysystem systemd[1]: rpcbind.service: Main process exited, code=dumped, status=6/ABRT Jun 10 23:03:09 mysystem systemd[1]: rpcbind.service: Failed with result 'core-dump'. Jun 10 23:03:09 mysystem systemd[1]: rpcbind.service: Service hold-off time over, scheduling restart. Jun 10 23:03:09 mysystem systemd[1]: rpcbind.service: Scheduled restart job, restart counter is at 17. Jun 10 23:03:09 mysystem systemd[1]: Stopped RPC bind portmap service. Jun 10 23:03:09 mysystem systemd[1]: Starting RPC bind portmap service... Jun 10 23:03:09 mysystem systemd[1]: Started RPC bind portmap service. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929533] Re: [needs-packaging] jpegqs (jpeg-quantsmooth)
** Bug watch added: Debian Bug tracker #989697 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989697 ** Also affects: debian via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989697 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/1929533 Title: [needs-packaging] jpegqs (jpeg-quantsmooth) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1929533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931475] Re: Ubuntu only stable in safe graphics mode
So what happens when you use i915.alpha_support=1 without nomodeset? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931475 Title: Ubuntu only stable in safe graphics mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
Marc, I verified that the new package works on all our systems. Thank you so much for the prompt solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931637] [NEW] Groovy update: upstream stable patchset 2021-06-10
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: upstream stable patchset 2021-06-10 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Groovy) 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/1931637 Title: Groovy update: upstream stable patchset 2021-06-10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929870] Re: AMD desktop often fails to resume from deep suspend
The magic key doesn't work, the keyboard appears to not function at all when this happens. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929870 Title: AMD desktop often fails to resume from deep suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
does it work, though. I think I just found it and installed/upgraded one of my systems and it's still aborting/crashing: Jun 10 13:41:28 rpcbind[9933]: free(): invalid pointer Jun 10 13:41:28 systemd[1]: rpcbind.service: Main process exited, code=dumped, status=6/ABRT Jun 10 13:41:28 systemd[1]: rpcbind.service: Failed with result 'core-dump'. Jun 10 13:41:28 systemd[1]: rpcbind.service: Service hold-off time over, scheduling restart. Jun 10 13:41:28 systemd[1]: rpcbind.service: Scheduled restart job, restart counter is at 9. # apt policy rpcbind rpcbind: Installed: 0.2.3-0.6ubuntu0.18.04.3 Candidate: 0.2.3-0.6ubuntu0.18.04.3 Version table: *** 0.2.3-0.6ubuntu0.18.04.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 0.2.3-0.6 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages From: boun...@canonical.com on behalf of Nate Collins <1931...@bugs.launchpad.net> Sent: Thursday, June 10, 2021 1:29 PM To: Kleinhesselink, Dirk Subject: [Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 I was able to pull the new version just now. -- You received this bug notification because you are subscribed to a duplicate bug report (1931616). https://urldefense.com/v3/__https://bugs.launchpad.net/bugs/1931507__;!!LQC6Cpwp!7admk8Py1J1naChWxy8CYTPkbtJq38T_3H3yyEhs0jgqmaE5ZtdJxCMgEg8oeO1MWFFuc1SX$ Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 Status in rpcbind package in Ubuntu: Fix Released Bug description: Failure with new rpcbind version. Reverting to the previous version fixes it. Bad: rpcbind_0.2.3-0.6ubuntu0.18.04.2_amd64.deb Good: rpcbind_0.2.3-0.6ubuntu0.18.04.1_amd64.deb $ journalctl -u rpcbind.service Jun 09 23:41:00 MYSYSTEM systemd[1]: Started RPC bind portmap service. Jun 09 23:41:30 MYSYSTEM rpcbind[25504]: rpcbind: pmap_prot.c:50: xdr_pmap: Assertion `regs != NULL' failed. Jun 09 23:41:30 MYSYSTEM systemd[1]: rpcbind.service: Main process exited, code=killed, status=6/ABRT Jun 09 23:41:30 MYSYSTEM systemd[1]: rpcbind.service: Failed with result 'signal'. Jun 09 23:41:30 MYSYSTEM systemd[1]: rpcbind.service: Service hold-off time over, scheduling restart. Jun 09 23:41:30 MYSYSTEM systemd[1]: rpcbind.service: Scheduled restart job, restart counter is at 477. Jun 09 23:41:30 MYSYSTEM systemd[1]: Stopped RPC bind portmap service. $ lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 $ uname -a Linux MYSYSTEM 5.4.0-1044-gcp #47~18.04.2-Ubuntu SMP Mon May 17 03:48:15 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux $ apt-cache policy rpcbind rpcbind: Installed: 0.2.3-0.6ubuntu0.18.04.1 Candidate: 0.2.3-0.6ubuntu0.18.04.2 Version table: 0.2.3-0.6ubuntu0.18.04.2 500 500 https://urldefense.com/v3/__http://us-east1.gce.archive.ubuntu.com/ubuntu__;!!LQC6Cpwp!7admk8Py1J1naChWxy8CYTPkbtJq38T_3H3yyEhs0jgqmaE5ZtdJxCMgEg8oeO1MWKNVOvR7$ bionic-updates/main amd64 Packages 500 https://urldefense.com/v3/__http://security.ubuntu.com/ubuntu__;!!LQC6Cpwp!7admk8Py1J1naChWxy8CYTPkbtJq38T_3H3yyEhs0jgqmaE5ZtdJxCMgEg8oeO1MWH7bgmEN$ bionic-security/main amd64 Packages *** 0.2.3-0.6ubuntu0.18.04.1 100 100 /var/lib/dpkg/status 0.2.3-0.6 500 500 https://urldefense.com/v3/__http://us-east1.gce.archive.ubuntu.com/ubuntu__;!!LQC6Cpwp!7admk8Py1J1naChWxy8CYTPkbtJq38T_3H3yyEhs0jgqmaE5ZtdJxCMgEg8oeO1MWKNVOvR7$ bionic/main amd64 Packages To manage notifications about this bug go to: https://urldefense.com/v3/__https://bugs.launchpad.net/ubuntu/*source/rpcbind/*bug/1931507/*subscriptions__;Kysr!!LQC6Cpwp!7admk8Py1J1naChWxy8CYTPkbtJq38T_3H3yyEhs0jgqmaE5ZtdJxCMgEg8oeO1MWAS6jv2V$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931387] Re: Ubuntu UI screen image freezes randomly during usage after fresh 21.04 install, suspecting Wayland
*** This bug is a duplicate of bug 1497593 *** https://bugs.launchpad.net/bugs/1497593 Thanks a lot for looking into this Daniel! I'll follow the duplicate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931387 Title: Ubuntu UI screen image freezes randomly during usage after fresh 21.04 install, suspecting Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1931387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931612] Re: Print dialog box shows same printer twice
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1931612/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931612 Title: Print dialog box shows same printer twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1931612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931618] Re: openscap 1.3.4 rebase+merge from sid
The attachment "rev1 rebase debdiff over sid" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931618 Title: openscap 1.3.4 rebase+merge from sid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openscap/+bug/1931618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
I was able to pull the new version just now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931522] Re: Radeon 7 - [drm] perform_link_training_with_retries: Link training attempt failed
Looks like upgrading to the newest mainline stable(?) kernel 5.12.9-051209-generic from here https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.12.9/ with the proper associated headers made an improvement. Switching TTY's and back to the active gnome session the second display stays awake. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931522 Title: Radeon 7 - [drm] perform_link_training_with_retries: Link training attempt failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931574] Re: Lost network connection, seems like an older kernel bug
https://wiki.archlinux.org/title/Dell_XPS_13_(9360)#Ethernet_repeatedly_disconnects /reconnects_with_Dell_USB-C_adapter_(DA200) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931574 Title: Lost network connection, seems like an older kernel bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 184547]
Missing logo and can't zoom when i try to goto my page https://factocert.com/qatar/iso-certification-in-qatar/ it's not showing properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/184547 Title: epiphany-gecko crashed with SIGSEGV while resizing fonts with Ctrl+MouseWheel To manage notifications about this bug go to: https://bugs.launchpad.net/epiphany-browser/+bug/184547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930275] Re: [nvidia] System does not wake up after suspend
Since the issue has appeared again on Ubuntu 21.04. Please see attached logs from previous boot. ** Attachment added: "Previous boot logs 06-10-2021" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1930275/+attachment/5503893/+files/prevboot.txt.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930275 Title: [nvidia] System does not wake up after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
It's still in the process of being copied over from launchpad to the web servers. It should be done soon. In the meantime, here's a direct link to the binary package: https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/21682528/+files/rpcbind_0.2.3-0.6ubuntu0.18.04.3_amd64.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927491] Re: sru cloud-init (21.1-19 to 21.2-3) Bionic, Focal, Groovy, and Hirsute
This bug was fixed in the package cloud-init - 21.2-3-g899bfaa9-0ubuntu2~20.10.1 --- cloud-init (21.2-3-g899bfaa9-0ubuntu2~20.10.1) groovy; urgency=medium * d/cloud-init.templates: Add Vultr datasource support * drop the following cherry-picks now included: + cpick-83f6bbfb-Fix-unpickle-for-source-paths-missing-run_dir-863 + cpick-d132356c-fix-error-on-upgrade-caused-by-new-vendordata2 * New upstream snapshot. (LP: #1927491) - Update test characters in substitution unit test (#893) - cc_disk_setup.py: remove UDEVADM_CMD definition as not used (#886) [dermotbradley] - Add AlmaLinux OS support (#872) [Andrew Lukoshko] - Release 21.2 (#890) - Add \r\n check for SSH keys in Azure (#889) - Revert "Add support to resize rootfs if using LVM (#721)" (#887) - Add Vultaire as contributor (#881) [Paul Goins] - Azure: adding support for consuming userdata from IMDS (#884) [Anh Vo] - test_upgrade: modify test_upgrade_package to run for more sources (#883) - Fix chef module run failure when chef_license is set (#868) [Ben Hughes] - Azure: Retry net metadata during nic attach for non-timeout errs (#878) [aswinrajamannar] - Azure: Retrieve username and hostname from IMDS (#865) [Thomas Stringer] - Azure: eject the provisioning iso before reporting ready (#861) [Anh Vo] - Use `partprobe` to re-read partition table if available (#856) [Nicolas Bock] - fix error on upgrade caused by new vendordata2 attributes (#869) - add prefer_fqdn_over_hostname config option (#859) [hamalq] - Emit dots on travis to avoid timeout (#867) - doc: Replace remaining references to user-scripts as a config module (#866) [Ryan Harper] - azure: Removing ability to invoke walinuxagent (#799) [Anh Vo] - Add Vultr support (#827) [David Dymko] - Fix unpickle for source paths missing run_dir (#863) [lucasmoura] - sysconfig: use BONDING_MODULE_OPTS on SUSE (#831) [Jens Sandmann] - bringup_static_routes: fix gateway check (#850) [Petr Fedchenkov] - add hamalq user (#860) [hamalq] - Add support to resize rootfs if using LVM (#721) [Eduardo Otubo] - Fix mis-detecting network configuration in initramfs cmdline (#844) - tools/write-ssh-key-fingerprints: do not display empty header/footer (#817) [dermotbradley] - Azure helper: Ensure Azure http handler sleeps between retries (#842) [Johnson Shi] - Fix chef apt source example (#826) [timothegenzmer] -- James Falcon Tue, 11 May 2021 12:07:28 -0500 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927491 Title: sru cloud-init (21.1-19 to 21.2-3) Bionic, Focal, Groovy, and Hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1927491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927491] Re: sru cloud-init (21.1-19 to 21.2-3) Bionic, Focal, Groovy, and Hirsute
This bug was fixed in the package cloud-init - 21.2-3-g899bfaa9-0ubuntu2~20.04.1 --- cloud-init (21.2-3-g899bfaa9-0ubuntu2~20.04.1) focal; urgency=medium * d/cloud-init.templates: Add Vultr datasource support * drop the following cherry-picks now included: + cpick-83f6bbfb-Fix-unpickle-for-source-paths-missing-run_dir-863 + cpick-d132356c-fix-error-on-upgrade-caused-by-new-vendordata2 * New upstream snapshot. (LP: #1927491) - Update test characters in substitution unit test (#893) - cc_disk_setup.py: remove UDEVADM_CMD definition as not used (#886) [dermotbradley] - Add AlmaLinux OS support (#872) [Andrew Lukoshko] - Release 21.2 (#890) - Add \r\n check for SSH keys in Azure (#889) - Revert "Add support to resize rootfs if using LVM (#721)" (#887) - Add Vultaire as contributor (#881) [Paul Goins] - Azure: adding support for consuming userdata from IMDS (#884) [Anh Vo] - test_upgrade: modify test_upgrade_package to run for more sources (#883) - Fix chef module run failure when chef_license is set (#868) [Ben Hughes] - Azure: Retry net metadata during nic attach for non-timeout errs (#878) [aswinrajamannar] - Azure: Retrieve username and hostname from IMDS (#865) [Thomas Stringer] - Azure: eject the provisioning iso before reporting ready (#861) [Anh Vo] - Use `partprobe` to re-read partition table if available (#856) [Nicolas Bock] - fix error on upgrade caused by new vendordata2 attributes (#869) - add prefer_fqdn_over_hostname config option (#859) [hamalq] - Emit dots on travis to avoid timeout (#867) - doc: Replace remaining references to user-scripts as a config module (#866) [Ryan Harper] - azure: Removing ability to invoke walinuxagent (#799) [Anh Vo] - Add Vultr support (#827) [David Dymko] - Fix unpickle for source paths missing run_dir (#863) [lucasmoura] - sysconfig: use BONDING_MODULE_OPTS on SUSE (#831) [Jens Sandmann] - bringup_static_routes: fix gateway check (#850) [Petr Fedchenkov] - add hamalq user (#860) [hamalq] - Add support to resize rootfs if using LVM (#721) [Eduardo Otubo] - Fix mis-detecting network configuration in initramfs cmdline (#844) - tools/write-ssh-key-fingerprints: do not display empty header/footer (#817) [dermotbradley] - Azure helper: Ensure Azure http handler sleeps between retries (#842) [Johnson Shi] - Fix chef apt source example (#826) [timothegenzmer] -- James Falcon Tue, 11 May 2021 12:22:24 -0500 ** Changed in: cloud-init (Ubuntu Groovy) 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/1927491 Title: sru cloud-init (21.1-19 to 21.2-3) Bionic, Focal, Groovy, and Hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1927491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927491] Re: sru cloud-init (21.1-19 to 21.2-3) Bionic, Focal, Groovy, and Hirsute
This bug was fixed in the package cloud-init - 21.2-3-g899bfaa9-0ubuntu2~18.04.1 --- cloud-init (21.2-3-g899bfaa9-0ubuntu2~18.04.1) bionic; urgency=medium * d/cloud-init.templates: Add Vultr datasource support * drop the following cherry-picks now included: + cpick-83f6bbfb-Fix-unpickle-for-source-paths-missing-run_dir-863 + cpick-d132356c-fix-error-on-upgrade-caused-by-new-vendordata2 * New upstream snapshot. (LP: #1927491) - Update test characters in substitution unit test (#893) - cc_disk_setup.py: remove UDEVADM_CMD definition as not used (#886) [dermotbradley] - Add AlmaLinux OS support (#872) [Andrew Lukoshko] - Release 21.2 (#890) - Add \r\n check for SSH keys in Azure (#889) - Revert "Add support to resize rootfs if using LVM (#721)" (#887) - Add Vultaire as contributor (#881) [Paul Goins] - Azure: adding support for consuming userdata from IMDS (#884) [Anh Vo] - test_upgrade: modify test_upgrade_package to run for more sources (#883) - Fix chef module run failure when chef_license is set (#868) [Ben Hughes] - Azure: Retry net metadata during nic attach for non-timeout errs (#878) [aswinrajamannar] - Azure: Retrieve username and hostname from IMDS (#865) [Thomas Stringer] - Azure: eject the provisioning iso before reporting ready (#861) [Anh Vo] - Use `partprobe` to re-read partition table if available (#856) [Nicolas Bock] - fix error on upgrade caused by new vendordata2 attributes (#869) - add prefer_fqdn_over_hostname config option (#859) [hamalq] - Emit dots on travis to avoid timeout (#867) - doc: Replace remaining references to user-scripts as a config module (#866) [Ryan Harper] - azure: Removing ability to invoke walinuxagent (#799) [Anh Vo] - Add Vultr support (#827) [David Dymko] - Fix unpickle for source paths missing run_dir (#863) [lucasmoura] - sysconfig: use BONDING_MODULE_OPTS on SUSE (#831) [Jens Sandmann] - bringup_static_routes: fix gateway check (#850) [Petr Fedchenkov] - add hamalq user (#860) [hamalq] - Add support to resize rootfs if using LVM (#721) [Eduardo Otubo] - Fix mis-detecting network configuration in initramfs cmdline (#844) - tools/write-ssh-key-fingerprints: do not display empty header/footer (#817) [dermotbradley] - Azure helper: Ensure Azure http handler sleeps between retries (#842) [Johnson Shi] - Fix chef apt source example (#826) [timothegenzmer] -- James Falcon Tue, 11 May 2021 12:24:46 -0500 ** Changed in: cloud-init (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/1927491 Title: sru cloud-init (21.1-19 to 21.2-3) Bionic, Focal, Groovy, and Hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1927491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927491] Re: sru cloud-init (21.1-19 to 21.2-3) Bionic, Focal, Groovy, and Hirsute
This bug was fixed in the package cloud-init - 21.2-3-g899bfaa9-0ubuntu2~21.04.1 --- cloud-init (21.2-3-g899bfaa9-0ubuntu2~21.04.1) hirsute; urgency=medium * d/cloud-init.templates: Add Vultr datasource support * drop the following cherry-picks now included: + cpick-83f6bbfb-Fix-unpickle-for-source-paths-missing-run_dir-863 + cpick-d132356c-fix-error-on-upgrade-caused-by-new-vendordata2 * New upstream snapshot. (LP: #1927491) - Update test characters in substitution unit test (#893) - cc_disk_setup.py: remove UDEVADM_CMD definition as not used (#886) [dermotbradley] - Add AlmaLinux OS support (#872) [Andrew Lukoshko] - Release 21.2 (#890) - Add \r\n check for SSH keys in Azure (#889) - Revert "Add support to resize rootfs if using LVM (#721)" (#887) - Add Vultaire as contributor (#881) [Paul Goins] - Azure: adding support for consuming userdata from IMDS (#884) [Anh Vo] - test_upgrade: modify test_upgrade_package to run for more sources (#883) - Fix chef module run failure when chef_license is set (#868) [Ben Hughes] - Azure: Retry net metadata during nic attach for non-timeout errs (#878) [aswinrajamannar] - Azure: Retrieve username and hostname from IMDS (#865) [Thomas Stringer] - Azure: eject the provisioning iso before reporting ready (#861) [Anh Vo] - Use `partprobe` to re-read partition table if available (#856) [Nicolas Bock] - fix error on upgrade caused by new vendordata2 attributes (#869) - add prefer_fqdn_over_hostname config option (#859) [hamalq] - Emit dots on travis to avoid timeout (#867) - doc: Replace remaining references to user-scripts as a config module (#866) [Ryan Harper] - azure: Removing ability to invoke walinuxagent (#799) [Anh Vo] - Add Vultr support (#827) [David Dymko] - Fix unpickle for source paths missing run_dir (#863) [lucasmoura] - sysconfig: use BONDING_MODULE_OPTS on SUSE (#831) [Jens Sandmann] - bringup_static_routes: fix gateway check (#850) [Petr Fedchenkov] - add hamalq user (#860) [hamalq] - Add support to resize rootfs if using LVM (#721) [Eduardo Otubo] - Fix mis-detecting network configuration in initramfs cmdline (#844) - tools/write-ssh-key-fingerprints: do not display empty header/footer (#817) [dermotbradley] - Azure helper: Ensure Azure http handler sleeps between retries (#842) [Johnson Shi] - Fix chef apt source example (#826) [timothegenzmer] -- James Falcon Wed, 12 May 2021 10:52:15 -0500 ** Changed in: cloud-init (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** Changed in: cloud-init (Ubuntu Bionic) 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/1927491 Title: sru cloud-init (21.1-19 to 21.2-3) Bionic, Focal, Groovy, and Hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1927491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927491] Re: sru cloud-init (21.1-19 to 21.2-3) Bionic, Focal, Groovy, and Hirsute
The verification of the Stable Release Update for cloud-init has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. ** Changed in: cloud-init (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927491 Title: sru cloud-init (21.1-19 to 21.2-3) Bionic, Focal, Groovy, and Hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1927491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931455] Re: open-iscsi fails to create nodes directory
As far as I can remember, the open-iscsi.service was not needed to run the iscsiadm command (on 18.04 and 20.04 at least). Could you share the full steps to reproduce the issue along with the errors you are getting, please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931455 Title: open-iscsi fails to create nodes directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1931455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
If you can't wait… I regain access with installing an old version apt-get install rpcbind=0.2.3-0.6 service nfs-kernel-server restart cat /etc/apt/preferences.d/rpcbind Package: rpcbind Pin: version 0.2.3-0.6 Pin-Priority: 1000 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931609] Re: gstreamer1.0-plugins-bad compilation from sources: missing cuda.h
I could not reproduce this in my Xubuntu 20.04 VM, so I believe it more of a support request than an actual bug in the package. ** Changed in: gst-plugins-bad1.0 (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+question/697484 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931609 Title: gstreamer1.0-plugins-bad compilation from sources: missing cuda.h To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1931609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931630] [NEW] Linux images for virtual machines with unset `CONFIG_MAGIC_SYSRQ` cause `10-magic-sysrq.conf` to fail
Public bug reported: *procps* ships `/etc/sysctl.d/10-magic-sysrq.conf:kernel.sysrq = 176`, which is run by `systemd-sysctl.service`. This fails on a system run with a Linux image built for virtual machines *linux-image-kvm*, which has `CONFIG_MAGIC_SYSRQ` not set. ``` $ sudo /lib/systemd/systemd-sysctl Couldn't write '176' to 'kernel/sysrq', ignoring: No such file or directory Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory Couldn't write '4194304' to 'kernel/pid_max': Invalid argument $ grep SYSRQ /boot/config-5.4.0-1009-kvm # CONFIG_MAGIC_SYSRQ is not set ``` ** Affects: procps (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/1931630 Title: Linux images for virtual machines with unset `CONFIG_MAGIC_SYSRQ` cause `10-magic-sysrq.conf` to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1931630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
Anybody see it? According to: https://launchpad.net/ubuntu/+source/rpcbind/0.2.3-0.6ubuntu0.18.04.3/+publishinghistory It has been published, but doing `apt update` doesn't show it. The: http://security.ubuntu.com/ubuntu/dists/bionic-security/main/binary-amd64/Packages.gz as of now still contains 0.2.3-0.6ubuntu0.18.04.2 package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929831] Re: cifs: On cifs_reconnect, resolve the hostname again
This bug was fixed in the package linux-azure - 5.4.0-1049.51 --- linux-azure (5.4.0-1049.51) focal; urgency=medium * focal/linux-azure: 5.4.0-1049.51 -proposed tracker (LP: #1930703) * cifs: On cifs_reconnect, resolve the hostname again (LP: #1929831) - cifs: rename reconn_inval_dfs_target() - cifs: Simplify reconnect code when dfs upcall is enabled - cifs: Avoid error pointer dereference - cifs: On cifs_reconnect, resolve the hostname again. -- Tim Gardner Thu, 03 Jun 2021 09:17:13 -0600 ** Changed in: linux-azure (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/1929831 Title: cifs: On cifs_reconnect, resolve the hostname again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929831/+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
ok thanks. On 09/06/2021 17:16, Colin Ian King wrote: > I've uploaded 2.4.6 to debian and this will sync this into Ubuntu Impish > development in the next 24-36 hours. Once that's done I'll backport this > fix to older releases of thermald. Thanks for fixing this. > -- 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 1910255] [gnutls28/focal] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed repository for focal for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository. ** Tags added: removal-candidate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910255 Title: autopkgtest fails due to an expired certificate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1910255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925985] Re: CVE-2021-22204
Hello Hugo, Thanks for the help! I've published your backport for bionic, focal, groovy, and hirsute. The changelog was a little different to be in the format that we use. About the version number, we use major numbers (like ubuntu1) when is a devel release otherwise we increment the minor number (like I did, ubuntu0.1). Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925985 Title: CVE-2021-22204 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimage-exiftool-perl/+bug/1925985/+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 Hirsute) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/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 1931621] Re: /usr/lib/update-notifier/apt_check.py:subprocess.CalledProcessError:get_distro:_get_info_from_os_release:/usr/lib/update-notifier/apt_check.py@63:get_distro:_get_output_from_lsb_rele
Looking at the code I guess raising an Exception here could be useful but it ends up preventing a flavor from using apt-check and that doesn't seem great. What would the negative consequences be of not raising and exception and having DISTRO be empty? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931621 Title: /usr/lib/update- notifier/apt_check.py:subprocess.CalledProcessError:get_distro:_get_info_from_os_release:/usr/lib /update- notifier/apt_check.py@63:get_distro:_get_output_from_lsb_release:check_output:run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1931621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931621] Re: /usr/lib/update-notifier/apt_check.py:subprocess.CalledProcessError:get_distro:_get_info_from_os_release:/usr/lib/update-notifier/apt_check.py@63:get_distro:_get_output_from_lsb_rele
We use the distro information all over the code, for example, to perform the check if a package is from a security pocket or if it is an ESM package. We also use the distro to correctly select the ESM messages we will deliver to the user -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931621 Title: /usr/lib/update- notifier/apt_check.py:subprocess.CalledProcessError:get_distro:_get_info_from_os_release:/usr/lib /update- notifier/apt_check.py@63:get_distro:_get_output_from_lsb_release:check_output:run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1931621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925985] Re: CVE-2021-22204
This bug was fixed in the package libimage-exiftool-perl - 10.80-1ubuntu0.1 --- libimage-exiftool-perl (10.80-1ubuntu0.1) bionic-security; urgency=medium * SECURITY UPDATE: Arbitrary code execution - debian/patches/CVE-2021-22204.patch: Improper neutralization of user data in the DjVu file format in ExifTool versions 7.44 and up allows arbitrary code execution when parsing the malicious image. (LP: #1925985) Thanks to William Bowling for the bug report on Launchpad. Thanks to Gregor Herrmann for backporting the patch. From debian release 12.16+dfsg-2. - CVE-2021-22204 -- hugo buddelmeijer Wed, 09 Jun 2021 20:39:41 +0200 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925985 Title: CVE-2021-22204 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimage-exiftool-perl/+bug/1925985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925985] Re: CVE-2021-22204
This bug was fixed in the package libimage-exiftool-perl - 11.88-1ubuntu0.1 --- libimage-exiftool-perl (11.88-1ubuntu0.1) focal-security; urgency=medium * SECURITY UPDATE: Arbitrary code execution - debian/patches/CVE-2021-22204.patch: Improper neutralization of user data in the DjVu file format in ExifTool versions 7.44 and up allows arbitrary code execution when parsing the malicious image. (LP: #1925985) Thanks to William Bowling for the bug report on Launchpad. Thanks to Gregor Herrmann for backporting the patch. From debian release 12.16+dfsg-2. - CVE-2021-22204 -- hugo buddelmeijer Wed, 09 Jun 2021 20:39:41 +0200 ** Changed in: libimage-exiftool-perl (Ubuntu Bionic) 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/1925985 Title: CVE-2021-22204 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimage-exiftool-perl/+bug/1925985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925985] Re: CVE-2021-22204
This bug was fixed in the package libimage-exiftool-perl - 12.05-1ubuntu0.1 --- libimage-exiftool-perl (12.05-1ubuntu0.1) groovy-security; urgency=medium * SECURITY UPDATE: Arbitrary code execution - debian/patches/CVE-2021-22204.patch: Improper neutralization of user data in the DjVu file format in ExifTool versions 7.44 and up allows arbitrary code execution when parsing the malicious image. (LP: #1925985) Thanks to William Bowling for the bug report on Launchpad. Thanks to Gregor Herrmann for backporting the patch. From debian release 12.16+dfsg-2. - CVE-2021-22204 -- hugo buddelmeijer Wed, 09 Jun 2021 20:39:41 +0200 ** Changed in: libimage-exiftool-perl (Ubuntu Focal) 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/1925985 Title: CVE-2021-22204 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimage-exiftool-perl/+bug/1925985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925985] Re: CVE-2021-22204
This bug was fixed in the package libimage-exiftool-perl - 12.16+dfsg- 1ubuntu0.1 --- libimage-exiftool-perl (12.16+dfsg-1ubuntu0.1) hirsute-security; urgency=medium * SECURITY UPDATE: Arbitrary code execution - debian/patches/CVE-2021-22204.patch: Improper neutralization of user data in the DjVu file format in ExifTool versions 7.44 and up allows arbitrary code execution when parsing the malicious image. (LP: #1925985) Thanks to William Bowling for the bug report on Launchpad. Thanks to Gregor Herrmann for backporting the patch. From debian release 12.16+dfsg-2. - CVE-2021-22204 -- hugo buddelmeijer Wed, 09 Jun 2021 20:39:41 +0200 ** Changed in: libimage-exiftool-perl (Ubuntu Hirsute) Status: New => Fix Released ** Changed in: libimage-exiftool-perl (Ubuntu Groovy) 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/1925985 Title: CVE-2021-22204 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimage-exiftool-perl/+bug/1925985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
The fix has been released, it will take a few minutes to replicate to the web servers and mirrors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
This bug was fixed in the package rpcbind - 0.2.3-0.6ubuntu0.18.04.3 --- rpcbind (0.2.3-0.6ubuntu0.18.04.3) bionic-security; urgency=medium * SECURITY REGRESSION: assertion failure (LP: #1931507) - debian/patches/CVE-2017-8779-3.patch: fixed typo in memory leak patch in src/pmap_svc.c. -- Marc Deslauriers Thu, 10 Jun 2021 14:40:54 -0400 ** Changed in: rpcbind (Ubuntu) Status: Confirmed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-8779 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
Manual download deb package: https://launchpad.net/ubuntu/+source/rpcbind/0.2.3-0.6ubuntu0.18.04.1 On the right, you can pick which architecture you need. @Marc, if you can publish the fix within the hour, that's fine. But if not, please consider restoring previous version. Thx for consideration. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
Can someone point me to where you can download the previous version? rpcbind_0.2.3-0.6ubuntu0.18.04.1_amd64.deb I can't locate it. Brad -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
The previous version is available here: https://launchpad.net/ubuntu/+source/rpcbind/0.2.3-0.6ubuntu0.18.04.1/+build/19780512/+files/rpcbind_0.2.3-0.6ubuntu0.18.04.1_amd64.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
Hi, This bug is affecting our NIS server. Can someone post where to download the updated rpcbind package for Ubuntu 18.04.5? rpcbind is crashing repeatedly. Jun 10 14:35:08 systemd[1]: rpcbind.service: Main process exited, code=dumped, status=6/ABRT Jun 10 14:35:08 systemd[1]: rpcbind.service: Failed with result 'core-dump'. Jun 10 14:35:08 systemd[1]: rpcbind.service: Service hold-off time over, scheduling restart. Jun 10 14:35:08 systemd[1]: rpcbind.service: Scheduled restart job, restart counter is at 10. Jun 10 14:35:08 systemd[1]: Stopped RPC bind portmap service. Jun 10 14:35:08 systemd[1]: Starting RPC bind portmap service... Thank you. Brad Zoltick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
Just to put the information on the bug, I reproduced this failure on a Raspberry Pi, not a piece of the Scalingstack infrastructure in sight ;-) As far as I can tell it looked as if it's timing out waiting for network-online.target to become active. It seems as if installing network-manager makes the target take way longer to activate, so long that it is over autopkgtest's timeout. I suppose this isn't expected, so maybe the next step is to look into why that happens? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
Yes, I second this request. I have mail system broken due to dependency upon package service. From: boun...@canonical.com on behalf of Edoardo Tirtarahardja <1931...@bugs.launchpad.net> Sent: Thursday, June 10, 2021 11:44 AM To: Kleinhesselink, Dirk Subject: [Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 For short term solution, is it possible to restore the working 0.2.3-0.6ubuntu0.18.04.1 package back to the repo, ASAP, until the fix is in. We have multiple system effected, manually update those with manually downloaded deb package is very tedious task. If we can at least fall back easily using `apt install rpcbind=0.2.3-0.6ubuntu0.18.04.1` command, which is very easy to deploy to multiple system. Thx Marc for consideration. -- You received this bug notification because you are subscribed to a duplicate bug report (1931616). https://urldefense.com/v3/__https://bugs.launchpad.net/bugs/1931507__;!!LQC6Cpwp!79YI-6eE5sBNQhr7g4NUuw9an9RwStbI4QJli8VR08i07tHPRIs5cN3Xcf0p7l3u9nXoSTXa$ Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 Status in rpcbind package in Ubuntu: Confirmed Bug description: Failure with new rpcbind version. Reverting to the previous version fixes it. Bad: rpcbind_0.2.3-0.6ubuntu0.18.04.2_amd64.deb Good: rpcbind_0.2.3-0.6ubuntu0.18.04.1_amd64.deb $ journalctl -u rpcbind.service Jun 09 23:41:00 MYSYSTEM systemd[1]: Started RPC bind portmap service. Jun 09 23:41:30 MYSYSTEM rpcbind[25504]: rpcbind: pmap_prot.c:50: xdr_pmap: Assertion `regs != NULL' failed. Jun 09 23:41:30 MYSYSTEM systemd[1]: rpcbind.service: Main process exited, code=killed, status=6/ABRT Jun 09 23:41:30 MYSYSTEM systemd[1]: rpcbind.service: Failed with result 'signal'. Jun 09 23:41:30 MYSYSTEM systemd[1]: rpcbind.service: Service hold-off time over, scheduling restart. Jun 09 23:41:30 MYSYSTEM systemd[1]: rpcbind.service: Scheduled restart job, restart counter is at 477. Jun 09 23:41:30 MYSYSTEM systemd[1]: Stopped RPC bind portmap service. $ lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 $ uname -a Linux MYSYSTEM 5.4.0-1044-gcp #47~18.04.2-Ubuntu SMP Mon May 17 03:48:15 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux $ apt-cache policy rpcbind rpcbind: Installed: 0.2.3-0.6ubuntu0.18.04.1 Candidate: 0.2.3-0.6ubuntu0.18.04.2 Version table: 0.2.3-0.6ubuntu0.18.04.2 500 500 https://urldefense.com/v3/__http://us-east1.gce.archive.ubuntu.com/ubuntu__;!!LQC6Cpwp!79YI-6eE5sBNQhr7g4NUuw9an9RwStbI4QJli8VR08i07tHPRIs5cN3Xcf0p7l3u9sGLzkGX$ bionic-updates/main amd64 Packages 500 https://urldefense.com/v3/__http://security.ubuntu.com/ubuntu__;!!LQC6Cpwp!79YI-6eE5sBNQhr7g4NUuw9an9RwStbI4QJli8VR08i07tHPRIs5cN3Xcf0p7l3u9hFLDfTR$ bionic-security/main amd64 Packages *** 0.2.3-0.6ubuntu0.18.04.1 100 100 /var/lib/dpkg/status 0.2.3-0.6 500 500 https://urldefense.com/v3/__http://us-east1.gce.archive.ubuntu.com/ubuntu__;!!LQC6Cpwp!79YI-6eE5sBNQhr7g4NUuw9an9RwStbI4QJli8VR08i07tHPRIs5cN3Xcf0p7l3u9sGLzkGX$ bionic/main amd64 Packages To manage notifications about this bug go to: https://urldefense.com/v3/__https://bugs.launchpad.net/ubuntu/*source/rpcbind/*bug/1931507/*subscriptions__;Kysr!!LQC6Cpwp!79YI-6eE5sBNQhr7g4NUuw9an9RwStbI4QJli8VR08i07tHPRIs5cN3Xcf0p7l3u9tTSkAPj$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
I will publish the fix within the hour -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
For short term solution, is it possible to restore the working 0.2.3-0.6ubuntu0.18.04.1 package back to the repo, ASAP, until the fix is in. We have multiple system effected, manually update those with manually downloaded deb package is very tedious task. If we can at least fall back easily using `apt install rpcbind=0.2.3-0.6ubuntu0.18.04.1` command, which is very easy to deploy to multiple system. Thx Marc for consideration. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
I believe the following commit is missing: https://git.linux- nfs.org/?p=steved/rpcbind.git;a=commit;h=c49a7ea639eb700823e174fd605bbbe183e229aa I am building packages now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
I can confirm the update caused a regression. I will investigate and will publish a fix shortly. ** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
** Tags added: fr-1435 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
