Comment 48 for bug 83587

Revision history for this message
Patricio (patricio-stwing) wrote : Re: [Bug 83587] Re: HP ScanJet 5300C doesn't work

Using my hp4215 I did:
scanimage -v > hp4215.pnm
scanimage: scanning image of size 638x1125 pixels at 24 bits/pixel
scanimage: acquiring RGB frame
scanimage: min/max graylevel value = 0/255
scanimage: read 2153250 bytes in total
and then I get the image... everything works. Does this mean most of my
configuration files are good?

But if I use hp5300C I get:
scanimage -v -x 10 -y 10 > hp5300C.pnm
scanimage: scanning image of size 56x59 pixels at 24 bits/pixel
scanimage: acquiring RGB frame
scanimage: received signal 2
scanimage: trying to stop scanner
scanimage: min/max graylevel value = 0/255
scanimage: sane_read: Operation was cancelled

I made a shorter the scan to make sure the HW was not getting stuck for
some mechanical problem.
I stopped the scan with ctrl-C

Is there a configuration file that only impacts the hp5300C?

What is supposed to be the size of this file? How do I get the
replacement?
ls Hewlett-Packard\:ScanJet5300C.drc -l
-rwxrwxrwx 1 patricio patricio 0 2008-10-16 14:15
Hewlett-Packard:ScanJet5300C.dr

Patricio

On Fri, 2008-10-17 at 06:28 +0000, miguelquiros wrote:
> Patricio:
> The scanimage reply shows that the device is detected and its permissions are properly set. From here, I do not know what the problem might be. For me, xsane worked fine when reaching this point.
> Perpahs you may try scanning something from the console with
> scanimage -v whatever.png
> And check the error messages that surely will show up to see if they give you any clue. It might be some wrong configuration file somewhere.
> Other possibility is to create a brand new user (with permission for using the scanner, of course) and try to use the scanner from this new user with the security of not having any user stale wrong configuration file hanging around.
> Sorry I cannot help you any more on this.
>
> bhmb:
> In your case, the screenshot only showed the end of the messages. Anyway, it is enough to see that sane-find-scanner does find the scanner but the user bb-laptop has no permission to use it. Firstly, please check that the user bb-laptop does belong to the group scanner:
> cat /etc/group | grep scanner
> The user bb-laptop should appear in the reply. If not, go to the users-admin utility, edit the user bb-laptop, check his privileges and set permission to use the scanner.
> If bb-laptop already belongs to the scanner group, check the properties of the scanner device by typing:
> sane-find-scanner
> and then
> ls -al /dev/bus/usb/001/002 (where you must replace "001" and "002" by the numbers obtained with the previous sane-find-scanner command)
> The device node should belong to the group "scanner"
>