Garuda arch - printer monitor goes to stopped after each job, and printed job goes to "pending"
Posted: Sun Jun 19, 2022 10:30 am
Hi,
I am running Turboprint on Garuda Linux (Arch) with an Epson SC P600 printer. This setup has always worked just fine, until a while back when the printer no longer started printing when I used the print command in an app (any app). When I opened the printer monitor, I saw that my print job was in the queue, but with status "pending", and with the queue status being "stopped" and set to "reject jobs". I had to manually set the queue to "Accept jobs" and to status "printing" to get my document printed.
However, after printing the job, the job stays in the queue with status "pending", and the queue status goes back to "stopped". This happens after every print job. So in order to use the printer, I each time have to:
- open the print monitor
- Make sure the queue status is set to "Idle"
- launch the print job from the app that needs to print
- when the job finishes, I have to select the just-printed job, and "cancel" it, in order to remove it from the queue
- set the queue status back to "Idle"
This makes using Turboprint quite labor-intensive.
Does anybody know how to solve this problem? Many thanks for your suggestions.
Best regards,
Gino Eelen
I am running Turboprint on Garuda Linux (Arch) with an Epson SC P600 printer. This setup has always worked just fine, until a while back when the printer no longer started printing when I used the print command in an app (any app). When I opened the printer monitor, I saw that my print job was in the queue, but with status "pending", and with the queue status being "stopped" and set to "reject jobs". I had to manually set the queue to "Accept jobs" and to status "printing" to get my document printed.
However, after printing the job, the job stays in the queue with status "pending", and the queue status goes back to "stopped". This happens after every print job. So in order to use the printer, I each time have to:
- open the print monitor
- Make sure the queue status is set to "Idle"
- launch the print job from the app that needs to print
- when the job finishes, I have to select the just-printed job, and "cancel" it, in order to remove it from the queue
- set the queue status back to "Idle"
This makes using Turboprint quite labor-intensive.
Does anybody know how to solve this problem? Many thanks for your suggestions.
Best regards,
Gino Eelen