Don't handle CUPS' "connecting-to-device" state reason

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).

diff --git a/modules/printbackends/cups/gtkprintbackendcups.c b/modules/printbackends/cups/gtkprintbackendcups.c
index 4b26cba5d3f9a9f9dce3fef09ad84f569609c27e..11616186ff674c560d76c73199c1967c1daa0213 100644 (file)
--- a/modules/printbackends/cups/gtkprintbackendcups.c
+++ b/modules/printbackends/cups/gtkprintbackendcups.c
@@ -1665,7 +1665,6 @@ cups_request_printer_list_cb (GtkPrintBackendCups *cups_backend,
           "media-low",
           "media-empty",
           "offline",
-          "connecting-to-device",
           "other"
         };
       static const char * reasons_descs[] =
@@ -1685,7 +1684,6 @@ cups_request_printer_list_cb (GtkPrintBackendCups *cups_backend,
           N_("Printer '%s' is low on paper."),
           N_("Printer '%s' is out of paper."),
           N_("Printer '%s' is currently off-line."),
-          N_("Printer '%s' may not be connected."),
           N_("There is a problem on printer '%s'.")
         };
       gboolean is_paused = FALSE;