Package Details: epson-inkjet-printer-201212w 1.0.0-9

Git Clone URL: (read-only)
Package Base: epson-inkjet-printer-201212w
Description: Epson printer driver (WF-3010, WF-3520, WF-3530, WF-3540)
Upstream URL:
Licenses: LGPL, custom:Epson Licence Agreement
Submitter: itoijala
Maintainer: Misery
Last Packager: Misery
Votes: 15
Popularity: 0.050728
First Submitted: 2012-12-30 18:52
Last Updated: 2018-05-01 14:46

Latest Comments

2bluesc commented on 2016-09-10 19:59

There's a breakage if this is built with Clang due to Clang's stricter -Wreturn-type flag which reveals a `return 0;` from a function that's supposed to return void.

I have a patch that can be applied to the AUR repo @

Direct link to patch:

catalin.hritcu commented on 2014-11-15 21:44

Nevermind, it seems that my wifi router sometimes chooses a different IP address. Not the driver's fault, sorry for the noise.

catalin.hritcu commented on 2014-11-15 14:19

I have a WF-3520 and most of the times I try to print I get the following error in CUPS: Processing - "The printer is unreachable at this time." Printing via the cloud works fine though.

Misery commented on 2013-09-30 16:18

There should be no difference if you add --enable-debug before or after --prefix. But I don't know why there is no "epson-inkjet-printer-filter.txt" file. Maybe the file has another name? I didn't checked every driver for that file.

I looked into the sources... is there one of these files??

debuglog.h:50: #define LOGFILENAME "/tmp/"PACKAGE_NAME".txt"
err.h:36:#define DEBUG_PATH "/tmp/eps_debug.txt"
err.h:37:#define EPS_DEBUG_PATH2 "/tmp/esp_time.txt"

Yes, you should rebuild your driver because it WOULD print "useless" debug information.

thaerin commented on 2013-09-24 22:22


It seems to be working now. Scrutinizing the error_log via cups web server utility I noticed ghostscript was missing. I installed that and the test page printed and I was then able to print from gedit, as well.

That being said, I still hope to understand the whole "--enable-debug" thing and why I never got the '/tmp/epson-inkjet-printer-filter.txt' file. Furthermore, do I need to reinstall the driver without the "--enable-debug" flag now that it is seemingly working? As far as I can tell, my use of that flag did not change anything.

As an aside for others that may be struggling to install a network printer, ufw blocks discovery of the printer despite rules in place to allow communication on the local network. Previously it had prevented the discovery of my media server or I may have been stumped quite a lot longer when cups couldn't find my printer. 'ufw disable' allows discovery and hopefully still works after 'ufw enable'. Otherwise one may require a special iptables rule to allow packets before ufw drops them. Perhaps something like: 'iptables -I ufw-before-input -s <printer ip address> -d <computer ip address> -j ACCEPT'.

thaerin commented on 2013-09-24 20:44

Hehe, sorry for the weirdness! :D

Anyway, I had noticed that in the PKGBUILD, but I'm not sure I understand how to implement it correctly. I'm quite new to arch (liking it a lot so far). After reading your comment I tried uninstalling the driver (pacman -Rs epson...), deleted the previous folder, and redid the installation. Only this time before 'makepkg' I edited the PKGBUILD to add the '--enable-debug'. The original was like:

"# if you have runtime problems: add "--enable-debug" and look into /tmp/epson-inkjet-printer-filter.txt
./configure LDFLAGS="$LDFLAGS -Wl,--no-as-needed" --prefix=/opt/$pkgname

I tried adding '--enable-debug' after '--prefix=/opt/$pkgname', I tried adding it before 'LDFLAGS=...', and I tried adding it after '--no-as-needed'. The one after '--no-as-needed' would not complete the 'makepkg' process. The other two went as smoothly as before, I re-added the printer in cups, and I ran into the same problem as before. When I checked the /tmp for epson-inkjet-printer.txt, it was not there.

I suspect I'm fundamentally misunderstanding something. Any idea what I'm doing wrong?

Thanks for the assistance!

Misery commented on 2013-09-24 08:09

Well, that's a weird comment. ;-)

Did you try this one in your PKGBUILD?
---> if you have runtime problems: add "--enable-debug" and look into /tmp/epson-inkjet-printer-filter.txt

thaerin commented on 2013-09-24 05:59

Also, fwiw, I'm trying to set up the WF-3540 for network printing.

thaerin commented on 2013-09-24 05:51

Does not work.

Everything seems okay until you try to print and get "stopped 'filter failed'". Then you check the error_log and find: "(/opt/epson-inkjet-printer-201212w/cups/lib/filter/epson_inkjet_printer_filter) stopped with status 1" and "Job stopped due to filter errors; please consult the error_log file for details". Then, to your dismay, you Google only to find that this is one of those particularly annoying random problems that seems to effect people on various distros going back for years. The proposed solutions are about as varied as the people experiencing the problems.

Currently, I am at a loss and have no idea what to try next. If I sort it out I'll post back. Otherwise, I'm hoping someone else can point me in the right direction. Basic printing should not be this complicated to set up.

itoijala commented on 2012-12-30 18:52

copied PKGBUILD from epson-inkjet-printer-201211w