OK,
I rebooted the printer and the printer was autodiscovered again.
Those cups apparmor denies don't appear to stop discovery ... so they
are noise on the journal log ... minor.
I will mark this as invalid.
** Changed in: cups (Ubuntu)
Status: Incomplete => Invalid
** Changed in:
Jammy has not had any changes to the apparmor packages.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1955434
Title:
Driverless printing detection does not work
Status in apparmor
To the maintainers of AppArmor: Did anything change in the
default/standard AppArmor restrictions in Jammy which requires changed
in the profiles of CUPS and cups-browsed?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
As usual, submitting to early, trying again ...
This looks like that either AppArmor got more restricted in Jammy. I
will CC AppArmor folks to make them aware, but due to the holidays they
will possibly not react quickly. So I recommend to temporarily de-
activate AppArmor for CUPS and for
This looks like that either AppArmor got more restricted in Jammy. I
will CC AppArmor folks to make them aware, but due to the holidays they
will possibly not react quickly. So I recommend to temporarily de-
activate AppArmor for CUPS and for cups-browsed:
sudo apt install apparmor-utils
5 matches
Mail list logo
