[Bug 1973308] Re: package mysql-server-8.0 8.0.29-0ubuntu0.22.04.2 failed to install/upgrade: el subproceso instalado paquete mysql-server-8.0 script post-installation devolvió el código de salida de
Hello, From your logs, I see you installed mariadb then removed mysql then tried to reinstall it again. Unfortunately mariadb and mysql are incompatible with each other. If you would like to install mysql make sure to remove and purge mariadb from your system. I'm marking this bug as invalid as it is a configuration error. If you feel this is incorrect please let us know. Thanks! ** Changed in: mysql-8.0 (Ubuntu) Status: New => Invalid ** Summary changed: - package mysql-server-8.0 8.0.29-0ubuntu0.22.04.2 failed to install/upgrade: el subproceso instalado paquete mysql-server-8.0 script post-installation devolvió el código de salida de error 1 + mariadb install causes mysql install to fail with ibdata1 locked -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973308 Title: mariadb install causes mysql install to fail with ibdata1 locked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1973308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1973379] Re: "additional drivers" says we are using nvidia drivers but its not true
Thanks, but I am not sure if that can still be helpful for the analysis, because in the meantime I got the nvidia drivers running properly. What finally got me there was these commands: ubuntu-drivers devices ubuntu-drivers autoinstall apt install nvidia-dkms-510 update-initramfs -k all -u and a reboot. it could be that the first two are not needed when properly selecting the nvidia drivers in the GUI drivers tool, but it appears to me the dkms part is missing in the GUI tool just as in the CLI version, and without that the drivers are not running for me. here's the debug output: $ ubuntu-drivers debug === log messages from detection === DEBUG:root:Skipping check for rtl8812au-dkms since it does not depend on video abi DEBUG:root:Skipping check for open-vm-tools-desktop since it does not depend on video abi DEBUG:root:Skipping check for rtl8821ce-dkms since it does not depend on video abi DEBUG:root:Skipping check for bcmwl-kernel-source since it does not depend on video abi DEBUG:root:Skipping check for oem-qemu-meta since it does not depend on video abi DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:Skipping check for rtl8812au-dkms since it does not depend on video abi DEBUG:root:Skipping check for open-vm-tools-desktop since it does not depend on video abi DEBUG:root:Skipping check for rtl8821ce-dkms since it does not depend on video abi DEBUG:root:Skipping check for bcmwl-kernel-source since it does not depend on video abi DEBUG:root:Skipping check for oem-qemu-meta since it does not depend on video abi DEBUG:root:Loading custom detection plugin /usr/share/ubuntu-drivers-common/detect/arm-gles.py DEBUG:root:plugin /usr/share/ubuntu-drivers-common/detect/arm-gles.py return value: None DEBUG:root:Loading custom detection plugin /usr/share/ubuntu-drivers-common/detect/sl-modem.py DEBUG:root:plugin /usr/share/ubuntu-drivers-common/detect/sl-modem.py return value: None === modaliases in the system === acpi:PNP0C14: wmi:86CCFD48-205E-4A77-9C48-2021CBEDE341 acpi:PNP0C0D: platform:thinkpad_hwmon platform:eisa
[Bug 1973608] Re: udev TAG-="uaccess" does not work on ubuntu 22.04
This was a deliberate change in systemd [1] to address the kernel's bind/unbind uevent issue [2]. In short, it is an intentional change in udev's behavior, and unfortunately breaks the assumptions that your custom udev rules rely on. [1] https://github.com/systemd/systemd/commit/e77b146f825ef1bb63c297cc713962b94422d2c6 [2] https://lwn.net/Articles/837033/ ** Changed in: systemd (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/1973608 Title: udev TAG-="uaccess" does not work on ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1973608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973623] Re: VirtualBox GUI is broken on multi-display systems
** Description changed: The GUI is totally broken on a multi-display setup, when one display is - set into portrait mode and scaling is enabled. + set into portrait mode and scaling is enabled. This also happens when + both displays are aligned at the top. + + Display connected via (for resolution & position see xrandr.txt): + - HDMI-0: Fractional Scaling: 125%, Orientation: Portrait Right + - DP-4: Fractional Scaling: 200%, Orientation: Landscape Workaround: 'env QT_AUTO_SCREEN_SCALE_FACTOR=0 virtualbox' It works without problems with the workaround. Description: Ubuntu 20.04.4 LTS Release: 20.04 Package: virtualbox-qt=6.1.32-dfsg-1~ubuntu1.20.04.1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: virtualbox 6.1.32-dfsg-1~ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon May 16 17:13:32 2022 InstallationDate: Installed on 2021-04-14 (396 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: The GUI is totally broken on a multi-display setup, when one display is - set into portrait mode and scaling is enabled. This also happens when - both displays are aligned at the top. + set into portrait mode and scaling is enabled. Display connected via (for resolution & position see xrandr.txt): - HDMI-0: Fractional Scaling: 125%, Orientation: Portrait Right - DP-4: Fractional Scaling: 200%, Orientation: Landscape Workaround: 'env QT_AUTO_SCREEN_SCALE_FACTOR=0 virtualbox' It works without problems with the workaround. Description: Ubuntu 20.04.4 LTS Release: 20.04 Package: virtualbox-qt=6.1.32-dfsg-1~ubuntu1.20.04.1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: virtualbox 6.1.32-dfsg-1~ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon May 16 17:13:32 2022 InstallationDate: Installed on 2021-04-14 (396 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: virtualbox 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/1973623 Title: VirtualBox GUI is broken on multi-display systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1973623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973623] [NEW] VirtualBox GUI is broken on multi-display systems
Public bug reported: The GUI is totally broken on a multi-display setup, when one display is set into portrait mode and scaling is enabled. Workaround: 'env QT_AUTO_SCREEN_SCALE_FACTOR=0 virtualbox' It works without problems with the workaround. Description:Ubuntu 20.04.4 LTS Release:20.04 Package: virtualbox-qt=6.1.32-dfsg-1~ubuntu1.20.04.1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: virtualbox 6.1.32-dfsg-1~ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon May 16 17:13:32 2022 InstallationDate: Installed on 2021-04-14 (396 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshots of VirtualBox run with/without workaround." https://bugs.launchpad.net/bugs/1973623/+attachment/5590100/+files/Screenshot%20from%202022-05-16%2017-4.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973623 Title: VirtualBox GUI is broken on multi-display systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1973623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973623] Re: VirtualBox GUI is broken on multi-display systems
** Attachment added: "xrandr.txt" https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1973623/+attachment/5590107/+files/xrandr.txt ** Description changed: The GUI is totally broken on a multi-display setup, when one display is - set into portrait mode and scaling is enabled. This also happens when - both displays are aligned at the top. + set into portrait mode and scaling is enabled. Workaround: 'env QT_AUTO_SCREEN_SCALE_FACTOR=0 virtualbox' It works without problems with the workaround. - Description: Ubuntu 20.04.4 LTS Release: 20.04 Package: virtualbox-qt=6.1.32-dfsg-1~ubuntu1.20.04.1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: virtualbox 6.1.32-dfsg-1~ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon May 16 17:13:32 2022 InstallationDate: Installed on 2021-04-14 (396 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: virtualbox 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/1973623 Title: VirtualBox GUI is broken on multi-display systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1973623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973622] [NEW] unable to start repo tool
Public bug reported: When starting the repo command (with no arguments) in a initialized repo folder, it fails to start. Here is the traceback of the failure output on the shell. Traceback (most recent call last): File "/home/tepperson/yocto/.repo/repo/main.py", line 56, in from subcmds.version import Version File "/home/tepperson/yocto/.repo/repo/subcmds/__init__.py", line 35, in mod = __import__(__name__, File "/home/tepperson/yocto/.repo/repo/subcmds/help.py", line 20, in from formatter import AbstractFormatter, DumbWriter ModuleNotFoundError: No module named 'formatter' ** Affects: repo (Ubuntu) Importance: Undecided Status: New ** Tags: 22.04 ubuntu ** Tags added: 22.04 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973622 Title: unable to start repo tool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/repo/+bug/1973622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957104] Re: updating openssh-server fails, because port 22 is in use by systemd
Hello Thomas, Since the issue can't be reproduced in impish or jammy, is this an error you found in Focal, or has this been fixed for you? If it's an error in an earlier supported version then we can backport the fix to it. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957104 Title: updating openssh-server fails, because port 22 is in use by systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1957104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968067] Re: upgrade_lts_contract.py exception on impish and later
This bug was fixed in the package ubuntu-advantage-tools - 27.8~21.10.1 --- ubuntu-advantage-tools (27.8~21.10.1) impish; urgency=medium * Backport new upstream release: (LP: #1969125) to impish -- Lucas Moura Thu, 14 Apr 2022 15:32:46 -0300 ** Changed in: ubuntu-advantage-tools (Ubuntu Impish) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968067 Title: upgrade_lts_contract.py exception on impish and later To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1968067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969125] Re: [SRU] ubuntu-advantage-tools (27.7 -> 27.8) Xenial, Bionic, Focal, Impish, Jammy
This bug was fixed in the package ubuntu-advantage-tools - 27.8~16.04.1 --- ubuntu-advantage-tools (27.8~16.04.1) xenial; urgency=medium * Backport new upstream release: (LP: #1969125) to xenial -- Lucas Moura Thu, 14 Apr 2022 15:32:30 -0300 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969125 Title: [SRU] ubuntu-advantage-tools (27.7 -> 27.8) Xenial, Bionic, Focal, Impish, Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1969125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969125] Re: [SRU] ubuntu-advantage-tools (27.7 -> 27.8) Xenial, Bionic, Focal, Impish, Jammy
This bug was fixed in the package ubuntu-advantage-tools - 27.8~18.04.1 --- ubuntu-advantage-tools (27.8~18.04.1) bionic; urgency=medium * Backport new upstream release: (LP: #1969125) to bionic -- Lucas Moura Thu, 14 Apr 2022 15:32:35 -0300 ** Changed in: ubuntu-advantage-tools (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969125 Title: [SRU] ubuntu-advantage-tools (27.7 -> 27.8) Xenial, Bionic, Focal, Impish, Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1969125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969125] Re: [SRU] ubuntu-advantage-tools (27.7 -> 27.8) Xenial, Bionic, Focal, Impish, Jammy
This bug was fixed in the package ubuntu-advantage-tools - 27.8~20.04.1 --- ubuntu-advantage-tools (27.8~20.04.1) focal; urgency=medium * Backport new upstream release: (LP: #1969125) to focal -- Lucas Moura Thu, 14 Apr 2022 15:32:40 -0300 ** Changed in: ubuntu-advantage-tools (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969125 Title: [SRU] ubuntu-advantage-tools (27.7 -> 27.8) Xenial, Bionic, Focal, Impish, Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1969125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969125] Re: [SRU] ubuntu-advantage-tools (27.7 -> 27.8) Xenial, Bionic, Focal, Impish, Jammy
This bug was fixed in the package ubuntu-advantage-tools - 27.8~21.10.1 --- ubuntu-advantage-tools (27.8~21.10.1) impish; urgency=medium * Backport new upstream release: (LP: #1969125) to impish -- Lucas Moura Thu, 14 Apr 2022 15:32:46 -0300 ** Changed in: ubuntu-advantage-tools (Ubuntu Impish) Status: Fix Committed => Fix Released ** Changed in: ubuntu-advantage-tools (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969125 Title: [SRU] ubuntu-advantage-tools (27.7 -> 27.8) Xenial, Bionic, Focal, Impish, Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1969125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973619] Re: Sane net autodiscovery not working in 22.04
Thanks for your report. Question: Is sane-airscan installed? (It ought to be, since libsane1 recommends it.) ** Changed in: sane-backends (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973619 Title: Sane net autodiscovery not working in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1973619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973620] Re: prevent kernel panic with overlayfs + shiftfs
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Impish) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973620 Title: prevent kernel panic with overlayfs + shiftfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969935] Re: Update evolution to 3.44.1
Yes, I've tried evolution 3.44.1-0ubuntu1 too and it works well. I'm going to temporarily drop the verification-done tags because I want evolution-data-server 3.44.1 to be fully phased in jammy-updates first. ** Tags removed: verification-done-jammy ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969935 Title: Update evolution to 3.44.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1969935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973382] Re: autopkgtests failures due to debhelper 13.6 changes
** Changed in: postgresql-common (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/1973382 Title: autopkgtests failures due to debhelper 13.6 changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1973382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960014] Re: Missing Dutch language interface for LibreOffice in Snap installation
That works, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960014 Title: Missing Dutch language interface for LibreOffice in Snap installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1960014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973598] Re: mtd-self-test failure on arm64 (mtdram module)
It's running in KVM. (armhf is the exception, running inside LXD container) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973598 Title: mtd-self-test failure on arm64 (mtdram module) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1973598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931603] Re: [apparmor] Unable to show Downloads with apparmor enabled
** Branch linked: lp:~mozillateam/firefox/firefox.bionic ** Branch linked: lp:~mozillateam/firefox/firefox.focal ** Branch linked: lp:~mozillateam/firefox/firefox.impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931603 Title: [apparmor] Unable to show Downloads with apparmor enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931603] Re: [apparmor] Unable to show Downloads with apparmor enabled
Fix committed: https://bazaar.launchpad.net/~mozillateam/firefox/firefox.focal/revision/1552 https://bazaar.launchpad.net/~mozillateam/firefox/firefox.impish/revision/1585 The update will make its way to the security and updates pockets with the next stable update of firefox. ** Changed in: firefox (Ubuntu Focal) Status: Confirmed => Fix Committed ** Changed in: firefox (Ubuntu Impish) Status: Confirmed => 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/1931603 Title: [apparmor] Unable to show Downloads with apparmor enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973598] Re: mtd-self-test failure on arm64 (mtdram module)
Is autopkgtest running on "real" hardware? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973598 Title: mtd-self-test failure on arm64 (mtdram module) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1973598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973620] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1973620 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Impish) Status: New => Incomplete ** Changed in: linux (Ubuntu Jammy) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973620 Title: prevent kernel panic with overlayfs + shiftfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973620] [NEW] prevent kernel panic with overlayfs + shiftfs
Public bug reported: [Impact] The patch that we have recently re-introduced to properly support overlayfs on top of shiftfs can introduce potential kernel panics, for example: BUG: kernel NULL pointer dereference, address: 0008 [ 447.039738] #PF: supervisor read access in kernel mode [ 447.040369] #PF: error_code(0x) - not-present page [ 447.041002] PGD 0 P4D 0 [ 447.041325] Oops: [#1] SMP NOPTI [ 447.041798] CPU: 0 PID: 73766 Comm: sudo Not tainted 5.15.0-28-generic #29~20.04.1-Ubuntu [ 447.042800] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Ubuntu-1.8.2-1ubuntu1+esm1 04/01/2014 [ 447.043979] RIP: 0010:aa_file_perm+0x3a/0x470 [ 447.044565] Code: 54 53 48 83 ec 68 48 89 7d 80 89 4d 8c 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 63 05 01 0a 19 01 48 03 82 c0 00 00 00 <4c> 8b 68 08 f6 46 40 02 0f 85 d0 00 00 00 41 f6 45 40 02 0f 85 c5 [ 447.046837] RSP: 0018:aefe80a4bca8 EFLAGS: 00010246 [ 447.047481] RAX: RBX: 96e4038abd01 RCX: 0004 [ 447.048351] RDX: 96e4038abd00 RSI: 96e401215eb8 RDI: 9c22a2ac [ 447.049241] RBP: aefe80a4bd38 R08: R09: [ 447.050121] R10: R11: R12: 96e401215eb8 [ 447.051040] R13: 96e4038abd00 R14: 9c22a2ac R15: 0004 [ 447.051942] FS: 7eff3c0f8c80() GS:96e45e40() knlGS: [ 447.052981] CS: 0010 DS: ES: CR0: 80050033 [ 447.053696] CR2: 0008 CR3: 02be2000 CR4: 003506f0 [ 447.054571] Call Trace: [ 447.054883] [ 447.055154] ? unlock_page_memcg+0x2f/0x40 [ 447.055668] ? page_remove_rmap+0x4b/0x320 [ 447.056180] common_file_perm+0x72/0x170 [ 447.056669] apparmor_file_permission+0x1c/0x20 [ 447.057237] security_file_permission+0x30/0x1a0 [ 447.057898] rw_verify_area+0x35/0x60 [ 447.058392] vfs_read+0x6d/0x1a0 [ 447.058842] ksys_read+0xb1/0xe0 [ 447.059276] __x64_sys_read+0x1a/0x20 [ 447.059732] do_syscall_64+0x5c/0xc0 [ 447.060183] ? __set_current_blocked+0x3b/0x60 [ 447.060738] ? exit_to_user_mode_prepare+0x3d/0x1c0 [ 447.061434] ? syscall_exit_to_user_mode+0x27/0x50 [ 447.062099] ? do_syscall_64+0x69/0xc0 [ 447.062603] ? irqentry_exit_to_user_mode+0x9/0x20 [ 447.063210] ? irqentry_exit+0x19/0x30 [ 447.063678] ? exc_page_fault+0x89/0x160 [ 447.064165] ? asm_exc_page_fault+0x8/0x30 [ 447.064675] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 447.065298] RIP: 0033:0x7eff3c2cb002 [Test case] It is really easy to trigger this specific kernel panic running the lxc autopackage test. [Fix] This bug happens because we don't need to decrement anymore the refcount for the previous vm_file value in ovl_vm_prfile_set(). So the fix simply consists of removing the unnecessary fput(). [Regression potential] This patch affects only overlayfs (only when AUFS is enabled), so we may see regressions in overlayfs in kernels that have AUFS enabled (focal hwe and cloud kernels). ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Impish) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) 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/1973620 Title: prevent kernel panic with overlayfs + shiftfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973619] [NEW] Sane net autodiscovery not working in 22.04
Public bug reported: I have used every Ubuntu version since 16.10 and on all of them my network scanner EPSON SX525WD could be discovered out of the box. On 22.04 the output of 'scanimage -L' is: No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). To double-check if something hadn't changed in my network, I opened a laptop which still has Ubuntu 21.10 installed. I ran 'scanimage -L' and it shows: device `epson2:net:192.168.8.8' is a Epson PID 085E flatbed scanner device `airscan:w0:EPSON Epson Stylus SX525WD' is a WSD EPSON Epson Stylus SX525WD ip=192.168.8.8 My current workaround for 22.04 is to append the line: net 192.168.8.8 to /etc/sane.d/epson2.conf. The command 'scanimage -L' detects the scanner (albeit no 'airscan' result shows up): device `epson2:net:192.168.8.8' is a Epson PID 085E flatbed scanner NOTE: I filled this bug under the 'sane-backends' package because this form gave this error: "sane-utils" does not exist in Ubuntu ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: sane-utils 1.1.1-5 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon May 16 15:53:46 2022 InstallationDate: Installed on 2020-02-02 (833 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: sane-backends UpgradeStatus: Upgraded to jammy on 2022-05-06 (9 days ago) ** Affects: sane-backends (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/1973619 Title: Sane net autodiscovery not working in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1973619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973618] Re: can no longer open new windows after some time
Thank you for taking the time to report this bug and help make Ubuntu better. Firefox is provided by a snap published by Mozilla, and they may not be aware of this issue. Please contact them via https://support.mozilla.org/kb/file-bug-report-or-feature-request- mozilla and link the bug report here so it can be further tracked. Thank you! ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973618 Title: can no longer open new windows after some time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1973618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958668] Re: Do not propose to reboot on WSL
** Changed in: update-manager (Ubuntu) Status: New => Triaged ** Changed in: update-manager (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958668 Title: Do not propose to reboot on WSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1958668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973382] Re: autopkgtests failures due to debhelper 13.6 changes
** Bug watch added: Debian Bug tracker #1011067 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011067 ** Also affects: postgresql-common (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011067 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/1973382 Title: autopkgtests failures due to debhelper 13.6 changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1973382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973589] Re: Restart loop when using PathExistsGlob
** Description changed: When using PathExistsGlob in a path unit, systemd starts the corresponding service unit in an infinite loop. We have observed this problem only under Jammy. -- [Unit] Description=Test [Path] PathExistsGlob=/home/www-data/test/*.so Unit=test.service [Install] WantedBy=multi-user.target -- [Unit] Description=Test [Service] Type=simple ExecStart=echo test StartLimitBurst=1000 [Install] WantedBy=multi-user.target + + - + www-data@josi-test-jammy03:~ $ systemctl --user status test.path + × test.path - Test + Loaded: loaded (/home/www-data/.config/systemd/user/test.path; disabled; vendor preset: enabled) + Active: failed (Result: unit-start-limit-hit) since Mon 2022-05-16 17:08:08 CEST; 121ms ago +Triggers: ● test.service + + May 16 17:08:04 josi-test-jammy03 systemd[24979]: Started Test + May 16 17:08:08 josi-test-jammy03 systemd[24979]: test.path: Failed with result 'unit-start-limit-hit'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973589 Title: Restart loop when using PathExistsGlob To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1973589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973618] [NEW] can no longer open new windows after some time
Public bug reported: After some time using firefox, I can no longer open a new window. => ps -ef | grep -c firefox 21 => /snap/bin/firefox => ps -ef | grep -c firefox 21 There is no new process created and the window never appears. I can open new tabs, but when I drag the tab to make it a new window, it is never created. The only remedy is to restart firefox. Sometimes I need to SIGTERM all of the zombi processes. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 15 19:45:08 2022 InstallationDate: Installed on 2021-10-12 (215 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2022-04-22 (22 days ago) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973618 Title: can no longer open new windows after some time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1973618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973615] Re: gnome-shell crashed with SIGSEGV in meta_window_get_window_type()
*** This bug is a duplicate of bug 1972812 *** https://bugs.launchpad.net/bugs/1972812 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1965897, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1973615/+attachment/5590073/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1973615/+attachment/5590075/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1973615/+attachment/5590079/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1973615/+attachment/5590080/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1973615/+attachment/5590081/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1973615/+attachment/5590084/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1973615/+attachment/5590085/+files/ThreadStacktrace.txt ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973615 Title: gnome-shell crashed with SIGSEGV in meta_window_get_window_type() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969935] Re: Update evolution to 3.44.1
Using 3.44.1-0ubuntu1 evolution works fine, tested email and calendar and played a bit with the options without issue ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969935 Title: Update evolution to 3.44.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1969935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971509] Re: qemu/kvm win10 client cannot upgrade to win11
Hello peterzay, The secure boot failure may indicate you don't have it installed on your system. Try running: sudo apt install ovmf If it is not already installed try running your vm again. Also it may help to enable SATA CDROM 1 in your boot options. Not having it has caused some issues for me in the past. See the screenshot for how to enable this. Otherwise, if both fail, you may want to create a new vm and install Windows 11 from there with TPM2.0, secure boot, and SATA CDROM enabled from the start. ** Attachment added: "boot.png" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1971509/+attachment/5590088/+files/boot.png ** Changed in: qemu (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971509 Title: qemu/kvm win10 client cannot upgrade to win11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1971509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973463] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1973463 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973463 Title: ZFS kernel null pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973598] Re: mtd-self-test failure on arm64 (mtdram module)
I think the question we'd need to ask first is: Why is there a /dev/mtd0 inside Ubuntu's arm64 autopkgtest VM? At no point during the tests do we modprobe the "mtdram" driver. So it is expected that /dev/mtd0 is not there and this test is skipped (as is the case for Debian and Ubuntu != arm64). Also, when I launch a Ubuntu Karmic VM in OpenStack, it does not have /dev/mtd0, only after "modprobe mtdram" can I query it: $ cat /sys/devices/virtual/mtd/mtd0/size 4194304 $ cat /sys/devices/virtual/mtd/mtd0/name mtdram test device The test is supposed to run against "mtdram", and 0x40=4194304 is the default size of that module, so that constant value is actually correct IMO, but the tests should be loading that module prior to executing the test. And it's strange that Ubuntu/arm64 would have a different mtd0 device.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973598 Title: mtd-self-test failure on arm64 (mtdram module) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1973598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972812] Re: gnome-shell (X11, nvidia-390) crashes with SIGSEGV when unlocking the screen
Finally got the crashdump uploaded but had to add all the details to a new ticket: LP#1973615 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972812 Title: gnome-shell (X11, nvidia-390) crashes with SIGSEGV when unlocking the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874578] Re: Dock has very long load time when show-mounts is enabled
Using 70~ubuntu3.21.10.1 there is no visble delay and the icons are still right ** Tags removed: verification-needed verification-needed-impish ** Tags added: verification-done verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874578 Title: Dock has very long load time when show-mounts is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1874578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else
We haven't got new reports since the fix landed nor visible regression so let's say the fix is working as intended. ** Tags removed: verification-needed verification-needed-impish ** Tags added: verification-done verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913775 Title: Copy from Firefox Wayland fails to be pasted anywhere else To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1913775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
Promotion from -proposed sure would be nice. I see verification has been done but a update excuses shows an netplan.io regression[1]. I'm not sure if the test is flaky but I see that seb retried it a few times[2] last week and it failed consistently, so maybe not. I'm just curious if there's any status on the test failure. (Also, I started writing this thinking it had been a month but it's been less than a week and I can't tell time. I know it wouldn't be promoted with less than a week in -proposed anyway.) [1] https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#wpa [2] https://autopkgtest.ubuntu.com/packages/netplan.io/jammy/arm64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949572] Re: Shell freeze after right click on the app in the dock
Using 70~ubuntu3.21.10.1 there is no freeze and the previews are correct ** Tags removed: verification-needed verification-needed-impish ** Tags added: verification-done verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949572 Title: Shell freeze after right click on the app in the dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1949572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973463] Re: ZFS kernel null pointer dereference
** Package changed: zfs-linux (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973463 Title: ZFS kernel null pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922342] Re: Impish live session takes ages to boot on BIOS systems
I agree with Thomas about the problems to boot some old computers. I'm continuing to develop/tweak dus-iso2usb, added an extra (optional) parameter 'boot-flag' that can be added when mkusb partition table is selected. It helps HP computers, but may spoil booting some other computers. So I think we probably need ways to get boot drive versions with and without a boot flag. One way would be two different iso files, another way is to use some special tool (like dus-iso2usb) for the corner cases that need a boot flag. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922342 Title: Impish live session takes ages to boot on BIOS systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1922342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
Hi Sujith - Can you update this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972766] Re: Changing default mounting options causes root owner
Thank you for your bug report. That's probably worth reporting upstream on https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues Unsure it is changing the mount option, when selecting as an user it can map to the user who did the action but for a system mount that's not possible. The UI could provide easier way to set those options though ** Changed in: gnome-disk-utility (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972766 Title: Changing default mounting options causes root owner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1972766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
Thank you Seb, I had the issue reported in this bug in a WeWork today (first time connecting since updating to Jammy) and the package in -proposed resolved the issue for me as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967860] Re: autopackage tests fail
https://autopkgtest.ubuntu.com/results/autopkgtest- kinetic/kinetic/ppc64el/c/composer/20220516_103941_ee570@/log.gz passed. ** Changed in: composer (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967860 Title: autopackage tests fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/composer/+bug/1967860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973320] Re: ua attach doesn't finish properly and shows "unexpected error" as a message
*** This bug is a duplicate of bug 1972809 *** https://bugs.launchpad.net/bugs/1972809 it is probably the same issue than bug #1972809 ** This bug has been marked a duplicate of bug 1972809 Cant enable ua from GUI, works from CLI -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973320 Title: ua attach doesn't finish properly and shows "unexpected error" as a message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1973320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973394] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1973394 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973394 Title: Can't find integrated camera in Ubuntu 22.04 on Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973433] Re: Cannot upgrade Ubuntu 21.10 to 22.04 - error info without concrete reason
It looks like your nodejs (version nodejs 15.14.0-deb-1nodesource1) is from the nodesource PPA. Since your upgrade is failing on a broken node- yargs-parser (according to VarLogDistupgradeAptlog.txt), I would guess this has something to do with it: Investigating (1) node-yargs-parser:amd64 < 18.1.3+~15.0.0-1 -> 21.0.0+~20.2.1-3 @ii umU Ib > Broken node-yargs-parser:amd64 Breaks on node-yargs:amd64 < 15.3.1+repack-2 @ii umH > (< 16.2.0~) Considering node-yargs:amd64 -3 as a solution to node-yargs-parser:amd64 1 Upgrading node-yargs:amd64 due to Breaks field in node-yargs-parser:amd64 Please try removing PPA packages with the ppa-purge tool, and then try the upgrade again. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973433 Title: Cannot upgrade Ubuntu 21.10 to 22.04 - error info without concrete reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1973433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973101] Re: After upgrade to 22.04 NFS exports for vers 2 and 3 no longer work
NFS UDP was disabled in the upstream kernel[1] in 2019, and the first Ubuntu release with that change was 20.10 (groovy). I didn't find this change in the 20.10 release notes, and added this bit to the 22.04 release notes[2] about a month before the release: """ UDP disabled for NFS mounts Since Ubuntu 20.10 (“Groovy Gorilla”), the kernel option CONFIG_NFS_DISABLE_UDP_SUPPORT=y is set and this disables using UDP as the transport for NFS mounts, regardless of NFS version. In practice, if you try to use udp, you will get this error: $ sudo mount f1:/storage /mnt -o udp mount.nfs: an incorrect mount option was specified """ If you can't get the older clients to use TCP, then I think the only way is for you to stick to an older Ubuntu release that still has UDP NFS support, like Focal (20.04). 1. https://patchwork.kernel.org/project/linux-nfs/patch/20191121160651.5317-1-olga.kornievsk...@gmail.com/ 2. https://discourse.ubuntu.com/t/jammy-jellyfish-release-notes/24668 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973101 Title: After upgrade to 22.04 NFS exports for vers 2 and 3 no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1973101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907250] Re: [focal] charm becomes blocked with workload-status "Failed to connect to MySQL"
** Tags added: cdo-qa foundations-engine -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907250 Title: [focal] charm becomes blocked with workload-status "Failed to connect to MySQL" To manage notifications about this bug go to: https://bugs.launchpad.net/charm-mysql-router/+bug/1907250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922342] Re: Impish live session takes ages to boot on BIOS systems
Hi, Chris Guiver wrote: > BOOT2: LIVE > 00:25 secs & screen blanks & messages > 00:35 plymouth visible > 01:11 message(s) again & plymouth gone > 02:23 system fully-operational The overall boot time is still very long. But no particular stage stands out as the big time waster. >...> motion computing j3400 This one is possibly allowed to be somewhat slow. > Ubuntu Desktop 22.04 LTS > 08:01 screen blanked I really wonder which side, GRUB or vmlinuz, causes this delay. After wasting time with clueless experiments i re-read what we have and what i vastly forgot. -- This prompts another test request @ Chris Guiver: Does it help to remove MBR partition 2 similarly to what i proposed a year ago to José Marinho and what helped to boot: # (When replacing the "X", take care not to zap your system disk) STICK=/dev/sdX dd if=/dev/zero bs=1 count=16 of="$STICK" conv=notrunc seek=462 Last year this worked only once, because casper added the partition again during "persistent partition creation". This could be fixed now: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/comments/60 If not fixed: A second dd treatment after the first boot was not overridden by casper in the next Live system run. -- Summary of my re-reading: José Marinho wrote in https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1922342/comments/35 > With the iso without any change: > - Plymouth --> 7 minutes > - Desktop environment --> 7 minutes 50 seconds > Marking the first partition as bootable legacy BIOS: > - Plymouth --> 54 seconds. > - Desktop environment --> 1 minute 45 seconds > Without marking any partition as bootable but changing the partition table > from GPT to MBR: > - Plymouth --> 25 seconds. > - Desktop environment --> 1 minute 20 seconds. So we had already a good suspect for a delay of about 6 minutes. Then we had the red herring of these lines in grub.cfg which for a while seemed to be the culprit. I proposed a change in #39. But in #55, José Marinho finally reported that the intermediate success was rather due to inadverted partition table changes during the experients. In #60 i propose to remove partition 2 from the MBR. (This partition exists to lure in some HP laptops which want to see a boot flag. This flag is forbidden for the GPT-announcing partition slot.) José Marinho reports in #61 that this helps for one time booting, but not for further attempts to boot. In #70 i demonstrated that the software in the ISO manipulates the MBR partition table of the stick. In #73 i point to "casper" and its "persistent partition creation". Chris Guiver introduced the j3400 tablet to us in #76. Chris Guiver and Brian Murray let GRUB be verbose in #82 and #83. It prints: > "Booting a command list" Screenshots are at #84 and #85. Since the messages do not look to me like from a Linux kernel, it appears that the delay is in GRUB. We could ask at grub-devel for help. But it happens only to a few (old ?) machines and it is about the boot flag, which at least Vladimir Serbinko rejected firmly when the HP laptops showed up which don't boot without it. So the conclusion of "tlk (sarcasticskull)" in #91 is noteworthy: > kinda frustrating that the fixes/kludges for both "advanced" EFI and > legacy crap "proprietary" systems suddenly make booting an Ubuntu LTS > live ISO impossible I thought i had read the proposal to have two flavors of Live ISOs but cannot find currently it in this giant bug report. So without the claim to have invented it myself: Have an EFI+BIOS flavor without the problematic boot flag in the MBR, and an Odd-Old-BIOS flavor without GPT and with boot flag. Most machines, including those which are affected by this bug would boot by the EFI+BIOS ISOs. Only a few would need Odd-Old-BIOS. - A peek over the fence: Fedora considers to adopt for its ISOs the GPT partition layout without boot flag in MBR: https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/message/2G3DQ5SGCV5DSD7NPVXU3KAKQ57BOXVU/ They found a Dell XPS 15 L502X laptop which does not boot from this but also does not boot if a boot flag MBR partition is added. Nevertheless it looks like Fedora is willing to leave it behind together with the HP laptops which want the boot flag. Have a nice day :) Thomas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922342 Title: Impish live session takes ages to boot on BIOS systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1922342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973379] Re: "additional drivers" says we are using nvidia drivers but its not true
Thank you for your bug report, could you include the output of $ ubuntu-drivers debug ? ** Changed in: software-properties (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973379 Title: "additional drivers" says we are using nvidia drivers but its not true To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1973379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973389] Re: Audio freezes, skips and failure to change volume when opening snap
Thank you for your bug report, could you perhaps report it upstream on https://gitlab.freedesktop.org/pipewire/pipewire/-/issues ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973389 Title: Audio freezes, skips and failure to change volume when opening snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1973389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973394] Re: Can't find integrated camera in Ubuntu 22.04 on Lenovo
** Package changed: cheese (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973394 Title: Can't find integrated camera in Ubuntu 22.04 on Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973612] [NEW] The installer said it couldn't install because there wasn't enough space but this was on a 128gb M.2 nvme stick.
Public bug reported: On my computer I have a 500gb ssd drive, as well as a 1tb regard hard drive. I've installed windows on the SSD and am trying to install ubuntu on the M.2 NVME stick. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.15 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: ubuntu:GNOME Date: Mon May 16 10:16:11 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-22.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973612 Title: The installer said it couldn't install because there wasn't enough space but this was on a 128gb M.2 nvme stick. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1973612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973598] Re: mtd-self-test failure on arm64 (mtdram module)
I suspect the self tests need to check the name is "mtdram test device" before running. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973598 Title: mtd-self-test failure on arm64 (mtdram module) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1973598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969434] Re: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1037.41 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969434 Title: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1969434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959581] Re: OCFS2 intermittently not mountable on a second Node in Ubuntu 20.04.3 LTS
Last week has been a bit busy and I couldn't get to this, sorry; it's still on my list. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959581 Title: OCFS2 intermittently not mountable on a second Node in Ubuntu 20.04.3 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/1959581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973425] Re: 22.04 file chooser automatically resizing in snap apps
*** This bug is a duplicate of bug 1971112 *** https://bugs.launchpad.net/bugs/1971112 ** This bug has been marked a duplicate of bug 1971112 File picker gets bigger more and more each time! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973425 Title: 22.04 file chooser automatically resizing in snap apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1973425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968096] Re: [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z
** Changed in: ubuntu-z-systems Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Frank Heimes (fheimes) ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968096 Title: [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1968096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969598] Re: Desktop Icons NG steals keyboard focus from apps after workspace switch
@daniel: thanks for the link, bug filed: https://gitlab.com/rastersoft/desktop-icons-ng/-/issues/235 ** Bug watch added: gitlab.com/rastersoft/desktop-icons-ng/-/issues #235 https://gitlab.com/rastersoft/desktop-icons-ng/-/issues/235 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969598 Title: Desktop Icons NG steals keyboard focus from apps after workspace switch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1969598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973054] Re: containerd regression for CVE-2022-23648 in latest version 1.5.9-0ubuntu1~20.04.1
This bug was fixed in the package containerd - 1.5.9-0ubuntu1~20.04.4 --- containerd (1.5.9-0ubuntu1~20.04.4) focal-security; urgency=medium * SECURITY UPDATE: Insecure handling of image volumes - debian/patches/CVE-2022-23648.patch: Use fs.RootPath when mounting volumes. (LP: #1973054) - CVE-2022-23648 -- Paulo Flabiano Smorigo Thu, 12 May 2022 13:42:43 + -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973054 Title: containerd regression for CVE-2022-23648 in latest version 1.5.9-0ubuntu1~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1973054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973054] Re: containerd regression for CVE-2022-23648 in latest version 1.5.9-0ubuntu1~20.04.1
This bug was fixed in the package containerd - 1.5.9-0ubuntu1~21.10.3 --- containerd (1.5.9-0ubuntu1~21.10.3) impish-security; urgency=medium * SECURITY UPDATE: Insecure handling of image volumes - debian/patches/CVE-2022-23648.patch: Use fs.RootPath when mounting volumes. (LP: #1973054) - CVE-2022-23648 -- Paulo Flabiano Smorigo Thu, 12 May 2022 13:41:37 + ** Changed in: containerd (Ubuntu Impish) Status: Confirmed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-23648 ** Changed in: containerd (Ubuntu Focal) 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/1973054 Title: containerd regression for CVE-2022-23648 in latest version 1.5.9-0ubuntu1~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1973054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971279] Re: Merge haproxy from Debian unstable for kinetic
** Changed in: haproxy (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: haproxy (Ubuntu) Status: New => In Progress ** Changed in: haproxy (Ubuntu) Milestone: ubuntu-22.06 => ubuntu-22.05 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971279 Title: Merge haproxy from Debian unstable for kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1971279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973382] Re: autopkgtests failures due to debhelper 13.6 changes
Hi Dave, Thanks for the thoughtful reply! > After all, if it's simulating a reinstallation, shouldn't it restart the service? [...] Usually, yes, I agree it should restart the service. In this specific postgresql-common case, debian/rules was crafted so a restart would not happen at this point: https://salsa.debian.org/postgresql/postgresql- common/-/blob/master/debian/rules#L27-31 Now, while the test suite regression is only present in Ubuntu (and not in Debian) due to the dpkg-reconfigure delta, a change of behavior was also introduced in the upgrade path due to the debhelper change at https://salsa.debian.org/debian/debhelper/-/commit/742b0c5ac8f4a6cfcd699f08915a8109a5ebec35. The service, which would be left untouched on postgresql-common upgrades, will now be stopped on upgrades. Finally, > You are certainly correct that [we should add --no-stop-on-upgrade option to dh_installsystemd?] This would restore the previous, designed behavior of the package upgrade path. Still, the preinst script would differ from the Debian one. Therefore, I filed https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/postgresql- common/+git/postgresql-common/+merge/422669 and will also file a Debian bug to include the Debian maintainers in the discussion before we do introduce the delta here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973382 Title: autopkgtests failures due to debhelper 13.6 changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1973382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973470] Re: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic
Thanks you for you bug report, does that cmd work for you? $ xdg-open http://www.ubuntu.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973470 Title: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1973470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973468] Re: New Windows from favorites often not working
Thank you for your bug report? Could you do $ journalctl -f then try to trigger the bug and copy the log section once you get the issue? ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973468 Title: New Windows from favorites often not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1973468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973565] Re: Upgrade to 21.10 not working
Hi Carsten, Looking at the attached VarLogDistupgradeMainlog.txt, it looks like the mirror you are using does not have information for the impish release: 2022-05-15 12:30:21,956 DEBUG examining: 'deb https://mirrors.tuxedocomputers.com/ubuntu/mirror/archive.ubuntu.com/ubuntu focal main restricted universe multiverse' 2022-05-15 12:30:21,956 DEBUG found apt-cacher/apt-torrent style uri https://mirrors.tuxedocomputers.com/ubuntu/mirror/archive.ubuntu.com/ubuntu 2022-05-15 12:30:21,956 DEBUG verifySourcesListEntry: deb https://mirrors.tuxedocomputers.com/ubuntu/mirror/archive.ubuntu.com/ubuntu impish main restricted universe multiverse 2022-05-15 12:30:21,957 DEBUG url_downloadable: https://mirrors.tuxedocomputers.com/ubuntu/mirror/archive.ubuntu.com/ubuntu/dists/impish/Release 2022-05-15 12:30:21,957 DEBUG s='https' n='mirrors.tuxedocomputers.com' p='/ubuntu/mirror/archive.ubuntu.com/ubuntu/dists/impish/Release' q='' f='' 2022-05-15 12:30:22,043 DEBUG error from httplib: 'HTTP Error 404: Not Found' Please select another mirror and try the upgrade again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973565 Title: Upgrade to 21.10 not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1973565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973610] [NEW] Bluetooth will not stay on or connect to devices when on
Public bug reported: Since upgrading from Ubuntu 20.10, my internal bluetooth card as well as an external usb dongle will not work. Bluetooth starts as off, and cannot be turned on. If I use systemctl to turn it on, it is on but doesn't find any devices through bluez. Blueman finds devices but cannot connect to them. The hardware on this machine has remained identical; the only difference is the new version of Ubuntu. Hence the problem has to be software. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 09:45:02 2022 InstallationDate: Installed on 2021-10-22 (205 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=710f912e-cc80-4456-915a-90de1169d201 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-05-03 (12 days ago) dmi.bios.date: 08/04/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.50 dmi.board.name: N7 B550 dmi.board.vendor: NZXT dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.50:bd08/04/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnNZXT:rnN7B550:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. hciconfig: hci0: Type: Primary Bus: USB BD Address: 5C:F3:70:A8:66:B1 ACL MTU: 1021:8 SCO MTU: 64:1 DOWN INIT RUNNING RX bytes:175353 acl:52 sco:0 events:6887 errors:0 TX bytes:18571 acl:52 sco:0 commands:1087 errors:2 mtime.conffile..etc.bluetooth.main.conf: 2022-05-16T09:39:58.915340 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973610 Title: Bluetooth will not stay on or connect to devices when on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1973610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747499] Re: 98-reboot-required and Interaction with livepatch
The package FTBFS against -proposed but builds successfully against the -release pocket. Based on the error, it seems related to recent changes in how apt determines kernels that can be autoremoved. apt (2.0.7) focal; urgency=medium * Revert "Protect currently running kernel at run-time" * Backport Determine autoremovable kernels at run-time (LP: #1615381) as of 2.4.5; including the change to only protect two kernels, not last installed one (LP: #1968154) -- Julian Andres Klode Mon, 25 Apr 2022 15:58:46 +0200 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747499 Title: 98-reboot-required and Interaction with livepatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1747499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973608] Re: udev TAG-="uaccess" does not work on ubuntu 22.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (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/1973608 Title: udev TAG-="uaccess" does not work on ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1973608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973609] [NEW] Bluetooth not starting/working
Public bug reported: Bluetooth simply will not turn on. I have an internal card and a usb dongle, both of which worked in Ubuntuu 20.10 - they will not work now. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: blueman 2.2.4-1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 09:41:07 2022 InstallationDate: Installed on 2021-10-22 (205 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: blueman UpgradeStatus: Upgraded to jammy on 2022-05-03 (12 days ago) ** Affects: blueman (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973609 Title: Bluetooth not starting/working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1973609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973474] Re: Rename "Pin to Dash" to "Pin to Dock"
If we go this route, we'll need yet another conditional in dash-to-dock. Adding gnome-shell-extension-ubuntu-dock as affected package. ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973474 Title: Rename "Pin to Dash" to "Pin to Dock" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1973474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973382] Re: autopkgtests failures due to debhelper 13.6 changes
** Merge proposal linked: https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/postgresql-common/+git/postgresql-common/+merge/422669 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973382 Title: autopkgtests failures due to debhelper 13.6 changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1973382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973608] [NEW] udev TAG-="uaccess" does not work on ubuntu 22.04
Public bug reported:
Ubuntu 22.04.
Udev version 249.11-0ubuntu3.1.
I have 72-my-rule.rules
ACTION=="add|bind", SUBSYSTEM=="usb",
ENV{ID_USB_INTERFACES}=="*:060101:*", TAG-="uaccess", RUN:="/bin/setfacl
-m g:sudo:rw -m g:plugdev:rw $env{DEVNAME}"
It removes TAG uaccess for my usb device. On my ubuntu 18.04 and 20.04
it works fine, but on 22.04 does not. It causes next rule 73-seat-
late.rules to run builtin uaccess, which does not need to run.
# SPDX-License-Identifier: LGPL-2.1-or-later
#
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
ACTION=="remove", GOTO="seat_late_end"
ENV{ID_SEAT}=="", ENV{ID_AUTOSEAT}=="1", ENV{ID_FOR_SEAT}!="",
ENV{ID_SEAT}="seat-$env{ID_FOR_SEAT}"
ENV{ID_SEAT}=="", IMPORT{parent}="ID_SEAT"
ENV{ID_SEAT}!="", TAG+="$env{ID_SEAT}"
TAG=="uaccess", ENV{MAJOR}!="", RUN{builtin}+="uaccess"
LABEL="seat_late_end"
Udev info:
udevadm info -q all -n /dev/bus/usb/001/007
P: /devices/pci:00/:00:14.0/usb1/1-1
N: bus/usb/001/007
L: 0
E: DEVPATH=/devices/pci:00/:00:14.0/usb1/1-1
E: DEVNAME=/dev/bus/usb/001/007
E: DEVTYPE=usb_device
E: DRIVER=apple-mfi-fastcharge
E: PRODUCT=5ac/12a8/1302
E: TYPE=0/0/0
E: BUSNUM=001
E: DEVNUM=007
E: MAJOR=189
E: MINOR=6
E: SUBSYSTEM=usb
E: USEC_INITIALIZED=2331114479
E: USBMUX_SUPPORTED=1
E: SYSTEMD_WANTS=usbmuxd.service
E: ID_VENDOR=Apple_Inc.
E: ID_VENDOR_ENC=Apple\x20Inc.
E: ID_VENDOR_ID=05ac
E: ID_MODEL=iPhone
E: ID_MODEL_ENC=iPhone
E: ID_MODEL_ID=12a8
E: ID_REVISION=1302
E: ID_SERIAL=Apple_Inc._iPhone_8101000A2DD826B8001E
E: ID_SERIAL_SHORT=8101000A2DD826B8001E
E: ID_BUS=usb
E: ID_USB_INTERFACES=:060101:010100:010200:03:fffe02:fffd01:
E: ID_VENDOR_FROM_DATABASE=Apple, Inc.
E: GPHOTO2_DRIVER=PTP
E: ID_GPHOTO2=1
E: ID_MODEL_FROM_DATABASE=iPhone 5/5C/5S/6/SE
E: ID_PATH=pci-:00:14.0-usb-0:1
E: ID_PATH_TAG=pci-_00_14_0-usb-0_1
E: ID_FOR_SEAT=usb-pci-_00_14_0-usb-0_1
E: COLORD_DEVICE=1
E: COLORD_KIND=camera
E: TAGS=:uaccess:seat:systemd:
E: CURRENT_TAGS=:seat:systemd:
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: Confirmed
** Description changed:
+ Ubuntu 22.04.
+ Udev version 249.11-0ubuntu3.1.
+
I have 72-my-rule.rules
ACTION=="add|bind", SUBSYSTEM=="usb",
ENV{ID_USB_INTERFACES}=="*:060101:*", TAG-="uaccess", RUN:="/bin/setfacl
- -m g:sudo:rw -m g:plugdev:rw -m g:2046:rw -m g:2027:rw $env{DEVNAME}"
+ -m g:sudo:rw -m g:plugdev:rw $env{DEVNAME}"
It removes TAG uaccess for my usb device. On my ubuntu 18.04 and 20.04
it works fine, but on 22.04 does not. It causes next rule 73-seat-
late.rules to run builtin uaccess, which does not need to run.
# SPDX-License-Identifier: LGPL-2.1-or-later
#
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
ACTION=="remove", GOTO="seat_late_end"
ENV{ID_SEAT}=="", ENV{ID_AUTOSEAT}=="1", ENV{ID_FOR_SEAT}!="",
ENV{ID_SEAT}="seat-$env{ID_FOR_SEAT}"
ENV{ID_SEAT}=="", IMPORT{parent}="ID_SEAT"
ENV{ID_SEAT}!="", TAG+="$env{ID_SEAT}"
TAG=="uaccess", ENV{MAJOR}!="", RUN{builtin}+="uaccess"
LABEL="seat_late_end"
** Description changed:
Ubuntu 22.04.
Udev version 249.11-0ubuntu3.1.
I have 72-my-rule.rules
ACTION=="add|bind", SUBSYSTEM=="usb",
ENV{ID_USB_INTERFACES}=="*:060101:*", TAG-="uaccess", RUN:="/bin/setfacl
-m g:sudo:rw -m g:plugdev:rw $env{DEVNAME}"
It removes TAG uaccess for my usb device. On my ubuntu 18.04 and 20.04
it works fine, but on 22.04 does not. It causes next rule 73-seat-
late.rules to run builtin uaccess, which does not need to run.
# SPDX-License-Identifier: LGPL-2.1-or-later
#
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
ACTION=="remove", GOTO="seat_late_end"
ENV{ID_SEAT}=="", ENV{ID_AUTOSEAT}=="1", ENV{ID_FOR_SEAT}!="",
ENV{ID_SEAT}="seat-$env{ID_FOR_SEAT}"
ENV{ID_SEAT}=="", IMPORT{parent}="ID_SEAT"
ENV{ID_SEAT}!="", TAG+="$env{ID_SEAT}"
TAG=="uaccess", ENV{MAJOR}!="", RUN{builtin}+="uaccess"
LABEL="seat_late_end"
+
+ Udev info:
+ udevadm info -q all -n /dev/bus/usb/001/007
+ P: /devices/pci:00/:00:14.0/usb1/1-1
+ N: bus/usb/001/007
+ L: 0
+ E: DEVPATH=/devices/pci:00/:00:14.0/usb1/1-1
+ E: DEVNAME=/dev/bus/usb/001/007
+ E: DEVTYPE=usb_device
+ E: DRIVER=apple-mfi-fastcharge
[Bug 1970819] Re: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi
v1 upstream got rejected, submitted v2 now https://lore.kernel.org/linux- bluetooth/20220516103329.516952-1-dimitri.led...@canonical.com/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970819 Title: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973607] Re: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)
Please find attached the debdiff between debian package and the ubuntu one. ** Patch added: "debdiff_debian_ubuntu.debdiff" https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+attachment/5590044/+files/debdiff_debian_ubuntu.debdiff ** Tags added: fr-2388 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973607 Title: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973607] Re: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)
Please find attached the debdiff between old ubuntu version and the new one. ** Patch added: "debdiff_oldubuntu_newubuntu.debdiff" https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+attachment/5590043/+files/debdiff_oldubuntu_newubuntu.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973607 Title: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970090] Re: Backintime not launching because of python error
I think, 22.04 being an LTS release, must have a working backup software. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970090 Title: Backintime not launching because of python error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/1970090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973598] Re: mtd-self-test failure on arm64 (mtdram module)
While we have the luxury of time with kinetic, I'd rather we figure out why the test fails rather than just skipping it. If the test is failing, the plugin may fail too! It seems that this code should be reading the "size" attribute from sysfs and comparing it (here https://github.com/fwupd/fwupd/blob/main/plugins/mtd/fu-mtd-device.c#L161) to a static value (here https://github.com/fwupd/fwupd/blob/main/plugins/mtd/fu-self-test.c#L53). That seems like a coding error to me. Maybe you can take a PR upstream to adjust it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973598 Title: mtd-self-test failure on arm64 (mtdram module) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1973598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973438] Re: /dev/fd0 no such file or directory
Hello, This project is only for issues with the Ubuntu One Single Sign-On service, and the problem you describe does not seem to be directly with the sign-on service. Further, the problem you describe is not a bug but probably a support request, so here are some pointers for the correct places to get help: If you need help with general Ubuntu issues you have two main choices. The first is to rely on free support provided by the Ubuntu community. For this please visit https://www.ubuntu.com/support/community-support or post your questions directly in http://askubuntu.com/ or https://ubuntuforums.org/. The second if you're looking for commercial-grade support, is to check out Canonical's support offerings for Ubuntu at https://www.ubuntu.com/support. I hope this helps you find a solution to your issue. Regards, - Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973438 Title: /dev/fd0 no such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1973438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973607] [NEW] Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)
Public bug reported: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) ** Affects: logrotate (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/1973607 Title: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir
Thanks Alberto. I tried running "hello" in a different directory, and you were correct: arc@andrewfairfield:~$ hello cannot open path of the current working directory: Permission denied arc@andrewfairfield:~$ cd / arc@andrewfairfield:/$ hello Hello, world! arc@andrewfairfield:/$ [ This is in 20.04, not 22.04 ] Yay! that is the first time I have seen a snap actually work with my normal user account. This feels like significant progress in working out what is going on! Of course firefox needs access to the home directory to load the profile and store downloads. Is the whole process run as some other user (a la sudo) or is there just some starting stub running as some other user doing something that returns to the actual user after doing something that thinks it needs access to the current directory but could get by without it? Actually, I can sort of answer that - I tried running "musescore" as a snap, starting from / It successfully ran. I tried saving something, and it sort of did... but in a new, empty "home" directory in a /home/arc/snap/musescore/216/ that the save file dialog went to when I pressed the home button. Is this normal behaviour for a snap? Regardless of the inconvenience of the subdirectory, that is running over nfs successfully. I can close Musescore and load it again. But not with cwd=/home/arc. So that is fairly strong evidence supporting your idea that it is the same root cause as https://bugs.launchpad.net/bugs/1973321 . I will add a comment there. Thanks for the insight Alberto! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784774 Title: snapd is not autofs aware and fails with nfs home dir To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1784774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973598] Re: mtd-self-test failure on arm64 (mtdram module)
** Patch added: "1-disable-mtd-self-test.debdiff" https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1973598/+attachment/5590042/+files/1-disable-mtd-self-test.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973598 Title: mtd-self-test failure on arm64 (mtdram module) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1973598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969432] Re: 5.17 kernel won't load mok, so it refused to load dkms signed by mok
** Description changed: + lp:1972802 + Steps to reproduce: 1. enroll mok, and use the mok to sign dkms 2. make sure secure boot is on, and boots with kernel 3. load the kernel by either modprobe or insmod. Expected: the kernel module can be loaded. Actually: the kernel module can't be loaded. Failed kernel: 5.17.0-1003-oem Passed kernel: 5.15.0-25-generic With 5.17 kernel, using command "dmesg | grep 509", I can't see the mok key. With 5.15 kernel above, I can see the mok key is loaded like: [0.896168] integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) [0.896283] integrity: Loaded X.509 cert 'ubuntu Secure Boot Module Signature key: 670bc7d76f65d9cfc786f5501de6af89bf3973e7' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969432 Title: 5.17 kernel won't load mok, so it refused to load dkms signed by mok To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973430] Re: backintime is broken with python 3.10
*** This bug is a duplicate of bug 1970090 *** https://bugs.launchpad.net/bugs/1970090 ** This bug has been marked a duplicate of bug 1970090 Backintime not launching because of python error -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973430 Title: backintime is broken with python 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/1973430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778082] Re: Language Support Is Incomplete dialog must show package list to install
This is still an issue in Kubuntu 22.04 LTS. The QApt Batch Installer will pop up a notification letting you know that additional packages are required, but won't tell you what they are. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778082 Title: Language Support Is Incomplete dialog must show package list to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-runtime/+bug/1778082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973604] Re: [nvidia340] display hangs 10s on boot with nvidia-340
** Package changed: gdm3 (Ubuntu) => ubuntu-drivers-common (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973604 Title: [nvidia340] display hangs 10s on boot with nvidia-340 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1973604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973382] Re: autopkgtests failures due to debhelper 13.6 changes
Sorry, I'd mis-interpreted this bug! I'd gone digging through the
history of debconf and couldn't understand how dpkg-reconfigure was only
restarting things just *now*, but hadn't correctly understood that your
bug was complaining the service was stopped, but *not started* again.
So, my apologies: must read more carefully!
Anyway, to the problem as described: checking d/rules in postgresql-
common we find:
# do not (re)start postgresql.service on postgresql-common install/upgrades
override_dh_installinit:
dh_installinit -ppostgresql-common --name=postgresql -u'defaults 19 21'
--no-start
override_dh_installsystemd:
dh_installsystemd --no-start
This strongly suggests you *do* want to add --no-stop-on-upgrade because
the comment indicates a mis-understanding of --no-start. The --no-start
option tells dh_install{init,systemd} that you don't want the service
automatically started upon installation but in the absence of --no-stop-
on-upgrade it *will* still attempt to restart it on upgrades (this isn't
terribly well documented in the dh_installsystemd manpage -- I should
correct that).
There is one other way you could go about solving this, but it's
horribly subtle. The reason preinst is stopping postgres is that --no-
start implies --no-restart-after-upgrade, the (terribly named) option
that specifies a service *should* be restarted but by stopping it before
and upgrade and starting it again afterward (as opposed to --restart-
after-upgrade, the usual default which simply runs a restart after an
upgrade). Quite *why* --no-start implies --no-restart-after-upgrade I've
no idea; I did note it at the time I was hacking on debhelper and it's
one of those things that, given free reign, I'd excise. However, as
mentioned before I tried to be extremely conservative with my changes to
debhelper (and dpkg-reconfigure).
Anyway, the other way you could solve this would be by specifying --no-
start and --restart-after-upgrade. This would mean preinst doesn't try
to stop the service, but postinst will "try-restart" the service (which
means restart if it's already running, but don't start it if it isn't).
However, that would run contrary to the comment in d/rules so I suspect
it's not what you want to do.
Hope that's not too confusing! Do let me know if there's anything that
needs clarification above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973382
Title:
autopkgtests failures due to debhelper 13.6 changes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1973382/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677781] Re: Missing dep8 tests
Sent new dep8 tests to debian, and then synced the package back into ubuntu: https://launchpad.net/ubuntu/+source/cyrus-sasl2/2.1.28+dfsg-5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677781 Title: Missing dep8 tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1677781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970779] Re: Multiple vulnerabilities in Focal and Impish
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-9952 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-9983 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-9862 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-9893 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-9894 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-9895 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-9915 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-9925 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1970779 Title: Multiple vulnerabilities in Focal and Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpewebkit/+bug/1970779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971272] Re: Merge cyrus-sasl2 from Debian unstable for kinetic
This became a sync, after debian accepted my DEP8 tests. https://launchpad.net/ubuntu/+source/cyrus-sasl2/2.1.28+dfsg-5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971272 Title: Merge cyrus-sasl2 from Debian unstable for kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1971272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956264] Re: Cannot set offload options to false
Hey, thank you for providing a focal.debdiff. To get this change landed in Focal, we need to follow the full SRU process, though. Could you please file an SRU template, according to https://wiki.ubuntu.com/StableReleaseUpdates ? Also, a few remarks about the debdiff: 1/ The version number for Focal should be 0.104-0ubuntu2~20.04.2, according to https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging (as this is a backport on top of -0ubuntu2, not -0ubuntu3) 2/ I'd like to reduce the backport to just the relevant changes, not pulling in the whole ABI validation logic, similar to what I've prepared for Kinetic: https://git.launchpad.net/~ubuntu-core- dev/netplan/+git/ubuntu/commit/?id=dc3b335e9a3ba0d22f7a62c52818e1c3ed2e6a3c 3/ We need to land this change in Kinetic (I've uploaded it recently), Jammy, Impish and then Focal, going top down and doing an SRU for each of them. Could you please file a git Merge-Proposal for each of them (instead of providing many debdiffs) on launchpad against those branches? https://git.launchpad.net/~ubuntu-core-dev/netplan/+git/ubuntu/log/?h=ubuntu/jammy https://git.launchpad.net/~ubuntu-core-dev/netplan/+git/ubuntu/log/?h=ubuntu/impish https://git.launchpad.net/~ubuntu-core-dev/netplan/+git/ubuntu/log/?h=ubuntu/focal ** Changed in: netplan.io (Ubuntu Kinetic) Status: New => In Progress ** Changed in: netplan.io (Ubuntu Kinetic) Assignee: (unassigned) => Lukas Märdian (slyon) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956264 Title: Cannot set offload options to false To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1956264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956191] Re: Sendmail 8.17.1 update request, fixes FTBFS with openssl 3
It's in kinetic proposed already, and built: https://launchpad.net/ubuntu/+source/sendmail/8.17.1-2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956191 Title: Sendmail 8.17.1 update request, fixes FTBFS with openssl 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sendmail/+bug/1956191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973601] Re: Please merge libsigsegv 2.14 (main) from Debian unstable (main)
Please find attached the debdiff between the old ubuntu version and the new one. ** Patch added: "debdiff_oldubuntu_newubuntu.debdiff" https://bugs.launchpad.net/ubuntu/+source/libsigsegv/+bug/1973601/+attachment/5590041/+files/debdiff_oldubuntu_newubuntu.debdiff ** Tags added: fr-2387 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973601 Title: Please merge libsigsegv 2.14 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsigsegv/+bug/1973601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973601] Re: Please merge libsigsegv 2.14 (main) from Debian unstable (main)
Please find attached the debdiff between debian package and the new ubuntu one. ** Patch added: "debdiff_debian_ubuntu.debdiff" https://bugs.launchpad.net/ubuntu/+source/libsigsegv/+bug/1973601/+attachment/5590040/+files/debdiff_debian_ubuntu.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973601 Title: Please merge libsigsegv 2.14 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsigsegv/+bug/1973601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747499] Re: 98-reboot-required and Interaction with livepatch
Trying to validate this upload but unattended-upgrades failed to build
with:
Applying pinning: PkgFilePin(id=0, priority=-32768)
Applying pin -32768 to package_file: >/test/root.unused-deps/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_lucid-updates_main_binary-amd64_Packages'
a=lucid-updates,c=main,v=10.04,o=Ubuntu,l=Ubuntu arch='amd64'
site='archive.ubuntu.com' IndexType='Debian Package Index' Size=106 ID:0>
Using
(^linux-image-[1-9][0-9]*\.[0-9]+\.[0-9]+-[0-9]+(-.+)?$|^.*-modules-[1-9][0-9]*\.[0-9]+\.[0-9]+-[0-9]+(-.+)?$|^linux-headers-[1-9][0-9]*\.[0-9]+\.[0-9]+-[0-9]+(-.+)?$)
regexp to find kernel packages
Using
(^linux-image-5\.4\.0\-109\-generic$|^linux-image-5\.4\.0\-109$|^.*-modules-5\.4\.0\-109\-generic$|^.*-modules-5\.4\.0\-109$|^linux-headers-5\.4\.0\-109\-generic$|^linux-headers-5\.4\.0\-109$)
regexp to find running kernel packages
{'old-unused-dependency', 'any-old-unused-modules'}
Keeping auto-removable test-package-dependency package(s) because it would also
remove the following packages which should be kept in this step:
old-unused-dependency
The following packages are marked for installation or upgrade which is not
allowed when performing autoremovals: forbidden-dependency
.
==
FAIL: test_remove_unused_dependencies_new_unused_only
(__main__.TestRemoveUnused)
--
Traceback (most recent call last):
File "./test_remove_unused.py", line 164, in
test_remove_unused_dependencies_new_unused_only
self.assertTrue(needle_kernel_good in haystack,
AssertionError: False is not true : Can not find 'Removing unused kernel
packages: linux-image-4.05.0-1021-kvm
' in '2022-05-10 20:56:21,336 INFO Starting unattended upgrades script
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747499
Title:
98-reboot-required and Interaction with livepatch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1747499/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
Thanks, just opened a separate bug: [nvidia340] display hangs 10s on boot with nvidia-340 https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1973604 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958488 Title: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958629] Re: Deprecation warnings about Proc.new
Sure, thanks for the bug report. However, this is just a deprecation warning and it does not crash AFAIU, so I am setting the importance to Low and will add it to the server team todo list. ** Also affects: ruby-faraday (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: ruby-faraday (Ubuntu) Status: Confirmed => Fix Released ** Changed in: ruby-faraday (Ubuntu Focal) Status: New => Triaged ** Changed in: ruby-faraday (Ubuntu Focal) Importance: Undecided => Low ** Tags added: server-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958629 Title: Deprecation warnings about Proc.new To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-faraday/+bug/1958629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
