CUPS backend shouldn't handle "connecting-to-device" state reason. It shows "Printer '%s' may not be connected" for this state, which is not true in almost all cases. Better is to use "printer-state-message" which contains correct message (#622011).
CUPS backend shouldn't handle "connecting-to-device" state reason. It shows "Printer '%s' may not be connected" for this state, which is not true in almost all cases. Better is to use "printer-state-message" which contains correct message (#622011).