Public bug reported: I tried using `lsblk` regularly, without any arguments, with and without `sudo`, and I got a segmentation fault. This also appeared when using `lsblk -h` or `--help` to try to just list the options of the program.
Eventually, I traced this bug back to the Plucky release notes which linked to these other launchpad bugs: - https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2107455 - https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2107402 I followed the troubleshooting of the plucky release notes ( https://discourse.ubuntu.com/t/plucky-puffin-release-notes/48687 ) which fixed the problem. So, with `sudo aa-enforce /etc/apparmor.d/lsblk`, I get the bug, while after running `sudo aa-disable /etc/apparmor.d/lsblk`, lsblk works as expected. Ubuntu 25.04, apparmor 4.1.0~beta5-0ubuntu14, running on a framework 13 with a AMD Ryzen 7 7840U, x86-64. ProblemType: Bug DistroRelease: Ubuntu 25.04 Package: apparmor 4.1.0~beta5-0ubuntu14 ProcVersionSignature: Ubuntu 6.14.0-15.15-generic 6.14.0 Uname: Linux 6.14.0-15-generic x86_64 ApportVersion: 2.32.0-0ubuntu5.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 15 18:23:05 2025 InstallationDate: Installed on 2024-08-21 (298 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-ghostty XDG_RUNTIME_DIR=<set> ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-6.14.0-15-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro amdgpu.dcdebugmask=0x10 quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 SourcePackage: apparmor UpgradeStatus: Upgraded to plucky on 2025-06-09 (6 days ago) modified.conffile..etc.apparmor.d.signal-desktop: [modified] mtime.conffile..etc.apparmor.d.signal-desktop: 2025-06-09T12:11:47.967435 ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug plucky 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/2114681 Title: lsblk crashes with segfault (on amd64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2114681/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
