Linux Lite Forums

Hardware - Support => Printing and Scanning => Topic started by: Sprintrdriver on June 23, 2019, 11:12:53 AM

Title: Vuescan must be run as root to be able to find scanner(s) [solved]
Post by: Sprintrdriver on June 23, 2019, 11:12:53 AM
Hi.
I'm trying out the program Vuescan before I decide to buy a licence for it.
The only practical problem is that the program does not detect any scanner (regarless of model, or connection method) unless I run it as root.The excact message: "VueScan didn't find a scanner connected to your computer."

When searching for a solution on the web, I found an old thread on ubuntuforum:https://ubuntuforums.org/showthread.php?t=2180205
Unfortunately, there is one, possible two major problems with that description:My test - Hoped it should work:  Contents of /etc/udev/rules.d/99-local.rules
Code: [Select]
SUBSYSTEM="usb_device", ACTION="add", GOTO="epson_rules_end"

# Epson XP-432 "Expression home"
ATTR{idVendor}="04b8", ATTR{idProduct}="1104 ", SYMLINK+="scan-epson-xp432", MODE="0666", OWNER="geir", GROUP="scanner"

LABEL="epson_rules_end"
But to no avail. Vuescan still say no scanner found unless run as root.

The output from lsusb -v https://pastebin.com/R8DCkFW1 (https://pastebin.com/R8DCkFW1)


[EDIT ]
Also tried to follow the instructions found on VUescan homepage - at here (https://www.hamrick.com/vuescan/vuescan.htm#linux) - and link to possibe ubuntu solution (https://help.ubuntu.com/community/SettingScannerPermissions).

So then I created the file /lib/udev/rules.d/40-libsane.rules as it did not existed before (sudo touch file-name).

I then opened the file in text editor as root, and inserted this content:
Code: [Select]
# Epson XP-432 expression home
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="1104", ENV{libsane_matched}="yes"

I then make my own user member of saned group.

Unfortunately, this action did not change anything :wallbash:
Title: Re: Vuescan must be run as root to be able to find scanner(s) [solved]
Post by: Sprintrdriver on June 23, 2019, 12:19:39 PM
Solved !

Problem was solved after a reboot of the computer.