Even great programmers can be terribly misguided

> That is hardly news that closing security holes causes regressions - some because users relied on insecure behavior, some because maintainer went overboard when closing the hole and disabled valid usecases too.

I was hit by one of these recently. A recent CUPS release fixed a bunch of vulnerabilities (https://github.com/OpenPrinting/cups/releases/tag/v2.4.17), and the fix for the first one in that list was so broken that it needed to be repaired not once (https://github.com/OpenPrinting/cups/releases/tag/v2.4.18) but twice (https://github.com/OpenPrinting/cups/releases/tag/v2.4.19). In the middle of tax filling season in my country. And the computer connected to the printer didn't have a user account with the same username as the user account being used to do the taxes on the other computer. The log messages weren't exactly helpful.

(The workaround, once I found https://github.com/OpenPrinting/cups/issues/1557 which explained the issue, was: print to PDF, and copy the file to a user account which has the same username as an account which does exist on that computer connected to the printer. Printing from that user account worked fine, which was really confusing until I found the explanation that the username somehow matters, even though it's not authenticating to the server at all.)