debcrafters-packages team mailing list archive

[Launchpad Bug Tracker <2122605@xxxxxxxxxxxxxxxxxx>]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: cups-browsed (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to cups-browsed in Ubuntu.
https://bugs.launchpad.net/bugs/2122605

Title:
  Printer properties broken on 25.10 due to outdated AppArmor profile

Status in cups-browsed package in Ubuntu:
  Confirmed

Bug description:
  I was testing a daily build of "questing" (built 2025-09-08) and noticed that I couldn't access
  the printer properties of my printer in GNOME settings.
  Additionally, my printer was not present in the management interface on 127.0.0.1:631.

  I've come to the conclusion that this regression is caused by an outdated AppArmor policy on cups-browsed,
  denying execution of /usr/lib/cargo/bin/coreutils/echo by ippfind. ippfind uses /usr/bin/echo, which was
  a binary provided by the "coreutils" package on "plucky".
  However, on "questing" it is a symlink to "../lib/cargo/bin/coreutils/echo", provided by "rust-coreutils".

  The journal error that narrowed it down was:
  audit: type=1400 audit(1757502845.833:255): apparmor="DENIED" operation="exec" class="file" profile="/usr/sbin/cups-browsed" name="/usr/lib/cargo/bin/coreutils/echo" pid=10442 comm="ippfind" requested_mask="x" denied_mask="x" fsuid=0 ouid=0

  I fixed this regression by adding the paths of gnu-coreutils' echo and rust-coreutils' echo to
  cups-browsed's AppArmor profile.

  Patch is attached.

  Reproduce with:
   - Ubuntu desktop daily build of "questing" from 2025-09-08
   - Connect printer to network, go to http://127.0.0.1:631, see that the printer is missing
   - Read journal to find AppArmor errors from ippfind

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2122605/+subscriptions