SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
When I try to start iscan, error occurs:
$> iscan
iscan: error while loading shared libraries: libgphoto2.so.2: cannot open shared object file: No such file or directory
I do not use iscan directly for scanning, rather I use the iscan "epkowa" backend for sane so that I can use the Gimp to acquire images from the scanner.
I have downloaded iscan and iscan-data x86_64 slackware packages from here:
http://www.giustetti.net/wiki/index.php?title=Iscan_and_Slackware_14.0
and libgphoto2 from here:
http://slackbuilds.org/mirror/slackware/slackware-14.1/source/l/libgphoto2/
You installed iscan packages for Slackware 14.0 and libgphoto2 for Slackware 14.1 and now have library mismatches. The iscan builds were probably based on an older version of libgphoto2 and since you built a newer one, the iscan libraries complain.
Alien Bob (aka Eric Hameleers) has created an iscan package that seems to not require libgphoto2, however, it does have two dependencies, iscan-data and iscan-network-nt. Uninstall iscan and iscan-data and then try installing these.
It's a good idea to try and stay away from packages that were built for previous versions of Slackware as you can run into a lot of dependency mismatched errors. And Eric is awesome with his amount of packages (he is part of the Slackware development team, so his packages are some of the best -- and he provides slackbuilds if you want to build them yourself), so it's always a good idea to check and see if he has a package available.
EDIT: And Eric beat me to it
Last edited by bassmadrigal; 08-03-2015 at 07:54 AM.
Reason: Too slow...
Many thanks, I have installed it and it looks like it's installed correctly.
Now I have (unrelevant output stripped):
root@x301:~# sane-find-scanner
found USB scanner (vendor=0x04b8 [Seiko Epson Corp. ], product=0x0147 [EPSON DS-30 ]) at libusb:004:005
in dmesg:
[ 2886.401163] usb 4-1: new high-speed USB device number 5 using ehci-pci
[ 2886.530409] usb 4-1: New USB device found, idVendor=04b8, idProduct=0147
[ 2886.530419] usb 4-1: New USB device strings: Mfr=10, Product=11, SerialNumber=12
[ 2886.530426] usb 4-1: Product: EPSON DS-30
[ 2886.530431] usb 4-1: Manufacturer: Seiko Epson Corp.
[ 2886.530436] usb 4-1: SerialNumber: Q5FZ011327
But when I run iscan:
1ac0@x301:~# iscan
message "Could not send command to scanner. Check the scanner's status." appear
Not know how to continue to do my scanner to work.
You ran sane-find-scanner as root, and then iscan as a non-root user, right? If so you might have a permissions problem on the USB device file for the scanner.
Quick way to check: run sane-find-scanner as your non-root user. If it works as root and not otherwise, you have a permissions problem in the device file.
Use 'lsusb' to find the scanner's current USB Bus and Device number, for example "Bus 004 Device 001".
Then look at the permissions on /dev/bus/usb/BBB/DDD where BBB=bus number, DDD=device number. It should be set to group 'scanner' or 'lp' (depending on the Slackware setup), with group read and write. And your user ID should be in that group.
If the owner/permissions are wrong, you need a udev rule to set it up.
You ran sane-find-scanner as root, and then iscan as a non-root user, right? If so you might have a permissions problem on the USB device file for the scanner.
Quick way to check: run sane-find-scanner as your non-root user. If it works as root and not otherwise, you have a permissions problem in the device file.
Use 'lsusb' to find the scanner's current USB Bus and Device number, for example "Bus 004 Device 001".
Then look at the permissions on /dev/bus/usb/BBB/DDD where BBB=bus number, DDD=device number. It should be set to group 'scanner' or 'lp' (depending on the Slackware setup), with group read and write. And your user ID should be in that group.
If the owner/permissions are wrong, you need a udev rule to set it up.
Your user account must of course be a member of the "scanner" group. I had assumed the OP was aware of that, but that assumption may have been incorrect.
Your user account must of course be a member of the "scanner" group...
The reason I said 'scanner or lp', was - didn't that get changed in Slackware 14.0, to put scanners into the 'lp' group? In order to better support multi-function devices? (I still use 'scanner' but I think it did change.)
The reason I said 'scanner or lp', was - didn't that get changed in Slackware 14.0, to put scanners into the 'lp' group? In order to better support multi-function devices? (I still use 'scanner' but I think it did change.)
You are right of course: the user account needs to be in group "lp" (for good measure you can still put/kep it in "scanner" group as well but that should not be required). See http://taper.alienbase.nl/mirrors/sl..._AND_HINTS.TXT
You ran sane-find-scanner as root, and then iscan as a non-root user, right? If so you might have a permissions problem on the USB device file for the scanner.
Quick way to check: run sane-find-scanner as your non-root user. If it works as root and not otherwise, you have a permissions problem in the device file.
Use 'lsusb' to find the scanner's current USB Bus and Device number, for example "Bus 004 Device 001".
Then look at the permissions on /dev/bus/usb/BBB/DDD where BBB=bus number, DDD=device number. It should be set to group 'scanner' or 'lp' (depending on the Slackware setup), with group read and write. And your user ID should be in that group.
If the owner/permissions are wrong, you need a udev rule to set it up.
I have added my user into 'lp' group and 'scanner' group:
1ac0@x301:/dev/bus/usb/002 $> cat /etc/group | grep 1ac0
lp:x:7:lp,1ac0
scanner:x:93:1ac0
1ac0:x:1000:
and permissions for scanner (on current bus number) is:
1ac0@x301:/dev/bus/usb/002 $> ls -la 002
crw-rw-r-- 1 root lp 189, 129 Aug 5 08:01 002
Now I can run 'sane-find-scaneer' under normal account (unrellevant output stripped):
1ac0@x301:/dev/bus/usb/002 $> sane-find-scanner
found USB scanner (vendor=0x04b8 [Seiko Epson Corp. ], product=0x0147 [EPSON DS-30 ]) at libusb:002:002
But when I run iscan, result is same 'Could not send command to scanner. Check the scanner's status.'
At the moment I'm missed what to do next. Checking USB kernel modules? Something else? Maybe problem that scanner is not in power on mode?
I looked at the source, and unfortunately that error message is a catch-all for many things that can go wrong when the scanner is first opened and commands are sent.
However, in the iscan-data package that goes with iscan, I see the following note in the SUPPORTED-DEVICES file:
Quote:
- DS-30 (requires iscan-plugin-ds-30)
So it looks like your DS-30 scanner requires an additional package, called "iscan plugin package" on Epson's download site, listed for the DS-30. I don't think Alien Bob has this on his site, so you will have to get it from Epson and figure how to install it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.