From 998459afb7ae8be77c138a879d82765785f3f54e Mon Sep 17 00:00:00 2001 From: Marek Kasik Date: Thu, 24 Jun 2010 09:27:16 +0200 Subject: [PATCH] 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). --- modules/printbackends/cups/gtkprintbackendcups.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/modules/printbackends/cups/gtkprintbackendcups.c b/modules/printbackends/cups/gtkprintbackendcups.c index 4b26cba5d..11616186f 100644 --- 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; -- 2.43.2