Adding a printer via the CUPS web interface fails on my rpi (1) that I now reuse as a print server (Thanks a lot for this great project!).
I've gone through a bit of troubleshooting and found the reason the printer setup fails before the driver selection page. The driver list is too long to be parsed by a rather slow pi before a hard timeout is reached, so you receive a rather odd error containing both "Error" and "success" instead of being able to select a driver and therefore add the printer.
A possible fix for me was to run lpinfo -m on the cups container as described here.
That way the driver XML gets parsed beforehand and the CUPS GUI can actually display all information in time, so that I was able to add my printer via the GUI as expected after running the command and refreshing the CUPS web interface.
You may want to run lpinfo -m on service startup, so that others don't have to deal with that manually. It seems that lpinfo -m actually caches the available drivers, so that the GUI can be displayed in time even on very slow hardware.
willswire
commented
2 years ago
Adding a printer via the CUPS web interface fails on my rpi (1) that I now reuse as a print server (Thanks a lot for this great project!).
I've gone through a bit of troubleshooting and found the reason the printer setup fails before the driver selection page. The driver list is too long to be parsed by a rather slow pi before a hard timeout is reached, so you receive a rather odd error containing both "Error" and "success" instead of being able to select a driver and therefore add the printer.
A possible fix for me was to run
lpinfo -mon thecupscontainer as described here. That way the driver XML gets parsed beforehand and the CUPS GUI can actually display all information in time, so that I was able to add my printer via the GUI as expected after running the command and refreshing the CUPS web interface.You may want to run
lpinfo -mon service startup, so that others don't have to deal with that manually. It seems thatlpinfo -mactually caches the available drivers, so that the GUI can be displayed in time even on very slow hardware.