[Bug 1955107] [NEW] package libreoffice-common 1:6.4.7-0ubuntu0.20.04.1 failed to install/upgrade: unable to open '/usr/lib/libreoffice/share/gallery/personas/gray/footer.png.dpkg-new': Operation not
Public bug reported: this is occurred during sudo apt upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-common 1:6.4.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 17 13:25:09 2021 ErrorMessage: unable to open '/usr/lib/libreoffice/share/gallery/personas/gray/footer.png.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-09-24 (83 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: libreoffice Title: package libreoffice-common 1:6.4.7-0ubuntu0.20.04.1 failed to install/upgrade: unable to open '/usr/lib/libreoffice/share/gallery/personas/gray/footer.png.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (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/1955107 Title: package libreoffice-common 1:6.4.7-0ubuntu0.20.04.1 failed to install/upgrade: unable to open '/usr/lib/libreoffice/share/gallery/personas/gray/footer.png.dpkg- new': Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1955107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955108] [NEW] package linux-headers-5.11.0-43-generic 5.11.0-43.47~20.04.2 failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-43-generic/include/config/textsearch/fsm.h.dpk
Public bug reported: occurred during apt upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.11.0-43-generic 5.11.0-43.47~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-headers-5.11.0-43-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 17 13:28:30 2021 DpkgTerminalLog: Preparing to unpack .../linux-headers-5.11.0-43-generic_5.11.0-43.47~20.04.2_amd64.deb ... Unpacking linux-headers-5.11.0-43-generic (5.11.0-43.47~20.04.2) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-headers-5.11.0-43-generic_5.11.0-43.47~20.04.2_amd64.deb (--unpack): unable to open '/usr/src/linux-headers-5.11.0-43-generic/include/config/textsearch/fsm.h.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-5.11.0-43-generic/include/config/textsearch/fsm.h.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-09-24 (83 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-headers-5.11.0-43-generic 5.11.0-43.47~20.04.2 failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-43-generic/include/config/textsearch/fsm.h.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-5.11 (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/1955108 Title: package linux-headers-5.11.0-43-generic 5.11.0-43.47~20.04.2 failed to install/upgrade: unable to open '/usr/src/linux- headers-5.11.0-43-generic/include/config/textsearch/fsm.h.dpkg-new': Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1955108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
I'm still having issues with this driver on Kernels later than 5.11 installed with Ubuntu Mainline - can it be the case that these drivers are not set for those? Here is a full dmesg output: [4.557452] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [4.557589] sof-audio-pci-intel-tgl :00:1f.3: SoundWire enabled on CannonLake+ platform, using SOF driver [4.557639] sof-audio-pci-intel-tgl :00:1f.3: enabling device ( -> 0002) [4.557935] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [4.558004] sof-audio-pci-intel-tgl :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.565246] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode [4.579175] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 4 [4.662581] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 1:6:1-53680 [4.662585] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:17:0 Kernel ABI 3:18:0 [4.701918] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:17:0 Kernel ABI 3:18:0 [4.714224] sof-audio-pci-intel-tgl :00:1f.3: ASoC: physical link SDW3-Capture (id 4) not exist [4.714254] sof-audio-pci-intel-tgl :00:1f.3: ASoC: topology: could not load header: -22 [4.714331] sof-audio-pci-intel-tgl :00:1f.3: error: tplg component load failed -22 [4.714360] sof-audio-pci-intel-tgl :00:1f.3: error: failed to load DSP topology -22 [4.714383] sof-audio-pci-intel-tgl :00:1f.3: ASoC: error at snd_soc_component_probe on :00:1f.3: -22 [4.714424] sof_sdw sof_sdw: ASoC: failed to instantiate card -22 [4.720966] sof_sdw sof_sdw: snd_soc_register_card failed -22 [4.720985] sof_sdw: probe of sof_sdw failed with error -22 Anything I could do? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945565] Re: [SRU] Revert amdgpu/renoir firmware
doesn't look like anything left to do to the kernel here ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Invalid ** 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/1945565 Title: [SRU] Revert amdgpu/renoir firmware To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726856] Re: ufw does not start automatically at boot
I have the same issue on an computer with NVME. Maybe the boot is too fast? The fix and all workarounds (cron) haven't helped. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726856 Title: ufw does not start automatically at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1726856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930086] Re: [22.04 FEAT] gcc tunings for power9
now built in jammy-proposed ** Changed in: llvm-toolchain-13 (Ubuntu) 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/1930086 Title: [22.04 FEAT] gcc tunings for power9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1930086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726856] Re: ufw does not start automatically at boot
Im using Ubuntu 20.04 by the way. To make clear what I meant: I think the dependencies aren't defined right such that some services are starting to early. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726856 Title: ufw does not start automatically at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1726856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955109] [NEW] boot menu not appearing after manual install of jellyfish daily build
Public bug reported: desktop amd64 PC, UEFI, 8 core processor, 16gb RAM, nVidia graphics card, several ssd's manual install of Kubuntu Jellyfish to a partition on ssd alongside Kubuntu Focal LTS I am testing an installation of Kubuntu Jellyfish daily build alongside Kubuntu Focal 20.04.3 Usually this proceeds without a problem. Since the 16th Dec daily build of Jammy, the boot menu does not appear any more after installation, also booting ignores Kubuntu Focal and proceeds directly to Kubuntu 22.04. I recovered the boot menu on this PC by running boot-restore from an iso of Kubuntu Focal both Focal and Jelly fish are then available from the boot menu. This bug appears in Kubuntu Jammy after a manual install directly to the computer's ssd. I'm not an expert at bug reporting, so if this report is incorrectly set out or if more info is needed I'm happy to follow instructions. I'll keep an eye on this thread. I think the problem is with Jammy, not Focal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Dec 17 08:24:04 2021 InstallationDate: Installed on 2020-10-27 (416 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Summary changed: - boot menu not appearing after install of jellyfish daily build + boot menu not appearing after manual install of jellyfish daily build ** Tags removed: focal ** Tags added: jammy ** Description changed: desktop amd64 PC, UEFI, 8 core processor, 16gb RAM, nVidia graphics card, several ssd's manual install of Kubuntu Jellyfish to a partition on ssd alongside Kubuntu Focal LTS I am testing an installation of Kubuntu Jellyfish daily build alongside Kubuntu Focal 20.04.3 Usually this proceeds without a problem. Since the 16th Dec daily build of Jammy, a boot menu does not appear any more after installation, also booting ignores Kubuntu Focal and proceeds directly to Kubuntu 22.04. I recovered the boot menu on this PC by running boot-restore from an iso of Kubuntu Focal both Focal and Jelly fish are then available from the boot menu. This bug appears in Kubuntu Jammy after a manual install directly to the computer's ssd. + I'm not an expert at bug reporting, so if this report is incorrectly set out or if more info is needed I'm happy to follow instructions. + I'll keep an eye on this thread. + I think the problem is with Jammy, not Focal. + ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Dec 17 08:24:04 2021 InstallationDate: Installed on 2020-10-27 (416 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: grub2 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/1955109 Title: boot menu not appearing after manual install of jellyfish daily build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1955109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726856] Re: ufw does not start automatically at boot
Running "/usr/bin/sleep 10 && /usr/sbin/ufw enable" via cron works for me -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726856 Title: ufw does not start automatically at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1726856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955109] Re: boot menu not appearing after manual install of jellyfish daily build
** Description changed: desktop amd64 PC, UEFI, 8 core processor, 16gb RAM, nVidia graphics card, several ssd's manual install of Kubuntu Jellyfish to a partition on ssd alongside Kubuntu Focal LTS I am testing an installation of Kubuntu Jellyfish daily build alongside Kubuntu Focal 20.04.3 Usually this proceeds without a problem. - Since the 16th Dec daily build of Jammy, a boot menu does not appear any - more after installation, also booting ignores Kubuntu Focal and proceeds - directly to Kubuntu 22.04. + Since the 16th Dec daily build of Jammy, the boot menu does not appear + any more after installation, also booting ignores Kubuntu Focal and + proceeds directly to Kubuntu 22.04. I recovered the boot menu on this PC by running boot-restore from an iso of Kubuntu Focal both Focal and Jelly fish are then available from the boot menu. This bug appears in Kubuntu Jammy after a manual install directly to the computer's ssd. I'm not an expert at bug reporting, so if this report is incorrectly set out or if more info is needed I'm happy to follow instructions. I'll keep an eye on this thread. I think the problem is with Jammy, not Focal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Dec 17 08:24:04 2021 InstallationDate: Installed on 2020-10-27 (416 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: desktop amd64 PC, UEFI, 8 core processor, 16gb RAM, nVidia graphics card, several ssd's manual install of Kubuntu Jellyfish to a partition on ssd alongside Kubuntu Focal LTS I am testing an installation of Kubuntu Jellyfish daily build alongside Kubuntu Focal 20.04.3 Usually this proceeds without a problem. Since the 16th Dec daily build of Jammy, the boot menu does not appear any more after installation, also booting ignores Kubuntu Focal and proceeds directly to Kubuntu 22.04. I recovered the boot menu on this PC by running boot-restore from an iso of Kubuntu Focal both Focal and Jelly fish are then available from the - boot menu. + restored boot menu. This bug appears in Kubuntu Jammy after a manual install directly to the computer's ssd. I'm not an expert at bug reporting, so if this report is incorrectly set out or if more info is needed I'm happy to follow instructions. I'll keep an eye on this thread. I think the problem is with Jammy, not Focal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Dec 17 08:24:04 2021 InstallationDate: Installed on 2020-10-27 (416 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: desktop amd64 PC, UEFI, 8 core processor, 16gb RAM, nVidia graphics card, several ssd's manual install of Kubuntu Jellyfish to a partition on ssd alongside Kubuntu Focal LTS I am testing an installation of Kubuntu Jellyfish daily build alongside Kubuntu Focal 20.04.3 Usually this proceeds without a problem. Since the 16th Dec daily build of Jammy, the boot menu does not appear any more after installation, also booting ignores Kubuntu Focal and proceeds directly to Kubuntu 22.04. I recovered the boot menu on this PC by running boot-restore from an iso of Kubuntu Focal both Focal and Jelly fish are then available from the restored boot menu. This bug appears in Kubuntu Jammy after a manual install directly to the computer's ssd. I'm not an expert at bug reporting, so if this report is incorrectly set out or if more info is needed I'm happy to follow instructions. I'll keep an eye on this thread. - I think the problem is with Jammy, not Focal. + I think the problem is with the Jammy iso, not Focal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Dec 17 08:24:04 2021 InstallationDate: Installed on 2020-10-27 (416 days ago) InstallationMedia:
[Bug 1955109] Re: boot menu not appearing after manual install of jellyfish daily build
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1955109 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955109 Title: boot menu not appearing after manual install of jellyfish daily build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1955109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955109] Re: boot menu not appearing after manual install of jellyfish daily build
Yes, this is expected. os-prober has been disabled for security reasons in 2.06. grub2 (2.06-1) UNRELEASED; urgency=medium * Boot menu entries for other operating systems are no longer generated by default. To re-enable this, set GRUB_DISABLE_OS_PROBER=false in /etc/default/grub. -- Colin Watson Wed, 18 Aug 2021 13:03:23 +0100 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955109 Title: boot menu not appearing after manual install of jellyfish daily build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1955109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939733] Re: [OSSA-2021-005] Arbitrary dnsmasq reconfiguration via extra_dhcp_opts (CVE-2021-40085)
** Tags removed: neutron-proactive-backport-potential -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939733 Title: [OSSA-2021-005] Arbitrary dnsmasq reconfiguration via extra_dhcp_opts (CVE-2021-40085) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1939733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950720] Re: GSYNC bug regression in 495.44 Ubuntu 21.10
This problem persists on driver 495.46 from NVIDIA website which stated the same regression fix in the patch notes, there was no change in the flickering on G-SYNC mode change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950720 Title: GSYNC bug regression in 495.44 Ubuntu 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1950720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954300] Re: mt7921e: Failed to start WM firmware
** No longer affects: linux-oem-5.13 (Ubuntu Impish) ** No longer affects: linux-oem-5.13 (Ubuntu Jammy) ** No longer affects: linux-oem-5.13 (Ubuntu) ** No longer affects: linux-oem-5.14 (Ubuntu Impish) ** No longer affects: linux-oem-5.14 (Ubuntu Jammy) ** No longer affects: linux-oem-5.14 (Ubuntu) ** No longer affects: linux (Ubuntu Focal) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954300 Title: mt7921e: Failed to start WM firmware To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953249] Re: UVD firmware for AMD Southern Islands (GCN 1) GPUs is missing
** Changed in: linux-firmware (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953249 Title: UVD firmware for AMD Southern Islands (GCN 1) GPUs is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1953249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954818] Re: Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish, and 470 in Focal
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-470 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-470/470.86-0ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954818 Title: Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish, and 470 in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1954818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955114] [NEW] swtpm: upgrade to jammy fails
Public bug reported: While trying to upgrade from impish to jammy I get: Preparing to unpack .../swtpm_0.6.1-0ubuntu5_amd64.deb ... Unpacking swtpm (0.6.1-0ubuntu5) over (0.6.1) ... dpkg: error processing archive /var/cache/apt/archives/swtpm_0.6.1-0ubuntu5_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/swtpm/libswtpm_libtpms.so.0.0.0', which is also in package swtpm-libs:amd64 0.6.1 Errors were encountered while processing: /var/cache/apt/archives/swtpm_0.6.1-0ubuntu5_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) I had previously installed the swtpm package using the upstream source as the package was not available for Impish. Best regards Heinrich ** Affects: swtpm (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/1955114 Title: swtpm: upgrade to jammy fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/swtpm/+bug/1955114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955116] [NEW] mk-sbuild create error due to bullseye security move
Public bug reported: Probably very similar to 1916633 reported and fixed in pbuilder-dist. while using `mk-sbuild --name foobar bullseye` ``` E: The repository 'http://security.debian.org bullseye/updates Release' does not have a Release file. ``` Bullseye changed the format of security suite: https://www.debian.org/releases/bullseye/amd64/release-notes/ch- information.en.html#security-archive and should look like: ``` deb https://deb.debian.org/debian-security bullseye-security main contrib ``` while mk-sbuild is still generating the older format as found in buster and earlier: ``` deb http://security.debian.org/ bullseye/updates main non-free contrib ``` at this bit of the code: https://git.launchpad.net/ubuntu/+source/ubuntu-dev-tools/tree/mk- sbuild#n661 ** Affects: ubuntu-dev-tools (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-dev-tools (Debian) 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/1955116 Title: mk-sbuild create error due to bullseye security move To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1955116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955114] Re: swtpm: upgrade to jammy fails
Can we mark package swtpm as replacing swtpm-libs? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955114 Title: swtpm: upgrade to jammy fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/swtpm/+bug/1955114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955109] Re: boot menu not appearing after manual install of jellyfish daily build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: grub2 (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/1955109 Title: boot menu not appearing after manual install of jellyfish daily build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1955109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947820] Re: [SRU] Backport xorg-server 1.20.13 to focal
** Changed in: oem-priority 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/1947820 Title: [SRU] Backport xorg-server 1.20.13 to focal To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1947820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955114] Re: swtpm: upgrade to jammy fails
To overcome the problem on my machine I removed the following lines /var/lib/dpkg/info/swtpm-libs:amd64.list:6:/usr/lib/x86_64-linux-gnu/swtpm/libswtpm_libtpms.so.0.0.0 /var/lib/dpkg/info/swtpm-libs:amd64.list:12:/usr/lib/x86_64-linux-gnu/swtpm/libswtpm_libtpms.so.0 and ran 'apt-get purge swtpm-libs'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955114 Title: swtpm: upgrade to jammy fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/swtpm/+bug/1955114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955116] Re: mk-sbuild create error due to bullseye security move
** Bug watch added: Debian Bug tracker #1001832 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001832 ** Also affects: ubuntu-dev-tools (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001832 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/1955116 Title: mk-sbuild create error due to bullseye security move To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1955116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927205] Re: Chromium menu is blank and freezes application
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (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/1927205 Title: Chromium menu is blank and freezes application To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1927205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955081] Re: Right-click on terminal causing no demand to enter user's password
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1955081 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955081 Title: Right-click on terminal causing no demand to enter user's password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1955081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954818] Re: Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish, and 470 in Focal
** Description changed:
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/NVidiaUpdates
Certification test suite must pass on a range of hardware:
https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu
The QA team that executed the tests will be in charge of attaching the
artifacts and console output of the appropriate run to the bug. nVidia
maintainers team members will not mark ‘verification-done’ until this
has happened.
[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned system level tests are attached to this bug.
[Discussion]
[Changelog]
== 470 (focal only) ==
nvidia-graphics-drivers-470 (470.86-0ubuntu0.20.04.2) focal;
urgency=medium
- * debian/{nvidia_supported|pm-aliases-gen}:
- - Drop the following IDs in favour of the 495 series (LP: #1954818):
- 1fbc, 249c, 249d, 24b6, 24b7, 24b8,
- 25a0, 25b8.
-
+ * debian/{nvidia_supported|pm-aliases-gen}:
+ - Drop the following IDs in favour of the 495 series (LP: #1954818):
+ 1fbc, 249c, 249d, 24b6, 24b7, 24b8,
+ 25a0, 25b8.
== 495 (bionic, focal, hirsute, impish) ==
nvidia-graphics-drivers-495 (495.46-0ubuntu*)
- * debian/additional_card_ids,
- debian/additional_runtimepm_ids:
- - Add the following IDs:
- 1FBC 249C 249D 24B6 24B7 24B8 25A0 25B8
- * New upstream release (LP: #1954818):
- - Added support for the GBM API. This adds the new symlink
- nvidia-drm_gbm.so pointing to the file libnvidia-
- allocator.so.VERSION to implement a GBM backend driver usable
- with the GBM loader from the Mesa project version 21.2 and
- above, as well as the files libnvidia-egl-gbm.so.1.1.0 and
- 15_nvidia_gbm.json, which implement EGL support for the GBM
- platform (EGL_KHR_platform_gbm).
- - Add indicator for Resizable BAR support on compatible systems.
- - Fixed a bug that could cause the X server to crash when
- starting a new server generation on PRIME configurations.
- - Removed support for NvIFROpenGL. This functionality was
- deprecated in the 470.xx driver release.
- - Removed libnvidia-cbl.so from the driver package. This
- functionality is now provided by other driver libraries.
- - Changed the minimum required Linux kernel version from 2.6.32
- to 3.10.
- - Updated nvidia.ko to load even if no supported NVIDIA GPUs are
- present when an NVIDIA NVSwitch device is detected in the
- system. Previously, nvidia.ko would fail to load into the
- kernel if no supported GPUs were present.
- - Fixed a bug in the Vulkan driver where unused input attributes
- to a vertex shader would corrupt the interpolation qualifiers
- for the shader.
- - Fixed a bug in the Vulkan driver where individual components of
- barycentric inputs could not be read.
- - Added support for the VK_KHR_present_id extension.
- - Added support for the VK_KHR_present_wait extension.
- - Added support for the
- VK_KHR_shader_subgroup_uniform_control_flow extension.
- - Fixed a bug where VK_NVX_binary_import was advertised as
- supported on unsupported platforms. This caused calls to
- vkCreateDevice to fail if applications attempted to enable
- VK_NVX_binary_import on such platforms.
- - Added a new command line option, "--no-peermem", to nvidia-
- installer. Selecting this option prevents the installation of
- the nvidia-peermem kernel module.
- - Fixed a regression which prevented DisplayPort and HDMI 2.1
- variable refresh rate (VRR) G-SYNC Compatible monitors from
- functioning correctly in variable refresh rate mode, resulting
- in issues such as flickering.
- - Fixed a bug that can cause a kernel crash in SLI Mosaic
- configurations.
- - Added support for the EGL_NV_robustness_video_memory_purge
- extension.
+ [ Daniel van Vugt ]
+ * debian/templates/libnvidia-extra-flavour.links.in:
+ - Move nvidia-drm_gbm.so into the gbm/ library subdirectory
+ which is where Mesa searches for it.
+
+ [ Alberto Milone ]
+ * debian/additional_card_ids,
+ debian/additional_runtimepm_ids:
+ - Add the following IDs:
+ 1FBC 249C 249D 24B6 24B7 24B8 25A0 25B8
+
+ * New upstream release (LP: #1954818):
+ - Added support for the GBM API. This adds the new symlink
+ nvidia-drm_gbm.so pointing to the file libnvidia-
+ allocator.so.VERSION to implement a GBM backend driver usable
+ with the GBM loader from the Mesa project version 21.2 and
+ above, as well as the files libnvidia-eg
[Bug 1927205] Re: Chromium menu is blank and freezes application
I have same problem, + it hangs when I click on html items
It looks to be connected with GPU (I have AMD Ryzen 7 4750U CPU with Radeon
graphics).
After chromium hangs, it took about 10 seconds to restart chromium. These log
messages appears in console:
[120832:120832:1217/115511.669028:ERROR:command_buffer_proxy_impl.cc(328)] GPU
state invalid after WaitForGetOffsetInRange.
[120832:120832:1217/115511.676066:ERROR:gpu_process_host.cc(967)] GPU process
exited unexpectedly: exit_code=512
si_init_perfcounters: max_sh_per_se = 2 not supported (inaccurate performance
counters)
[122614:122614:1217/115511.784632:ERROR:sandbox_linux.cc(376)]
InitializeSandbox() called with multiple threads in process gpu-process.
When chromium app starts, this messages are shown:
si_init_perfcounters: max_sh_per_se = 2 not supported (inaccurate performance
counters)
[120938:120938:1217/114538.723373:ERROR:sandbox_linux.cc(376)]
InitializeSandbox() called with multiple threads in process gpu-process.
[120832:120925:1217/114541.025791:ERROR:chrome_browser_main_extra_parts_metrics.cc(226)]
crbug.com/1216328: Checking Bluetooth availability started. Please report if
there is no report that this ends.
[120832:120925:1217/114541.025815:ERROR:chrome_browser_main_extra_parts_metrics.cc(229)]
crbug.com/1216328: Checking Bluetooth availability ended.
[120832:120925:1217/114541.025819:ERROR:chrome_browser_main_extra_parts_metrics.cc(232)]
crbug.com/1216328: Checking default browser status started. Please report if
there is no report that this ends.
[120832:120965:1217/114541.072325:ERROR:udev_watcher.cc(98)] Failed to begin
udev enumeration.
[120832:120925:1217/114541.155048:ERROR:chrome_browser_main_extra_parts_metrics.cc(236)]
crbug.com/1216328: Checking default browser status ended.
Warning: disabling flag --expose_wasm due to conflicting flags
Kernel: Linux 5.11.0-41-generic #45~20.04.1-Ubuntu SMP Wed Nov 10 10:20:10 UTC
2021 x86_64 x86_64 x86_64 GNU/Linux
Not installed AMD PRO drivers
Version:
Chromium96.0.4664.110 (Official Build) snap (64-bit)
Revision
d5ef0e8214bc14c9b5bbf69a1515e431394c62a6-refs/branch-heads/4664@{#1283}
OS Linux
JavaScript V8 9.6.180.21
User Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like
Gecko) Chrome/96.0.4664.110 Safari/537.36
Command Line/snap/chromium/1854/usr/lib/chromium-browser/chrome
--password-store --flag-switches-begin --flag-switches-end
--origin-trial-disabled-features=CaptureHandle
Executable Path /snap/chromium/1854/usr/lib/chromium-browser/chrome
Profile Path/home/michal/snap/chromium/common/chromium/Default
Variations b56a9ab2-5558097f
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927205
Title:
Chromium menu is blank and freezes application
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1927205/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868244] Re: python3.8 crashed with signal 5 in g_object_new_with_properties()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python3.8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868244 Title: python3.8 crashed with signal 5 in g_object_new_with_properties() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.8/+bug/1868244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955081] Re: Right-click on terminal causing no demand to enter user's password
Thank you. Moreover, I confirm the presence of the vulnerability on Debian GNU/Linux 10, Gnome 3.30.2, Acer AMD A9-9420 radeon r5. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955081 Title: Right-click on terminal causing no demand to enter user's password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1955081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955129] [NEW] trace-cmd report buffer overflow detected
Public bug reported: [IMPACT] When running trace-cmd report on Bionic it crashes with *** buffer overflow detected ***: trace-cmd terminated Aborted (core dumped) [TEST CASE] Prepare a simple script to trace e.g. : #!/usr/bin/python import socket s = socket.socket(socket.AF_INET, socket.SOCK_STREAM) s.close() then $ sudo trace-cmd record -a -p function_graph -g __fput -g sock_close -g tcp_close python2 ./close.py $ sudo trace-cmd report The latter will fail with buffer overflow detected [WHERE THINGS COULD GO WRONG] The fixing commit changes the size of a buffer from 20 to 24 in arg_eval() function to avoid buffer overflow. Any potential regression would occur in that function. [OTHER] Only Bionic is affected, it is fixed in newer releases. Fix upstream commit 1375d98d8017e371776adbef10122a57ce2100e5 ** Affects: trace-cmd (Ubuntu) Importance: Medium Assignee: Ioanna Alifieraki (joalif) Status: In Progress ** Affects: trace-cmd (Ubuntu Bionic) Importance: Medium Assignee: Ioanna Alifieraki (joalif) Status: In Progress ** Changed in: trace-cmd (Ubuntu) Status: New => In Progress ** Changed in: trace-cmd (Ubuntu) Importance: Undecided => Medium ** Changed in: trace-cmd (Ubuntu) Assignee: (unassigned) => Ioanna Alifieraki (joalif) ** Also affects: trace-cmd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: trace-cmd (Ubuntu Bionic) Status: New => In Progress ** Changed in: trace-cmd (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: trace-cmd (Ubuntu Bionic) Assignee: (unassigned) => Ioanna Alifieraki (joalif) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955129 Title: trace-cmd report buffer overflow detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trace-cmd/+bug/1955129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955001] Re: File reading speed is slow
Sorry but your reply is confusing, nautilus is the graphical file manager, similar to explorer on Windows, https://en.wikipedia.org/wiki/GNOME_Files . Ssh prompt don't use nautilus... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955001 Title: File reading speed is slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1955001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954818] Re: Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish, and 470 in Focal
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-495 into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-495/495.46-0ubuntu0.21.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. 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: nvidia-graphics-drivers-495 (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags added: verification-needed-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954818 Title: Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish, and 470 in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1954818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953671] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548289/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953671] Re: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion
apport information ** Description changed: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon-Tech/Anyone- have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (26 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) Package: linux-image-generic 5.13.0.21.32 [origin: unknown] PackageArchitecture: arm64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Tags: jammy uec-images third-party-packages Uname: Linux 5.14.21-051421-generic aarch64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2021-11-15 (23 days ago) UserGroups: N/A _MarkForUpload: True + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw+ 1 root audio 116, 1 Dec 17 11:38 seq + crw-rw+ 1 root audio 116, 33 Dec 17 11:38 timer + AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-21-generic. + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu74 + Architecture: arm64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/seq:myitcv 1543 F pipewire + CasperMD5CheckResult: pass + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2021-11-12 (34 days ago) + InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + MachineType: VMware, Inc. VBSA + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + LANG=C.UTF-8 + SHELL=/bin/bash + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=7378d8ea-883e-47b8-b5ab-a92790860f9c ro + ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-5.13.0-21-generic N/A + linux-backports-modules-5.13.0-21-generic N/A + linux-firmware 1.202 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: jammy uec-images + Uname: Linux 5.13.0-21-generic aarch64 + UpgradeStatus: Upgraded to jammy on 2021-11-15 (31 days ago) + UserGroups: N/A + _MarkForUpload: True + acpidump: + + dmi.bios.date: 12/31/2020 + dmi.bios.release: 0.0 + dmi.bios.vendor: VMware + dmi.bios.version: VEFI + dmi.board.name: VBSA + dmi.board.vendor: VMware + dmi.board.version: 1 + dmi.chassis.type: 1 + dmi.chassis.vendor: VMware + dmi.chassis.version: VBSA + dmi.ec.firmware.release: 0.0 + dmi.modalias: dmi:bvnVMware:bvrVEFI:bd12/31/2020:br0.0:efr0.0:svnVMware,Inc.:pnVBSA:pvr1:rvnVMware:rnVBSA:rvr1:cvnVMware:ct1:cvrVBSA:sku0001: + dmi.product.family: VMware + dmi.product.name: VBSA + dmi.product.sku: 0001 + dmi.product.version: 1 + dmi.sys.vendor: VMware, Inc. ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548287/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+sourc
[Bug 1953671] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548288/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953671] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548291/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953671] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548292/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953671] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548293/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953671] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548290/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953671] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548294/+files/PaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953671] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548300/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953671] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548295/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953671] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548296/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953671] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548297/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953671] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548299/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953671] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548298/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953671] Re: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion
I've just updated with the logs from: apport-collect 1953671 Please note: these are gathered when using the 5.13.0-21-generic kernel. However, VMWare Fusion requires at least 5.14, so I have been running v5.14.21-051421-generic day-to-day, and only switched to 5.13.0-21 in order to report these diagnostics. Both v5.15.8 and v5.16-rc5 both hang, so v5.14.21-051421 remains the only kernel I can use at the moment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954818] Re: Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish, and 470 in Focal
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-495 into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-495/495.46-0ubuntu0.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: nvidia-graphics-drivers-495 (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Tags added: verification-needed-hirsute ** Changed in: nvidia-graphics-drivers-495 (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/1954818 Title: Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish, and 470 in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1954818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954818] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-495 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-495/495.46-0ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-495 (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954818 Title: Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish, and 470 in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1954818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954818] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-495 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-495/495.46-0ubuntu0.18.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- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954818 Title: Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish, and 470 in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1954818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955116] Re: mk-sbuild create error due to bullseye security move
** Changed in: ubuntu-dev-tools (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955116 Title: mk-sbuild create error due to bullseye security move To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1955116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950321] Re: [MIR] glusterfs
Review for Package: src:glusterfs [Summary] This is a big piece of software and might have quite some security implications (embedded sources, root daemon, regex parsing, lintian warnings, openssl3 warnings, ...) but I'll leave this to the security-team to judge on. It is really unfortunate that it does not currently contain any automated testing. Thanks for starting the work on a DEP-8 test already, we absolutely need this! In addition it should be further investigated if the unit-tests can be run at build time or if we can setup similar test as the upstream CI that run during build. Having unit tests + DEP-8 would make me feel much more confortable in ACKing this, but I guess having at least one of them is the bare minimum. MIR team ACK under the constraint to resolve the below listed required TODOs and as much as possible having a look at the recommended TODOs. This does need a security review, so I'll assign ubuntu-security List of specific binary packages to be promoted to main: glusterfs-cli, glusterfs-client, glusterfs-common, glusterfs-server, libgfapi0, libgfchangelog0, libgfrpc0, libgfxdr0, libglusterd0, libglusterfs-dev, libglusterfs0 Specific binary packages built, but NOT to be promoted to main: Required TODOs: - Implement & upload the proposed autopkgtests (+ try to get them into Debian): Thanks for starting the work on this already! https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1954452 - State a plan of how you will stay on top of the embedded sources (security issues, updates, ...) Recommended TODOs: - The package should get a team bug subscriber before being promoted - try to enable the unittests (BUILD_UNITTEST="no" in configure.ac) at buildtime - Work with upstream to resolve the build time warnings - Work with Debian to clean up the lintian warnings & overrides [Duplication] There is no other package in main providing the same functionality. There are some parallels to Ceph, as a scale-out storage solution, but the usecases are quite a bit different (object storage in a full cloud environment vs HA file storage), so I'm not considering this a duplication of functionality. [Dependencies] OK: - no other Dependencies to MIR due to this - checked with check-mir - not listed in seeded-in-ubuntu - none of the (potentially auto-generated) dependencies (Depends and Recommends) that are present after build are not in main - no -dev/-debug/-doc packages that need exclusion - No dependencies in main that are only superficially tested requiring more tests now. Problems: None [Embedded sources and static linking] OK: - no static linking - does not have odd Built-Using entries - not a go package, no extra constraints to consider in that regard Problems: - Some embedded sources present (like xxhash, libexecinfo, ...) in contrib/ [Security] OK: - history of CVEs does not look concerning (there are plenty of CVEs, but the situation seems to have become much better since 2018, only one CVE in 2019 since then) - does not use webkit1,2 - does not use lib*v8 directly - does not process arbitrary web content - does not use centralized online accounts - does not integrate arbitrary javascript into the desktop - does not deal with system authentication (eg, pam), etc) - does not deal with security attestation (secure boot, tpm, signatures) Problems: - does run a daemon as root - does open a port/socket - does some regex parsing in libglusterfs/src/parse-utils.c [Common blockers] OK: - does not FTBFS currently - if special HW does prevent build/autopkgtest is there a test plan, code, log provided? – not needed - if a non-trivial test on this level does not make sense (the lib alone is only doing rather simple things), is the overall solution (app+libs) extensively covered i.e. via end to end autopkgtest ? – not needed - no new python2 dependency - Python package, but using dh_python (some parts of it) - NO Go package Problems: - does NOT have a test suite that runs at build time - does NOT have a non-trivial test suite that runs as autopkgtest: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1954452 [Packaging red flags] OK: - Ubuntu does carry a delta, but it is reasonable and maintenance under control - symbols tracking is in place (using dh_makeshlibs -VUpstream-Version) - d/watch is present and looks ok (if needed, e.g. non-native) - Upstream update history is good - Debian/Ubuntu update history is good - the current release is packaged - promoting this does not seem to cause issues for MOTUs that so far maintained the package - d/rules is rather clean - It is not on the lto-disabled list Problems: - some Lintian warnings (especially the no-symbols-control-file & hardening-no-fortify-functions) [Upstream red flags] OK: - no incautious use of malloc/sprintf (as far as we can check it) - no use of sudo, gksu, pkexec (usage is OK inside tests) - no use of setuid - no important open bugs (crashers, etc) in Debian or Ubuntu => some cra
[Bug 1955131] [NEW] Cash-flow report fails with exception
Public bug reported: I have had a cash-flow report configured and unchanged for several y ears. Lately it is failing. Gnucash 3.8 No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal Report output and specification attached ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnucash 1:3.8b-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Dec 17 12:15:35 2021 InstallationDate: Installed on 2018-02-09 (1407 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnucash UpgradeStatus: Upgraded to focal on 2020-10-09 (434 days ago) ** Affects: gnucash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Report output" https://bugs.launchpad.net/bugs/1955131/+attachment/5548301/+files/WebKitWebProcess_job__1__ng_non-Linux-generated_files-job_346.pdf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955131 Title: Cash-flow report fails with exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1955131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955131] Re: Cash-flow report fails with exception
Added the 2nd attachment as the original form only permitted one attachment. ** Attachment added: "Report spec as saved by gnucash" https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1955131/+attachment/5548305/+files/saved-reports-2.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955131 Title: Cash-flow report fails with exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1955131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939678] Re: Apache2 Balancer Manager not working after dist-upgrade to focal behind a Proxy
Hello Paride,
for a kinde of integrity i did the same with the ubuntu 20.04 Apache.
:~$ apt-get source apache2
:~$ cp apache2-2.4.41/modules/proxy/mod_proxy_balancer.c .
:~$ vim mod_proxy_balancer.c
[...]
/* Ignore parameters if this looks like XSRF */
ref = apr_table_get(r->headers_in, "Referer");
if (apr_table_elts(params)
&& (!ref || !safe_referer(r, ref))) {
ap_log_rerror(APLOG_MARK, APLOG_ERR, 0, r, APLOGNO(10187)
"ignoring params in balancer-manager cross-site access");
apr_table_clear(params);
}
[...]
Delete that part and compile the module only
:~# apxs2 -c -i mod_proxy_balancer.c
:~# systemctl restart apache2
And it looks like for me everything ist working again as expected. But
also the I'am a non Developer hint and mybe this todo so is a really bad
idea.
Thx Horst
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939678
Title:
Apache2 Balancer Manager not working after dist-upgrade to focal
behind a Proxy
To manage notifications about this bug go to:
https://bugs.launchpad.net/apache2/+bug/1939678/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946882] Re: Merge open-isns from Debian unstable for 22.04
This bug was fixed in the package open-isns - 0.101-0ubuntu1 --- open-isns (0.101-0ubuntu1) jammy; urgency=medium * Merge 0.101 from upstream (LP: #1946882), remaining changes - d/open-isns-utils.install: Include isnssetup script in /usr/sbin along with its man documentation * Dropped changes: - d/p/0001-Do-not-ignore-write-return-value.patch: Avoid warn_unused_result error [Fixed in 0.101] - d/p/0002-Fix-different-signedness-integer-expression-comparis.patch: Fix sign error [Fixed in 0.101] - d/p/0003-Fix-broken-server-authentication-initialization.patch: Fix broken server authorization initialization [Fixed in 0.101] - d/p/no-werror.patch: Build without werror enabled [Fixed in 0.101] -- Lena Voytek Wed, 16 Dec 2021 07:15:31 -0700 ** Changed in: open-isns (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/1946882 Title: Merge open-isns from Debian unstable for 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-isns/+bug/1946882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890592] Re: trying to overwrite shared '/etc/java-8-openjdk/security/java.security', which is different from other instances of package openjdk-8-jre-headless:i386 on Ubuntu 20.04
** Tags added: focal jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890592 Title: trying to overwrite shared '/etc/java-8-openjdk/security/java.security', which is different from other instances of package openjdk-8-jre-headless:i386 on Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1890592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946833] Re: Merge bind9 from Debian unstable for 22.04
** Changed in: bind9 (Ubuntu) Milestone: ubuntu-21.12 => ubuntu-22.01 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946833 Title: Merge bind9 from Debian unstable for 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1946833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955129] Re: trace-cmd report buffer overflow detected
Debdiff for Bionic ** Patch added: "lp1955129_bionic.debdiff" https://bugs.launchpad.net/ubuntu/+source/trace-cmd/+bug/1955129/+attachment/5548306/+files/lp1955129_bionic.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955129 Title: trace-cmd report buffer overflow detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trace-cmd/+bug/1955129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955129] Re: trace-cmd report buffer overflow detected
Debdiff for Bionic ** Patch added: "lp1955129_bionic.debdiff" https://bugs.launchpad.net/ubuntu/+source/trace-cmd/+bug/1955129/+attachment/5548307/+files/lp1955129_bionic.debdiff ** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955129 Title: trace-cmd report buffer overflow detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trace-cmd/+bug/1955129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954452] Re: Add dep8 tests to glusterfs
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/glusterfs/+git/glusterfs/+merge/413053 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954452 Title: Add dep8 tests to glusterfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1954452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954452] Re: Add dep8 tests to glusterfs
** Changed in: glusterfs (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954452 Title: Add dep8 tests to glusterfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1954452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929926] Comment bridged from LTC Bugzilla
--- Comment From i...@de.ibm.com 2021-12-17 08:24 EDT--- Hi! Sorry about the delay. Both 20.04 and 21.04 packages work fine. Here is the sequence I used: host# docker run -it ubuntu:20.04 bash docker# apt-get update docker# apt-get install binutils linux-image-5.11 qemu-system-s390x wget docker# cd /tmp docker# lz4 -d : docker# wget http://launchpadlibrarian.net/571593767/qemu-system-s390x_4.2-3ubuntu6.19_s390x.deb docker# dpkg -i --force-all qemu-system-s390x_4.2-3ubuntu6.19_s390x.deb docker# qemu-system-s390x -kernel /boot/vmlinuz-5.11.0-43-generic -initrd /boot/initrd.img-5.11.0-43-generic -m 1024 -nographic vm# mount -t debugfs foo /sys/kernel/debug vm# echo "r:read_plt /bin/sh:0x7080" >/sys/kernel/debug/tracing/uprobe_events vm# echo 1 >/sys/kernel/debug/tracing/events/uprobes/read_plt/enable Fails without the fix, works with it. Same on 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/1929926 Title: [UBUNTU 21.10] qemu: target/s390x: Fix translation exception on illegal instruction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931790] Re: Unable to mount btrfs RAID 1 filesystem after reboot - Error - device total_bytes should be at most X but found Y
Hi, I have the same problem, raid1 partition does not mount after upgrade from 5.8 to 5.11 kernel. (Ubuntu 20.04LTS > 21.04) Mount is ok with Kernel up to 5.10. (SystemRescue-USB) BTRFS error (device sdb): device total_bytes should be at most 4000780910592 but found 4000785960960 Why the difference of 5050368 bytes (9864 sectors) ? Łukasz had a difference of 568942592 bytes (216 sectors) sdb is the only Harddrive with both. 512 bytes Sector size (logical/physical)! sda: root/boot SDD sdb,sdc,sdd,sde: RAID1 btrfspool sdf: clean 16TB btrfs HDD Disk /dev/sda: 232.89 GiB, 250059350016 bytes, 488397168 sectors Disk model: Samsung SSD 850 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Device Start End Sectors Size Type /dev/sda1 2048 10239 8192 4M BIOS boot /dev/sda210240 1034239 1024000 500M EFI System /dev/sda3 1034240 488397134 487362895 232.4G Linux filesystem Disk /dev/sdb: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: HGST HUS726T4TAL Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Device StartEndSectors Size Type /dev/sdb1 10240 7814035455 7814025216 3.6T Linux filesystem /dev/sdb2 2048 10239 81924M BIOS boot Disk /dev/sdc: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors Disk model: WDC WD8003FRYZ-0 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Device Start End Sectors Size Type /dev/sdc1 10240 15628053134 15628042895 7.3T Linux filesystem /dev/sdc2 2048 1023981924M BIOS boot Disk /dev/sdd: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: WDC WD40EFRX-68N Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Device StartEndSectors Size Type /dev/sdd1 10240 7814035455 7814025216 3.6T Linux filesystem /dev/sdd2 2048 10239 81924M BIOS boot Disk /dev/sde: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: WDC WD4003FFBX-6 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Device StartEndSectors Size Type /dev/sde1 10240 7814035455 7814025216 3.6T Linux filesystem /dev/sde2 2048 10239 81924M BIOS boot Disk /dev/sdf: 14.55 TiB, 16000900661248 bytes, 31251759104 sectors Disk model: TOSHIBA MG08ACA1 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Device Start End Sectors Size Type /dev/sdf1 2048 31251759070 31251757023 14.6T Linux filesystem Comparision (extract) between sdb1 and sdd1, sde1: [root@sysrescue ~]# btrfs inspect-internal dump-super /dev/sdb1 /dev/sdd1 /dev/sde1 superblock: bytenr=65536, device=/dev/sdb1 - label btrfspool generation 1003437 total_bytes 20003910791168 bytes_used 8994780921856 sectorsize 4096 dev_item.total_bytes4000780910592 dev_item.bytes_used 3532610600960 dev_item.io_align 4096 dev_item.io_width 4096 dev_item.sector_size4096 superblock: bytenr=65536, device=/dev/sdd1 - label btrfspool generation 1003437 total_bytes 20003910791168 bytes_used 8994780921856 sectorsize 4096 dev_item.total_bytes4000785960960 dev_item.bytes_used 3532610600960 dev_item.io_align 4096 dev_item.io_width 4096 dev_item.sector_size4096 superblock: bytenr=65536, device=/dev/sde1 - label btrfspool generation 1003437 total_bytes 20003910791168 bytes_used 8994780921856 sectorsize 4096 dev_item.total_bytes4000785960960 dev_item.bytes_used 3532644155392 dev_item.io_align 4096 dev_item.io_width 4096 dev_item.sector_size4096 To make it short, I sent a Snapshot to the new big drive (sdf1), made it writeable and used it as new mountpoint in my /etc/fstab mount /dev/sdb1 /source btrfs sub snapshot -r /source /@snap btrfs send /source/@snap | btrfs receive /target btrfs property set -ts /target/@snap ro false mv /target/@snap /target/@ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed t
[Bug 1955009] Re: Freeradius 3.0.21+dfsg-3build1 fails test of moonshot-gss-eap
** Changed in: freeradius (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: moonshot-gss-eap (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: moonshot-gss-eap (Ubuntu) Status: New => Triaged ** Changed in: freeradius (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955009 Title: Freeradius 3.0.21+dfsg-3build1 fails test of moonshot-gss-eap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1955009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930446] Re: Wallaby ceilometer.compute.discovery fails to get domain metadata
** Also affects: ceilometer (Ubuntu) Importance: Undecided Status: New ** Also affects: ceilometer (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: ceilometer (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: ceilometer (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: ceilometer (Ubuntu Hirsute) Status: New => Confirmed ** Changed in: ceilometer (Ubuntu Hirsute) Status: Confirmed => Triaged ** Changed in: ceilometer (Ubuntu Impish) Status: New => Triaged ** Changed in: ceilometer (Ubuntu Jammy) Status: New => Triaged ** Changed in: ceilometer (Ubuntu Impish) Importance: Undecided => High ** Changed in: ceilometer (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: ceilometer (Ubuntu Jammy) 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/1930446 Title: Wallaby ceilometer.compute.discovery fails to get domain metadata To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1930446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929926] Re: [UBUNTU 21.10] qemu: target/s390x: Fix translation exception on illegal instruction
Thank you, Ilya. I've adjusted the tags accordingly ... ** Tags removed: verification-needed verification-needed-focal verification-needed-hirsute ** Tags added: verification-done verification-done-focal verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929926 Title: [UBUNTU 21.10] qemu: target/s390x: Fix translation exception on illegal instruction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951066] Re: [MIR] dh-elpa
** Changed in: dh-elpa (Debian) 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/1951066 Title: [MIR] dh-elpa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/1951066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851250] Re: [snap] chromium-browser snap cannot upload files outside ~
Hi Olivier, let me take some time to investigate what are the changes to the next major version, because if we are lucky and they are small and safe, we could really think about a SRU. At least for 20.04, which is going to be supported for quite a few years from now. Also, let's keep in mind that Firefox and other apps will also be affected by this (version 3 of the XDG spec add the "directory mode" to the file chooser, which is likely useful to many applications). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851250 Title: [snap] chromium-browser snap cannot upload files outside ~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947601] Re: Cannot start docker container on ubuntu 21.10 server for raspberry pi
Hey, Its not possible install linux-modules-extra-raspi in chroot, because it activates flash-kernel which fails. I also tried to bypass flash-kernel by moving /sbin/flash-kernel aside before installing, but that then the issue does not get fixed. This means that a number of distros I maintain can't have docker running correctly. Related: https://github.com/guysoft/CustomPiOS/issues/149 ** Bug watch added: github.com/guysoft/CustomPiOS/issues #149 https://github.com/guysoft/CustomPiOS/issues/149 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947601 Title: Cannot start docker container on ubuntu 21.10 server for raspberry pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1947601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955134] [NEW] test_markdown fails rendering with pygments > 2.10
Public bug reported: Upstream is aware of the problem (tho, the proposed fix does not resolve the issue quite yet): https://github.com/encode/django-rest-framework/issues/8160 === FAILURES === __ TestViewNamesAndDescriptions.test_markdown __ self = @pytest.mark.skipif(not apply_markdown, reason="Markdown is not installed") def test_markdown(self): """ Ensure markdown to HTML works as expected. """ # Markdown 3.3 is only supported on Python 3.6 and higher if sys.version_info >= (3, 6): > assert apply_markdown(DESCRIPTION) == MARKDOWN_BASE % > MARKDOWN_gte_33 E AssertionError: assert '' E Skipping 445 identical leading characters in diff, use -v to show E - an class="nt">"beta: "this is a string"}] E + an class="s2">"beta: "this is a string"https://docs.pytest.org/en/stable/warnings.html === short test summary info FAILED tests/test_description.py::TestViewNamesAndDescriptions::test_markdown === 1 failed, 1275 passed, 127 skipped, 2 warnings in 15.83s === ** Affects: djangorestframework (Ubuntu) Importance: Undecided Status: New ** Affects: pygments (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Also affects: pygments (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/1955134 Title: test_markdown fails rendering with pygments > 2.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/djangorestframework/+bug/1955134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955009] Re: Freeradius 3.0.21+dfsg-3build1 fails test of moonshot-gss-eap
I would suggest trying 3.0.25. If that works, don't even bother trying to debug this. OpenSSL has minor behavior differences across a major version change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955009 Title: Freeradius 3.0.21+dfsg-3build1 fails test of moonshot-gss-eap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1955009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955106] Re: Facing issues in new GST Registration?
** Package changed: gnome-disk-utility (Ubuntu) => null-and-void ** Changed in: null-and-void Status: New => Invalid ** Information type changed from Public to Private Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955106 Title: Facing issues in new GST Registration? To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1955106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917037] Re: Frozen screen (NVidia GM107 card with large 3840 × 2160 screen)
I can confirm that this freezing issue disappeared after changing the motherboard – as well as another annoying issue where the screen would suddenly start flickering, on/off every second or so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917037 Title: Frozen screen (NVidia GM107 card with large 3840 × 2160 screen) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1917037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955135] [NEW] multiple issues with /etc/X11/Xsession.d/ - "has_option: command not found"
Public bug reported: Steps to reproduce: 1. Boot 20211217 Ubuntu MATE daily ISO 2. Open ~/.xsession-errors Expected results: * no errors and warnings Actual results: * there are two errors about xorg: /etc/X11/Xsession.d/30x11-common_xresources: line 16: has_option: command not found /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: x11-common 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.465 CompositorRunning: None CurrentDesktop: MATE Date: Fri Dec 17 14:22:15 2021 Dependencies: lsb-base 11.1.0ubuntu3 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF108M [GeForce GT 425M] [10de:0df0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation GF108M [GeForce GT 425M] [104d:907a] LiveMediaBuild: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211217) MachineType: Sony Corporation VPCF13Z1R PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2010 dmi.bios.release: 1.90 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0190Y9 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 1.90 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0190Y9:bd10/20/2010:br1.90:efr1.90:svnSonyCorporation:pnVPCF13Z1R:pvrC606GZYK:skuN/A:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCF13Z1R dmi.product.sku: N/A dmi.product.version: C606GZYK dmi.sys.vendor: Sony Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-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-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy reproducible single-occurrence ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955135 Title: multiple issues with /etc/X11/Xsession.d/ - "has_option: command not found" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1955135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955009] Re: Freeradius 3.0.21+dfsg-3build1 fails test of moonshot-gss-eap
Thanks Alan, I'll try that -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955009 Title: Freeradius 3.0.21+dfsg-3build1 fails test of moonshot-gss-eap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1955009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955136] [NEW] /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command not found
Public bug reported: teps to reproduce: 1. Boot 20211217 Ubuntu MATE daily ISO 2. Open ~/.xsession-errors Expected results: * no errors and warnings Actual results: * there are two errors about dbus: /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dbus-x11 1.12.20-2ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: MATE Date: Fri Dec 17 14:28:01 2021 LiveMediaBuild: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211217) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955136 Title: /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1955136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955138] [NEW] External monitor stops showing image for a few seconds
Public bug reported: I use Dell Dock Station - D6000S and noticed in the latest two kernels an instability on my external monitors. I use two external monitors and they randomly stops showing the images for a couple of seconds. It's similar as if the usb-C connection to the docker got interrupted and then connected again. Notebook display doesn't have this issue. Please verify the root cause. Thanks, ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Fri Dec 17 11:25:54 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: evdi, 1.9.1, 5.11.0-41-generic, x86_64: installed evdi, 1.9.1, 5.11.0-43-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-41-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:09a0] InstallationDate: Installed on 2021-04-07 (253 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Latitude 5410 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2021 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 08NM43 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd03/11/2021:br1.5:svnDellInc.:pnLatitude5410:pvr:sku09A0:rvnDellInc.:rn08NM43:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5410 dmi.product.sku: 09A0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955138 Title: External monitor stops showing image for a few seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1955138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955137] [NEW] [SRU] 2.54
Public bug reported: Placeholder ** Affects: snapd (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/1955137 Title: [SRU] 2.54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1955137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776030] Re: Backup fails with "an unknown error"
As much as I hate to be a "me too" message the same 'failed with unknown error' occurred with last night's automated backup, as well as the manual retests. Running Ubuntu 18.04. Nothing was changed here, although I did create a script on two Raspberry Pi's to monitor the status of accessing the remote NAS -- RPi with Motion, storage to the NAS; this Ubuntu system with storage to the same NAS, different directory. (No issues with the RPi writing.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776030 Title: Backup fails with "an unknown error" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1776030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955153] [NEW] nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
Public bug reported: module nvidia_uvm is loaded. after few days the graphic is messi, the windows are clear, but the desktop is unmanageable. Every thing is fixed with a reboot. Graphics: VGA compatible controller [0300]: NVIDIA Corporation GF108 [GeForce GT 730] [10de:0f02] (rev a1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-43-generic Date: Fri Dec 17 06:41:12 2021 InstallationDate: Installed on 2021-05-22 (209 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (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/1955153 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1955153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955155] [NEW] Ubuntu shuts down now from locked screen after some amount of time despite all automatic shutdown disabled
Public bug reported: I have no idea when this started, but my Desktop goes offline (shuts down) when left in the lock screen or when left on the log in screen with no activity. I used to have things set up to auto-reboot on power failure and no shut down occurred. This was working as of last year roughly and I do not have any event to associate the change in behaviour other than all the updates that happened over that time. On 20.04. This is a pretty disastrous bug as you can imagine as a) nobody has any information on this, looking at logs (last -x) I saw no shutdown commands issued. b) configs are a mess documentation wise with words like "sleep", "suspend" thrown around and nobody really knows what they mean. Asking about "sleep" gets a lots of responses about "why are you asking about /bin/sleep". It is a kind of state where you end up in an asylum because nobody wants to debug this, it's probably a config change done by some update, and it's not very interesting in terms of problems to solve. Except it is absolutely disastrous since now my machine is offline and I am away (I tried N rounds of debugging and testing before I left) but was *unable* to block automatic shutdown AND not leave the computer logged in and totally vulnerable. Probably what should happen is that instead of some massive and fruitless debugging project, a feature should be enabled that is a "block ALL automatic shutdowns no matter what reason never ever allow anything to shut me down that isn't a human typing at a keyboard. Reboots are fine." You might call this server mode. I have seen people saying to simply set /bin/shutdown to unexecutable ... I might try that when back but it sounds like it might have potentially bad side effects. ** Affects: 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/1955155 Title: Ubuntu shuts down now from locked screen after some amount of time despite all automatic shutdown disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1955155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890569] Re: javaldx: Could not find a Java Runtime Environment! Please ensure that a JVM and the package libreoffice-java-common is installed.
** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890569 Title: javaldx: Could not find a Java Runtime Environment! Please ensure that a JVM and the package libreoffice-java-common is installed. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1890569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936966] Re: Libreoffice 7.1 from PPA uses wrong desktop/panel/window icons for Template wizards
** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936966 Title: Libreoffice 7.1 from PPA uses wrong desktop/panel/window icons for Template wizards To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1936966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955157] [NEW] Ubuntu installer overwrote the wrong hard drive bootloader
Public bug reported: I had ubuntu installed on my main hard drive, sda, and wanted to make an external hard drive have its own ubuntu installation that was bootable. I plugged it in, and used the live USB to install to it. (20.04.4 LTS ubuntu desktop) In ubiquity 20.04.15.17, on the partition manager, I selected something else, and made the / partition on the external hard drive sdb (different make and capacity so it was definitely the right hard drive). I also added a swap partition to it too. I changed the 'device for boot loader installation' to sdb also and finished installation. After installing, the external hard drive was not bootable. I unplugged it, and tried to boot to my normal ubuntu desktop, which was also now broken. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: ubiquity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955157 Title: Ubuntu installer overwrote the wrong hard drive bootloader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1955157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710385] Re: missing freerdp2-x11
The package freerdp2-x11 is available in bionic and newer Ubuntu series but in universe ** Changed in: freerdp2 (Ubuntu) Importance: Undecided => High ** Changed in: freerdp2 (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/1710385 Title: missing freerdp2-x11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1710385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955161] [NEW] Jammy update: v5.15.9 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.9 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955161 Title: Jammy update: v5.15.9 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949643] Re: iptables-persistent unconditionally drops existing iptables rules
Hello Mauricio, or anyone else affected, Accepted iptables-persistent into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/iptables- persistent/1.0.15ubuntu0.21.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. 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: iptables-persistent (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-impish ** Changed in: iptables-persistent (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Tags added: 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/1949643 Title: iptables-persistent unconditionally drops existing iptables rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables-persistent/+bug/1949643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949643] Please test proposed package
Hello Mauricio, or anyone else affected, Accepted iptables-persistent into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/iptables- persistent/1.0.14ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: iptables-persistent (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949643 Title: iptables-persistent unconditionally drops existing iptables rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables-persistent/+bug/1949643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955163] [NEW] passwd command somehow screwed up the password, lost access to the machine
Public bug reported: I had a fresh install of Ubuntu 20.4 Desktop on a server (yes, desktop on a server). The only extra package installed was ssh. It was a fresh install of 20.4 desktop as downloaded from the official website, plus the ssh package (and any dependency) installed via apt. The user created during installation was x with password "x" (not the real credentials, I'm using fake ones here, but the username was the same as the password). I logged in via SSH with user x: > ssh x@123.123.123.123 (obviously this wasn't the real IP) was prompted for the password, entered it, and I was in. Then I did: > sudo passwd x (yes I could probably just have done "passwd" without sudoing and without specifying the user, so I would have changed my own password. But that should be the same. I'm sudoing to change the password of an arbitrary user that happens to be myself. No reason why that shouldn't work). So I was prompted for the current password (because sudo), which I entered, and then I was prompted for a new password that I had to repeat twice and so I did. Let's say the new password was 12345678. Actually (this shouldn't be relevant), I copied the password from somewhere else and pasted it both times. I got a message saying the password was changed successfully. Then I logged out with: > exit Now I can't ssh to it anymore. When I do: > ssh x@123.123.123.123 and enter the new password, it says "Permission denied, please try again." I tried the old password too, with no success. I also tried ssh root@123.123.123.123, both with the old and new password, but unsurprisingly that doesn't work either (I don't think the root user actually has a password at all, right? and if it does, there's no reason it should be any of those two). I also tried entering nothing when prompted for the password (just the Enter key, i.e. an empty password, thinking maybe the copy-paste was what failed for whatever reason), but no. And I also tried both pasting the password and manually typing it. I'm not asking for help, I'm reporting a bug because whatever happened here, it shouldn't have happened and it caused me to lose access to the machine forever. Luckily it was a freshly installed system so it's no big deal, but in principle this is a disaster. There's no way I can have mis-typed the password at any stage, because I had it in a text file before I started and I copied and pasted it from there. If somehow some character got screwed up by pasting, and what was saved is not the string that I copied, that would be a bug. My local machine is linux too and I use a konsole terminal to ssh to the remote machine. To paste copied text I use Ctrl+Shift+V which generally work (I use it all the time to paste into the terminal both locally and when connected via ssh to other remote machines). ** Affects: 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/1955163 Title: passwd command somehow screwed up the password, lost access to the machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1955163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949643] Please test proposed package
Hello Mauricio, or anyone else affected, Accepted iptables-persistent into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/iptables- persistent/1.0.4+nmu2ubuntu1.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- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949643 Title: iptables-persistent unconditionally drops existing iptables rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables-persistent/+bug/1949643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949643] Please test proposed package
Hello Mauricio, or anyone else affected, Accepted iptables-persistent into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/iptables- persistent/1.0.15ubuntu0.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: iptables-persistent (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949643 Title: iptables-persistent unconditionally drops existing iptables rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables-persistent/+bug/1949643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931001] Re: Soft lockup due to interrupt storm from smbus
** Summary changed: - kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! + Soft lockup due to interrupt storm from smbus -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931001 Title: Soft lockup due to interrupt storm from smbus To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1931001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954683] Re: grub is missing secure boot support for compressed kernels (our arm64 kernels)
** Summary changed: - grub is missing secure boot support for compressed kernels + grub is missing secure boot support for compressed kernels (our arm64 kernels) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954683 Title: grub is missing secure boot support for compressed kernels (our arm64 kernels) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1954683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955136] Re: /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command not found
Also happens on Xubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955136 Title: /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1955136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955136] Re: /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command not found
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1955136 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955136 Title: /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1955136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955136] Re: /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command not found
.xsession-errors from Xubuntu ** Attachment added: ".xsession-errors from Xubuntu" https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1955136/+attachment/5548386/+files/.xsession-errors -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955136 Title: /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1955136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955135] Re: multiple issues with /etc/X11/Xsession.d/ - "has_option: command not found"
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1955135 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955135 Title: multiple issues with /etc/X11/Xsession.d/ - "has_option: command not found" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1955135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955135] Re: multiple issues with /etc/X11/Xsession.d/ - "has_option: command not found"
.xsession-errors from Xubuntu ** Attachment added: ".xsession-errors from Xubuntu" https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1955135/+attachment/5548385/+files/.xsession-errors -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955135 Title: multiple issues with /etc/X11/Xsession.d/ - "has_option: command not found" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1955135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
