As of Kubuntu 17.10, my Epson V33 Perfection scanner stopped working with Linux. I bought this scanner specifically because it did work with Linux. That it stopped working was a serious disappointment as I have been using the same scanner for years and regularly need it for a variety of things.

I tried installing older versions of the software (I’ve kept the downloads from Epson for years) but that didn’t work. I tried it on a different computer with the same OS and that didn’t work. I tried a lot of troubleshooting and came up empty. After hours of trying various solutions, I gave up (that was a few months ago).

However, when my CPU died on my desktop computer forcing me to reformat it again about a month after I had previously tried, I figured it was time to try to solve this again. This time, however, I quickly came across the answer online (see here). It turns out, this is a bug in the latest version of the scanning software that ships with Linux, which confirmed that it wasn’t a problem with my scanner or with Epson’s software. Here’s what I did to fix the problem.

First, go ahead and install the latest version of Epson’s software from their website (start here – or just here – lots of clicks to get to where you need to go).

Untar the file you download and read the directions for how to install the software. (Basically, navigate to the directory you just untarred in a terminal then run ./

Before this bug, that was all you needed to do and the scanner would work. Now, there are two more steps.

The second step, also at the terminal, is to type in:

sudo ln -sfr /usr/lib/sane/libsane-epkowa* /usr/lib/x86_64-linux-gnu/sane

I’m not exactly sure what this command does but the “ln” command creates symbolic links, so I’m guessing it’s linking two files or commands that help correct the bug in the latest iteration of the software.

Then, open a text editing program and create a new, blank file. In that file, you’re going to add the following content:

# chmod device EPSON group
ATTRS{manufacturer}=="EPSON", DRIVERS=="usb", SUBSYSTEMS=="usb", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="*", MODE="0777"

The first line of this file is just a comment. The second adds information about Epson scanners.

Save the file as “79-udev-epson.rules”.

Now, move that file from wherever you created it to the following directory:


Like this:

Now, restart your computer. This worked for me. Hopefully, it will work for you too.


18 Replies to “Linux – Fixing the Epson (V33 Perfection) Scanner Issue in Kubuntu 18.04”

  1. 20180829
    I implemented your fix under Ubuntu 18.04 LTS running the Gnome Flashback desktop. It worked: my V33 started working just as it had under 16.04 and Debian 9. Thanks for the post.

  2. I’ve followed all the steps to resurrect my Epson V330, but I’m stuck near the end – trying to move the file to the new directory, all I’m getting is:

    mv: cannot move ‘/home/stasia/Desktop/79-udev-epson.rules’ to ‘/etc/undev.rules.d/’: Not a directory

    Incidentally, I do vaguely remember an etc folder in Home before the upgrade to 18.04, but it ain’t there anymore (and I do see all the hidden files/folders there).

    I regret upgrading to 18.04, its screwy in general.

    1. I’m glad you found an answer.

      However, I saw two problems in the command you posted. First, you need to use “sudo mv” for the command. Second, you misspelled “undev.rules.d”. It should be “udev.rules.d”. Those alterations would probably have worked for you.

  3. damn.

    I get this .

    “E: Repository ‘ stable Release’ changed its ‘Origin’ value from ‘Google, Inc.’ to ‘Google LLC’
    N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.”

    and now I’m stuck.

    1. That’s actually a problem I can help you with.


      “sudo apt update” and/or “sudo apt upgrade” (without the “-get”)

      You’ll then get a prompt to accept the new repository from Google. Say “Y” and you should be good to go.

  4. Thanks a lot. I have a V550 scanner. Found a fix that mentioned the rules file but not the symbolic link for the sane drivers. That got me working. This really needs to be widely documented.

  5. Dear Ryan,

    thank you very much for publishing this solution. It worked exactly as you described on my Kubuntu 18.04 but I would never have gotten this on my own.
    You da Man!


Leave a Reply

Your email address will not be published. Required fields are marked *