[Bug 452073]
Created attachment 175300 /opt/libreofficedev7.3/program/soffice in version 7.3.0.0.alpha0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/452073 Title: [Upstream] Shouldn't detect configuration at each invocation To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/452073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 452073]
Dear Jérôme, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/452073 Title: [Upstream] Shouldn't detect configuration at each invocation To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/452073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1943368] Re: Touchpad not recognised
Wäre can I find this Information in Windows? Hui Wang <1943...@bugs.launchpad.net> schrieb am Mo. 27. Sept. 2021 um 02:43: > Under windows, does the touchpad connect to i8042/ps2 bus or i2c bus? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1943368 > > Title: > Touchpad not recognised > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > the touchpad is not recognised > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: linux-image-5.4.0-81-generic 5.4.0-81.91 > ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 > Uname: Linux 5.4.0-81-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: bem1753 F pulseaudio >/dev/snd/pcmC0D0p: bem1753 F...m pulseaudio > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Sun Sep 12 15:55:20 2021 > InstallationDate: Installed on 2021-08-17 (25 days ago) > InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 > (20200806.1) > MachineType: Medion Akoya E6239 > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=de_DE.UTF-8 >SHELL=/bin/bash > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic > root=UUID=a2ea56ce-d8fa-4472-954d-4c580bee4549 ro i8042.nomux=1 quiet > splash vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-5.4.0-81-generic N/A >linux-backports-modules-5.4.0-81-generic N/A >linux-firmware1.187.16 > SourcePackage: linux > UpgradeStatus: Upgraded to focal on 2021-08-18 (25 days ago) > dmi.bios.date: 04/09/2014 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 612 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: Akoya E6239 > dmi.board.vendor: Medion > dmi.board.version: 1.0 > dmi.chassis.asset.tag: To Be Filled By O.E.M. > dmi.chassis.type: 3 > dmi.chassis.vendor: Medion > dmi.chassis.version: To Be Filled By O.E.M. > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr612:bd04/09/2014:svnMedion:pnAkoyaE6239:pvr1.0:rvnMedion:rnAkoyaE6239:rvr1.0:cvnMedion:ct3:cvrToBeFilledByO.E.M.: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: Akoya E6239 > dmi.product.sku: To be filled by O.E.M. > dmi.product.version: 1.0 > dmi.sys.vendor: Medion > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943368/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943368 Title: Touchpad not recognised To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944739] Re: package linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944739 Title: package linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1944739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1609750]
if patching the PulseAudio default.pa works, then the initial issue was probably a problem with alsa-ucm-conf not being updated in your distros. There's no reason to use asound.state these days, it's a much better idea to use UCM. my 2 cents. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609750 Title: Audio not working on Acer Chromebook R11 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1609750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1609750]
I don't have problems running Ubuntu 20.04 LTS with (original, non-HWE kernel) 5.4 series kernel these days. Granted, I've probably indeed modified the default.pa as indicated above, and have had a state file which I've restored - but the kernel is default, and the audio works fine without any manual state restores on every boot and I can switch between internal and HDMI audio fine. I've mostly used the HDMI audio though in recent years so I cannot say if there would be problems with internal audio in prolonged use. The reason for not upgrading beyond 5.4 kernel used to be that 5.8 kernel regressed with these low tier Intel graphics, but I recall that was fixed in later ones so the current Ubuntu 20.04 HWE kernel (5.11) that comes on eg 20.04.3 installation media might be worth trying again if wanting excitement to life. It'd be nice to experiment with out-of-the-box functionality too, which would be likely easiest done with live USB sticks. Overall, I think there might not be any kernel bug left here, only userspace ones. Although it might have easily regressed in more recent kernels given the low amount of users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609750 Title: Audio not working on Acer Chromebook R11 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1609750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806681]
Same issue here from a year ago on HP Z1: [4.556401] hp_wmi: query 0x4 returned error 0x5 [4.557900] hp_wmi: query 0xd returned error 0x5 [4.561206] hp_wmi: query 0x1b returned error 0x5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806681 Title: hp_wmi: query 0xd returned error 0x5 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945242] Re: Failed to refresh to pi-kernel rev 343 on uc18
apport-collect doesn't work on Ubuntu Core ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945242 Title: Failed to refresh to pi-kernel rev 343 on uc18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1609750]
solved the bug already i cleared some things and made an update On Sun, Sep 26, 2021, 05:40 ian <1609...@bugs.launchpad.net> wrote: > Any update on this? Having issues with sound working for some time, > than suddenly stopping with a buzzing sound. Will attempt to modify > patch for most recent kernel, but my understanding is the kernel should > already be patched. Works fine on galliumos, but not with any other > distro or most recent kernel > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1803810). > https://bugs.launchpad.net/bugs/1609750 > > Title: > Audio not working on Acer Chromebook R11 > > Status in linux: > Confirmed > Status in linux package in Ubuntu: > In Progress > Status in pulseaudio package in Ubuntu: > Invalid > > Bug description: > Audio is not working at all on Acer Chromebook R11 (codename CYAN). > It's a Intel Braswell platform. snd_hda_intel messages seem normal, > but Pulseaudio does not detect sound hardware. > > ProblemType: Bug > DistroRelease: Ubuntu 16.10 > Package: pulseaudio 1:9.0-1.1ubuntu1 > ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 > Uname: Linux 4.4.0-33-generic x86_64 > ApportVersion: 2.20.3-0ubuntu2 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', > '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', > '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', > '/dev/snd/timer'] failed with exit code 1: > CurrentDesktop: Unity > Date: Thu Aug 4 14:12:03 2016 > InstallationDate: Installed on 2016-07-22 (13 days ago) > InstallationMedia: > > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > SourcePackage: pulseaudio > Symptom: audio > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 05/20/2016 > dmi.bios.vendor: coreboot > dmi.chassis.type: 3 > dmi.chassis.vendor: GOOGLE > dmi.modalias: > dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: > dmi.product.name: Cyan > dmi.product.version: 1.0 > dmi.sys.vendor: GOOGLE > --- > ApportVersion: 2.20.3-0ubuntu2 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', > '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', > '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', > '/dev/snd/timer'] failed with exit code 1: > CurrentDesktop: Unity > DistroRelease: Ubuntu 16.10 > HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08 > InstallationDate: Installed on 2016-07-22 (13 days ago) > InstallationMedia: > > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 8087:0a2a Intel Corp. >Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: GOOGLE Cyan > Package: linux-image-4.4.0-33-generic 4.4.0-33.52 > PackageArchitecture: amd64 > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic > root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7 > ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > RelatedPackageVersions: >linux-restricted-modules-4.4.0-33-generic N/A >linux-backports-modules-4.4.0-33-generic N/A >linux-firmware1.159 > Tags: yakkety > Uname: Linux 4.4.0-33-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > dmi.bios.date: 05/20/2016 > dmi.bios.vendor: coreboot > dmi.chassis.type: 3 > dmi.chassis.vendor: GOOGLE > dmi.modalias: > dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: > dmi.product.name: Cyan > dmi.product.version: 1.0 > dmi.sys.vendor: GOOGLE > > To manage notifications about this bug go to: > https://bugs.launchpad.net/kernel/+bug/1609750/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609750 Title: Audio not working on Acer Chromebook R11 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1609750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
This is great, thanks for the fix. @jchittum, do you think you guys at CPC could respin the Ubuntu Impish images with this new snapd? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945246] Re: Gnome software fails to detect network connection
Output from executing gnome-software 22:47:39:0912 Gs not handling error no-network for action refresh: Cannot refresh cache whilst offline 22:47:39:0982 Gs failed to get featured apps: no apps to show 22:47:41:0142 Gtk Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945246 Title: Gnome software fails to detect network connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1945246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945246] [NEW] Gnome software fails to detect network connection
Public bug reported: Cannot install applications from deb or repos. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-software 40.4-1build1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Sep 27 17:47:47 2021 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2021-09-27 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) InstalledPlugins: gnome-software-plugin-flatpak 40.4-1build1 gnome-software-plugin-snap40.4-1build1 ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945246 Title: Gnome software fails to detect network connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1945246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850667] Re: Switch to "unified" cgroup hierarchy (cgroupv2)
This bug was fixed in the package snapd - 2.53~pre1.git19b68f708 --- snapd (2.53~pre1.git19b68f708) impish; urgency=medium * New git snapshot with fix for snapd.seeded.service in lxd (LP: #1944004) * New git snapshot that supports cgroups v2 (LP: #1850667) -- Michael Vogt Fri, 24 Sep 2021 16:26:55 +0200 ** Changed in: snapd (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/1850667 Title: Switch to "unified" cgroup hierarchy (cgroupv2) To manage notifications about this bug go to: https://bugs.launchpad.net/lxc/+bug/1850667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942646] Re: SRU 2.52
This bug was fixed in the package snapd - 2.53~pre1.git19b68f708 --- snapd (2.53~pre1.git19b68f708) impish; urgency=medium * New git snapshot with fix for snapd.seeded.service in lxd (LP: #1944004) * New git snapshot that supports cgroups v2 (LP: #1850667) -- Michael Vogt Fri, 24 Sep 2021 16:26:55 +0200 ** Changed in: snapd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942646 Title: SRU 2.52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1942646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
This bug was fixed in the package snapd - 2.53~pre1.git19b68f708 --- snapd (2.53~pre1.git19b68f708) impish; urgency=medium * New git snapshot with fix for snapd.seeded.service in lxd (LP: #1944004) * New git snapshot that supports cgroups v2 (LP: #1850667) -- Michael Vogt Fri, 24 Sep 2021 16:26:55 +0200 ** Changed in: snapd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929865] Re: autopkgtests fail due to precise being removed from the archive
This bug was fixed in the package update-manager - 1:20.04.10.9 --- update-manager (1:20.04.10.9) focal; urgency=medium * ubuntu-security-status: use ubuntu-advantage-tools to determine whether or not livepatch or esm are enabled and if the system is attached. Thanks to Chad Smith for the patch. (LP: #1938043) -- Brian Murray Fri, 03 Sep 2021 15:17:22 -0700 ** Changed in: update-manager (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/1929865 Title: autopkgtests fail due to precise being removed from the archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1929865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938043] Update Released
The verification of the Stable Release Update for update-manager has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938043 Title: ubuntu-security-status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1938043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938043] Re: ubuntu-security-status
This bug was fixed in the package update-manager - 1:20.04.10.9 --- update-manager (1:20.04.10.9) focal; urgency=medium * ubuntu-security-status: use ubuntu-advantage-tools to determine whether or not livepatch or esm are enabled and if the system is attached. Thanks to Chad Smith for the patch. (LP: #1938043) -- Brian Murray Fri, 03 Sep 2021 15:17:22 -0700 ** Changed in: update-manager (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/1938043 Title: ubuntu-security-status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1938043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939628] Re: Fan goes full speed on resume from suspend (Lenovo ThinkPad T460)
Still a problem on latest 20.04 kernel, 5.11.0-36-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939628 Title: Fan goes full speed on resume from suspend (Lenovo ThinkPad T460) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1939628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944475] Update Released
The verification of the Stable Release Update for ubuntu-release- upgrader has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944475 Title: DistUpgradeViewNonInteractive is now interactive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1944475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944475] Re: DistUpgradeViewNonInteractive is now interactive
This bug was fixed in the package ubuntu-release-upgrader - 1:21.04.17 --- ubuntu-release-upgrader (1:21.04.17) hirsute; urgency=medium * DistUpgrade/DistUpgradeFetcherCore.py: when running in non-interactive mode do not show the release notes. (LP: #1944475) * Run pre-build.sh: updating mirrors, demotions, and translations. -- William 'jawn-smith' Wilson Thu, 23 Sep 2021 13:52:27 -0500 ** Changed in: ubuntu-release-upgrader (Ubuntu Hirsute) 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/1944475 Title: DistUpgradeViewNonInteractive is now interactive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1944475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed
Thanks, Simon. I'll verify a revert from the menu after I update and post there if things don't go well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945242] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1945242 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945242 Title: Failed to refresh to pi-kernel rev 343 on uc18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944951] Re: delayed display update / konsole artifacts
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944951 Title: delayed display update / konsole artifacts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1944951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944951] Re: delayed display update / konsole artifacts
It looks that I'm struck by the same bug. For me all KDE applications show display problems, not only just konsole. But konsole is the one that's used most often. After you have "fixed" you installation now, could you please turn off the composite manager. Just use Shift-Alt-F12 for that. I do not get any display errors here as long as the composite manager runs. Is the problem back without composite manager? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944951 Title: delayed display update / konsole artifacts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1944951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945242] [NEW] Failed to refresh to pi-kernel rev 343 on uc18
Public bug reported: The refresh to a new kernel snap is failing in uc18 image. Something important to remark is that the DTB's for the new kernel were installed, but it still failed to complete the refresh to the new kernel Steps to reproduce I am using a rpi3 and I create an uc18 arm64 image using the following snaps $ snap list core18 2127 core20 1084 pi 81 pi-kernel 278 snapd 12967 Then, once the image is booted, I login and refresh snapd and pi gadget $ sudo snap refresh snapd --beta 2021-09-27T20:49:56Z INFO Waiting for automatic snapd restart... snapd (beta) 2.52 from Canonical✓ refreshed $ sudo snap refresh pi --stable pi (18-pi/stable) 18-1 from Canonical✓ refreshed Then I refresh pi-kernel snap $ sudo snap refresh pi-kernel --stable Make current revision for snap "pi-kernel" unavailable \ Broadcast message from root@localhost (Mon 2021-09-27 20:55:04 UTC): But it fails 7Error today at 20:54 UTC today at 20:56 UTC Refresh "pi-kernel" snap sergio-j-cazzolato@localhost:~$ snap change 7 Status Spawn Ready Summary Donetoday at 20:54 UTC today at 20:56 UTC Ensure prerequisites for "pi-kernel" are available Undone today at 20:54 UTC today at 20:56 UTC Download snap "pi-kernel" (343) from channel "18-pi/stable" Donetoday at 20:54 UTC today at 20:56 UTC Fetch and check assertions for snap "pi-kernel" (343) Undone today at 20:54 UTC today at 20:56 UTC Mount snap "pi-kernel" (343) Undone today at 20:54 UTC today at 20:56 UTC Run pre-refresh hook of "pi-kernel" snap if present Undone today at 20:54 UTC today at 20:56 UTC Stop snap "pi-kernel" services Undone today at 20:54 UTC today at 20:56 UTC Remove aliases for snap "pi-kernel" Undone today at 20:54 UTC today at 20:56 UTC Make current revision for snap "pi-kernel" unavailable Donetoday at 20:54 UTC today at 20:56 UTC Update assets from kernel "pi-kernel" (343) Undone today at 20:54 UTC today at 20:56 UTC Copy snap "pi-kernel" data Undone today at 20:54 UTC today at 20:56 UTC Setup snap "pi-kernel" (343) security profiles Undone today at 20:54 UTC today at 20:56 UTC Make snap "pi-kernel" (343) available to the system Error today at 20:54 UTC today at 20:56 UTC Automatically connect eligible plugs and slots of snap "pi-kernel" Holdtoday at 20:54 UTC today at 20:56 UTC Set automatic aliases for snap "pi-kernel" Holdtoday at 20:54 UTC today at 20:56 UTC Setup snap "pi-kernel" aliases Holdtoday at 20:54 UTC today at 20:56 UTC Run post-refresh hook of "pi-kernel" snap if present Holdtoday at 20:54 UTC today at 20:56 UTC Start snap "pi-kernel" (343) services Holdtoday at 20:54 UTC today at 20:56 UTC Clean up "pi-kernel" (343) install Holdtoday at 20:54 UTC today at 20:56 UTC Run configure hook of "pi-kernel" snap if present Holdtoday at 20:54 UTC today at 20:56 UTC Run health check of "pi-kernel" snap Donetoday at 20:54 UTC today at 20:56 UTC Handling re-refresh of "pi-kernel" as needed .. Make snap "pi-kernel" (343) available to the system ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: The refresh to a new kernel snap is failing in uc18 image. Something important to remark is that the DTB's for the new kernel were installed, but it still failed to complete the refresh to the new kernel Steps to reproduce I am using a rpi3 and I create an uc18 arm64 image using the following snaps $ snap list - Name VersionRevTracking Publisher Notes - core18 20210722 2127 latest/stable canonical✓ base - core20 20210702 1084 latest/stable canonical✓ base - pi 18-1 81 18-pi/stable canonical✓ gadget - pi-kernel 5.3.0-1040.42 27818-pi/stable canonical✓ kernel - snapd 2.52 13269 latest/betacanonical✓ snapd + core18 2127 + core20 1084 + pi 81 + pi-kernel 278 + snapd 12967 Then, once the image is booted, I login and refresh snapd and pi gadget $ sudo snap refresh snapd --beta 2021-09-27T20:49:56Z INFO Waiting for automatic snapd restart... snapd (beta) 2.52 from Canonical✓ refreshed $ sudo snap refresh pi --stable pi (18-pi/stable) 18-1 from Canonical✓ refreshed Then I refresh pi-kernel snap $ sudo snap refresh pi-kernel --stable Make current revision for snap "pi-kernel" unavailable \ Broadcast message from root@localhost (Mon 2021-09-27 20:55:04 UTC): But it fails 7Error today at
[Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed
@#41: Dataset “rpool/ROOT/ubuntu_” sounds like bug 1894329, although that one should have been fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871566] Re: Files from packages installed in directory /debian
** Changed in: nv-codec-headers (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871566 Title: Files from packages installed in directory /debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nv-codec-headers/+bug/1871566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945241] [NEW] Please update nv-codec-headers to version 11
Public bug reported: The latest version of gnome-remote-desktop (41) can optionally enable better Nvidia support but it needs nv-codec-headers version 11. Please package this version and let the Ubuntu Desktop team know so that they can enable that feature. ** Affects: nv-codec-headers (Ubuntu) Importance: Wishlist Status: New ** Tags: upgrade-software-version ** Description changed: - The latest version of gnome-remote-desktop can optionally enable better - Nvidia support but it needs nv-codec-headers version 11. + The latest version of gnome-remote-desktop (41) can optionally enable + better Nvidia support but it needs nv-codec-headers version 11. Please package this version and let the Ubuntu Desktop team know so that they can enable that feature. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945241 Title: Please update nv-codec-headers to version 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nv-codec-headers/+bug/1945241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta/5.11.0.38.39)
All autopkgtests for the newly accepted linux-meta (5.11.0.38.39) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: systemd/247.3-3ubuntu3.6 (armhf, amd64) initramfs-tools/0.139ubuntu3 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#linux-meta [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931296] Re: docs inconsistency in CVE-2021-29921
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python3.8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931296 Title: docs inconsistency in CVE-2021-29921 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.8/+bug/1931296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
** Changed in: docker.io (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912811] Please test proposed package
Hello Seth, or anyone else affected, Accepted dwarves-dfsg into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dwarves- dfsg/1.21-0ubuntu1~20.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912811 Title: Update dwarves-dfsg in focal to version 1.21 from impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1912811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912811] Re: Update dwarves-dfsg in focal to version 1.21 from impish
Hello Seth, or anyone else affected, Accepted dwarves-dfsg into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dwarves- dfsg/1.21-0ubuntu1~21.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: dwarves-dfsg (Ubuntu Hirsute) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-hirsute ** Changed in: dwarves-dfsg (Ubuntu Focal) Status: Confirmed => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912811 Title: Update dwarves-dfsg in focal to version 1.21 from impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1912811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944389] Re: Thermald 1.9.1-1ubuntu0.6 keeps Tigerlake GPU frequency on 400 MHz
I just checked old and new behavior again. First of all it's not clear for me from where this value of 53 is taken, according to the data in /sys/class/thermal/thermal_zone5 (THP) trip_point_0_hyst:4000 trip_point_0_temp:-274000 trip_point_0_type:passive trip_point_1_hyst:4000 trip_point_1_temp:-274000 trip_point_1_type:passive trip_point_2_hyst:4000 trip_point_2_temp:80050 trip_point_2_type:critical trip_point_3_hyst:4000 trip_point_3_temp:75050 trip_point_3_type:hot trip_point_4_hyst:4000 trip_point_4_temp:65050 trip_point_4_type:passive and the same values are shown for THP by old thermald (via ThermalMonitor): THP: 65 Passive 75 Max 80 Critical 58 Polling For new thermald with --adaptive THP values (via ThermalMonitor) are the following: 52 Passive 46 Polling and doesn't comply with data from /sys/class/thermal/thermal_zone5/ I'll be grateful if you could explain me what I missed, but I believe that it could be so -- at least it looks like thermald tries to maintain 53 degree value. But regarding my issue I can tell you some measurements: With old thermald zone5 (THP) temperature is kept 53-56 during the load, CPU temperature 60-64, CPU frequency 1.3-1.4 with new thermald zone5 (THP) temperature is also kept 53-56 during the load, CPU temperature 70-74 CPU frequency 2.4 (up to 2.7) and amount of noise is bigger. So it looks like thermald tries to keep THP temperature within limits by decreasing the GPU frequency, but as far as GPU chip is on the same die with CPU and shares the cooling fan, thermald is not succeed -- because the CPU heats the GPU chip. So my biggest concern and suspicion here is that new thermald (with --adaptive) sacrifices GPU by CPU -- it makes GPU run on lower frequencies in favor of allowing CPU run on higher ones. Maybe it is reasonable for some loads (I can hardly imagine for which ones?) but not for end-user laptop and especially for gaming/3D or 4K accelerated video from Youtube -- if there is a high demand for GPU it means that it would mostly affect performance, latency and overall end-user experience. Tigerlake laptops have more than enough CPU performance for end-user but a very weak GPU and even this GPU is throttled in case of serious load. I understand that it would be better to have some option, what to prioritize GPU or CPU, but for majority of end-users (and this Tigerlake is not a tool for ones who want to run a heavy computing tasks) the GPU prioritization would be more desired and expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944389 Title: Thermald 1.9.1-1ubuntu0.6 keeps Tigerlake GPU frequency on 400 MHz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1944389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926442] Autopkgtest regression report (netplan.io/0.99-0ubuntu3~18.04.5)
All autopkgtests for the newly accepted netplan.io (0.99-0ubuntu3~18.04.5) for bionic have finished running. The following regressions have been reported in tests triggered by the package: netplan.io/0.99-0ubuntu3~18.04.5 (ppc64el, i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#netplan.io [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926442 Title: [SRU] cannot execute 'netplan generate' from within a snap To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1926442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925246] Re: binderfs support is not enabled
This bug was fixed in the package linux-azure - 5.11.0-1017.18
---
linux-azure (5.11.0-1017.18) hirsute; urgency=medium
* hirsute/linux-azure: 5.11.0-1017.18 -proposed tracker (LP: #1944161)
* Hirsute update: upstream stable patchset 2021-08-12 (LP: #1939738)
- [Config] updateconfigs for RESET_INTEL_GW, RESET_BRCMSTB_RESCAL
* binderfs support is not enabled (LP: #1925246)
- [Config] linux-azure: CONFIG_ANDROID_BINDERFS=m
* Drivers: hv: vmbus: Fix duplicate CPU assignments within a device
(LP: #1937078)
- Drivers: hv: vmbus: Fix duplicate CPU assignments within a device
[ Ubuntu: 5.11.0-37.41 ]
* hirsute/linux: 5.11.0-37.41 -proposed tracker (LP: #1944180)
* CVE-2021-41073
- io_uring: ensure symmetry in handling iter types in loop_rw_iter()
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.09.06)
* LRMv5: switch primary version handling to kernel-versions data set
(LP: #1928921)
- [Packaging] switch to kernel-versions
* disable “CONFIG_HISI_DMA” config for ubuntu version (LP: #1936771)
- Disable CONFIG_HISI_DMA
- [Config] Record hisi_dma no longer built for arm64
* ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with
dump_page() (LP: #1941829)
- selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio
limit
hot-remove error test
* alsa: the soundwire audio doesn't work on the Dell TGL-H machines
(LP: #1941669)
- ASoC: SOF: allow soundwire use desc->default_fw_filename
- ASoC: Intel: tgl: remove sof_fw_filename set for tgl_3_in_1_default
* e1000e blocks the boot process when it tried to write checksum to its NVM
(LP: #1936998)
- e1000e: Do not take care about recovery NVM checksum
* Dell XPS 17 (9710) PCI/internal sound card not detected (LP: #1935850)
- ASoC: Intel: sof_sdw: include rt711.h for RT711 JD mode
- ASoC: Intel: sof_sdw: add quirk for Dell XPS 9710
* mute/micmute LEDs no function on HP ProBook 650 G8 (LP: #1939473)
- ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 650 G8 Notebook PC
* Fix mic noise on HP ProBook 445 G8 (LP: #1940610)
- ALSA: hda/realtek: Limit mic boost on HP ProBook 445 G8
* GPIO error logs in start and dmesg after update of kernel (LP: #1937897)
- ODM: mfd: Check AAEON BFPI version before adding device
* External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3
Dock (LP: #1938999)
- drm/i915/ilk-glk: Fix link training on links with LTTPRs
* Fix kernel panic caused by legacy devices on AMD platforms (LP: #1936682)
- SAUCE: iommu/amd: Keep swiotlb enabled to ensure devices with 32bit DMA
still work
* Hirsute update: upstream stable patchset 2021-08-30 (LP: #1942123)
- drm/i915: Revert "drm/i915/gem: Asynchronous cmdparser"
- Revert "drm/i915: Propagate errors on awaiting already signaled fences"
- regulator: rtmv20: Fix wrong mask for strobe-polarity-high
- regulator: rt5033: Fix n_voltages settings for BUCK and LDO
- spi: stm32h7: fix full duplex irq handler handling
- ASoC: tlv320aic31xx: fix reversed bclk/wclk master bits
- r8152: Fix potential PM refcount imbalance
- qed: fix possible unpaired spin_{un}lock_bh in _qed_mcp_cmd_and_union()
- ASoC: rt5682: Fix the issue of garbled recording after powerd_dbus_suspend
- net: Fix zero-copy head len calculation.
- ASoC: ti: j721e-evm: Fix unbalanced domain activity tracking during
startup
- ASoC: ti: j721e-evm: Check for not initialized parent_clk_id
- efi/mokvar: Reserve the table only if it is in boot services data
- nvme: fix nvme_setup_command metadata trace event
- drm/amd/display: Fix comparison error in dcn21 DML
- drm/amd/display: Fix max vstartup calculation for modes with borders
- Revert "Bluetooth: Shutdown controller after workqueues are flushed or
cancelled"
- firmware: arm_scmi: Add delayed response status check
- Revert "watchdog: iTCO_wdt: Account for rebooting on second timeout"
- selftest/bpf: Adjust expected verifier errors
- bpf, selftests: Adjust few selftest result_unpriv outcomes
- bpf: Update selftests to reflect new error states
- bpf, selftests: Adjust few selftest outcomes wrt unreachable code
- selftest/bpf: Verifier tests for var-off access
- spi: mediatek: Fix fifo transfer
- cifs: use helpers when parsing uid/gid mount options and validate them
- cifs: add missing parsing of backupuid
- net: dsa: sja1105: parameterize the number of ports
- ASoC: Intel: boards: handle hda-dsp-common as a module
- [Config] updateconfigs for SND_SOC_INTEL_HDA_DSP_COMMON
- ASoC: Intel: boards: create sof-maxim-common module
- [Config] updateconfigs for SND_SOC_INTEL_SOF_MAXIM_COMMON
- ASoC: Intel: boards: fix xrun issue on platform with max98373
- r8152: Fix a deadlock by doubly PM resume
- Revert "ACPICA:
[Bug 1937078] Re: Drivers: hv: vmbus: Fix duplicate CPU assignments within a device
This bug was fixed in the package linux-azure - 5.11.0-1017.18
---
linux-azure (5.11.0-1017.18) hirsute; urgency=medium
* hirsute/linux-azure: 5.11.0-1017.18 -proposed tracker (LP: #1944161)
* Hirsute update: upstream stable patchset 2021-08-12 (LP: #1939738)
- [Config] updateconfigs for RESET_INTEL_GW, RESET_BRCMSTB_RESCAL
* binderfs support is not enabled (LP: #1925246)
- [Config] linux-azure: CONFIG_ANDROID_BINDERFS=m
* Drivers: hv: vmbus: Fix duplicate CPU assignments within a device
(LP: #1937078)
- Drivers: hv: vmbus: Fix duplicate CPU assignments within a device
[ Ubuntu: 5.11.0-37.41 ]
* hirsute/linux: 5.11.0-37.41 -proposed tracker (LP: #1944180)
* CVE-2021-41073
- io_uring: ensure symmetry in handling iter types in loop_rw_iter()
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.09.06)
* LRMv5: switch primary version handling to kernel-versions data set
(LP: #1928921)
- [Packaging] switch to kernel-versions
* disable “CONFIG_HISI_DMA” config for ubuntu version (LP: #1936771)
- Disable CONFIG_HISI_DMA
- [Config] Record hisi_dma no longer built for arm64
* ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with
dump_page() (LP: #1941829)
- selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio
limit
hot-remove error test
* alsa: the soundwire audio doesn't work on the Dell TGL-H machines
(LP: #1941669)
- ASoC: SOF: allow soundwire use desc->default_fw_filename
- ASoC: Intel: tgl: remove sof_fw_filename set for tgl_3_in_1_default
* e1000e blocks the boot process when it tried to write checksum to its NVM
(LP: #1936998)
- e1000e: Do not take care about recovery NVM checksum
* Dell XPS 17 (9710) PCI/internal sound card not detected (LP: #1935850)
- ASoC: Intel: sof_sdw: include rt711.h for RT711 JD mode
- ASoC: Intel: sof_sdw: add quirk for Dell XPS 9710
* mute/micmute LEDs no function on HP ProBook 650 G8 (LP: #1939473)
- ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 650 G8 Notebook PC
* Fix mic noise on HP ProBook 445 G8 (LP: #1940610)
- ALSA: hda/realtek: Limit mic boost on HP ProBook 445 G8
* GPIO error logs in start and dmesg after update of kernel (LP: #1937897)
- ODM: mfd: Check AAEON BFPI version before adding device
* External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3
Dock (LP: #1938999)
- drm/i915/ilk-glk: Fix link training on links with LTTPRs
* Fix kernel panic caused by legacy devices on AMD platforms (LP: #1936682)
- SAUCE: iommu/amd: Keep swiotlb enabled to ensure devices with 32bit DMA
still work
* Hirsute update: upstream stable patchset 2021-08-30 (LP: #1942123)
- drm/i915: Revert "drm/i915/gem: Asynchronous cmdparser"
- Revert "drm/i915: Propagate errors on awaiting already signaled fences"
- regulator: rtmv20: Fix wrong mask for strobe-polarity-high
- regulator: rt5033: Fix n_voltages settings for BUCK and LDO
- spi: stm32h7: fix full duplex irq handler handling
- ASoC: tlv320aic31xx: fix reversed bclk/wclk master bits
- r8152: Fix potential PM refcount imbalance
- qed: fix possible unpaired spin_{un}lock_bh in _qed_mcp_cmd_and_union()
- ASoC: rt5682: Fix the issue of garbled recording after powerd_dbus_suspend
- net: Fix zero-copy head len calculation.
- ASoC: ti: j721e-evm: Fix unbalanced domain activity tracking during
startup
- ASoC: ti: j721e-evm: Check for not initialized parent_clk_id
- efi/mokvar: Reserve the table only if it is in boot services data
- nvme: fix nvme_setup_command metadata trace event
- drm/amd/display: Fix comparison error in dcn21 DML
- drm/amd/display: Fix max vstartup calculation for modes with borders
- Revert "Bluetooth: Shutdown controller after workqueues are flushed or
cancelled"
- firmware: arm_scmi: Add delayed response status check
- Revert "watchdog: iTCO_wdt: Account for rebooting on second timeout"
- selftest/bpf: Adjust expected verifier errors
- bpf, selftests: Adjust few selftest result_unpriv outcomes
- bpf: Update selftests to reflect new error states
- bpf, selftests: Adjust few selftest outcomes wrt unreachable code
- selftest/bpf: Verifier tests for var-off access
- spi: mediatek: Fix fifo transfer
- cifs: use helpers when parsing uid/gid mount options and validate them
- cifs: add missing parsing of backupuid
- net: dsa: sja1105: parameterize the number of ports
- ASoC: Intel: boards: handle hda-dsp-common as a module
- [Config] updateconfigs for SND_SOC_INTEL_HDA_DSP_COMMON
- ASoC: Intel: boards: create sof-maxim-common module
- [Config] updateconfigs for SND_SOC_INTEL_SOF_MAXIM_COMMON
- ASoC: Intel: boards: fix xrun issue on platform with max98373
- r8152: Fix a deadlock by doubly PM resume
- Revert "ACPICA:
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
I'm not sure if this is the right package ** Package changed: ubuntu => thermald (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938289] Re: Please update to upstream release 20210728.00
## Conclusion Due to the completion of Google's testing and my own verification, I am marking verification-complete for all releases. ## Notes Testing of the new Google guest agents was primarily performed by Google themselves. They have given the +1. In addition, these images have gone through testing from the Canonical Public Cloud team. From my own testing images were produced with the guest agents directly from proposed and uploaded to GCE. These are the same images that Google used in their own testing. I verified: 1) The versions of packages 2) that the services were running/completed successfully 3) that my account and other project accounts were created 4) correct SSH keys were imported 5) the new packages provided parity with the existing agents. Bionic: google-compute-engine-oslogin 20210728.00-0ubuntu1~18.04.0 systemctl status google-oslogin-cache.service ● google-oslogin-cache.service - NSS cache refresh Loaded: loaded (/lib/systemd/system/google-oslogin-cache.service; static; vendor preset: enabled) Active: inactive (dead) since Mon 2021-09-27 14:17:57 UTC; 2h 14min ago Process: 30617 ExecStart=/usr/bin/google_oslogin_nss_cache (code=exited, status=0/SUCCESS) Main PID: 30617 (code=exited, status=0/SUCCESS) Focal: google-compute-engine-oslogin 20210728.00-0ubuntu1~20.04.0 systemctl status google-oslogin-cache.service ● google-oslogin-cache.service - NSS cache refresh Loaded: loaded (/lib/systemd/system/google-oslogin-cache.service; static; vendor preset: enabled) Active: inactive (dead) since Mon 2021-09-27 14:09:16 UTC; 3h 23min ago TriggeredBy: ● google-oslogin-cache.timer Process: 32376 ExecStart=/usr/bin/google_oslogin_nss_cache (code=exited, status=0/SUCCESS) Main PID: 32376 (code=exited, status=0/SUCCESS) Hirsute: google-compute-engine-oslogin 20210728.00-0ubuntu1~21.04.0 systemctl status google-oslogin-cache.service ● google-oslogin-cache.service - NSS cache refresh Loaded: loaded (/lib/systemd/system/google-oslogin-cache.service; static) Active: inactive (dead) since Mon 2021-09-27 14:11:58 UTC; 3h 42min ago TriggeredBy: ● google-oslogin-cache.timer Process: 33903 ExecStart=/usr/bin/google_oslogin_nss_cache (code=exited, status=0/SUCCESS) Main PID: 33903 (code=exited, status=0/SUCCESS) ** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-hirsute ** Tags added: verification-done-bionic verification-done-focal 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/1938289 Title: Please update to upstream release 20210728.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-compute-engine-oslogin/+bug/1938289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938440] Re: Please update gce-compute-image-packages to 20210629.00
** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-hirsute ** Tags added: verification-done-bionic verification-done-focal 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/1938440 Title: Please update gce-compute-image-packages to 20210629.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1938440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
@DanglingPointer (ferncasado) gonna try #74. i really do want to understand how all this works. this might be the most reliable option since even ppa's break. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938286] Re: Please update to 20210629.00 upstream release
## Conclusion Due to the completion of Google's testing and my own verification, I am marking verification-complete for all releases. ## Notes Testing of the new Google guest agents was primarily performed by Google themselves. They have given the +1. In addition, these images have gone through testing from the Canonical Public Cloud team. From my own testing images were produced with the guest agents directly from proposed and uploaded to GCE. These are the same images that Google used in their own testing. I verified: 1) The versions of packages 2) that the services were running/completed successfully 3) that my account and other project accounts were created 4) correct SSH keys were imported 5) the new packages provided parity with the existing agents. Bionic: google-guest-agent 20210629.00-0ubuntu1~18.04.1 systemctl status google-guest-agent ● google-guest-agent.service - Google Compute Engine Guest Agent Loaded: loaded (/lib/systemd/system/google-guest-agent.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-09-22 20:06:24 UTC; 4 days ago Main PID: 1323 (google_guest_ag) Tasks: 12 (limit: 4666) CGroup: /system.slice/google-guest-agent.service └─1323 /usr/bin/google_guest_agent systemctl status google-shutdown-scripts.service ● google-shutdown-scripts.service - Google Compute Engine Shutdown Scripts Loaded: loaded (/lib/systemd/system/google-shutdown-scripts.service; enabled; vendor preset: enabled) Active: active (exited) since Wed 2021-09-22 20:06:23 UTC; 4 days ago Main PID: 1324 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4666) CGroup: /system.slice/google-shutdown-scripts.service systemctl status google-startup-scripts.service ● google-startup-scripts.service - Google Compute Engine Startup Scripts Loaded: loaded (/lib/systemd/system/google-startup-scripts.service; enabled; vendor preset: enabled) Active: inactive (dead) since Wed 2021-09-22 20:06:39 UTC; 4 days ago Main PID: 2325 (code=exited, status=0/SUCCESS) Focal: google-guest-agent 20210629.00-0ubuntu1~20.04.0 systemctl status google-guest-agent ● google-guest-agent.service - Google Compute Engine Guest Agent Loaded: loaded (/lib/systemd/system/google-guest-agent.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-09-22 20:04:08 UTC; 4 days ago Main PID: 656 (google_guest_ag) Tasks: 11 (limit: 4705) Memory: 18.8M CGroup: /system.slice/google-guest-agent.service └─656 /usr/bin/google_guest_agent systemctl status google-shutdown-scripts.service ● google-shutdown-scripts.service - Google Compute Engine Shutdown Scripts Loaded: loaded (/lib/systemd/system/google-shutdown-scripts.service; enabled; vendor preset: enabled) Active: active (exited) since Wed 2021-09-22 20:04:12 UTC; 4 days ago Main PID: 798 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4705) Memory: 0B CGroup: /system.slice/google-shutdown-scripts.service systemctl status google-startup-scripts.service ● google-startup-scripts.service - Google Compute Engine Startup Scripts Loaded: loaded (/lib/systemd/system/google-startup-scripts.service; enabled; vendor preset: enabled) Active: inactive (dead) since Wed 2021-09-22 20:04:21 UTC; 4 days ago Main PID: 1511 (code=exited, status=0/SUCCESS) Hirsute: google-guest-agent 20210629.00-0ubuntu1~21.04.0 systemctl status google-guest-agent ● google-guest-agent.service - Google Compute Engine Guest Agent Loaded: loaded (/lib/systemd/system/google-guest-agent.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-09-22 20:07:21 UTC; 4 days ago Main PID: 675 (google_guest_ag) Tasks: 10 (limit: 4700) Memory: 18.5M CGroup: /system.slice/google-guest-agent.service └─675 /usr/bin/google_guest_agent systemctl status google-shutdown-scripts.service ● google-shutdown-scripts.service - Google Compute Engine Shutdown Scripts Loaded: loaded (/lib/systemd/system/google-shutdown-scripts.service; enabled; vendor preset: enabled) Active: active (exited) since Wed 2021-09-22 20:07:25 UTC; 4 days ago Main PID: 808 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4700) Memory: 0B CGroup: /system.slice/google-shutdown-scripts.service systemctl status google-startup-scripts.service ● google-startup-scripts.service - Google Compute Engine Startup Scripts Loaded: loaded (/lib/systemd/system/google-startup-scripts.service; enabled; vendor preset: enabled) Active: inactive (dead) since Wed 2021-09-22 20:07:33 UTC; 4 days ago Main PID: 1446 (code=exited, status=0/SUCCESS) ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute ** Tags removed: verification-needed-bionic verification-needed-focal ** Tags added: verificatio
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
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/1945221/+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/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1945221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938553] Re: Please update to upstream release 20210608.1
## Conclusion Due to the completion of Google's testing and my own verification, I am marking verification-complete for all releases. ## Notes Testing of the new Google guest agents was primarily performed by Google themselves. They have given the +1. In addition, these images have gone through testing from the Canonical Public Cloud team. From my own testing images were produced with the guest agents directly from proposed and uploaded to GCE. These are the same images that Google used in their own testing. I verified: 1) The versions of packages 2) that the services were running/completed successfully 3) that my account and other project accounts were created 4) correct SSH keys were imported 5) the new packages provided parity with the existing agents. Bionic: google-osconfig-agent 20210608.1-0ubuntu1~18.04.1 systemctl status google-osconfig-agent ● google-osconfig-agent.service - Google OSConfig Agent Loaded: loaded (/lib/systemd/system/google-osconfig-agent.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-09-22 20:06:20 UTC; 4 days ago Main PID: 1096 (google_osconfig) Tasks: 11 (limit: 4666) CGroup: /system.slice/google-osconfig-agent.service └─1096 /usr/bin/google_osconfig_agent Focal: google-osconfig-agent 20210608.1-0ubuntu1~20.04.0 systemctl status google-osconfig-agent ● google-osconfig-agent.service - Google OSConfig Agent Loaded: loaded (/lib/systemd/system/google-osconfig-agent.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-09-22 20:04:06 UTC; 4 days ago Main PID: 569 (google_osconfig) Tasks: 10 (limit: 4705) Memory: 22.8M CGroup: /system.slice/google-osconfig-agent.service └─569 /usr/bin/google_osconfig_agent Hirsute: google-osconfig-agent 20210608.1-0ubuntu1~21.04.0 systemctl status google-osconfig-agent ● google-osconfig-agent.service - Google OSConfig Agent Loaded: loaded (/lib/systemd/system/google-osconfig-agent.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-09-22 20:07:17 UTC; 4 days ago Main PID: 579 (google_osconfig) Tasks: 8 (limit: 4700) Memory: 22.4M CGroup: /system.slice/google-osconfig-agent.service └─579 /usr/bin/google_osconfig_agent ** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-hirsute ** Tags added: verification-done-bionic verification-done-focal 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/1938553 Title: Please update to upstream release 20210608.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/1938553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945234] Re: Snapped apps are unable to trigger mate-notification-daemon
The attachment "add-upstream-patch.patch" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue 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/1945234 Title: Snapped apps are unable to trigger mate-notification-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-notification-daemon/+bug/1945234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938440] Re: Please update gce-compute-image-packages to 20210629.00
## Conclusion Due to the completion of Google's testing and my own verification, I am marking verification-complete for all releases. ## Notes Testing of the new Google guest agents was primarily performed by Google themselves. They have given the +1. In addition, these images have gone through testing from the Canonical Public Cloud team. From my own testing images were produced with the guest agents directly from proposed and uploaded to GCE. These are the same images that Google used in their own testing. I verified: 1) The versions of packages 3) that my account and other project accounts were created 4) correct SSH keys were imported 5) the new packages provided parity with the existing agents. Verified with the following package versions: Bionic: google-compute-engine 20210629.00-0ubuntu1~18.04.0 Focal: google-compute-engine 20210629.00-0ubuntu1~20.04.0 Hirsute: google-compute-engine 20210629.00-0ubuntu1~21.04.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938440 Title: Please update gce-compute-image-packages to 20210629.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1938440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945234] Re: Snapped apps are unable to trigger mate-notification-daemon
** Patch added: "*jsut* the upstream patch without the debian changelog mod" https://bugs.launchpad.net/ubuntu/+source/mate-notification-daemon/+bug/1945234/+attachment/5528515/+files/1001-snapped-apps-fix.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945234 Title: Snapped apps are unable to trigger mate-notification-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-notification-daemon/+bug/1945234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945234] Re: Snapped apps are unable to trigger mate-notification-daemon
** Patch added: "add-upstream-patch.patch" https://bugs.launchpad.net/ubuntu/+source/mate-notification-daemon/+bug/1945234/+attachment/5528514/+files/add-upstream-patch.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945234 Title: Snapped apps are unable to trigger mate-notification-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-notification-daemon/+bug/1945234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850667] Re: Switch to "unified" cgroup hierarchy (cgroupv2)
This bug was fixed in the package systemd - 248.3-1ubuntu7 --- systemd (248.3-1ubuntu7) impish; urgency=medium * d/tests/tests-in-lxd: suppress the cgroups v2 warning on stderr from lxd/lxc even more comprehensively until the snapd change required to do it nicely gets into a release. -- Michael Hudson-Doyle Wed, 01 Sep 2021 19:21:58 +1200 ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: Switch to "unified" cgroup hierarchy (cgroupv2) To manage notifications about this bug go to: https://bugs.launchpad.net/lxc/+bug/1850667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed
This bug was fixed in the package zfs-linux - 2.0.6-1ubuntu2 --- zfs-linux (2.0.6-1ubuntu2) impish; urgency=medium * Revert workaround on fill locked flag patch (LP: #1906476) - disable 4701-enable-ARC-FILL-LOCKED-flag.patch as this is causing zfs_node.c panics -- Colin Ian King Sun, 26 Sep 2021 12:59:43 +0100 ** Changed in: zfs-linux (Ubuntu Impish) 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/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed
If the issue doesn't affect hirsute then it should be possible to update an impish system by chroot from hirsute media, I would think. I've been booting up only occasionally this past week when I need to access something, but I find that apt, or possibly initramfs, updates seem to trigger the issue for me and render my system unbootable. I've been recovering with zfs rollback from hirsute media. Unfortunately, something also seems to go wrong with the zsys recovery entries in grub, where I end up with a dataset called rpool/ROOT/ubuntu_ (no trailing unique ID). I'll file that as a separate bug if it persists after this is resolved, though. Anyway, I plan to try to chroot and update later and I'll report back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed
Actually, I realize I may have been overconfident about that. Should it work to fix from a chroot or is the fix in the userland tools such that a chroot from hirsute would not help due to an issue in the userland ZFS tools under the chroot? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914740] Re: IPs are not assigned for Hipersockets in DHCP mode
This bug was fixed in the package systemd - 248.3-1ubuntu7 --- systemd (248.3-1ubuntu7) impish; urgency=medium * d/tests/tests-in-lxd: suppress the cgroups v2 warning on stderr from lxd/lxc even more comprehensively until the snapd change required to do it nicely gets into a release. -- Michael Hudson-Doyle Wed, 01 Sep 2021 19:21:58 +1200 ** Changed in: systemd (Ubuntu Impish) 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/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929184] Re: [21.10 FEAT] RoCE: Predictable Interface Names - systemd part
This bug was fixed in the package systemd - 248.3-1ubuntu7 --- systemd (248.3-1ubuntu7) impish; urgency=medium * d/tests/tests-in-lxd: suppress the cgroups v2 warning on stderr from lxd/lxc even more comprehensively until the snapd change required to do it nicely gets into a release. -- Michael Hudson-Doyle Wed, 01 Sep 2021 19:21:58 +1200 ** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929184 Title: [21.10 FEAT] RoCE: Predictable Interface Names - systemd part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934981] Re: systemctl suspend-then-hibernate attempts hybrid-sleep instead
This bug was fixed in the package systemd - 248.3-1ubuntu7 --- systemd (248.3-1ubuntu7) impish; urgency=medium * d/tests/tests-in-lxd: suppress the cgroups v2 warning on stderr from lxd/lxc even more comprehensively until the snapd change required to do it nicely gets into a release. -- Michael Hudson-Doyle Wed, 01 Sep 2021 19:21:58 +1200 ** Changed in: systemd (Ubuntu Impish) 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/1934981 Title: systemctl suspend-then-hibernate attempts hybrid-sleep instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938259] Re: Add ACCEL_LOCATION=base property for Dell clamshell models
This bug was fixed in the package systemd - 248.3-1ubuntu7 --- systemd (248.3-1ubuntu7) impish; urgency=medium * d/tests/tests-in-lxd: suppress the cgroups v2 warning on stderr from lxd/lxc even more comprehensively until the snapd change required to do it nicely gets into a release. -- Michael Hudson-Doyle Wed, 01 Sep 2021 19:21:58 +1200 ** Changed in: systemd (Ubuntu Impish) Status: Won't Fix => 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/1938259 Title: Add ACCEL_LOCATION=base property for Dell clamshell models To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1938259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940635] Re: systemd-networkd failing to acquire a DHCP6 lease from dnsmasq on armhf
This bug was fixed in the package systemd - 248.3-1ubuntu7 --- systemd (248.3-1ubuntu7) impish; urgency=medium * d/tests/tests-in-lxd: suppress the cgroups v2 warning on stderr from lxd/lxc even more comprehensively until the snapd change required to do it nicely gets into a release. -- Michael Hudson-Doyle Wed, 01 Sep 2021 19:21:58 +1200 ** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940635 Title: systemd-networkd failing to acquire a DHCP6 lease from dnsmasq on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1940635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942113] Re: systemd unit test regression in autopkgtest (oomd-utils)
This bug was fixed in the package systemd - 248.3-1ubuntu7 --- systemd (248.3-1ubuntu7) impish; urgency=medium * d/tests/tests-in-lxd: suppress the cgroups v2 warning on stderr from lxd/lxc even more comprehensively until the snapd change required to do it nicely gets into a release. -- Michael Hudson-Doyle Wed, 01 Sep 2021 19:21:58 +1200 ** Changed in: systemd (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942113 Title: systemd unit test regression in autopkgtest (oomd-utils) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1942113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945006] Re: re-sync to debian zfs-2.0.6 point release
This bug was fixed in the package zfs-linux - 2.0.6-1ubuntu2 --- zfs-linux (2.0.6-1ubuntu2) impish; urgency=medium * Revert workaround on fill locked flag patch (LP: #1906476) - disable 4701-enable-ARC-FILL-LOCKED-flag.patch as this is causing zfs_node.c panics -- Colin Ian King Sun, 26 Sep 2021 12:59:43 +0100 ** Changed in: zfs-linux (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/1945006 Title: re-sync to debian zfs-2.0.6 point release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1945006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941990] Re: Nové návrhy na překlad v balíku slideshow-ubuntu-mate
Přidal jsem návrhy i pro další odnože: https://translations.launchpad.net/ubuntu/impish/+source/ubiquity- slideshow-ubuntu/+pots/ubiquity-slideshow-xubuntu https://translations.launchpad.net/ubuntu/impish/+source/ubiquity- slideshow-ubuntu/+pots/ubiquity-slideshow-lubuntu https://translations.launchpad.net/ubuntu/impish/+source/ubiquity- slideshow-ubuntu/+pots/slideshow-ubuntu-budgie https://translations.launchpad.net/ubuntu/impish/+source/ubiquity- slideshow-ubuntu/+pots/slideshow-oem-config-ubuntu-budgie https://translations.launchpad.net/ubuntu/impish/+source/ubiquity- slideshow-ubuntu/+pots/ubiquity-slideshow-ubuntustudio https://translations.launchpad.net/ubuntu/impish/+source/ubiquity- slideshow-ubuntu/+pots/slideshow-ubuntukylin https://translations.launchpad.net/ubuntu/impish/+source/ubiquity- slideshow-ubuntu/+pots/ubiquity-slideshow-ubuntu-gnome -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941990 Title: Nové návrhy na překlad v balíku slideshow-ubuntu-mate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-cs/+bug/1941990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944468] Re: Electron applications all crash upon launch
I can confirm @mwhudson's glibc build from https://launchpad.net/~mwhudson/+archive/ubuntu/devirt fixed the issue for me as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944468 Title: Electron applications all crash upon launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1944468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921137] Re: mount.ocfs2 causes kernel BUG at lib/string.c:1149!
More details and proposed patch for the mount bug is here: https://lore.kernel.org/lkml/20210927154459.15976-1-vvidic@valentin- vidic.from.hr/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921137 Title: mount.ocfs2 causes kernel BUG at lib/string.c:1149! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1921137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945225] Re: udev produces unpredictable net names when PCI device is a bridge
** Changed in: systemd (Ubuntu Impish) Status: New => Fix Released ** Changed in: systemd (Ubuntu Hirsute) Status: New => Fix Released ** Changed in: systemd (Ubuntu Focal) Status: New => In Progress ** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => dann frazier (dannf) ** Description changed: [Impact] udev can produce unpredictable network interface names by default when multiple devices map to the same slot due to an intermediate bridge. On an Nvidia DGX2 system, I see the following when booting a system with udev 245.4-4ubuntu3.13: ubuntu@akis:~$ ls /sys/class/net enp134s0f0 enp6s0 ens103 ens107 eth3 eth9 enp134s0f1 ens102 ens106 eth1eth7 lo For each ens* device, there is a sibling eth* device that maps to the same slot because both devices are behind the same bridge. Unpredictable names present well known problems, but I'll describe a specific issue I'm having. We currently do automated network testing that MAAS deploys a system and then configures 2 specific NICs on the system. While MAAS does take care to always restore the names used during commissioning (eth3 will always be the same NIC on every deploy), these names can change each time the system is commissioned. So today we need to go in and edit the NIC names manually in MAAS any time the system is re-commissioned. + [Test Case] + Boot with kernel option net.naming-scheme=v247; verify that all network interfaces receive predictable names. + [Fix] This issue was addressed upstream by adding a new v247 naming scheme that detects this scenario and disables usage of slot-based names for these devices. Obviously changing the default naming scheme in a released LTS series could break users. However, we could introduce the v247 scheme in a focal SRU, and keep the default scheme of v245 (via -Ddefault-net-naming-scheme=v245). Users impacted by this could then opt-in to the v247 scheme by passing net.naming-scheme=v247 or net.naming-scheme=latest on the kernel command line. I could add this to DGX2 systems via a kernel_opts MAAS tag to always get predictable names during commissioning. [Regression Risk] This would change the behavior of any users who select net.naming-scheme=latest, since the latest will now be v247 and not v245. I'm not sure why an existing Ubuntu user would be doing that though - AFAICT, Ubuntu currently always defaults to the latest scheme. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945225 Title: udev produces unpredictable net names when PCI device is a bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1945225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926442] Re: [SRU] cannot execute 'netplan generate' from within a snap
** Changed in: netplan.io (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** Changed in: netplan.io (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/1926442 Title: [SRU] cannot execute 'netplan generate' from within a snap To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1926442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945234] [NEW] Snapped apps are unable to trigger mate-notification-daemon
Public bug reported: From https://forum.snapcraft.io/t/snapd-doesnt-allow-notification- daemon-to-be-activatable/22912 Snapped applications are unable to trigger the mate-notification-daemon due to the service file not specifying an assumed apparmor label so apparmor does not know that it is unconfined and thus may receive the dbus calls. Snapd specifies in the apparmor policy that the label must be "unconfined". I've filed an upstream PR to fix this at https://github.com/mate- desktop/mate-notification-daemon/pull/201 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: mate-notification-daemon 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon Sep 27 20:05:15 2021 InstallationDate: Installed on 2021-09-21 (6 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Beta amd64 (20210921) SourcePackage: mate-notification-daemon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mate-notification-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945234 Title: Snapped apps are unable to trigger mate-notification-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-notification-daemon/+bug/1945234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945234] Re: Snapped apps are unable to trigger mate-notification-daemon
This likely affects all of Impish, Hirsute, Focal, Bionic, and Xenial but I haven't validated the earlier releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945234 Title: Snapped apps are unable to trigger mate-notification-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-notification-daemon/+bug/1945234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931004] Re: Add support for Pacific to RBD driver
Reviewed: https://review.opendev.org/c/openstack/cinder/+/809190 Committed: https://opendev.org/openstack/cinder/commit/7fd4d46a8ea1fa18cc641845ec932b84e45c4657 Submitter: "Zuul (22348)" Branch:stable/train commit 7fd4d46a8ea1fa18cc641845ec932b84e45c4657 Author: Jon Bernard Date: Wed Apr 14 11:14:13 2021 -0400 RBD: use correct stripe unit in clone operation The recent release of Ceph Pacific saw a change to the clone() logic where invalid values of stripe unit would cause an error to be returned where previous versions would correct the value at runtime. This becomes a problem when creating a volume from an image, where the source RBD image may have a larger stripe unit than cinder's RBD driver is configured for. When this happens, clone() is called with a stripe unit that is too small given that of the source image and the clone fails. The RBD driver in Cinder has a configuration parameter 'rbd_store_chunk_size' that stores the preferred object size for cloned images. If clone() is called without a stripe_unit passed in, the stripe unit defaults to the object size, which is 4MB by default. The issue arises when creating a volume from a Glance image, where Glance is creating images with a default stripe unit of 8MB (distinctly larger than that of Cinder). If we do not consider the incoming stripe unit and select the larger of the two, Ceph cannot clone an RBD image with a smaller stripe unit and raises an error. This patch adds a function in our driver's clone logic to select the larger of the two stripe unit values so that the appropriate stripe unit is chosen. It should also be noted that we're determining the correct stripe unit, but using the 'order' argument to clone(). Ceph will set the stripe unit equal to the object size (order) by default and we rely on this behaviour for the following reason: passing stripe-unit alone or with an order argument causes an invalid argument exception to be raised in pre-pacific releases of Ceph, as it's argument parsing appears to have limitations. Closes-Bug: #1931004 Change-Id: Iec111ab83e9ed8182c9679c911e3d90927d5a7c3 (cherry picked from commit 49a2c85eda9fd3cddc75fd904fe62c87a6b50735) (cherry picked from commit 5db58159feec3d2d39d1abf3637310f5ac60a3cf) Conflicts: cinder/tests/unit/volume/drivers/test_rbd.py (cherry picked from commit 07ead73eec0ac6b962b533b07861d6a81226fa37) (cherry picked from commit 06b32da4be8b69e626eb7eb8091f695cbdcd92e7) Conflicts: cinder/tests/unit/volume/drivers/test_rbd.py ** Tags added: in-stable-train -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931004 Title: Add support for Pacific to RBD driver To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1931004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945015] Re: link for opening release notes no longer works
This bug was fixed in the package ubiquity - 21.10.6 --- ubiquity (21.10.6) impish; urgency=medium [ Didier Roche ] * debian/ubiquity.templates: fix formatting of error message to not contain markup [ Olivier Tilloy ] * ubiquity/frontend/gtk_ui.py, ubiquity/misc.py, debian/control: use xdg-open instead of sensible-browser to open the release notes and other hyperlinks consistently (LP: #1945015) [ Yuan-Chen Cheng ] * bin/ubiquity: add pre-install hookdir for oem-config mode -- Olivier Tilloy Mon, 27 Sep 2021 15:14:25 +0200 ** Changed in: ubiquity (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/1945015 Title: link for opening release notes no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1945015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942633] Re: Can not boot impish in Cavium ThunderX
The patch was merged into 5.13.0-17.17, which is currently in impish-proposed. At some point it should promulgate to the release pocket. You can view the status here: https://launchpad.net/ubuntu/+source/linux I don't know how long after that it will before it appears in images. As a workaround, you can test with kpti=off on the kernel command line. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942633 Title: Can not boot impish in Cavium ThunderX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945013] Re: mysql imposes a silent limit on passwords
It might also be worth fixing debconf to reject any password that MySQL will reject. But that can only be done if upstream have clear documentation so that the debconf script can accurately predict that, so this needs Sergio's point above addressed first before any progress can be made in packaging. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945013 Title: mysql imposes a silent limit on passwords To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1945013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944621] Re: sshd in chroot has regression with glibc 2.34
This patch moves the configuration option to the appropriate section of d/rules and adds a reference to this bug report. ** Patch added: "lp1944621.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1944621/+attachment/5528491/+files/lp1944621.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944621 Title: sshd in chroot has regression with glibc 2.34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1944621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875172] Re: geoclue polls wpasupplicant SSID list too often, resulting in lag and packet loss
This was a problem for me as well with a RTL8821CE card on my laptop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875172 Title: geoclue polls wpasupplicant SSID list too often, resulting in lag and packet loss To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1875172/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta/5.4.0.89.93)
All autopkgtests for the newly accepted linux-meta (5.4.0.89.93) for focal have finished running. The following regressions have been reported in tests triggered by the package: lxc/1:4.0.6-0ubuntu1~20.04.1 (arm64) backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64, ppc64el, arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926442] Re: [SRU] cannot execute 'netplan generate' from within a snap
Hello Lukas, or anyone else affected, Accepted netplan.io into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/netplan.io/0.99-0ubuntu3~18.04.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: netplan.io (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926442 Title: [SRU] cannot execute 'netplan generate' from within a snap To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1926442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.11/5.11.0.37.41~20.04.16)
All autopkgtests for the newly accepted linux-meta-hwe-5.11 (5.11.0.37.41~20.04.16) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/245.4-4ubuntu3.13 (s390x, ppc64el, amd64) nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 (amd64) backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (ppc64el, arm64, amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-hwe-5.11 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945225] Re: udev produces unpredictable net names when PCI device is a bridge
** Also affects: systemd (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Impish) Importance: Undecided Status: New ** Description changed: [Impact] udev can produce unpredictable network interface names by default when multiple devices map to the same slot due to an intermediate bridge. On an Nvidia DGX2 system, I see the following when booting a system with udev 245.4-4ubuntu3.13: ubuntu@akis:~$ ls /sys/class/net enp134s0f0 enp6s0 ens103 ens107 eth3 eth9 enp134s0f1 ens102 ens106 eth1eth7 lo For each ens* device, there is a sibling eth* device that maps to the same slot because both devices are behind the same bridge. Unpredictable names present well known problems, but I'll describe a specific issue I'm having. We currently do automated network testing that MAAS deploys a system and then configures 2 specific NICs on the system. While MAAS does take care to always restore the names used during commissioning (eth3 will always be the same NIC on every deploy), these names can change each time the system is commissioned. So today we need to go in and edit the NIC names manually in MAAS any time the system is re-commissioned. [Fix] This issue was addressed upstream by adding a new v247 naming scheme that detects this scenario and disables usage of slot-based names for these devices. Obviously changing the default naming scheme in a released LTS series could break users. However, we could introduce the v247 scheme in a focal SRU, and keep the default scheme of v245 (via -Ddefault-net-naming-scheme=v245). Users impacted by this could then opt-in to the v247 scheme by passing net.naming-scheme=v247 or net.naming-scheme=latest on the kernel command line. I could add this to DGX2 systems via a kernel_opts MAAS tag to always get predictable names during commissioning. [Regression Risk] - This would change the behavior of any users who select net.naming-scheme=latest. I'm not sure why an existing Ubuntu user would be doing that though - AFAICT, Ubuntu currently always defaults to the latest scheme. + This would change the behavior of any users who select net.naming-scheme=latest, since the latest will now be v247 and not v245. I'm not sure why an existing Ubuntu user would be doing that though - AFAICT, Ubuntu currently always defaults to the latest scheme. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945225 Title: udev produces unpredictable net names when PCI device is a bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1945225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940400] Update Released
The verification of the Stable Release Update for linux-firmware-raspi2 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940400 Title: [SRU] Pi 4B 2GB boot failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1940400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940400] Re: [SRU] Pi 4B 2GB boot failure
This bug was fixed in the package linux-firmware-raspi2 - 4-0ubuntu0~18.04.1 --- linux-firmware-raspi2 (4-0ubuntu0~18.04.1) bionic; urgency=medium * Backport to bionic (LP: #1940400) - Removed Breaks on flash-kernel and reinstated postinst to install boot firmware - Added diversions for all wifi firmware blobs - New upstream boot firmware release, 1.20210303 - New upstream bluetooth firmware release, 1.2-4+rpt8 [ Phil Elwell ] - Second Spectra fix for CYW43455 (CVE-2020-10370) - Original firmware name: BCM4345C0_003.001.025.0174.0342.hcd - New upstream wifi firmware release, 1:20190114-1+rpt11 [ Serge Schneider ] - Update CYW43455 firmware - brcm/brcmfmac43455-sdio.bin 7.45.229 - See: https://github.com/raspberrypi/linux/issues/3849 -- Dave Jones Tue, 31 Aug 2021 15:43:35 +0100 ** Changed in: linux-firmware-raspi2 (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Bug watch added: github.com/raspberrypi/linux/issues #3849 https://github.com/raspberrypi/linux/issues/3849 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-10370 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940400 Title: [SRU] Pi 4B 2GB boot failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1940400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943160] Re: [SRU] It will take about 90+ seconds to open the 'Nvidia settings' app when 'Power Saving mode' running.
This bug was fixed in the package nvidia-settings - 470.57.01-0ubuntu0.21.04.2 --- nvidia-settings (470.57.01-0ubuntu0.21.04.2) hirsute; urgency=medium * debian/patches/17_do_not_read_config_on_power_saving_mode.patch: - Do not read config on Power Saving mode. (LP: #1943160). -- Shengyao Xue Fri, 10 Sep 2021 00:31:29 +0800 ** Changed in: nvidia-settings (Ubuntu Hirsute) 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/1943160 Title: [SRU] It will take about 90+ seconds to open the 'Nvidia settings' app when 'Power Saving mode' running. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945230] [NEW] System doesn't seem to recognize WiFi card yet Bluetooth works
Public bug reported: I've also downloaded rtl8821ce-v5.5.2_34066.20200325 and installed it. The system is still insisting on 5.5.1. I'm following the instructions in the forums and not getting any satisfactory results. I had to sudo copy dkms.conf into the 5.5.2 folder in order for it to continue and say it doesn't exist. This is its latest results: sudo /home/~/rtl8821ce-master/dkms-install.sh About to run dkms install steps... Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area...(bad exit status: 2) 'make' -j4 KVER=5.11.0-36-generic...(bad exit status: 2) ERROR (dkms apport): binary package for rtl8821ce: v5.5.2_34066.20200325 not found Error! Bad return status for module build on kernel: 5.11.0-36-generic (x86_64) Consult /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/make.log for more information. Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area...(bad exit status: 2) 'make' -j4 KVER=5.11.0-36-generic...(bad exit status: 2) ERROR (dkms apport): binary package for rtl8821ce: v5.5.2_34066.20200325 not found Error! Bad return status for module build on kernel: 5.11.0-36-generic (x86_64) Consult /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/make.log for more information. Finished running dkms install steps. I'll keep trying on my end and will update when appropriate. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtl8821ce-dkms 5.5.2.1-0ubuntu4~20.04.3 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Sep 27 10:38:35 2021 InstallationDate: Installed on 2021-09-22 (4 days ago) InstallationMedia: Ubuntu-Budgie 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210210.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rtl8821ce UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rtl8821ce (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal rtl8821 ** Description changed: I've also downloaded rtl8821ce-v5.5.2_34066.20200325 and installed it. The system is still insisting on 5.5.1. I'm following the instructions in the forums and not getting any satisfactory results. I had to sudo copy dkms.conf into the 5.5.2 folder in order for it to continue and say it doesn't exist. This is its latest results: - udo /home/~/rtl8821ce-master/dkms-install.sh + sudo /home/~/rtl8821ce-master/dkms-install.sh About to run dkms install steps... Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area...(bad exit status: 2) 'make' -j4 KVER=5.11.0-36-generic...(bad exit status: 2) ERROR (dkms apport): binary package for rtl8821ce: v5.5.2_34066.20200325 not found Error! Bad return status for module build on kernel: 5.11.0-36-generic (x86_64) Consult /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/make.log for more information. Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area...(bad exit status: 2) 'make' -j4 KVER=5.11.0-36-generic...(bad exit status: 2) ERROR (dkms apport): binary package for rtl8821ce: v5.5.2_34066.20200325 not found Error! Bad return status for module build on kernel: 5.11.0-36-generic (x86_64) Consult /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/make.log for more information. Finished running dkms install steps. I'll keep trying on my end and will update when appropriate. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtl8821ce-dkms 5.5.2.1-0ubuntu4~20.04.3 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Sep 27 10:38:35 2021 InstallationDate: Installed on 2021-09-22 (4 days ago) InstallationMedia: Ubuntu-Budgie 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210210.1) PackageArchitecture: all ProcEnviron: - LANGUAGE=en_US - TERM=xterm-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: rtl8821ce UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945230 Title: System doesn't seem to recognize WiFi card yet Bluetooth works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1945230/+subscriptions -- ubuntu-bugs mailin
[Bug 1938920] Update Released
The verification of the Stable Release Update for netplan.io has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938920 Title: [SRU] Update to netplan.io 0.103 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1938920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938920] Re: [SRU] Update to netplan.io 0.103
This bug was fixed in the package netplan.io - 0.103-0ubuntu5~20.04.1 --- netplan.io (0.103-0ubuntu5~20.04.1) focal; urgency=medium * Backport netplan.io 0.103-0ubuntu5 to 20.04 (LP: #1938920) - Add YAML generator and Keyfile parser for NetworkManager YAML backend - Add activation-mode parameter - Add io.netplan.Netplan.Generate() DBus method - Changed the way of how unmanaged-devices are handled by NetworkManager * Add d/p/0003-Mute-gateway4-6-deprecation-warnings.patch: - Do not show a deprecation warning on the backported version * Update systemd dependency to >= 245.4-4ubuntu3.8 for activation-mode * Update debian/gbp.conf * Use debhelper-compat 12 in debian/control * Keep riscv64 build-time tests disabled -- Lukas Märdian Tue, 07 Sep 2021 10:53:10 +0200 ** Changed in: netplan.io (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/1938920 Title: [SRU] Update to netplan.io 0.103 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1938920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938920] Re: [SRU] Update to netplan.io 0.103
This bug was fixed in the package netplan.io - 0.103-0ubuntu5~21.04.1 --- netplan.io (0.103-0ubuntu5~21.04.1) hirsute; urgency=medium * Backport netplan.io 0.103-0ubuntu5 to 21.04 (LP: #1938920) - Add YAML generator and Keyfile parser for NetworkManager YAML backend - Add activation-mode parameter - Add io.netplan.Netplan.Generate() DBus method - Changed the way of how unmanaged-devices are handled by NetworkManager * Add d/p/0003-Mute-gateway4-6-deprecation-warnings.patch: - Do not show a deprecation warning on the backported version * Update systemd dependency to >= 247.3-3ubuntu3.2 for activation-mode * Update debian/gbp.conf * Use debhelper-compat 12 in debian/control * Keep skipping many armhf/LXD tests * Skip flaky 'regressions' test on armhf/LXD containers, too -- Lukas Märdian Tue, 07 Sep 2021 10:50:30 +0200 ** Changed in: netplan.io (Ubuntu Hirsute) 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/1938920 Title: [SRU] Update to netplan.io 0.103 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1938920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774249] Re: update_available_resource will raise DiskNotFound after resize but before confirm
An updated package for nova in Ubuntu has been uploaded to the bionic unapproved queue: https://launchpad.net/ubuntu/bionic/+queue?queue_state=1&queue_text=nova -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774249 Title: update_available_resource will raise DiskNotFound after resize but before confirm To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1774249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943160] Re: [SRU] It will take about 90+ seconds to open the 'Nvidia settings' app when 'Power Saving mode' running.
This bug was fixed in the package nvidia-settings - 470.57.01-0ubuntu0.20.04.2 --- nvidia-settings (470.57.01-0ubuntu0.20.04.2) focal; urgency=medium * debian/patches/17_do_not_read_config_on_power_saving_mode.patch: - Do not read config on Power Saving mode. (LP: #1943160). -- Shengyao Xue Fri, 10 Sep 2021 00:42:38 +0800 ** Changed in: nvidia-settings (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/1943160 Title: [SRU] It will take about 90+ seconds to open the 'Nvidia settings' app when 'Power Saving mode' running. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885403] Update Released
The verification of the Stable Release Update for postfix has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885403 Title: posttls-finger fails to connect to private/tlsmgr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1885403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885403] Re: posttls-finger fails to connect to private/tlsmgr
This bug was fixed in the package postfix - 3.4.13-0ubuntu1.2 --- postfix (3.4.13-0ubuntu1.2) focal; urgency=medium * d/rules: Removed LDFLAG -Bsymbolic-functions (LP: #1885403). -- Miriam España Acebal Tue, 07 Sep 2021 08:58:01 +0200 ** Changed in: postfix (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/1885403 Title: posttls-finger fails to connect to private/tlsmgr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1885403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885403] Re: posttls-finger fails to connect to private/tlsmgr
This bug was fixed in the package postfix - 3.5.6-1ubuntu0.2 --- postfix (3.5.6-1ubuntu0.2) hirsute; urgency=medium * d/rules: Removed LDFLAG -Bsymbolic-functions (LP: #1885403). -- Miriam España Acebal Tue, 07 Sep 2021 11:36:44 +0200 ** Changed in: postfix (Ubuntu Hirsute) 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/1885403 Title: posttls-finger fails to connect to private/tlsmgr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1885403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942633] Re: Can not boot impish in Cavium ThunderX
Thanks a lot dann. I dont know the release process of the kernel, and when our public images are generated by CPC. I have to test it when is uploaded here: https://images.maas.io/ephemeral-v3/candidate/impish/arm64/ Do you have any tip about how to be aware when this should happen? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942633 Title: Can not boot impish in Cavium ThunderX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943160] Update Released
The verification of the Stable Release Update for nvidia-settings has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943160 Title: [SRU] It will take about 90+ seconds to open the 'Nvidia settings' app when 'Power Saving mode' running. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else
I think I have occasionally observed this problem, although I wasn't sure which component was at fault. I cannot seem to find an upstream bug tracking this issue, would you mind filing one at https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CFirefox, and sharing the link to it here? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913775 Title: Copy from Firefox Wayland fails to be pasted anywhere else To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1913775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943623] Update Released
The verification of the Stable Release Update for stress-ng has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943623 Title: system-info.version in YAML output needs ' ' quoting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1943623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943623] Re: system-info.version in YAML output needs ' ' quoting
This bug was fixed in the package stress-ng - 0.12.06-1ubuntu1
---
stress-ng (0.12.06-1ubuntu1) hirsute; urgency=medium
* Quote the system-info.version value in YAML metrics (LP: #1943623)
- upstream commit a52f236917f5 ("core-helper: Quote the
system-info.version value in YAML metrics")
-- Colin King Tue, 14 Sep 2021 18:08:14
+0100
** Changed in: stress-ng (Ubuntu Hirsute)
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/1943623
Title:
system-info.version in YAML output needs ' ' quoting
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1943623/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943623] Re: system-info.version in YAML output needs ' ' quoting
** Changed in: stress-ng (Ubuntu Impish) 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/1943623 Title: system-info.version in YAML output needs ' ' quoting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1943623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] Re: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611)
I found the following link: https://forum.manjaro.org/t/new-install-amd-fx-6300-wont-wake-from-suspend/39471/10 Suggesting that setting TearFree on may help (RS780L) However... I wonder if ShadowPrimary did not help. Section "Device" Identifier "Radeon" Driver "radeon" Option "AccelMethod" "glamor" #legacy "exa" Option "DRI" "3" #legacy "2" Option "TearFree" "on" Option "ColorTiling" "on" Option "ColorTiling2D" "on" Option "ShadowPrimary" "on" #only possible with "glamor" AccelMethod EndSection Note that it should be in a file /usr/share/X11/xorg.conf.d/20-radeon.conf on Ubuntu. And should rename my suggested /etc/X11/xorg.conf to xorg.conf.old. I might have temporary access to the computer in the next 48h to test it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945060] Re: [snap] Firefox browser opens and then closes, but Chromium web browser does work fine.
Thank you for the report. Is this happening consistently, i.e. firefox is always crashing at startup? Could you please run the following commands in a terminal, and share the output here? snap info firefox snap connections firefox firefox -version Thanks in advance! ** Changed in: firefox (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/1945060 Title: [snap] Firefox browser opens and then closes, but Chromium web browser does work fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1945060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943623] Re: system-info.version in YAML output needs ' ' quoting
This bug was fixed in the package stress-ng - 0.11.07-1ubuntu1
---
stress-ng (0.11.07-1ubuntu1) focal; urgency=medium
* Quote the system-info.version value in YAML metrics (LP: #1943623)
- upstream commit a52f236917f5 ("core-helper: Quote the
system-info.version value in YAML metrics")
-- Colin King Tue, 14 Sep 2021 18:08:14
+0100
** Changed in: stress-ng (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/1943623
Title:
system-info.version in YAML output needs ' ' quoting
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1943623/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945031] Re: Thunderbird snap won't launch unless with offloading variable __NV_PRIME_RENDER_OFFLOAD=1
I don't have experience with NVIDIA Optimus, but according to https://wiki.debian.org/NVIDIA%20Optimus#Using_NVIDIA_PRIME_Render_Offload, and assuming it's up-to-date, it looks like passing those environment variables (__NV_PRIME_RENDER_OFFLOAD=1 and __GLX_VENDOR_LIBRARY_NAME=nvidia) is expected from the user. Has this changed? Is there a way for for a strictly-confined snap to detect that it's running with the PRIME profile, and set those variables accordingly, maybe? ** Tags added: snap ** Changed in: thunderbird (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/1945031 Title: Thunderbird snap won't launch unless with offloading variable __NV_PRIME_RENDER_OFFLOAD=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1945031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945227] [NEW] drm/amdgpu: Add support for Yellow Carp
Public bug reported: [Impact] New hardware support for AMD's Yellow Carp need five commits backported to mesa and new firmware. This is only needed on focal, skipping hirsute/impish (no kernel support there). [Test plan] Install updates, boot a YC machine and check that the desktop has full hardware acceleration. [Where problems could occur] The firmware is new, so it will simply add new files to l-f without any impact on others. Mesa adds five commits in total, and while some affect other chips, they mostly fix hw bugs or add a helper and such, hard to see what could go wrong. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Affects: mesa (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Affects: mesa (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Fix Committed ** Changed in: mesa (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945227 Title: drm/amdgpu: Add support for Yellow Carp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
