[Bug 2056730] Re: noble-daily (20240310) cannot be installed offline
** Changed in: subiquity 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/2056730 Title: noble-daily (20240310) cannot be installed offline To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/2056730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062515] Re: ubuntu 24.04 update-manager
looks like it's solved -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062515 Title: ubuntu 24.04 update-manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2062515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062435] Re: ubuntu 24.04 partial upgrade failes with python exception
yep fix worked -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062435 Title: ubuntu 24.04 partial upgrade failes with python exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2062435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062515] [NEW] ubuntu 24.04 update-manager
Public bug reported: not sure if this is different from my other bug but the automatic error reporter is trying to do this every time I use update manager now 1) $ lsb_release -rd No LSB modules are available. Description:Ubuntu Noble Numbat (development branch) Release:24.04 2) $ apt-cache policy update-manager update-manager: Installed: 1:24.04.6 Candidate: 1:24.04.6 Version table: *** 1:24.04.6 500 500 http://au.archive.ubuntu.com/ubuntu noble/main amd64 Packages 500 http://au.archive.ubuntu.com/ubuntu noble/main i386 Packages 100 /var/lib/dpkg/status 3) expected update-manager to do it's thing 4) I get it wanting to do this as well ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: update-manager 1:24.04.6 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.1-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 17:47:11 2024 InstallationDate: Installed on 2024-04-09 (10 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240408) PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble 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/2062515 Title: ubuntu 24.04 update-manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2062515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062435] Re: ubuntu 24.04 partial upgrade failes with python exception
seams I grabbed an extra the ubuntu-bug call on the end -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062435 Title: ubuntu 24.04 partial upgrade failes with python exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2062435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062435] [NEW] ubuntu 24.04 partial upgrade failes with python exception
Public bug reported: 1) lsb_release -rd No LSB modules are available. Description:Ubuntu Noble Numbat (development branch) Release:24.04 2) apt-cache policy update-manager update-manager: Installed: 1:24.04.6 Candidate: 1:24.04.6 Version table: *** 1:24.04.6 500 500 http://au.archive.ubuntu.com/ubuntu noble/main amd64 Packages 500 http://au.archive.ubuntu.com/ubuntu noble/main i386 Packages 100 /var/lib/dpkg/status 3) expected it to do a partial upgrade on clicking the "partial upgrade" button 4) crashes with the following messages $ sudo update-manager (update-manager:497814): dconf-WARNING **: 10:29:23.723: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory) (update-manager:497814): dconf-WARNING **: 10:29:23.723: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory) (update-manager:497814): libunity-CRITICAL **: 10:29:23.731: file unity- launcher.c: line 1638: unexpected error: Failed to execute child process “dbus-launch” (No such file or directory) (g-exec-error-quark, 8) (update-manager:497814): libunity-CRITICAL **: 10:29:23.731: unity_launcher_entry_dbus_impl_construct: assertion 'conn != NULL' failed (update-manager:497814): libunity-CRITICAL **: 10:29:23.735: unity-inspector.vala:96: Unable to connect to session bus: Failed to execute child process “dbus-launch” (No such file or directory) warning: could not initiate dbus /usr/lib/python3/dist-packages/uaclient/apt.py:288: Warning: W:Unable to read /var/lib/ubuntu-advantage/apt-esm/etc/apt/apt.conf.d/ - DirectoryExists (2: No such file or directory) apt_pkg.init() /usr/lib/python3/dist-packages/uaclient/apt.py:270: Warning: W:Unable to read /var/lib/ubuntu-advantage/apt-esm/etc/apt/preferences.d/ - DirectoryExists (2: No such file or directory) apt_pkg.init_system() ERROR:root:not handled exception: Traceback (most recent call last): File "/usr/lib/ubuntu-release-upgrader/do-partial-upgrade", line 114, in controller.doPartialUpgrade() File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeController.py", line 2609, in doPartialUpgrade self.prepare() File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeController.py", line 465, in prepare if not self._pythonSymlinkCheck(): ^^ File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeController.py", line 415, in _pythonSymlinkCheck config.readfp(f) ^ AttributeError: 'ConfigParser' object has no attribute 'readfp'. Did you mean: 'read'? Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeViewGtk3.py", line 540, in _handleException apport_crash(type, value, tb) File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeApport.py", line 57, in apport_crash apport_excepthook(type, value, tb) TypeError: apport_excepthook() missing 1 required positional argument: 'exc_tb' Original exception was: Traceback (most recent call last): File "/usr/lib/ubuntu-release-upgrader/do-partial-upgrade", line 114, in controller.doPartialUpgrade() File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeController.py", line 2609, in doPartialUpgrade self.prepare() File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeController.py", line 465, in prepare if not self._pythonSymlinkCheck(): ^^ File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeController.py", line 415, in _pythonSymlinkCheck config.readfp(f) ^ AttributeError: 'ConfigParser' object has no attribute 'readfp'. Did you mean: 'read'? [grizzlysmit:~] 34s 1 $ ubuntu-bug update-manager REDACTED config part /etc/cloud/cloud.cfg.d/99-installer.cfg, insufficient permissions REDACTED config part /etc/cloud/cloud.cfg.d/90-installer-network.cfg, insufficient permissions Gdk-Message: 10:31:25.104: Unable to load col-resize from the cursor theme ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: update-manager 1:24.04.6 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 10:30:28 2024 InstallationDate: Installed on 2024-04-09 (10 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240408) PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble 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/2062435 Title: ubuntu 24.04 partial upgrade
[Bug 2059978] Re: linux-aws-5.15 ADT test MISS because it's unable to find package
@paride: Yes, I've seen this with other kernels, mostly with the nvidia drivers. I think all of the runs of the following since March 20 show this problem: https://autopkgtest.ubuntu.com/packages/n/nvidia-graphics-drivers-510-server/focal/amd64 https://autopkgtest.ubuntu.com/packages/n/nvidia-graphics-drivers-515/focal/amd64 https://autopkgtest.ubuntu.com/packages/n/nvidia-graphics-drivers-460-server/focal/amd64 As mentioned in MM, all of these started failing between March 11 and March 20. All of these drivers are transitional packages (they don't really do anything other then depend on the next driver in the series to keep users on a supported driver), but I don't know if this is of interest to the problem as I've seen this with other packages too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059978 Title: linux-aws-5.15 ADT test MISS because it's unable to find package To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2059978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055771] [NEW] when installing ubuntu
Public bug reported: fatal error ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.20 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470.2 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 2 14:44:58 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) 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: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-22.04.20 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055771 Title: when installing ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/2055771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2044973] Re: ubuntu-drivers install the wrong version of Nvidia driver on some machines
@Kevin, Thank you for testing again. This latest output indicates something may not be correct in your test environment. This line: WARNING:root:_pkg_get_support nvidia-driver-525: package has invalid Support PBheader, cannot determine support level is indicating that the driver packages are providing a "PB" in the support field, but ubuntu-drivers doesn't know how to handle this. Support for PB drivers was added in version 1:0.9.0~0.20.04.7, which is the latest version in focal-updates (see lp:1964747 for details). This indicates this particular test was run with an even older version, but that doesn't make sense if you've also updated to 1:0.9.0~0.20.04.8. I really can only speculate what is going on here. I did run an experiment on a device attached to testflinger, 202007-28059. This is an HP ZBook Studio G7 with a TU117GLM [Quadro T2000 Mobile / Max-Q]. This appears to match the devices used in the original bug description. I first verified that the problem exists with the version of the package in focal-updates: ubuntu@hp-zbook-studio-g7-c28059:~$ dpkg -l|grep ubuntu-drivers ii ubuntu-drivers-common 1:0.9.0~0.20.04.7 amd64Detect and install additional Ubuntu driver packages ubuntu@hp-zbook-studio-g7-c28059:~$ sudo ubuntu-drivers devices ERROR:root:could not open aplay -l Traceback (most recent call last): File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect aplay = subprocess.Popen( File "/usr/lib/python3.8/subprocess.py", line 858, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'aplay' == /sys/devices/pci:00/:00:1f.4 == modalias : pci:v8086d06A3sv103Csd8736bc0Csc05i00 vendor : Intel Corporation driver : oem-stella.cmit-meowth-meta - distro free == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd1FB8sv103Csd8736bc03sc00i00 vendor : NVIDIA Corporation model: TU117GLM [Quadro T2000 Mobile / Max-Q] driver : nvidia-driver-535-server - distro non-free driver : nvidia-driver-535-server-open - distro non-free recommended driver : nvidia-driver-535 - distro non-free driver : nvidia-driver-525-open - distro non-free driver : nvidia-driver-535-open - distro non-free driver : nvidia-driver-450-server - distro non-free driver : nvidia-driver-470 - distro non-free driver : nvidia-driver-418-server - distro non-free driver : nvidia-driver-525 - distro non-free driver : nvidia-driver-470-server - distro non-free driver : nvidia-driver-525-server - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin Then updated to the package from proposed: ubuntu@hp-zbook-studio-g7-c28059:~$ dpkg -l|grep ubuntu-drivers ii ubuntu-drivers-common 1:0.9.0~0.20.04.8 amd64Detect and install additional Ubuntu driver packages ubuntu@hp-zbook-studio-g7-c28059:~$ sudo ubuntu-drivers devices ERROR:root:could not open aplay -l Traceback (most recent call last): File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect aplay = subprocess.Popen( File "/usr/lib/python3.8/subprocess.py", line 858, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'aplay' == /sys/devices/pci:00/:00:1f.4 == modalias : pci:v8086d06A3sv103Csd8736bc0Csc05i00 vendor : Intel Corporation driver : oem-stella.cmit-meowth-meta - distro free == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd1FB8sv103Csd8736bc03sc00i00 vendor : NVIDIA Corporation model: TU117GLM [Quadro T2000 Mobile / Max-Q] driver : nvidia-driver-535-open - distro non-free driver : nvidia-driver-525-open - distro non-free driver : nvidia-driver-450-server - distro non-free driver : nvidia-driver-535-server-open - distro non-free driver : nvidia-driver-535 - distro non-free recommended driver : nvidia-driver-418-server - distro non-free driver : nvidia-driver-470-server - distro non-free driver : nvidia-driver-535-server - distro non-free driver : nvidia-driver-525-server - distro non-free driver : nvidia-driver-470 - distro non-free driver : nvidia-driver-525 - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin Based on this, it is now choosing the expected `nvidia-driver-535` driver. I can look further, but I'm going to need to triage the problem on your test device or somewhere you can reproduced this. -- You received this bug notification because you are a member of
[Bug 2052640] Re: New NVIDIA release 470.239.06
I have done my typical CUDA based testing with this package using the generic, nvidia and gcp kernels using bionic, focal, jammy and mantic (amd64 only so far). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052640 Title: New NVIDIA release 470.239.06 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-470/+bug/2052640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054571] Re: New NVIDIA release 535.161.07
I have done my typical CUDA based testing with this package using the generic, nvidia and gcp kernels using bionic, focal, jammy and mantic (amd64 only so far). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054571 Title: New NVIDIA release 535.161.07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2054571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2044973] Re: ubuntu-drivers install the wrong version of Nvidia driver on some machines
@kevinyew, @shanew, It looks like you are hitting this on focal. Can you please confirm? If so, can you please retest with the latest ubuntu-drivers from focal- proposed? This should be version 1:0.9.0~0.20.04.8. This appears to fix a bug (discussed in https://bugs.launchpad.net/ubuntu/+source/nvidia- graphics-drivers-515/+bug/1988836) which caused the -open drivers to be preferred. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2044973 Title: ubuntu-drivers install the wrong version of Nvidia driver on some machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2044973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Retention period for autopkgtest test logs
On Mon, Sep 25, 2023 at 1:18 PM Bryce Harrington < bryce.harring...@canonical.com> wrote: > On Mon, Sep 25, 2023 at 10:23:36AM -0700, Brian Murray wrote: > > Currently test results and log files for autopkgtest runs are kept until > > the release for which the test was run reaches its End of Life. This is > > also true for autopkgtest runs for packages in PPAs and the Ubuntu QA > > team thinks we should not be keeping these for such a long period of > > time. > > > > We plan to automatically remove test results for PPAs which ran more > > than 8 weeks ago. Does 8 weeks seem like too short of a period to > > anybody? > > It does feel a bit short; prior results can sometimes be interesting for > comparison purposes, although even that value diminishes quickly over > time. Is there a strong reason to favor 8 weeks vs. say 26 weeks > (i.e. our development cycle length)? > > Bryce > I would also recommend a longer period, at least 12 or 16 weeks. The selfish reasoning is that this would give us at least 2 kernel SRU cycles worth of (hopefully) passing logs to use when triaging a failure. Francis -- Francis Ginther Canonical - Kernel -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
[Bug 1973034] Re: linux generic fails to boot on azure arm64 instance types
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973034 Title: linux generic fails to boot on azure arm64 instance types To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973034] Re: linux generic fails to boot on azure arm64 instance types
Artifacts were collected from a new VM running focal/linux-azure just prior to rebooting to linux-generic (which gets stuck at initramfs). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973034 Title: linux generic fails to boot on azure arm64 instance types To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973034] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1973034/+attachment/5588654/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973034 Title: linux generic fails to boot on azure arm64 instance types To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973034] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1973034/+attachment/5588652/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973034 Title: linux generic fails to boot on azure arm64 instance types To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973034] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1973034/+attachment/5588653/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973034 Title: linux generic fails to boot on azure arm64 instance types To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973034] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1973034/+attachment/5588651/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973034 Title: linux generic fails to boot on azure arm64 instance types To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973034] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1973034/+attachment/5588649/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973034 Title: linux generic fails to boot on azure arm64 instance types To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973034] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1973034/+attachment/5588650/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973034 Title: linux generic fails to boot on azure arm64 instance types To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973034] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1973034/+attachment/5588648/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973034 Title: linux generic fails to boot on azure arm64 instance types To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973034] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1973034/+attachment/5588647/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973034 Title: linux generic fails to boot on azure arm64 instance types To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973034] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1973034/+attachment/5588646/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973034 Title: linux generic fails to boot on azure arm64 instance types To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973034] Re: linux generic fails to boot on azure arm64 instance types
apport information ** Tags added: apport-collected focal uec-images ** Description changed: Azure now has arm64 instances in a preview, for example Standard_D2pds_v5. These work with the b/linux-azure and f/linux-azure kernels, but fail to boot with linux-generic. Looks like a storage device issue (from serial console): Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [4.651830] Btrfs loaded, crc32c=crc32c-generic [4.651830] Btrfs loaded, crc32c=crc32c-generic Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... mdadm: No devices listed in conf file were found. done. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: error opening /dev/md?*: No such file or directory mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. done. Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! UUID=b9c04583-2c65-4891-aa8e-a494eb94fd14 does not exist. Dropping to a shell! + --- + ProblemType: Bug + AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu27.23 + Architecture: arm64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lspci-vt: + -+-[3c75:00]---02.0 Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function] + \-[:00]- + Lsusb: Error: command ['lsusb'] failed with exit code 1: + Lsusb-t: + + Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: + MachineType: Microsoft Corporation Virtual Machine + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=screen + PATH=(custom, no user) + LANG=C.UTF-8 + SHELL=/bin/bash + ProcFB: 0 hyperv_fb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-1023-azure root=PARTUUID=379f8683-bd7e-48a0-8460-5c7f68b4b091 ro console=tty1 console=ttyAMA0 earlycon=pl011,0xeffec000 initcall_blacklist=arm_pmu_acpi_init panic=-1 + ProcVersionSignature: Ubuntu 5.13.0-1023.27~20.04.1-azure 5.13.19 + RelatedPackageVersions: + linux-restricted-modules-5.13.0-1023-azure N/A + linux-backports-modules-5.13.0-1023-azure N/A + linux-firmware 1.187.30 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: focal uec-images + Uname: Linux 5.13.0-1023-azure aarch64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 02/07/2022 + dmi.bios.release: 4.1 + dmi.bios.vendor: Microsoft Corporation + dmi.bios.version: Hyper-V UEFI Release v4.1 + dmi.board.asset.tag: None + dmi.board.name: Virtual Machine + dmi.board.vendor: Microsoft Corporation + dmi.board.version: Hyper-V UEFI Release v4.1 + dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 + dmi.chassis.type: 3 + dmi.chassis.vendor: Microsoft Corporation + dmi.chassis.version: Hyper-V UEFI Release v4.1 + dmi.modalias:
[Bug 1973034] [NEW] linux generic fails to boot on azure arm64 instance types
Public bug reported: Azure now has arm64 instances in a preview, for example Standard_D2pds_v5. These work with the b/linux-azure and f/linux-azure kernels, but fail to boot with linux-generic. Looks like a storage device issue (from serial console): Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [4.651830] Btrfs loaded, crc32c=crc32c-generic [4.651830] Btrfs loaded, crc32c=crc32c-generic Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... mdadm: No devices listed in conf file were found. done. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: error opening /dev/md?*: No such file or directory mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. done. Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! UUID=b9c04583-2c65-4891-aa8e-a494eb94fd14 does not exist. Dropping to a shell! ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973034 Title: linux generic fails to boot on azure arm64 instance types To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971679] [NEW] crash on install
Public bug reported: When installing, i don't knwo when exactly 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: Thu May 5 11:10: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=fr_FR.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.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/1971679 Title: crash on install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1971679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968062] Re: jammy/linux-aws hibernation timeout on xen instances
This screenshot was taken a few minutes after the resume attempt. These ssm-amazon-agent messages repeat every 120 seconds with a new set. But this is all the progress we see from either the screenshot or the serial console. There are no new memory consumption messages indicating that the resume was complete. ** Attachment added: "Third screenshot after resume initiated" https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1968062/+attachment/5577703/+files/post-hibernate.16.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968062 Title: jammy/linux-aws hibernation timeout on xen instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1968062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968062] Re: jammy/linux-aws hibernation timeout on xen instances
** Attachment added: "Last screenshot before hibernation" https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1968062/+attachment/5577676/+files/pre-hibernation.04.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968062 Title: jammy/linux-aws hibernation timeout on xen instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1968062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968062] [NEW] jammy/linux-aws hibernation timeout on xen instances
Public bug reported: Hibernation testing of jammy/linux-aws 5.15.0-1003-aws is failing on all xen instance types (c3/c4/i3/m3/m4/r3/r4/t2). The failure happens while attempting to resume from the first attempt to hibernate. Testing on nitro instances types (c5/m5/r5/t3) all pass. After the resume, the system is inaccessible via ssh. The console screenshot does change, but the console log obtained from `aws ec2 get- console-output` does not. ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Attachment added: "serial console log" https://bugs.launchpad.net/bugs/1968062/+attachment/5577675/+files/aws-jammy-all-c3.8xlarge-9-1.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968062 Title: jammy/linux-aws hibernation timeout on xen instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1968062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968062] Re: jammy/linux-aws hibernation timeout on xen instances
In this screenshot, it appears the system has resumed as the login screen is shown along with the messages from the hibernation memory consumption utility. The first memory message was generated prior to the hibernation (matches the message from the pre-hibernation image). The second message could have been generated before the hibernation or after the resume (there isn't enough data to know for sure). ** Attachment added: "Second screenshot after resume initiated" https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1968062/+attachment/5577701/+files/post-hibernate.12.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968062 Title: jammy/linux-aws hibernation timeout on xen instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1968062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968062] Re: jammy/linux-aws hibernation timeout on xen instances
** Attachment added: "First screenshot after resume initiated" https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1968062/+attachment/5577677/+files/post-hibernate.01.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968062 Title: jammy/linux-aws hibernation timeout on xen instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1968062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964622] Re: MariaDB limits to 1000 parameters
I suspect this might be related to `in_predicate_conversion_threshold`?
While I have fixed this elsewhere by using
foreach (array_chunk($ids, 900) as $chunk_ids) {
}
I've also been able to use the following as a temporary work around:
SET in_predicate_conversion_threshold=2000;
I assume this config variable is used to protect against something, so
I'm hesitant to apply it globally.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964622
Title:
MariaDB limits to 1000 parameters
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1964622/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964622] [NEW] MariaDB limits to 1000 parameters
Public bug reported:
With the recent release of MariaDB `1:10.3.34-0ubuntu0.20.04.1`, or
maybe php7.4-mysql `7.4.3-4ubuntu2.9`, something changed so the number
of parameters used with `IN()` is now being limited to 1000.
I believe the number of parameters used to only be limited by the
`max_allowed_packet` value, where I was able to specify 3,000+ integers.
This is not noted in the MariaDB documentation, but is in MySQL:
https://mariadb.com/kb/en/in/
https://dev.mysql.com/doc/refman/8.0/en/comparison-operators.html#operator_in
The `$statement->errno` returns the integer 2014, and
`$statement->error` does include "Commands out of sync; you can't run
this command now", which matches later versions of MariaDB, so I think
part of this change has been back-ported somehow (cannot see in either
patch, but I can't understand all that has changed).
For a test script, using PHP (so I can easily use parameters)... I can
do 2 x `IN()` with 999 parameters each, but as soon as there are 1000
parameters in either or both, it fails.
prepare('SELECT id FROM my_table WHERE id IN (' . $params .
') AND id IN (' . $params . ')');
$statement->bind_param($types, ...$values);
$statement->execute();
$result = $statement->get_result();
var_dump($db->error);
var_dump($statement->error);
var_dump($statement->errno);
var_dump($result);
while ($row = mysqli_fetch_assoc($result)) {
print_r($row);
}
?>
Running this without parameters is fine, same with the `mysql` cli:
SELECT id FROM my_table WHERE id IN (
1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,
1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,
1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,
1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,
1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,
1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,
1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,
1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,
1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,
1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
);
** Affects: mariadb-10.3 (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- MariaDB limits to 1000 parameters, but no error
+ MariaDB limits to 1000 parameters
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964622
Title:
MariaDB limits to 1000 parameters
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1964622/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873093] Re: Gnome-terminal tab bar steals keyboard focus
There is one important step for reproducing this bug, not only in gnome-terminal, but also in nautilus and gedit: * open multiple tabs * !!! reorder one of the tabs !!! * leave pointer hovering over one of the tabs * observe tooltip appearing, and cursor changing to reflect loss of focus in the tab window * observe the next keypress not going to the tab window, but seemingly either the tooltip or the tab widget (not sure which); after this, focus returns to the tab window for subsequent input. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873093 Title: Gnome-terminal tab bar steals keyboard focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1873093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961800] Re: Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal)
Moving this to xmltodict as I've been able to parse multiple xml files through just python3's xml.parsers.expat without error, but none of them through xmltodict. ** Also affects: python-xmltodict (Ubuntu) Importance: Undecided Status: New ** Changed in: python-xmltodict (Ubuntu) Status: New => Confirmed ** Changed in: expat (Ubuntu) Status: Confirmed => Invalid ** Summary changed: - Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal) + Seeing out of memory errors after libexpat1 upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961800 Title: Seeing out of memory errors after libexpat1 upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1961800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961800] Re: Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal)
This may be an issue with the python3 xmltodict module. Further testing indicates that parsing a file with just xml.parsers.expat is working just fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961800 Title: Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1961800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961800] Re: Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4
Attached is an example config file and python script which demonstrates the parsing error. This was reproduced on focal with: $ apt-cache policy libexpat1 libexpat1: Installed: 2.2.9-1ubuntu0.2 Candidate: 2.2.9-1ubuntu0.2 Version table: *** 2.2.9-1ubuntu0.2 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.2.9-1build1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages This example worked with 2.2.9-1build1 but not 2.2.9-1ubuntu0.2. To run the example: $ ./parser_example.py ./sample-config.xml The sample-config.xml was generated by jenkins (version 2.303.2) of a freestyle project with only the job name and description set. ** Attachment added: "sample-config-and-parser.tgz" https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1961800/+attachment/5562745/+files/sample-config-and-parser.tgz ** Summary changed: - Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4 + Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961800 Title: Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1961800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961800] Re: Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4
I was able to workaround the issue by downgrading to the release version of the package: $ sudo apt-get install libexpat1=2.2.5-3 libexpat1-dev=2.2.5-3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961800 Title: Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1961800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961800] [NEW] Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4
Public bug reported: I started seeing errors parsing XML files today (Feb 22, 2022) after my system was updated to 2.2.5-3ubuntu0.4. This is on a bionic server. The parsing is being done by python3's xmltodict module, which uses python3 expat as the actual parser. This is the error it raises: xml.parsers.expat.ExpatError: out of memory: line 1, column 0 So far this is happening on multiple xml files, although they all come from the same source (these are jenkins config.xml files). I'm working on coming up with a minimal test case which I'll provide once I have it cleaned up of any private data. [System info] $ lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 $ apt-cache policy libexpat1 libexpat1: Installed: 2.2.5-3ubuntu0.4 Candidate: 2.2.5-3ubuntu0.4 Version table: *** 2.2.5-3ubuntu0.4 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.2.5-3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: expat (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/1961800 Title: Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1961800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961356] Re: jammy fails to install due to "KeyError: 'LOG-SEC'"
*** This bug is a duplicate of bug 1956613 *** https://bugs.launchpad.net/bugs/1956613 This is a dup. After upgrading the maas server to 3.1, the issue is resolved. ** This bug has been marked a duplicate of bug 1956613 Traceback deploying Jammy with MAAS 3.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961356 Title: jammy fails to install due to "KeyError: 'LOG-SEC'" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1961356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961356] [NEW] jammy fails to install due to "KeyError: 'LOG-SEC'"
Public bug reported:
Using maas to install jammy to an nvidia dgx-1. Curtin fails with the
following log:
curtin: Installation started. (21.2-0ubuntu1~20.04.1)
third party drivers not installed or necessary.
start: cmd-install/stage-partitioning/builtin/cmd-block-meta: curtin command
block-meta
get_path_to_storage_volume for volume sda({'grub_device': True, 'id': 'sda',
'model': 'MRROMB', 'name': 'sda', 'ptable': 'gpt', 'serial':
'6001636002696668214e5fab86021ad8', 'type': 'disk', 'wipe': 'superblock'})
Processing serial 6001636002696668214e5fab86021ad8 via udev to
6001636002696668214e5fab86021ad8
lookup_disks found: ['wwn-0x6001636002696668214e5fab86021ad8',
'scsi-36001636002696668214e5fab86021ad8',
'scsi-36001636002696668214e5fab86021ad8-part1',
'wwn-0x6001636002696668214e5fab86021ad8-part1',
'wwn-0x6001636002696668214e5fab86021ad8-part2',
'scsi-36001636002696668214e5fab86021ad8-part2']
Running command ['udevadm', 'info', '--query=property', '--export', '/dev/sda']
with allowed return codes [0] (capture=True)
/dev/sda is multipath device? False
Running command ['multipath', '-c', '/dev/sda'] with allowed return codes [0]
(capture=True)
/dev/sda is multipath device member? False
block.lookup_disk() returning path /dev/sda
Running command ['partprobe', '/dev/sda'] with allowed return codes [0, 1]
(capture=False)
Running command ['udevadm', 'settle'] with allowed return codes [0]
(capture=False)
TIMED udevadm_settle(): 0.144
devsync happy - path /dev/sda now exists
return volume path /dev/sda
get_path_to_storage_volume for volume sdb({'id': 'sdb', 'model': 'MRROMB',
'name': 'sdb', 'serial': '60016360026966682393bfeb0902038f', 'type': 'disk',
'wipe': 'superblock'})
Processing serial 60016360026966682393bfeb0902038f via udev to
60016360026966682393bfeb0902038f
lookup_disks found: ['wwn-0x60016360026966682393bfeb0902038f',
'scsi-360016360026966682393bfeb0902038f']
Running command ['udevadm', 'info', '--query=property', '--export', '/dev/sdb']
with allowed return codes [0] (capture=True)
/dev/sdb is multipath device? False
Running command ['multipath', '-c', '/dev/sdb'] with allowed return codes [0]
(capture=True)
/dev/sdb is multipath device member? False
block.lookup_disk() returning path /dev/sdb
Running command ['partprobe', '/dev/sdb'] with allowed return codes [0, 1]
(capture=False)
Running command ['udevadm', 'settle'] with allowed return codes [0]
(capture=False)
TIMED udevadm_settle(): 0.056
devsync happy - path /dev/sdb now exists
return volume path /dev/sdb
get_path_to_storage_volume for volume sda-part1({'device': 'sda', 'flag':
'boot', 'id': 'sda-part1', 'name': 'sda-part1', 'number': 1, 'offset':
'4194304B', 'size': '536870912B', 'type': 'partition', 'uuid':
'f906950a-1a1c-4573-ad9c-54675ed9284b', 'wipe': 'superblock'})
get_path_to_storage_volume for volume sda({'grub_device': True, 'id': 'sda',
'model': 'MRROMB', 'name': 'sda', 'ptable': 'gpt', 'serial':
'6001636002696668214e5fab86021ad8', 'type': 'disk', 'wipe': 'superblock'})
Processing serial 6001636002696668214e5fab86021ad8 via udev to
6001636002696668214e5fab86021ad8
lookup_disks found: ['wwn-0x6001636002696668214e5fab86021ad8',
'scsi-36001636002696668214e5fab86021ad8',
'scsi-36001636002696668214e5fab86021ad8-part1',
'wwn-0x6001636002696668214e5fab86021ad8-part2',
'wwn-0x6001636002696668214e5fab86021ad8-part1',
'scsi-36001636002696668214e5fab86021ad8-part2']
Running command ['udevadm', 'info', '--query=property', '--export', '/dev/sda']
with allowed return codes [0] (capture=True)
/dev/sda is multipath device? False
Running command ['multipath', '-c', '/dev/sda'] with allowed return codes [0]
(capture=True)
/dev/sda is multipath device member? False
block.lookup_disk() returning path /dev/sda
Running command ['partprobe', '/dev/sda'] with allowed return codes [0, 1]
(capture=False)
Running command ['udevadm', 'settle'] with allowed return codes [0]
(capture=False)
TIMED udevadm_settle(): 0.140
devsync happy - path /dev/sda now exists
return volume path /dev/sda
Running command ['partprobe', '/dev/sda'] with allowed return codes [0, 1]
(capture=False)
Running command ['udevadm', 'settle'] with allowed return codes [0]
(capture=False)
TIMED udevadm_settle(): 0.140
devsync happy - path /dev/sda now exists
return volume path /dev/sda1
get_path_to_storage_volume for volume sda-part2({'device': 'sda', 'id':
'sda-part2', 'name': 'sda-part2', 'number': 2, 'size': '479014682624B', 'type':
'partition', 'uuid': 'a96eeb67-466e-4652-9b58-2b2d94c91d26', 'wipe':
'superblock'})
get_path_to_storage_volume for volume sda({'grub_device': True, 'id': 'sda',
'model': 'MRROMB', 'name': 'sda', 'ptable': 'gpt', 'serial':
'6001636002696668214e5fab86021ad8', 'type': 'disk', 'wipe': 'superblock'})
Processing serial 6001636002696668214e5fab86021ad8 via udev to
6001636002696668214e5fab86021ad8
lookup_disks found: ['wwn-0x6001636002696668214e5fab86021ad8',
'scsi-36001636002696668214e5fab86021ad8',
[Bug 1960871] [NEW] linux-modules-extra-* fails to install due to dependency on unsigned package
Public bug reported: Several SRU tests are failing the test setup due to failure to install the modules-extra package: * Command: yes "" | DEBIAN_FRONTEND=noninteractive apt-get install --yes --force-yes automake bison build-essential byacc flex git keyutils libacl1-dev libaio- dev libcap-dev libmm-dev libnuma-dev libsctp-dev libselinux1-dev libssl- dev libtirpc-dev pkg-config quota xfslibs-dev xfsprogs gcc linux-modules- extra-4.15.0-1120-aws Exit status: 100 Duration: 0.908210039139 stdout: Reading package lists... Building dependency tree... Reading state information... xfsprogs is already the newest version (4.9.0+nmu1ubuntu2). xfsprogs set to manually installed. git is already the newest version (1:2.17.1-1ubuntu0.9). git set to manually installed. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-modules-extra-4.15.0-1120-aws : Depends: linux-image-unsigned-4.15.0-1120-aws but it is not going to be installed stderr: W: --force-yes is deprecated, use one of the options starting with --allow instead. E: Unable to correct problems, you have held broken packages. ** Affects: linux-aws (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/1960871 Title: linux-modules-extra-* fails to install due to dependency on unsigned package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1960871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960094] Re: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal
This is the result of pulling the lxc test sources from the git repo, but using the lxc from the archive. Currently, the archive has version 4.0.6 and the git repo has been updated to 4.0.12 as an upload is in progress (it's in the unapproved queue as this comment is being written). The result is a mismatch in the tests and the package and test failures. Switching to a different version of the test sources results in a passing test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960094 Title: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960094] Re: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal
I've retested two released kernels that passed the lxc test last cycle: * focal/azure 5.4.0-1068.71 * focal/azure-5-11 5.11.0-1028.31~20.04.1 Both tests now show the same testcase failures where they were passing before. Will start digging into any other changes in the environment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960094 Title: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888992] Re: [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching to front jack after plugging in headphones
Apologies, I was unable to access the machine for testing this until recently, so have been unable to run the test kernel in #21. Revisiting this problem again on the same machine with kernel 5.13.0-27 I still see it as behaving as originally reported, so I expect neither the patch nor proper fix has made its way to the ubuntu kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888992 Title: [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching to front jack after plugging in headphones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905665] Re: dstat --output is broken
Edit /usr/bin/dstat and change lines 547 and 552 Change line 547 to: if isinstance(self.val[name], (tuple, list)): Change line 552 to: elif isinstance(self.val[name], str): For more details, please visit https://serverfault.com/questions/996996/dstat-fails-to-start-trying-to- load-python3s-csv -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905665 Title: dstat --output is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dstat/+bug/1905665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952036] Re: ubuntu_lxc hang on Impish 5.13 with api_test.py test
Restoring the state for python3-lxc as we're using the test from this project. ** Changed in: python3-lxc (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952036 Title: ubuntu_lxc hang on Impish 5.13 with api_test.py test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1952036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952036] Re: ubuntu_lxc hang on Impish 5.13 with api_test.py test
This is expected due to the change in impish to cgroups2. This is really a test issue, not an issue with lxc. ** Changed in: python3-lxc (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/1952036 Title: ubuntu_lxc hang on Impish 5.13 with api_test.py test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1952036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318134] Re: Apache2.so: undefined symbol: modperl_xs_sv2request_rec
same problem on Ubuntu 21.10 found the cause was a miss-configuration of mod_perl not sure of details as I'm not the admin at work -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318134 Title: Apache2.so: undefined symbol: modperl_xs_sv2request_rec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libapreq2/+bug/1318134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928888] Re: test_utils_testsuite from ubuntu_qrt_apparmor linux ADT test failure with linux/5.11.0-18.19
Tests are now passing. ** Changed in: ubuntu-kernel-tests 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/192 Title: test_utils_testsuite from ubuntu_qrt_apparmor linux ADT test failure with linux/5.11.0-18.19 To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944061] [NEW] remote cursor only shows if all settings for it are default
Public bug reported: OK both systems are running Ubuntu 21.04 hirsute hippo $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 21.04 Release:21.04 Codename: hirsute all packages up to date 2).$ apt-cache policy vinagre vinagre: Installed: 3.22.0-8ubuntu2 Candidate: 3.22.0-8ubuntu2 Version table: *** 3.22.0-8ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages 100 /var/lib/dpkg/status both are the same on both ends. 3). expected to see a working cursor 4). nothing until I had the bright idea to change the remote systems cursor back to default yaru default size. I had it on Redglass maximum size like the local box. ** Affects: vinagre (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/1944061 Title: remote cursor only shows if all settings for it are default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/1944061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939673] Re: Update the 470 and the 470-server NVIDIA drivers
Retested with the latest kernels as of Sept 7, 2021. Now able to see that ubuntu-drivers now lists the 470-server driver as an available option. For both Focal and Hirsute, I first had to enable -proposed. For Bionic, it worked with the 4.15.0-156.163 kernel that was released this week. Tested combinations: Release Kernel Bionic 4.15.0-156.163 Focal 5.4.0-85.95 (from focal-proposed) Hirsute 5.11.0-35.37 (from hirsute-proposed) Tested each driver with a cuda workload and use of nvidia-smi to verify the driver functions as expected after install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939673 Title: Update the 470 and the 470-server NVIDIA drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939673] Re: Update the 470 and the 470-server NVIDIA drivers
While the 470-server drivers installed and passed the cuda testing across bionic/focal/hirsute, "ubuntu-drivers" does not identify this as a option for any release. The response I see is: $ sudo ubuntu-drivers list --gpgpu WARNING:root:_pkg_get_support nvidia-driver-390: package has invalid Support Legacyheader, cannot determine support level nvidia-driver-450-server, (kernel modules provided by linux-modules-nvidia-450-server-generic) nvidia-driver-390, (kernel modules provided by linux-modules-nvidia-390-generic) nvidia-driver-418-server, (kernel modules provided by linux-modules-nvidia-418-server-generic) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic) nvidia-driver-460-server, (kernel modules provided by linux-modules-nvidia-460-server-generic) nvidia-driver-460, (kernel modules provided by linux-modules-nvidia-460-generic) This is from a hirsute host running linux-generic using a "Tesla V100-SXM2-16GB". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939673 Title: Update the 470 and the 470-server NVIDIA drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940750] [NEW] public key is not available: NO_PUBKEY FCEF32E745F2C3D5
Public bug reported: Hello Got the error below when running a apt update command: fandre@ubuntu-18-04:~$ sudo apt update [sudo] password for fandre: Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease Hit:2 http://ppa.launchpad.net/webupd8team/java/ubuntu bionic InRelease Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB] Hit:6 https://download.mono-project.com/repo/ubuntu stable-bionic InRelease Hit:7 https://packages.microsoft.com/ubuntu/18.04/prod bionic InRelease Ign:8 https://pkg.jenkins.io/debian-stable binary/ InRelease Get:9 https://pkg.jenkins.io/debian-stable binary/ Release [2044 B] Get:10 https://pkg.jenkins.io/debian-stable binary/ Release.gpg [833 B] Err:10 https://pkg.jenkins.io/debian-stable binary/ Release.gpg The following signatures couldn't be verified because the public key is not available: NO_PUBKEY FCEF32E745F2C3D5 Fetched 253 kB in 2s (157 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 332 packages can be upgraded. Run 'apt list --upgradable' to see them. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://pkg.jenkins.io/debian-stable binary/ Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY FCEF32E745F2C3D5 W: Failed to fetch https://pkg.jenkins.io/debian-stable/binary/Release.gpg The following signatures couldn't be verified because the public key is not available: NO_PUBKEY FCEF32E745F2C3D5 W: Some index files failed to download. They have been ignored, or old ones used instead. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 4.15.0-136.140-generic 4.15.18 Uname: Linux 4.15.0-136-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CrashDB: ubuntu Date: Sat Aug 21 18:17:14 2021 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940750 Title: public key is not available: NO_PUBKEY FCEF32E745F2C3D5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1940750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929860] Re: initrdfail can result in resuming with different initrd images and hanging resume
Adding verification-done as this does fix the problem in nearly all testing. I think there is a corner case or something specific to the testing which is causing these outliers. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929860 Title: initrdfail can result in resuming with different initrd images and hanging resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1929860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929860] Re: initrdfail can result in resuming with different initrd images and hanging resume
@sil2100 Following up on our chat conversation. I actually thing this grub2 package update could be released. It is greatly improving the situation and I think is doing the right thing. But I think there may be other external factors in play that may result in these corner cases. I can give a verification done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929860 Title: initrdfail can result in resuming with different initrd images and hanging resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1929860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929860] Re: initrdfail can result in resuming with different initrd images and hanging resume
@juliank This does not appear to be a complete fix for the issue seen on AWS t2.nano. I see failures in about 5 - 10% of cases. There are two different symptoms: * grub-initrd-fallback.service sometimes runs right before the system hibernates (it runs after the hibernation request was sent to the VM and before it and before it fully hibernates). * grub-initrd-fallback.service sometimes runs after resume, but checking the status of `initrdfail` a few minutes later indicates it is still set (not sure if it was ever cleared). Both of these were determined by checking the last active timestamp reported by 'systemctl status grub-initrd-fallback.service' and comparing this with timestamps generated by the hibernation test. If either situation occurs, the next hibernation/resume will fail. I'm trying to collect more information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929860 Title: initrdfail can result in resuming with different initrd images and hanging resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1929860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936577] Re: Introduce the 470-server series
Testing has completed for this 470-server driver across bionic, focal and hirsute. The LRM version of the driver was tested against the linux generic kernels currently in -proposed: 4.15.0-152-generic 5.4.0-81-generic 5.11.0-25-generic Testing consisted of running a basic set of the cuda samples (from 11.0). Additional testing on bionic and focal was done with the Data Center GPU Manager to exercise nvidia-fabricmanager and libnvidia-nscq-470. ** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-hirsute ** Tags added: verification-done-bionic verification-done-focal verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936577 Title: Introduce the 470-server series To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1936577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938299] Re: Unable to SSH Into Instance when deploying Impish 21.10
[Summary] I believe this problem is related to a change in behavior in cloud-init version 21.2-43-g184c836a-0ubuntu1 due to comparing two different daily impish images before and after this update. The problem appears in a gcp account which currently has multple global sshkeys associated with different users. For example, we have keys for a 'testuser' and 'testuser2' account. When booting the older serial (as well as older releases), we see accounts created for 'testuser', 'testuser2' and 'ubuntu'. For the newer serial, we only see an account for 'ubuntu'. As our test automation uses one of the 'testuser' keys, it can no longer access impish VMs. I've included the package list below from my two test systems. Including the google-agent packages since these could also be suspect. [Expected behavoir] If I have a gcp account with global ssh keys associated with non-ubuntu users, I expect those users to be present in the VM after launch and .ssh/authorized_keys updated with those public keys. [Current behavoir] Only the 'ubuntu' user is being created [Package list with unexpected behavior - impish 20210728 serial] $ dpkg -l|grep cloud-init ii cloud-init 21.2-43-g184c836a-0ubuntu1all initialization and customization tool for cloud instances ii cloud-initramfs-copymods 0.47ubuntu1 all copy initramfs modules into root filesystem for later use ii cloud-initramfs-dyn-netconf0.47ubuntu1 all write a network interface file in /run for BOOTIF $ dpkg -l |grep agent ii google-guest-agent 20210414.00-0ubuntu1 amd64 Google Compute Engine Guest Agent ii google-osconfig-agent 20210219.00-0ubuntu1 amd64 Google OS Config Agent ii gpg-agent 2.2.20-1ubuntu4 amd64 GNU privacy guard - cryptographic agent ii libpolkit-agent-1-0:amd64 0.105-31 amd64 PolicyKit Authentication Agent API ii lxd-agent-loader 0.4 all LXD - VM agent loader [Package list with expected behavior - impish 20190719 serial] $ dpkg -l|grep cloud-init ii cloud-init 21.2-3-g899bfaa9-0ubuntu2 all initialization and customization tool for cloud instances ii cloud-initramfs-copymods 0.47ubuntu1 all copy initramfs modules into root filesystem for later use ii cloud-initramfs-dyn-netconf0.47ubuntu1 all write a network interface file in /run for BOOTIF $ dpkg -l |grep agent ii google-guest-agent 20210414.00-0ubuntu1 amd64 Google Compute Engine Guest Agent ii google-osconfig-agent 20210219.00-0ubuntu1 amd64 Google OS Config Agent ii gpg-agent 2.2.20-1ubuntu4 amd64 GNU privacy guard - cryptographic agent ii libpolkit-agent-1-0:amd64 0.105-31 amd64 PolicyKit Authentication Agent API ii lxd-agent-loader 0.4 all LXD - VM agent loader ** Also affects: cloud-init (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/1938299 Title: Unable to SSH Into Instance when deploying Impish 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1938299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876687] Re: function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on B/F
Failed on bionic:linux generic amd64 host spitfire sru-20210621. ** Summary changed: - function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on Focal + function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on B/F ** Tags added: sru-20210621 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876687 Title: function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on B/F To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1876687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931131] Re: Update the 465 and the 460 NVIDIA driver series
@albertomilone. I've completed the basic CUDA testing of the server drivers. As with the prior version, the 450-server and 460-server drivers passed across the generic kernels for bionic, focal, groovy, hirsute and impish. This applies to both the dkms and lrm installations. Impish was tested with the 5.11 kernel. For the 418-server driver, the dkms driver passed for bionic, focal and groovy did not work with hirsute or impish (both with the 5.11 kernel). The LRM driver worked across all 5 series. This was the same behavior as the prior version of the driver. I plan on doing additional testing to get coverage on more platforms, but this passes the minimal testing criteria. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931131 Title: Update the 465 and the 460 NVIDIA driver series To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934424] [NEW] kernel NULL pointer dereference during xen hibernation
Public bug reported: Encountered the following panic while doing hibernation/resume testing with linux-aws 5.8 on Focal on an m3.xlarge (xen) instance type: [ 594.291317] ACPI: Hardware changed while hibernated, success doubtful! [ 594.411609] BUG: kernel NULL pointer dereference, address: 01f4 [ 594.424658] #PF: supervisor write access in kernel mode [ 594.424660] #PF: error_code(0x0002) - not-present page [ 594.424661] PGD 0 P4D 0 [ 594.424665] Oops: 0002 [#1] SMP PTI [ 594.424668] CPU: 3 PID: 362 Comm: systemd-timesyn Not tainted 5.8.0-1036-aws #38~20.04.1-Ubuntu [ 594.424669] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 594.424675] RIP: 0010:_raw_spin_lock_irqsave+0x23/0x40 [ 594.424678] Code: 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 9c 58 0f 1f 44 00 00 49 89 c4 fa 66 0f 1f 44 00 00 31 c0 ba 01 00 00 00 0f b1 17 75 07 4c 89 e0 41 5c 5d c3 89 c6 e8 e9 d1 56 ff 66 90 [ 594.424679] RSP: 0018:c94e3848 EFLAGS: 00010046 [ 594.424680] RAX: RBX: 8883bcc0d000 RCX: 0e02 [ 594.424681] RDX: 0001 RSI: RDI: 01f4 [ 594.424682] RBP: c94e3850 R08: 8883b90b5ec0 R09: 005a [ 594.424683] R10: c94e3910 R11: R12: 0206 [ 594.424684] R13: ea000ee42d40 R14: R15: 0001 [ 594.424686] FS: 7f65ba055980() GS:8883c0ac() knlGS: [ 594.424687] CS: 0010 DS: ES: CR0: 80050033 [ 594.424688] CR2: 01f4 CR3: 0003b99f0001 CR4: 001606e0 [ 594.424692] Call Trace: [ 594.424699] xennet_start_xmit+0x158/0x570 [ 594.424704] dev_hard_start_xmit+0x91/0x1f0 [ 594.424706] ? validate_xmit_skb+0x300/0x340 [ 594.424710] sch_direct_xmit+0x113/0x340 [ 594.424712] __dev_queue_xmit+0x57c/0x8e0 [ 594.424714] ? neigh_add_timer+0x37/0x60 [ 594.424716] dev_queue_xmit+0x10/0x20 [ 594.424717] neigh_resolve_output+0x112/0x1c0 [ 594.424721] ip_finish_output2+0x19b/0x590 [ 594.424723] __ip_finish_output+0xc8/0x1e0 [ 594.424725] ip_finish_output+0x2d/0xb0 [ 594.424728] ip_output+0x7a/0xf0 [ 594.424730] ? __ip_finish_output+0x1e0/0x1e0 [ 594.424732] ip_local_out+0x3d/0x50 [ 594.424734] ip_send_skb+0x19/0x40 [ 594.424737] udp_send_skb.isra.0+0x165/0x390 [ 594.424739] udp_sendmsg+0xb0e/0xd50 [ 594.424742] ? ip_reply_glue_bits+0x50/0x50 [ 594.424747] ? delete_from_swap_cache+0x6a/0x90 [ 594.424750] ? _cond_resched+0x19/0x30 [ 594.424754] ? aa_sk_perm+0x43/0x1b0 [ 594.424757] inet_sendmsg+0x65/0x70 [ 594.424759] ? security_socket_sendmsg+0x35/0x50 [ 594.424760] ? inet_sendmsg+0x65/0x70 [ 594.424764] sock_sendmsg+0x5e/0x70 [ 594.424766] __sys_sendto+0x113/0x190 [ 594.424770] ? __secure_computing+0x42/0xe0 [ 594.424774] ? syscall_trace_enter+0x10d/0x280 [ 594.424777] __x64_sys_sendto+0x29/0x30 [ 594.424781] do_syscall_64+0x49/0xc0 [ 594.424783] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 594.424785] RIP: 0033:0x7f65baee4844 [ 594.424788] Code: 42 3f f7 ff 44 8b 4c 24 2c 4c 8b 44 24 20 89 c5 44 8b 54 24 28 48 8b 54 24 18 b8 2c 00 00 00 48 8b 74 24 10 8b 7c 24 08 0f 05 <48> 3d 00 f0 ff ff 77 30 89 ef 48 89 44 24 08 e8 68 3f f7 ff 48 8b [ 594.424789] RSP: 002b:7ffe9b5fd3a0 EFLAGS: 0293 ORIG_RAX: 002c [ 594.424790] RAX: ffda RBX: 7ffe9b5fd4e0 RCX: 7f65baee4844 [ 594.424791] RDX: 0030 RSI: 7ffe9b5fd3f0 RDI: 0010 [ 594.424792] RBP: R08: 560426541678 R09: 0010 [ 594.424793] R10: 0040 R11: 0293 R12: [ 594.424794] R13: 7ffe9b5fd3e4 R14: 0068 R15: [ 594.424796] Modules linked in: btrfs blake2b_generic xor raid6_pq ufs msdos xfs libcrc32c dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd input_leds glue_helper serio_raw floppy sch_fq_codel drm ip_tables x_tables autofs4 [ 594.424813] CR2: 01f4 [ 594.424821] ---[ end trace bb5f35055c1a8060 ]--- [ 594.424822] RIP: 0010:_raw_spin_lock_irqsave+0x23/0x40 [ 594.424824] Code: 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 9c 58 0f 1f 44 00 00 49 89 c4 fa 66 0f 1f 44 00 00 31 c0 ba 01 00 00 00 0f b1 17 75 07 4c 89 e0 41 5c 5d c3 89 c6 e8 e9 d1 56 ff 66 90 [ 594.424824] RSP: 0018:c94e3848 EFLAGS: 00010046 [ 594.424825] RAX: RBX: 8883bcc0d000 RCX: 0e02 [ 594.424826] RDX: 0001 RSI: RDI: 01f4 [ 594.424826] RBP: c94e3850 R08: 8883b90b5ec0 R09: 005a [ 594.424827] R10: c94e3910 R11: R12: 0206 [ 594.424827] R13: ea000ee42d40 R14: R15: 0001 [ 594.424828] FS: 7f65ba055980()
[Bug 1929860] [NEW] initrdfail can result in resuming with different initrd images and hanging resume
Public bug reported: Ubuntu Focal (and new releases) on AWS will normally boot without an initrd image (just the microcode.cpio). There is a fallback mechanism to reboot with the full initrd image when the boot fails to complete. The grub environment variable "initrdfail" is used to track when a boot failed and switch between the optimized initrd-less boot path and the full initrd path. On a normal successful boot, the "initrdfail" variable is cleared by grub-initrd-fallback.service. However, this doesn't happen when resuming from hibernation. As a result, the initrd fallback will get triggered on the second hibernation / resume cycle despite the original boot using only the microcode.cpio. This switch in initrd images leads to the second resume hanging. We've been able to successfully avoid this issue by adding the following to the ec2-hibinit-agent resume handler: /usr/bin/grub-editenv - unset initrdfail /usr/bin/grub-editenv - unset recordfail (Note: clearing recordfail may not be necessary, will need to try again without it.) This bug was filed against grub2 as it appears to own initrdfail. ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Package changed: ec2-hibinit-agent (Ubuntu) => grub2 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929860 Title: initrdfail can result in resuming with different initrd images and hanging resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1929860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923191] Re: cpuhotplug from ubuntu_ltp failed for cpuhotplug02 cpuhotplug03 cpuhotplug04 cpuhotplug06
** Tags added: 5.4 sru-20210510 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923191 Title: cpuhotplug from ubuntu_ltp failed for cpuhotplug02 cpuhotplug03 cpuhotplug04 cpuhotplug06 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1923191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925522] Re: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
fabric-manager-460 and libnvidia-nscq-460: These passed using the cuda samples test and 'dcgmi discovery -l' test on a dgx-2 host using bionic and focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925522 Title: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/1925522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925522] Re: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
I've completed additional testing on bionic on a dgx2: nvidia-graphics-drivers-450-server: Both the bionic lrm and dkms versions were tested successfully with via the cuda samples test (version 11.0). fabric-manager-450 and libnvidia-nscq-450: These passed using the cuda samples test and 'dcgmi discovery -l' on a dgx-2 host using bionic. I also retested the focal lrm version nvidia-graphics-drivers-450-server on a gcp cloud VM. It now installs with the kernel and lrm packages in focal-proposed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925522 Title: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/1925522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925522] Re: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
nvidia-graphics-drivers-450-server, 450.119.04 results: The DKMS driver was tested via the cuda samples test. This passed for bionic, focal and groovy, but failed for hirsute and impish. This failure was expected as the nvidia_uvm module doens't currently load with the 5.11 kernel in hirsute and impish. The LRM driver was also tested via the cuda samples test. This passed for groovy, hirsute and impish, but failed on bionic and focal as there isn't yet a matching lrm package for the 450.119.04 driver. When these packages are available later in the kernel SRU cycle, it will be retested. fabric-manager-450 and libnvidia-nscq-450: These passed using the cuda samples test and 'dcgmi discovery -l' on a dgx-2 host using focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925522 Title: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/1925522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928297] [NEW] package mysql-server-8.0 8.0.23-0ubuntu0.20.04.1 failed to install/upgrade: subproces van het nieuwe pakket mysql-server-8.0 het script pre-removal gaf de foutwaarde 1 terug
Public bug reported: attempt to load a xammp ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.23-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 AptOrdering: mysql-server-8.0:amd64: Install mysql-server-core-8.0:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 13 06:19:43 2021 ErrorMessage: subproces van het nieuwe pakket mysql-server-8.0 het script pre-removal gaf de foutwaarde 1 terug InstallationDate: Installed on 2021-05-08 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Logs.var.log.daemon.log: Logs.var.log.mysql.error.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLVarLibDirListing: ['performance_schema', 'debian-10.3.flag', 'ib_logfile1', 'ibdata1', 'ib_logfile0', 'ib_buffer_pool', 'mysql', 'aria_log.0001', 'mysql_upgrade_info', 'multi-master.info', 'aria_log_control'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=5c04150e-5b06-4ff9-bc44-bcfda1a423f1 ro quiet splash i8042.nomux i8024.noloop vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.23-0ubuntu0.20.04.1 failed to install/upgrade: subproces van het nieuwe pakket mysql-server-8.0 het script pre-removal gaf de foutwaarde 1 terug UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-8.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928297 Title: package mysql-server-8.0 8.0.23-0ubuntu0.20.04.1 failed to install/upgrade: subproces van het nieuwe pakket mysql-server-8.0 het script pre-removal gaf de foutwaarde 1 terug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1928297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925407] Re: ubuntu_aufs_smoke_test failed on Hirsute RISCV (CONFIG_AUFS_FS is not set)
This is resolved in autotest-client-tests 5b2d46bf401e50a13be5c0641e0157d58c2a7669 ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux-riscv (Ubuntu) Status: New => Won't Fix ** Changed in: linux-riscv (Ubuntu Hirsute) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925407 Title: ubuntu_aufs_smoke_test failed on Hirsute RISCV (CONFIG_AUFS_FS is not set) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1925407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927801] Re: on my dual monitor 21.04 system gnome-shell locks up about 2 to 5 mins after login
it did it again after many hours ** Attachment added: "this is from running sudo journalctl -b-1 |tee ~/tmp/prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1927801/+attachment/5496196/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927801 Title: on my dual monitor 21.04 system gnome-shell locks up about 2 to 5 mins after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1927801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927801] Re: on my dual monitor 21.04 systemm gnome-shell locks up about 2 to 5 mins after login
it's not happening just now, > 1:20:00 and still nothing bad will see how it goes will do what you asked if it plays up, hmm there have been updates wonder if any of those where dependancies -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927801 Title: on my dual monitor 21.04 systemm gnome-shell locks up about 2 to 5 mins after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1927801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927801] Re: on my dual monitor 21.04 systemm gnome-shell locks up about 2 to 5 mins after login
must have missed the fields for the package and distro version sorry, but it was all in there -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927801 Title: on my dual monitor 21.04 systemm gnome-shell locks up about 2 to 5 mins after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1927801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927801] Re: on my dual monitor 21.04 systemm gnome-shell locks up about 2 to 5 mins after login
running Mate until this is fixed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927801 Title: on my dual monitor 21.04 systemm gnome-shell locks up about 2 to 5 mins after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1927801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927801] Re: on my dual monitor 21.04 systemm gnome-shell locks up about 2 to 5 mins after login
Oh and I did run ubuntu-bug gnome-shell from the F2 dialog but it locked up before I could finish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927801 Title: on my dual monitor 21.04 systemm gnome-shell locks up about 2 to 5 mins after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1927801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927801] [NEW] on my dual monitor 21.04 systemm gnome-shell locks up about 2 to 5 mins after login
Public bug reported: 1. $ lsb_release -rd Description:Ubuntu 21.04 Release:21.04 2. $ apt-cache policy gnome-shell gnome-shell: Installed: 3.38.4-1ubuntu2 Candidate: 3.38.4-1ubuntu2 Version table: *** 3.38.4-1ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status 3. I expected it to work like normal. 4. It locked up after 2 to 5 mins. I have tried logging into Xorg, a different account with no plugins I removed the extra monitor All to NO EFFECT ** Affects: ubuntu Importance: Undecided Status: New ** Tags: gnome-shell gui-lockup -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927801 Title: on my dual monitor 21.04 systemm gnome-shell locks up about 2 to 5 mins after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1927801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923062] Re: NVIDIA CVE-2021-1076 CVE-2021-1077
Also tested linux-modules-nvidia-460-server-generic-hwe-18.04 on bionic and linux-modules-nvidia-460-server-generic-hwe-20.04 on focal. They look good now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923062 Title: NVIDIA CVE-2021-1076 CVE-2021-1077 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1923062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923062] Re: NVIDIA CVE-2021-1076 CVE-2021-1077
Testing of the server drivers is also complete. All drivers were able to install as both dkms and l-r-m with no issues. A cuda workload and nvidia-smi was also tested for each. Note: no upgrade testing was attempted. Drivers were fully purged before testing the next driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923062 Title: NVIDIA CVE-2021-1076 CVE-2021-1077 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1923062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922387] Re: BUG: kernel NULL pointer dereference, address: 0000000000000050
This panic occurred while running the ubuntu_kernel_selftests suite. The last bit of logs are: 13:33:20 DEBUG| [stdout] # selftests: ftrace: ftracetest 13:33:20 DEBUG| [stdout] # === Ftrace unit tests === 13:33:28 DEBUG| [stdout] # [1] Basic trace file check [PASS] 13:37:04 DEBUG| [stdout] # [2] Basic test for tracers [PASS] 13:39:48 DEBUG| [stdout] # [3] Basic trace clock test [PASS] 13:39:56 DEBUG| [stdout] # [4] Basic event tracing check [PASS] 13:40:04 DEBUG| [stdout] # [5] Change the ringbuffer size [PASS] 13:40:20 DEBUG| [stdout] # [6] Snapshot and tracing setting [PASS] 13:40:35 DEBUG| [stdout] # [7] trace_pipe and trace_marker [PASS] 13:40:51 DEBUG| [stdout] # [8] Generic dynamic event - add/remove kprobe events [PASS] 13:41:07 DEBUG| [stdout] # [9] Generic dynamic event - add/remove synthetic events [PASS] 13:41:14 DEBUG| [stdout] # [10] Generic dynamic event - selective clear (compatibility) [PASS] 13:41:22 DEBUG| [stdout] # [11] Generic dynamic event - generic clear event [PASS] 13:41:46 DEBUG| [stdout] # [12] event tracing - enable/disable with event level files [PASS] 13:42:17 DEBUG| [stdout] # [13] event tracing - restricts events based on pid [PASS] 13:42:41 DEBUG| [stdout] # [14] event tracing - enable/disable with subsystem level files [PASS] 13:43:05 DEBUG| [stdout] # [15] event tracing - enable/disable with top level files [PASS] 13:43:14 DEBUG| [stdout] # [16] Test trace_printk from module [PASS] 13:43:56 DEBUG| [stdout] # [17] ftrace - function graph filters with stack tracer [PASS] 13:44:29 DEBUG| [stdout] # [18] ftrace - function graph filters [PASS] 13:45:49 DEBUG| [stdout] # [19] ftrace - function pid filters [PASS] 13:46:06 DEBUG| [stdout] # [20] ftrace - stacktrace filter command [PASS] 13:46:38 DEBUG| [stdout] # [21] ftrace - function trace with cpumask [PASS] 13:47:13 DEBUG| [stdout] # [22] ftrace - test for function event triggers [PASS] 13:47:21 DEBUG| [stdout] # [23] ftrace - function trace on module [PASS] 13:47:31 DEBUG| [stdout] # [24] ftrace - function profiling [PASS] 13:48:07 DEBUG| [stdout] # [25] ftrace - function profiler with function tracing [PASS] 13:48:25 DEBUG| [stdout] # [26] ftrace - test reading of set_ftrace_filter [PASS] END OF MESSAGES This job was run twice. The prior run also hung before completing, but we don't have a console log for that time period, so it's unclear if it also panic'd. It's last messages were: 04:44:27 DEBUG| [stdout] # selftests: timers: nsleep-lat 04:44:48 DEBUG| [stdout] # nsleep latency CLOCK_REALTIME [OK] 04:45:09 DEBUG| [stdout] # nsleep latency CLOCK_MONOTONIC [OK] 04:45:09 DEBUG| [stdout] # nsleep latency CLOCK_MONOTONIC_RAW [UNSUPPORTED] 04:45:09 DEBUG| [stdout] # nsleep latency CLOCK_REALTIME_COARSE [UNSUPPORTED] 04:45:09 DEBUG| [stdout] # nsleep latency CLOCK_MONOTONIC_COARSE [UNSUPPORTED] 04:45:30 DEBUG| [stdout] # nsleep latency CLOCK_BOOTTIME [OK] 04:45:52 DEBUG| [stdout] # nsleep latency CLOCK_REALTIME_ALARM [OK] 04:46:13 DEBUG| [stdout] # nsleep latency CLOCK_BOOTTIME_ALARM [OK] 04:46:34 DEBUG| [stdout] # nsleep latency CLOCK_TAI [OK] 04:46:34 DEBUG| [stdout] # # Pass 0 Fail 0 Xfail 0 Xpass 0 Skip 0 Error 0 04:46:34 DEBUG| [stdout] ok 3 selftests: timers: nsleep-lat 04:46:34 DEBUG| [stdout] # selftests: timers: set-timer-lat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922387 Title: BUG: kernel NULL pointer dereference, address: 0050 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922387] Re: BUG: kernel NULL pointer dereference, address: 0000000000000050
This panic occurred while running the ubuntu_kernel_selftests suite. The last bit of logs are: 13:33:20 DEBUG| [stdout] # selftests: ftrace: ftracetest 13:33:20 DEBUG| [stdout] # === Ftrace unit tests === 13:33:28 DEBUG| [stdout] # [1] Basic trace file check [PASS] 13:37:04 DEBUG| [stdout] # [2] Basic test for tracers [PASS] 13:39:48 DEBUG| [stdout] # [3] Basic trace clock test [PASS] 13:39:56 DEBUG| [stdout] # [4] Basic event tracing check[PASS] 13:40:04 DEBUG| [stdout] # [5] Change the ringbuffer size [PASS] 13:40:20 DEBUG| [stdout] # [6] Snapshot and tracing setting [PASS] 13:40:35 DEBUG| [stdout] # [7] trace_pipe and trace_marker [PASS] 13:40:51 DEBUG| [stdout] # [8] Generic dynamic event - add/remove kprobe events [PASS] 13:41:07 DEBUG| [stdout] # [9] Generic dynamic event - add/remove synthetic events [PASS] 13:41:14 DEBUG| [stdout] # [10] Generic dynamic event - selective clear (compatibility) [PASS] 13:41:22 DEBUG| [stdout] # [11] Generic dynamic event - generic clear event [PASS] 13:41:46 DEBUG| [stdout] # [12] event tracing - enable/disable with event level files [PASS] 13:42:17 DEBUG| [stdout] # [13] event tracing - restricts events based on pid [PASS] 13:42:41 DEBUG| [stdout] # [14] event tracing - enable/disable with subsystem level files [PASS] 13:43:05 DEBUG| [stdout] # [15] event tracing - enable/disable with top level files [PASS] 13:43:14 DEBUG| [stdout] # [16] Test trace_printk from module [PASS] 13:43:56 DEBUG| [stdout] # [17] ftrace - function graph filters with stack tracer [PASS] 13:44:29 DEBUG| [stdout] # [18] ftrace - function graph filters [PASS] 13:45:49 DEBUG| [stdout] # [19] ftrace - function pid filters [PASS] 13:46:06 DEBUG| [stdout] # [20] ftrace - stacktrace filter command [PASS] 13:46:38 DEBUG| [stdout] # [21] ftrace - function trace with cpumask[PASS] 13:47:13 DEBUG| [stdout] # [22] ftrace - test for function event triggers [PASS] 13:47:21 DEBUG| [stdout] # [23] ftrace - function trace on module [PASS] 13:47:31 DEBUG| [stdout] # [24] ftrace - function profiling [PASS] 13:48:07 DEBUG| [stdout] # [25] ftrace - function profiler with function tracing[PASS] 13:48:25 DEBUG| [stdout] # [26] ftrace - test reading of set_ftrace_filter [PASS] END OF MESSAGES This job was run twice. The prior run also hung before completing, but we don't have a console log for that time period, so it's unclear if it also panic'd. It's last messages were: 04:44:27 DEBUG| [stdout] # selftests: timers: nsleep-lat 04:44:48 DEBUG| [stdout] # nsleep latency CLOCK_REALTIME [OK] 04:45:09 DEBUG| [stdout] # nsleep latency CLOCK_MONOTONIC[OK] 04:45:09 DEBUG| [stdout] # nsleep latency CLOCK_MONOTONIC_RAW [UNSUPPORTED] 04:45:09 DEBUG| [stdout] # nsleep latency CLOCK_REALTIME_COARSE [UNSUPPORTED] 04:45:09 DEBUG| [stdout] # nsleep latency CLOCK_MONOTONIC_COARSE [UNSUPPORTED] 04:45:30 DEBUG| [stdout] # nsleep latency CLOCK_BOOTTIME [OK] 04:45:52 DEBUG| [stdout] # nsleep latency CLOCK_REALTIME_ALARM [OK] 04:46:13 DEBUG| [stdout] # nsleep latency CLOCK_BOOTTIME_ALARM [OK] 04:46:34 DEBUG| [stdout] # nsleep latency CLOCK_TAI [OK] 04:46:34 DEBUG| [stdout] # # Pass 0 Fail 0 Xfail 0 Xpass 0 Skip 0 Error 0 04:46:34 DEBUG| [stdout] ok 3 selftests: timers: nsleep-lat 04:46:34 DEBUG| [stdout] # selftests: timers: set-timer-lat The job can be found here: http://10.246.72.4:8080/view/nvidia%20a100%20-%20blanka/job/focal-linux- generic-amd64-5.4.0-blanka-ubuntu_kernel_selftests/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922387 Title: BUG: kernel NULL pointer dereference, address: 0050 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918226] Re: testbed auxverb failed with exit code 255 with linux on Groovy ADT failure
I also looked at this and compared with older kernels. This test has never progressed past the "Kretprobe dynamic event with maxactive" test on 5.8, but it has on 5.4: ``` 18:41:31 DEBUG| [stdout] # [43] Kprobe event parser error log check [PASS] 18:41:32 DEBUG| [stdout] # [44] Kretprobe dynamic event with arguments [PASS] 18:41:33 DEBUG| [stdout] # [45] Kretprobe dynamic event with maxactive [PASS] 18:41:49 DEBUG| [stdout] # [46] Register/unregister many kprobe events [PASS] 18:41:49 DEBUG| [stdout] # [47] Kprobe dynamic event - adding and removing [PASS] 18:41:50 DEBUG| [stdout] # [48] Uprobe event parser error log check [PASS] 18:41:50 DEBUG| [stdout] # [49] test for the preemptirqsoff tracer [UNSUPPORTED] 18:42:32 DEBUG| [stdout] # [50] Meta-selftest [PASS] ``` I suspect that next test is causing a hang and ssh dies. The autopkgtest infrastructure sees this and tries to provide some debugging info (the console log and vm details). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918226 Title: testbed auxverb failed with exit code 255 with linux on Groovy ADT failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805806] Re: test_maps in ubuntu_bpf failed with "Failed sockmap unexpected timeout" on D ARM64
Seen with linux-aws 5.4.0-1038.40~18.04.1. ** Tags added: sru-20210125 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805806 Title: test_maps in ubuntu_bpf failed with "Failed sockmap unexpected timeout" on D ARM64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1805806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844493] Re: ubuntu_sysdig_smoke_test failed on 5.3 / 5.4 / 5.6 /5.8 kernels
** Tags added: sru-20210125 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844493 Title: ubuntu_sysdig_smoke_test failed on 5.3 / 5.4 / 5.6 /5.8 kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1844493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905728] Re: Found insecure W+X mapping at address on Groovy RISCV
** Attachment added: "dmesg-5.8.0-17-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905728/+attachment/5464855/+files/dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905728 Title: Found insecure W+X mapping at address on Groovy RISCV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905728] Re: Found insecure W+X mapping at address on Groovy RISCV
Still seeing this with the 5.8.0-17-generic riscv kernel on groovy. See attached dmesg. ** Changed in: linux (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905728 Title: Found insecure W+X mapping at address on Groovy RISCV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748103] Re: apic test in kvm-unit-test failed with timeout
Seen with linux-oracle 4.15.0-1065.73~16.04.1. ** Tags added: sru-20210125 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748103 Title: apic test in kvm-unit-test failed with timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1748103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831449] Re: memory in ubuntu_kvm_unit_tests fails
Seen with linux-oracle 4.15.0-1065.73~16.04.1. ** Tags added: sru-20210125 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831449 Title: memory in ubuntu_kvm_unit_tests fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748105] Re: port80 test in ubuntu_kvm_unit_tests failed with timeout
Seen with linux-oracle 4.15.0-1065.73~16.04.1. ** Tags added: sru-20210125 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748105 Title: port80 test in ubuntu_kvm_unit_tests failed with timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1748105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827979] Re: pcid in ubuntu_kvm_unit_tests failed on B-KVM / X-4.15-oracle / B-oracle-5.3
Seen with linux-oracle 4.15.0-1065.73~16.04.1. ** Tags added: sru-20210125 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827979 Title: pcid in ubuntu_kvm_unit_tests failed on B-KVM / X-4.15-oracle / B-oracle-5.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829995] Re: getaddrinfo_01 from ipv6_lib test suite in LTP failed
Seen with linux-oracle 4.15.0-1065.73. ** Tags added: oracle sru-20210125 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829995 Title: getaddrinfo_01 from ipv6_lib test suite in LTP failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837035] Re: memcg_stat_rss from controllers in ubuntu_ltp failed
Seen with linux-oracle 4.15.0-1065.73. ** Tags added: sru-20210125 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837035 Title: memcg_stat_rss from controllers in ubuntu_ltp failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837543] Re: crypto_user02 in crypto from ubuntu_ltp failed
Seen with linux-oracle 4.15.0-1065.73. ** Tags added: sru-20210125 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837543 Title: crypto_user02 in crypto from ubuntu_ltp failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829849] Re: proc01 in fs from ubuntu_ltp failed
Seen with linux-oracle 4.15.0-1065.73. ** Tags added: sru-20210125 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829849 Title: proc01 in fs from ubuntu_ltp failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829978] Re: cpuacct_100_100 from controllers test suite in LTP failed
Seen with linux-oracle 4.15.0-1065.73. ** Tags added: oracle sru-20210125 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829978 Title: cpuacct_100_100 from controllers test suite in LTP failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822309] Re: vmx_apic_passthrough_thread in kvm_unit_tests failed with 1 unexpected failures
Still seen with linux-oracle 4.15.0-1065.73. ** Tags added: sru-20210125 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822309 Title: vmx_apic_passthrough_thread in kvm_unit_tests failed with 1 unexpected failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822308] Re: vmx_hlt_with_rvi_test in kvm_unit_tests fails
Seen with linux-oracle 4.15.0-1065.73. ** Tags added: sru-2021-0125 ** Tags removed: sru-2021-0125 ** Tags added: sru-20210125 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822308 Title: vmx_hlt_with_rvi_test in kvm_unit_tests fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839912] Re: test_map in ubuntu_bpf failed with "Allowed update sockmap '0:3' not in ESTABLISHED"
Still seen with linux-oracle 4.15.0-1065.73. ** Tags added: sru-20210125 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839912 Title: test_map in ubuntu_bpf failed with "Allowed update sockmap '0:3' not in ESTABLISHED" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1839912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882213] Re: cp file from external HDD to NFS on Pi 3B causes ubuntu 19.10 and 20.04 kernel to hang
@juergh, I retested this with focal 5.4.0-1028-raspi and was unable to reproduce. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882213 Title: cp file from external HDD to NFS on Pi 3B causes ubuntu 19.10 and 20.04 kernel to hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1882213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1886114] Re: package samba-common-bin 2:4.11.6+dfsg-0ubuntu1.3 failed to install/upgrade: installed samba-common-bin package post-installation script subprocess returned error exit status 1
sudo apt-get remove --purge *samba*; sudo apt-get install samba I applied this recommendation without error; thank you Le 12/02/2021 à 02:08, Bryce Harrington a écrit : > sudo apt-get remove --purge > *samba*; sudo apt-get install samba -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886114 Title: package samba-common-bin 2:4.11.6+dfsg-0ubuntu1.3 failed to install/upgrade: installed samba-common-bin package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1886114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913200] Re: Introduce the new NVIDIA 460-server series and update the 460 series
Testing of the 460-server driver has passed on bionic, focal and groovy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913200 Title: Introduce the new NVIDIA 460-server series and update the 460 series To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
