[Bug 2063470] [NEW] 6.8.0-1004-raspi "The futex facility returned an unexpected error code."
Public bug reported: Upgrading my Raspberry Pi 5 to 6.8.0-1004-raspi broke the CI that runs on it. https://cirrus-ci.com/task/6254679959535616 All the attempts were after upgrading, except the very last re-run that succeeded after downgrading to 6.8.0-1001-raspi. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-1004-raspi 6.8.0-1004.4 ProcVersionSignature: Ubuntu 6.8.0-1001.1-raspi 6.8.0-rc4 Uname: Linux 6.8.0-1001-raspi aarch64 ApportVersion: 2.28.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Thu Apr 25 18:54:42 2024 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063470 Title: 6.8.0-1004-raspi "The futex facility returned an unexpected error code." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2063470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056500] Re: missing words in /usr/share/dict/words
it looks like I needed to install wamerican-insane then run sudo select-default-wordlist ** Changed in: scowl (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/2056500 Title: missing words in /usr/share/dict/words To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scowl/+bug/2056500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056500] [NEW] missing words in /usr/share/dict/words
Public bug reported: ``` luke@opus91:~$ dpkg -S /usr/share/dict/words wamerican: /usr/share/dict/words luke@opus91:~$ luke@opus91:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy luke@opus91:~$ ``` ```grep tuck /usr/share/dict/words ``` shows that the following words (minimally) are missing: ``` tuckahoe tuckahoe tuckshops untuck untucked untucks untucking tuckerization tuckedly stuckism ``` all of which show up on https://www.thefreedictionary.com/words- containing-tuck and some of which are used in the NY Times spelling bee game. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wamerican 2020.12.07-2 ProcVersionSignature: Ubuntu 6.2.0-1017.17~22.04.1-aws 6.2.16 Uname: Linux 6.2.0-1017-aws x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: aws CloudName: aws CloudPlatform: ec2 CloudRegion: us-east-1 CloudSubPlatform: metadata (http://169.254.169.254) Date: Thu Mar 7 22:21:42 2024 Ec2AMI: ami-0c7217cdde317cfec Ec2AMIManifest: (unknown) Ec2Architecture: x86_64 Ec2AvailabilityZone: us-east-1a Ec2Imageid: ami-0c7217cdde317cfec Ec2InstanceType: t3.medium Ec2Instancetype: t3.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Ec2Region: us-east-1 PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: scowl UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: scowl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056500 Title: missing words in /usr/share/dict/words To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scowl/+bug/2056500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 39376]
Just wanted to note: To unhide any of the file extensions affected by this change / Dolphin 23.08, use "File Associations" in System Settings to create a new file type for them. To the contrary, removing *.old and *.bak from the "application/x-trash" association still kept them hidden (which makes sense since the file types probably fell back to the system association, which is still "application/x-trash") Might be stating the obvious, but I think this tip might help someone stumbling into this in future. I was one of the users purposefully renaming files to end in *.bak or *.old and naturally would like to keep them visible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/39376 Title: Allow hidding of backup files To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/39376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976116] Re: Focal update: v5.4.191 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976116 Title: Focal update: v5.4.191 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976116/+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
Found on 2022.05.09/bionic/linux-gcp-fips/4.15.0-2035.38/g1-small ** Tags added: sru-20220509 -- 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 1971479] Re: ADT failure to apply buildfix on Bionic (390.147-0ubuntu0.18.04.1)
Since we don't build i386 for lrm, I have released bionic as this issue isn't related to the kernel release. But when testing I did find that this issue can still be reproduced and leads to a build failure. I tested this with 4.15.0-176 in a i386 VM and could reproduce the failure to apply the buildfix which seems to lead to a build failure. ** Attachment added: "nvidia_file_2.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1971479/+attachment/5588603/+files/nvidia_file_2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971479 Title: ADT failure to apply buildfix on Bionic (390.147-0ubuntu0.18.04.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1971479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972281] Re: ext4: limit length to bitmap_maxbytes
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Luke Nowakowski-Krijger (lukenow) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972281 Title: ext4: limit length to bitmap_maxbytes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972006] Re: Bionic update: upstream stable patchset 2022-05-06
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972006 Title: Bionic update: upstream stable patchset 2022-05-06 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970479] Re: Bionic update: upstream stable patchset 2022-04-26
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970479 Title: Bionic update: upstream stable patchset 2022-04-26 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971480] Re: issuing invalid ioctl to /dev/vsock may spam dmesg
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971480 Title: issuing invalid ioctl to /dev/vsock may spam dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951289] Re: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3, 9, 11, 17, 19, 25 report incorrect sched domain for cpu#32
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951289 Title: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3,9,11,17,19,25 report incorrect sched domain for cpu#32 To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1951289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971479] [NEW] ADT failure to apply buildfix on Bionic (390.147-0ubuntu0.18.04.1)
Public bug reported: There is a failure on ADT with nvidia-graphics-drivers-390 package starting when the package was updated to 390.147-0ubuntu0.18.04.1. This is the failure with bionic/linux 4.15.0-177.186 https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/n/nvidia-graphics-drivers-390/20220503_180848_8905f@/log.gz ... Loading new nvidia-390.147 DKMS files... Building for 4.15.0-177-generic Building for architecture i686 Building initial module for 4.15.0-177-generic Error! Application of patch buildfix_kernel_5.17.patch failed. Check /var/lib/dkms/nvidia/390.147/build/ for more information. ... That leads to ... tar: Cowardly refusing to create an empty archive Try 'tar --help' or 'tar --usage' for more information. autopkgtest [18:08:31]: test dkms-autopkgtest: ---] autopkgtest [18:08:32]: test dkms-autopkgtest: - - - - - - - - - - results - - - - - - - - - - dkms-autopkgtest FAIL non-zero exit status 123 autopkgtest [18:08:32]: summary dkms-autopkgtest FAIL non-zero exit status 123 ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-390 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-390 (Ubuntu Bionic) 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/1971479 Title: ADT failure to apply buildfix on Bionic (390.147-0ubuntu0.18.04.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1971479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968210] Re: USB devices not detected during boot on USB 3.0 hubs
Hi Dries, Please do not feel a rush to validate the fix, I was more asking just to confirm personally that your issue has been resolved :) That message about dropping the fix is more of an empty threat by a bot than anything else.. So feel free at your earliest convenience to update and confirm that the new kernel fixes things for you. Best, - Luke -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968210 Title: USB devices not detected during boot on USB 3.0 hubs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968210] Re: USB devices not detected during boot on USB 3.0 hubs
Verification of the fix was confirmed by Chris Chiu when testing the patch changes. For now we will flip verification done for bionic and focal 5.4 kernels. We are also still waiting for confirmation from Dries Oeyen and Tilman Schmidt to confirm that they are also seeing their issues fixed. ** Tags removed: verification-needed-bionic verification-needed-focal ** Tags added: verification-done-bionic 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/1968210 Title: USB devices not detected during boot on USB 3.0 hubs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968774] Re: LRMv6: add multi-architecture support
** Changed in: linux (Ubuntu Bionic) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968774 Title: LRMv6: add multi-architecture support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968932] Re: Bionic update: upstream stable patchset 2022-04-13
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968932 Title: Bionic update: upstream stable patchset 2022-04-13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968751] Re: Devlink wasn't enabled from common config
** Changed in: linux-bluefield (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968751 Title: Devlink wasn't enabled from common config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1968751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968751] Re: Devlink wasn't enabled from common config
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968751 Title: Devlink wasn't enabled from common config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1968751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968210] Re: USB devices not detected during boot on USB 3.0 hubs
** Description changed:
- There have been reports by some users using certain intel xHCI
- controllers that their USB devices are not being detected after boot
- again after similar issues were previously found and fixed. This seems
- to be related to both [1][2] with the majority of the discussion on [1]
- about these problems reoccurring. This bug report is being made more for
- documentation of this new regression.
+ [SRU Justification]
+
+ [Impact]
+ There are users with certain intel xHCI controllers that are
+ experiencing problems with USB devices not being detected at boot.
+
+ This is because when the primary roothub is registered, device
+ enumeration happens before xHC is running and leads to devices not being
+ detected. This results in the error that looks something like
+ 'usb usb1-port3: couldn't allocate usb_device'.
+
+ [Fix]
+ Register both root hubs along with the secondary hcd for xhci.
+
+ This original fix was reverted upstream due to regressions that occured due to
+ racing that happened when both roothubs were registered simultaneously.
+ However with those fixes being addressed in commits
+ ("usb: hub: Fix usb enumeration issue due to address0 race")
+ ("usb: hub: Fix locking issues with address0_mutex")
+ the maintainers have stated that they will be reintroducing this commit.
+ So lets reintroduce it here to fix the issues that users are
+ experiencing.
+
+ [Test Case]
+ Confirmed by Chris Chiu that this issue exists on similiar hardware
+ reported by the users and that reverting these reverts fixes the issue
+ showing no signs of 'couldn't allocate usb_device' and with USB devices
+ available after boot.
+
+ [Regression Potential]
+ Should be low now that we carry the fixes that seemed to be caused by
+ this patch series.
+
+
+ There have been reports by some users using certain intel xHCI controllers
that their USB devices are not being detected after boot again after similar
issues were previously found and fixed. This seems to be related to both [1][2]
with the majority of the discussion on [1] about these problems reoccurring.
This bug report is being made more for documentation of this new regression.
These seems to be due to the patchset for [2] being reverted upstream
due to regressions.
[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939638
[2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945211
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968210
Title:
USB devices not detected during boot on USB 3.0 hubs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968210/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968210] Re: USB devices not detected during boot on USB 3.0 hubs
** Also affects: linux (Ubuntu Impish) 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/1968210 Title: USB devices not detected during boot on USB 3.0 hubs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968210] [NEW] USB devices not detected during boot on USB 3.0 hubs
Public bug reported: There have been reports by some users using certain intel xHCI controllers that their USB devices are not being detected after boot again after similar issues were previously found and fixed. This seems to be related to both [1][2] with the majority of the discussion on [1] about these problems reoccurring. This bug report is being made more for documentation of this new regression. These seems to be due to the patchset for [2] being reverted upstream due to regressions. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939638 [2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945211 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Luke Nowakowski-Krijger (lukenow) Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Summary changed: - USB devices not detected during boot on USB 3.0 hubs + USB devices not detected during boot on USB 3.0 hubs ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968210 Title: USB devices not detected during boot on USB 3.0 hubs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939638] Re: [regression] USB device is not detected during boot
Is it possible to test on a machine that is not in a secureboot default environment that experienced these issues? i.e. a non-core device. This would be to just confirm if the fix does anything. If so I put up the kernel .deb files with the possible fix here https://kernel.ubuntu.com/~lukenow/lp1939638/deferred_xhci. If that is possible please let me know if you are still experiencing these issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939638 Title: [regression] USB device is not detected during boot To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1939638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939638] Re: [regression] USB device is not detected during boot
Hello Dries and Tilman, Thank you for providing the logs and other relevant information. For clarification, when you were testing if the issue still exists, was this from cold boot or warm boot? And if you sometimes see it working from cold boot it indeed seems to be very racey. There now should be a 100ms power-on-to-good delay on all usb 3.0 hubs since 5.4.0-97, which seems like it used to delay whatever race seems to be going on when the roothubs are being registered (as per the discussion here https://bugzilla.kernel.org/show_bug.cgi?id=214021), but maybe that isn't enough to avoid the race in your case? p.s. If you run lsusb -v as root you should be able to see the bPwrOn2PwrGood value of the root hubs as 100ms. Also, the patchset that seemed to directly address this issue got reverted due to regressions and never seemed to be re-addressed upstream... there seem to be a lot of fixes for those introduced problems since then though so maybe it would make sense to reintroduce those patches. I will send an email to the upstream usb mailing list asking about this and see what their thoughts are. Thanks, - Luke ** Bug watch added: Linux Kernel Bug Tracker #214021 https://bugzilla.kernel.org/show_bug.cgi?id=214021 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939638 Title: [regression] USB device is not detected during boot To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1939638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913977] Re: Bad sound quality (no bass) on Thinkpad T490s
I am having the same issue on my Thinkpad T490. Very tinny/high treble audio with no bass. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913977 Title: Bad sound quality (no bass) on Thinkpad T490s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1913977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939638] Re: [regression] USB device is not detected during boot
Hi, would it be possible to provide the dmesg output after boot? Could you also provide the output of 'lspci -nn | grep USB' since since a lot of these issues seem to be USB card specific and I am unfamiliar with your hardware. As Jarkko mentioned, in 5.4.0-90 there were some patches that were reverted to do with https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945211 that might be now affecting your machines. Thanks, - Luke -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939638 Title: [regression] USB device is not detected during boot To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1939638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966795] [NEW] First boot with fingerprint auth enabled, gdm doesn't prompt to enter password
Public bug reported: Steps: - Enroll fingerprints - Run `pam-auth-update` - Enable "Fingerprint authentication" - Restart Outcome: Fingerprint authentication will work correctly but the textbox to enter a password manually will be disabled. If fingerprint verification fails, then you can type into it. Expected: Should be able to enter your password manually OR use the fingerprint. Ideal scenario: Some things require that you enter your password at least once on startup (e.g.: unlocking the keyring). The best UX (in my opinion) would be to disallow the fingerprint option and require a password on first login. Each subsequent login should then default to fingerprint (or other option as configured), hide the password entry and then only show the password entry if verification fails. System info: Ubuntu Jammy Jellyfish (development branch) Gnome 42 Wayland 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ** Affects: ubuntu Importance: Undecided Status: New ** Summary changed: - First boot with fingerprint auth is enabled, gnome doesn't prompt to enter password + First boot with fingerprint auth enabled, gnome doesn't prompt to enter password ** Summary changed: - First boot with fingerprint auth enabled, gnome doesn't prompt to enter password + First boot with fingerprint auth enabled, gdm doesn't prompt to enter password -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966795 Title: First boot with fingerprint auth enabled, gdm doesn't prompt to enter password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1966795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959762] Re: HID_ASUS should depend on USB_HID in stable v4.15 backports
For Bionic, similar to focal, this was part of stable update (4.15.0-172) which doesn't need verification. The config also was the same after with HID_ASUS and USB_HID set to 'm'. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959762 Title: HID_ASUS should depend on USB_HID in stable v4.15 backports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959762/+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
2022.02.21/bionic/linux/4.15.0-172.181 on dryden ** Tags added: sru-20220221 -- 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 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
@Maciej Borzecki I'll believe that when I see it. This thread is a five-year history of users requesting a fix and the dev team responding that the users are stupid and it's not really a big problem. Why should we believe you that this will ever be fixed, let alone documented? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
@Maciej Borzecki So that's it? There's an experimental setting I can use to manually move my ~snap folder. No documentation to go with it? No plans to actually implement this feature for anyone who isn't extremely tech literate? That solution is less helpful than the ~/.hidden workaround that the userbase figured out years ago -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
Is anyone from Canonical actually working on this bug? And why tf is this still considered a "Wishlist" item after 1200 user reports and hundreds of comments? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812189] Re: test_bpf in net from ubuntu_kernel_selftests failed on cloud kernels
Found on 2022.01.31/xenial/kvm/4.4.0-1100.109 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812189 Title: test_bpf in net from ubuntu_kernel_selftests failed on cloud kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927533] Re: selftests/net/test_bpf fails for linux-kvm due to lack of Kconfig
Found on 2022.01.31/xenial/kvm/4.4.0-1100.109 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927533 Title: selftests/net/test_bpf fails for linux-kvm due to lack of Kconfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958299] Re: Support CIFS for CUDA
** Changed in: linux-bluefield (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958299 Title: Support CIFS for CUDA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1958299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957807] Re: Fix ct_state nat matching and nat action not being executed
** Changed in: linux-bluefield (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957807 Title: Fix ct_state nat matching and nat action not being executed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1957807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959119] Re: Fix sprintf usage that may lead to buffer overflow
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959119 Title: Fix sprintf usage that may lead to buffer overflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1959119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836169] Re: cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on amd64/ARM64
Found on instances akis exotic-skunk starmie-kernel 2022.01.31/bionic/linux/4.15.0-169.177 ** Tags added: sru-20220131 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836169 Title: cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on amd64/ARM64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836169/+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
** Description changed: There are failures in ubuntu_lxc regression tests on Focal/linux/5.4.0-99.112 sru cycle 2022.01.03 with the error lxc-create: symbol lookup error: lxc-create: undefined symbol: strlcat - This does not seem like a kernel regression as these errors did not - appear in the previous spin of kernels in the same cycle and seems like - an lxc test build failure of some kind. + These errors did not appear on previous kernels in the same cycle and + are now have a few tests failing on all architectures and systems as of + Feb 4th 2022 it seems. Log with details is attached in the comments. ** Description changed: There are failures in ubuntu_lxc regression tests on Focal/linux/5.4.0-99.112 sru cycle 2022.01.03 with the error lxc-create: symbol lookup error: lxc-create: undefined symbol: strlcat These errors did not appear on previous kernels in the same cycle and - are now have a few tests failing on all architectures and systems as of - Feb 4th 2022 it seems. Log with details is attached in the comments. + now have a few tests failing on all architectures and systems as of Feb + 4th 2022 it seems. Log with details is attached in the comments. -- 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
** Description changed: There are failures in ubuntu_lxc regression tests on Focal/linux/5.4.0-99.112 sru cycle 2022.01.03 with the error lxc-create: symbol lookup error: lxc-create: undefined symbol: strlcat - This does not seem like a kernel regression as these errors did not appear in the previous spin of kernels in the same cycle and seems like a test build failure corresponding with the lxc/1:4.0.12-0ubuntu1 update. - http://10.246.75.167/2022.01.03/focal/linux/5.4.0-99.112/sru-generic-metal-dryden.ppc64el-ubuntu_lxc-log.txt - http://10.246.75.167/2022.01.03/focal/linux/5.4.0-99.112/sru-generic-metal-kernel04.s390x.zvm-ubuntu_lxc-log.txt - http://10.246.75.167/2022.01.03/focal/linux/5.4.0-99.112/sru-generic-metal-onibi.amd64-ubuntu_lxc-log.txt + This does not seem like a kernel regression as these errors did not + appear in the previous spin of kernels in the same cycle and seems like + an lxc test build failure of some kind. -- 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
My apologies, I looked at the change log from the focal branch of the lxc-pkg-ubuntu repo and pasted the package version I saw in the top commit. I updated the bug description with the package that the regression tests are installing which seems to be 1:4.0.6-0ubuntu1~20.04.1. And yes you're right I should not post internal links, was not thinking Friday evening... I will update the description and remove them. I attached the log, these errors seem to be affecting all of the architectures and systems and failing the same tests across everything. ** Attachment added: "sru-generic-metal-akis.amd64-ubuntu_lxc-log.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960094/+attachment/5559424/+files/sru-generic-metal-akis.amd64-ubuntu_lxc-log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/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
** Summary changed: - lxc/1:4.0.12-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal + lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal -- 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 1960079] [NEW] Settings should cover cases where the dock is disabled
Public bug reported: Release:22.04 - Ubuntu Jammy Jellyfish (development branch) Description: The Appearance Settings within Gnome Settings contains various configuration items for the dock. However, it is possible to disable the dock fully using the Gnome Extensions application. In the case where it is fully disabled, Gnome Settings still shows dock configuration options. Expectation: It would be great if those options are hidden when you've disabled the dock completely. It would also be great to be able to disable the dock from the settings panel. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960079 Title: Settings should cover cases where the dock is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959752] Re: ubuntu_kernel_selftests.ftrace:ftracetest fails with bionic:linux 4.15.0-168.176 on s390x
** Description changed:
- All ftrace tests from selftests are failing with bionic:linux
- 4.15.0-168.176 on s390x:
+ SRU Justification
+
+ [Impact]
+
+ There seems to have been a typo in Commit 85bf17b28f97
+ ("recordmcount.pl: look for jgnop instruction as well as bcrl on s390")
+ that causes errors in finding mcount locations. This seems to cause problems
with ftrace initialization leading to not being able to use ftrace
+ functions.
+
+ [Fix]
+
+ Fix the typo by changing it to the correct instruction.
+
+ [Test Case]
+
+ Ftrace files in /sys/kernel/debug/tracing should be able to be read from
+ and written to with normal functionality. Ftrace selftests should now
+ pass.
+
+ [Where things could go wrong]
+
+ Its a simple typo fix so none really.
+
+ ---
+ All ftrace tests from selftests are failing with bionic:linux 4.15.0-168.176
on s390x:
https://autopkgtest.ubuntu.com/results/autopkgtest-
bionic/bionic/s390x/l/linux/20220201_190955_5689e@/log.gz
==
selftests: ftracetest
=== Ftrace unit tests ===
[1] Basic trace file check[FAIL]
[2] Basic test for tracers[FAIL]
[3] Basic trace clock test[FAIL]
[4] Basic event tracing check [FAIL]
[5] Snapshot and tracing setting [FAIL]
[6] event tracing - enable/disable with event level files [FAIL]
[7] event tracing - restricts events based on pid [FAIL]
[8] event tracing - enable/disable with subsystem level files [FAIL]
[9] event tracing - enable/disable with top level files [FAIL]
[10] ftrace - function graph filters with stack tracer[FAIL]
[11] ftrace - function graph filters [FAIL]
[12] ftrace - function pid filters[FAIL]
[13] ftrace - test for function event triggers[FAIL]
[14] ftrace - function profiler with function tracing [FAIL]
[15] ftrace - test reading of set_ftrace_filter [FAIL]
[16] ftrace - test for function traceon/off triggers [FAIL]
[17] Test creation and deletion of trace instances while setting an event
[FAIL]
[18] Test creation and deletion of trace instances[FAIL]
[19] Kprobe dynamic event - adding and removing [FAIL]
[20] Kprobe dynamic event - busy event check [FAIL]
[21] Kprobe dynamic event with arguments [FAIL]
[22] Kprobe event string type argument[FAIL]
[23] Kprobe event argument syntax [FAIL]
[24] Kprobes event arguments with types [FAIL]
[25] Kprobe event auto/manual naming [FAIL]
[26] Kprobe dynamic event with function tracer[FAIL]
[27] Kretprobe dynamic event with arguments [FAIL]
[28] Kretprobe dynamic event with maxactive [FAIL]
[29] Register/unregister many kprobe events [FAIL]
[30] event trigger - test multiple actions on hist trigger[FAIL]
[31] event trigger - test synthetic_events syntax parser [FAIL]
[32] event trigger - test event enable/disable trigger[FAIL]
[33] event trigger - test trigger filter [FAIL]
[34] event trigger - test histogram modifiers [FAIL]
[35] event trigger - test multiple histogram triggers [FAIL]
[36] event trigger - test snapshot-trigger[FAIL]
[37] event trigger - test stacktrace-trigger [FAIL]
[38] event trigger - test traceon/off trigger [FAIL]
[39] (instance) Basic test for tracers [FAIL]
[40] (instance) Basic trace clock test [FAIL]
[41] (instance) Snapshot and tracing setting [FAIL]
[42] (instance) event tracing - enable/disable with event level files
[FAIL]
[43] (instance) event tracing - restricts events based on pid[FAIL]
[44] (instance) event tracing - enable/disable with subsystem level files
[FAIL]
[45] (instance) ftrace - test for function event triggers[FAIL]
[46] (instance) ftrace - test for function traceon/off triggers [FAIL]
[47] (instance) event trigger - test event enable/disable trigger[FAIL]
[48] (instance) event trigger - test trigger filter [FAIL]
[49] (instance) event trigger - test histogram modifiers [FAIL]
[50] (instance) event trigger - test multiple histogram triggers [FAIL]
# of passed: 0
# of failed: 50
# of unresolved: 0
# of untested: 0
# of unsupported: 0
# of xfailed: 0
# of undefined(test bug): 0
not ok 1..1 selftests: ftracetest [FAIL]
==
After some debugging I've found out that the testcases are not actually
run, the failure happens while running
'tools/testing/selftests/ftrace/test.d/functions:initialize_ftrace()',
on the following line:
[ -f set_ftrace_filter ] && echo | tee set_ftrace_*
After a reboot for clean ftrace state, with kernel 4.15.0-168-generic:
root@kleber-bionic:/sys/kernel/debug/tracing# head set_ftrace_*
head: cannot open
[Bug 1949532] Re: ubuntu_ltp_controllers tests failing on Impish ($cgroup_name already mounted or mount point busy)
** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Luke Nowakowski-Krijger (lukenow) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949532 Title: ubuntu_ltp_controllers tests failing on Impish ($cgroup_name already mounted or mount point busy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition
** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Medium ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849346 Title: [snap] kerberos GSSAPI no longer works after deb->snap transition To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1849346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition
Unless the snap move was intended to provide isolation from Kerberos, setting to medium because this breaks many enterprise usecases for Firefox. ** Changed in: firefox (Ubuntu) Importance: Undecided => Medium ** Changed in: firefox (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849346 Title: [snap] kerberos GSSAPI no longer works after deb->snap transition To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1849346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949532] Re: ubuntu_ltp_controllers tests failing on Impish
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1942113 Here is a discussion about recent regressions in systemd tests where its stated that the cgroups are set up in "unified" (v2) mode in 248.3-1ubuntu5 systemd package. 248.3-1ubuntu7 became the release package on 2021-09-27 which was around the start of the cycle that we started seeing this issues (did we see this before then?), which means that it could very likely have been this upgrade that caused it. Even if earlier packages were in updates I am pretty sure that the machine needs to be restarted for the systemd changes to take affect, which I am pretty sure our test machines don't restart after updating during deployment. So it would make sense that we are seeing the errors correlating with the new systemd package hitting release. I also re-ran tests on previous kernels which didnt have these issues and they are now reporting all the errors, which also points to this being a problem with the systemd package upgrade. In the meantime, it seems that these tests are broken and we should just hint the whole ubuntu_ltp_controllers test suite. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949532 Title: ubuntu_ltp_controllers tests failing on Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949532] Re: ubuntu_ltp_controllers tests failing on Impish
** Description changed: Almost half of the ubuntu_ltp_controllers tests are failing due to the general pattern 'cgroup_name already mounted or mount point busy' causing the tests to fail. e.g. mount: /dev/cgroup: ltp_cgroup already mounted or mount point busy. cgroup_fj_function2_memory 1 TBROK: mount -t cgroup -o memory ltp_cgroup /dev/cgroup failed - From investigation it seems there's an issue with the transition to - cgroup-v2, which on the ltp mailing list has been rumored that one of - these days the tests would break. Its likely this was caused by a - systemd update, switching to cgroup-v2 causing these tests to break due - to different mount and cgroup hierarchy semantics. + From investigation it seems there could be an issue with the transition + to cgroup-v2. There have been rumors on the ltp mailing list that one of + these days the tests could break due to the transition. Switching to + cgroup-v2, likely due to a systemd update, could cause these tests to + break due to different mount and cgroup hierarchy semantics. - After setting systemd.unified_cgroup_hierarchy=0 on the kernel command - line which sets cgroup back to v1, we get the expected failures that we - saw in previous cycles, pointing to this not being a kernel regression. + I could only reproduce a subset of the new failures we are seeing, but + after setting systemd.unified_cgroup_hierarchy=0 on the kernel command + line which sets cgroup back to v1, a lot of the failures I could produce + went away. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949532 Title: ubuntu_ltp_controllers tests failing on Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949532] Re: ubuntu_ltp_controllers tests failing on Impish
** Tags added: 5.13 hinted linux-kvm sru-20211018 ubuntu-ltp ubuntu-ltp- controllers ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949532 Title: ubuntu_ltp_controllers tests failing on Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949532] [NEW] ubuntu_ltp_controllers tests failing on Impish
Public bug reported: Almost half of the ubuntu_ltp_controllers tests are failing due to the general pattern 'cgroup_name already mounted or mount point busy' causing the tests to fail. e.g. mount: /dev/cgroup: ltp_cgroup already mounted or mount point busy. cgroup_fj_function2_memory 1 TBROK: mount -t cgroup -o memory ltp_cgroup /dev/cgroup failed From investigation it seems there's an issue with the transition to cgroup-v2, which on the ltp mailing list has been rumored that one of these days the tests would break. Its likely this was caused by a systemd update, switching to cgroup-v2 causing these tests to break due to different mount and cgroup hierarchy semantics. After setting systemd.unified_cgroup_hierarchy=0 on the kernel command line which sets cgroup back to v1, we get the expected failures that we saw in previous cycles, pointing to this not being a kernel regression. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 5.13 hinted impish linux-kvm sru-20211018 ubuntu-ltp ubuntu-ltp-controllers ** Also affects: ubuntu-kernel-tests 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/1949532 Title: ubuntu_ltp_controllers tests failing on Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927272] Re: Some kernel selftests fail on linux-kvm
** Tags added: 5.13 impish sru-20211018 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927272 Title: Some kernel selftests fail on linux-kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944613] Re: memfd from ubuntu_kernel_selftests failed to build on B-5.4 (unknown type name ‘__u64’)
** 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/1944613 Title: memfd from ubuntu_kernel_selftests failed to build on B-5.4 (unknown type name ‘__u64’) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1944613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896420] Re: seccomp_bpf in seccomp from ubuntu_kernel_selftests failed to build on B-5.4
** Description changed: + [Impact] + + Test fails to build in selftests/seccomp/seccomp_bpf.c with + 'error: storage size of ‘md’ isn’t known' due to the type + struct seccomp_metadata not being defined for B/5.4 kernels. + + [Test case] + + Test successfully builds and test cases pass both on Bionic/5.4 and on + Focal + + [Fixes] + + Unconditionally define struct seccomp_metadata. + Remove linux/ptrace.h where a definition of seccomp_metadata is already being + defined in Focal. + + [Potential regression] + + There could be future build failures if glibc headers get updated to + include definitions of struct seccomp_metadata or if linux/ptrace.h gets updated + to include needed definitions. + + --- Issue found on 5.4.0-48.52~18.04.1 Test build failed with: gcc -Wl,-no-as-needed -Wall seccomp_bpf.c -lpthread -o seccomp_bpf seccomp_bpf.c: In function ‘get_metadata’: seccomp_bpf.c:3028:26: error: storage size of ‘md’ isn’t known struct seccomp_metadata md; ^~ seccomp_bpf.c:3028:26: warning: unused variable ‘md’ [-Wunused-variable] Makefile:12: recipe for target 'seccomp_bpf' failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896420 Title: seccomp_bpf in seccomp from ubuntu_kernel_selftests failed to build on B-5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1896420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944390] Re: Fix ignoring ct state match of OVS offload to TC/HW
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944390 Title: Fix ignoring ct state match of OVS offload to TC/HW To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1944390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946266] Re: Add psample tunnel support and also two fixes for psample issues.
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946266 Title: Add psample tunnel support and also two fixes for psample issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1946266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946393] Re: Fix byte count on fragmented packets in tc ct action
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946393 Title: Fix byte count on fragmented packets in tc ct action To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1946393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934477] Re: ubuntu_aufs_smoke_test failed on F-OEM-5.13
Spotted on b/linux-gke-5.4 5.4.0-1052.55~18.04.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934477 Title: ubuntu_aufs_smoke_test failed on F-OEM-5.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942931] Re: "ethtool -S oob_net0" does not report interrupt counts
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942931 Title: "ethtool -S oob_net0" does not report interrupt counts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1942931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943065] Re: mlxbf_gige: update driver version to 1.25
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943065 Title: mlxbf_gige: update driver version to 1.25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1943065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942932] Re: oob_net0 up but stops processing Rx packets
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942932 Title: oob_net0 up but stops processing Rx packets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1942932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926142] Re: memfd from ubuntu_kernel_selftests failed to build on B-5.4 (error: ‘F_SEAL_FUTURE_WRITE’ undeclared)
** 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/1926142 Title: memfd from ubuntu_kernel_selftests failed to build on B-5.4 (error: ‘F_SEAL_FUTURE_WRITE’ undeclared) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1926142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943484] Re: Focal update: v5.4.141 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Focal) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943484 Title: Focal update: v5.4.141 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926142] Re: memfd from ubuntu_kernel_selftests failed to build on B-5.4 (error: ‘F_SEAL_FUTURE_WRITE’ undeclared)
Another build issue affecting B/5.4 kernels with __u64 for reference https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1944613 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926142 Title: memfd from ubuntu_kernel_selftests failed to build on B-5.4 (error: ‘F_SEAL_FUTURE_WRITE’ undeclared) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1926142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837386] Re: test_maps from ubuntu_bpf failed with "FAIL:failed to create hashmap" on B-hwe i386
Very similar issue found on bionic/gcp-4.15 on 4.15.0-1109.123 only for n1-highcpu-4 instance. 18:45:34 DEBUG| Running './test_maps' 18:45:36 DEBUG| [stdout] Failed to create hashmap 'Cannot allocate memory'! 18:45:36 DEBUG| [stdout] Failed to create hashmap 'Cannot allocate memory'! 18:45:36 DEBUG| [stdout] Failed to create hashmap 'Cannot allocate memory'! 18:45:36 DEBUG| [stdout] Failed to create hashmap 'Cannot allocate memory'! 18:46:06 ERROR| [stderr] test_maps: test_maps.c:967: run_parallel: Assertion `status == 0' failed. With the rest of the threads reporting the same error. This issue also seems to be found in previous cycles on other instances as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837386 Title: test_maps from ubuntu_bpf failed with "FAIL:failed to create hashmap" on B-hwe i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866323] Re: btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed
Found on bionic/gcp-4.15 on 4.15.0-1109.123 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866323 Title: btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897764] Re: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed on X-gcp-4.15 / F-5.4 zVM
Observed on F/gcp 5.4.0-1053.57 on e2-standard-2, f1-micro, n1-highcpu-4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897764 Title: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed on X-gcp-4.15 / F-5.4 zVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1897764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821903] Re: svm in ubuntu_kvm_unit_tests failed on 3.13 / 4.4 / 4.15 (tsc_adjust)
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821903 Title: svm in ubuntu_kvm_unit_tests failed on 3.13 / 4.4 / 4.15 (tsc_adjust) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910312] Re: semctl09 from ubuntu_ltp_syscalls failed on X / F-oem-5.6 / F-oracle-5.4
Failure found on F/oracle 5.4.0-1055.59 on all instances in sru 2021-09-06 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910312 Title: semctl09 from ubuntu_ltp_syscalls failed on X / F-oem-5.6 / F-oracle-5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1910312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943627] [NEW] Controllers test in ubuntu_ltp fails to mount on /dev/cpuctl
Public bug reported: Found on Focal linux-gcp 5.11.0-1019.21 on g1-small instance. The tests are not able to mount on /dev/cpuctl which is causing cpu controller testing, latency tests, and cpuctl_test_fj to fail, seems to be only on g1-small instances. This error has been observed in previous cycles and is not a new regression. 20:09:23 DEBUG| [stdout] startup='Mon Sep 13 20:07:02 2021' 20:09:23 DEBUG| [stdout] TEST 1: CPU CONTROLLER TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] TEST 3: CPU CONTROLLER TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] TEST 4: CPU CONTROLLER TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] TEST 5: CPU CONTROLLER TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] /opt/ltp/testcases/bin/run_cpuctl_stress_test.sh: line 97: /opt/ltp/output/cpuctl_results_stress-678.txt: No such file or directory 20:09:23 DEBUG| [stdout] TEST 6: CPU CONTROLLER STRESS TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] TEST 7: CPU CONTROLLER STRESS TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] TEST 8: CPU CONTROLLER STRESS TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] /opt/ltp/testcases/bin/run_cpuctl_stress_test.sh: line 120: /opt/ltp/output/cpuctl_results_stress-9.txt: No such file or directory 20:09:23 DEBUG| [stdout] TEST 9: CPU CONTROLLER STRESS TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] /opt/ltp/testcases/bin/run_cpuctl_stress_test.sh: line 127: /opt/ltp/output/cpuctl_results_stress-10.txt: No such file or directory 20:09:23 DEBUG| [stdout] TEST 10: CPU CONTROLLER STRESS TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] TINFO Running cpuctl Latency Test 1 20:09:23 DEBUG| [stdout] TINFO The latency check task started 20:09:23 DEBUG| [stdout] FAIL The Latency test 1 failed 20:09:23 DEBUG| [stdout] Max latency observed = 123838 in Iteration 0 20:09:23 DEBUG| [stdout] The results FAIL is just intuitive and not exact failure. Please look at cpuctl_testplan.txt in the test directory. 20:09:23 DEBUG| [stdout] Task 763103 exited abnormally with return value: 1 20:09:23 DEBUG| [stdout] TBROK Test could'nt execute for expected duration 20:09:23 DEBUG| [stdout] Doing cleanup 20:09:23 DEBUG| [stdout] Cleanup done for latency test 1 20:09:23 DEBUG| [stdout] 20:09:23 DEBUG| [stdout] TINFO Running cpuctl Latency Test 2 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] Doing cleanup 20:09:23 DEBUG| [stdout] cat: '/dev/cpuctl/group*/tasks': No such file or directory 20:09:23 DEBUG| [stdout] rmdir: failed to remove '/dev/cpuctl/group*': No such file or directory 20:09:23
[Bug 1942472] Re: seccomp from ubuntu_kernel_selftests failed to build on B-5.4
*** This bug is a duplicate of bug 1896420 *** https://bugs.launchpad.net/bugs/1896420 ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 1896420 seccomp_bpf in seccomp from ubuntu_kernel_selftests failed to build on B-5.4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942472 Title: seccomp from ubuntu_kernel_selftests failed to build on B-5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1942472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942472] Re: seccomp from ubuntu_kernel_selftests failed to build on B-5.4
** Description changed: Test build on B-5.4 (5.4.0-1054.58~18.04.1) failed with: error: storage size of ‘md’ isn’t known Build log: - * Command: - sudo make -C linux/tools/testing/selftests TARGETS=seccomp run_tests - Exit status: 2 - Duration: 2.12612104416 - - stdout: - make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' - make --no-builtin-rules ARCH=x86 -C ../../.. headers_install - make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' - INSTALL ./usr/include - make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' - make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/seccomp' - gcc -Wl,-no-as-needed -Wall seccomp_bpf.c -lpthread -o seccomp_bpf - Makefile:12: recipe for target 'seccomp_bpf' failed - make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/seccomp' - Makefile:143: recipe for target 'all' failed - make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' - stderr: - seccomp_bpf.c: In function ‘get_metadata’: - seccomp_bpf.c:3029:26: error: storage size of ‘md’ isn’t known - struct seccomp_metadata md; - ^~ - seccomp_bpf.c:3029:26: warning: unused variable ‘md’ [-Wunused-variable] - make[1]: *** [seccomp_bpf] Error 1 - make: *** [all] Error 2 + * Command: + sudo make -C linux/tools/testing/selftests TARGETS=seccomp run_tests + Exit status: 2 + Duration: 2.12612104416 + + stdout: + make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' + make --no-builtin-rules ARCH=x86 -C ../../.. headers_install + make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' + INSTALL ./usr/include + make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' + make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/seccomp' + gcc -Wl,-no-as-needed -Wall seccomp_bpf.c -lpthread -o seccomp_bpf + Makefile:12: recipe for target 'seccomp_bpf' failed + make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/seccomp' + Makefile:143: recipe for target 'all' failed + make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' + stderr: + seccomp_bpf.c: In function get_metadata’: + seccomp_bpf.c:3029:26: error: storage size of ‘md’ isn’t known + struct seccomp_metadata md; + ^~ + seccomp_bpf.c:3029:26: warning: unused variable unused variable ‘md’ [-Wunused-variable] + make[1]: *** [seccomp_bpf] Error 1 + make: *** [all] Error 2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942472 Title: seccomp from ubuntu_kernel_selftests failed to build on B-5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942472] [NEW] seccomp from ubuntu_kernel_selftests failed to build on B-5.4
Public bug reported: Test build on B-5.4 (5.4.0-1054.58~18.04.1) failed with: error: storage size of ‘md’ isn’t known Build log: * Command: sudo make -C linux/tools/testing/selftests TARGETS=seccomp run_tests Exit status: 2 Duration: 2.12612104416 stdout: make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' make --no-builtin-rules ARCH=x86 -C ../../.. headers_install make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/seccomp' gcc -Wl,-no-as-needed -Wall seccomp_bpf.c -lpthread -o seccomp_bpf Makefile:12: recipe for target 'seccomp_bpf' failed make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/seccomp' Makefile:143: recipe for target 'all' failed make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' stderr: seccomp_bpf.c: In function get_metadata’: seccomp_bpf.c:3029:26: error: storage size of ‘md’ isn’t known struct seccomp_metadata md; ^~ seccomp_bpf.c:3029:26: warning: unused variable unused variable ‘md’ [-Wunused-variable] make[1]: *** [seccomp_bpf] Error 1 make: *** [all] Error 2 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux-oracle-5.4 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: Incomplete ** Affects: linux-oracle-5.4 (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Incomplete ** Affects: linux-oracle-5.4 (Ubuntu Focal) Importance: Undecided Status: New ** Tags: 5.4 bionic sru-20210816 ubuntu-kernel-selftests ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oracle-5.4 (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/1942472 Title: seccomp from ubuntu_kernel_selftests failed to build on B-5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938748] Re: test_320_config_arm_pan from ubuntu_qrt_kernel_security failed on F-oracle-5.4 / H-oracle-5.11 ARM64
Observed on B/oracle 5.4.0-1054.58~18.04.1 with same instance problem on VM.Standard.A1.Flex-4c.8m -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938748 Title: test_320_config_arm_pan from ubuntu_qrt_kernel_security failed on F-oracle-5.4 / H-oracle-5.11 ARM64 To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1938748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853797] Re: pmu in ubuntu_kvm_unit_tests fails
Found new failures on bionic/linux-oracle/5.4.0-1054.58~18.04.1 on VM.DenseIO2.8 and VM.Standard2.1 2 newly added tests failed 18:12:43 DEBUG| [stdout] FAIL: all counters 18:12:43 DEBUG| [stdout] PASS: overflow: cntr-0 18:12:43 DEBUG| [stdout] PASS: overflow: status-0 18:12:43 DEBUG| [stdout] PASS: overflow: status clear-0 18:12:43 DEBUG| [stdout] PASS: overflow: irq-0 18:12:43 DEBUG| [stdout] PASS: overflow: cntr-1 18:12:43 DEBUG| [stdout] PASS: overflow: status-1 18:12:43 DEBUG| [stdout] PASS: overflow: status clear-1 18:12:43 DEBUG| [stdout] PASS: overflow: irq-1 18:12:43 DEBUG| [stdout] PASS: overflow: cntr-2 18:12:43 DEBUG| [stdout] PASS: overflow: status-2 18:12:43 DEBUG| [stdout] PASS: overflow: status clear-2 18:12:43 DEBUG| [stdout] PASS: overflow: irq-2 18:12:43 DEBUG| [stdout] PASS: overflow: cntr-3 18:12:43 DEBUG| [stdout] PASS: overflow: status-3 18:12:43 DEBUG| [stdout] PASS: overflow: status clear-3 18:12:43 DEBUG| [stdout] PASS: overflow: irq-3 18:12:43 DEBUG| [stdout] PASS: overflow: cntr-4 18:12:43 DEBUG| [stdout] PASS: overflow: status-4 18:12:43 DEBUG| [stdout] PASS: overflow: status clear-4 18:12:43 DEBUG| [stdout] PASS: overflow: irq-4 18:12:43 DEBUG| [stdout] PASS: cmask 18:12:43 DEBUG| [stdout] FAIL: running counter wrmsr: cntr 18:12:43 DEBUG| [stdout] FAIL: running counter wrmsr: status 18:12:43 DEBUG| [stdout] Unhandled exception 13 #GP at ip 0040127f 18:12:43 DEBUG| [stdout] error_code= rflags=00010002 cs=0008 18:12:44 DEBUG| [stdout] rax=00619cf5 rcx=0345 rdx=0002 rbx= 18:12:44 DEBUG| [stdout] rbp=00519f30 rsi=00418117 rdi=00619cf5 18:12:44 DEBUG| [stdout] r8= r9=0020 r10=000d r11=2492492492492493 18:12:44 DEBUG| [stdout] r12=07300402 r13=0603 r14= r15= 18:12:44 DEBUG| [stdout] cr0=80010011 cr2= cr3=01007000 cr4=0020 18:12:44 DEBUG| [stdout] cr8= 18:12:44 DEBUG| [stdout]STACK: @40127f 400338 18:12:44 DEBUG| [stdout] FAIL pmu ** Also affects: linux-oracle-5.4 (Ubuntu) Importance: Undecided Status: New ** Tags added: 5.4 sru-20210816 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853797 Title: pmu in ubuntu_kvm_unit_tests fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1853797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856294] Re: programs in "Installed (local or obsolete)"
This also affects me, on Ubuntu 20.04.2 with synaptic 0.84.6ubuntu5, and on more than one machine. Unfortunately I can't reproduce it reliably; core packages just appear in the 'local or obsolete' tab from time to time, and stay there. On one machine it is network-manager and pulseaudio as in the original post above, but on another it is: libc-bin libc-dev-bin libc6 libc6-dbg libc6-dev libc6-i386 locales Then as of today also: ubuntu-advantage-tools Just as a check I ran 'apt list ?obsolete' to see whether apt was at fault, but that listed only genuinely local packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856294 Title: programs in "Installed (local or obsolete)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1856294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1481835]
Why is this listed as a "papercut"? From Regina's analysis in Comment 48, the developer is going to have to be very careful to not break things worse than they fix. For a student developer new the codebase, this sounds like a standalone project itself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1481835 Title: [UPSTREAM] Unable to group raster image(s) with drawing object(s) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1481835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874824] Re: pgrep reports error "cannot allocate" when run without stack limit
FWIW, I was able to apply bb96fc4295 cleanly to the current 20.04 package (2:3.3.16-1ubuntu2) and it works for me. apt-get -y source procps && cd procps-* curl -fSsL -o debian/patches/sc_arg_max https://gitlab.com/procps-ng/procps/-/commit/bb96fc4295.patch echo sc_arg_max >>debian/patches/series dch --local myorg 'Apply patch: "pgrep: check sanity of SC_ARG_MAX"' debuild -us -uc -G -i -tc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874824 Title: pgrep reports error "cannot allocate" when run without stack limit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916878] Re: Gparted under Welcome app does not launch in live session
** Changed in: ubuntu-mate-welcome (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-mate 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/1916878 Title: Gparted under Welcome app does not launch in live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1916878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917183] Re: Font spacing and rendering is wrong in Firefox 86
It may not be just limited to Firefox, I can confirm the WebKit inspector window has rendering issues too. Ubuntu MATE Welcome is an example. $ ubuntu-mate-welcome --inspect (Note that I was running from its source code, I have not checked the snap) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917183 Title: Font spacing and rendering is wrong in Firefox 86 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1917183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916878] Re: Gparted under Welcome app does not launch in live session
Fixed in https://github.com/ubuntu-mate/ubuntu-mate-welcome- legacy/commit/e949c852b20132c79067bce00bb5d6e79b7192eb ** Changed in: ubuntu-mate-welcome (Ubuntu) Status: New => Fix Committed ** Changed in: ubuntu-mate Status: New => Fix Committed ** Changed in: ubuntu-mate Importance: Undecided => Medium ** Changed in: ubuntu-mate Assignee: (unassigned) => Luke Horwell (lah7) ** Changed in: ubuntu-mate-welcome (Ubuntu) Assignee: (unassigned) => Luke Horwell (lah7) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916878 Title: Gparted under Welcome app does not launch in live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1916878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895036] Re: spamprobe crashes on train and cleanup operations
I'm not quite sure how to build a replacement deb with the patch? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895036 Title: spamprobe crashes on train and cleanup operations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamprobe/+bug/1895036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846423] Re: Lightning: Cannot dismiss reminders. Got a VALUE parameter with an illegal type for property: VALUE=DURATION
I Confirm that bug on Ubuntu Focal with release :1:78.5.1+build1-0ubuntu0.20.04.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846423 Title: Lightning: Cannot dismiss reminders. Got a VALUE parameter with an illegal type for property: VALUE=DURATION To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1846423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908460] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 143
** Description changed: Attempting to upgrade from 18.04 to 20.04, migrating a LXD installation to the 4.0 channel on a host with a ZFS pool. - The migration process hung at "" and had to be killed to continue the - upgrade. + The migration process hung at "Waiting for LXD to come online" and had + to be killed to continue the upgrade. ``` - ^MESC[?1049l==> Installing the LXD snap from the 4.0 track for ubuntu-20.04 + ^MESC[?1049l==> Installing the LXD snap from the 4.0 track for ubuntu-20.04 lxd (4.0/stable) 4.0.4 from CanonicalESC[32m✓ESC[0m installed ==> Waiting for LXD to be online (10min timeout) ==> Running migration from Deb to Snap => Connecting to source server => Connecting to destination server => Running sanity checks === Source server LXD version: 3.0.3 LXD PID: 27120 Resources: - Containers: 37 - Images: 9 - Networks: 1 - Storage pools: 2 + Containers: 37 + Images: 9 + Networks: 1 + Storage pools: 2 === Destination server LXD version: 4.0.4 LXD PID: 26842 Resources: - Containers: 0 - Images: 0 - Networks: 0 - Storage pools: 0 + Containers: 0 + Images: 0 + Networks: 0 + Storage pools: 0 The migration process will shut down all your containers then move your data to the destination LXD. Once the data is moved, the destination LXD will start and apply any needed updates. And finally your containers will be brought back to their previous state, completing the migration. => Shutting down the source LXD => Stopping the source LXD units => Stopping the destination LXD unit => Unmounting source LXD paths => Unmounting destination LXD paths => Wiping destination LXD clean => Backing up the database => Moving the data => Updating the storage backends => Starting the destination LXD => Waiting for LXD to come online Terminated ``` ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lxd 3.0.3-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-126.129-generic 4.15.18 Uname: Linux 4.15.0-126-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 Date: Wed Dec 16 23:57:56 2020 ErrorMessage: new lxd package pre-installation script subprocess returned error exit status 143 InstallationDate: Installed on 2016-08-28 (1571 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: - dpkg 1.19.7ubuntu3 - apt 2.0.2ubuntu0.2 + dpkg 1.19.7ubuntu3 + apt 2.0.2ubuntu0.2 SourcePackage: lxd Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 143 UpgradeStatus: Upgraded to focal on 2020-12-16 (0 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908460 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 143 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1908460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908460] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 143
As a result of the botched migration, attempts to start the snap service failed with: ``` Dec 17 00:08:09 lithium lxd.daemon[9711]: => Re-using existing LXCFS Dec 17 00:08:09 lithium lxd.daemon[9711]: => Starting LXD Dec 17 00:08:09 lithium lxd.daemon[9828]: t=2020-12-17T00:08:09+ lvl=warn msg=" - Couldn't find the CGroup memory swap accounting, swap limits will be ignored" Dec 17 00:08:09 lithium lxd.daemon[9828]: t=2020-12-17T00:08:09+ lvl=eror msg="Failed to start the daemon: Failed applying patch \"storage_api_rename_container_snapshots_links\": readlink /var/snap/lxd/common/lxd/snapshots/matrix: invalid argument" Dec 17 00:08:10 lithium lxd.daemon[9828]: Error: Failed applying patch "storage_api_rename_container_snapshots_links": readlink /var/snap/lxd/common/lxd/snapshots/matrix: invalid argument Dec 17 00:08:10 lithium lxd.daemon[9711]: => LXD failed to start ``` ** Attachment added: "restart-syslog.txt" https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1908460/+attachment/5444351/+files/restart-syslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908460 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 143 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1908460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908460] [NEW] package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 143
Public bug reported: Attempting to upgrade from 18.04 to 20.04, migrating a LXD installation to the 4.0 channel on a host with a ZFS pool. The migration process hung at "" and had to be killed to continue the upgrade. ``` ^MESC[?1049l==> Installing the LXD snap from the 4.0 track for ubuntu-20.04 lxd (4.0/stable) 4.0.4 from CanonicalESC[32m✓ESC[0m installed ==> Waiting for LXD to be online (10min timeout) ==> Running migration from Deb to Snap => Connecting to source server => Connecting to destination server => Running sanity checks === Source server LXD version: 3.0.3 LXD PID: 27120 Resources: Containers: 37 Images: 9 Networks: 1 Storage pools: 2 === Destination server LXD version: 4.0.4 LXD PID: 26842 Resources: Containers: 0 Images: 0 Networks: 0 Storage pools: 0 The migration process will shut down all your containers then move your data to the destination LXD. Once the data is moved, the destination LXD will start and apply any needed updates. And finally your containers will be brought back to their previous state, completing the migration. => Shutting down the source LXD => Stopping the source LXD units => Stopping the destination LXD unit => Unmounting source LXD paths => Unmounting destination LXD paths => Wiping destination LXD clean => Backing up the database => Moving the data => Updating the storage backends => Starting the destination LXD => Waiting for LXD to come online Terminated ``` ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lxd 3.0.3-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-126.129-generic 4.15.18 Uname: Linux 4.15.0-126-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 Date: Wed Dec 16 23:57:56 2020 ErrorMessage: new lxd package pre-installation script subprocess returned error exit status 143 InstallationDate: Installed on 2016-08-28 (1571 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: lxd Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 143 UpgradeStatus: Upgraded to focal on 2020-12-16 (0 days ago) ** Affects: lxd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908460 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 143 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1908460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893543] Re: dovecot is not parsing the variables in dovecot-ldap.conf.ext correctly
Upstream's mailing list was very unhelpful. I'm essentially stuck on this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893543 Title: dovecot is not parsing the variables in dovecot-ldap.conf.ext correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1893543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893543] Re: dovecot is not parsing the variables in dovecot-ldap.conf.ext correctly
** Changed in: dovecot (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893543 Title: dovecot is not parsing the variables in dovecot-ldap.conf.ext correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1893543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901486] [NEW] update libtss2-dev version
Public bug reported: The version of libtss2-dev on ubuntu 20.4 is an old release: version 2.3.2. This release carries many bugs and some security vulnerabilites such as CVE-2020-24455 Currently Ubuntu 20.4 provides version and the latest release is version 2.4.3 Please could you update the package? ** Affects: tpm2-tss (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/1901486 Title: update libtss2-dev version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpm2-tss/+bug/1901486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
>From what I can gather this is not a function of the headset or Bluetooth device, but it's a function of firmware differences in the host side Bluetooth adapters. For example, I have a Sony WH-1000MX3. I have a USB dongle adapter that does not work in the HSP/HFP mode. When selecting the mode the active profile throws various errors then returns to the "off" PulseAudio/ALSA profile. lsusb on the CSR USB dongle. ``` Bus 001 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 224 Wireless bDeviceSubClass 1 Radio Frequency bDeviceProtocol 1 Bluetooth bMaxPacketSize064 idVendor 0x0a12 Cambridge Silicon Radio, Ltd idProduct 0x0001 Bluetooth Dongle (HCI mode) bcdDevice 88.91 iManufacturer 0 iProduct2 iSerial 0 bNumConfigurations 1 ``` I also have an Intel Bluetooth/WiFi 802.11ac card (Bluetooth is on the USB bus), that does support the HSP/HFP mode, abet with noticeably reduced audio quality. I think there is a separate bug in launchpad tracking the audio quality issues of that mode though. header for `lsusb -v` on the Intel card. ``` Bus 001 Device 005: ID 8087:07dc Intel Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 224 Wireless bDeviceSubClass 1 Radio Frequency bDeviceProtocol 1 Bluetooth bMaxPacketSize064 idVendor 0x8087 Intel Corp. idProduct 0x07dc bcdDevice0.01 iManufacturer 0 iProduct0 iSerial 0 bNumConfigurations 1 ``` lspci on the intel card ``` 04:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 Flags: bus master, fast devsel, latency 0, IRQ 96 Memory at f760 (64-bit, non-prefetchable) [size=8K] Capabilities: Kernel driver in use: iwlwifi Kernel modules: iwlwifi ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895036] Re: spamprobe crashes on train and cleanup operations
I'm unsure, but this may be related to https://bugs.launchpad.net/ubuntu/+source/spamprobe/+bug/1882418 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895036 Title: spamprobe crashes on train and cleanup operations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamprobe/+bug/1895036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
I'm on kernel 5.8.8 and am experiencing what I think is the exact same issue with my Magic Trackpad 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1834085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895036] Re: spamprobe crashes on train and cleanup operations
I copied my database out of the way and created a new one to see if that helped. Working it through a corpus of my saved mail with train-good and this brand-new empty database, I see that it is not crashing on every run, only some of them. I do not know yet if there is a pattern to when it does and does not crash, the count of emails it will and will not train-good on is not at all consistent. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895036 Title: spamprobe crashes on train and cleanup operations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamprobe/+bug/1895036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895036] Re: spamprobe crashes on train and cleanup operations
** Package changed: ubuntu => spamprobe (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895036 Title: spamprobe crashes on train and cleanup operations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamprobe/+bug/1895036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895036] Re: spamprobe crashes on train and cleanup operations
this just startted happening after upgrading from bionic to focal. ** Tags added: regression-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895036 Title: spamprobe crashes on train and cleanup operations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1895036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895036] [NEW] spamprobe crashes on train and cleanup operations
Public bug reported: luke@schierer@opus001:~$ lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 luke@schierer@opus001:~$ luke@schierer@opus001:~$ apt-cache policy spamprobe; dpkg -l spamprobe spamprobe: Installed: 1.4d-14build2 Candidate: 1.4d-14build2 Version table: *** 1.4d-14build2 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--= ii spamprobe 1.4d-14build2 amd64Bayesian spam filter luke@schierer@opus001:~$ whenever I run spamprobe cleanup, spamprobe train-good (recursively on a maildir via cronjob) or train-spam (also recursively on a maildir via cronjob) it is crashing. I'm attaching one of the crash files created in /var/crash. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: regression-release ** Attachment added: "_usr_bin_spamprobe.2000.crash" https://bugs.launchpad.net/bugs/1895036/+attachment/5409146/+files/_usr_bin_spamprobe.2000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895036 Title: spamprobe crashes on train and cleanup operations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1895036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893543] Re: dovecot is not parsing the variables in dovecot-ldap.conf.ext correctly
Those list posts both speak to working dovecot configurations (dovecot is working for imap) where the doveadm command does not work. The above snippets are from my /etc/dovecot/dovecot-ldap.conf.ext file which is referenced by /etc/dovecot/conf.d/auth-ldap.conf.ext file. Thus my imap connections aren't working at all. I do not see any where in the man page of the commented out in-file documentation to indicate that I can change the way dovecot uses the search base for its default searches as part of authentication. I've posted upstream, we'll see if I get a reply. https://dovecot.org/pipermail/dovecot/2020-August/119819.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893543 Title: dovecot is not parsing the variables in dovecot-ldap.conf.ext correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1893543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893543] [NEW] dovecot is not parsing the variables in dovecot-ldap.conf.ext correctly
Public bug reported: My dovecot users log in as user@domain, with the ldap directory set up with a couple of different OUs, with one OU per domain. the users in the OUs overlap. if I set luke@schierer@littera001:/etc/dovecot$ sudo grep -v ^# dovecot- ldap.conf.ext | uniq hosts = censor001.plerumque.thecrazyguys.net tls = yes tls_ca_cert_dir = /etc/ssl/certs tls_require_cert = allow debug_level = 4 auth_bind = yes base = ou=%d,dc=thecrazyguys,dc=net scope = subtree user_filter = (&(objectClass=posixAccount)(uid=%n)) pass_filter = (&(objectClass=posixAccount)(uid=%n)) blocking = no luke@schierer@littera001:/etc/dovecot$ then I get a search base of ou=,dc=thecrazyguys,dc=net which is invalid I was experimenting, and I tried base = dc=%d,dc=thecrazyguys,dc=net which produces a search base of dc=domain,dc=thecrazyguys,dc=net which would be correct, except that my ldap tree is set up with OUs and not an extra DC component. for whatever reason, it will do variable substitution for dc=%d, but not for ou=%d. this is certainly not documented, and seems like wrong behavior, since having an ou in a search base is valid. luke@schierer@littera001:/etc/dovecot$ lsb_release -rd Description:Ubuntu 18.04.5 LTS Release: 18.04 luke@schierer@littera001:/etc/dovecot$ luke@schierer@littera001:/etc/dovecot$ dpkg -l | grep -i dovecot ii dovecot-core 1:2.2.33.2-1ubuntu4.6 amd64secure POP3/IMAP server - core files ii dovecot-imapd 1:2.2.33.2-1ubuntu4.6 amd64secure POP3/IMAP server - IMAP daemon ii dovecot-ldap 1:2.2.33.2-1ubuntu4.6 amd64secure POP3/IMAP server - LDAP support ii dovecot-pop3d 1:2.2.33.2-1ubuntu4.6 amd64secure POP3/IMAP server - POP3 daemon luke@schierer@littera001:/etc/dovecot$ ** Affects: dovecot (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/1893543 Title: dovecot is not parsing the variables in dovecot-ldap.conf.ext correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1893543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891643] Re: amavisd-new suggests missing packages
I tried to use one of the programs in the amavis package and it failed because of missing programs from the suggested packages. Cannot remember which one it was now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891643 Title: amavisd-new suggests missing packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1891643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 752542] Re: ACPI DSDT info
https://uk.store.asus.com/asus-rog-strix-gl703gm-ee063t-17-3-120hz-3ms- full-hd-gaming-laptop-intel-i7-8750h-8gb-ram-128gb-pci-e-ssd-1tb-hdd- nvidia-gtx-1060-6gb-windows-10.html ** Attachment added: "ASUSTeK_COMPUTER_INC.-Strix_GL703GM_GL703GM.tar.gz" https://bugs.launchpad.net/lpbugreporter/+bug/752542/+attachment/5401587/+files/ASUSTeK_COMPUTER_INC.-Strix_GL703GM_GL703GM.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/752542 Title: ACPI DSDT info To manage notifications about this bug go to: https://bugs.launchpad.net/bumblebee/+bug/752542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
