I have a Lexmark E120 network connected via ethernet. Occasionally, attempts to print to this printer result in the subject error message. So, the only resolution that I have found is to reboot the box. The printer then works for a while. I'm not sure how long it lasts as I rarely print anything.
Rebooting is a bit drastic for the occasional print so I hope there is a better fix.
Cheers and thanks, Stephen
if it uses dhcp, is the lease expiring??
On Wed, Jan 13, 2016 at 7:47 PM, Stephen Davies sdavies@sdc.com.au wrote:
I have a Lexmark E120 network connected via ethernet. Occasionally, attempts to print to this printer result in the subject error message. So, the only resolution that I have found is to reboot the box. The printer then works for a while. I'm not sure how long it lasts as I rarely print anything.
Rebooting is a bit drastic for the occasional print so I hope there is a better fix.
Cheers and thanks, Stephen --
============================================================================= Stephen Davies Consulting P/L Phone: 08-8177 1595 Adelaide, South Australia. Mobile:040 304 0583 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On 14/01/16 14:22, Jack Craig wrote:
if it uses dhcp, is the lease expiring??
On Wed, Jan 13, 2016 at 7:47 PM, Stephen Davies <sdavies@sdc.com.au mailto:sdavies@sdc.com.au> wrote:
I have a Lexmark E120 network connected via ethernet. Occasionally, attempts to print to this printer result in the subject error message. So, the only resolution that I have found is to reboot the box. The printer then works for a while. I'm not sure how long it lasts as I rarely print anything. Rebooting is a bit drastic for the occasional print so I hope there is a better fix. Cheers and thanks, Stephen -- ============================================================================= Stephen Davies Consulting P/L Phone: 08-8177 1595 Adelaide, South Australia. Mobile:040 304 0583 -- users mailing list users@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org> To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Good thought but no; it has a hard-wired IP. The issue seems only to have arisen since F22.
On Thu, 2016-01-14 at 14:17 +1030, Stephen Davies wrote:
I have a Lexmark E120 network connected via ethernet. Occasionally, attempts to print to this printer result in the subject error message. So, the only resolution that I have found is to reboot the box. The printer then works for a while. I'm not sure how long it lasts as I rarely print anything.
Cups can remember printer errors, to prevent printing to a printer when the paper is out. Sometimes remembering errors means it never, ever tries again, and you get the old error message.
You can try 'cupsenable <printername>' the next time it happens instead of rebooting, to reset the error. If that does work, you need something like 'lpadmin -p <printer> -o error-policy=retry-job'. I've forgotten the exact spelling.
There's an option to retry every 30 seconds. I don't know if that's the default in f22.
Also, ping <ip> -- check if it is down. This will tell you if it's a cups or networking error.
On 14/01/16 15:51, Berend De Schouwer wrote:
On Thu, 2016-01-14 at 14:17 +1030, Stephen Davies wrote:
I have a Lexmark E120 network connected via ethernet. Occasionally, attempts to print to this printer result in the subject error message. So, the only resolution that I have found is to reboot the box. The printer then works for a while. I'm not sure how long it lasts as I rarely print anything.
Cups can remember printer errors, to prevent printing to a printer when the paper is out. Sometimes remembering errors means it never, ever tries again, and you get the old error message.
You can try 'cupsenable <printername>' the next time it happens instead of rebooting, to reset the error. If that does work, you need something like 'lpadmin -p <printer> -o error-policy=retry-job'. I've forgotten the exact spelling.
There's an option to retry every 30 seconds. I don't know if that's the default in f22.
Also, ping <ip> -- check if it is down. This will tell you if it's a cups or networking error.
Just had to reboot again to be able to print but will try your suggestions again now. (ping worked before and after reboot)
Thanks, Stephen
On Thu, 14 Jan 2016, Stephen Davies wrote:
I have a Lexmark E120 network connected via ethernet. Occasionally, attempts to print to this printer result in the subject error message. So, the only resolution that I have found is to reboot the box. The printer then works for a while. I'm not sure how long it lasts as I rarely print anything.
Rebooting is a bit drastic for the occasional print so I hope there is a better fix.
Cheers and thanks, Stephen
I'm having the same problem with F23, only with an HP PhotoSmart on wireless. Instead of rebooting, I keep removing and re-adding the printer. I don't have the problem with Mint 17.3. The other thing that works *sometimes* is to pause and unpause the printer a few times from the System Settings -> Printers -> open queue in KDE.
billo
On 15/01/16 02:24, vendor@billoblog.com wrote:
On Thu, 14 Jan 2016, Stephen Davies wrote:
I have a Lexmark E120 network connected via ethernet. Occasionally, attempts to print to this printer result in the subject error message. So, the only resolution that I have found is to reboot the box. The printer then works for a while. I'm not sure how long it lasts as I rarely print anything.
Rebooting is a bit drastic for the occasional print so I hope there is a better fix.
Cheers and thanks, Stephen
I'm having the same problem with F23, only with an HP PhotoSmart on wireless. Instead of rebooting, I keep removing and re-adding the printer. I don't have the problem with Mint 17.3. The other thing that works *sometimes* is to pause and unpause the printer a few times from the System Settings -> Printers -> open queue in KDE.
billo
Thanks for that. I will try it next time.
-
Berend De Schouwer -
Jack Craig -
Stephen Davies -
William Oliver