The #5683 is closed, so I create this new issue.
I have tested the newest branch master & 2.2.x. The test result is as below:
If the default printer name in the file /etc/cups/printers.conf is empty, then the phenomenon described in the #5683 has been fixed.
But if the default printer name in the file /etc/cups/printers.conf is not empty, then the phenomenon described in the #5683 is still existent.