Hello! Same problem here on a DELL Vostro 1015 laptop with Ubuntu 22.04 LTS installed. Case looks very similar (I did not try installing Chromium from 3rd party repo, so cannot say anything about Chromium configurations working ok for print preview).
Looking up in the /var/log/syslog file, I found out that the same kind of message appeared (thanks a lot Dalik for the history! It helped a lot...) Some lines above that message about cups/ppd saying Dec 14 22:47:15 Vostro-1015 vmunix: [ 7591.002262] audit: type=1400 audit(1734212835.036:373): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/cups/ppd/ET-2860-Series.ppd" pid=12081 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 I found out that there were some /other/ DENIED messages by apparmor like Dec 14 22:46:32 Vostro-1015 vmunix: [ 7548.431167] audit: type=1400 audit(1734212792.465:362): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/sys/devices/pci0000:00/0000:00:1a.0/usb2/2-1/2-1.1/devnum" pid=12081 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 and earlier Dec 14 22:46:13 Vostro-1015 vmunix: [ 7529.767007] audit: type=1400 audit(1734212773.800:352): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/icd.d/" pid=12197 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 showing that apparmor was indeed forbidding a lot of actions in the snap.chromium.chromium profile... I checked that all such data in /etc/vulkan were at least readable by anyone (they are root-owned so drwxr-xr-x is minimum and was there) and I issued the command sudo gedit /var/lib/snapd/apparmor/profiles/snap.chromium.chromium and updated some lines (addition on top of lines following line #1931 reading "# Support reading the Vulkan ICD files") /etc/vulkan/ r, /etc/vulkan/** r, plus added apparmor permissions in that file for /sys/devices/pci*/**/**/**/**/devnum I also changed in the terminal the access permissions on the /etc/cups/ppd/ET-2860-Series.ppd file (root-owned, group lp, changed from 640 to 644) for more safety on user access. I closed the Chromium application and reopened it, hoping for -at least- getting rid of that last message and its relatives regarding /etc/vulkan. Unfortunately, this proved useless and the message still is there in the syslog file (along with siblings). I would welcome any new idea to go further on investigating this case. Regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2088333 Title: Chromium - printer unavailable - apparmor denial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2088333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
