[Bug 1923050] Re: Cannot resume from suspend
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923050 Title: Cannot resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923167] Re: Screen flickering- QHD Benq
[Expired for xserver-xorg-video-amdgpu (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xserver-xorg-video-amdgpu (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/1923167 Title: Screen flickering- QHD Benq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1923167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923233] Re: Computer is very slow
[Expired for Ubuntu because there has been no activity for 60 days.] ** Changed in: ubuntu Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923233 Title: Computer is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1923233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923333] Re: Benq G610HDA not being detected
[Expired for nvidia-graphics-drivers-460 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers-460 (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/192 Title: Benq G610HDA not being detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923318] Re: Ubuntu does not detect video output devices
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (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/1923318 Title: Ubuntu does not detect video output devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1923318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923397] Re: Xorg freeze
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (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/1923397 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1923397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931756] Re: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931756 Title: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1931756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920836] Re: Show Extended Security Maintenence status
This bug was fixed in the package software-properties - 0.99.13 --- software-properties (0.99.13) impish; urgency=medium * Catch exception if UA status file is not written -- Robert Ancell Fri, 11 Jun 2021 17:16:09 +1200 ** Changed in: software-properties (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/1920836 Title: Show Extended Security Maintenence status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931756] [NEW] [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
Public bug reported: I have tried modifications to DKMS, modprobe.d, pulseaudio and alsa but all were no sound. The modprobe,d modifications did result in the "dummy" message being replaced by a device. This was done 2 installs ago,sorry. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.10.0-051000-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pbea 1894 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Fri Jun 11 23:34:27 2021 InstallationDate: Installed on 2021-06-11 (0 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2021 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.2 dmi.board.name: 0P25F6 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.2:bd03/04/2021:br1.7:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0P25F6:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931756 Title: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1931756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926806] Re: pipx terminates with "TypeError: __init__() got an unexpected keyword argument 'encoding'"
Version: 0.16.2.1 What testing: installed protontricks Result: it works now! ** Tags added: verification-done-hirsute ** Tags removed: verification-needed-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926806 Title: pipx terminates with "TypeError: __init__() got an unexpected keyword argument 'encoding'" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pipx/+bug/1926806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931306] Re: bionic: postfix-dbgsym package lacks DWARF information
** Changed in: postfix (Debian) Status: Unknown => 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/1931306 Title: bionic: postfix-dbgsym package lacks DWARF information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1931306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931685] Re: Ubuntu 21.04: ubuntu dock causes windows in Activities view get cutt off at the bottom
** Description changed: - On ubuntu 21.04 and on 21.10. When I open the activities view with a few + On ubuntu 21.04 and on 20.10. When I open the activities view with a few windows open the bottom edge of the windows (with the window names) get cut off, the bottom of the workspaces bar on the right side also gets cut off. When the workspaces bar is fully extended, the windows can be seen fully. So when I hover over the workspaces bar, or there are multiple workspaces with windows in them, or with an extension to always keep the workspaces open, this issue doesn't impact anything. However, the issue still exists because you can see the bottom of the workspaces bar being cut off. When I connect a second monitor, and arrange the monitors one above the other (with the top one as the permanent), I can see the cut off UI elements on the bottom monitor. With the ubuntu dock extension disabled, none of these issues are present. Here are a few screenshots that show the bug in action: https://ibb.co/album/4whv2c I could NOT spot this issue on a clean install of ubuntu 20.04. But I could see it on clean installs of both on 20.10 and on 21.04. This exists both on Wayland and Xorg. This might be related to this prior issue: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/+bug/1834967 . Maybe this issue was fixed in 20.04 but not on the later versions. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell-extension-ubuntu-dock 69ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 13:05:40 2021 InstallationDate: Installed on 2021-06-11 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931685 Title: Ubuntu 21.04: ubuntu dock causes windows in Activities view get cutt off at the bottom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1931685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891643] Re: amavisd-new suggests missing packages
amavis-mc service requires this missing package: "libzeromq-perl" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891643 Title: amavisd-new suggests missing packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1891643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931755] Re: package grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit stat
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931755 Title: package grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1931755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931755] [NEW] package grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit st
Public bug reported: This error popped up towards the end when installing Groovy Gorilla. However everything, at least at this point in time, seems to be working OK. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 ProcVersionSignature: Ubuntu 5.8.0-55.62-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 11 18:12:07 2021 ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-06-12 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.3 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931755 Title: package grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1931755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783377] Re: systemd-resolved updated by network-manager-strongswan needed to restart to use the new dns servers
This became an issue in Fedora 33 when they went to systemd-resolved. They have just packaged and updated to strongsWan 5.9.2 and I can confirm it resolves this issue without workarounds. This is a VPN, surely for security reasons alone we should be getting the latest packages as updates? This affects every version of Ubuntu 18 / Bionic as the latest I can find is 5.9.1 I would appreciate any hints on how to ask for something to be done... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783377 Title: systemd-resolved updated by network-manager-strongswan needed to restart to use the new dns servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925985] Re: CVE-2021-22204
** Changed in: libimage-exiftool-perl (Ubuntu) Status: In Progress => Fix Released ** Changed in: libimage-exiftool-perl (Ubuntu) Importance: Medium => High ** Changed in: libimage-exiftool-perl (Ubuntu Bionic) Importance: Undecided => High ** Changed in: libimage-exiftool-perl (Ubuntu Focal) Importance: Undecided => High ** Changed in: libimage-exiftool-perl (Ubuntu Groovy) Importance: Undecided => High ** Changed in: libimage-exiftool-perl (Ubuntu Hirsute) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925985 Title: CVE-2021-22204 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimage-exiftool-perl/+bug/1925985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930891] Autopkgtest regression report (golang-github-docker-go-connections/0.4.0-2ubuntu0.21.04.1)
All autopkgtests for the newly accepted golang-github-docker-go-connections (0.4.0-2ubuntu0.21.04.1) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: golang-github-containers-image/5.10.3-1ubuntu1 (s390x, ppc64el, arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#golang-github-docker-go- connections [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930891 Title: FTBFS in Hirsute is blocking runc migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-go-connections/+bug/1930891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926250] Re: CVE-2021-31826: Session recovery feature contains a null pointer deference
** Changed in: shibboleth-sp (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926250 Title: CVE-2021-31826: Session recovery feature contains a null pointer deference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shibboleth-sp/+bug/1926250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931306] Re: bionic: postfix-dbgsym package lacks DWARF information
So, I was able to confirm that just rebuilding the package does not fix the problem (Alexander had already confirmed this, btw). But I remembered seeing something about "-g" on d/rules, so I decided to take a look what the commit history for the Debian package and voilà, there's a very simple change that was pushed to fix this issue: https://salsa.debian.org/postfix-team/postfix- dev/-/commit/04a33ed8c10fa958a70c35a2808ac16e935742bd There's also a corresponding Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910291 Anyway, I've backported the fix, built the package on my PPA and verified that it does fix the problem. Here's the PPA, in case you would like to try: https://launchpad.net/~sergiodj/+archive/ubuntu/postfix- debuginfo/+packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931306 Title: bionic: postfix-dbgsym package lacks DWARF information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1931306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta-raspi/5.8.0.1027.30)
All autopkgtests for the newly accepted linux-meta-raspi (5.8.0.1027.30) for groovy have finished running. The following regressions have been reported in tests triggered by the package: xtrx-dkms/unknown (arm64) rtl8821ce/unknown (arm64) west-chamber/unknown (arm64) zfs-linux/unknown (arm64) virtualbox-hwe/unknown (arm64) r8168/unknown (arm64) openrazer/unknown (arm64) mali-midgard/unknown (arm64) v4l2loopback/unknown (arm64) systemd/unknown (arm64) snapd/unknown (arm64) systemd/246.6-1ubuntu1.3 (armhf) xtables-addons/unknown (arm64) rtl8812au/unknown (arm64) wireguard-linux-compat/unknown (arm64) openafs/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/groovy/update_excuses.html#linux-meta-raspi [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917904] Re: Arbitrary file reads
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917904 Title: Arbitrary file reads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1917904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931306] Re: bionic: postfix-dbgsym package lacks DWARF information
** Bug watch added: Debian Bug tracker #910291 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910291 ** Also affects: postfix (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910291 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/1931306 Title: bionic: postfix-dbgsym package lacks DWARF information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1931306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871644]
I can confirm this issue still exists in Fedora 34, Firefox 89, Wayland. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931698] Re: Can't uninstall firefox.
Thank you for adding extra details. I still don't see how you have met the requirements for the cinnamon desktop to remain in your case. The dep rules for your release can be see at https://packages.ubuntu.com/hirsute/cinnamon-desktop-environment meaning you need either - firefox-esr ; Package not available - or firefox ; Safe and easy web browser from Mozilla - or chromium ; Package not available - or gnome-www-browser ; virtual package provided by chromium-browser, epiphany-browser, firefox As your system had none of those, the removal of cinnamon needed to be performed, which was done; it worked as designed. (ie. your package-list contained none of those dependencies/requirements) ** Changed in: cinnamon-desktop-environment (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/1931698 Title: Can't uninstall firefox. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon-desktop-environment/+bug/1931698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886092] Re: libreoffice doesn't list gpg private key for a digital signature due to apparmor
Marcelo, you can see which versions of libreoffice are packaged in which Ubuntu releases via the libreoffice source package page on launchpad https://launchpad.net/ubuntu/+source/libreoffice There's a link at the bottom of that page to help you explore versions that might be published in PPAs. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886092 Title: libreoffice doesn't list gpg private key for a digital signature due to apparmor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1886092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0
Same issue Interesting thing, i got that errors, but all work fine, except libvirt/qemu/kvm, my VM didn't start. I go to logs and see that errors about i915 and suggest to restart libvirtd daemon, and when i stop admin socket ( meaning: sudo systemctl stop libvirtd-admin.socket ) system hangs up, exactly like in author post. Environment Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal Uname: Linux ThinkPad-E14 5.8.0-45-generic #51~20.04.1-Ubuntu SMP Tue Feb 23 13:46:31 UTC 2021 journalctl: Jun 12 01:51:06 ThinkPad-E14 kernel: i915 :00:02.0: [drm] Resetting rcs0 for CS error Jun 12 01:51:06 ThinkPad-E14 kernel: i915 :00:02.0: [drm] Renderer[68496] context reset due to GPU hang Jun 12 01:51:06 ThinkPad-E14 kernel: i915 :00:02.0: [drm] Resetting rcs0 for CS error Jun 12 01:51:06 ThinkPad-E14 kernel: i915 :00:02.0: [drm] Renderer[68496] context reset due to GPU hang Jun 12 01:51:06 ThinkPad-E14 kernel: i915 :00:02.0: [drm] GPU HANG: ecode 9:1:8cbf8db6, in Renderer [68496] Jun 12 01:51:06 ThinkPad-E14 kernel: i915 :00:02.0: [drm] Resetting rcs0 for CS error Jun 12 01:51:06 ThinkPad-E14 kernel: i915 :00:02.0: [drm] Renderer[68496] context reset due to GPU hang Jun 12 01:51:06 ThinkPad-E14 kernel: i915 :00:02.0: [drm] GPU HANG: ecode 9:1:8cbf8db6, in Renderer [68496] Jun 12 01:51:06 ThinkPad-E14 kernel: i915 :00:02.0: [drm] Resetting rcs0 for CS error Jun 12 01:51:06 ThinkPad-E14 kernel: i915 :00:02.0: [drm] Renderer[68496] context reset due to GPU hang Jun 12 01:51:06 ThinkPad-E14 kernel: i915 :00:02.0: [drm] GPU HANG: ecode 9:1:8cbf8db6, in Renderer [68496] Jun 12 01:51:06 ThinkPad-E14 kernel: i915 :00:02.0: [drm] Resetting rcs0 for CS error Jun 12 01:51:06 ThinkPad-E14 kernel: i915 :00:02.0: [drm] Renderer[68496] context reset due to GPU hang Jun 12 01:51:06 ThinkPad-E14 kernel: i915 :00:02.0: [drm] GPU HANG: ecode 9:1:8cbf8db6, in Renderer [68496] Jun 12 01:51:06 ThinkPad-E14 kernel: i915 :00:02.0: [drm] Resetting rcs0 for CS error -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861395 Title: system hang: i915 Resetting rcs0 for hang on rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1861395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577120] Re: Mounted NFS share prevents shutdown
I used to have intermittent hangs on shutdown with 16.04 , but with 20.04, the hangs always happen. Item #4 fixed my problem. I suggest #4 be added to the official tree unless someone can explain it is not a good idea. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577120 Title: Mounted NFS share prevents shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1577120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886092] Re: libreoffice doesn't list gpg private key for a digital signature due to apparmor
Today I upgraded libreoffice via PPA from version 7.1.2 to version 7.1.4 where the digital document signature function stopped working. When informed about the resolution of this bug in version 7.1.2, I didn't find the date of update of libreoffice from version 6.4.7 to 7.1.2 in ubuntu version 20.04, so I decided to test version 7.1.2 via PPA and it worked. With the update via PPA this function was now stopped working with version 7.1.4. Is there any relationship in ubuntu regarding these libreoffice versions? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886092 Title: libreoffice doesn't list gpg private key for a digital signature due to apparmor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1886092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918023] Re: Please remove armhf and s390x binaries for gdpc
This got done somewhere along the way :) ** Changed in: gdpc (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/1918023 Title: Please remove armhf and s390x binaries for gdpc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdpc/+bug/1918023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930891] Re: FTBFS in Hirsute is blocking runc migration
Hello Lucas, or anyone else affected, Accepted golang-github-docker-go-connections into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/golang-github-docker-go- connections/0.4.0-2ubuntu0.21.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- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: golang-github-docker-go-connections (Ubuntu Hirsute) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930891 Title: FTBFS in Hirsute is blocking runc migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-go-connections/+bug/1930891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931315] Re: Please drop php-laravel-framework (and associated components), and movim from impish
Removing packages from impish: ratchetphp 0.4.2-1build1 in impish php-cboden-ratchet 0.4.2-1build1 in impish amd64 php-cboden-ratchet 0.4.2-1build1 in impish arm64 php-cboden-ratchet 0.4.2-1build1 in impish armhf php-cboden-ratchet 0.4.2-1build1 in impish i386 php-cboden-ratchet 0.4.2-1build1 in impish ppc64el php-cboden-ratchet 0.4.2-1build1 in impish riscv64 php-cboden-ratchet 0.4.2-1build1 in impish s390x Comment: blocks php transition; LP: #1931315 1 package successfully removed. ** Changed in: ratchetphp (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/1931315 Title: Please drop php-laravel-framework (and associated components), and movim from impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/movim/+bug/1931315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931315] Re: Please drop php-laravel-framework (and associated components), and movim from impish
Removing packages from impish: php-robmorgan-phinx 0.9.2-3build1 in impish php-robmorgan-phinx 0.9.2-3build1 in impish amd64 php-robmorgan-phinx 0.9.2-3build1 in impish arm64 php-robmorgan-phinx 0.9.2-3build1 in impish armhf php-robmorgan-phinx 0.9.2-3build1 in impish i386 php-robmorgan-phinx 0.9.2-3build1 in impish ppc64el php-robmorgan-phinx 0.9.2-3build1 in impish riscv64 php-robmorgan-phinx 0.9.2-3build1 in impish s390x Comment: blocks php transition; LP: #1931315 1 package successfully removed. ** Changed in: php-robmorgan-phinx (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/1931315 Title: Please drop php-laravel-framework (and associated components), and movim from impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/movim/+bug/1931315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920959] Re: Remove rust-derive-more from hirsute{,-proposed}
Deleted on 2021-03-29.
** Changed in: rust-derive-more (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/1920959
Title:
Remove rust-derive-more from hirsute{,-proposed}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rust-derive-more/+bug/1920959/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920961] Re: Remove ams.lv2
Deleted on 2021-03-31. ** Changed in: ams.lv2 (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/1920961 Title: Remove ams.lv2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ams.lv2/+bug/1920961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926918] Re: cannot install libc6-dev, requires old libc6 version
I don't feel safe downgrading the package as https://serverfault.com/a/993629/272284 warns that this could break the system and my general ignorance on the subject. Will this resolve by itself once the new version superseding 2.31-0ubuntu9.3 is released and I update or are updates jammed as the previous comment by patrickdk suggests? I ran into this bug trying to install a package which depends on build- essential. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926918 Title: cannot install libc6-dev, requires old libc6 version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1926918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921100] Re: remove gconf-editor again, add it to sync blocklist
I don't think we want to blacklist this; it came back because it previously had an Ubuntu delta and was out of date, so the new version was synced. I expect any further uploads of gconf-editor to fix this bug, so no need to blacklist. Removing packages from impish-proposed: gconf-editor 3.0.1-6 in impish Comment: deprecated, build-depends on the deprecated gnome-doc-utils, removed from Debian; LP: #1921100 1 package successfully removed. ** Changed in: gconf-editor (Ubuntu) Status: New => Incomplete ** Changed in: gconf-editor (Ubuntu) Status: Incomplete => 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/1921100 Title: remove gconf-editor again, add it to sync blocklist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf-editor/+bug/1921100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901648] Re: docker.io package: cannot stat /var/lib/docker.migrating/*
I'm affected by this bug, too, and I confirm that @raczkow patch solves the problem -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901648 Title: docker.io package: cannot stat /var/lib/docker.migrating/* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1901648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931749] [NEW] cant upgarde from 20.10 to 21.04
Public bug reported: [42674:42674:0612/003912.211688:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. [42638:42638:0612/003913.486834:ERROR:CONSOLE(0)] "Unchecked runtime.lastError: The message port closed before a response was received.", source: chrome-extension://mpognobbkildjkofajifpdfhcoklimli/browser.html (0) [42638:42638:0612/003913.487063:ERROR:CONSOLE(0)] "Unchecked runtime.lastError: The message port closed before a response was received.", source: chrome-extension://mpognobbkildjkofajifpdfhcoklimli/browser.html (0) [42638:42638:0612/003914.012888:ERROR:password_sync_bridge.cc(446)] Passwords datatype error was encountered: Failed to load entries from password store. Encryption service failure. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.16 Uname: Linux 5.11.0-051100-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: KDE Date: Sat Jun 12 00:38:32 2021 InstallationDate: Installed on 2020-02-24 (473 days ago) InstallationMedia: Ubuntu-Studio 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2021-06-11 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931749 Title: cant upgarde from 20.10 to 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1931749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908411] Re: autopkgtest times out on armhf in bionic
Recent runs of this are passing so I'm setting this to Fix Released. ** Changed in: linux-hwe-5.4 (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/1908411 Title: autopkgtest times out on armhf in bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1908411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920674] Re: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation
5.13.0-6 (lp1920674-debug) with "blacklist=amdgpu modprobe.blacklist=amdgpu" then ssh and modprobe amdgpu: a) black screen but system keeps runnig b) dmesg attached ** Attachment added: "dmesg_5.13.0-6_ModprobeAmdgpu_noX.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920674/+attachment/5504173/+files/dmesg_5.13.0-6_ModprobeAmdgpu_noX.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920674 Title: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922754] Re: Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** 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/1922754 Title: Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925539] Re: ftrace synthetic_events selftests failure in 5.11
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** 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/1925539 Title: ftrace synthetic_events selftests failure in 5.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925075] Re: Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** 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/1925075 Title: Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** 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/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1925211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
Hello I am richard618921. I need to solve the error message debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable. What can I do ??? ** Changed in: aptdaemon Assignee: (unassigned) => RICARDO ALEXIS RESTREPO RENGIFO (richard618921) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/349469 Title: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/aptdaemon/+bug/349469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908279] Re: Unable to upgrade from 18.04LTS to 20.04LTS
Sorry for the delay in getting back to you. If you are still having an issue with this upgrade could you please open a new bug report using "ubuntu-bug ubuntu-release-upgrader"? Once you've done that let me know. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908279 Title: Unable to upgrade from 18.04LTS to 20.04LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1908279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931746] [NEW] Elantech touchpad
Public bug reported: Ubuntu doesn't detect my ElanTech touchpad in my HP 14-CF0006dx laptop. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-55-generic 5.8.0-55.62 ProcVersionSignature: Ubuntu 5.8.0-55.62-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: me 1266 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 14:07:35 2021 InstallationDate: Installed on 2021-03-07 (96 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b009 Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 003: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 006: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 14-cf0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=2a50d7fd-da1c-4180-90c5-4e12a54fc911 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-55-generic N/A linux-backports-modules-5.8.0-55-generic N/A linux-firmware1.190.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2020 dmi.bios.release: 15.59 dmi.bios.vendor: Insyde dmi.bios.version: F.59 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8544 dmi.board.vendor: HP dmi.board.version: KBC Version 74.34 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 74.34 dmi.modalias: dmi:bvnInsyde:bvrF.59:bd09/18/2020:br15.59:efr74.34:svnHP:pnHPLaptop14-cf0xxx:pvrType1ProductConfigId:rvnHP:rn8544:rvrKBCVersion74.34:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-cf0xxx dmi.product.sku: 5VQ99UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931746 Title: Elantech touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931728] Re: [scalingstack bos01] bionic (arm64) instances always fail to boot on eMAGs in this cloud
I don't have access to an eMAG system at the moment, but I tried and failed to reproduce on ThunderX 2 box by running xenial + hwe kernel + cloud-archive:queens. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931728 Title: [scalingstack bos01] bionic (arm64) instances always fail to boot on eMAGs in this cloud To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1931728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928259] Re: Package upgrade won't restart services
Bionic verification "TEST A" verification was done following steps from bug #1927745, where the lack of the restart was first found, and that fix is included in this upload as well. ubuntu@b-gssd-restart-1928259-1927745-A:~$ apt-cache policy nfs-common nfs-common: Installed: 1:1.3.4-2.1ubuntu5.3 Candidate: 1:1.3.4-2.1ubuntu5.3 Version table: *** 1:1.3.4-2.1ubuntu5.3 500 500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://br.archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 1:1.3.4-2.1ubuntu5 500 500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Problem quickly reproduced: ubuntu@b-gssd-restart-1928259-1927745-a:~$ sudo ./bz1419280_test_threads Iter 1 calling stat on '/mnt/test_krb5/foo' with uids 9995 through 10035 reproduced the bug after 1 iterations ubuntu@b-gssd-restart-1928259-1927745-a:~$ ps axw|grep stat_as 8012 pts/0D 0:00 ./stat_as /mnt/test_krb5/foo 9995 10035 8036 pts/0D 0:00 ./stat_as /mnt/test_krb5/foo 9995 10035 8091 pts/0S+ 0:00 grep --color=auto stat_as In this state, I installed the fixed packages from proposed. But first, let's get the rpc.gssd pid: ubuntu@b-gssd-restart-1928259-1927745-a:~$ ps axw | grep rpc\\.gssd 7854 ?Ss 0:00 /usr/sbin/rpc.gssd Now upgrade: ubuntu@b-gssd-restart-1928259-1927745-a:~$ sudo apt install nfs-common Reading package lists... Done (...) Do you want to continue? [Y/n] Get:1 http://br.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 nfs-common amd64 1:1.3.4-2.1ubuntu5.5 [206 kB] Get:2 http://br.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 nfs-kernel-server amd64 1:1.3.4-2.1ubuntu5.5 [93.8 kB] Fetched 299 kB in 0s (1479 kB/s) (Reading database ... 64831 files and directories currently installed.) Preparing to unpack .../nfs-common_1%3a1.3.4-2.1ubuntu5.5_amd64.deb ... Unpacking nfs-common (1:1.3.4-2.1ubuntu5.5) over (1:1.3.4-2.1ubuntu5.3) ... Preparing to unpack .../nfs-kernel-server_1%3a1.3.4-2.1ubuntu5.5_amd64.deb ... Unpacking nfs-kernel-server (1:1.3.4-2.1ubuntu5.5) over (1:1.3.4-2.1ubuntu5.3) ... Setting up nfs-common (1:1.3.4-2.1ubuntu5.5) ... Setting up nfs-kernel-server (1:1.3.4-2.1ubuntu5.5) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Processing triggers for ureadahead (0.100.0-21) ... Processing triggers for systemd (237-3ubuntu10.47) ... Not only was rpc.gssd restarted automatically (see new pid): ubuntu@b-gssd-restart-1928259-1927745-a:~$ ps axw | grep rpc\\.gssd 8886 ?Ss 0:00 /usr/sbin/rpc.gssd We also got rid of the stuck stat_as processes: ubuntu@b-gssd-restart-1928259-1927745-a:~$ ps axw|grep stat_as 9550 pts/0S+ 0:00 grep --color=auto stat_as TEST B ubuntu@b-gssd-restart-1928259-1927745-b:~$ diff -u pstree.old pstree.new ubuntu@b-gssd-restart-1928259-1927745-b:~$ l pstree.* -rw-rw-r-- 1 ubuntu ubuntu 633 Jun 11 20:55 pstree.new -rw-rw-r-- 1 ubuntu ubuntu 633 Jun 11 20:55 pstree.old
[Bug 1928259] Re: Package upgrade won't restart services
Focal verification TEST A Reproducing the bug with the focal package: ubuntu@f-gssd-restart-1928259-1927745-A:~$ apt-cache policy nfs-common nfs-common: Installed: 1:1.3.4-2.5ubuntu3.3 Candidate: 1:1.3.4-2.5ubuntu3.3 Version table: *** 1:1.3.4-2.5ubuntu3.3 500 500 http://br.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://br.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 1:1.3.4-2.5ubuntu3 500 500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages rpc.gssd running: ubuntu@f-gssd-restart-1928259-1927745-A:~$ pidof rpc.gssd 2968 Reinstall: ubuntu@f-gssd-restart-1928259-1927745-A:~$ sudo apt install --reinstall nfs-common Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 48 not upgraded. Need to get 204 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://br.archive.ubuntu.com/ubuntu focal-updates/main amd64 nfs-common amd64 1:1.3.4-2.5ubuntu3.3 [204 kB] Fetched 204 kB in 0s (10.1 MB/s) (Reading database ... 63643 files and directories currently installed.) Preparing to unpack .../nfs-common_1%3a1.3.4-2.5ubuntu3.3_amd64.deb ... Unpacking nfs-common (1:1.3.4-2.5ubuntu3.3) over (1:1.3.4-2.5ubuntu3.3) ... Setting up nfs-common (1:1.3.4-2.5ubuntu3.3) ... nfs-utils.service is a disabled or a static unit not running, not starting it. Processing triggers for man-db (2.9.1-1) ... Processing triggers for systemd (245.4-4ubuntu3.6) ... Same PID as before, so it wasn't restarted: ubuntu@f-gssd-restart-1928259-1927745-A:~$ pidof rpc.gssd 2968 Installing the package from proposed restarted rpc.gssd: ubuntu@f-gssd-restart-1928259-1927745-A:~$ sudo apt install nfs-common Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: watchdog The following packages will be upgraded: nfs-common 1 upgraded, 0 newly installed, 0 to remove and 67 not upgraded. Need to get 204 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://br.archive.ubuntu.com/ubuntu focal-proposed/main amd64 nfs-common amd64 1:1.3.4-2.5ubuntu3.4 [204 kB] Fetched 204 kB in 0s (1411 kB/s) (Reading database ... 63643 files and directories currently installed.) Preparing to unpack .../nfs-common_1%3a1.3.4-2.5ubuntu3.4_amd64.deb ... Unpacking nfs-common (1:1.3.4-2.5ubuntu3.4) over (1:1.3.4-2.5ubuntu3.3) ... Setting up nfs-common (1:1.3.4-2.5ubuntu3.4) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for systemd (245.4-4ubuntu3.6) ... New PID: ubuntu@f-gssd-restart-1928259-1927745-A:~$ pidof rpc.gssd 4131 TEST B ubuntu@f-gssd-restart-1928259-1927745-B:~$ diff -u pstree.old pstree.new ubuntu@f-gssd-restart-1928259-1927745-B:~$ l pstree.*
[Bug 1931648] Re: Brisk menu unevokable once calendar is open
I haven't changed the default one from 21.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931648 Title: Brisk menu unevokable once calendar is open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1931648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812194] Re: rtnetlink.sh in net from ubuntu_kernel_selftests failed on KVM kernels (config not enabled)
Observed on G/KVM, cycle sru-20210531 . ** Tags added: sru-20210531 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812194 Title: rtnetlink.sh in net from ubuntu_kernel_selftests failed on KVM kernels (config not enabled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856010] Re: xfrm_policy.sh / pmtu.sh / udpgso_bench.sh from net in ubuntu_kernel_selftests will fail with timeout if running the whole suite
Observed on G/KVM, cycle sru-20210531 . ** Tags added: sru-20210531 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856010 Title: xfrm_policy.sh / pmtu.sh / udpgso_bench.sh from net in ubuntu_kernel_selftests will fail with timeout if running the whole suite To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1856010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880645] Re: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / G / H
Observed on G/KVM, cycle sru-20210531 . ** Tags added: sru-20210531 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880645 Title: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / G / H To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1880645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887661] Re: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message
Observed on G/KVM, cycle sru-20210531 . ** Tags added: sru-20210531 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887661 Title: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1887661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/linux
Observed on G/KVM, cycle sru-20210531 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892213 Title: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1892213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905203] Re: selftests: net: fib_nexthops.sh in linux from Groovy/linux 5.8.0-30.32 ADT test failure
Observed on G/KVM, cycle sru-20210531 . ** Tags added: sru-20210531 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905203 Title: selftests: net: fib_nexthops.sh in linux from Groovy/linux 5.8.0-30.32 ADT test failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1905203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928259] Re: Package upgrade won't restart services
Groovy verification
TEST A
This time I followed the test from this bug exactly, without mounting an
actual NFSv4 share. I'll leave that test for the bionic case.
Reproducing the bug with the groovy package:
ubuntu@g-gssd-restart-1928259-1927745-A:~$ apt-cache policy nfs-common
nfs-common:
Installed: 1:1.3.4-2.5ubuntu6
Candidate: 1:1.3.4-2.5ubuntu6
Version table:
*** 1:1.3.4-2.5ubuntu6 500
500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
100 /var/lib/dpkg/status
ubuntu@g-gssd-restart-1928259-1927745-A:~$ pidof rpc.gssd
2600
Reinstall and we get the same pid:
ubuntu@g-gssd-restart-1928259-1927745-A:~$ sudo apt install --reinstall
nfs-common
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 204 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 nfs-common amd64
1:1.3.4-2.5ubuntu6 [204 kB]
Fetched 204 kB in 0s (10.7 MB/s)
(Reading database ... 64886 files and directories currently installed.)
Preparing to unpack .../nfs-common_1%3a1.3.4-2.5ubuntu6_amd64.deb ...
Unpacking nfs-common (1:1.3.4-2.5ubuntu6) over (1:1.3.4-2.5ubuntu6) ...
Setting up nfs-common (1:1.3.4-2.5ubuntu6) ...
nfs-utils.service is a disabled or a static unit not running, not starting it.
Processing triggers for man-db (2.9.3-2) ...
Processing triggers for systemd (246.6-1ubuntu1.3) ...
ubuntu@g-gssd-restart-1928259-1927745-A:~$ pidof rpc.gssd
2600
Now install the version from proposed:
ubuntu@g-gssd-restart-1928259-1927745-A:~$ apt-cache policy nfs-common
nfs-common:
Installed: 1:1.3.4-2.5ubuntu6.1
Candidate: 1:1.3.4-2.5ubuntu6.1
Version table:
*** 1:1.3.4-2.5ubuntu6.1 500
500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64
Packages
100 /var/lib/dpkg/status
1:1.3.4-2.5ubuntu6 500
500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
And rpc.gssd restarted:
ubuntu@g-gssd-restart-1928259-1927745-A:~$ pidof rpc.gssd
3721
TEST B
There was a diff in the pstree output, but unrelated to nfs services:
ubuntu@g-gssd-restart-1928259-1927745-B:~$ diff -u pstree.old pstree.new
--- pstree.old 2021-06-11 20:08:05.431952295 +
+++ pstree.new 2021-06-11 20:09:08.581416621 +
@@ -6,7 +6,7 @@
|-irqbalance---{irqbalance}
|-multipathd---6*[{multipathd}]
|-networkd-dispat
-|-packagekitd---3*[{packagekitd}]
+|-packagekitd---2*[{packagekitd}]
|-polkitd---2*[{polkitd}]
|-rpcbind
|-rsyslogd---3*[{rsyslogd}]
ubuntu@g-gssd-restart-1928259-1927745-B:~$ l pstree.*
-rw-rw-r-- 1 ubuntu ubuntu 678 Jun 11 20:09 pstree.new
-rw-rw-r-- 1 ubuntu ubuntu 678 Jun 11 20:08 pstree.old
Second pstree was with the package from proposed:
ubuntu@g-gssd-restart-1928259-1927745-A:~$ apt-cache policy nfs-common
nfs-common:
Installed: 1:1.3.4-2.5ubuntu6.1
Candidate: 1:1.3.4-2.5ubuntu6.1
Version table:
[Bug 1931728] Re: [scalingstack bos01] bionic (arm64) instances always fail to boot on eMAGs in this cloud
This is very strange. It looks like the guest has managed to start /init in the initramfs. /init is a simple shell script that just creates a few directories/mounts sysfs/proc, before printing "Loading, please wait" - which we do not see. I've tried to simulate this by removing /init from the initramfs, removing /bin/sh, and removing the loader (/lib/ld-linux-aarch64.so.1), but none cause the boot to fail in *this* way. I've asked for some more info from the scalingstack setup - the libvirt xml/qemu command with the hopes of reproducing it in a debug environment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931728 Title: [scalingstack bos01] bionic (arm64) instances always fail to boot on eMAGs in this cloud To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1931728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878389] Re: tpci from kernel_misc in ubuntu_ltp failed with Test-case '13'
Issue observed in G/KVM, cycle sru-20210531 . ** Tags added: sru-20210531 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878389 Title: tpci from kernel_misc in ubuntu_ltp failed with Test-case '13' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1878389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917601] Re: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.8.0-45.51
Issue observed for a long time in 5.8 kernels, for example G/KVM. ** Tags added: 5.8 groovy kvm sru-20210531 ** Tags added: sru-20210510 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917601 Title: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.8.0-45.51 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1917601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829979] Re: memcg_max_usage_in_bytes from controllers test suite in LTP failed
Issue observed in G/KVM, cycle sru-20210531 . Thanks krzk for the fix! Hope in next cycle we don't see it anymore in our tests. ** Tags added: sru-20210531 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829979 Title: memcg_max_usage_in_bytes from controllers test suite in LTP failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829984] Re: memcg_usage_in_bytes from controllers test suite in LTP failed
Issue observed in G/KVM, cycle sru-20210531 . ** Tags added: sru-20210531 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829984 Title: memcg_usage_in_bytes from controllers test suite in LTP failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928259] Re: Package upgrade won't restart services
** Description changed: [Impact] In order to get the fixes provided by a package update, the affected services shipped in it need to be restarted. When that restart does not happen, the system remains running the old binaries with the bug(s). This bug was found while testing the fix for #1927745, which affected rpc.gssd, one of the services shipped in nfs-common. Without the restart, systems that installed the update are still affected by the bug. [Test Plan] To make the test simple, we are not going to mount an NFSv4 share using kerberos. We are just going to have a minimal configuration that gets rpc.gssd running to demonstrate the before and after of this bug. For a more thorough testing, which includes actually mounting an NFSv4 export with kerberos, follow the test instructions of bug #1927745, and you will see that the manual restart included because of this bug here, after the package is updated, is no longer needed. TEST (A) # create a VM for the affected ubuntu release under test, login and run: sudo touch /etc/krb5.keytab sudo chmod 0600 /etc/krb5.keytab # install nfs-common sudo apt install nfs-common -y # note message about nfs-utils.service being disabled/static: nfs-utils.service is a disabled or a static unit, not starting it. # Manually start rpc-gssd. It will start, but since we have an empty # krb5.keytab file, it won't work. That's ok, we are not actually going to # mount nfsv4 - systemctl start rpc-gssd.service + sudo systemctl start rpc-gssd.service # Check it's running, and make note of its pid: pidof rpc.gssd 2994 # reinstall nfs-common sudo apt install --reinstall nfs-common # note rpc-gssd wasn't restarted pidof rpc.gssd 2994 # install the fixed nfs-common package. Notice the message about starting a disabled or static unit no longer appears: sudo apt install nfs-common # this time, rpc.gssd is restarted pidof rpc.gssd 5000 - TEST (B) This test is to confirm no new services are started after the fixed package is installed for the first time. # create a VM for the affected ubuntu release under test, login and run: sudo touch /etc/krb5.keytab sudo chmod 0600 /etc/krb5.keytab # install nfs-common that has the bug sudo apt install nfs-common -y # take a snapshot of running processes pstree > pstree.old # purge the nfs-common package sudo apt purge nfs-common -y # install the new nfs-common package sudo apt purge nfs-common -y # take a new pstree snapshot and compare with the old one pstree > pstree.new diff -u pstree.old pstree.new Should be no difference. - [Where problems could occur] Also known as "I'm doing an unconditional start in postinst, what could go wrong": - start services that were not started with the previous package on first install - systemd behavior change or bug and suddenly PartOf units also react to "start", instead of just "restart" and "stop" as documented - starting services that are not configured, and start fails, breaking postinst (but we have the proverbial || true to avoid that) [Other Info] This fix is a bit awkward, but I think it's in line with the SRU spirit of doing the least unpredictable change, and one that is simple and can be better understood. See the linked MP for an explanation of this fix, why it works, and other tests I did: https://code.launchpad.net/~ahasenack/ubuntu/+source/nfs-utils/+git/nfs-utils/+merge/403288 [Original Description] Upgrading the nfs-common debian package will not restart its services. Specifically, the package tries to restart "nfs-utils.service", which is a "fake" service meant to coordinate all the other daemons that make up a modern NFS server. This service, however, as it is, cannot be enabled: $ sudo systemctl enable nfs-utils.service The unit files have no installation config (WantedBy, RequiredBy, Also, Alias settings in the [Install] section, and DefaultInstance for template units). This means they are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). 4) In case of template units, the unit is meant to be enabled with some instance name specified Granted, d/rules of the nfs-utils package doesn't even try: dh_systemd_enable -p nfs-common nfs-client.target dh_systemd_enable -p nfs-kernel-server nfs-server.service dh_installinit -pnfs-common -R dh_systemd_start -p nfs-common --restart-after-upgrade nfs-utils.service dh_systemd_start -p
[Bug 1931481] Re: vault: hook failed: "start"
** Project changed: openstack-bundles => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931481 Title: vault: hook failed: "start" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1931481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931744] [NEW] Dell Precision 5750: internal mic stopped working after kernel update to 5.10.0-1029-oem
Public bug reported: On all kernel versions that I used before the 5.10.0-1029-oem the internal microphone of my Dell Precision 5750 worked perfectly. After the upgrade to 5.10.0-1029-oem the internal mic stopped working but I can still use an external mic. I couldn't enable the internal mic using pavucontrol and alsamixer. P.S. Looks like there is the same issue with Dell XPS 9700 (which is no wonder): https://askubuntu.com/questions/1343942/dell-xps-17-9700 -internal-microphone-not-working lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 ** Affects: linux-oem-5.10 (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/1931744 Title: Dell Precision 5750: internal mic stopped working after kernel update to 5.10.0-1029-oem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931740] Re: Bionic update: upstream stable patchset 2021-06-11
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931740 Title: Bionic update: upstream stable patchset 2021-06-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931481] [NEW] vault: hook failed: "start"
You have been subscribed to a public bug:
After a a server shoot down the valve is no starting again.with the error
vault 1.5.4error1 vault charmstore
44 ubuntu hook failed: "start"
tail /var/log/juju/unit-vault-0.log is
2021-06-09 19:04:10 WARNING start File
"/var/lib/juju/agents/unit-vault-0/.venv/lib/python3.8/site-packages/requests/sessions.py",
line 542, in request
2021-06-09 19:04:10 WARNING start resp = self.send(prep, **send_kwargs)
2021-06-09 19:04:10 WARNING start File
"/var/lib/juju/agents/unit-vault-0/.venv/lib/python3.8/site-packages/requests/sessions.py",
line 655, in send
2021-06-09 19:04:10 WARNING start r = adapter.send(request, **kwargs)
2021-06-09 19:04:10 WARNING start File
"/var/lib/juju/agents/unit-vault-0/.venv/lib/python3.8/site-packages/requests/adapters.py",
line 516, in send
2021-06-09 19:04:10 WARNING start raise ConnectionError(e, request=request)
2021-06-09 19:04:10 WARNING start requests.exceptions.ConnectionError:
HTTPConnectionPool(host='127.0.0.1', port=8220): Max retries exceeded with url:
/v1/auth/approle/login (Caused by
NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection
refused'))
2021-06-09 19:04:10 ERROR juju.worker.uniter.operation runhook.go:136 hook
"start" (via explicit, bespoke hook script) failed: exit status 1
2021-06-09 19:04:10 INFO juju.worker.uniter resolver.go:143 awaiting error
resolution for "start" hook
2021-06-09 19:06:11 INFO juju.worker.uniter resolver.go:143 awaiting error
resolution for "start" hook
my settings are:
OS: Focal
versions:
openstack-dashboard 18.6.1
keystone 18.0.0
nova-cloud-controller 22.0.1
nova-compute 22.0.1
nova-mysql-router 8.0.23
charm openstack base #73
openstack 4.0.0
** Affects: ubuntu
Importance: Undecided
Status: New
--
vault: hook failed: "start"
https://bugs.launchpad.net/bugs/1931481
You received this bug notification because you are a member of Ubuntu Bugs,
which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929756] Re: php-psr-* 1.x not compatible with php8
$ rmad php-psr-cache php-psr-cache | 1.0.1-2 | hirsute/universe | source php-psr-cache | 1.0.1-2 | impish/universe | source php-psr-cache | 3.0.0-1 | impish-proposed/universe | source php-psr-cache | 1.0.1-1 | stable | source php-psr-cache | 1.0.1-2 | testing | source php-psr-cache | 1.0.1-2 | unstable | source php-psr-cache | 3.0.0-1 | experimental | source $ rmad php-psr-container php-psr-container | 1.0.0-2 | hirsute/universe | source php-psr-container | 1.0.0-2 | impish/universe | source php-psr-container | 2.0.1-1 | impish-proposed/universe | source php-psr-container | 1.0.0-1 | stable | source php-psr-container | 1.0.0-2 | testing | source php-psr-container | 1.0.0-2 | unstable | source php-psr-container | 2.0.1-1 | experimental | source It seems we're a bit aggressive in moving to this newer PSR, as some packages' upstreams have not yet moved to it, but so far we've been able to make the necessary updates to those packages, and/or set them aside. ** Changed in: php-psr-container (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/1929756 Title: php-psr-* 1.x not compatible with php8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-psr-cache/+bug/1929756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931731] Re: pmtu.sh from selftests.net in linux ADT test failure with linux/5.8.0-56.63
This is now also showing up on F/hwe-5.8 amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l /linux-hwe-5.8/20210611_185322_b0873@/log.gz F/hwe-5.8 selftests.net use to fail with "Cannot find a vmlinux for VMLINUX_BTF at any of..." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931731 Title: pmtu.sh from selftests.net in linux ADT test failure with linux/5.8.0-56.63 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929630] Re: symfony 4.x incompatible with php8
symfony 5 has been imported into impish. It is not yet transitioned but it builds and passes its own tests. ** Changed in: symfony (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/1929630 Title: symfony 4.x incompatible with php8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/symfony/+bug/1929630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931743] [NEW] xcalib -gammacor .7 -a results in Error - unsupported ramp size 0 in 21.04
Public bug reported: Since installing 21.04, "xcalib -gammacor .7 -a " gets error "Error - unsupported ramp size 0" Before 21.04, this resulted in changing the gamma correction profile. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xcalib 0.8.dfsg1-2.1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 15:29:36 2021 InstallationDate: Installed on 2018-10-22 (962 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xcalib UpgradeStatus: Upgraded to hirsute on 2021-06-10 (1 days ago) ** Affects: xcalib (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931743 Title: xcalib -gammacor .7 -a results in Error - unsupported ramp size 0 in 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xcalib/+bug/1931743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931742] [NEW] Fonts not rendered properly in qpdfview on 21.04
Public bug reported: Since upgrading to 21.04, fonts not being rendered properly in qpdfview main window and also in the File - Print dialog. Same behavior observed in okular. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: qpdfview 0.4.18-4 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 15:20:36 2021 InstallationDate: Installed on 2018-10-22 (962 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qpdfview UpgradeStatus: Upgraded to hirsute on 2021-06-10 (1 days ago) ** Affects: qpdfview (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931742 Title: Fonts not rendered properly in qpdfview on 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdfview/+bug/1931742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931612] Re: Print dialog box shows same printer twice
https://gitlab.gnome.org/GNOME/gtk/-/issues/4025 filed Thanks for triaging this bug. ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #4025 https://gitlab.gnome.org/GNOME/gtk/-/issues/4025 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931612 Title: Print dialog box shows same printer twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1931612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931741] [NEW] Second Display Never Supports Proper Resolution
Public bug reported: I have tried cables, drivers, upgrades --no matter what I do I cannot get Ubuntu to recognize that my 32" UHD LG display supports 2560x1440. I can work around it with `cvt` and `xrandr` but this is tedious and is not saved across sessions, and xorg.conf is no longer a possibility (bricks the system). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 12:06:05 2021 DistUpgraded: 2021-06-11 10:51:25,279 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc5] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09a4] InstallationDate: Installed on 2021-03-08 (95 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Dell Inc. OptiPlex 7080 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to hirsute on 2021-06-11 (0 days ago) dmi.bios.date: 12/24/2020 dmi.bios.release: 1.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0J37VM dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd12/24/2020:br1.3:svnDellInc.:pnOptiPlex7080:pvr:rvnDellInc.:rn0J37VM:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7080 dmi.product.sku: 09A4 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931741 Title: Second Display Never Supports Proper Resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1931741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931612] Re: Print dialog box shows same printer twice
> "systemctl stop cups" removes the wrong entry -- the > one that actually works. So now I can't print any more. That's because that entry is controlled by cups. The other one isn't. As I said, cups is not involved in producing the duplicate entry. File a bug against GTK. systemctl start cups-browsed to get your working entry back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931612 Title: Print dialog box shows same printer twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1931612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931740] Re: Bionic update: upstream stable patchset 2021-06-11
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + upstream stable patchset 2021-06-11 + from git://git.kernel.org/ -upstream stable patchset 2021-06-11 -from git://git.kernel.org/ + openrisc: Fix a memory leak + RDMA/rxe: Clear all QP fields if creation failed + scsi: qla2xxx: Fix error return code in qla82xx_write_flash_dword() + ptrace: make ptrace() fail if the tracee changed its pid unexpectedly + cifs: fix memory leak in smb2_copychunk_range + ALSA: line6: Fix racy initialization of LINE6 MIDI + ALSA: usb-audio: Validate MS endpoint descriptors + ALSA: bebob/oxfw: fix Kconfig entry for Mackie d.2 Pro + Revert "ALSA: sb8: add a check for request_region" + ALSA: hda/realtek: reset eapd coeff to default value for alc287 + Revert "rapidio: fix a NULL pointer dereference when create_workqueue() fails" + rapidio: handle create_workqueue() failure + xen-pciback: reconfigure also from backend watch handler + dm snapshot: fix crash with transient storage and zero chunk size + Revert "video: hgafb: fix potential NULL pointer dereference" + Revert "net: stmicro: fix a missing check of clk_prepare" + Revert "leds: lp5523: fix a missing check of return value of lp55xx_read" + Revert "hwmon: (lm80) fix a missing check of bus read in lm80 probe" + Revert "video: imsttfb: fix potential NULL pointer dereferences" + Revert "ecryptfs: replace BUG_ON with error handling code" + Revert "gdrom: fix a memory leak bug" + cdrom: gdrom: deallocate struct gdrom_unit fields in remove_gdrom + cdrom: gdrom: initialize global variable at init time + Revert "media: rcar_drif: fix a memory disclosure" + Revert "rtlwifi: fix a potential NULL pointer dereference" + Revert "qlcnic: Avoid potential NULL pointer dereference" + Revert "niu: fix missing checks of niu_pci_eeprom_read" + ethernet: sun: niu: fix missing checks of niu_pci_eeprom_read() + net: stmicro: handle clk_prepare() failure during init + net: rtlwifi: properly check for alloc_workqueue() failure + leds: lp5523: check return value of lp5xx_read and jump to cleanup code + qlcnic: Add null check after calling netdev_alloc_skb + video: hgafb: fix potential NULL pointer dereference + vgacon: Record video mode changes with VT_RESIZEX + vt: Fix character height handling with VT_RESIZEX + tty: vt: always invoke vc->vc_sw->con_resize callback + video: hgafb: correctly handle card detect failure during probe + Bluetooth: SMP: Fail if remote and local public keys are identical + firmware: arm_scpi: Prevent the ternary sign expansion bug + platform/x86: dell-smbios-wmi: Fix oops on rmmod dell_smbios + locking/mutex: clear MUTEX_FLAGS if wait_list is empty due to signal + ALSA: hda/realtek: Add some CLOVE SSIDs of ALC293 + Revert "serial: mvebu-uart: Fix to avoid a potential NULL pointer dereference" + UBUNTU: upstream stable to v4.14.234, v4.19.192 + mm, vmstat: drop zone->lock in /proc/pagetypeinfo + usb: dwc3: gadget: Enable suspend events + NFC: nci: fix memory leak in nci_allocate_device + NFSv4: Fix a NULL pointer dereference in pnfs_mark_matching_lsegs_return() + iommu/vt-d: Fix sysfs leak in alloc_iommu() + perf intel-pt: Fix sample instruction bytes + perf intel-pt: Fix transaction abort handling + proc: Check /proc/$pid/attr/ writes against file opener + net: hso: fix control-request directions + mac80211: assure all fragments are encrypted + mac80211: prevent mixed key and fragment cache attacks + mac80211: properly handle A-MSDUs that start with an RFC 1042 header + cfg80211: mitigate A-MSDU aggregation attacks + mac80211: drop A-MSDUs on old ciphers + mac80211: add fragment cache to sta_info + mac80211: check defrag PN against current frame + mac80211: prevent attacks on TKIP/WEP as well + mac80211: do not accept/forward invalid EAPOL frames + mac80211: extend protection against mixed key and fragment cache attacks + ath10k: Validate first subframe of A-MSDU before processing the list + dm snapshot: properly fix a crash when an origin has no snapshots + kgdb: fix gcc-11 warnings harder + misc/uss720: fix memory leak in uss720_probe + thunderbolt:
[Bug 1931306] Re: bionic: postfix-dbgsym package lacks DWARF information
My bad: I built the package for Focal, which doesn't suffer from the bug. I haven't tested Bionic. Sorry about it. ** Also affects: postfix (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: postfix (Ubuntu Bionic) Status: New => Triaged ** Changed in: postfix (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: postfix (Ubuntu Focal) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931306 Title: bionic: postfix-dbgsym package lacks DWARF information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1931306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931740] [NEW] Bionic update: upstream stable patchset 2021-06-11
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-06-11 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931740 Title: Bionic update: upstream stable patchset 2021-06-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931612] Re: Print dialog box shows same printer twice
"systemctl stop cups" removes the wrong entry -- the one that actually works. So now I can't print any more. Interestingly, "systemctl start cups" does not restore the printer. Looks like I will have to reboot now to restore printing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931612 Title: Print dialog box shows same printer twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1931612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931612] Re: Print dialog box shows same printer twice
Correction; the second entry disappears. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931612 Title: Print dialog box shows same printer twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1931612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928259] Re: Package upgrade won't restart services
# Hirsute verification
## TEST A
I did the test from bug #1927745, which actually sets up a kerberized NFSv4
server/client on localhost.
With the original hirsute packages, after all that configuration, rpc.gssd was
running and I had the nfv4 mount point done:
ubuntu@h-gssd-restart-1928259-1927745:~$ ps fxaw|grep rpc\\.gssd
7882 ?Ss 0:00 /usr/sbin/rpc.gssd
ubuntu@h-gssd-restart-1928259-1927745:~$ mount -t nfs4
h-gssd-restart-1928259-1927745.example.com:/export on /mnt/test_krb5 type nfs4
(rw,relatime,vers=4.2,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=krb5,clientaddr=192.168.122.123,local_lock=none,addr=192.168.122.123)
I then updated to the nfs-{common,server} packages from hirsute-proposed:
ubuntu@h-gssd-restart-1928259-1927745:~$ apt-cache policy nfs-common
nfs-common:
Installed: 1:1.3.4-4ubuntu2.1
Candidate: 1:1.3.4-4ubuntu2.1
Version table:
*** 1:1.3.4-4ubuntu2.1 500
500 http://br.archive.ubuntu.com/ubuntu hirsute-proposed/main amd64
Packages
100 /var/lib/dpkg/status
And immediately after apt finished, I listed the processes again, and
rpc.gssd had a different pid:
ubuntu@h-gssd-restart-1928259-1927745:~$ ps fxaw|grep rpc\\.gssd
8780 ?Ss 0:00 /usr/sbin/rpc.gssd
## TEST B
Installed nfs-common from hirsute:
nfs-common:
Installed: 1:1.3.4-4ubuntu2
Candidate: 1:1.3.4-4ubuntu2
Version table:
*** 1:1.3.4-4ubuntu2 500
500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
ubuntu@h-gssd-restart-1928259-1927745-B:~$ pstree > pstree.old
ubuntu@h-gssd-restart-1928259-1927745-B:~$ l pstree.old
-rw-rw-r-- 1 ubuntu ubuntu 707 Jun 11 18:30 pstree.old
Installed new nfs-common:
ubuntu@h-gssd-restart-1928259-1927745-B:~$ apt-cache policy nfs-common
nfs-common:
Installed: 1:1.3.4-4ubuntu2.1
Candidate: 1:1.3.4-4ubuntu2.1
Version table:
*** 1:1.3.4-4ubuntu2.1 500
500 http://br.archive.ubuntu.com/ubuntu hirsute-proposed/main amd64
Packages
100 /var/lib/dpkg/status
1:1.3.4-4ubuntu2 500
500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
New pstree dump, and it's identical to the previous one:
ubuntu@h-gssd-restart-1928259-1927745-B:~$ pstree > pstree.new
ubuntu@h-gssd-restart-1928259-1927745-B:~$ l pstree.*
-rw-rw-r-- 1 ubuntu ubuntu 707 Jun 11 18:32 pstree.new
-rw-rw-r-- 1 ubuntu ubuntu 707 Jun 11 18:30 pstree.old
ubuntu@h-gssd-restart-1928259-1927745-B:~$ diff -u pstree.old pstree.new
ubuntu@h-gssd-restart-1928259-1927745-B:~$
Hirsute verification succeeded.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928259
Title:
Package upgrade won't restart services
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1928259/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863697] Re: not compatible with python3.8 on focal
Same here - why is this still not fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863697 Title: not compatible with python3.8 on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphite-web/+bug/1863697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931612] Re: Print dialog box shows same printer twice
The print dialog box is generated GTK. The Printers system setup dialog is probably generated by Qt. Stop cups: systemctl stop cups Which entry remains in the GTK print dialog box? I would guess - the first one. Therefore cups is not involved in its display. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931612 Title: Print dialog box shows same printer twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1931612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927272] Re: Some kernel selftests fail on linux-kvm
New observation: 13:41:43 DEBUG| [stdout] # ./ip_defrag: recv: payload_len = 8462 max_frag_len = 8: Resource temporarily unavailable 13:41:43 DEBUG| [stdout] not ok 18 selftests: net: ip_defrag.sh # exit=1 This is due to bug https://bugs.launchpad.net/ubuntu-kernel- tests/+bug/1908498 . Noticed on G/KVM, cycle sru-20210531 . ** Tags added: sru-20210531 ** Tags added: 5.4 5.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927272 Title: Some kernel selftests fail on linux-kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929516] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.15 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/1929516 Title: Failed to load DMC firmware i915/adls_dmc_ver2_01.bin To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931677] Please test proposed package
Hello koba, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.15 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/1931677 Title: [SRU][F/G][linux-firmware] add realtek 8852a wifi fimware To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1931677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931677] Re: [SRU][F/G][linux-firmware] add realtek 8852a wifi fimware
Hello koba, or anyone else affected, Accepted linux-firmware into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.190.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- 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: linux-firmware (Ubuntu Groovy) Status: In Progress => Fix Committed ** Changed in: linux-firmware (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931677 Title: [SRU][F/G][linux-firmware] add realtek 8852a wifi fimware To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1931677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917601] Re: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.8.0-45.51
Marked https://bugs.launchpad.net/bugs/1900662 as duplicate of this one. Same issue, and seems (per Christian) that is fixed on 4.0.6 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917601 Title: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.8.0-45.51 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1917601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917601] Re: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.8.0-45.51
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu Groovy) 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/1917601 Title: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.8.0-45.51 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1917601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917601] Re: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.8.0-45.51
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (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/1917601 Title: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.8.0-45.51 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1917601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931733] [NEW] ftracetest from selftests in linux ADT test failure with linux/5.4.0-75.84 (Max stack tracer)
Public bug reported: This is a scripted bug report about ADT failures while running linux tests for linux/5.4.0-75.84 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Problem appears to be isolated to Focal. Seeing on Focal/linux and Focal/hwe-5.8. ppc64el only. Failing with: ftrace - Max stack tracer [FAIL] Testing failed on: ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20210603_094441_f3830@/log.gz ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Summary changed: - linux ADT test failure with linux/5.4.0-75.84 + ftracetest from selftests in linux ADT test failure with linux/5.4.0-75.84 ** Summary changed: - ftracetest from selftests in linux ADT test failure with linux/5.4.0-75.84 + ftracetest from selftests in linux ADT test failure with linux/5.4.0-75.84 (Max stack tracer) ** Description changed: This is a scripted bug report about ADT failures while running linux tests for linux/5.4.0-75.84 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. + Problem appears to be isolated to Focal. Seeing on Focal/linux and + Focal/hwe-5.8. ppc64el only. + + Failing with: + ftrace - Max stack tracer [FAIL] + Testing failed on: - amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/linux/20210611_011314_332bc@/log.gz - arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/linux/20210609_074326_f3df0@/log.gz - ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20210603_094441_f3830@/log.gz - s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/linux/20210603_084654_a83cb@/log.gz + ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20210603_094441_f3830@/log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931733 Title: ftracetest from selftests in linux ADT test failure with linux/5.4.0-75.84 (Max stack tracer) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931315] Re: Please drop php-laravel-framework (and associated components), and movim from impish
Thanks vorlon! There are two more I missed in my original list, that should also be removed from the archive, for now: php-robmorgan-phinx/0.9.2-3build1 php-cboden-ratchet/0.4.2-1build1 These are movim dependencies that nothing else appears to require, that become uninstallable with the new symfony. stirling:~/pkg/Php8.0-transition/symfony/symfony-utkarsh$ apt-cache rdepends --recurse php-robmorgan-phinx php-robmorgan-phinx Reverse Depends: movim movim movim Reverse Depends: stirling:~/pkg/Php8.0-transition/symfony/symfony-utkarsh$ apt-cache rdepends --recurse php-cboden-ratchet php-cboden-ratchet Reverse Depends: movim movim movim Reverse Depends: ** Description changed: Please drop the Laravel eco-system from impish. This includes the following binary packages: php-illuminate-auth php-illuminate-broadcasting php-illuminate-bus php-illuminate-cache php-illuminate-config php-illuminate-console php-illuminate-container php-illuminate-contracts php-illuminate-cookie php-illuminate-database php-illuminate-encryption php-illuminate-events php-illuminate-filesystem php-illuminate-hashing php-illuminate-http php-illuminate-log php-illuminate-mail php-illuminate-notifications php-illuminate-pagination php-illuminate-pipeline php-illuminate-queue php-illuminate-redis php-illuminate-routing php-illuminate-session php-illuminate-support php-illuminate-translation php-illuminate-validation php-illuminate-view php-laravel-framework php-laravel-lumen-framework movim Currently, tests fail with PHP 8.0, Symfony 5, and newer PSR; this blocks our transition for symfony, and thus PHP 8.0. No updates to this ecosystem are currently available from Debian. + + Update -- These should also be dropped: + php-robmorgan-phinx + php-cboden-ratchet + + Only movim depended on these. [Discussion] Movim is a distributed social network built on XMPP and Illuminate. Illuminate is the namespace used by the Laravel project for its components. Laravel is a PHP-based, commercially-supported web framework that builds atop the Symfony web framework, providing a number of "1st-party" plugins for billing, auth, browser testing, etc. Laravel 6.20 was introduced in Debian ubuntu in Dec 2020, and auto- sync'd into Ubuntu hirsute at that time. (Current upstream is releasing Laravel 8.45, however 6.x is their LTS series, with security support through Sep. 2022.) For Ubuntu impish we are introducing PHP 8.0, and updating a number of PHP ecosystem pieces to their PHP 8 versions. Technically, Laravel 6.20 indicates support for PHP 8.0 itself (https://github.com/laravel/framework/commit/897a47136c2da2fdc7e19cee89c2f3a514192dee), however Laravel 6.20 appears to not be compatible with some of the other ecosystem pieces being introduced, and looks like significant work will be needed to get it transitioned. Upstream recommends to their new users to install Laravel via their Docker container [https://laravel.com/docs/8.x/installation]. Experienced users are directed to use PHP's package manager, 'composer', to install Laravel's PHP components from the web. 3rd party install guides found via google also walk users through using composer to install laravel, rather than install via apt. In general it appears users are relying on an Ubuntu LTS for the webserver and the PHP runtime, but prefer latest Laravel in order to get up-to-date security fixes and features. Debian's PopCon gives the php-laravel-framework and related components a 0.00% rating, with only 7 people having installed it (of which only 2 people used it recently). We do not have any data suggesting Ubuntu's install base is significantly different from Debian's. Given the above, it seems most helpful for end users to focus efforts on stabilizing the base PHP 8.0 components, and drop Laravel from the archive for Impish. Since Laravel was only just introduced in hirsute, and since the popcon numbers suggest few are using it yet, it's unlikely this change will have a notable impact to users. ** Also affects: php-robmorgan-phinx (Ubuntu) Importance: Undecided Status: New ** Also affects: ratchetphp (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/1931315 Title: Please drop php-laravel-framework (and associated components), and movim from impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/movim/+bug/1931315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[Bug 1887544] Re: upgrade from 18.04 to 20.04 fails to calculate if python-dbg is installed
@Toto - Yes this bug is considered closed. Could you please open a new bug report using "ubuntu-bug ubuntu-release-upgrader"? Once you've done that let me know and I'll have a look at the logs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887544 Title: upgrade from 18.04 to 20.04 fails to calculate if python-dbg is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1887544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931303] Re: Thinkpad T14 AMD Gen1 fresh installation bug
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931303 Title: Thinkpad T14 AMD Gen1 fresh installation bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1931303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931732] [NEW] package initramfs-tools 0.136ubuntu6.5 failed to install/upgrade: o subprocesso instalado, do pacote initramfs-tools, o script post-installation retornou erro do status de saída 1
Public bug reported: não instalou ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.5 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 9 03:03:16 2021 ErrorMessage: o subprocesso instalado, do pacote initramfs-tools, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2021-06-09 (2 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.5 failed to install/upgrade: o subprocesso instalado, do pacote initramfs-tools, o script post-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (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/1931732 Title: package initramfs-tools 0.136ubuntu6.5 failed to install/upgrade: o subprocesso instalado, do pacote initramfs-tools, o script post- installation retornou erro do status de saída 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1931732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931731] [NEW] pmtu.sh from selftests.net in linux ADT test failure with linux/5.8.0-56.63
Public bug reported: This is a scripted bug report about ADT failures while running linux tests for linux/5.8.0-56.63 on groovy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Looks to be isolated to Groovy and appearing on all arches. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/amd64/l/linux/20210610_035450_9c9b9@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/arm64/l/linux/20210611_103429_5c4be@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/ppc64el/l/linux/20210611_013418_76b18@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/s390x/l/linux/20210610_030630_fb359@/log.gz 02:56:31 DEBUG| [stdout] # selftests: net: pmtu.sh 02:56:31 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions [ OK ] 02:56:31 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions - nexthop objects [ OK ] 02:56:31 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions [ OK ] 02:56:32 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions - nexthop objects [ OK ] 02:56:33 DEBUG| [stdout] # TEST: IPv4 over vxlan4: PMTU exceptions [ OK ] 02:56:34 DEBUG| [stdout] # TEST: IPv4 over vxlan4: PMTU exceptions - nexthop objects [ OK ] 02:56:35 DEBUG| [stdout] # TEST: IPv6 over vxlan4: PMTU exceptions [ OK ] 02:56:36 DEBUG| [stdout] # TEST: IPv6 over vxlan4: PMTU exceptions - nexthop objects [ OK ] 02:56:38 DEBUG| [stdout] # TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] 02:56:39 DEBUG| [stdout] # TEST: IPv4 over vxlan6: PMTU exceptions - nexthop objects [ OK ] 02:56:40 DEBUG| [stdout] # TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] 02:56:41 DEBUG| [stdout] # TEST: IPv6 over vxlan6: PMTU exceptions - nexthop objects [ OK ] 02:56:43 DEBUG| [stdout] # TEST: IPv4 over geneve4: PMTU exceptions [ OK ] 02:56:44 DEBUG| [stdout] # TEST: IPv4 over geneve4: PMTU exceptions - nexthop objects [ OK ] 02:56:45 DEBUG| [stdout] # TEST: IPv6 over geneve4: PMTU exceptions [ OK ] 02:56:46 DEBUG| [stdout] # TEST: IPv6 over geneve4: PMTU exceptions - nexthop objects [ OK ] 02:56:48 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions [FAIL] 02:56:48 DEBUG| [stdout] # PMTU exception wasn't created after exceeding link layer MTU on geneve interface 02:56:49 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions - nexthop objects [FAIL] 02:56:49 DEBUG| [stdout] # PMTU exception wasn't created after exceeding link layer MTU on geneve interface 02:56:50 DEBUG| [stdout] # TEST: IPv6 over geneve6: PMTU exceptions [ OK ] 02:56:51 DEBUG| [stdout] # TEST: IPv6 over geneve6: PMTU exceptions - nexthop objects [ OK ] 02:56:53 DEBUG| [stdout] # TEST: IPv4 over fou4: PMTU exceptions [ OK ] 02:56:54 DEBUG| [stdout] # TEST: IPv4 over fou4: PMTU exceptions - nexthop objects [ OK ] 02:56:56 DEBUG| [stdout] # TEST: IPv6 over fou4: PMTU exceptions [ OK ] 02:56:57 DEBUG| [stdout] # TEST: IPv6 over fou4: PMTU exceptions - nexthop objects [ OK ] 02:56:58 DEBUG| [stdout] # TEST: IPv4 over fou6: PMTU exceptions [ OK ] 02:56:59 DEBUG| [stdout] # TEST: IPv4 over fou6: PMTU exceptions - nexthop objects [ OK ] 02:57:01 DEBUG| [stdout] # TEST: IPv6 over fou6: PMTU exceptions [ OK ] 02:57:02 DEBUG| [stdout] # TEST: IPv6 over fou6: PMTU exceptions - nexthop objects [ OK ] 02:57:03 DEBUG| [stdout] # TEST: IPv4 over gue4: PMTU exceptions [ OK ] 02:57:04 DEBUG| [stdout] # TEST: IPv4 over gue4: PMTU exceptions - nexthop objects [ OK ] 02:57:05 DEBUG| [stdout] # TEST: IPv6 over gue4: PMTU exceptions [ OK ] 02:57:07 DEBUG| [stdout] # TEST: IPv6 over gue4: PMTU exceptions - nexthop objects [ OK ] 02:57:08 DEBUG| [stdout] # TEST: IPv4 over gue6: PMTU exceptions [ OK ] 02:57:09 DEBUG| [stdout] # TEST: IPv4 over gue6: PMTU exceptions - nexthop objects [ OK ] 02:57:10 DEBUG| [stdout] # TEST: IPv6 over gue6: PMTU exceptions [ OK ] 02:57:11 DEBUG| [stdout] # TEST: IPv6 over gue6: PMTU exceptions - nexthop objects [ OK ] 02:57:13 DEBUG| [stdout] # TEST: IPv4 over IPv4: PMTU exceptions [ OK ] 02:57:14 DEBUG| [stdout] # TEST: IPv4 over IPv4: PMTU exceptions - nexthop objects [ OK ]
[Bug 1921781] Re: Build-depends on qt5-default which is obsolete and dropped in hirsute
indicator-sound has reverse-dependencies, so this probably needs fixed rather than removed. ** Changed in: poppler-qml-plugin (Ubuntu) Status: New => Fix Released ** Changed in: qtpowerd (Ubuntu) Status: New => Fix Released ** Changed in: qtubuntu-cameraplugin-fake (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/1921781 Title: Build-depends on qt5-default which is obsolete and dropped in hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1921781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta/5.8.0.56.61)
All autopkgtests for the newly accepted linux-meta (5.8.0.56.61) for groovy have finished running. The following regressions have been reported in tests triggered by the package: systemd/246.6-1ubuntu1.3 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/groovy/update_excuses.html#linux-meta [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
