[Bug 1928595] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1928595/+attachment/5498031/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928595 Title: cheese camera app not display anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928595] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1928595/+attachment/5498025/+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/1928595 Title: cheese camera app not display anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928595] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1928595/+attachment/5498029/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928595 Title: cheese camera app not display anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928595] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1928595/+attachment/5498030/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928595 Title: cheese camera app not display anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928595] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1928595/+attachment/5498026/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928595 Title: cheese camera app not display anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928595] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1928595/+attachment/5498028/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928595 Title: cheese camera app not display anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928595] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1928595/+attachment/5498027/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928595 Title: cheese camera app not display anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928595] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1928595/+attachment/5498024/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928595 Title: cheese camera app not display anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928595] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1928595/+attachment/5498023/+files/PaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928595 Title: cheese camera app not display anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928595] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1928595/+attachment/5498022/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928595 Title: cheese camera app not display anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928595] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1928595/+attachment/5498021/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928595 Title: cheese camera app not display anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928595] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1928595/+attachment/5498020/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928595 Title: cheese camera app not display anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928595] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1928595/+attachment/5498019/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928595 Title: cheese camera app not display anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928595] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1928595/+attachment/5498018/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928595 Title: cheese camera app not display anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928595] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1928595/+attachment/5498017/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928595 Title: cheese camera app not display anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928595] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1928595/+attachment/5498016/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928595 Title: cheese camera app not display anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928595] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1928595/+attachment/5498015/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928595 Title: cheese camera app not display anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928595] Re: cheese camera app not display anything
apport information ** Tags added: apport-collected ** Description changed: when opening the cheese camera app nothing is displayed it shows nothing just a black screen on my end tested on Ubuntu 21. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: cheese 3.38.0-3 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 16 11:46:58 2021 InstallationDate: Installed on 2021-05-14 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Hewlett-Packard HP 15 TS Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: cheese3.38.0-3 cheese-common 3.38.0-3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2014 dmi.bios.release: 15.22 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.26 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.26 dmi.modalias: dmi:bvnInsyde:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 TS Notebook PC dmi.product.sku: G9D75UA#ABA dmi.product.version: 097412405F0620180 dmi.sys.vendor: Hewlett-Packard + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu65 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: familypc 1357 F pulseaudio + /dev/snd/controlC0: familypc 1357 F pulseaudio + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 21.04 + InstallationDate: Installed on 2021-05-14 (2 days ago) + InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) + MachineType: Hewlett-Packard HP 15 TS Notebook PC + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=c4c005df-0176-4582-a70b-d2a43dc51b21 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 + RelatedPackageVersions: + linux-restricted-modules-5.11.0-17-generic N/A + linux-backports-modules-5.11.0-17-generic N/A + linux-firmware 1.197 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: hirsute wayland-session + Uname: Linux 5.11.0-17-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 04/24/2014 + dmi.bios.release: 15.22 + dmi.bios.vendor: Insyde + dmi.bios.version: F.16 + dmi.board.asset.tag: Type2 - Board Asset Tag + dmi.board.name: 2211 + dmi.board.vendor: Hewlett-Packard + dmi.board.version: 86.26 + dmi.chassis.asset.tag: Chassis Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: Hewlett-Packard + dmi.chassis.version: Chassis Version + dmi.ec.firmware.release: 86.26 + dmi.modalias: dmi:bvnInsyde:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion: + dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV + dmi.product.name: HP 15 TS Notebook PC + dmi.product.sku: G9D75UA#ABA + dmi.product.version: 097412405F0620180 + dmi.sys.vendor: Hewlett-Packard ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1928595/+attachment/5498014/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928595 Title: cheese camera app not display anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928595] [NEW] cheese camera app not display anything
Public bug reported: when opening the cheese camera app nothing is displayed it shows nothing just a black screen on my end tested on Ubuntu 21. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: cheese 3.38.0-3 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 16 11:46:58 2021 InstallationDate: Installed on 2021-05-14 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Hewlett-Packard HP 15 TS Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: cheese3.38.0-3 cheese-common 3.38.0-3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2014 dmi.bios.release: 15.22 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.26 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.26 dmi.modalias: dmi:bvnInsyde:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 TS Notebook PC dmi.product.sku: G9D75UA#ABA dmi.product.version: 097412405F0620180 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gstreamer-error hirsute 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/1928595 Title: cheese camera app not display anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928590] [NEW] slow pc resposnisivnes when using multple programs
Public bug reported: sometimes when using multaple programs on Ubuntu 21 it causes some parts of Ubuntu to freeze up. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 16 11:27:05 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:2211] InstallationDate: Installed on 2021-05-14 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Hewlett-Packard HP 15 TS Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=c4c005df-0176-4582-a70b-d2a43dc51b21 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2014 dmi.bios.release: 15.22 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.26 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.26 dmi.modalias: dmi:bvnInsyde:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 TS Notebook PC dmi.product.sku: G9D75UA#ABA dmi.product.version: 097412405F0620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute performance ubuntu 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/1928590 Title: slow pc resposnisivnes when using multple programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1928590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801642] Re: Bluetooth mouse sleeps after 5 seconds of inactivity, but btusb.enable_autosuspend=0 fixes it
The problem is clearly visible on a Dell Precision 5750. On a ThinkPad P1 Gen 3 the mouse "freezing" effect is barely noticeable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801642 Title: Bluetooth mouse sleeps after 5 seconds of inactivity, but btusb.enable_autosuspend=0 fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928475] [NEW] Xorg freeze when booting up
Public bug reported: when booting up Ubuntu 21 it hangs for a few minutes then it becomes responsive it should not hang ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 14 10:42:48 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: I don't know GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:2211] InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Hewlett-Packard HP 15 TS Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=c4c005df-0176-4582-a70b-d2a43dc51b21 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2014 dmi.bios.release: 15.22 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.26 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.26 dmi.modalias: dmi:bvnInsyde:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 TS Notebook PC dmi.product.sku: G9D75UA#ABA dmi.product.version: 097412405F0620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze hirsute ubuntu 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/1928475 Title: Xorg freeze when booting up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1928475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801642] Re: Bluetooth mouse sleeps after 5 seconds of inactivity, but btusb.enable_autosuspend=0 fixes it
I'm seeing this annoying issue with Ubuntu 20.04 running the linux- oem-20.04b kernel (currently 5.10.0-1026-oem). The above workaround fixes it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801642 Title: Bluetooth mouse sleeps after 5 seconds of inactivity, but btusb.enable_autosuspend=0 fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928407] [NEW] Screen not locked when coming out of suspend/hibernate
Public bug reported: when using my hp if my screen is a sleep and i wake it up it dosen't ask me for my password it should ask me i'm using Ubuntu 21 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 13 21:41:23 2021 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver Symptom: security Title: Screen not locked when coming out of suspend/hibernate UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute 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/1928407 Title: Screen not locked when coming out of suspend/hibernate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1928407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928406] [NEW] [HP 15 TS Notebook PC, Realtek ALC3227, Speaker, Internal] Background noise or low volume
Public bug reported: speaker audio is low compared to windows 10 the sound needs to be better optimized im using ubuntu 21 it should sound the same as in windows 10 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: familypc 1345 F pulseaudio /dev/snd/controlC1: familypc 1345 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 13 21:31:32 2021 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [HP 15 TS Notebook PC, Realtek ALC3227, Speaker, Internal] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2014 dmi.bios.release: 15.22 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.26 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.26 dmi.modalias: dmi:bvnInsyde:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 TS Notebook PC dmi.product.sku: G9D75UA#ABA dmi.product.version: 097412405F0620180 dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute 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/1928406 Title: [HP 15 TS Notebook PC, Realtek ALC3227, Speaker, Internal] Background noise or low volume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1928406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927802] [NEW] ALSA: cannot set period size to 1024 frames for capture with sofhdadsp [sof-hda-dsp] Instead buffer sizes of 1008, 240, 120 work
Public bug reported: This was first reported in Bug #1872244 by John Smith on 2020-04-11 That bug report was converted into a question: question #692397: I reported this on that thread however have heard no response. However, I consider it to be a bug as it is not possible to configure the standard power of 2 buffer sizes. Instead buffer sizes of 1008, 240, 120 work. The man page states that they should be powers of 2, and most jack audio software fails to work properly. My card is a card 1: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 0/1 Subdevice #0: subdevice #0 uname -a Linux rtx 5.8.0-50-generic #56~20.04.1-Ubuntu SMP Mon Apr 12 21:46:35 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux All software has been updated to the latest versions. apt-cache policy jackd jackd: Installed: 5+nmu1 Candidate: 5+nmu1 Version table: *** 5+nmu1 500 500 http://co.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://co.archive.ubuntu.com/ubuntu focal/universe i386 Packages 100 /var/lib/dpkg/status With the default configuration jackd -R -d alsa -d hw:1,0 ... ALSA: cannot set period size to 1024 frames for capture ALSA: cannot configure capture channel As reported jackd starts with a buffer size of 1008, a non standard, non power of 2 jackd -R -d alsa -d hw:1,0 -p 1008 creating alsa driver ... hw:1,0|hw:1,0|1008|2|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz, period = 1008 frames (21.0 ms), buffer = 2 periods ALSA: final selected sample format for capture: 24bit little-endian ALSA: use 2 periods for capture ALSA: final selected sample format for playback: 24bit little-endian ALSA: use 2 periods for playback I consider this a bug as the manual page for jackd states -p, --period int Specify the number of frames between JACK process() calls. This value must be a power of 2, and the default is 1024. And the current situation is that the only way jackd starts is with a non power of 2. Also buffer sizes of 240, 120 works jackd -R -d alsa -d hw:1,0 -p 240 creating alsa driver ... hw:1,0|hw:1,0|240|2|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz, period = 240 frames (5.0 ms), buffer = 2 periods jackd -R -d alsa -d hw:1,0 -p 120 creating alsa driver ... hw:1,0|hw:1,0|120|2|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz, period = 120 frames (2.5 ms), buffer = 2 periods FYI a buffer size of 48 also works however I get another message (maybe because I am not running with a low latency kernel ... yet) Please see attachment for details. ** Affects: jackd-defaults (Ubuntu) Importance: Undecided Status: New ** Attachment added: "jack_buffer_bug.txt" https://bugs.launchpad.net/bugs/1927802/+attachment/5495609/+files/jack_buffer_bug.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927802 Title: ALSA: cannot set period size to 1024 frames for capture with sofhdadsp [sof-hda-dsp] Instead buffer sizes of 1008, 240, 120 work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd-defaults/+bug/1927802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918482] Re: Update for CVE-2021-21381
I've also done some exploratory testing of .desktop icon related tests from the test plan on a Bionic VM and things are working normally. $ apt policy flatpak flatpak: Installed: 1.0.9-0ubuntu0.3 Candidate: 1.0.9-0ubuntu0.3 Version table: *** 1.0.9-0ubuntu0.3 500 500 http://ppa.launchpad.net/ubuntu-security-proposed/ppa/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 1.0.9-0ubuntu0.2 500 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages 0.11.3-3 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918482 Title: Update for CVE-2021-21381 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1918482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926819] Re: Empty MOTD on up-to-date systems (includes fix)
I agree with Aaron and Daniel. I have a custom MOTD generation script that uses the output of updater-notifier `head -qn 2 /var/lib/update- notifier/updates-available`. Not having any text in that file if there are no updates available breaks the layout of the MOTD output. Regardless of my custom setup, having the blank lines in the default MOTD generated by `/etc/motd.d/90-updates-available` does make me think something is broken. It's nice to have the validation of "0 packages can be updated", IMO. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926819 Title: Empty MOTD on up-to-date systems (includes fix) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1926819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927064] [NEW] Bluetooth toggle not working in Ubuntu 21.04
Public bug reported: After updating my OS from 20.10 to 21.04 the Bluetooth service remains turned off even when I turn the toggle switch on. The toggle is not working, neither from the top bar dropdown menu nor from the settings window. Switching on the toggle did not have any effect. I have tried using these commands in the terminal: sudo modprobe -r btusb sudo modprobe btusb They worked once, then when I toggle off and toggle on bluetooth it remains turned off. I have restart the system for the commands to work again I also tried from the terminal: sudo systemctl restart Bluetooth Again it did restart the bluetooth service but if I toggle off and then on again bluetooth service remains off. As before I have to restart the system for the command to work. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrew 1376 F pulseaudio /dev/snd/controlC0: andrew 1376 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue May 4 09:37:29 2021 InstallationDate: Installed on 2021-04-15 (18 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Acer Aspire E5-572G ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=6b9d5149-b57c-405b-802b-9e82a0fe23e3 ro quiet splash resume=UUID=69d3cfd8-3a1a-4a9e-b158-4c66cfe64a1a vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-04-22 (11 days ago) dmi.bios.date: 12/17/2014 dmi.bios.release: 1.3 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HWS dmi.board.vendor: Acer dmi.board.version: V1.03 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd12/17/2014:br1.3:efr1.3:svnAcer:pnAspireE5-572G:pvrV1.03:rvnAcer:rnEA50_HWS:rvrV1.03:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-572G dmi.product.sku: Aspire E5-572G_0922_V1.03 dmi.product.version: V1.03 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session ** Attachment added: "bluetoot-toogle-1r.png" https://bugs.launchpad.net/bugs/1927064/+attachment/5494634/+files/bluetoot-toogle-1r.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927064 Title: Bluetooth toggle not working in Ubuntu 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926856] [NEW] Dismissing reminder for recurring meeting removes from all instances
Public bug reported: See upstream bug report https://gitlab.gnome.org/GNOME/evolution- ews/-/issues/144 . It is reported as fixed in Evolution 3.40. Using the Gnome Evolution email and calendar client with an Exchange account. When a reminder comes up for an instance of a recurring meeting which was added from an Exchange invite email, pressing the "Dismiss" button will remove reminders from all instances of that meeting, so that reminders do not appear for future instances. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evolution-ews 3.36.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 1 18:01:17 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution-ews UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution-ews (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926856 Title: Dismissing reminder for recurring meeting removes from all instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-ews/+bug/1926856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+
Installed and booted into the newly supplied kernel: root@jenkins-lon02-02-general-swarm-node-03:~# dpkg -l | grep linux | grep 144 ii linux-image-unsigned-4.15.0-144-generic 4.15.0-144.148~LP1926081.2 amd64Linux kernel image for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.15.0-144-generic4.15.0-144.148~LP1926081.2 amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP root@jenkins-lon02-02-general-swarm-node-03:~# uname -r 4.15.0-144-generic root@jenkins-lon02-02-general-swarm-node-03:~# uptime 08:06:22 up 19 min, 1 user, load average: 0.74, 0.31, 0.21 root@jenkins-lon02-02-general-swarm-node-03:~# ls -l /boot/ total 201933 -rw-r--r-- 1 root root 1537161 Jul 17 2018 abi-4.15.0-29-generic -rw-r--r-- 1 root root 217414 Mar 24 12:47 config-4.15.0-141-generic -rw-r--r-- 1 root root 217426 Apr 28 09:46 config-4.15.0-144-generic -rw-r--r-- 1 root root 216807 Jul 17 2018 config-4.15.0-29-generic -rw-r--r-- 1 root root 237757 Apr 12 17:02 config-5.4.0-72-generic drwxr-xr-x 5 root root 1024 Apr 29 04:06 grub -rw-r--r-- 1 root root 43066106 Apr 15 09:40 initrd.img-4.15.0-141-generic -rw-r--r-- 1 root root 24589989 Apr 29 04:06 initrd.img-4.15.0-144-generic -rw-r--r-- 1 root root 39975786 Apr 15 08:14 initrd.img-4.15.0-29-generic -rw-r--r-- 1 root root 44490420 Apr 27 04:50 initrd.img-5.4.0-72-generic drwx-- 2 root root12288 Apr 15 07:55 lost+found -rw-r--r-- 1 root root0 Jul 17 2018 retpoline-4.15.0-29-generic -rw--- 1 root root 4081420 Mar 24 12:47 System.map-4.15.0-141-generic -rw--- 1 root root 4081469 Apr 28 09:46 System.map-4.15.0-144-generic -rw--- 1 root root 4040379 Jul 17 2018 System.map-4.15.0-29-generic -rw--- 1 root root 4585968 Apr 12 17:02 System.map-5.4.0-72-generic -rw--- 1 root root 8445600 Mar 24 11:00 vmlinuz-4.15.0-141-generic -rw--- 1 root root 8447776 Apr 28 09:46 vmlinuz-4.15.0-144-generic -rw--- 1 root root 8257272 Jul 17 2018 vmlinuz-4.15.0-29-generic -rw--- 1 root root 9445632 Apr 12 17:15 vmlinuz-5.4.0-72-generic I've run my test through 5 times, and there has been no observed leak in the writeback queue/memory used, so everything still looks good from my side. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926081 Title: nr_writeback memory leak in kernel 4.15.0-137+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+
Tim, I'll cordon off the machine we've been using again and run some tests with this new kernel, hopefully I'll be able to do it today. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926081 Title: nr_writeback memory leak in kernel 4.15.0-137+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+
Awesome, 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/1926081 Title: nr_writeback memory leak in kernel 4.15.0-137+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+
Good news on the custom -144 kernel you provided: root@jenkins-lon02-02-general-swarm-node-03:~# uname -r 4.15.0-144-generic root@jenkins-lon02-02-general-swarm-node-03:~# dpkg -l | grep 144 ii linux-image-unsigned-4.15.0-144-generic 4.15.0-144.148~LP1926081.1 amd64Linux kernel image for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.15.0-144-generic4.15.0-144.148~LP1926081.1 amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP root@jenkins-lon02-02-general-swarm-node-03:~# uptime 08:53:37 up 48 min, 1 user, load average: 1.22, 3.54, 3.05 root@jenkins-lon02-02-general-swarm-node-03:~# grep "writeback" /proc/vmstat nr_writeback 0 nr_writeback_temp 0 I've run through my testcase 3 times on this new kernel and I've not seen any permanent increase in the `nr_writeback` value, it always returns to zero, which is great. So from my end, this looks really good - is there anything else you'd like me to do or test, or is this good enough to pull them in for the -144 update? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926081 Title: nr_writeback memory leak in kernel 4.15.0-137+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+
Thank you both, I'll give that kernel a go now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926081 Title: nr_writeback memory leak in kernel 4.15.0-137+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+
So, good news. I pulled in the ubuntu kernel sources and applied the main patch I had previously identified (https://github.com/torvalds/linux/commit/c3cc39118c3610eb6ab4711bc624af7fc48a35fe). Looking at the other patch (https://github.com/torvalds/linux/commit/e27be240df53), that seems to be related to the accuracy of returned statistics which is not something that my testcase is going to show up. I built a version of the 4.15.0-142 kernel with patch, and booted back into it, and with two iterations of my testcase my `nr_writeback` value has ended up on zero - which is excellent news. From previous runs it has never failed to leak, so this looks good to me. I will run it some more, but it is safe to say I am pretty happy at this point. To that end, I believe that https://github.com/torvalds/linux/commit/c3cc39118c3610eb6ab4711bc624af7fc48a35fe "mm: memcontrol: fix NR_WRITEBACK leak in memcg and system stats" does indeed fix this issue and the symptoms I have reported above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926081 Title: nr_writeback memory leak in kernel 4.15.0-137+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+
Guilherme, thank you for your kind words :) I have been trying to reproduce this bug on several other systems that I have access to in our cloud account, but I have been unable to reproduce it on a VM (either with SAN or local SSD storage). The main set of servers where this has been seen by us are bare-metal servers with a RAID card backed by SSDs - it's possible that a combination of the resources available on the machine (CPU, RAM, disk IO) cause this bug to be more reproducible with my basic testcase. I have taken a server out of production and rebooted it into the 4.15 kernel (4.15.0-141-generic) where the issue is able to be seen. I confirmed my testcase still reproduces the issue here, and it does - nr_writeback is currently stuck at 2641 after one iteration. I have supplied the apport collected information from that server, which is now attached to this issue. This is my first bug report on Launchpad, so I am as yet unfamiliar with the process of testing the potential patches I need. Are you suggesting that I follow the process to rebuild the kernel (https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel) including the patches you have mentioned? Assuming that is the correct course of action I'll attempt to follow the instructions and do that, and report back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926081 Title: nr_writeback memory leak in kernel 4.15.0-137+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926081] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1926081/+attachment/5492737/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926081 Title: nr_writeback memory leak in kernel 4.15.0-137+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926081] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1926081/+attachment/5492736/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926081 Title: nr_writeback memory leak in kernel 4.15.0-137+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926081] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1926081/+attachment/5492735/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926081 Title: nr_writeback memory leak in kernel 4.15.0-137+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926081] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1926081/+attachment/5492734/+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/1926081 Title: nr_writeback memory leak in kernel 4.15.0-137+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926081] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1926081/+attachment/5492733/+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/1926081 Title: nr_writeback memory leak in kernel 4.15.0-137+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926081] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1926081/+attachment/5492731/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926081 Title: nr_writeback memory leak in kernel 4.15.0-137+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926081] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1926081/+attachment/5492730/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926081 Title: nr_writeback memory leak in kernel 4.15.0-137+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926081] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1926081/+attachment/5492729/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926081 Title: nr_writeback memory leak in kernel 4.15.0-137+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+
apport information
** Tags added: apport-collected
** Description changed:
Ubuntu 18.04.5 4.15.0 LTS kernels at version 4.15.0-137 and above contain a
memory leak due to the inclusion of patch from the upstream kernel, but not the
fix for that patch which was released later.
This issue manifests itself as an increasing amount of memory used by
the writeback queue, which never returns to zero. This can been seen
either as the value of `nr_writeback` in /proc/vmstat, or the value of
`Writeback` in /proc/meminfo.
Ordinarily these values should be at or around zero, but on our servers
we observe the `nr_writeback` value increasing to over 8 million, (32GB
of memory), at which point it isn't long before the system IO slows to a
crawl (tens of Kb/s). Our servers have 256GB of memory, and are
performing many CI related activities - this issue appears to be related
to concurrent writing to disk, and can be demonstrated with a simple
testcase (see later).
On our heavily used systems this memory leak can result in an unstable
server after 2-3 days, requiring a reboot to fix it.
After much investigation the issue appears to be because the patch "mm:
memcontrol: fix excessive complexity in memory.stat reporting" was
brought in to the 4.15.0-137 Ubuntu kernel (see
https://launchpad.net/ubuntu/+source/linux/4.15.0-137.141) as part of "
Bionic update: upstream stable patchset 2021-01-25 (LP: #1913214)",
however in the mainline kernel there was a follow up patch because this
initial patch introduced concurrency issues. The patch "mm: memcontrol:
fix NR_WRITEBACK leak in memcg and system stats" is required, and should
be brought into the Ubuntu packaged kernel to fix the issues reported.
The required patch is here:
https://github.com/torvalds/linux/commit/c3cc39118c3610eb6ab4711bc624af7fc48a35fe
and was committed a few weeks after the original (broken) patch:
https://github.com/torvalds/linux/commit/a983b5ebee57209c99f68c8327072f25e0e6e3da
I have checked the release notes for Ubuntu versions -137 to -143, and
none include this second patch that should fix the issue. (I checked
https://people.canonical.com/~kernel/info/kernel-version-map.html for
all the kernel versions, and then visited each changelog page in turn,
e.g. https://launchpad.net/ubuntu/+source/linux/4.15.0-143.147 looking
for "mm: memcontrol: fix NR_WRITEBACK leak in memcg and system stats").
We do not observe this on the 5.4.0 kernel (supported HWE kernel on
18.05.5), which includes this second patch. That kernel may also include
other patches, so we do not know if any other fixes are also required,
but the one we have linked above seems to definitely be needed, and
seems to match our symptoms.
Testcase:
The following is enough to permanently increase the value of
`nr_writeback` on our systems (by about 2000 during most executions):
```
date
grep nr_writeback /proc/vmstat
mkdir -p /docker/testfiles/{1..5}
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/1/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/2/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/3/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/4/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/5/file.% bs=4k count=10 status=none' &
wait $(jobs -p)
grep nr_writeback /proc/vmstat
date
```
Subsequent iterations of the test raise it further, and on a system
doing a lot of writing from a lot of different processes, it can rise
quickly.
System details:
lsb_release -rd
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Affected kernel: 4.15.0-137 onwards (current latest version tried was
4.15.0-142)
e.g.
apt-cache policy linux-image-4.15.0-141-generic
linux-image-4.15.0-141-generic:
Installed: 4.15.0-141.145
Candidate: 4.15.0-141.145
Version table:
*** 4.15.0-141.145 500
500 http://mirrors.service.networklayer.com/ubuntu
bionic-updates/main amd64 Packages
500 http://mirrors.service.networklayer.com/ubuntu
bionic-security/main amd64 Packages
100 /var/lib/dpkg/status
According to https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies I
should include additional information from the server, but at this stage
we have upgraded all our affected systems to 5.4.0, and therefore the
kernel versions do not match those with this issue.
We likely have other servers used in other services that are not as
heavily loaded that have not been as affected by this issue - and
therefore and I may be able to get the equivalent diagnostics from there
after confirming
[Bug 1918482] Re: Update for CVE-2021-21381
@Steve Beattie, was there any progress on this or anything I can do to help ? Or is it just stuck in a queue of items to be reviewed? :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918482 Title: Update for CVE-2021-21381 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1918482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+
I did not initially run the `apport-collect` command as the servers on which I observed this bug have been upgraded to use the 5.4.0 kernel to mitigate the issue (as mentioned in the initial report), therefore the kernel related information may be misleading. I will endeavour to find a server that is exhibiting this issue that remains on an impacted kernel, however I cannot do so today, and given that I have identified a required upstream patch I believe some progress can be made with this bug without this information. If an `apport-collect` command on a server that has been upgraded to the newer kernel is still useful, please let me know and I can see if I can generate the information there. I will attempt to find a server that has not been upgraded, replicate the issue, and then will upload the required logs from that server. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926081 Title: nr_writeback memory leak in kernel 4.15.0-137+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926081] [NEW] nr_writeback memory leak in kernel 4.15.0-137+
Public bug reported:
Ubuntu 18.04.5 4.15.0 LTS kernels at version 4.15.0-137 and above contain a
memory leak due to the inclusion of patch from the upstream kernel, but not the
fix for that patch which was released later.
This issue manifests itself as an increasing amount of memory used by
the writeback queue, which never returns to zero. This can been seen
either as the value of `nr_writeback` in /proc/vmstat, or the value of
`Writeback` in /proc/meminfo.
Ordinarily these values should be at or around zero, but on our servers
we observe the `nr_writeback` value increasing to over 8 million, (32GB
of memory), at which point it isn't long before the system IO slows to a
crawl (tens of Kb/s). Our servers have 256GB of memory, and are
performing many CI related activities - this issue appears to be related
to concurrent writing to disk, and can be demonstrated with a simple
testcase (see later).
On our heavily used systems this memory leak can result in an unstable
server after 2-3 days, requiring a reboot to fix it.
After much investigation the issue appears to be because the patch "mm:
memcontrol: fix excessive complexity in memory.stat reporting" was
brought in to the 4.15.0-137 Ubuntu kernel (see
https://launchpad.net/ubuntu/+source/linux/4.15.0-137.141) as part of "
Bionic update: upstream stable patchset 2021-01-25 (LP: #1913214)",
however in the mainline kernel there was a follow up patch because this
initial patch introduced concurrency issues. The patch "mm: memcontrol:
fix NR_WRITEBACK leak in memcg and system stats" is required, and should
be brought into the Ubuntu packaged kernel to fix the issues reported.
The required patch is here:
https://github.com/torvalds/linux/commit/c3cc39118c3610eb6ab4711bc624af7fc48a35fe
and was committed a few weeks after the original (broken) patch:
https://github.com/torvalds/linux/commit/a983b5ebee57209c99f68c8327072f25e0e6e3da
I have checked the release notes for Ubuntu versions -137 to -143, and
none include this second patch that should fix the issue. (I checked
https://people.canonical.com/~kernel/info/kernel-version-map.html for
all the kernel versions, and then visited each changelog page in turn,
e.g. https://launchpad.net/ubuntu/+source/linux/4.15.0-143.147 looking
for "mm: memcontrol: fix NR_WRITEBACK leak in memcg and system stats").
We do not observe this on the 5.4.0 kernel (supported HWE kernel on
18.05.5), which includes this second patch. That kernel may also include
other patches, so we do not know if any other fixes are also required,
but the one we have linked above seems to definitely be needed, and
seems to match our symptoms.
Testcase:
The following is enough to permanently increase the value of
`nr_writeback` on our systems (by about 2000 during most executions):
```
date
grep nr_writeback /proc/vmstat
mkdir -p /docker/testfiles/{1..5}
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/1/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/2/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/3/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/4/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/5/file.% bs=4k count=10 status=none' &
wait $(jobs -p)
grep nr_writeback /proc/vmstat
date
```
Subsequent iterations of the test raise it further, and on a system
doing a lot of writing from a lot of different processes, it can rise
quickly.
System details:
lsb_release -rd
Description:Ubuntu 18.04.5 LTS
Release:18.04
Affected kernel: 4.15.0-137 onwards (current latest version tried was
4.15.0-142)
e.g.
apt-cache policy linux-image-4.15.0-141-generic
linux-image-4.15.0-141-generic:
Installed: 4.15.0-141.145
Candidate: 4.15.0-141.145
Version table:
*** 4.15.0-141.145 500
500 http://mirrors.service.networklayer.com/ubuntu bionic-updates/main
amd64 Packages
500 http://mirrors.service.networklayer.com/ubuntu bionic-security/main
amd64 Packages
100 /var/lib/dpkg/status
According to https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies I
should include additional information from the server, but at this stage
we have upgraded all our affected systems to 5.4.0, and therefore the
kernel versions do not match those with this issue.
We likely have other servers used in other services that are not as
heavily loaded that have not been as affected by this issue - and
therefore and I may be able to get the equivalent diagnostics from there
after confirming that they demonstrate the same issue with my testcase
Workaround:
After several weeks narrowing this down, our only option was to upgrade
our servers to the 5.4 kernel, which is included as the HWE kernel in
18.04.5:
apt update && apt install
[Bug 1872244] Re: Jack audio not working on Ubuntu 20.04 running on a Thinkpad Carbon X1 (7th gen)
Please can you look into this. It has been marked as Invalid, however, it is not a support request as has been assumed. My card is a card 1: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 0/1 Subdevice #0: subdevice #0 uname -a Linux rtx 5.8.0-50-generic #56~20.04.1-Ubuntu SMP Mon Apr 12 21:46:35 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux All software has been updated to the latest versions. With the default configuration jackd -R -d alsa -d hw:1,0 ... ALSA: cannot set period size to 1024 frames for capture ALSA: cannot configure capture channel As reported jackd starts with a buffer size of 1008, a non standard, non power of 2 jackd -R -d alsa -d hw:1,0 -p 1008 creating alsa driver ... hw:1,0|hw:1,0|1008|2|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz, period = 1008 frames (21.0 ms), buffer = 2 periods ALSA: final selected sample format for capture: 24bit little-endian ALSA: use 2 periods for capture ALSA: final selected sample format for playback: 24bit little-endian ALSA: use 2 periods for playback I consider this a bug as the manual page for jackd states -p, --period int Specify the number of frames between JACK process() calls. This value must be a power of 2, and the default is 1024. And the current situation is that the only way jackd starts is with a non power of 2. Also buffer sizes of 240, 120 works jackd -R -d alsa -d hw:1,0 -p 240 creating alsa driver ... hw:1,0|hw:1,0|240|2|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz, period = 240 frames (5.0 ms), buffer = 2 periods jackd -R -d alsa -d hw:1,0 -p 120 creating alsa driver ... hw:1,0|hw:1,0|120|2|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz, period = 120 frames (2.5 ms), buffer = 2 periods FYI a buffer size of 48 also works however I get another message (maybe because I am not running with a low latency kernel ... yet) Please see attachment for details. ** Attachment added: "jack_buffer_bug.txt" https://bugs.launchpad.net/ubuntu/+source/jackd-defaults/+bug/1872244/+attachment/5491789/+files/jack_buffer_bug.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872244 Title: Jack audio not working on Ubuntu 20.04 running on a Thinkpad Carbon X1 (7th gen) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd-defaults/+bug/1872244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917912] Re: Skip indexing s3fs
Related to https://bugs.launchpad.net/ubuntu/+source/mlocate/+bug/1918448. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917912 Title: Skip indexing s3fs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mlocate/+bug/1917912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1001035] Re: lightdm uses a hardcoded path to .xsession-errors, please make it configurable
Any update on this? I'd love to move xsession-errors file out of my SSD to minimize writes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1001035 Title: lightdm uses a hardcoded path to .xsession-errors, please make it configurable To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1001035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879816] Re: package mythtv-status 1.0.1-1 failed to install/upgrade: installed mythtv-status package post-installation script subprocess returned error exit status 1
I pondered more on this issue this morning and decided to allow the service to fail to start on installation and remove. This is now fixed in 1.0.1-6. ** Changed in: mythtv-status (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/1879816 Title: package mythtv-status 1.0.1-1 failed to install/upgrade: installed mythtv-status package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv-status/+bug/1879816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918482] Re: Update for CVE-2021-21381
Thanks for reviewing these updates! I've done some exploratory testing of .desktop icon related tests from the test plan on a Focal VM and things are working normally. $ apt policy flatpak flatpak: Installed: 1.6.5-0ubuntu0.3 Candidate: 1.6.5-0ubuntu0.3 Version table: *** 1.6.5-0ubuntu0.3 500 500 http://ppa.launchpad.net/ubuntu-security-proposed/ppa/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 1.6.5-0ubuntu0.2 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages 1.6.3-1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918482 Title: Update for CVE-2021-21381 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1918482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 706362] Re: update-motd.d script prevents updating motd
Ugh. This evening I prepared a new package for Debian (1.0.1-2) which includes a patch for this: http://git.etc.gen.nz/cgi-bin/gitweb.cgi?p=mythtv-status.git;a=commit;h=089616c32247d109dc735da56838a6a4bc5d12f8 I'll be releasing version 1.0.2 which will also include this soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/706362 Title: update-motd.d script prevents updating motd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv-status/+bug/706362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879816] Re: package mythtv-status 1.0.1-1 failed to install/upgrade: installed mythtv-status package post-installation script subprocess returned error exit status 1
Hmm... I'm interested in hearing opinions here on how better to handle this situation. mythtv-status was unable to collect information from the mythtv-backend, so it was a legitimate failure. Should I be asking for the hostname to check during installation? Treat failure as acceptable? (Which might hide the issue) Something else? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879816 Title: package mythtv-status 1.0.1-1 failed to install/upgrade: installed mythtv-status package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv-status/+bug/1879816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 36812] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts
https://cdraustralia.org/ provided hassle-free professional CDR Writing Services. I got my CDR professionally prepared on time. They offered me a detailed questionnaire relevant to my projects and prepared the Career Episodes Report and summary statements based on the information. Thanks to your team member. Well-done! -- 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/36812 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/36812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922095] Re: usb-creator-gtk crashed with FileNotFoundError in _execute_child(): [Errno 2] No such file or directory: 'isoinfo'
Same issue with usb-creator-kde on kubuntu 21.04 An unhandled exception occured: [Errno 2] No such file or directory: 'isoinfo' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922095 Title: usb-creator-gtk crashed with FileNotFoundError in _execute_child(): [Errno 2] No such file or directory: 'isoinfo' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1922095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915492] Re: ayatana-indicator-keyboard-service crashed with SIGSEGV in keyboard_GetLayout()
Upstream bug is here https://github.com/AyatanaIndicators/ayatana- indicator-keyboard/issues/5 ** Bug watch added: github.com/AyatanaIndicators/ayatana-indicator-keyboard/issues #5 https://github.com/AyatanaIndicators/ayatana-indicator-keyboard/issues/5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915492 Title: ayatana-indicator-keyboard-service crashed with SIGSEGV in keyboard_GetLayout() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-keyboard/+bug/1915492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906535] Re: "Windows" Section/Setting Forces Window Button Placement To Left Side On Open
Reported a bug upstream with some analysis of the issue. https://github.com/mate-desktop/mate-control-center/issues/640 ** Bug watch added: github.com/mate-desktop/mate-control-center/issues #640 https://github.com/mate-desktop/mate-control-center/issues/640 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906535 Title: "Windows" Section/Setting Forces Window Button Placement To Left Side On Open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-control-center/+bug/1906535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920963] Re: Tried installing with ZFS, but two failures during format, I think.
I tried to install with ZFS again after rebooting. It worked fine when making the first attempt when the target drive was not mounted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920963 Title: Tried installing with ZFS, but two failures during format, I think. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1920963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921135] [NEW] package linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: no further information ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+1 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Mar 18 10:34:46 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-01-23 (60 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: initramfs-tools Title: package linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921135 Title: package linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+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/1921135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921136] [NEW] package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Public bug reported: no further information ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.4 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Mar 24 15:49:31 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-01-23 (60 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921136 Title: package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1921136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920963] [NEW] Tried installing with ZFS, but two failures during format, I think.
Public bug reported: Trying to install with zfs. First attempt had drive mounted. Second attempt with unmounted drive failed to format, maybe. Third attempt failed after sending me time timezone selection. Then collected error report and brought me to the webpage. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.10 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 23 10:09:25 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.10 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920963 Title: Tried installing with ZFS, but two failures during format, I think. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1920963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920016] [NEW] Upgrade s3fs to 1.89
Public bug reported: Release notes: https://github.com/s3fs-fuse/s3fs-fuse/releases/tag/v1.89 This release fixes a regression when writing objects larger than 10 GB during periodic dirty data flush (on by default). Is it possible to include this in 21.04 or cherry pick the fix in a 1.88-3? ** Affects: s3fs-fuse (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920016 Title: Upgrade s3fs to 1.89 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s3fs-fuse/+bug/1920016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857073] Re: Cavium ThunderX CN88XX Oops at smi_send.isra.4+0x80/0x158 [ipmi_msghandler]
I understand that there are no further f/w updates planned for these ThunderX boards. Marking as "won't fix". ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Bionic) 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/1857073 Title: Cavium ThunderX CN88XX Oops at smi_send.isra.4+0x80/0x158 [ipmi_msghandler] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911376] Re: [ssbs-0118] backport SSBS bug (arm64: cpufeature: Detect SSBS and advertise to userspace)
** Changed in: kunpeng920/ubuntu-18.04 Status: Fix Committed => Fix Released ** Changed in: kunpeng920 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/1911376 Title: [ssbs-0118] backport SSBS bug (arm64: cpufeature: Detect SSBS and advertise to userspace) To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1911376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918482] Re: Update for GHSA-xgh4-387p-hqpp
Hirsute now contains 1.10.2-1 with the fix, so I am marking it as fixed released. ** Changed in: flatpak (Ubuntu) Status: In Progress => Fix Released ** Description changed: [Links] https://github.com/flatpak/flatpak/security/advisories/GHSA-xgh4-387p-hqpp https://github.com/flatpak/flatpak/pull/4156 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984859 + https://security-tracker.debian.org/tracker/CVE-2021-21381 [Impact] Versions in Ubuntu right now: Hirsute: 1.10.1-4 Groovy: 1.8.2-1ubuntu0.1 Focal: 1.6.5-0ubuntu0.2 Bionic: 1.0.9-0ubuntu0.2 Affected versions: >= 0.9.4 Patched versions: >= 1.10.2 [Test Case] No test case has been mentioned yet, but in the patches there are changes/additions to the unit tests. [Regression Potential] Flatpak has a test suite, which is run on build across all relevant architectures and passes. There is also a manual test plan https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak . Flatpak has autopkgtests enabled http://autopkgtest.ubuntu.com/packages/f/flatpak . Regression potential is low, and upstream is very responsive to any issues raised. [Other information] Sandbox escape via special tokens in .desktop file (flatpak#4146) Flatpak since 0.9.4 has a vulnerability in the "file forwarding" feature which can be used by an attacker to gain access to files that would not ordinarily be allowed by the app's permissions. Impact By putting the special tokens @@ and/or @@u in the Exec field of a Flatpak app's .desktop file, a malicious app publisher can trick flatpak into behaving as though the user had chosen to open a target file with their Flatpak app, which automatically makes that file available to the Flatpak app. A minimal solution is the first commit "Disallow @@ and @@U usage in desktop files". The follow-up commits "dir: Reserve the whole @@ prefix" and "dir: Refuse to export .desktop files with suspicious uses of @@ tokens" are recommended, but not strictly required. Workarounds Avoid installing Flatpak apps from untrusted sources, or check the contents of the exported .desktop files in exports/share/applications/*.desktop (typically ~/.local/share/flatpak/exports/share/applications/*.desktop and /var/lib/flatpak/exports/share/applications/*.desktop) to make sure that literal filenames do not follow @@ or @@u. References Acknowledgements Thanks to @AntonLydike for reporting this issue, and @refi64 for providing the initial solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918482 Title: Update for GHSA-xgh4-387p-hqpp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1918482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918482] Re: Update for GHSA-xgh4-387p-hqpp
This is now CVE-2021-21381, whoever comes to upload the debdiffs please consider the following: * Please rename "- GHSA-xgh4-387p-hqpp" in the debian/changelog to "- CVE-2021-21381" * Please consider renaming the debian/patches from (for example) "GHSA-xgh4-387p-hqpp-1.patch" to "CVE-2021-21381-1.patch" ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-21381 ** Changed in: flatpak (Ubuntu Bionic) Assignee: (unassigned) => Andrew Hayzen (ahayzen) ** Changed in: flatpak (Ubuntu Focal) Assignee: (unassigned) => Andrew Hayzen (ahayzen) ** Changed in: flatpak (Ubuntu Groovy) Assignee: (unassigned) => Andrew Hayzen (ahayzen) ** Changed in: flatpak (Ubuntu Bionic) Status: New => In Progress ** Changed in: flatpak (Ubuntu Focal) Status: New => In Progress ** Changed in: flatpak (Ubuntu Groovy) 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/1918482 Title: Update for GHSA-xgh4-387p-hqpp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1918482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918482] Re: Update for GHSA-xgh4-387p-hqpp
** Description changed: [Links] https://github.com/flatpak/flatpak/security/advisories/GHSA-xgh4-387p-hqpp https://github.com/flatpak/flatpak/pull/4156 + https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984859 [Impact] Versions in Ubuntu right now: Hirsute: 1.10.1-4 Groovy: 1.8.2-1ubuntu0.1 Focal: 1.6.5-0ubuntu0.2 Bionic: 1.0.9-0ubuntu0.2 Affected versions: >= 0.9.4 Patched versions: >= 1.10.2 [Test Case] No test case has been mentioned yet, but in the patches there are changes/additions to the unit tests. [Regression Potential] Flatpak has a test suite, which is run on build across all relevant architectures and passes. There is also a manual test plan https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak . Flatpak has autopkgtests enabled http://autopkgtest.ubuntu.com/packages/f/flatpak . Regression potential is low, and upstream is very responsive to any issues raised. [Other information] Sandbox escape via special tokens in .desktop file (flatpak#4146) Flatpak since 0.9.4 has a vulnerability in the "file forwarding" feature which can be used by an attacker to gain access to files that would not ordinarily be allowed by the app's permissions. Impact By putting the special tokens @@ and/or @@u in the Exec field of a Flatpak app's .desktop file, a malicious app publisher can trick flatpak into behaving as though the user had chosen to open a target file with their Flatpak app, which automatically makes that file available to the Flatpak app. A minimal solution is the first commit "Disallow @@ and @@U usage in desktop files". The follow-up commits "dir: Reserve the whole @@ prefix" and "dir: Refuse to export .desktop files with suspicious uses of @@ tokens" are recommended, but not strictly required. Workarounds Avoid installing Flatpak apps from untrusted sources, or check the contents of the exported .desktop files in exports/share/applications/*.desktop (typically ~/.local/share/flatpak/exports/share/applications/*.desktop and /var/lib/flatpak/exports/share/applications/*.desktop) to make sure that literal filenames do not follow @@ or @@u. References Acknowledgements Thanks to @AntonLydike for reporting this issue, and @refi64 for providing the initial solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918482 Title: Update for GHSA-xgh4-387p-hqpp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1918482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918482] Re: Update for GHSA-xgh4-387p-hqpp
If someone has the permissions could they add bionic, focal, and groovy as affected series ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918482 Title: Update for GHSA-xgh4-387p-hqpp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1918482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918482] Re: Placeholder for GHSA-xgh4-387p-hqpp
This is the bionic debdiff. ** Description changed: - Patches and description coming soon ! I need this to generate a LP bug - number :-) + [Links] + https://github.com/flatpak/flatpak/security/advisories/GHSA-xgh4-387p-hqpp + https://github.com/flatpak/flatpak/pull/4156 + + [Impact] + Versions in Ubuntu right now: + Hirsute: 1.10.1-4 + Groovy: 1.8.2-1ubuntu0.1 + Focal: 1.6.5-0ubuntu0.2 + Bionic: 1.0.9-0ubuntu0.2 + + Affected versions: + >= 0.9.4 + + Patched versions: + >= 1.10.2 + + [Test Case] + + No test case has been mentioned yet, but in the patches there are + changes/additions to the unit tests. + + [Regression Potential] + + Flatpak has a test suite, which is run on build across all relevant + architectures and passes. + + There is also a manual test plan + https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak . + + Flatpak has autopkgtests enabled + http://autopkgtest.ubuntu.com/packages/f/flatpak . + + Regression potential is low, and upstream is very responsive to any + issues raised. + + [Other information] + + Flatpak since 0.9.4 has a vulnerability in the "file forwarding" feature which can be used by an attacker to gain access to files that would not ordinarily be allowed by the app's permissions. + Impact + + By putting the special tokens @@ and/or @@u in the Exec field of a + Flatpak app's .desktop file, a malicious app publisher can trick flatpak + into behaving as though the user had chosen to open a target file with + their Flatpak app, which automatically makes that file available to the + Flatpak app. + + A minimal solution is the first commit "Disallow @@ and @@U usage in desktop files". The follow-up commits "dir: Reserve the whole @@ prefix" and "dir: Refuse to export .desktop files with suspicious uses of @@ tokens" are recommended, but not strictly required. + Workarounds + + Avoid installing Flatpak apps from untrusted sources, or check the contents of the exported .desktop files in exports/share/applications/*.desktop (typically ~/.local/share/flatpak/exports/share/applications/*.desktop and /var/lib/flatpak/exports/share/applications/*.desktop) to make sure that literal filenames do not follow @@ or @@u. + References + + Acknowledgements + + Thanks to @AntonLydike for reporting this issue, and @refi64 for + providing the initial solution. ** Summary changed: - Placeholder for GHSA-xgh4-387p-hqpp + Update for GHSA-xgh4-387p-hqpp ** Description changed: [Links] https://github.com/flatpak/flatpak/security/advisories/GHSA-xgh4-387p-hqpp https://github.com/flatpak/flatpak/pull/4156 [Impact] Versions in Ubuntu right now: Hirsute: 1.10.1-4 Groovy: 1.8.2-1ubuntu0.1 Focal: 1.6.5-0ubuntu0.2 Bionic: 1.0.9-0ubuntu0.2 Affected versions: - >= 0.9.4 + >= 0.9.4 Patched versions: - >= 1.10.2 + >= 1.10.2 [Test Case] No test case has been mentioned yet, but in the patches there are changes/additions to the unit tests. [Regression Potential] Flatpak has a test suite, which is run on build across all relevant architectures and passes. There is also a manual test plan https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak . Flatpak has autopkgtests enabled http://autopkgtest.ubuntu.com/packages/f/flatpak . Regression potential is low, and upstream is very responsive to any issues raised. [Other information] + Sandbox escape via special tokens in .desktop file (flatpak#4146) + Flatpak since 0.9.4 has a vulnerability in the "file forwarding" feature which can be used by an attacker to gain access to files that would not ordinarily be allowed by the app's permissions. Impact By putting the special tokens @@ and/or @@u in the Exec field of a Flatpak app's .desktop file, a malicious app publisher can trick flatpak into behaving as though the user had chosen to open a target file with their Flatpak app, which automatically makes that file available to the Flatpak app. A minimal solution is the first commit "Disallow @@ and @@U usage in desktop files". The follow-up commits "dir: Reserve the whole @@ prefix" and "dir: Refuse to export .desktop files with suspicious uses of @@ tokens" are recommended, but not strictly required. Workarounds Avoid installing Flatpak apps from untrusted sources, or check the contents of the exported .desktop files in exports/share/applications/*.desktop (typically ~/.local/share/flatpak/exports/share/applications/*.desktop and /var/lib/flatpak/exports/share/applications/*.desktop) to make sure that literal filenames do not follow @@ or @@u. References Acknowledgements Thanks to @AntonLydike for reporting this issue, and @refi64 for providing the initial solution. ** Information type changed from Public to Public Security ** Attachment added: "[bionic] flatpak_1.0.9-0ubuntu0.2_to_flatpak_1.0.9-0ubuntu0.3.debdiff.gz"
[Bug 1918482] Re: Update for GHSA-xgh4-387p-hqpp
So we do not have a CVE yet, I believe one will be auto assigned via github at some point (I don't know how long this takes :-) ). I realised there is a typo in the bionic changelog "- GHSA-xgh4-387p- hqpp-1" should be "- GHSA-xgh4-387p-hqpp". But once a CVE is available this line will need to be replaced anyway ? For hirsute, 1.10.1-4 has the first commit from https://github.com/flatpak/flatpak/pull/4156/commits but 1.10.2-1 has just been submitted to debian sid with the full fixes, so should be syncing shortly ( https://tracker.debian.org/news/1235768/accepted- flatpak-1102-1-source-into-unstable/ ). I have not performed any deep testing yet, I have only built the bionic and focal debdiffs in a PPA (I was surprised that the patches still applied cleanly for bionic so wanted to check that, as the line numbers are quite different). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918482 Title: Update for GHSA-xgh4-387p-hqpp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1918482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918482] Re: Update for GHSA-xgh4-387p-hqpp
This is the focal debdiff. ** Attachment added: "[focal] flatpak_1.6.5-0ubuntu0.2_to_flatpak_1.6.5-0ubuntu0.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1918482/+attachment/5475503/+files/flatpak_1.6.5-0ubuntu0.2_to_flatpak_1.6.5-0ubuntu0.3.debdiff.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918482 Title: Update for GHSA-xgh4-387p-hqpp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1918482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918482] Re: Update for GHSA-xgh4-387p-hqpp
This is the groovy debdiff. ** Attachment added: "[groovy] flatpak_1.8.2-1ubuntu0.1_to_flatpak_1.8.2-1ubuntu0.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1918482/+attachment/5475504/+files/flatpak_1.8.2-1ubuntu0.1_to_flatpak_1.8.2-1ubuntu0.2.debdiff.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918482 Title: Update for GHSA-xgh4-387p-hqpp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1918482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918482] [NEW] Placeholder for GHSA-xgh4-387p-hqpp
Public bug reported: Patches and description coming soon ! I need this to generate a LP bug number :-) ** Affects: flatpak (Ubuntu) Importance: Undecided Assignee: Andrew Hayzen (ahayzen) Status: In Progress ** Changed in: flatpak (Ubuntu) Assignee: (unassigned) => Andrew Hayzen (ahayzen) ** Changed in: flatpak (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/1918482 Title: Placeholder for GHSA-xgh4-387p-hqpp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1918482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed
@Colin Would the package in your PPA be a better source of information for trying to reproduce this bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed
I just upgraded to the latest ZoL release and am still having the same problem. I also upgrade my pool (after creating a checkpoint). $ modinfo zfs | head -12 filename: /lib/modules/5.4.0-66-generic/updates/dkms/zfs.ko version:2.0.3-0york0~20.04 license:CDDL author: OpenZFS description:ZFS alias: devname:zfs alias: char-major-10-249 srcversion: DCE77834FDF1B30075B1328 depends:spl,znvpair,icp,zlua,zzstd,zunicode,zcommon,zavl retpoline: Y name: zfs vermagic: 5.4.0-66-generic SMP mod_unload $ dpkg -l | grep zfs ii libzfs2linux 2.0.3-0york0~20.04 amd64OpenZFS filesystem library for Linux ii zfs-dkms 2.0.3-0york0~20.04all OpenZFS filesystem kernel modules for Linux ii zfs-zed 0.8.3-1ubuntu12.6 amd64OpenZFS Event Daemon ii zfsutils-linux 2.0.3-0york0~20.04 amd64command-line tools to manage OpenZFS filesystems $ zfs --version zfs-2.0.3-0york0~20.04 zfs-kmod-0.8.3-1ubuntu12.6 Panic: ``` Mar 7 20:29:28 home-nas kernel: [ 181.778239] VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed Mar 7 20:29:28 home-nas kernel: [ 181.778605] PANIC at zfs_znode.c:339:zfs_znode_sa_init() Mar 7 20:29:28 home-nas kernel: [ 181.778778] Showing stack for process 2854 Mar 7 20:29:28 home-nas kernel: [ 181.778793] CPU: 0 PID: 2854 Comm: ls Tainted: P OE 5.4.0-66-generic #74-Ubuntu Mar 7 20:29:28 home-nas kernel: [ 181.778796] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-48-gd9c812dda519-prebuilt.qemu.org 04/01/2014 Mar 7 20:29:28 home-nas kernel: [ 181.778798] Call Trace: Mar 7 20:29:28 home-nas kernel: [ 181.778948] dump_stack+0x6d/0x9a Mar 7 20:29:28 home-nas kernel: [ 181.779068] spl_dumpstack+0x29/0x2b [spl] Mar 7 20:29:28 home-nas kernel: [ 181.779081] spl_panic+0xd4/0xfc [spl] Mar 7 20:29:28 home-nas kernel: [ 181.779491] ? __zfs_dbgmsg+0xe0/0x110 [zfs] Mar 7 20:29:28 home-nas kernel: [ 181.779624] ? sa_cache_constructor+0x27/0x50 [zfs] Mar 7 20:29:28 home-nas kernel: [ 181.779643] ? _cond_resched+0x19/0x30 Mar 7 20:29:28 home-nas kernel: [ 181.779657] ? mutex_lock+0x13/0x40 Mar 7 20:29:28 home-nas kernel: [ 181.779760] ? dmu_buf_replace_user+0x60/0x80 [zfs] Mar 7 20:29:28 home-nas kernel: [ 181.779863] ? dmu_buf_set_user_ie+0x1a/0x20 [zfs] Mar 7 20:29:28 home-nas kernel: [ 181.78] zfs_znode_sa_init.isra.0+0xdf/0xf0 [zfs] Mar 7 20:29:28 home-nas kernel: [ 181.780138] zfs_znode_alloc+0x102/0x6d0 [zfs] Mar 7 20:29:28 home-nas kernel: [ 181.780249] ? aggsum_add+0x196/0x1b0 [zfs] Mar 7 20:29:28 home-nas kernel: [ 181.780343] ? dmu_buf_unlock_parent+0x38/0x80 [zfs] Mar 7 20:29:28 home-nas kernel: [ 181.780429] ? dbuf_read_impl.constprop.0+0x614/0x700 [zfs] Mar 7 20:29:28 home-nas kernel: [ 181.780442] ? spl_kmem_cache_alloc+0xc1/0x7d0 [spl] Mar 7 20:29:28 home-nas kernel: [ 181.780447] ? _cond_resched+0x19/0x30 Mar 7 20:29:28 home-nas kernel: [ 181.780452] ? mutex_lock+0x13/0x40 Mar 7 20:29:28 home-nas kernel: [ 181.780537] ? aggsum_add+0x196/0x1b0 [zfs] Mar 7 20:29:28 home-nas kernel: [ 181.780541] ? _cond_resched+0x19/0x30 Mar 7 20:29:28 home-nas kernel: [ 181.780546] ? _cond_resched+0x19/0x30 Mar 7 20:29:28 home-nas kernel: [ 181.780551] ? down_read+0x13/0xa0 Mar 7 20:29:28 home-nas kernel: [ 181.780638] ? dbuf_read+0x1d0/0x520 [zfs] Mar 7 20:29:28 home-nas kernel: [ 181.780643] ? _cond_resched+0x19/0x30 Mar 7 20:29:28 home-nas kernel: [ 181.780647] ? mutex_lock+0x13/0x40 Mar 7 20:29:28 home-nas kernel: [ 181.780746] ? dnode_rele_and_unlock+0x6c/0xe0 [zfs] Mar 7 20:29:28 home-nas kernel: [ 181.780751] ? _cond_resched+0x19/0x30 Mar 7 20:29:28 home-nas kernel: [ 181.780755] ? mutex_lock+0x13/0x40 Mar 7 20:29:28 home-nas kernel: [ 181.780847] ? dmu_object_info_from_dnode+0x84/0xb0 [zfs] Mar 7 20:29:28 home-nas kernel: [ 181.780975] zfs_zget+0x1c3/0x270 [zfs] Mar 7 20:29:28 home-nas kernel: [ 181.781104] zfs_dirent_lock+0x34b/0x680 [zfs] Mar 7 20:29:28 home-nas kernel: [ 181.781232] zfs_dirlook+0x90/0x2b0 [zfs] Mar 7 20:29:28 home-nas kernel: [ 181.781358] ? zfs_zaccess+0x153/0x410 [zfs] Mar 7 20:29:28 home-nas kernel: [ 181.781484] zfs_lookup+0x1fd/0x3f0 [zfs] Mar 7 20:29:28 home-nas kernel: [ 181.781608] zpl_lookup+0xc9/0x1e0 [zfs] Mar 7 20:29:28 home-nas kernel: [ 181.781662] ? security_capable+0x3d/0x60 Mar 7 20:29:28 home-nas kernel: [ 181.781697] __lookup_slow+0x92/0x160 Mar 7 20:29:28 home-nas kernel: [ 181.781703] lookup_slow+0x3b/0x60 Mar 7 20:29:28 home-nas kernel: [ 181.781709] walk_component+0x1da/0x360 Mar 7 20:29:28 home-nas kernel: [ 181.781714] ? link_path_walk.part.0+0x6d/0x550 Mar 7 20:29:28 home-nas
[Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise
This appears to be the problem I ran into with Ubuntu Desktop 20.10 as reported here: https://askubuntu.com/questions/1321431/ubuntu-desktop-20-10-on-usb-flash-drive-boots-only-on-original-computer If it is the same problem (and not a limitation with the latest [but old] ASUS N551VW BIOS) then please escalate this ABOVE CRITICAL. I'm sure a lot more Windows 10 users would delight to have a bootable Ubuntu system on a USB Flash Drive (or an externally USB-connected SSD, e.g. in an ICY BOX) if the "Device for boot loader installation" set to /dev/sdb would really write something there. I also noticed a couple of error messages during booting - one was only a few seconds on the screen so I was not able to capture it. I will post what I have (in AskUbuntu) if it is of any assistance to you. My laptop works perfectly (error- free) with Windows 10. Apparently the workaround is to remove Disk 0 (Windows 10 drive) from the laptop. I will give this a try though I doubt that the casual user would go so far as to unscrew the back cover of their laptop to remove their HD/SSD. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396379 Title: installer uses first EFI system partition found even when directed otherwise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1396379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917977] Re: Synaptiks touchpad not detected in kernel
I tried to run the command but it said command not available ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917977 Title: Synaptiks touchpad not detected in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917977] [NEW] Synaptiks touchpad not detected in kernel
Public bug reported: After using "cat /proc/bus/input/devices" no touchpad shows up same with xinput and other commands. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Summary changed: - Synaptiks touchpad not detected in kernal + Synaptiks touchpad not detected in kernel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917977 Title: Synaptiks touchpad not detected in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917912] [NEW] Skip indexing s3fs
Public bug reported: updatedb crawls large remote S3 object stores which incurs a high IO cost. This confuses users who experience poor performance and high AWS bills. Similar to NFS and ceph, the s3fs project would like to add fuse.s3fs to PRUNEFS. Tracking issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1587 ** Affects: mlocate (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917912 Title: Skip indexing s3fs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mlocate/+bug/1917912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917757] Re: General protection fault in Bluetooth HID (Magic Mouse driver)
** Attachment added: "dmesg output" https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.10/+bug/1917757/+attachment/5472556/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917757 Title: General protection fault in Bluetooth HID (Magic Mouse driver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.10/+bug/1917757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917757] [NEW] General protection fault in Bluetooth HID (Magic Mouse driver)
Public bug reported: Description:KDE neon User Edition 5.21 Release:20.04 linux-image-5.10.0-1014-oem: Installed: 5.10.0-1014.15 Candidate: 5.10.0-1014.15 Once in a while (typically once every 10 minutes or so) my Bluetooth Apple Magic Mouse (I gen) disconnects and reconnects again leading to the "magicmouse 0005:05AC:030D.001E: unknown main item tag 0x0" messages in the kernel log. But this time it seems to have caused a crash in the Bluetooth stack. Here is the dmesg output: [57748.295271] magicmouse 0005:05AC:030D.001E: unknown main item tag 0x0 [57748.295749] input: Magic Mouse as /devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/bluetooth/hci0/hci0:512/0005:05AC:030D.001E/input/input56 [57748.296035] magicmouse 0005:05AC:030D.001E: input,hidraw1: BLUETOOTH HID v3.06 Mouse [Magic Mouse] on 34:2e:b7:45:c7:ba [62464.630828] general protection fault, probably for non-canonical address 0xdead00e8: [#1] SMP NOPTI [62464.630835] CPU: 11 PID: 36176 Comm: kworker/u25:2 Tainted: G O 5.10.0-1014-oem #15-Ubuntu [62464.630836] Hardware name: Dell Inc. Precision 5750/0XFTD8, BIOS 1.6.3 12/30/2020 [62464.630860] Workqueue: hci0 hci_rx_work [bluetooth] [62464.630867] RIP: 0010:__wake_up_common+0xbd/0x140 [62464.630869] Code: c0 00 74 26 41 83 c4 01 41 83 fc 40 7e 1c 48 8d 43 18 48 39 45 d0 75 66 8b 45 c8 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 <48> 8b 43 18 48 89 df 48 8d 53 18 48 83 e8 18 48 39 55 d0 74 d9 48 [62464.630871] RSP: 0018:a0b58be0fb80 EFLAGS: 00010083 [62464.630873] RAX: RBX: dead00e8 RCX: c1672078 [62464.630875] RDX: 0001 RSI: 0046 RDI: 0046 [62464.630876] RBP: a0b58be0fbc0 R08: R09: a0b58be0faf8 [62464.630878] R10: 94fe130d5a10 R11: 95057d56c270 R12: 0002 [62464.630879] R13: R14: R15: [62464.630881] FS: () GS:95057d6c() knlGS: [62464.630883] CS: 0010 DS: ES: CR0: 80050033 [62464.630884] CR2: 119361d2e000 CR3: 0001b2bce004 CR4: 007706e0 [62464.630886] PKRU: 5554 [62464.630887] Call Trace: [62464.630892] __wake_up_common_lock+0x7c/0xc0 [62464.630896] __wake_up+0x13/0x20 [62464.630898] sock_def_wakeup+0x36/0x40 [62464.630919] l2cap_sock_teardown_cb+0x1b1/0x200 [bluetooth] [62464.630936] l2cap_chan_del+0x4a/0x2e0 [bluetooth] [62464.630952] l2cap_conn_del+0x113/0x230 [bluetooth] [62464.630969] l2cap_disconn_cfm+0x3d/0x60 [bluetooth] [62464.630983] hci_disconn_complete_evt.isra.0+0x147/0x2e0 [bluetooth] [62464.630998] hci_event_packet+0x1b43/0x29b0 [bluetooth] [62464.631010] hci_rx_work+0x1a5/0x3b0 [bluetooth] [62464.631013] process_one_work+0x1ef/0x390 [62464.631016] worker_thread+0x4d/0x3f0 [62464.631018] kthread+0x114/0x150 [62464.631020] ? process_one_work+0x390/0x390 [62464.631022] ? kthread_park+0x90/0x90 [62464.631025] ret_from_fork+0x1f/0x30 [62464.631027] Modules linked in: hid_magicmouse hidp rfcomm vboxnetadp(O) vboxnetflt(O) vboxdrv(O) ccm aufs cmac algif_hash algif_skcipher overlay af_alg bnep zram btusb btrtl btbcm btintel bluetooth nls_iso8859_1 ecdh_generic ecc uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc snd_soc_sof_sdw snd_soc_hdac_hdmi snd_soc_rt715 snd_soc_rt1308_sdw snd_soc_rt711 regmap_sdw snd_soc_dmic snd_sof_pci snd_sof_intel_byt mei_hdcp intel_rapl_msr snd_sof_intel_ipc snd_sof_intel_hda_common snd_soc_hdac_hda dell_rbtn snd_sof_xtensa_dsp snd_sof_intel_hda snd_sof snd_hda_codec_hdmi dell_laptop snd_hda_ext_core snd_soc_acpi_intel_match dell_smm_hwmon snd_soc_acpi ledtrig_audio snd_hda_intel joydev snd_intel_dspcfg soundwire_intel x86_pkg_temp_thermal intel_powerclamp soundwire_generic_allocation soundwire_cadence snd_seq_midi coretemp snd_seq_midi_event snd_hda_codec snd_rawmidi snd_hda_core kvm_intel snd_hwdep soundwire_bus snd_soc_core iwlmvm kvm snd_compress ac97_bus [62464.631086] dell_wmi snd_pcm_dmaengine dell_smbios mac80211 snd_seq rapl snd_pcm dcdbas libarc4 intel_cstate input_leds serio_raw efi_pstore dell_wmi_descriptor snd_seq_device wmi_bmof hid_sensor_gyro_3d intel_wmi_thunderbolt iwlwifi ee1004 snd_timer hid_sensor_als hid_sensor_trigger industrialio_triggered_buffer kfifo_buf hid_sensor_iio_common industrialio snd ucsi_ccg mei_me processor_thermal_device ucsi_acpi cfg80211 cros_ec_ishtp typec_ucsi intel_rapl_common mei hid_multitouch cros_ec soundcore intel_soc_dts_iosf intel_pch_thermal typec int3403_thermal int340x_thermal_zone mac_hid intel_hid int3400_thermal acpi_tad sparse_keymap acpi_pad acpi_thermal_rel sch_fq_codel msr parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_sensor_custom hid_sensor_hub
[Bug 1917278] [NEW] Unable to reinstall grub. Started with Windows 7. Installed Ubuntu 20.04 to dual boot. Upgraded to Windows 10. Got new monitor, did not recognize Ubuntu install. Reinstalled Ubunt
Public bug reported: >From what I can see, the original boot loader was not UEFI, it was legacy(not sure what that means). There are 3 primary partitions for windows and all Ubuntu was installed on an extended partition. I think the boot loader is the first primary partition that is 100 mb, but it is ntfs, not fat32 like efi partitions should be. Boot-repair doesn't work either. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.13 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 Date: Sun Feb 28 21:40:12 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RebootRequiredPkgs: linux-image-5.8.0-25-generic linux-base SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.13 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917278 Title: Unable to reinstall grub. Started with Windows 7. Installed Ubuntu 20.04 to dual boot. Upgraded to Windows 10. Got new monitor, did not recognize Ubuntu install. Reinstalled Ubuntu. Nothing works. Post here. Cry in corner. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1917278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1454306] Re: apt-btrfs-snapshot supported reports "Sorry, your system lacks support for the snapshot feature" since update of btrfs-tools to 4.0-2 in debian/testing
All these messages from 2016-2017 saying it's fixed in v16.. Now it's 2021, Feb, I'm using up-to date 20.04 LTS with apt-btrfs-snapshot v353. I still get the message. How could it have been fixed 5 years ago, but I'm still having the problem? I even made sure there was a copy in /bin and /sbin (and /usr/bin where it was according to which) Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1454306 Title: apt-btrfs-snapshot supported reports "Sorry, your system lacks support for the snapshot feature" since update of btrfs-tools to 4.0-2 in debian/testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-btrfs-snapshot/+bug/1454306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812892] Re: Use high ram memory by the gnome-shell-extension-gsconnect
When I enable GSConnect version 28 (as reported by GSConnect > About) in Tweaks > Extensions > GSConnect, after a while my Ubuntu 18.04 system becomes unresponsive, with the disk activity light solidly on. With it disabled, the system never becomes unresponsive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812892 Title: Use high ram memory by the gnome-shell-extension-gsconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-gsconnect/+bug/1812892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730612] Re: Enable Remote desktop feature during build
@jik, I think that you need the package gnome-remote-desktop, this has a MIR request in bug 1802614. And then another package will need to recommend it to have it installed by default, you can follow this on the Trello board here https://trello.com/c/NnUq5bHv/15-mir-gnome-remote- desktop-and-seed-recommend-it -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730612 Title: Enable Remote desktop feature during build To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1730612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793124]
Related meta: Bug 98754 Current ticket will celebrate 10th anniversary in a week -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793124 Title: [upstream] Scrolling on Calc leaves content invisible if cell is higher than screen To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1793124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891934] Re: [MIR] google-osconfig-agent
I worked on addressing a number of the concerns in the "Software Recipe" section of the agent, this included the File IO concerns as well as a number of unchecked errors and other issues. We are currently testing a new stable release containing these changes. There was some concern around the archive extraction implementation overwriting files, we check for conflicts and abort the the extractions on any file conflicts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891934 Title: [MIR] google-osconfig-agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/1891934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904906] Re: 5.10 kernel fails to boot with secure boot disabled
Waiting to close as "Fix Released" once the 5.10 kernel has landed in hirsute. 5.10 kernel is currently in hirsute -proposed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904906 Title: 5.10 kernel fails to boot with secure boot disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872476] Re: Shared files are shown as folders
@rmills: workaround is described in https://askubuntu.com/questions/1288678/some-files-on-samba-shares-are- displayed-as-folders (run `setfattr -x user.DOSATTRIB ` on every file that shows as a dir). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872476 Title: Shared files are shown as folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1872476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869763] Re: Huawei Kunpeng 920 arm64 machine KVM guest frequently crash
** Changed in: kunpeng920 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/1869763 Title: Huawei Kunpeng 920 arm64 machine KVM guest frequently crash To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1869763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913602] [NEW] Rendering of formatted cells is at odfds with Excel and Open Office
Public bug reported: I have been writing an .xlsx file using java POI from InteliJ. Rendering the sheet does not reflect the cell-styles which have been applied. The sheet is absolutely as expected in Excel (on Windows 10) and OpenOffice on Ubuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-calc 1:6.4.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Thu Jan 28 14:42:29 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 InstallationDate: Installed on 2020-08-18 (163 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2020-08-25 (155 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "peter.xlsx" https://bugs.launchpad.net/bugs/1913602/+attachment/5457770/+files/peter.xlsx -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913602 Title: Rendering of formatted cells is at odfds with Excel and Open Office To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1913602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912902] Re: Merge steam 1.0.0.68-1 from debian sid to ubuntu hirsute
** Description changed: - Placeholder as we merge the latest changes from Debian sid to Ubuntu - hirsute. + Debian has a newer version of steam packaging available, let's merge the + changes into the Ubuntu version to bring us back into sync. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912902 Title: Merge steam 1.0.0.68-1 from debian sid to ubuntu hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1912902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911473] Re: Update for ghsa-4ppf-fxf6-vxg2
@Paulo, was there any progress on this or anything you need help with ? I've posted debdiffs for focal and groovy. Sounds like you have a diff for bionic. Let me know if there is anything I can do to help this move to the next step :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911473 Title: Update for ghsa-4ppf-fxf6-vxg2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1911473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913488] [NEW] could not determine upgrade an unresolvable problem occured
Public bug reported: Could not determine the upgrade An unresolvable problem occurred while calculating the upgrade. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. Restoring original system state ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.42 ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18 Uname: Linux 4.15.0-135-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Jan 27 21:32:27 2021 InstallationDate: Installed on 2018-08-15 (896 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2021-01-27 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913488 Title: could not determine upgrade an unresolvable problem occured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1913488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912902] [NEW] Merge steam 1.0.0.68-1 from debian sid to ubuntu hirsute
Public bug reported: Placeholder as we merge the latest changes from Debian sid to Ubuntu hirsute. ** Affects: steam (Ubuntu) Importance: Undecided Assignee: Andrew Hayzen (ahayzen) Status: In Progress ** Changed in: steam (Ubuntu) Assignee: (unassigned) => Andrew Hayzen (ahayzen) ** Changed in: steam (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/1912902 Title: Merge steam 1.0.0.68-1 from debian sid to ubuntu hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1912902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911473] Re: Update for ghsa-4ppf-fxf6-vxg2
Please find attached the debdiff for Ubuntu 20.10 groovy. This includes a similar set of patches to the focal set and has been picked from between the 1.8.4 and 1.8.5 tags. Let me know if anything has been done incorrectly or missed any commits. I will leave it up to the security team to decide if Ubuntu should also include the extra setuid patches provides by upstream in any of these debdiffs. ** Attachment added: "flatpak_1.8.2-1_to_1.8.2-1ubuntu0.1.debdiff.gz" https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1911473/+attachment/5455341/+files/flatpak_1.8.2-1_to_1.8.2-1ubuntu0.1.debdiff.gz ** Changed in: flatpak (Ubuntu Groovy) 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/1911473 Title: Update for ghsa-4ppf-fxf6-vxg2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1911473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910866] Re: nvme drive fails after some time
@Kleber I have installed the focal hwe kernel from proposed (as seen below). So far when A/B testing this kernel it is working correctly :-) I will continue running this kernel and report any issues I have. Also note that I have been continuously running the test kernel (from comment 22) since last week and it has worked perfectly so far :-) I look forward to this migrating from -proposed into focal. $ uname -a Linux xps-13-9360 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux $ apt policy linux-generic-hwe-20.04 linux-generic-hwe-20.04: Installed: 5.8.0.41.46~20.04.27 Candidate: 5.8.0.41.46~20.04.27 Version table: *** 5.8.0.41.46~20.04.27 500 500 http://gb.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.8.0.40.45~20.04.25 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 5.8.0.38.43~20.04.23 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 5.4.0.26.32 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910866 Title: nvme drive fails after some time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
