I've taken charge of my first scanner (a freebie from a friend) but I'm having trouble getting it installed. If I go to XSane it says "failed to open device snapscan :libusb:001:002 " . I have since installed every XSane extra there was via synaptic but it's still won't play ball. I'm very reluctant to give in though so how do I investigate what's up? And even more to the point, how do I fix it? It knows it's there I'm sure.
[Ubuntu 8.04]
Bev.
On 30 September 2010 16:53, Bev Nicolson lumos60@gmail.com wrote:
I've taken charge of my first scanner (a freebie from a friend) but I'm having trouble getting it installed. If I go to XSane it says "failed to open device snapscan :libusb:001:002 " . I have since installed every XSane extra there was via synaptic but it's still won't play ball. I'm very reluctant to give in though so how do I investigate what's up? And even more to the point, how do I fix it? It knows it's there I'm sure.
Can you be more specific about the brand and model? Does it show up when you run "lsusb"?
[Ubuntu 8.04]
Is the scanner older than 2 years?
Regards, Tim.
On 30 Sep 17:28, Tim Green wrote:
On 30 September 2010 16:53, Bev Nicolson lumos60@gmail.com wrote:
I've taken charge of my first scanner (a freebie from a friend) but I'm having trouble getting it installed. If I go to XSane it says "failed to open device snapscan :libusb:001:002 " . I have since installed every XSane extra there was via synaptic but it's still won't play ball. I'm very reluctant to give in though so how do I investigate what's up? And even more to the point, how do I fix it? It knows it's there I'm sure.
Can you be more specific about the brand and model? Does it show up when you run "lsusb"?
It's a snapscan, it's been detected by XSane. It's a permissions problem most likely. The fact that XSane has detected it is a *GOOD* sign.
[Ubuntu 8.04]
Is the scanner older than 2 years?
Regards, Tim.
main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
On 30-Sep-10 15:53:07, Bev Nicolson wrote:
I've taken charge of my first scanner (a freebie from a friend) but I'm having trouble getting it installed. If I go to XSane it says "failed to open device snapscan :libusb:001:002 " . I have since installed every XSane extra there was via synaptic but it's still won't play ball. I'm very reluctant to give in though so how do I investigate what's up? And even more to the point, how do I fix it? It knows it's there I'm sure.
[Ubuntu 8.04]
Bev.
Hi Bev, First, what make & model of scanner is it? And what mode of connection are you using? (Looks like USB, from what you quote above).
You may try to (a) plug it in and switch it on, then (b) look at the output of
cat /proc/bus/usb/devices
You should see a few blocks of lines, one of which should be identifiable as info about your scanner which has been recognised by your system. E.g. I just did this with a USB stick (manufactured by PNY) and saw (2nd block of stuff):
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 5 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=154b ProdID=6545 Rev= 2.00 S: Manufacturer=PNY S: Product=USB 2.0 FD S: SerialNumber=1100831DD6033F17 C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=200mA I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
In particular, the line labelled "I:" shows how the system is accessing it.
If you post that output to us, we may be able to help!
Ted.
-------------------------------------------------------------------- E-Mail: (Ted Harding) Ted.Harding@manchester.ac.uk Fax-to-email: +44 (0)870 094 0861 Date: 30-Sep-10 Time: 17:32:11 ------------------------------ XFMail ------------------------------
On 30 Sep 17:32, Ted Harding wrote:
On 30-Sep-10 15:53:07, Bev Nicolson wrote:
I've taken charge of my first scanner (a freebie from a friend) but I'm having trouble getting it installed. If I go to XSane it says "failed to open device snapscan :libusb:001:002 " . I have since installed every XSane extra there was via synaptic but it's still won't play ball. I'm very reluctant to give in though so how do I investigate what's up? And even more to the point, how do I fix it? It knows it's there I'm sure.
[Ubuntu 8.04]
Bev.
Hi Bev, First, what make & model of scanner is it? And what mode of connection are you using? (Looks like USB, from what you quote above).
As it's also stated above that that's a message from XSane, you can bet your life that XSane has detected the scanner and can probably use it...
See other posts for what's likely to be wrong...
You may try to (a) plug it in and switch it on, then (b) look at the output of
cat /proc/bus/usb/devices
You should see a few blocks of lines, one of which should be identifiable as info about your scanner which has been recognised by your system. E.g. I just did this with a USB stick (manufactured by PNY) and saw (2nd block of stuff):
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 5 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=154b ProdID=6545 Rev= 2.00 S: Manufacturer=PNY S: Product=USB 2.0 FD S: SerialNumber=1100831DD6033F17 C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=200mA I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
In particular, the line labelled "I:" shows how the system is accessing it.
If you post that output to us, we may be able to help!
Ted.
E-Mail: (Ted Harding) Ted.Harding@manchester.ac.uk Fax-to-email: +44 (0)870 094 0861 Date: 30-Sep-10 Time: 17:32:11 ------------------------------ XFMail ------------------------------
main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
On 30 Sep 16:53, Bev Nicolson wrote:
I've taken charge of my first scanner (a freebie from a friend) but I'm having trouble getting it installed. If I go to XSane it says "failed to open device snapscan :libusb:001:002 " . I have since installed every XSane extra there was via synaptic but it's still won't play ball. I'm very reluctant to give in though so how do I investigate what's up? And even more to the point, how do I fix it? It knows it's there I'm sure.
[Ubuntu 8.04]
At a guess, and this will be a guess, the scanner 'device' is owned by the wrong group, or a group you're not in...
do: ls -la /dev/bus/usb/001/002
You should then know what user and group owns the scanner, you can check your own groups using id, if you're not in the group that owns the scanner (I'd guess it'll be "scanner"), then add yourself to the group, logout and log back in again.
All being well, Bob should be your mother's brother.
Cheers,
On Thursday 30 September 2010 16:53:07 Bev Nicolson wrote:
I've taken charge of my first scanner (a freebie from a friend) but I'm having trouble getting it installed. If I go to XSane it says "failed to open device snapscan :libusb:001:002 " . I have since installed every XSane extra there was via synaptic but it's still won't play ball. I'm very reluctant to give in though so how do I investigate what's up? And even more to the point, how do I fix it? It knows it's there I'm sure.
[Ubuntu 8.04]
Bev.
Download vuescan, see if it will work with that, if so now try it with xsane and see if it works. If not, buy vuescan. If it works with xsane after you've used vuescan, I don't know why this happens, but it does, so just keep your demo copy around in case of need.
Peter
I shall try this, Peter. Permissions is not an issue as I'm the only person using this computer (though I did check Users and Groups to be sure.) Steve is correct in identifying it as an AGFA Snapscan 1212u.
Bev.
Download vuescan, see if it will work with that, if so now try it with xsane and see if it works. If not, buy vuescan. If it works with xsane after you've used vuescan, I don't know why this happens, but it does, so just keep your demo copy around in case of need.
Peter
On Fri, Oct 01, 2010 at 10:01:08AM +0100, Bev Nicolson wrote:
I shall try this, Peter. Permissions is not an issue as I'm the only person using this computer (though I did check Users and Groups to be sure.) Steve is correct in identifying it as an AGFA Snapscan 1212u.
Do what Brett suggested, it could be (and is likely to be) a permissions issue. Just because you are the only user on the system doesn't mean you have permission to do everything. I'd suggest reading a guide on Linux and permissions along with how they work.
Adam
For the sake of understanding, I did say I had checked. The box in Users and Groups is ticked for scanners so I know it allows me to.
Bev.
Do what Brett suggested, it could be (and is likely to be) a permissions issue. Just because you are the only user on the system doesn't mean you have permission to do everything. I'd suggest reading a guide on Linux and permissions along with how they work.
Adam
Another question. How do I unzip VueScan so that it is installed as a program rather than a folder? (I have the bash command, btw.)
Bev.
On 01 Oct 10:01, Bev Nicolson wrote:
I shall try this, Peter. Permissions is not an issue as I'm the only person using this computer (though I did check Users and Groups to be sure.) Steve is correct in identifying it as an AGFA Snapscan 1212u.
Erm, just because you're the only user on a linux box does *not* mean that permissions are not the problem. I am the only user on my laptop, that doesn't mean that I haven't had to add myself to various groups over time, change udev rules to bring devices up that I own, etc etc.
How about posting us the output of: lsusb ls -laR /dev/bus/usb id
Using non-free software to "fix" something that probably isn't even remotely broken seems like a very very silly way of dealing with the problem IMO.
Bev.
Download vuescan, see if it will work with that, if so now try it with xsane and see if it works. If not, buy vuescan. If it works with xsane after you've used vuescan, I don't know why this happens, but it does, so just keep your demo copy around in case of need.
Peter
main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
In the past I have found the easiest way to resolve permissions with sane is to log in as root and try scanning. Usually that works which confirms it is simply a permissions problem.
Cheers
Ian
Bev Nicolson wrote:
I shall try this, Peter. Permissions is not an issue as I'm the only person using this computer (though I did check Users and Groups to be sure.) Steve is correct in identifying it as an AGFA Snapscan 1212u.
Bev.
Download vuescan, see if it will work with that, if so now try it with xsane and see if it works. If not, buy vuescan. If it works with xsane after you've used vuescan, I don't know why this happens, but it does, so just keep your demo copy around in case of need.
Peter
main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
On 01 Oct 10:58, Ian Thompson-Bell wrote:
In the past I have found the easiest way to resolve permissions with sane is to log in as root and try scanning. Usually that works which confirms it is simply a permissions problem.
sane will also complain that you're root, ask if you're absolutely sure you want to do this, and warn you that if it kills your cat it's your own silly fault...
For a case of just looking at the permissions that the device has in /dev/bus/usb...
E.g. on this laptop I have a (working) finger print scanner, relevant line from lsusb: Bus 002 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor
Permissions on the device: $ ls -la /dev/bus/usb/002/002 crw-rw-r-- 1 root plugdev 189, 129 Oct 1 11:14 /dev/bus/usb/002/002 $
Oh, look, that's read and writable by root and the plugdev group... so, what groups am I in? $ id uid=1000(brettp) gid=1000(brettp) groups=1000(brettp),20(dialout),24(cdrom),25(floppy),29(audio),44(video),46(plugdev),109(fuse),1002(sbox) $
Oh look, I'm in the plugdev group, so I have read/write on the fingerprint scanner! Well, that's handy... (given that I use it to auth to xscreensaver... along with a password fallback).
Permissions are *not* complicated, *are* central to the operation of a linux machine, and should be got to grips with early on.
If I hadn't been in the group then I'd have done: sudo adduser brettp plugdev
Which would have added me in to the group, I'd have then logged out and back in again to make sure that the group membership had taken, and then tried again.
This ain't rocket science. Use root *very* sparingly and always remember that running *anything* as root is a security risk.
Cheers,
On 01/10/10 11:34, Brett Parker wrote:
On 01 Oct 10:58, Ian Thompson-Bell wrote:
In the past I have found the easiest way to resolve permissions with sane is to log in as root and try scanning. Usually that works which confirms it is simply a permissions problem.
sane will also complain that you're root, ask if you're absolutely sure you want to do this, and warn you that if it kills your cat it's your own silly fault...
For a case of just looking at the permissions that the device has in /dev/bus/usb...
E.g. on this laptop I have a (working) finger print scanner, relevant line from lsusb: Bus 002 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor
Permissions on the device: $ ls -la /dev/bus/usb/002/002 crw-rw-r-- 1 root plugdev 189, 129 Oct 1 11:14 /dev/bus/usb/002/002 $
Oh, look, that's read and writable by root and the plugdev group... so, what groups am I in? $ id uid=1000(brettp) gid=1000(brettp) groups=1000(brettp),20(dialout),24(cdrom),25(floppy),29(audio),44(video),46(plugdev),109(fuse),1002(sbox) $
Oh look, I'm in the plugdev group, so I have read/write on the fingerprint scanner! Well, that's handy... (given that I use it to auth to xscreensaver... along with a password fallback).
Permissions are *not* complicated, *are* central to the operation of a linux machine, and should be got to grips with early on.
If I hadn't been in the group then I'd have done: sudo adduser brettp plugdev
Which would have added me in to the group, I'd have then logged out and back in again to make sure that the group membership had taken, and then tried again.
This ain't rocket science. Use root *very* sparingly and always remember that running *anything* as root is a security risk.
I *think* I understand the stuff above but here's a typical problem for me.
I want to move stuff. In this case it's from a 1 gig SD card plugged into a reader. As me i.e. the 'normal' user, I select all the stuff on the card and now want to move it to my NAS drive. That's /mnt/server/...... and 3 directories down, I create a folder. When I come to paste the files, that option is greyed out. so how do I find out groups and stuff for that?
If I type ls- ls for /mnt/server/Epox.... it just returns with 'total 0' which tells me naff all.
If I do a 'id' as you did above, it tells me this :- gid=10001(chris) groups=10001(chris),500(raw1394),501(nas)
So I can see that I'm already in a nas group but why then am I not allowed to paste the files into the newly created folder?
*You* might not think it's rocket science but it sure beats the hell out of me sometimes ;-)
On 02 Oct 17:12, Chris Walker wrote:
I *think* I understand the stuff above but here's a typical problem for me.
I want to move stuff. In this case it's from a 1 gig SD card plugged into a reader. As me i.e. the 'normal' user, I select all the stuff on the card and now want to move it to my NAS drive. That's /mnt/server/...... and 3 directories down, I create a folder. When I come to paste the files, that option is greyed out. so how do I find out groups and stuff for that?
Paste? Ahh - nautilus? Right click on the folder, ask for it's properties, and it'll tell you the permissions...
If I type ls- ls for /mnt/server/Epox.... it just returns with 'total 0' which tells me naff all.
Is that actually where it's mounted? How have you got the NAS setup to mount? Are you using NFS? CIFS? Magic?
If I do a 'id' as you did above, it tells me this :- gid=10001(chris) groups=10001(chris),500(raw1394),501(nas)
That just tells me there's a group called nas, it doesn't tell me what the filesystem permissions on the NAS are, or how it's mounted...
So I can see that I'm already in a nas group but why then am I not allowed to paste the files into the newly created folder?
How did you create the folder?
*You* might not think it's rocket science but it sure beats the hell out of me sometimes ;-)
It really isn't rocket science, but then, I suspect having started very much terminal based, I tend to not have had the luxery of laying behind a pointy clicky gui when starting out, so had to learn things the hard way (which is why after getting my sendmail config right, I didn't touch it for a while until I really really decided that I should be running exim... now I tend to be able to churn out a new mailserver config without having to think too hard... getting used to bash and generally using the console is very much a very useful thing to do, and means later on that you can more easily figure things out...)
On 03/10/10 23:41, Brett Parker wrote:
On 02 Oct 17:12, Chris Walker wrote:
I *think* I understand the stuff above but here's a typical problem for me.
I want to move stuff. In this case it's from a 1 gig SD card plugged into a reader. As me i.e. the 'normal' user, I select all the stuff on the card and now want to move it to my NAS drive. That's /mnt/server/...... and 3 directories down, I create a folder. When I come to paste the files, that option is greyed out. so how do I find out groups and stuff for that?
Paste? Ahh - nautilus? Right click on the folder, ask for it's properties, and it'll tell you the permissions...
Dolphin, not Nautilus. It says 'Owner, Group and Others' can all View & Modify Content with the User and Group shown as 503. But I as user created the folder by doing a right click and creating it. Where does group 503 come into it, if you look down below, I'm not in group 503.
If I type ls- ls for /mnt/server/Epox.... it just returns with 'total 0' which tells me naff all.
Is that actually where it's mounted? How have you got the NAS setup to mount? Are you using NFS? CIFS? Magic?
It's mounted at startup using the fstab file. This is one of the lines in it relating to the NAS drive :- //storage_server/Epox_Share /mnt/Epox_Share cifs credentials=/etc/samba/auth.storage_server.Epox 0 0
The /etc/samba/auth.storage_server.Epox file contains two lines, a user name and the relevant password.
If I do a 'id' as you did above, it tells me this :- gid=10001(chris) groups=10001(chris),500(raw1394),501(nas)
That just tells me there's a group called nas, it doesn't tell me what the filesystem permissions on the NAS are, or how it's mounted...
So I can see that I'm already in a nas group but why then am I not allowed to paste the files into the newly created folder?
How did you create the folder?
Right click in Dolphin as the only user of the system.
*You* might not think it's rocket science but it sure beats the hell out of me sometimes ;-)
It really isn't rocket science, but then, I suspect having started very much terminal based, I tend to not have had the luxery of laying behind a pointy clicky gui when starting out, so had to learn things the hard way (which is why after getting my sendmail config right, I didn't touch it for a while until I really really decided that I should be running exim... now I tend to be able to churn out a new mailserver config without having to think too hard... getting used to bash and generally using the console is very much a very useful thing to do, and means later on that you can more easily figure things out...)
I started using linux with Red Hat 4.2 but it hasn't got any easier ;-)
On 30/09/10 16:53, Bev Nicolson wrote: {stuff}
I've installed a snapscan - I think from memory it's a 1212U.
I recall I had problems with an older version of Ubuntu.
I vaguely recall I had to find a firmware driver .bin file to upload to the scanner, but this page https://wiki.ubuntu.com/HardwareSupportComponentsScannersAgfa says my scanner works "out of the box"
I think that initially I had to use gksu to run xsane, and once I'd got it working like that, I then tweaked the permissions on my users, and either ticked role "Permission to use scanner" and/or added the relevant users to group "Scanner"
These pages may help https://help.ubuntu.com/8.04/printing/C/scanning.html https://help.ubuntu.com/community/ScanningHowTo
Hope that helps. Steve
-
Adam Bower -
Bev Nicolson -
Brett Parker -
Chris Walker -
Ian Thompson-Bell -
Peter Alcibiades -
steve-ALUG＠hst.me.uk -
Ted.Harding＠manchester.ac.uk -
Tim Green