Re: Scanner problems in Suse 10.1
- From: Darrell Stec <darrell_stec@xxxxxxxxxxxxxxxxxx>
- Date: Wed, 23 Aug 2006 12:16:21 -0400
After serious contemplation, on or about Wednesday 23 August 2006 9:29
am Dik Voorthuis perhaps from dikvoorthuis@xxxxxxxxxxxxxxxxx wrote:
Per Inge Oestmoen wrote:
I experience trouble when scanning with Suse Linux 10.1.
The scanners used are the Nikon LS-50 and LS-5000. I use VueScan.
Under 9.0, 9.1 and 9.3 there are no problems whatsoever. However,
when I installed Suse Linux 10.1 on a box here, VueScan installed
just fine as it did before - and I thought everything was OK.
Alas, when I fired up the program with the USB scanner, VueScan said:
"No scanner was found attached to your computer. If you have one,
close this tip window, exit VueScan, turn on the scanner and run
VueScan again. See the VueScan Release Notes for more information."
But the scanner was on. This only happens under Suse 10.1.
When I ran sane-find-scanner, this came up:
found USB scanner (vendor=0x04b0, product=0x4001) at libusb:005:002
The scanner is likewise detected by the hardware management tools in
Yast2, but VueScan does not find the scanner. Restart does not help.
Why did this not happen in Suse 9.3 and earlier, but only in 10.1?
And most pressing: Where is the fault, and what is the remedy?
Per Inge Oestmoen, Norway
Did you try set up the scanner, using Yast?
When I connected my epson scanner to a SUSE 10.1 testbox, Vuescan also
did not find it. Only after I set it up with Yast, Vuescan also
detected it and works just fine.
(IIRC this was the same with 10.0)
Maybe something with access permissions not set up properly.
I had the same problem gong from Suse Professional 9.3 to version 10.0.
It turned out to be a permissions thing on the USB device. Several
weeks ago either Nathan or Vahis posted a cure to set the permissions
permanently. Every once in a while I had to log off and when I logged
on the group was set back to root and not on users.
I think you are right on the mark about the permissions. An easy check
is to use the console 'su' to root (I use 'sux -' for some reason I
forgot) and call up Gimp and try to scan something. If that works it
is a definite permissions problem.
Darrell Stec darstec@xxxxxxxxxx
We Put the Magic in Your Webpages
- Prev by Date: Re: cannot get wuxga resolution with SLES 10
- Next by Date: Re: RetHat has no yen for Xen
- Previous by thread: Re: Scanner problems in Suse 10.1
- Next by thread: Re: Scanner problems in Suse 10.1