Comment 25 for bug 1613027
Revision history for this message
| Anthony Buckley (tony-buckley) wrote | #25 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
e3ace39
(Get the code!)
Hello Christopher,
Sorry for the delay in responding. I've been away.
1. I tested 1.0.4 shortly after release and I can confirm that the problem still persists. The network plug-in in the package (iscan-network-nt) that I am fairly sure is the problem has not been changed since 2013. This plug-in is proprietary and we don't have source code (that I can find anyway).
2. My interactions with Epson support bordered on being comical.
I first contacted them shortly after I noticed the problem on the off chance they may have had some input. The response was that they do not support Linux and simply provided a link to the driver download page.
I next contacted them when I was pretty sure what the problem was, explaining that I understood there was no Linux support, but that I didn't want support as such. I explained in general terms what was happening, what needed to be done and that I was trying to trace the origins / ownership of the network plug-in or could they follow it up. The response I received was that they are very supportive of Linux and then proceeded to tell me all the options for "printing" under Linux and that my best option was to use GIMP! When I responded (politely) that nowhere in my mail did I mention printing, but that I had mentioned a scanner problem several times, they responded that they thought I should contact my computer support - Linux!
So, in effect, I got nowhere. At least I have a workaround.