Thanks for the details. Cups is supposed to error out when it parses an invalid configuration file (per the FatalErrors setting in cups-files.conf). Because of a bug, before this security update, it wasn't doing that.
The unknown issue here is why the users experiencing this bug have JobPrivateAccess, JobPrivateValues, SubscriptionPrivateAccess, and SubscriptionPrivateValues configuration outside of a <Policy> section, which is a configuration error. I have tried multiple tools, including system-config-printer, and I can't get any of them to write out those invalid configuration options. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2133207 Title: cups security update causes issues with invalid config file To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/2133207/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
