[Bug 1901344] Re: [SRU] Spotify album icon shows optimal CD disk instead of album/cover image
This looks good from a quick glance. What's the status of the bug in Hirsute? I appreciate you might not have been able to add bug tasks, but just a comment would help me create the tasks and set the status you state. To save review time, could you also prepare the Groovy debdiffs please? If the quilt patch files can be kept the same, then that really helps. But even if not, a reviewer can do both faster than two reviewers reviewing the two series separately at different times. ** Also affects: cinnamon (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: cinnamon-screensaver (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: cinnamon (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: cinnamon-screensaver (Ubuntu Groovy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901344 Title: [SRU] Spotify album icon shows optimal CD disk instead of album/cover image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1901344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908366] Re: Failed to load DMC firmware i915/tgl_dmc_ver2_08.bin
** Tags added: originate-from-1908228 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908366 Title: Failed to load DMC firmware i915/tgl_dmc_ver2_08.bin To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911113] [NEW] rtl8812au package is based on very old source, needs update
Public bug reported: I am concerned that the source being used for this driver is extremely dated. This came to my attention due to reports in wifi related forums. I have a Github site where I maintain a much more modern driver for the rtl8812au chipet. The driver is based on the Realtek source version 5.9.3.2 dated (2020-10-12). This version of the driver is only for the rtl8812au chipset. There is another driver for the rtl8821au/8811au. Both drivers in their maintained form can be found here. https://github.com/morrownr I am willing to assist the current maintainer in getting the new code into this package... actually we would need to add a new package to continue supporting the rtl8821au/8811au. My testing has shown this v5.9.3.2 rtl8812au driver to be the best driver I've ever seen out of Realtek. It is very good in station mode and outstanding in AP mode. Power saving just works and the log is clean. Regards. ** Affects: rtl8812au (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/193 Title: rtl8812au package is based on very old source, needs update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8812au/+bug/193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907686] Re: ovn: instance unable to retrieve metadata
Also see a few of these: 2021-01-12 06:48:21.947 52569 INFO eventlet.wsgi.server [-] 10.5.3.232, "GET /openstack HTTP/1.1" status: 500 len: 362 time: 0.0006430 2021-01-12 06:48:49.848 52569 ERROR neutron.agent.ovn.metadata.server [-] Unexpected error.: AttributeError: 'MetadataProxyHandler' object has no attribute 'sb_idl' 2021-01-12 06:48:49.848 52569 ERROR neutron.agent.ovn.metadata.server Traceback (most recent call last): 2021-01-12 06:48:49.848 52569 ERROR neutron.agent.ovn.metadata.server File "/usr/lib/python3/dist-packages/neutron/agent/ovn/metadata/server.py", line 67, in __call__ 2021-01-12 06:48:49.848 52569 ERROR neutron.agent.ovn.metadata.server instance_id, project_id = self._get_instance_and_project_id(req) 2021-01-12 06:48:49.848 52569 ERROR neutron.agent.ovn.metadata.server File "/usr/lib/python3/dist-packages/neutron/agent/ovn/metadata/server.py", line 84, in _get_instance_and_project_id 2021-01-12 06:48:49.848 52569 ERROR neutron.agent.ovn.metadata.server ports = self.sb_idl.get_network_port_bindings_by_ip(network_id, 2021-01-12 06:48:49.848 52569 ERROR neutron.agent.ovn.metadata.server AttributeError: 'MetadataProxyHandler' object has no attribute 'sb_idl' 2021-01-12 06:48:49.848 52569 ERROR neutron.agent.ovn.metadata.server Restarting the neutron-ovn-metadata-agent service resolves the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907686 Title: ovn: instance unable to retrieve metadata To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ovn-chassis/+bug/1907686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900141] Re: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120
Thanks! >> I noticed that in the list of affected packages in the bug metadata >> Bionic is not mentioned. Will the fix also be backported there? > > It depends on which kernel you are talking about. The bionic GA kernel > (4.15) was not affected based on my testing. If you are seeing problems > with it, please let me know. 4.15 was not affected indeed. > The bionic HWE kernel is derived from the kernel source in focal, so > that kernel does not need to be fixed separately from the focal kernel. Ok, just wanted to make sure this is the case. Everything is fine for me now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900141 Title: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911110] [NEW] On installation the error occured.
Public bug reported: No further info. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 11 22:28:39 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/190 Title: On installation the error occured. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898910] Re: gnome-shell crashes with [St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL)] called from DesktopGrid::_backgroundDestroyed() [desktopGrid.js:206
It looks fairly likely that https://gitlab.gnome.org/World/ShellExtensions/desktop- icons/-/merge_requests/191 already fixed the only possible root cause of this. I can't be sure because I still can't reproduce it. Regardless, the related gnome-shell fix should prevent all possible forms of the same mistake from crashing the shell: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1507 ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Groovy) Status: Confirmed => Won't Fix ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Hirsute) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898910 Title: gnome-shell crashes with [St:ERROR:../src/st/st- bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL)] called from DesktopGrid::_backgroundDestroyed() [desktopGrid.js:206] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1898910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905393] Re: Ubuntu 20.04: opal-prd fails to start on 20.04
--- Comment From hegdevas...@in.ibm.com 2021-01-12 01:25 EDT--- (In reply to comment #20) > Hello bugproxy, or anyone else affected, > > Accepted skiboot into groovy-proposed. The package will build now and be > available at > https://launchpad.net/ubuntu/+source/skiboot/6.5.2-1ubuntu0.20.10.1 in a few > hours, and then in the -proposed repository. > > Please help us by testing this new package. See > https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to > enable and use -proposed. Your feedback will aid us getting this update out > to other Ubuntu users. > > If this package fixes the bug for you, please add a comment to this bug, > mentioning the version of the package you tested, what testing has been > performed on the package and change the tag from verification-needed-groovy > to verification-done-groovy. If it does not fix the bug for you, please add > a comment stating that, and change the tag to verification-failed-groovy. 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. Thanks! Changes looks good. With this change we are able to start opal-prd daemon and co-worker fix also working fine. -Vasant ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905393 Title: Ubuntu 20.04: opal-prd fails to start on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1905393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910455] Re: Thunar and Nautilus USB drive ejecting takes long time
thanks, the log doesn't seem to have any useful clue though :-/ it's probably not a nautilus bug if other browsers have the same issue ** Changed in: nautilus (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910455 Title: Thunar and Nautilus USB drive ejecting takes long time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1910455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow
** Changed in: gnome-shell (Ubuntu Groovy)
Importance: Undecided => High
** Changed in: gnome-shell (Ubuntu Groovy)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Also affects: gnome-shell (Ubuntu Hirsute)
Importance: High
Assignee: Daniel van Vugt (vanvugt)
Status: 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/1897765
Title:
gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw
accounting") from meta_window_actor_thaw() from
WindowManager::_sizeChangedWindow
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897765/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 507089]
I can answer for 68.10.0 that the problem does not occur anymore (but our setup changed since then, additionally using kerberos) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/507089 Title: Thunderbird 3 (Shredder) always segfaults on startup with LDAP auth in nsswitch To manage notifications about this bug go to: https://bugs.launchpad.net/seamonkey/+bug/507089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882418] Re: spamprobe crashes on email containing images
Joseph: Your patch works for me! I applied it to the Ubuntu package and rebuilt it (i.e., retaining the existing configure options, compiler/linker flags, all the other patches, etc.), and it appears that the crashes I was seeing have gone away. Before: $ cat /tmp/junk.mbox | ./debian/spamprobe/usr/bin/spamprobe spam caught signal 11: quitting Aborted (core dumped) After: $ cat /tmp/junk.mbox | ./debian/spamprobe/usr/bin/spamprobe spam Thanks for creating the patch. I hope the spamprobe package maintainers are willing to apply it to the spamprobe package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882418 Title: spamprobe crashes on email containing images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamprobe/+bug/1882418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801267] Re: regina-normal crashes on startup
** Changed in: regina-normal (Ubuntu Bionic) Assignee: (unassigned) => Logan Rosen (logan) ** Changed in: regina-normal (Ubuntu Bionic) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801267 Title: regina-normal crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/regina-normal/+bug/1801267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911036] Re: GDK/GTK app crash when performing drag operation
It appears that crash report has not been retraced so does not have any useful debug info in it. I don't know if that's because of a missing core dump or because the infrastructure has failed (both are equally likely in my experience). If you would like to get to the bottom of the issue then I have three suggestions: * Add GDK_SYNCHRONIZE=1 to your /etc/environment file. It will make things slower but that's a necessary evil to debug the issue properly. * If you can open gnome-control-center then look in Privacy>Diagnostics and try enabling error reports. * Continue checking /var/crash for new files. If you have any old files in there that don't seem useful then please delete them. Sometimes old files will prevent new more useful crashes from being recorded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911036 Title: GDK/GTK app crash when performing drag operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1911036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"
This bug started affecting me a few weeks ago. It seems to happen whenever a new kernel version is pushed out. This time, what Ben did in #75 -- downgrading grub to 2.02+dfsg1-12ubuntu2.1 -- was the only thing that fixed it for me. I cannot remember exactly what fixed it for me the first time, but I did not have to downgrade grub - I believe installing an older kernel was what finally fixed it. I have a Dell XPS 15 9550, Ubuntu 20.04 installed with EFI, and a LUKS encrypted primary drive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853369 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1853369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801267] Re: regina-normal crashes on startup
** Also affects: regina-normal (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: regina-normal (Ubuntu) Status: New => Fix Released ** Changed in: regina-normal (Ubuntu Bionic) Status: New => Triaged ** Changed in: regina-normal (Ubuntu Bionic) Importance: Undecided => High ** Description changed: + [Impact] + This is a bug in Ubuntu 18.04 LTS. The application Regina (installed through the package regina-normal) will not start. The problem seems to be that it is linked against the graphviz plugins, which moved location (thus the executable can no longer find the libraries that it links against). The fix is simply to rebuild regina- normal, with no changes needed to the source. - To reproduce: + [Test Case] - Install the package regina-normal; - At a command line, type "regina-gui". The application crashes with the message: "regina-gui: error while loading shared libraries: libgvplugin_core.so.6: cannot open shared object file: No such file or directory" + + [Where problems could occur] + + It can't get much worse than how it is currently (not starting at all). + + --- + + From original description: Rebuilding regina-normal against the current Ubuntu 18.04 LTS causes the executable to be linked correctly, and the problem is fixed. This problem does *not* affect Ubuntu 18.10. It is only present in Ubuntu 18.04 LTS. I would be grateful if someone could please rebuild regina-normal on 18.04 and upload this to bionic-updates, and/or include the rebuild in the next point release (I presume 18.04.2). Thanks - Ben. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801267 Title: regina-normal crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/regina-normal/+bug/1801267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910859] Re: Sync biboumi 9.0-1 (universe) from Debian unstable (main)
This bug was fixed in the package biboumi - 9.0-1 Sponsored for Hans Joachim Desserud (hjd) --- biboumi (9.0-1) unstable; urgency=medium [ upstream ] * New release(s) (Closes: Bug#957037 and Bug#976356). -- Michel Le Bihan Sat, 19 Dec 2020 15:43:03 +0200 ** Changed in: biboumi (Ubuntu) Importance: Undecided => Wishlist ** Changed in: biboumi (Ubuntu) Assignee: (unassigned) => Logan Rosen (logan) ** Changed in: biboumi (Ubuntu) Status: New => In Progress ** Changed in: biboumi (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/1910859 Title: Sync biboumi 9.0-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/biboumi/+bug/1910859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882228] Re: tests fail on armhf
This bug was fixed in the package regina-normal - 6.0-1 --- regina-normal (6.0-1) unstable; urgency=low * New upstream release. * Bumped standards-version to 4.5.1 (no changes required). -- Ben Burton Sat, 9 Jan 2021 12:12:06 +1000 ** Changed in: regina-normal (Ubuntu) Assignee: (unassigned) => Logan Rosen (logan) ** Changed in: regina-normal (Ubuntu) Status: New => In Progress ** Changed in: regina-normal (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/1882228 Title: tests fail on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/regina-normal/+bug/1882228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910866] Re: nvme drive fails after some time
Andrew, since you can reliably reproduce the issue, can you please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11-rc3/amd64/ And we'll do a bisect or reverse-bisect based on the result. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910866 Title: nvme drive fails after some time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911036] Re: GDK/GTK app crash when performing drag operation
As this server is used heavily used, rebooting is not that convenient. Is there a way to force crashdb.conf to be reloaded? I tried restarting apport & whoopsie services with systemctl but not sure if that worked. There's a recent crash file for thunar that may or may not have been produced from the same issue. Though it oddly doesn't show up on my servers' error page, the url should be https://errors.ubuntu.com/oops/f9a43c4e-5076-11eb-8e16-fa163ee63de6 based on the contents of the .uploaded file. Unfortunately, I'm unable to check as I'm not a member of the appropriate group. Let me know what you find and if a reboot is absolutely necessary to get the crash file uploaded securely. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911036 Title: GDK/GTK app crash when performing drag operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1911036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644541] Re: Update stuck at “configuring unattended-upgrades”
[Expired for unattended-upgrades (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unattended-upgrades (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644541 Title: Update stuck at “configuring unattended-upgrades” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1644541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838258] Re: Unable to configure VLAN on an additional OSA interface
[Expired for iproute2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: iproute2 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838258 Title: Unable to configure VLAN on an additional OSA interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1838258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896137] Re: syslog flooded with "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7"
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896137 Title: syslog flooded with "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903941] Re: dcf
[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubiquity (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903941 Title: dcf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1903941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906256] Re: grub-install: error: cannot find EFI directory.
Windows requires MBR(msdos) partitioning for BIOS boot. Ubuntu will let you install in UEFI mode to MBR drive, but probably should not as Windows wants boot partition to be its partition with boot files (system), but UEFI wants boot flag on ESP - efi system partition. UEFI highly recommends gpt partitioning for UEFI, and Windows only installs in UEFI mode to gpt drives. Normal reinstall in different mode will erase drive. So if you attempt to reinstall Windows in UEFI mode, it will convert drive to gpt & totally erase drive. Or have good backups. Either reinstall Windows in UEFI mode since you have UEFI hardware. Microsoft has required vendors to install in UEFI mode to gpt partitioned drives since 2012 and release of Windows 8. Or only install Ubuntu in 40 year old BIOS/MBR configuration. How you boot install media, UEFI or BIOS is then how it installs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906256 Title: grub-install: error: cannot find EFI directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1906256/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888724] Re: usbauth: autopkgtest fails on Ubuntu
This was fixed by Steve in 1.0.2-2ubuntu1. ** Changed in: usbauth (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/1888724 Title: usbauth: autopkgtest fails on Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbauth/+bug/1888724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909603] Re: fwupd-refresh.service: Failed with result 'exit-code'
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fwupd (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/1909603 Title: fwupd-refresh.service: Failed with result 'exit-code' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1909603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911085] [NEW] no touchpad available in devices
Public bug reported: chris@jones-ideapad-il:~$ cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input4 U: Uniq= H: Handlers=rfkill kbd event4 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0003 Vendor=5986 Product=1135 Version=5408 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:00:14.0-5/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input5 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0003 Vendor=046d Product=4002 Version=0111 N: Name="Logitech K750" P: Phys=usb-:00:14.0-2/input2:1 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.2/0003:046D:C52B.0003/0003:046D:4002.0004/input/input22 U: Uniq=4002-09-1b-c4-72 H: Handlers=sysrq kbd event6 leds B: PROP=0 B: EV=12001f B: KEY=3f000301ff 0 0 48317aff32d bfd6 1 130ff38b17c007 7bfad941dfff ffbeffdfffef fffe B: REL=1040 B: ABS=1 B: MSC=10 B: LED=1f I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input23 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=046d Product=4082 Version=0111 N: Name="Logitech MX Master 3" P: Phys=usb-:00:14.0-2/input2:2 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.2/0003:046D:C52B.0003/0003:046D:4082.0005/input/input24 U: Uniq=4082-04-68-de-4f H: Handlers=sysrq kbd mouse0 event8 leds B: PROP=0 B: EV=120017 B: KEY= 10007 ff9f207ac14057ff febeffdfffef fffe B: REL=1943 B: MSC=10 B: LED=1f I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input25 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input26 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input27 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input28 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input29 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input30 U: Uniq= H: Handlers=event14 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input31 U: Uniq= H: Handlers=event15 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=11" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input32 U: Uniq= H: Handlers=event16 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=12" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input33 U: Uniq= H: Handlers=event17 B: PROP=0 B: EV=21 B: SW=140 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-36-generic 5.8.0-36.40~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5
[Bug 1909744] Re: FTBFS ring-clojure depends on itself
** Changed in: ring-clojure (Ubuntu) Assignee: (unassigned) => Logan Rosen (logan) ** Changed in: ring-clojure (Ubuntu) Importance: Undecided => High ** Changed in: ring-clojure (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909744 Title: FTBFS ring-clojure depends on itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ring-clojure/+bug/1909744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910636] Re: update icu-data which is bundled in tzdata to 2020f
The verification passed for focal.
bdmurray@clean-focal-amd64:~$ python3 -c "from datetime import datetime; from
icu import ICUtzinfo, TimeZone; tz = ICUtzinfo(TimeZone.create
TimeZone('Europe/Volgograd')); print(str(tz.utcoffset(datetime(2020, 12, 28"
4:00:00
bdmurray@clean-focal-amd64:~$ sudo apt-get install tzdata
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
tzdata
1 upgraded, 0 newly installed, 0 to remove and 91 not upgraded.
Need to get 296 kB of archives.
After this operation, 6,144 B of additional disk space will be used.
Get:1 http://192.168.10.7/ubuntu focal-proposed/main amd64 tzdata all
2020f-0ubuntu0.20.04.1 [296 kB]
Fetched 296 kB in 0s (6,181 kB/s)
Preconfiguring packages ...
(Reading database ... 223591 files and directories currently installed.)
Preparing to unpack .../tzdata_2020f-0ubuntu0.20.04.1_all.deb ...
Unpacking tzdata (2020f-0ubuntu0.20.04.1) over (2020d-0ubuntu0.20.04) ...
Setting up tzdata (2020f-0ubuntu0.20.04.1) ...
Current default time zone: 'America/Los_Angeles'
Local time is now: Mon Jan 11 19:15:47 PST 2021.
Universal Time is now: Tue Jan 12 03:15:47 UTC 2021.
Run 'dpkg-reconfigure tzdata' if you wish to change it.
bdmurray@clean-focal-amd64:~$ python3 -c "from datetime import datetime; from
icu import ICUtzinfo, TimeZone; tz = ICUtzinfo(TimeZone.create
TimeZone('Europe/Volgograd')); print(str(tz.utcoffset(datetime(2020, 12, 28"
3:00:00
** Tags removed: verification-needed verification-needed-focal
verification-needed-groovy
** Tags added: verification-done verification-done-focal
verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910636
Title:
update icu-data which is bundled in tzdata to 2020f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1910636/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910636] Re: update icu-data which is bundled in tzdata to 2020f
The verification passed for groovy.
bdmurray@clean-groovy-amd64:~$ python3 -c "from datetime import datetime; from
icu import ICUtzinfo, TimeZone; tz = ICUtzinfo(TimeZone.creat
eTimeZone('Europe/Volgograd')); print(str(tz.utcoffset(datetime(2020, 12,
28"
4:00:00
bdmurray@clean-groovy-amd64:~$ sudo apt-get install tzdata
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
ippusbxd libllvm10 libtepl-4-0 linux-headers-5.4.0-42
linux-headers-5.4.0-42-generic linux-image-5.4.0-42-generic
linux-modules-5.4.0-42-generic linux-modules-extra-5.4.0-42-generic
Use 'sudo apt autoremove' to remove them.
The following packages will be upgraded:
tzdata
1 upgraded, 0 newly installed, 0 to remove and 180 not upgraded.
Need to get 294 kB of archives.
After this operation, 6,144 B of additional disk space will be used.
Get:1 http://192.168.10.7/ubuntu groovy-proposed/main amd64 tzdata all
2020f-0ubuntu0.20.10.1 [294 kB]
Fetched 294 kB in 0s (5,658 kB/s)
Preconfiguring packages ...
(Reading database ... 228033 files and directories currently installed.)
Preparing to unpack .../tzdata_2020f-0ubuntu0.20.10.1_all.deb ...
Unpacking tzdata (2020f-0ubuntu0.20.10.1) over (2020d-1ubuntu1) ...
Setting up tzdata (2020f-0ubuntu0.20.10.1) ...
Current default time zone: 'America/Los_Angeles'
Local time is now: Mon Jan 11 19:10:44 PST 2021.
Universal Time is now: Tue Jan 12 03:10:44 UTC 2021.
Run 'dpkg-reconfigure tzdata' if you wish to change it.
bdmurray@clean-groovy-amd64:~$ python3 -c "from datetime import datetime; from
icu import ICUtzinfo, TimeZone; tz = ICUtzinfo(TimeZone.creat
eTimeZone('Europe/Volgograd')); print(str(tz.utcoffset(datetime(2020, 12,
28"
3:00:00
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910636
Title:
update icu-data which is bundled in tzdata to 2020f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1910636/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910886] Re: Crash | Upgate manager from GUI when clicked on install | File "/usr/lib/python3/dist-packages/UpdateManager/UpdatesAvailable.py", line 882, in on_button_install_clicked
The recent update looks to be okay and working fine as per described scenario: What's changed At the time of bug report 2021-01-10 ubuntu-release-upgrader version: ubuntu-release-upgrader-core 1:21.04.3 Python Version: Python 3.9.1 After update on 2021-01-12 ubuntu-release-upgrader version: ubuntu-release-upgrader-core/hirsute-proposed,hirsute-proposed,now 1:21.04.4 all [installed] Python Version: Python 3.9.1+ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910886 Title: Crash | Upgate manager from GUI when clicked on install | File "/usr/lib/python3/dist-packages/UpdateManager/UpdatesAvailable.py", line 882, in on_button_install_clicked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1910886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899288] Re: Python3 can't co-exist with Oracle's VirtualBox on 20.10
Same issue: after upgrading from Ubuntu 20.04 to 20.10 my Virtualbox installation was missing (removed as part of the upgrade). Attempts to re-install indicated a conflict between the python pre-req and dh- python. I performed the following and all appears to be working now: sudo apt remove dh-python sudo apt install ./virtualbox-6.1_6.1.16-140961~Ubuntu~eoan_amd64.deb sudo apt-get update sudo apt-get upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899288 Title: Python3 can't co-exist with Oracle's VirtualBox on 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1899288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759328]
No recent problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759328 Title: plasmashell crash when changing deskop containment from 'folder view' to 'desktop' To manage notifications about this bug go to: https://bugs.launchpad.net/plasma-framework/+bug/1759328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759328]
Phew, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759328 Title: plasmashell crash when changing deskop containment from 'folder view' to 'desktop' To manage notifications about this bug go to: https://bugs.launchpad.net/plasma-framework/+bug/1759328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759328]
Frameworks: 5.78.0 Plasmashell: 5.20.80 QT: 5.15.2 I don't have this issue anymore. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1759328 Title: plasmashell crash when changing deskop containment from 'folder view' to 'desktop' To manage notifications about this bug go to: https://bugs.launchpad.net/plasma-framework/+bug/1759328/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1759328]
After getting quite a few reports in rapid succession, we have not gotten any duplicates following a potential fix via code change. Is anyone still experiencing this? I am not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759328 Title: plasmashell crash when changing deskop containment from 'folder view' to 'desktop' To manage notifications about this bug go to: https://bugs.launchpad.net/plasma-framework/+bug/1759328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759328] Re: plasmashell crash when changing deskop containment from 'folder view' to 'desktop'
** Changed in: plasma-framework 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/1759328 Title: plasmashell crash when changing deskop containment from 'folder view' to 'desktop' To manage notifications about this bug go to: https://bugs.launchpad.net/plasma-framework/+bug/1759328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911036] Re: GDK/GTK app crash when performing drag operation
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911036 Title: GDK/GTK app crash when performing drag operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1911036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911079] Re: Unable to click top right corner of screen
Also, is the bug in gnome-shell or in Unity? Both seem to be mentioned here. Can you please attach a screenshot of the whole screen when the problem is occuring? ** Package changed: gnome-shell (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911079 Title: Unable to click top right corner of screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1911079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911079] Re: Unable to click top right corner of screen
Do you mean top right or top left corner? The bug title says "right" but the screenshot shows "left". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911079 Title: Unable to click top right corner of screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1911079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911030] Re: graphical flashes on a raspi 4
** Tags added: raspi raspi-gfx ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Summary changed: - graphical flashes on a raspi 4 + Graphical flashes on a raspi 4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911030 Title: Graphical flashes on a raspi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1911030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882850] Re: Touchpad not detected
** This bug is no longer a duplicate of bug 1885573 Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB) ** Summary changed: - Touchpad not detected + [Lenovo ThinkBook 14-IIL] Touchpad not detected -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882850 Title: [Lenovo ThinkBook 14-IIL] Touchpad not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885604] Re: Lenovo thinkbook 15IIL - touchpad and fingerprint don't work
*** This bug is a duplicate of bug 1885573 *** https://bugs.launchpad.net/bugs/1885573 ** This bug has been marked a duplicate of bug 1885573 Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885604 Title: Lenovo thinkbook 15IIL - touchpad and fingerprint don't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893804] Re: [Lenovo ThinkBook 14-IIL] Touchpad not responding
*** This bug is a duplicate of bug 1882850 *** https://bugs.launchpad.net/bugs/1882850 ** Summary changed: - touchpad not responding + [Lenovo ThinkBook 14-IIL] Touchpad not responding ** This bug has been marked a duplicate of bug 1882850 [Lenovo ThinkBook 14-IIL] Touchpad not detected -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893804 Title: [Lenovo ThinkBook 14-IIL] Touchpad not responding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894154] Re: touchpad doesn't work at all
*** This bug is a duplicate of bug 1882850 *** https://bugs.launchpad.net/bugs/1882850 ** This bug has been marked a duplicate of bug 1893804 [Lenovo ThinkBook 14-IIL] Touchpad not responding ** This bug is no longer a duplicate of bug 1893804 [Lenovo ThinkBook 14-IIL] Touchpad not responding ** This bug has been marked a duplicate of bug 1882850 [Lenovo ThinkBook 14-IIL] Touchpad not detected -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894154 Title: touchpad doesn't work at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897389] Re: Touchpad not detected in Lenovo Thinkbook
*** This bug is a duplicate of bug 1882850 *** https://bugs.launchpad.net/bugs/1882850 ** This bug has been marked a duplicate of bug 1893804 [Lenovo ThinkBook 14-IIL] Touchpad not responding ** This bug is no longer a duplicate of bug 1893804 [Lenovo ThinkBook 14-IIL] Touchpad not responding ** This bug has been marked a duplicate of bug 1882850 [Lenovo ThinkBook 14-IIL] Touchpad not detected -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897389 Title: Touchpad not detected in Lenovo Thinkbook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911024] Re: segfault crash after fresh restart
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (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/1911024 Title: segfault crash after fresh restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1911024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910455] Re: Thunar and Nautilus USB drive ejecting takes long time
Sorry about that. Here is a new log that is not truncated. ** Attachment added: "new_log.txt" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1910455/+attachment/5451936/+files/new_log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910455 Title: Thunar and Nautilus USB drive ejecting takes long time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1910455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910559] Re: GDM3: Black screen with blinking cursor
OK, thanks. If the problem returns then we can reopen the bug. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910559 Title: GDM3: Black screen with blinking cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910840] Re: Xorg freeze
Thanks but that crash is from 'nautilus' which is not relevant to the shell. Please follow the steps in comment #2 again next time the problem happens. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910840 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1910840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910928] Re: Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL
Thanks. It looks like the kernel has everything turned on: 1: ideapad_bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no Do you still have a 'bluetoothd' process when the problem occurs? Also, can you run 'bluetoothctl' successfully when the bug is happening? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910928 Title: Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1910928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1265541] Re: Update to upstream snapshot of 2.4.1
This bug was fixed in the package libfcgi - 2.4.2-2 --- libfcgi (2.4.2-2) unstable; urgency=medium * Move to unstable: no changes required. * New version includes only bug fixes, updates of build scripts and updates of documentation. * No changes in ABI => transition is not required. -- Boris Pek Mon, 11 Jan 2021 08:57:45 +0300 ** Changed in: libfcgi (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/1265541 Title: Update to upstream snapshot of 2.4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfcgi/+bug/1265541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909732] Re: unable to login to desktop manager after suspend
All of those bullet points are related :) ** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu) ** Summary changed: - unable to login to desktop manager after suspend + Gnome Shell freezes for 2 minutes on unlock when mobile phone is connected (log shows gvfsd PTP errors) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909732 Title: Gnome Shell freezes for 2 minutes on unlock when mobile phone is connected (log shows gvfsd PTP errors) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1909732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910618] Re: bcmwl 6.30.223.271+bdcom build fails with kernel 5.8.0-34/36 Ubuntu 20.04.1 LTS
** Summary changed: - bcmwl 6.30.223.271+bdcom build fails with kernel 5.8.0-34/36 Ubuntu 20.04 LTS + bcmwl 6.30.223.271+bdcom build fails with kernel 5.8.0-34/36 Ubuntu 20.04.1 LTS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910618 Title: bcmwl 6.30.223.271+bdcom build fails with kernel 5.8.0-34/36 Ubuntu 20.04.1 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909495] Re: Unable to start BIOS VMs since Linux 5.10
I am currently moved to hirsute. And this issue still present with latest stable 5.10.6-051006 kernel from the mainline ppa. ** Tags added: hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909495 Title: Unable to start BIOS VMs since Linux 5.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1909495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910866] Re: nvme drive fails after some time
FYI I have captured the `sudo lspci -vv` output on the kernel 5.8 *before* the issue here https://pastebin.ubuntu.com/p/GtZyTWzKTd/ it is subtly different to the 5.4 kernel (which has not had the issue) in case that mattered. I was also able to reproduce the issue again by causing high disk I/O, specifically I needed to have writes occurring for it to happen (I was recursive grep'ing the whole filesystem while installing apt/pip packages inside a docker container). This then froze the system for 120 seconds until write timeouts occurred, then the disk was remounted as read-only. After this point commands on the system would fail with I/O errors (even basic ones such as "top", although some such as "mount" still work). However our plan was to try to retrieve more information by copying the lspci binary and libs into a tmpfs system in RAM, so it'd still be accessible when the disk stopped. This almost worked, but it appears a few more configuration files would need to be placed in RAM (I could run "lspci --help" but not "lspci" or "lspci -vv"). Instead popey has suggested maybe using a USB key with debootstrap/chroot. (Any suggestions of how we can retrieve more information at this point are welcome and any commands that would be useful to run). Also as a note, if I use REISUB ( https://en.m.wikipedia.org/wiki/Magic_SysRq_key#Uses ) to reboot the machine it enters a Dell BIOS/recovery thing that states that "No Hard Disk is found". Then after a full power off the machine works again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910866 Title: nvme drive fails after some time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911079] [NEW] Unable to click top right corner of screen
Public bug reported: Dead zone ~10% of the top corner how ever I can click above the side tool bar it is like some invisible box is nested on top of my window ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 Uname: Linux 5.10.0-051000-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Jan 12 10:55:21 2021 DisplayManager: lightdm InstallationDate: Installed on 2020-12-03 (39 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 ShellJournal: -- Logs begin at Fri 2020-12-04 07:06:30 AEST, end at Tue 2021-01-12 10:55:09 AEST. -- -- No entries -- SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images ** Attachment added: "Screenshot from 2021-01-12 10-58-57.png" https://bugs.launchpad.net/bugs/1911079/+attachment/5451927/+files/Screenshot%20from%202021-01-12%2010-58-57.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911079 Title: Unable to click top right corner of screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1911079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878045] Re: doing dist-upgrade got error related do Broadcom
I have the same problem like @Alex explain, adding to that when i run `lshw -C network` I noticed wireless network is not claimed. How to claim it? `*-network UNCLAIMED description: Network controller product: BCM4331 802.11a/b/g/n vendor: Broadcom Inc. and subsidiaries physical id: 0 bus info: pci@:02:00.0 version: 02 width: 64 bits clock: 33MHz capabilities: bus_master cap_list configuration: latency=0 resources: memory:a060-a0603fff` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878045 Title: doing dist-upgrade got error related do Broadcom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911077] [NEW] sudo apt-get dist-upgrade report: package linux-modules-extra-5.8.0-36-generic (not installed) failed to install/upgrade: »/lib/modules/5.8.0-36-generic/kernel/drivers/media/pci/cx
Public bug reported: 1. lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 2. apt-cache policy linux-modules-extra-5.8.0-36-generic linux-modules-extra-5.8.0-36-generic: Installiert: (keine) Installationskandidat: 5.8.0-36.40~20.04.1 Versionstabelle: 5.8.0-36.40~20.04.1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 3. I didn't expect anything. I've never had any problems. 4. I upgraded my laptop after a long time, only one package seems to have problems. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.8.0-36-generic (not installed) ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 AptOrdering: linux-modules-5.8.0-36-generic:amd64: Install linux-modules-extra-5.8.0-36-generic:amd64: Install linux-hwe-5.8-headers-5.8.0-36:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jan 12 01:26:26 2021 ErrorMessage: »/lib/modules/5.8.0-36-generic/kernel/drivers/media/pci/cx88/cx88-vp3054-i2c.ko.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig InstallationDate: Installed on 2020-08-07 (157 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: linux-hwe-5.8 Title: package linux-modules-extra-5.8.0-36-generic (not installed) failed to install/upgrade: »/lib/modules/5.8.0-36-generic/kernel/drivers/media/pci/cx88/cx88-vp3054-i2c.ko.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911077 Title: sudo apt-get dist-upgrade report: package linux-modules- extra-5.8.0-36-generic (not installed) failed to install/upgrade: »/lib/modules/5.8.0-36-generic/kernel/drivers/media/pci/cx88/cx88-vp3054-i2c.ko .dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1911077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909698] Re: new upstream release 2020f
Hi Brian, Thanks for the trusty and precise debdiffs. I have gone ahead and published the updates to trusty-esm and precise-esm, after verifying the fixes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909698 Title: new upstream release 2020f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817286] Re: Some Media Keys (Not all) and custom keyboard shortcuts irregulary don't work after boot/reboot
*** This bug is a duplicate of bug 1818978 *** https://bugs.launchpad.net/bugs/1818978 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-settings-daemon (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/1817286 Title: Some Media Keys (Not all) and custom keyboard shortcuts irregulary don't work after boot/reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1817286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905591] Re: no brightness control in {455, 460} after update from 450
@sureshot16 thanks a lot!! fixes on my system too! (hp omen 15)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905591
Title:
no brightness control in {455,460} after update from 450
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1905591/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911074] [NEW] Rockpi 4C Installtion issue
Public bug reported: Description: Ubuntu 20.04.01 LTS Release: 20.04 mali-midgard-dkms: Installed: 16.0+pristine-4 Candidate: 16.0+pristine-4 Version table: *** 16.0+pristine-4 500 500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages 100 /var/lib/dpkg/status When running either "apt install mali-midgard-dkms". Or "dpkg -i mali- midgard-dkms_16.0+pristine-4_all.deb". I ran into two issue when I expect an installation 1. "/usr/bin/env python" Not found. That was easily fixable with the ln command. 2. /var/lib/dkms/mali-midgrad/16.0/build/Kbuild:192: /var/lib/dkms/mali-midgard/16.0/build/platform/rk/Kbuild: No such file or directory make[2]: *** NO rule to make target '/var/lib/dkms/mali-midgard/16.0/build/platform/rk/build' make[1]: *** [Makefile:1474: _module_/var/lib/dkms/mali-midgard/16.0/build] Error 2 ** Affects: mali-midgard (Ubuntu) Importance: Undecided Status: New ** Description changed: Description: Ubuntu 20.04.01 LTS Release: 20.04 mali-midgard-dkms: - Installed: 16.0+pristine-4 - Candidate: 16.0+pristine-4 - Version table: - *** 16.0+pristine-4 500 - 500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages - 100 /var/lib/dpkg/status + Installed: 16.0+pristine-4 + Candidate: 16.0+pristine-4 + Version table: + *** 16.0+pristine-4 500 + 500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages + 100 /var/lib/dpkg/status - - When running either "apt install mali-midgard-dkms". Or "dpkg -i mali-midgard-dkms_16.0+pristine-4_all.deb". I ran into two issue when I expect an installation + When running either "apt install mali-midgard-dkms". Or "dpkg -i mali- + midgard-dkms_16.0+pristine-4_all.deb". I ran into two issue when I + expect an installation 1. "/usr/bin/env python" Not found. That was easily fixable with the ln command. 2. /var/lib/dkms/mali-midgrad/16.0/build/Kbuild:192: /var/lib/dkms/mali-midgard/16.0/build/platform/rk/Kbuild: No such file or directory make[2]: *** NO rule to make target '/var/lib/dkms/mali-midgard/16.0/build/platform/rk/build' - make[1]" *** [Makefile:1474: _module_/var/lib/dkms/mali-midgard/16.0/build] Error 2 + make[1]: *** [Makefile:1474: _module_/var/lib/dkms/mali-midgard/16.0/build] Error 2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911074 Title: Rockpi 4C Installtion issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mali-midgard/+bug/1911074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911073] Re: libc6 package version 2.31-0ubuntu9.1 in ubuntu 20.04.1 - no traces of where it came from
** Package changed: ubuntu => apt (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911073 Title: libc6 package version 2.31-0ubuntu9.1 in ubuntu 20.04.1 - no traces of where it came from To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1911073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911073] [NEW] libc6 package version 2.31-0ubuntu9.1 in ubuntu 20.04.1 - no traces of where it came from
Public bug reported: I installed `Ubuntu 20.04.1 LTS` few weeks ago. So it's almost fresh install. I can't install libc6-dev: The following packages have unmet dependencies: libc6-dev : Depends: libc6 (= 2.31-0ubuntu9) but 2.31-0ubuntu9.1 is to be installed Here's what version the `-dev` package is: $ apt show libc6-dev Version: 2.31-0ubuntu9 Depends: libc6 (= 2.31-0ubuntu9), libc-dev-bin (= 2.31-0ubuntu9), linux-libc-dev, libcrypt-dev `Depends: libc6 (= 2.31-0ubuntu9)` looks good to me. apt-cache shows libc version is ok: $ apt-cache show libc6 Version: 2.31-0ubuntu9 However, `apt` differs: $ apt show libc6 Version: 2.31-0ubuntu9.1 apt can not tell where this version comes from `focal/main`: $ apt policy libc6 libc6: Installed: 2.31-0ubuntu9.1 Candidate: 2.31-0ubuntu9.1 Version table: *** 2.31-0ubuntu9.1 100 100 /var/lib/dpkg/status 2.31-0ubuntu9 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 9.1 can only be found in `/var/lib/dpkg/status` however, neither in packages here: `http://us.archive.ubuntu.com/ubuntu/dists/focal/main /binary-amd64/` nor in `/var/lib/apt/lists/us.archive.ubuntu .com_ubuntu_dists_focal_main_binary-amd64_Packages` version `2.31-0ubuntu9.1` does not exist. Upgrade can be seen in the logs: 2021-01-02 21:02:03 startup archives unpack 2021-01-02 21:02:03 upgrade libc6:amd64 2.31-0ubuntu9 2.31-0ubuntu9.1 2021-01-02 21:02:03 status half-configured libc6:amd64 2.31-0ubuntu9 2021-01-02 21:02:03 status unpacked libc6:amd64 2.31-0ubuntu9 2021-01-02 21:02:03 status half-installed libc6:amd64 2.31-0ubuntu9 2021-01-02 21:02:03 status unpacked libc6:amd64 2.31-0ubuntu9.1 2021-01-02 21:02:04 startup packages configure 2021-01-02 21:02:04 configure libc6:amd64 2.31-0ubuntu9.1 2021-01-02 21:02:04 status unpacked libc6:amd64 2.31-0ubuntu9.1 2021-01-02 21:02:04 status half-configured libc6:amd64 2.31-0ubuntu9.1 2021-01-02 21:02:04 status installed libc6:amd64 2.31-0ubuntu9.1 Is there a legitimate ubuntu repository with this package? How can I find the repository name where this package really came from? What worries me is md5s hash of this package is `1ec728d58f7fc0d302119e9bb53050f8` which can only be found on ropshell. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.2ubuntu0.2 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 11 18:44:00 2021 InstallationDate: Installed on 2021-01-03 (8 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911073 Title: libc6 package version 2.31-0ubuntu9.1 in ubuntu 20.04.1 - no traces of where it came from To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1911073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896334] Re: SRU 3.36.6
I have gnome-shell 3.36.7-0ubuntu0.20.04.1 installed from focal-proposed for three weeks now and my two-monitor setup is working great. I also have the gnome-shell-extensions-gpaste (from Ubuntu universe) and the gsconnect extension (from https://extensions.gnome.org/extension/1319/gsconnect/) installed and running without any problems. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896334 Title: SRU 3.36.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903764] Re: [SRU] Update gnome-shell to 3.36.7 in Focal
I have gnome-shell 3.36.7-0ubuntu0.20.04.1 installed from focal-proposed for three weeks now and my two-monitor setup is working great. I have also the gnome-shell-extensions-gpaste installed and running without any problems. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903764 Title: [SRU] Update gnome-shell to 3.36.7 in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911072] [NEW] LibreOffice Impress OpenGL transitions flickering only on Ubuntu Gnome
Public bug reported: When I'm using the standard Ubuntu installation with Gnome DE, LibreOffice Impress transitions that require OpenGL do not work. To reproduce the bug: 1) Create a presentation using LO Impress 2) Add an OpenGL transition (e.g. Fade In) 3) Start the presentation 4) The transition will be flickering in a very weird manner I am currently using Ubuntu 20.10 with Nvidia drivers and the gtk3 VCL plugin. However, this issue has existed since at least Ubuntu 19.10, which was when I first experienced it. This is a long-standing bug that might to be related with the way drivers/OpenGL/Gnome are set-up on Ubuntu. See the following bug report on LibreOffice's Bugzilla page: https://bugs.documentfoundation.org/show_bug.cgi?id=131610 The weirdest thing is that I also run Kubuntu 20.10 on the same machine and on Kubuntu all transitions work perfectly fine. That's why I think it may have something to do with Gnome on Ubuntu. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911072 Title: LibreOffice Impress OpenGL transitions flickering only on Ubuntu Gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1911072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904585] Re: opal-prd: Have a worker process handle page offlining (Fixes "PlatServices: dyndealloc memory_error() failed" is getting reported in error log (opal-prd))
** Tags removed: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904585 Title: opal-prd: Have a worker process handle page offlining (Fixes "PlatServices: dyndealloc memory_error() failed" is getting reported in error log (opal-prd)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910835] Re: Azure IMDS publicKeys contain \r\n which prevents ssh access to vms using cloud-generated ssh keys.
Hello Chad, or anyone else affected, Accepted cloud-init into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/20.4-0ubuntu1~20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: cloud-init (Ubuntu Focal) Status: New => 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/1910835 Title: Azure IMDS publicKeys contain \r\n which prevents ssh access to vms using cloud-generated ssh keys. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1910835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903230] Re: Mutter release 3.36.7
I have mutter 3.36.7+git20201123-0.20.04.1 installed from focal-proposed for over two weeks now and gnome-shell, with two monitors, is running great without any problems. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903230 Title: Mutter release 3.36.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910945] Re: can't upgrade from 19.10
The change to sources was in my EOL link (https://help.ubuntu.com/community/EOLUpgrades) As for it still responding 19.10; if you're talking wallpaper; that isn't changed, as I suspect users would be horrified if their beloved wallpaper was changed on upgrade; so it's left alone (even it's the prior default wallpaper). Glad you got it solved though ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910945 Title: can't upgrade from 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1910945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910835] Re: Azure IMDS publicKeys contain \r\n which prevents ssh access to vms using cloud-generated ssh keys.
Hello Chad, or anyone else affected, Accepted cloud-init into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/20.4-0ubuntu1~20.10.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: cloud-init (Ubuntu Groovy) Status: New => Fix Committed ** Tags added: verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910835 Title: Azure IMDS publicKeys contain \r\n which prevents ssh access to vms using cloud-generated ssh keys. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1910835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905630] Re: [SRU] Cinnamon and applications won't run a sh script if the directory has spaces in its name
While this SRU is in Groovy/Hirsute it's not worth introducing regression risk ** Changed in: cinnamon-desktop (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905630 Title: [SRU] Cinnamon and applications won't run a sh script if the directory has spaces in its name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon-desktop/+bug/1905630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895343] Re: Microsoft Azure Enablement: azure-lb missing in Bionic
Hello Rafael, or anyone else affected, Accepted resource-agents into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/resource- agents/1:4.5.0-2ubuntu2.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: resource-agents (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895343 Title: Microsoft Azure Enablement: azure-lb missing in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1895343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910806] Re: System hang - kernel 5.8.0-36
This problem report is related to 1910588. I am running kernel 5.8.0-36 now and found that the dd command I was using to test zfs raidz1 performance worked the last time I tried. dd now provides speed measurement skewed by arc though (2.0GB/s). I have run memtest86 on this machine recently. Four passes found no errors. The machine memory is non-ECC though. I'll try again after the next reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910806 Title: System hang - kernel 5.8.0-36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910835] Please test proposed package
Hello Chad, or anyone else affected, Accepted cloud-init into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/20.4-0ubuntu1~18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910835 Title: Azure IMDS publicKeys contain \r\n which prevents ssh access to vms using cloud-generated ssh keys. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1910835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910835] Re: Azure IMDS publicKeys contain \r\n which prevents ssh access to vms using cloud-generated ssh keys.
Hello Chad, or anyone else affected, Accepted cloud-init into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/20.4-0ubuntu1~16.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: cloud-init (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-xenial ** Changed in: cloud-init (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: 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/1910835 Title: Azure IMDS publicKeys contain \r\n which prevents ssh access to vms using cloud-generated ssh keys. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1910835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910835] Re: Azure IMDS publicKeys contain \r\n which prevents ssh access to vms using cloud-generated ssh keys.
** Description changed:
- cloud-init 20.4 or later will incorrectly add Azure publicKeys to
- .ssh/authorized_keys preventing ssh access for cloud-generated keys.
+ == Begin SRU Template ==
+ [Impact]
+ This release is only a single functional cherry-pick which solely affects
Azure platform. It is a critical bug we wish to release as soon as possible
+ * Azure: cherry-pick 4f62ae8d: Fix regression with handling of IMDS ssh keys
+ (#760) (LP: #1910835)
+
+
+ [Test Case]
+ The following development and SRU process was followed:
+ https://wiki.ubuntu.com/CloudinitUpdates
+
+ The cloud-init team will be in charge of attaching the artifacts and
+ console output of the appropriate run to the bug. cloud-init team
+ members will not mark ‘verification-done’ until this has happened.
+
+ * Automated Test Results
+
+
+
+
+
+ * Manual Test Results
+
+
+
+
+ [Regression Potential]
+ In order to mitigate the regression potential, the results of the
+ aforementioned integration tests are attached to this bug.
+
+ [Discussion]
+ This should only affect public Azure VM launched which use Azure to
--generate-ssh-keys either from the dashboard or from the `az cli`
+
+
+ Any other cloud-platform is not affected by this change.
+
+
+ == End SRU Template ==
+
+ * cherry-pick 4f62ae8d: Fix regression with handling of IMDS ssh keys
+ (#760) (LP: #1910835)
+
+
+ == Original Description ==
+
+
+ cloud-init 20.4 or later will incorrectly add Azure publicKeys to
.ssh/authorized_keys preventing ssh access for cloud-generated keys.
To reproduce: launch an ubuntu VM from the portal.azure.com choosing to
generate new ssh key.
When the instance is launched you can see that the ssh-rsa content
provided in the metadata publicKeys value contains CRLF characters
(\r\n) thus splitting the content of the pubkey onto multiple lines when
it is rendered into .ssh/authorized_keys.
-
- the solution is either for IMDS to stop adding the CRLF characters or
cloud-init to strip them out.
-
+ the solution is either for IMDS to stop adding the CRLF characters or
+ cloud-init to strip them out.
Here is the IMDS value provided to cloud-init
cloud-init query --format '{{ds.meta_data.imds.compute.publicKeys}}'
[{'keyData': 'ssh-rsa
B3NzaC1yc2EDAQABAAABgQCllNnyHXFWlMb9EKD9LZrOxt1d\r\nk/QxYwQ0HYEP8n6TUWoUsN3mv/Qk/qWH76Pa6f33hefzTFRiom7Ls/tJMcr/ki8R\r\n9FqyYOu0xxHmpXTUWFoZQCZtGRMtvDl/s76Wr1sCsE/ez+EcAPeGGm/B7jHtDAUW\r\nlkINfuPVBDfRtSfmnlCKS+sIf1XOqvRASGWi05zAW921T4OkiattyXyhaOimJOwq\r\n4jAXmydwtNCN2iGGKWS8YeXbtgveReqZVVKtcDKevgWdNyqZa69uq9tRujobjCh7\r\n6xxCkQcdCLospgqX79GBbdRys6mVxVgc349RIWjQwglRQpJwNzkeOG5Q+La2MEhu\r\niKqKJMvYVhil3khzMuZwzmTrGbRx0E8AS+Cm064RBgbcdjCW8dDYGLuk2eQ2v9Ht\r\n6eERfxMBNg3udv1jmiKpjjHIg99HDU4VqhL3aHmg+TSrxByd0cAgFBV+H0CiUVC9\r\nS2mLJ6Peu/HDwd88E8Wqiv3eAsjcaCRH3QiQVaU=
generated-by-azure\r\n', 'path': '/home/ubuntu/.ssh/authorized_keys'}]
-
- cloud-init renders this directly to .ssh/authorized_keys without processing
the string, resulting in an invalid keyline:
+ cloud-init renders this directly to .ssh/authorized_keys without
+ processing the string, resulting in an invalid keyline:
ssh-rsa B3NzaC1yc2EDAQABAAABgQCllNnyHXFWlMb9EKD9LZrOxt1d
k/QxYwQ0HYEP8n6TUWoUsN3mv/Qk/qWH76Pa6f33hefzTFRiom7Ls/tJMcr/ki8R^M
9FqyYOu0xxHmpXTUWFoZQCZtGRMtvDl/s76Wr1sCsE/ez+EcAPeGGm/B7jHtDAUW^M
lkINfuPVBDfRtSfmnlCKS+sIf1XOqvRASGWi05zAW921T4OkiattyXyhaOimJOwq^M
4jAXmydwtNCN2iGGKWS8YeXbtgveReqZVVKtcDKevgWdNyqZa69uq9tRujobjCh7^M
6xxCkQcdCLospgqX79GBbdRys6mVxVgc349RIWjQwglRQpJwNzkeOG5Q+La2MEhu^M
iKqKJMvYVhil3khzMuZwzmTrGbRx0E8AS+Cm064RBgbcdjCW8dDYGLuk2eQ2v9Ht^M
6eERfxMBNg3udv1jmiKpjjHIg99HDU4VqhL3aHmg+TSrxByd0cAgFBV+H0CiUVC9^M
S2mLJ6Peu/HDwd88E8Wqiv3eAsjcaCRH3QiQVaU= generated-by-azure
-
this prevents ssh from actually reading the right key from azure:
$ ssh-keygen -lf /home/ubuntu/.ssh/authorized_keys
If we strip the CRLF (^M) characters and reparse with ssh-keygenm we see
the proper key registered:
$ ssh-keygen -lf /home/ubuntu/.ssh/authorized_keys
3072 SHA256:PQ9EKxTKONJKFC2N56UpL6+Oc/cujfA9HpsF5VW2QDI generated-by-azure
(RSA)
-
If cloud-init (or IMDS) were to strip those \r\n characters from each
line ssh
** Description changed:
== Begin SRU Template ==
[Impact]
This release is only a single functional cherry-pick which solely affects
Azure platform. It is a critical bug we wish to release as soon as possible
- * Azure: cherry-pick 4f62ae8d: Fix regression with handling of IMDS ssh keys
- (#760) (LP: #1910835)
+ * Azure: cherry-pick 4f62ae8d: Fix regression with handling of IMDS ssh keys
+ (#760) (LP: #1910835)
+
+ The functional changeset here introduces a raise KeyError exception
+ which forces cloud-init to revert to previous released logic of the
+ previous cloud-init public release 20.3.
[Test Case]
The following development and SRU process was followed:
htt
[Bug 1911068] [NEW] no puedo actualizar a una nueva version del software por un error en launchpad
Public bug reported: tengo una actualizacion para una version mas nueva para mi laptop y no la puedo descargar por un problema con una carpeta de launchpad, ya he informado del problema pero igual no me han ayudado ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.29 ProcVersionSignature: Ubuntu 4.15.0-1028.33-oem 4.15.18 Uname: Linux 4.15.0-1028-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jan 11 17:50:28 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs canonical-oem-stella-bionic-amd64-47 InstallationDate: Installed on 2020-08-07 (157 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20181213-08:48 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2021-01-11 (0 days ago) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2021-01-09T20:52:16.692141 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911068 Title: no puedo actualizar a una nueva version del software por un error en launchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1911068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911069] [NEW] Attempted install on VirtualBox after initial install attempt crashed.
Public bug reported: Attempted to install Xubuntu 18.04 on VirtualBox, initial install stalled and crashed. Rebooted computer, attempted to install again, opting to completely erase the virtual drive it was being installed on and start from scratch. Made it through the majority of the install, in the final stages it threw an error with listed debug info. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.15 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CasperVersion: 1.394.3 Date: Mon Jan 11 16:46:55 2021 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Xubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.15 xubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911069 Title: Attempted install on VirtualBox after initial install attempt crashed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1911069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904585] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted skiboot into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/skiboot/5.4.3-1ubuntu0.16.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904585 Title: opal-prd: Have a worker process handle page offlining (Fixes "PlatServices: dyndealloc memory_error() failed" is getting reported in error log (opal-prd)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904585] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted skiboot into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/skiboot/5.10~rc4-1ubuntu1.3 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: skiboot (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904585 Title: opal-prd: Have a worker process handle page offlining (Fixes "PlatServices: dyndealloc memory_error() failed" is getting reported in error log (opal-prd)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904585] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted skiboot into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/skiboot/6.5.2-1ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- 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. ** Changed in: skiboot (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: 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/1904585 Title: opal-prd: Have a worker process handle page offlining (Fixes "PlatServices: dyndealloc memory_error() failed" is getting reported in error log (opal-prd)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904585] Re: opal-prd: Have a worker process handle page offlining (Fixes "PlatServices: dyndealloc memory_error() failed" is getting reported in error log (opal-prd))
Hello bugproxy, or anyone else affected, Accepted skiboot into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/skiboot/6.5.2-1ubuntu0.20.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: skiboot (Ubuntu Groovy) Status: Incomplete => Fix Committed ** Tags added: verification-needed verification-needed-groovy ** Changed in: skiboot (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904585 Title: opal-prd: Have a worker process handle page offlining (Fixes "PlatServices: dyndealloc memory_error() failed" is getting reported in error log (opal-prd)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905393] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted skiboot into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/skiboot/6.5.2-1ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- 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/1905393 Title: Ubuntu 20.04: opal-prd fails to start on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1905393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905393] Re: Ubuntu 20.04: opal-prd fails to start on 20.04
Hello bugproxy, or anyone else affected, Accepted skiboot into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/skiboot/6.5.2-1ubuntu0.20.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: skiboot (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy ** Changed in: skiboot (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905393 Title: Ubuntu 20.04: opal-prd fails to start on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1905393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878045] Re: doing dist-upgrade got error related do Broadcom
I'm in the same boat as @adrian and @meeraj and @angels. I clicked through on the update windows when I got them last week (or there abouts) and the next time I rebooted I had no wifi at all. I followed the suggestion to purge the bcmwl-kernel-source package and install the three broadcom ones, now my Additional Drivers page shows I have three options. Using the Broadcom one is disabled, Do not use this device is selected and disabled; and the new one Continuing using manually installed driver. Selecting that doesn't let me apply and I don't know what to do here... I should add I have Ubuntu 20.04 running on a MacBookPro from... some old year... 2015? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878045 Title: doing dist-upgrade got error related do Broadcom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910835] Re: Azure IMDS publicKeys contain \r\n which prevents ssh access to vms using cloud-generated ssh keys.
** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Groovy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910835 Title: Azure IMDS publicKeys contain \r\n which prevents ssh access to vms using cloud-generated ssh keys. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1910835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911014] Re: include-config-dir from sshd not recognized
** Bug watch added: Debian Bug tracker #972192 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972192 ** Also affects: rkhunter (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972192 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911014 Title: include-config-dir from sshd not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rkhunter/+bug/1911014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881947] Re: Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52, function main(). Aborting.
Hello dann, or anyone else affected, Accepted systemd into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: systemd (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881947 Title: Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52, function main(). Aborting. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1881947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
Hello Christian, or anyone else affected, Accepted systemd into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: systemd (Ubuntu Groovy) Status: New => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902960] Re: Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS resolution in some cases
Hello David, or anyone else affected, Accepted systemd into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: systemd (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902960 Title: Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS resolution in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1902960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905044] Re: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8
Hello Kleber, or anyone else affected, Accepted systemd into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: systemd (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905044 Title: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907306] Re: networkd dhcpv4 client never attempts more than 2 renew and 2 rebind
Hello Dan, or anyone else affected, Accepted systemd into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: systemd (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907306 Title: networkd dhcpv4 client never attempts more than 2 renew and 2 rebind To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1907306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908067] Re: systemd-fsckd test fails on groovy checking plymouth-start isactive
Hello Dan, or anyone else affected, Accepted systemd into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: systemd (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908067 Title: systemd-fsckd test fails on groovy checking plymouth-start isactive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911059] Re: gce: 247.1-4ubuntu1 causes loss of networking
Greater output of journalctl: https://pastebin.canonical.com/p/XJzPMHrSbx/ ** Description changed: Summary === On Hirsute, upgrading or using to systemd 247.1-4ubuntu1 causes Google Cloud instance to loose network access. Expected Result === Working network access Actual Result === After upgrade, network access is lost and serial console is filled with messages about IPv4 martian source and ll header, see below. Steps to Reproduce === 1. Launch `daily-ubuntu-2104-hirsute-v20210107` the last known good image 2. sudo apt update - 3. sudo apt install systems + 3. sudo apt install systemd 4. ssh is lost The images, built with this version do not appear to be able to start networking. Logs === Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 483.915720] IPv4: martian source 10.138.0.56 from 169.254.169.254, on dev ens4 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 483.915724] ll header: : 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 483.978762] IPv4: martian source 10.138.0.56 from 169.254.169.254, on dev ens4 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 483.978803] ll header: : 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 484.042242] IPv4: martian source 10.138.0.56 from 169.254.169.254, on dev ens4 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 484.042302] ll header: : 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 484.105412] IPv4: martian source 10.138.0.56 from 169.254.169.254, on dev ens4 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 484.105448] ll header: : 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 484.168141] IPv4: martian source 10.138.0.56 from 169.254.169.254, on dev ens4 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 484.168178] ll header: : 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00 $ journalctl --no-pager -u systemd-net -- Journal begins at Mon 2021-01-11 21:30:31 UTC, ends at Mon 2021-01-11 21:52:03 UTC. -- Jan 11 21:30:35 ubuntu systemd[1]: Starting Network Service... Jan 11 21:30:35 ubuntu systemd-networkd[413]: Enumeration completed Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Interface name change detected, ens4 has been renamed to eth0. Jan 11 21:30:35 ubuntu systemd[1]: Started Network Service. Jan 11 21:30:35 ubuntu systemd-networkd[413]: eth0: Interface name change detected, eth0 has been renamed to ens4. Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: IPv6 successfully enabled Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Link UP Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Gained carrier Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: DHCPv4 address 10.138.0.56/32 via 10.138.0.1 Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Classless static routes received from DHCP server: ignoring router option Jan 11 21:30:37 ubuntu systemd-networkd[413]: ens4: Gained IPv6LL Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[413]: ens4: DHCPv6 lease lost Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Stopping Network Service... Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: systemd-networkd.service: Succeeded. Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Stopped Network Service. Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Starting Network Service... Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[2446]: ens4: Gained IPv6LL Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[2446]: Enumeration completed Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Started Network Service. Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[2446]: ens4: DHCPv4 address 10.138.0.56/32 via 10.138.0.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911059 Title: gce: 247.1-4ubuntu1 causes loss of networking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1911059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905245] Re: "Failed to parse bus message: Invalid argument" with Linux 5.8
Hello Gary, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.44 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: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: 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/1905245 Title: "Failed to parse bus message: Invalid argument" with Linux 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907306] Re: networkd dhcpv4 client never attempts more than 2 renew and 2 rebind
Hello Dan, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.44 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: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: 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/1907306 Title: networkd dhcpv4 client never attempts more than 2 renew and 2 rebind To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1907306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
