[Bug 1959867] [NEW] nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build
Public bug reported: not sure? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.13.0-28-generic Date: Thu Feb 3 07:36:53 2022 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-460:460.73.01-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/460.73.01/build/nvidia-drm/nvidia-drm-crtc.c:311:23: error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state *)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct drm_plane_state *)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2021-03-18 (321 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 460.73.01-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-460 Title: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959867 Title: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1959867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916931] Re: omshell returns inconsistent results or segfaults
I can also confirm this bug with ubuntu 20.04 and isc-dhcp-server 4.4.1 I use the isc-dhcp-server as part of foreman infrastructure and with this bug it is not possible to automate the isc-dhcp-server from foreman. The Problem was solved for the moment as I just compile the isc-dhcp- server from source and install it over the package... but this should not be the long time solution I think.. For whom ever interested this is my solution at this moment: https://community.theforeman.org/t/foreman-proxy-failed-to-add-dhcp- reservation-for-new-vm/27091/3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916931 Title: omshell returns inconsistent results or segfaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1916931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959865] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1959865/+attachment/5558836/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959865 Title: lubuntu jammy bug exploration failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1959865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959865] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1959865/+attachment/5558834/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959865 Title: lubuntu jammy bug exploration failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1959865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959865] .home.lubuntu..cache.calamares.session.log.txt
apport information ** Attachment added: ".home.lubuntu..cache.calamares.session.log.txt" https://bugs.launchpad.net/bugs/1959865/+attachment/5558833/+files/.home.lubuntu..cache.calamares.session.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/1959865 Title: lubuntu jammy bug exploration failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1959865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959865] .etc.calamares.modules.users.conf.txt
apport information ** Attachment added: ".etc.calamares.modules.users.conf.txt" https://bugs.launchpad.net/bugs/1959865/+attachment/5558830/+files/.etc.calamares.modules.users.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959865 Title: lubuntu jammy bug exploration failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1959865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959865] .etc.calamares.modules.welcome.conf.txt
apport information ** Attachment added: ".etc.calamares.modules.welcome.conf.txt" https://bugs.launchpad.net/bugs/1959865/+attachment/5558831/+files/.etc.calamares.modules.welcome.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959865 Title: lubuntu jammy bug exploration failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1959865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959865] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1959865/+attachment/5558835/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959865 Title: lubuntu jammy bug exploration failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1959865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959865] .etc.calamares.modules.partition.conf.txt
apport information ** Attachment added: ".etc.calamares.modules.partition.conf.txt" https://bugs.launchpad.net/bugs/1959865/+attachment/5558829/+files/.etc.calamares.modules.partition.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959865 Title: lubuntu jammy bug exploration failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1959865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959865] .etc.calamares.settings.conf.txt
apport information ** Attachment added: ".etc.calamares.settings.conf.txt" https://bugs.launchpad.net/bugs/1959865/+attachment/5558832/+files/.etc.calamares.settings.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959865 Title: lubuntu jammy bug exploration failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1959865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959865] .etc.calamares.modules.packages.conf.txt
apport information ** Attachment added: ".etc.calamares.modules.packages.conf.txt" https://bugs.launchpad.net/bugs/1959865/+attachment/5558828/+files/.etc.calamares.modules.packages.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959865 Title: lubuntu jammy bug exploration failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1959865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959865] .etc.calamares.modules.mount.conf.txt
apport information ** Attachment added: ".etc.calamares.modules.mount.conf.txt" https://bugs.launchpad.net/bugs/1959865/+attachment/5558827/+files/.etc.calamares.modules.mount.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959865 Title: lubuntu jammy bug exploration failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1959865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959865] .etc.calamares.modules.machineid.conf.txt
apport information ** Attachment added: ".etc.calamares.modules.machineid.conf.txt" https://bugs.launchpad.net/bugs/1959865/+attachment/5558826/+files/.etc.calamares.modules.machineid.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959865 Title: lubuntu jammy bug exploration failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1959865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959865] .etc.calamares.modules.locale.conf.txt
apport information ** Attachment added: ".etc.calamares.modules.locale.conf.txt" https://bugs.launchpad.net/bugs/1959865/+attachment/5558825/+files/.etc.calamares.modules.locale.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959865 Title: lubuntu jammy bug exploration failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1959865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959865] .etc.calamares.modules.displaymanager.conf.txt
apport information ** Attachment added: ".etc.calamares.modules.displaymanager.conf.txt" https://bugs.launchpad.net/bugs/1959865/+attachment/5558823/+files/.etc.calamares.modules.displaymanager.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959865 Title: lubuntu jammy bug exploration failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1959865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959865] .etc.calamares.modules.bootloader.conf.txt
apport information ** Attachment added: ".etc.calamares.modules.bootloader.conf.txt" https://bugs.launchpad.net/bugs/1959865/+attachment/5558822/+files/.etc.calamares.modules.bootloader.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959865 Title: lubuntu jammy bug exploration failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1959865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959865] .etc.calamares.modules.fstab.conf.txt
apport information ** Attachment added: ".etc.calamares.modules.fstab.conf.txt" https://bugs.launchpad.net/bugs/1959865/+attachment/5558824/+files/.etc.calamares.modules.fstab.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959865 Title: lubuntu jammy bug exploration failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1959865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959865] .etc.calamares.modules.before_bootloader_mkdirs_context.conf.txt
apport information ** Attachment added: ".etc.calamares.modules.before_bootloader_mkdirs_context.conf.txt" https://bugs.launchpad.net/bugs/1959865/+attachment/5558821/+files/.etc.calamares.modules.before_bootloader_mkdirs_context.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959865 Title: lubuntu jammy bug exploration failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1959865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959865] .etc.calamares.modules.before_bootloader_context.conf.txt
apport information ** Attachment added: ".etc.calamares.modules.before_bootloader_context.conf.txt" https://bugs.launchpad.net/bugs/1959865/+attachment/5558820/+files/.etc.calamares.modules.before_bootloader_context.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959865 Title: lubuntu jammy bug exploration failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1959865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959865] .etc.calamares.modules.automirror.conf.txt
apport information ** Attachment added: ".etc.calamares.modules.automirror.conf.txt" https://bugs.launchpad.net/bugs/1959865/+attachment/5558819/+files/.etc.calamares.modules.automirror.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959865 Title: lubuntu jammy bug exploration failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1959865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959865] .etc.calamares.modules.after_bootloader_context.conf.txt
apport information ** Attachment added: ".etc.calamares.modules.after_bootloader_context.conf.txt" https://bugs.launchpad.net/bugs/1959865/+attachment/5558818/+files/.etc.calamares.modules.after_bootloader_context.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959865 Title: lubuntu jammy bug exploration failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1959865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959865] [NEW] lubuntu jammy bug exploration failed
Public bug reported: attempt to use `ubuntu-bug calamares` fails -- lubuntu@lubuntu:~$ ubuntu-bug calamares *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. *** The contents of the files attached to this report will help developers diagnose your bug more quickly. It may be possible that there is sensitive information in these files. You will be able to review these attachments before they are sent. Do you want to include these files? What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): y *** Problem in calamares The problem cannot be reported: Your /tmp partition has less than 32.33792 MB of free space available, which leads to problems using applications and installing updates. Please free some space. Press any key to continue... No pending crash reports. Try --help for more information. -- that however is not the purpose of this install; calamares crashed. issue reminded me of SQUASHFS errors; but not are found in logs ** ACTUAL ERROR 2022-02-03 - 18:19:08 [1]: void Calamares::ViewManager::onInstallationFailed(const QString&, const QString&) ERROR: Installation failed: "Failed to unpack image \"/cdrom/casper/filesystem.squashfs\"" 2022-02-03 - 18:19:08 [6]: .. - message: "Failed to unpack image \"/cdrom/casper/filesystem.squashfs\"" 2022-02-03 - 18:19:08 [6]: .. - details: rsync failed with error code 11. 2022-02-03 - 18:19:08 [6]: void Calamares::ViewManager::onInstallationFailed(const QString&, const QString&) Calamares will quit when the dialog closes. 2022-02-03 - 18:19:08 [6]: void Config::doNotify(bool, bool) Notification not sent; completion: failed 2022-02-03 - 18:19:36 [6]: void Config::doRestart(bool) mode= "never" user wants restart? false force restart? false from session.log (I'll add more shortly when on my primary box, either way I'm not convinced this is a real issue, at most it duplicates the issue/reason I was trying this install... ** testcase earlier today a FOCAL.4 install was made to this box; WITH encryption. this was re-using that partition WITHOUT format. If encryption was not involved I'm 100% convinced install would work; I'd have music on the box (added post-QA-install test) & be able to play them `clementine` (again added post-QA-install test). this issue is related I believe to the encryption.. IF IT IS related to encryption; I don't think this type of 'upgrade via reinstall' needs be supported anyway; I'm happy for it to only support unencrypted disks, HOWEVER I have used this install before with Xubuntu and/or `ubiquity` without issue though that was NOT a calamares/install encrypted disk --- ProblemType: Bug .etc.calamares.modules.finished.conf: --- restartNowMode: user-checked restartNowCommand: "systemctl -i reboot" .etc.calamares.modules.shellprocess_logs.conf: --- dontChroot: true timeout: 30 script: - calamares-logs-helper @@ROOT@@ .etc.calamares.modules.unpackfs.conf: --- unpack: - source: "/cdrom/casper/filesystem.squashfs" sourcefs: "squashfs" destination: "" ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: LXQt DistroRelease: Ubuntu 22.04 LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) Package: calamares 3.2.41.1-0ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: calamares-settings-ubuntu-common 1:22.04.1 calamares-settings-lubuntu 1:22.04.1 xfsprogs 5.13.0-1ubuntu1 btrfs-progs 5.15.1-1 Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UnreportableReason: Your /tmp partition has less than 30.253056 MB of free space available, which leads to problems using applications and installing updates. Please free some space. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True ** Affects: calamares (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected jammy ** Attachment added: "~/.cache/calamares/session.log" https://bugs.launchpad.net/bugs/1959865/+attachment/5558817/+files/session.log ** Tags added: apport-collected jammy ** Description changed: attempt to use `ubuntu-bug calamares` fails -- lubuntu@lubuntu:~$ ubuntu-bug calamares *** Collect
[Bug 1926092] Re: lbzip2 package is empty in hirsute
This bug was fixed in the package lbzip2 - 2.5-2.2 --- lbzip2 (2.5-2.2) unstable; urgency=medium * Non-maintainer upload. * d/compat: Remove. * d/control: B-D on debhelper-compat 13. * d/rules: Export DEB_BUILD_MAINT_OPTIONS. Adjust rules to build with debhelper-compat 13. (LP: #1926092) * d/s/options: Remove. -- Sergio Durigan Junior Wed, 02 Feb 2022 17:48:58 -0500 ** Changed in: lbzip2 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926092 Title: lbzip2 package is empty in hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lbzip2/+bug/1926092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949106] Re: HP hotkeys does not work.
** Changed in: linux (Ubuntu) Status: Confirmed => New ** Description changed: - HP hotkeys does not work at all on HP 15-da1071ne laptop. Brightness - keys returns the same scancode, airplane mode returns nothing at all, - closing the lid toggles airplane mode. + Some HP hotkeys does not work at all on HP 15-da1071ne laptop. + Brightness keys returns the same scancode, airplane mode returns nothing + at all, closing the lid toggles airplane mode. Using evtest: Available devices: /dev/input/event0:Lid Switch /dev/input/event1:Power Button /dev/input/event2:Power Button /dev/input/event3:AT Translated Set 2 keyboard /dev/input/event4:SynPS/2 Synaptics TouchPad /dev/input/event5:Video Bus /dev/input/event6:Video Bus /dev/input/event7:HP Wireless hotkeys /dev/input/event8:HP TrueVision HD Camera: HP Tru /dev/input/event9:HDA Intel PCH Mic /dev/input/event10: HDA Intel PCH Headphone /dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event14: HDA Intel PCH HDMI/DP,pcm=9 /dev/input/event15: HDA Intel PCH HDMI/DP,pcm=10 /dev/input/event16: HP WMI hotkeys Testing event 16 (HP WMI hotkeys): No output for the mentioned keys. Testing event 3 (AT Translated Set 2 keyboard): #Brightness up/down yield the following (both the same): Event: time 1630657967.702964, type 4 (EV_MSC), code 4 (MSC_SCAN), value ab Event: time 1630657967.702964, -- SYN_REPORT #Closing the lid then reopening it yields the following: Event: time 1630658208.483290, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9c Event: time 1630658208.483290, type 1 (EV_KEY), code 96 (KEY_KPENTER), value 0 Event: time 1630658208.483290, -- SYN_REPORT Event: time 1630658211.288732, type 4 (EV_MSC), code 4 (MSC_SCAN), value d8 Event: time 1630658211.288732, -- SYN_REPORT Event: time 1630658211.298740, type 4 (EV_MSC), code 4 (MSC_SCAN), value d8 Event: time 1630658211.298740, -- SYN_REPORT Event: time 1630658212.041279, type 4 (EV_MSC), code 4 (MSC_SCAN), value d7 Event: time 1630658212.041279, type 1 (EV_KEY), code 238 (KEY_WLAN), value 1 Event: time 1630658212.041279, -- SYN_REPORT Event: time 1630658212.051527, type 4 (EV_MSC), code 4 (MSC_SCAN), value d7 Event: time 1630658212.051527, type 1 (EV_KEY), code 238 (KEY_WLAN), value 0 Event: time 1630658212.051527, -- SYN_REPORT Event: time 1630658212.058783, type 4 (EV_MSC), code 4 (MSC_SCAN), value e3 Event: time 1630658212.058783, type 1 (EV_KEY), code 143 (KEY_WAKEUP), value 1 Event: time 1630658212.058783, -- SYN_REPORT Event: time 1630658212.069128, type 4 (EV_MSC), code 4 (MSC_SCAN), value e3 Event: time 1630658212.069128, type 1 (EV_KEY), code 143 (KEY_WAKEUP), value 0 Event: time 1630658212.069128, -- SYN_REPORT Check the dmesg attached. If anything else is needed I will provide it. This bug has been occurring since at least kernel 5.4 on various Ubuntu based distros, and still happens on kernel 5.13 - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: ahmad 2384 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: ahmad 2384 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 21.04 Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 002: ID 04f2:b65d Chicony Electronics Co., Ltd HP TrueVision HD Camera - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 002: ID 04f2:b65d Chicony Electronics Co., Ltd HP TrueVision HD Camera + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: - /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M - /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M - |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M - |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M + |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M + |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: HP HP Laptop 15-da1xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: initrd=\EFI\Pop_OS-37d4cd8c-cd5e-47f5-83e1-f04caf17536d\initrd.img root=UUID=37d4cd8c-cd5e-47f5-83e1-f04caf17536d ro quiet loglevel=0
[Bug 1959101] Re: sync/merge krb5
I struggled as well to use that syncpackage behavior right. The time you trigger the sync is often too far away from the actual migration to -release to happen. I happened to find my own way around (Not perfect, but a suggestion). I call it with --bug and once it has built (but not yet migrated) I say "y". This adds the nice changelog style info to the bug. Then I go to the bug and set it back from "Fix Released" to "Fix Committed" saying that it is in -proposed but we wait for migration to be fully complete. It is a useful update/info on the bug, but still needs someone to - potentially much - later close the bug for real. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959101 Title: sync/merge krb5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1959101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958439] Re: tpm2-tss: builds against OpenSSL 3.0, but fails on execution
This is a universe package that is IMHO rather important, so without some care it might end up broken in jammy-release. Thanks to Robert Reitz for bringing this up here! I tagged it transition-openssl3-jj as that is just as related as the other fallout that we know so far. Since this is cause by the openssl3 transition I wanted have subscribed @schopin and wanted to ask if he could have a look please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958439 Title: tpm2-tss: builds against OpenSSL 3.0, but fails on execution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpm2-tools/+bug/1958439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958439] Re: OpenSSL HMAC mismatch
Thanks for the report, to me that seems to be a consequence of the openssl3 transition [0] Your hint that upstream master has this fixed seems right to me, I found these to most likely be related: https://github.com/tpm2-software/tpm2-tss/commit/e5bb5fb9 Remove deprecated OpenSSL_add_all_algorithms https://github.com/tpm2-software/tpm2-tss/commit/362fda1d Implement EVP_PKEY export/import for OpenSSL 3.0 https://github.com/tpm2-software/tpm2-tss/commit/73d25d68 Drop support for OpenSSL < 1.1.0 https://github.com/tpm2-software/tpm2-tss/commit/aeb5ae44 Test: Use EVP_MAC_xxx with OpenSSL 3.0 https://github.com/tpm2-software/tpm2-tss/commit/f4f528ff FAPI: Change SHA256_Update to EVP_DigestUpdate https://github.com/tpm2-software/tpm2-tss/commit/fdc4f481 Require OpenSSL >= 1.1.0 https://github.com/tpm2-software/tpm2-tss/commit/8fdfadd2 FAPI Test: Change RSA_sign to EVP_PKEY_sign https://github.com/tpm2-software/tpm2-tss/commit/0b24bc2d FAPI Test: Use EVP_PKEY_base_id to detect key type https://github.com/tpm2-software/tpm2-tss/commit/c73be98c FAPI Test: Call EVP_DigestSignInit in the correct order https://github.com/tpm2-software/tpm2-tss/commit/c0a0d376 Test: Remove unused configuration fields So it is about picking that OR going to 3.2 directly which right now is only on -rc0 :-/ [0]: https://lists.ubuntu.com/archives/ubuntu-devel/2021-November/041676.html [1]: https://github.com/tpm2-software/tpm2-tss [2]: https://github.com/tpm2-software/tpm2-tss/releases/tag/3.2.0-rc0 ** Summary changed: - OpenSSL HMAC mismatch + tpm2-tss: builds against OpenSSL 3.0, but fails on execution ** Tags added: transition-openssl3-jj -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958439 Title: tpm2-tss: builds against OpenSSL 3.0, but fails on execution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpm2-tools/+bug/1958439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959665] Re: linux-image-5.4.0-97.110 freezes by accessing cifs shares
Hi Tim, thanks for your afford! Best regards, Kai. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959665 Title: linux-image-5.4.0-97.110 freezes by accessing cifs shares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1502604] Re: autopkgtests fail in LXC testbed
** Changed in: lxc (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1502604 Title: autopkgtests fail in LXC testbed To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1502604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1510108] Re: pre-installed lxc in cloud-image means loss of access to 10.0.X.0/24
Closing as these days we only have LXD preinstalled on those images and LXD does a lot more validation and only creates the networks on first use. ** Changed in: lxc (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1510108 Title: pre-installed lxc in cloud-image means loss of access to 10.0.X.0/24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1510108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1591124] Re: LXC: Cannot create a container with the specific alias "tasks"
** Changed in: lxc (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1591124 Title: LXC: Cannot create a container with the specific alias "tasks" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1591124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1226855] Re: Cannot use open-iscsi inside LXC container
Closing the LXC side of this bug as there's nothing we can really do here. It's either a kernel issue (needs support for their socket option within a network namespace) or an open-iscsi issue where they could have some kind of fallback mechanism. ** Changed in: lxc (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1226855 Title: Cannot use open-iscsi inside LXC container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1226855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522992] Re: /usr/bin/lxc-stop:11:strlen:prune_init_scope:try_get_abs_cgroup:do_cgm_get:cgm_get
** Changed in: lxc (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1522992 Title: /usr/bin/lxc- stop:11:strlen:prune_init_scope:try_get_abs_cgroup:do_cgm_get:cgm_get To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1522992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303756] Re: make lxc-console work non-confusingly by default on touch images
Ubuntu Touch hasn't been a thing for a few years and UBPorts hasn't really been hitting this issue as far as I know. ** Changed in: lxc (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303756 Title: make lxc-console work non-confusingly by default on touch images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1303756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515615] Re: Disk quotas don't work in LXC containers
@brauner do you know what's the state of quotas in a VFS idmapped shifted world? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1515615 Title: Disk quotas don't work in LXC containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1515615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1549391] Re: /proc/sched_debug Information Leak
Closing as it's not really LXC's job to try and change that one. These days we'd recommend distros to change default permissions or ideally get that changed at the kernel level. Short of that, we do have some documented recommendations in our production environment doc for LXD: https://linuxcontainers.org/lxd/docs/master/production-setup/ ** Changed in: lxc (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549391 Title: /proc/sched_debug Information Leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1549391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642767] Re: starting any container with umask 007 breaks host system shutdown. lxc-stop just hangs.
Moving over to the kernel as a userspace process shouldn't be able to cause such a hang regardless of what it does so this looks like a kernel bug (lock related by the looks of it). ** Package changed: lxc (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642767 Title: starting any container with umask 007 breaks host system shutdown. lxc-stop just hangs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1646462] Re: lxc-create cannot setgid
** Changed in: lxc (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646462 Title: lxc-create cannot setgid To manage notifications about this bug go to: https://bugs.launchpad.net/lxc/+bug/1646462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813362] Re: lxc-top flash error and blkio write is always zero
Could you recheck with the current LXC (4.0.12) as the cgroup code was reworked quite extensively. ** Changed in: lxc (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813362 Title: lxc-top flash error and blkio write is always zero To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1813362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857542] Re: lxc-checkpoint needs the criu package
CRIU is once again in the archive (Ubuntu is just following what's in Debian for this one). ** Changed in: lxc (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857542 Title: lxc-checkpoint needs the criu package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1857542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881292] Re: Linux 5.7: autopkgtest failures - lxc-test-cloneconfig && lxc-destroy
Did we ever see this one again or was it just transient? ** Changed in: lxc (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881292 Title: Linux 5.7: autopkgtest failures - lxc-test-cloneconfig && lxc-destroy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1881292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883041] Re: libpam-cgfs fails to create freezer cgroup writable by user
** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883041 Title: libpam-cgfs fails to create freezer cgroup writable by user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1883041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test)
** Changed in: lxc (Ubuntu) Status: In Progress => Fix Released ** Changed in: lxc (Ubuntu Bionic) 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/1886790 Title: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887919] Re: autopkgtest failure with libselinux 3.1
** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887919 Title: autopkgtest failure with libselinux 3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1887919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907307] Re: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.10.0-7.8
Are we still seeing this? The failure looks a lot like it could be a legitimate kernel issue. ** Changed in: lxc (Ubuntu) Status: New => Incomplete ** Changed in: lxc (Ubuntu Focal) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907307 Title: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.10.0-7.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1907307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947811] Re: cgroups broken in impish
Said change is in LXCFS 4.0.12 which is now in jammy ** Changed in: lxcfs (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947811 Title: cgroups broken in impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1947811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959862] [NEW] shutdown command do not turn off machine
Public bug reported: Machine do not turn off after issuing shutdown command either through GUI or terminal. last command displayed is ucsi_acpi USBC000:00: PPM init failed (-110) or systemd-shutdown[1]: Failed to finalize DM devices. ignoring OS version 21.10 Gnome version: 40.4.0 The machine is suppose to turn off but it is left hanging. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Feb 2 21:41:33 2022 InstallationDate: Installed on 2021-02-14 (353 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to impish on 2021-10-20 (105 days ago) VarLogDistupgradeApttermlog: Error: [Errno 13] Permission denied: '/var/log/dist-upgrade/apt-term.log' VarLogDistupgradeTermlog: ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade impish wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959862 Title: shutdown command do not turn off machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1959862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959655] Re: package linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959655 Title: package linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1959655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959756] Re: package linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959756 Title: package linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1959756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891903] Re: "File exists" error while starting container
This bug was fixed in the package lxc - 1:4.0.12-0ubuntu1 --- lxc (1:4.0.12-0ubuntu1) jammy; urgency=medium * Cherry-pick upstream bugfixes (stable-4.0): - 0002-lxc-checkconfig-Fix-bashism.patch - 0003-doc-Fix-reverse-allowlist-denylist.patch (LP: #1957934) * New upstream bugfix release (4.0.12): (https://discuss.linuxcontainers.org/t/lxc-4-0-12-has-been-released/13288) - Fixed CRIU restoration of containers with pre-created veth interfaces - Fixed issue with kernels lacking SMT support - Extended cgroup2 config options in lxc.mount.auto (cgroup2) - lxc-download now relies on HTTPS for validation (avoids GPG issues) * New upstream bugfix release (4.0.11) (LP: #1943441, LP: #1938771, LP: #1891903): (https://discuss.linuxcontainers.org/t/lxc-4-0-11-has-been-released/12427) - Core scheduling support (lxc.sched.core) - riscv64 support in lxc.arch - Significantly improved bash completion profile - Greater use of the new VFS mount API (when supported by the kernel) - Fix containers with empty network namespaces - Handle kernels that lack TIOCGPTPEER - Improve CPU bitmask/id handling (handle skipped CPU numbers) - Reworked the tests to run offline * Bump to debhelper 12 (allows focal SRUs) * Bump standards to 4.6.0.1 * Add lintian overrides for incorrect bashism detection * Remove bash completion install logic (now done upstream) -- Stéphane Graber Wed, 02 Feb 2022 20:48:39 -0500 ** Changed in: lxc (Ubuntu) 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/1891903 Title: "File exists" error while starting container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1891903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938771] Re: lxc-test-rootfs test regression with 4.0.10-0ubuntu3
This bug was fixed in the package lxc - 1:4.0.12-0ubuntu1 --- lxc (1:4.0.12-0ubuntu1) jammy; urgency=medium * Cherry-pick upstream bugfixes (stable-4.0): - 0002-lxc-checkconfig-Fix-bashism.patch - 0003-doc-Fix-reverse-allowlist-denylist.patch (LP: #1957934) * New upstream bugfix release (4.0.12): (https://discuss.linuxcontainers.org/t/lxc-4-0-12-has-been-released/13288) - Fixed CRIU restoration of containers with pre-created veth interfaces - Fixed issue with kernels lacking SMT support - Extended cgroup2 config options in lxc.mount.auto (cgroup2) - lxc-download now relies on HTTPS for validation (avoids GPG issues) * New upstream bugfix release (4.0.11) (LP: #1943441, LP: #1938771, LP: #1891903): (https://discuss.linuxcontainers.org/t/lxc-4-0-11-has-been-released/12427) - Core scheduling support (lxc.sched.core) - riscv64 support in lxc.arch - Significantly improved bash completion profile - Greater use of the new VFS mount API (when supported by the kernel) - Fix containers with empty network namespaces - Handle kernels that lack TIOCGPTPEER - Improve CPU bitmask/id handling (handle skipped CPU numbers) - Reworked the tests to run offline * Bump to debhelper 12 (allows focal SRUs) * Bump standards to 4.6.0.1 * Add lintian overrides for incorrect bashism detection * Remove bash completion install logic (now done upstream) -- Stéphane Graber Wed, 02 Feb 2022 20:48:39 -0500 ** Changed in: lxc (Ubuntu) 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/1938771 Title: lxc-test-rootfs test regression with 4.0.10-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1938771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943441] Re: lxc: lxc-test-parse-config-file failure
This bug was fixed in the package lxc - 1:4.0.12-0ubuntu1 --- lxc (1:4.0.12-0ubuntu1) jammy; urgency=medium * Cherry-pick upstream bugfixes (stable-4.0): - 0002-lxc-checkconfig-Fix-bashism.patch - 0003-doc-Fix-reverse-allowlist-denylist.patch (LP: #1957934) * New upstream bugfix release (4.0.12): (https://discuss.linuxcontainers.org/t/lxc-4-0-12-has-been-released/13288) - Fixed CRIU restoration of containers with pre-created veth interfaces - Fixed issue with kernels lacking SMT support - Extended cgroup2 config options in lxc.mount.auto (cgroup2) - lxc-download now relies on HTTPS for validation (avoids GPG issues) * New upstream bugfix release (4.0.11) (LP: #1943441, LP: #1938771, LP: #1891903): (https://discuss.linuxcontainers.org/t/lxc-4-0-11-has-been-released/12427) - Core scheduling support (lxc.sched.core) - riscv64 support in lxc.arch - Significantly improved bash completion profile - Greater use of the new VFS mount API (when supported by the kernel) - Fix containers with empty network namespaces - Handle kernels that lack TIOCGPTPEER - Improve CPU bitmask/id handling (handle skipped CPU numbers) - Reworked the tests to run offline * Bump to debhelper 12 (allows focal SRUs) * Bump standards to 4.6.0.1 * Add lintian overrides for incorrect bashism detection * Remove bash completion install logic (now done upstream) -- Stéphane Graber Wed, 02 Feb 2022 20:48:39 -0500 ** Changed in: lxc (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943441 Title: lxc: lxc-test-parse-config-file failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1943441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957934] Re: error in man page for lxc.container.conf
This bug was fixed in the package lxc - 1:4.0.12-0ubuntu1 --- lxc (1:4.0.12-0ubuntu1) jammy; urgency=medium * Cherry-pick upstream bugfixes (stable-4.0): - 0002-lxc-checkconfig-Fix-bashism.patch - 0003-doc-Fix-reverse-allowlist-denylist.patch (LP: #1957934) * New upstream bugfix release (4.0.12): (https://discuss.linuxcontainers.org/t/lxc-4-0-12-has-been-released/13288) - Fixed CRIU restoration of containers with pre-created veth interfaces - Fixed issue with kernels lacking SMT support - Extended cgroup2 config options in lxc.mount.auto (cgroup2) - lxc-download now relies on HTTPS for validation (avoids GPG issues) * New upstream bugfix release (4.0.11) (LP: #1943441, LP: #1938771, LP: #1891903): (https://discuss.linuxcontainers.org/t/lxc-4-0-11-has-been-released/12427) - Core scheduling support (lxc.sched.core) - riscv64 support in lxc.arch - Significantly improved bash completion profile - Greater use of the new VFS mount API (when supported by the kernel) - Fix containers with empty network namespaces - Handle kernels that lack TIOCGPTPEER - Improve CPU bitmask/id handling (handle skipped CPU numbers) - Reworked the tests to run offline * Bump to debhelper 12 (allows focal SRUs) * Bump standards to 4.6.0.1 * Add lintian overrides for incorrect bashism detection * Remove bash completion install logic (now done upstream) -- Stéphane Graber Wed, 02 Feb 2022 20:48:39 -0500 ** Changed in: lxc (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957934 Title: error in man page for lxc.container.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1957934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796047] Re: update-ieee-data throws error because of wrong url
** Changed in: ieee-data (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796047 Title: update-ieee-data throws error because of wrong url To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ieee-data/+bug/1796047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917187] Re: lxc cgroup2: containers unbootable
Hmmm, that's an old one. IIRC the real root cause was, that some files possibly included via /usr/share/lxc/config/ubuntu.common.conf still used lxc.cgroup.devices.* instead of lxc.cgroup2.devices.* (the machine was upgraded from bionic to focal). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917187 Title: lxc cgroup2: containers unbootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1917187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958594] Re: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work
Are you guaranteed to be able to know the set of architecture(s) of libgcc_s needed? That's what's prevented me from suggesting a patch like that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958594 Title: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953022] Re: refcount leak in pep_sock_accept
It looks like I lost track of this browser tab a lot longer than I expected. Thanks Hangyu Hua for the fixes! :) ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953022 Title: refcount leak in pep_sock_accept To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959848] Re: "_" not accepted within email addresses for copying
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1959848 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -Moreover- The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: gnome-terminal (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959848 Title: "_" not accepted within email addresses for copying To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1959848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953022] [NEW] refcount leak in pep_sock_accept
*** This bug is a security vulnerability ***
You have been subscribed to a public security bug by Seth Arnold (seth-arnold):
sock_hold(sk) is invoked in pep_sock_accept(),but __sock_put() is not
invoked in subsequent failure branches(pep_accept_conn() != 0).
static struct sock *pep_sock_accept(struct sock *sk, int flags, int *errp,
bool kern)
{
struct pep_sock *pn = pep_sk(sk), *newpn;
struct sock *newsk = NULL;
struct sk_buff *skb;
struct pnpipehdr *hdr;
struct sockaddr_pn dst, src;
int err;
u16 peer_type;
u8 pipe_handle, enabled, n_sb;
u8 aligned = 0;
...
newsk = sk_alloc(sock_net(sk), PF_PHONET, GFP_KERNEL, sk->sk_prot,
kern);
if (!newsk) {
pep_reject_conn(sk, skb, PN_PIPE_ERR_OVERLOAD, GFP_KERNEL);
err = -ENOBUFS;
goto drop;
}
...
sock_hold(sk);< here,sk->sk_refcnt++
newpn->listener = sk;
skb_queue_head_init(>ctrlreq_queue);
newpn->pipe_handle = pipe_handle;
atomic_set(>tx_credits, 0);
newpn->ifindex = 0;
newpn->peer_type = peer_type;
newpn->rx_credits = 0;
newpn->rx_fc = newpn->tx_fc = PN_LEGACY_FLOW_CONTROL;
newpn->init_enable = enabled;
newpn->aligned = aligned;
err = pep_accept_conn(newsk, skb);
if (err) {
sock_put(newsk);< before sock_put(newsk) may need
sk->sk_refcnt--
newsk = NULL;
goto drop;
}
sk_add_node(newsk, >hlist);
drop:
release_sock(sk);
kfree_skb(skb);
*errp = err;
return newsk;
}
My suggestion for the patch:
static struct sock *pep_sock_accept(struct sock *sk, int flags, int *errp,
bool kern)
{
...
err = pep_accept_conn(newsk, skb);
if (err) {
+++ __sock_put(sk);
sock_put(newsk);
newsk = NULL;
goto drop;
}
sk_add_node(newsk, >hlist);
drop:
release_sock(sk);
kfree_skb(skb);
*errp = err;
return newsk;
}
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
refcount leak in pep_sock_accept
https://bugs.launchpad.net/bugs/1953022
You received this bug notification because you are a member of Ubuntu Bugs,
which is subscribed to the bug report.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.11/5.11.0.60.61)
All autopkgtests for the newly accepted linux-meta-hwe-5.11 (5.11.0.60.61) for focal have finished running. The following regressions have been reported in tests triggered by the package: lxc/1:4.0.6-0ubuntu1~20.04.1 (arm64, amd64) nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 (amd64) systemd/245.4-4ubuntu3.15 (arm64, s390x, ppc64el, amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-hwe-5.11 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532314] Re: Buffer overflow in cgmanager
** Changed in: lxc (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: libnih (Ubuntu) Status: Confirmed => Won't Fix -- 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/1532314 Title: Buffer overflow in cgmanager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1532314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916669] Re: autopkgtests flaky for hirsute across various architectures
Seems green lately ** Changed in: lxc (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916669 Title: autopkgtests flaky for hirsute across various architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1916669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917187] Re: lxc cgroup2: containers unbootable
The error you're getting is coming from systemd in the container which for some reason is trying to mount a cgroup1 hierarchy rather than using cgroup2 like the rest of your system. You may be able to workaround that by using `lxc.init_cmd` to pass /sbin/init with additional arguments to change the systemd behavior in the container. ** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917187 Title: lxc cgroup2: containers unbootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1917187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917601] Re: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.8.0-45.51
** Changed in: lxc (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917601 Title: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.8.0-45.51 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1917601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931064] Re: lxc autotest failure with kernel >= 5.13
Marking as invalid as this wasn't an LXC bug but a kernel bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931064 Title: lxc autotest failure with kernel >= 5.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1931064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931064] Re: lxc autotest failure with kernel >= 5.13
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=591a22c14d3f45cc38bd1931c593c221df2f1881 ** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931064 Title: lxc autotest failure with kernel >= 5.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1931064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957934] Re: error in man page for lxc.container.conf
** Changed in: lxc (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957934 Title: error in man page for lxc.container.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1957934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959841] Re: Lower 8 bits are always zero in stackguard value
That's fine. Thanks for the kind explanation. Thank you, Jason Kim -- 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/1959841 Title: Lower 8 bits are always zero in stackguard value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1959841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901452] Re: Upgrade to 20.10 error. acpi-call-dkms : ERROR: Kernel configuration is invalid.
This bug was fixed in the package acpi-call - 1.2.2-1 --- acpi-call (1.2.2-1) unstable; urgency=medium * [e4c61df] Remove '-guest' from Vcs-* URLs * [022a8aa] Use nix-community repository as new upstream (Closes: #989384) * [0776fac] New upstream version 1.2.2 (LP: #1953261, #1901452) * [6ddc66d] Remove all patches (already in new upstream) * [3eb35a3] Bump Standards-Version to 4.6.0 * [2808ee6] Bump debhelper compat to 13 * [2ea6bde] Drop unused lintian overrides - testsuite-autopkgtest-missing - spelling-error-in-changelog -- Raphaël Halimi Wed, 02 Feb 2022 17:07:02 +0100 ** Changed in: acpi-call (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901452 Title: Upgrade to 20.10 error. acpi-call-dkms : ERROR: Kernel configuration is invalid. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1901452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958594] Re: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work
Yes, that's my take as well. I was going to proposed a patch to do just
that but I decided to see if there was another way to just selectively
copy lib{gcc_s,pthread}. I don't think it's worth the hassle, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958594
Title:
Boot error: libgcc_s.so.1 must be installed for pthread_exit to work
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958594/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953261] Re: kernel >= 5.13 BUG: kernel NULL pointer dereference
This bug was fixed in the package acpi-call - 1.2.2-1 --- acpi-call (1.2.2-1) unstable; urgency=medium * [e4c61df] Remove '-guest' from Vcs-* URLs * [022a8aa] Use nix-community repository as new upstream (Closes: #989384) * [0776fac] New upstream version 1.2.2 (LP: #1953261, #1901452) * [6ddc66d] Remove all patches (already in new upstream) * [3eb35a3] Bump Standards-Version to 4.6.0 * [2808ee6] Bump debhelper compat to 13 * [2ea6bde] Drop unused lintian overrides - testsuite-autopkgtest-missing - spelling-error-in-changelog -- Raphaël Halimi Wed, 02 Feb 2022 17:07:02 +0100 ** Changed in: acpi-call (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953261 Title: kernel >= 5.13 BUG: kernel NULL pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959841] Re: Lower 8 bits are always zero in stackguard value
Ah, sorry, I see I lost a race condition :) thanks ** Changed in: gcc-defaults (Ubuntu) Status: New => Invalid -- 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/1959841 Title: Lower 8 bits are always zero in stackguard value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1959841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959841] Re: Lower 8 bits are always zero in stackguard value
Hello, the stack checking is intended to detect simplistic overwrites of stack control structures. If an attacker is able to overwrite a single NUL in the canary with a NUL supplied from an input string, but no further, then the stack control structures are still intact and undamaged. As far as the stack checking is concerned, this is a success. The intention of the 'terminator canary' is that it would be difficult to cause a write with common string functions to go beyond the canary -- they'd stop on the newline, or the NUL, and wouldn't progress beyond that. Can you get strcpy() to go beyond the canary, to the control structures? Thanks -- 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/1959841 Title: Lower 8 bits are always zero in stackguard value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1959841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959844] Re: lagging
Thanks for the bug report. So we can understand the main issue and have clear success criteria for a fix, can you please identify something specific that is too slow? Maybe also take a video of the problem. You can record the screen to a video in ~/Videos by pressing Shift+Ctrl+Alt+R to start and stop recording. Or if that's not enough to show the problem then record a video with a phone. And attach it here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: performance -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959844 Title: lagging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1959844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959523] Re: pychess is broken in Jammy
Should probably pull in the latest version from here: https://github.com/pychess/pychess/releases python3-pychess_1.0.3-1_all.deb seems to work fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959523 Title: pychess is broken in Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pychess/+bug/1959523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959841] Re: Lower 8 bits are always zero in stackguard value
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959841 Title: Lower 8 bits are always zero in stackguard value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1959841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950720] Re: GSYNC bug regression in 495.44 Ubuntu 21.10
Something new (2 hours old) for you to try: https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950720 Title: GSYNC bug regression in 495.44 Ubuntu 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1950720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 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 1959841] [NEW] Lower 8 bits are always zero in stackguard value
*** This bug is a security vulnerability ***
You have been subscribed to a public security bug by Seth Arnold (seth-arnold):
Lower 8bits are always zero in stack guard value, which makes stack
protector cannot detect the following stack smashing:
```
#include
int get_input(char *data)
{
strcpy(data, "01234567");
return 0;
}
// main.c
#include
#include
void *__stack_chk_guard = (void *)0xdeadbeef;
void __stack_chk_fail(void)
{
fprintf(stderr, "Stack smashing detected.\n");
exit(1);
}
void get_input(char *data);
char main(void)
{
char buffer[8] = { 0 };
get_input(buffer);
return buffer[0];
}
```
When I look into the problem with gdb, fs:0x28 (stack guard value) has always
lower 8 bits like
```
0x007fffe190│+0x: 0x0d ("\r"?) ← $rsp
0x007fffe198│+0x0008: 0x3fd2300ef2282e00 <-
0x007fffe1a0│+0x0010: 0x0001 ← $rbp
0x007fffe1a8│+0x0018: 0x0077db6fd0 → <__libc_start_call_main+128> mov
edi, eax
0x007fffe1b0│+0x0020: 0x004040 → (bad)
0x007fffe1b8│+0x0028: 0x00519e → endbr64
0x007fffe1c0│+0x0030: 0x0001
0x007fffe1c8│+0x0038: 0x007fffe2c8 → 0x007fffe577 →
"/home/sukbeom/Workspace/arm/stack_protector/sp"
```
I don't know much about stack protector but I think this should be
fixed. So I report this as a bug related to stack protector to get more
information. Please let me know if there is anything wrong with my
report.
I attach my system information:
$ lsb_release -rd
Description:Ubuntu 21.10
Release:21.10
$ gcc -v
➜ linux git:(study) gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/11/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 11.2.0-7ubuntu2'
--with-bugurl=file:///usr/share/doc/gcc-11/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr
--with-gcc-major-version-only --program-suffix=-11
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib
--enable-libphobos-checking=release --with-target-system-zlib=auto
--enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32
--enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none=/build/gcc-11-ZPT0kp/gcc-11-11.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-11-ZPT0kp/gcc-11-11.2.0/debian/tmp-gcn/usr
--without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
--with-build-config=bootstrap-lto-lean --enable-link-serialization=2
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2)
Thank you.
** Affects: gcc-defaults (Ubuntu)
Importance: Undecided
Status: New
--
Lower 8 bits are always zero in stackguard value
https://bugs.launchpad.net/bugs/1959841
You received this bug notification because you are a member of Ubuntu Bugs,
which is subscribed to the bug report.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta-gcp/5.13.0.1014.13)
All autopkgtests for the newly accepted linux-meta-gcp (5.13.0.1014.13) for impish have finished running. The following regressions have been reported in tests triggered by the package: systemd/248.3-1ubuntu8.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/impish/update_excuses.html#linux-meta-gcp [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955362] Re: epiphany December 2021 XSS issues
** No longer affects: epiphany-browser (Ubuntu Hirsute) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955362 Title: epiphany December 2021 XSS issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1955362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else
** No longer affects: firefox (Ubuntu) ** Bug watch removed: Mozilla Bugzilla #1722369 https://bugzilla.mozilla.org/show_bug.cgi?id=1722369 ** Changed in: gtk+3.0 (Ubuntu Impish) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913775 Title: Copy from Firefox Wayland fails to be pasted anywhere else To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1913775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959421] Re: [22.04 FEAT] Upgrade libica to latest version (crypto) (v4.0)
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959421 Title: [22.04 FEAT] Upgrade libica to latest version (crypto) (v4.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955944] Re: Missing Breaks/Replaces on network-manager-gnome
** Tags added: packaging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955944 Title: Missing Breaks/Replaces on network-manager-gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnma/+bug/1955944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957716] Re: Update for CVE-2021-43860 and CVE-2022-21682
** Changed in: flatpak (Ubuntu) Importance: Undecided => Medium ** Changed in: flatpak (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: flatpak (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: flatpak (Ubuntu Impish) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957716 Title: Update for CVE-2021-43860 and CVE-2022-21682 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1957716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959346] Re: Please merge iniparser 4.1-6 from Debian unstable
** Changed in: iniparser (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959346 Title: Please merge iniparser 4.1-6 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iniparser/+bug/1959346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959757] Re: [SRU] etcd FTBFS on Focal
** Tags added: ftbfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959757 Title: [SRU] etcd FTBFS on Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/etcd/+bug/1959757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959211] Re: Please merge dbus 1.12.20-3 from Debian unstable
** Changed in: dbus (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959211 Title: Please merge dbus 1.12.20-3 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1959211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959241] Re: Merge u-boot-menu 4.0.4 from Debian
** Changed in: u-boot-menu (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959241 Title: Merge u-boot-menu 4.0.4 from Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot-menu/+bug/1959241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911893] Re: latest microcode is not working properly on intel core i9
Hello Asus delivered new BIOS update for the laptop - " Version 309 2021/12/06" (https://rog.asus.com/laptops/rog-flow/rog-g703-series/helpdesk_bios) with description "Optimize system performance". After upgrading BIOS problem solved and I can use laptop with the latest intel microcode. It a SHAME for the ASUS ROG due to fix was delivered AFTER 2 years! Also there is no info about fix, just description "Optimize system performance". Unfortunately premium ASUS ROG laptop with bad quality support. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911893 Title: latest microcode is not working properly on intel core i9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1911893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959850] Re: Network printer suddenly stopped working, cannot be accessed using zeroconf anymore
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1959850/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959850 Title: Network printer suddenly stopped working, cannot be accessed using zeroconf anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1959850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959855] Re: FTBFS against openssl 3
The attachment "validns-1_0.8+git20170804-0ubuntu2_0.8+git20170804-0ubuntu3.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959855 Title: FTBFS against openssl 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/validns/+bug/1959855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959857] Re: xdg-desktop-portal crashed with SIGSEGV in g_mutex_lock()
*** This bug is a duplicate of bug 1958157 *** https://bugs.launchpad.net/bugs/1958157 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1958157, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1959857/+attachment/5558797/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1959857/+attachment/5558799/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1959857/+attachment/5558802/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1959857/+attachment/5558803/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1959857/+attachment/5558804/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1959857/+attachment/5558805/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1959857/+attachment/5558806/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1958157 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959857 Title: xdg-desktop-portal crashed with SIGSEGV in g_mutex_lock() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1959857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959855] Re: FTBFS against openssl 3
** Patch added: "validns-1_0.8+git20170804-0ubuntu2_0.8+git20170804-0ubuntu3.debdiff" https://bugs.launchpad.net/ubuntu/+source/validns/+bug/1959855/+attachment/5558796/+files/validns-1_0.8+git20170804-0ubuntu2_0.8+git20170804-0ubuntu3.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959855 Title: FTBFS against openssl 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/validns/+bug/1959855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1959101] Re: sync/merge krb5
I did, and it asked me to wait for the sync to be complete before closing the bug, this time I obeyed ;) On Wed, Feb 2, 2022, 20:16 Sergio Durigan Junior <1959...@bugs.launchpad.net> wrote: > On Wednesday, February 02 2022, Andreas Hasenack wrote: > > > Sync requested, I'll wait for the package to migrate before closing the > > bug. > > You can also invoke "syncpackage" using the "--bug" option, FWIW. > > -- > Sergio > GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1959101 > > Title: > sync/merge krb5 > > Status in krb5 package in Ubuntu: > In Progress > > Bug description: > We went ahead of debian because of openssl3: > krb5 (1.19.2-0ubuntu1) jammy; urgency=medium > > [ Sam Hartman ] > * New Upstream version > * Depend on tex-gyre, Closes: #997407 > > [Simon Chopin] > * d/p/0012-Fix-softpkcs11-build-issues-with-openssl-3.0.patch: > Cherry-picked from upstream master to fix OpenSSL3 build. > Closes: #995152, LP: #1945795 > >-- Simon Chopin Tue, 30 Nov 2021 > 10:54:17 +0100 > > Debian unstable still has 1.18.3-7, but experimental got 1.19.2-1: > krb5 (1.19.2-1) experimental; urgency=medium > > * New Upstream version > * Include patch to work with OpenSSL 3.0, Closes: #995152 > * Depend on tex-gyre, Closes: #997407 > >-- Sam Hartman Wed, 27 Oct 2021 14:04:42 -0600 > > Since we are already at 1.19.2, we might as well merge/sync with > experimental. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1959101/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=krb5; component=main; > milestone=ubuntu-22.02; status=In Progress; importance=Undecided; assignee= > andr...@canonical.com; > Launchpad-Bug-Tags: needs-merge > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: ahasenack sergiodj > Launchpad-Bug-Reporter: Andreas Hasenack (ahasenack) > Launchpad-Bug-Modifier: Sergio Durigan Junior (sergiodj) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: ahasenack > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959101 Title: sync/merge krb5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1959101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910821] Re: [snap] chromium fails to start with "/snap/chromium/1444/usr/lib/chromium-browser/chrome: error while loading shared libraries: libatk-1.0.so.0: cannot open shared object file: No su
same here, all data gone. what a shit show, like waking up after a car crash feeling fine but no memory. Perhaps devs can consider these kind of things before these things happen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910821 Title: [snap] chromium fails to start with "/snap/chromium/1444/usr/lib/chromium-browser/chrome: error while loading shared libraries: libatk-1.0.so.0: cannot open shared object file: No such file or directory" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1910821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910927] Re: Suspend stopped working since kernel 5.4 (ubuntu 20.04)
Ah, I see the report refers to a Core Duo processor and that is what the T61p has too (Intel T7700 to be precise). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910927 Title: Suspend stopped working since kernel 5.4 (ubuntu 20.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910927] Re: Suspend stopped working since kernel 5.4 (ubuntu 20.04)
Recently I installed Ubuntu 20.04.3 LTS on an old Lenovo laptop (T61p). I was disappointed to discover that suspend did not work (as described in this report, black screen and no way to recover). I tried two version 5 kernels (5.13.0-27-generic and 5.8.0-43-generic). As a wild guess I downloaded 4.19.0-041900-generic and suspend works for me with that kernel. I would prefer to run a newer kernel but I need suspend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910927 Title: Suspend stopped working since kernel 5.4 (ubuntu 20.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1959101] Re: sync/merge krb5
On Wednesday, February 02 2022, Andreas Hasenack wrote: > Sync requested, I'll wait for the package to migrate before closing the > bug. You can also invoke "syncpackage" using the "--bug" option, FWIW. -- Sergio GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959101 Title: sync/merge krb5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1959101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959581] Re: OCFS2 intermittently not mountable on a second Node in Ubuntu 20.04.3 LTS
Thanks for the bug report, Norbert. First of all, I noticed that the ocfs2-tools package contains a delta relative to the Debian package. The delta is trivial, though, and is there just to make sure the package is built only on support architectures (see bug #1745155 for more details). I don't think it is what's causing this bug. Debian itself carries a few distro-specific patches. Upon inspecting them, I don't think they're directly related to this issue either. So we're left with two possibilities here: 1) This is an upstream bug (which may have been fixed meanwhile), or 2) This is a bug elsewhere (Linux kernel, maybe?) I did some research on the internet and found some interesting things. First, I found that it's really hard to obtain the list of patches that have been applied to a package on Oracle [GNU/]Linux! I knew that theoretically already, but now I have seen it for real. Anyway, I was trying to take a look at their package to see if anything strange/interesting came up. No deal. Then, I decided to do a search for some terms from your bug descriptions. It caught my attention that you were able to provide a stack trace (thanks, by the way!), so I tried searching for one of the functions listed there. And I did find something interesting: https://support.oracle.com/knowledge/Oracle%20Linux%20and%20Virtualization/2375753_1.html Both the descript of the problem (high I/O wait) and the stack trace provided in the link above match what you're seeing. I don't have an Oracle account so I can't see the rest of the article, but I'm assuming you do, so could you please take a look and see if there is anything useful for you there? Meanwhile, I'm going to mark this bug as Incomplete (which is the closest we have to a "Waiting" state). When you have more information, please mark it as New again. Thanks. ** Changed in: ocfs2-tools (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959581 Title: OCFS2 intermittently not mountable on a second Node in Ubuntu 20.04.3 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/1959581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
