[Bug 2111604] Re: lsblk: failed to get sysfs name: Permission denied

2025-05-28 Thread Ryan Lee
** Changed in: apparmor (Ubuntu Questing) Status: New => Fix Released ** Changed in: apparmor (Ubuntu Plucky) Status: New => Confirmed ** Changed in: apparmor (Ubuntu Questing) Assignee: (unassigned) => Ryan Lee (rlee287) -- You received this bug notification because you are

[Bug 2111604] Re: lsblk: failed to get sysfs name: Permission denied

2025-05-28 Thread Ryan Lee
FYI the iotop-c profile fixing is tracked in https://bugs.launchpad.net/ubuntu/+source/iotop-c/+bug/2107727. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2111604 Title: lsblk: failed to get sysfs n

[Bug 2111604] Re: lsblk: failed to get sysfs name: Permission denied

2025-05-28 Thread Marc Deslauriers
** Also affects: apparmor (Ubuntu Questing) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu Plucky) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs

[Bug 2111604] Re: lsblk: failed to get sysfs name: Permission denied

2025-05-27 Thread Ryan Lee
** Tags added: sec-6366 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2111604 Title: lsblk: failed to get sysfs name: Permission denied To manage notifications about this bug go to: https://bugs.la

[Bug 2111604] Re: lsblk: failed to get sysfs name: Permission denied

2025-05-23 Thread Christian Kujau
I've created https://gitlab.com/apparmor/apparmor/-/merge_requests/1702 but the build pipeline is still in progress. FWIW, I noticed that "iotop-c" command needs some AA tweaking too, and the fix has already been merged upstream: https://gitlab.com/apparmor/apparmor/-/merge_requests/1675 -- You

[Bug 2111604] Re: lsblk: failed to get sysfs name: Permission denied

2025-05-23 Thread Ubuntu Foundations Team Bug Bot
The attachment "patch proposal" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray,

[Bug 2111604] Re: lsblk: failed to get sysfs name: Permission denied

2025-05-23 Thread Georgia Garcia
Hi Christian. The patch looks good to me. Do you mind submitting it to the apparmor project upstream? https://gitlab.com/apparmor/apparmor under profiles/apparmor.d/lsblk If possible, please include a link to this bug in the commit message -- You received this bug notification because you are a

[Bug 2111604] Re: lsblk: failed to get sysfs name: Permission denied

2025-05-23 Thread Christian Kujau
** Attachment added: "patch proposal" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2111604/+attachment/5880001/+files/aa_lsblk.patch.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/211

[Bug 2111604] Re: lsblk: failed to get sysfs name: Permission denied

2025-05-23 Thread Christian Kujau
Not a util-linux issue, but an AA profile issue ** Package changed: util-linux (Ubuntu) => apparmor (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2111604 Title: lsblk: failed to get sysfs

[Bug 2111604] Re: lsblk: failed to get sysfs name: Permission denied

2025-05-23 Thread Christian Kujau
Gaah, and shortly after submitting this one I remembered that Ubuntu enables AppArmor by default: - $ sudo aa-status apparmor module is loaded. 173 profiles are loaded. 90 profiles are in enforce mode. [...] lsblk $ sudo aa-complain /usr/bin/lsb