EPSON printer via WLAN doesn't accept print jobs

Hey there,

recently, I upgraded my 42.1 box to 42.2 via fresh install. I own an EPSON WorkForce 2760 inkjet printer. With 42.1 I had no trouble using my printer via WLAN. Under 42.2 the setup dialogues have changed significantly, and I can’t get my printer working.

I installed the appropriate EPSON driver and added my printer’s IP address as ip:// device in YaST. It appears in the printer setup and can be configured. Now, when I want to start a print job, printer management tells me it connected successfully to the device. But then it stops, saying “print job not accepted”.

A quick Google research suggested a problem with openSUSE’s firewall, but deactivating the firewall doesn’t change anything.

Any hints to what might be the problem?

I installed the appropriate EPSON driver and added my printer’s IP address as ip:// device in YaST.

Do you mean ‘ipp://’ perhaps?

lpstat -t

Sure, that’s what I meant.

prompt: # lpstat -t

scheduler is running
system default destination: EPSON_WF-2760
device for EPSON_WF-2760: ipp://[printer's IP]
EPSON_WF-2760 accepting requests since Di 22 Nov 2016 07:00:10 CET
printer EPSON_WF-2760 is idle.  enabled since Di 22 Nov 2016 07:00:10 CET

Perhaps worth checking /var/log/cups/error_log for more information.

If necessary put CUPS in debugging mode with

sudo cupsctl --debug-logging

Cancel any stale print jobs

cancel -a

then try printing again. Examine the error_log. You can share the lengthy output by uploading to https://paste.opensuse.org/ and post the link to it here.

BTW, does a test page print successfully?

I usually use the CUPS web interface for configuration and administrative tasks…
http:/localhost:631/printers

Click on the printer listed then Maintenance > Print Test Page

Just in case this is relevant, I wanted to share the openSUSE 42.2 release notes concerning CUPS 1.7 and the IPP protocol default version changing from 1.1 to 2.0…
https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/42.2/#fate-314630

It may or may not be the issue here, but in any case you could try using the ‘socket://’ protocol instead (as I understand many Epson models support this network protocol).

That did the trick. Now it’s working perfectly. Thank you so much!

Pleased to read of your success with this! :slight_smile: