Bug 281914

Please attach output of 'hwinfo --scanner' , dmesg and lshal, run it from terminal and attach also it's output. Try to run it as root and report if works then. 
What version of kernel and udev are you running?

Created attachment 145185 [details]
dmesg

Created attachment 145186 [details]
hwinfo

Created attachment 145187 [details]
lshal

udev: udev-111-2
kernel: linux-7qk2 2.6.21-8-default

doesn't work as root.

What are the results and (error)-messages when you
set it up with the YaST scanner config?

What results "sane-find-scanner -q"

What results "scanimage -L" both as root and as normal user?

(In reply to comment #6 from Johannes Meixner)
> What are the results and (error)-messages when you
> set it up with the YaST scanner config?

After configuring with YaST and starting xsane:

"no devices available"

> What results "sane-find-scanner -q"

found USB scanner (vendor=0x06bd, product=0x2061) at libusb:003:006

> What results "scanimage -L" both as root and as normal user?

As User:
No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).

As root:
No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).

You didn't answer what are results and (error)-messages are
when you set it up with the YaST scanner config.
I have no idea what goes wrong.
I need detailed debug info.

1.
Move /var/log/YaST2/y2log away:
mv /var/log/YaST2/y2log /var/log/YaST2/y2log.save
2.
Re-do the scanner config with YaST.
Before you finish YaST, use "other"->"test" to test if it works.
3.
Save the log file:
cp /var/log/YaST2/y2log /tmp/y2log.scanner
4.
Attach /tmp/y2log.scanner as mime type "text/plain" to this bug.

Created attachment 147991 [details]
y2log.scanner

Attachment #147991 [details] shows that the snapscan driver is correctly
set up and it recognizes the scanner in YaST as
-------------------------------------------------------------------
snapscan", "AGFA SNAPSCAN an snapscan:libusb:003:006"
-------------------------------------------------------------------
YaST also runs "scanimage -L" so that this one works.

Also the test with "scanimage -d snapscan:libusb:003:006 -T"
is successful in YaST:
--------------------------------------------------------------------
[snapscan] Scanner warming up - waiting 15 seconds.
scanimage: scanning image of size 2551x3507 pixels at 24 bits/pixel
scanimage: acquiring RGB frame, 8 bits/sample
scanimage: reading one scanline, 7653 bytes...  PASS
scanimage: reading one byte...          PASS
scanimage: stepped read, 2 bytes...     PASS
scanimage: stepped read, 4 bytes...     PASS
scanimage: stepped read, 8 bytes...     PASS
scanimage: stepped read, 16 bytes...    PASS
scanimage: stepped read, 32 bytes...    PASS
scanimage: stepped read, 64 bytes...    PASS
scanimage: stepped read, 128 bytes...   PASS
scanimage: stepped read, 256 bytes...   PASS
scanimage: stepped read, 512 bytes...   PASS
scanimage: stepped read, 1024 bytes...  PASS
scanimage: stepped read, 2048 bytes...  PASS
scanimage: stepped read, 4096 bytes...  PASS
scanimage: stepped read, 8192 bytes...  PASS
scanimage: stepped read, 8191 bytes...  PASS
scanimage: stepped read, 4095 bytes...  PASS
scanimage: stepped read, 2047 bytes...  PASS
scanimage: stepped read, 1023 bytes...  PASS
scanimage: stepped read, 511 bytes...   PASS
scanimage: stepped read, 255 bytes...   PASS
scanimage: stepped read, 127 bytes...   PASS
scanimage: stepped read, 63 bytes...    PASS
scanimage: stepped read, 31 bytes...    PASS
scanimage: stepped read, 15 bytes...    PASS
scanimage: stepped read, 7 bytes...     PASS
scanimage: stepped read, 3 bytes...     PASS
--------------------------------------------------------------------

Therefore there is no bug at all (at least not in YaST)
and I can only close it as invalid.

(In reply to comment #10 from Johannes Meixner)
 
> Therefore there is no bug at all (at least not in YaST)
> and I can only close it as invalid.

Who said the bug was in YaST?

YaST runs "sane-find-scanner" successfully.
Therefore "sane-find-scanner" works.

YaST runs "scanimage -L" successfully.
Therefore "scanimage -L" works.

YaST runs "scanimage -d snapscan:libusb:003:006 -T" successfully.
Therefore your scanner works.
And when your scanner works, there is no bug.

So you must provide information what exactly does not work.

I cannot run Xsane on your machine.

So you must provide information what exactly you do to
so that I have at least a chance that I can reproduce it.

I now know why it works with YaST: because it works as root.

If I'm root the scanner works like it should but as normal user it is not detected.

In comment #7 you wrote that "scanimage -L" didn't work as root?
Regardless of comment #7:

I assume this bug is a duplicate of bug #250659 which is meanwhile
fixed regarding scanners.
Please test the next openSUSE 10.3 alpha version.

In the meantime there is a workaround:
Use YaST "Other", "scanning via network" and do a "localhost config".

*** This bug has been marked as a duplicate of bug 250659 ***