Michel (mikenavy) - That is the point I was making, which may explain why "some users are encountering the configuration errors after installing the security update, and some aren't". It may be that the offending configuration entries (JobPrivateAccess, JobPrivateValues, etc) may have been introduced with some unrelated update in the past, but were never detected because of the "hole" in the CUPS code that this recent security update patched.
If some users somehow avoided whatever originally corrupted the config file, they, of course, won't have any issues after installing the latest CUPS update (whether in Ubuntu or a derivative OS like Mint). -- 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
