Since upgrading to Suse 12.3 I have noticed that if a send a document to
my configured USB printer after having forgotten to turn on the power to that printer
then I can no longer print anything even after I power up the printer.
I then have to fire up Yast2 and go to Printer Configurations where I see that
Printer status has gone from “Ready” to “Printout disabled”.
The only way I know to restore the printer to ready state is to “Edit” the configuration in Yast2,
which involves sitting through the endless “Retrieving printer driver information…” progress bar
and other delays before I can re-check the “Enable Printing” checkbox. Then comes the glacial
“Modifying printer Setup” progress bar. This all adds up to a real pain.
Is there any way to keep the printer configuration status from changing if I forget printer power?
or
Is there an easier way to re-set the printer status to ready without going through Yast?
PS: I notice that if I attempt to print a test page from Printer Configurations for a
configuration in status ready but with printer power off then or course nothing emerges
from the printer. If I then press “Testpage printing failed” the printer status automatically
goes to “Printout disabled”. Then I get to go through the Edit Configuration again.
> The only way I know to restore the printer to ready state is to “Edit”
> the configuration in Yast2,
No, you should go to “localhost:631” in a web browser and activate it
there. There is also a CLI command for it, too, which I don’t remember
right now. lpsomething, perhaps.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
With your instructions I found the “Resume printer” function at localhost:631.
This is helpful and much easier than going to Yast.
But I was also hoping to find a way to prevent the printer from automatically going into “paused” status due to sending a print job to powered-down printer.
As far as I remember from previous releases, queued jobs would simply begin to print as soon as I turn the printer on,
which I believe was the behavior before I upgraded to 12.3.
On 2013-09-13 22:26, helge59 wrote:
>
> Thanks for responding.
>
> With your instructions I found the “Resume printer” function at
> localhost:631.
>
> This is helpful and much easier than going to Yast.
I found the cli command, it could be “cupsenable”. I do not have a stuck
printer to try it on at this moment). There are some printer commands
that start with “cups…” and some other that start with “lp…”. Some
work as user, some as root.
>
> But I was also hoping to find a way to prevent the printer from
> automatically going into “paused” status due to sending a print job to
> powered-down printer.
>
> As far as I remember from previous releases, queued jobs would simply
> begin to print as soon as I turn the printer on,
> which I believe was the behavior before I upgraded to 12.3.
Dunno. It may be intentional for hot-plugged printers. It sounds
familiar, somehow.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)