This is a pretty old bug, I quickly look at this with refpolicy
2:2.20131214-1 and all the avc denials mentioned here should now be
granted
Feel free to reopen if you are still experiencing this bug
** Changed in: refpolicy (Ubuntu)
Status: New = Fix Released
--
You received this bug
The printer definitely works when selinux is permissive. With selinux
enforced, I repeated many times `restorecon -rv /` and the following
lines continue to appear, as if the modifications were not registered
when executed:
restorecon reset /usr/lib/cups/backend-available/dnssd context
When I indicated that selinux was set in permissive mode, in fact I was
diseabling it by changing to selinux=0 on boot.
--
selinux enforced (Ubuntu Hardy) : printer doesn't print : cupsd: Unable to open
log file /var/log/cups/access_log - Permission denied
https://bugs.launchpad.net/bugs/290891
** Summary changed:
- selinux enforced (Ubuntu Hardy) : printer problem
+ selinux enforced (Ubuntu Hardy) : printer doesn't print : cupsd: Unable to
open log file /var/log/cups/access_log - Permission denied
--
selinux enforced (Ubuntu Hardy) : printer doesn't print : cupsd: Unable to open
The audit message shows that the context of /var/log/cups/access_log is
tcontext=system_u:object_r:file_t, it should cupsd_log_t. `restorecon
-rv /` should fix that (along with any other mislabeled files).
--
selinux enforced (Ubuntu Hardy) : printer doesn't print : cupsd: Unable to open
log
Thank you for your response. I had to repeat the command because of an
error in pipe. Many many files were relabeled. Even with these
changes, I cannot print. The printer can't connect:
Oct 29 22:53:19 localhostlouis Photosmart_C6100_series?serial=[...]:
io/hpmud/musb.c 1058: unable to open
Thank you for your response. I had to repeat the command because of an
error in pipe. Many many files were relabeled. Even with these
changes, I cannot print. The printer can't connect:
Oct 29 22:53:19 localhostlouis Photosmart_C6100_series?serial=[...]:
io/hpmud/musb.c 1058: unable to open
Your audit message says the target context is usb_device_t, I think it
should be printer_device_t. restorecon should have caught this, it
might need to be updated in the policy.
If it works in permissive mode then we know that it is an SELinux issue.
If it still is broken then it might be the
