Print module initialization hangs on network printers
When there is a network printer currently unavailable the print module will hang waiting for an HTTP request to fulfill GetPPD. The relevant code is here:
This probably needs to be ran in another thread or in some other way so as to not have the whole program waiting for that call. For example the GNOME printer dialog seems to enumerate the printers fine and only when the unavailable printer gets selected tries to get it's info. It seems to do that in a separate thread as it never blocks the GUI.
I stumbled on this when a network printer was automatically added to my list of printers. Apparently is some sort of network printer, probably ipp protocol, so cups just added it with no intervention from me.
#1 Updated by Pascal Obry over 4 years ago
- Priority changed from Low to Medium
I have proposed a patch to fix that. If you feel like testing it, do not hesitate!