HP ScanJet 5300C doesn't work

[SteveCoast]

Plugging in a 5300C with USB results in this:

[17179723.368000] usb 3-2: new full speed USB device using uhci_hcd and address 3
[17179733.548000] usb 3-2: configuration #1 chosen from 1 choice
[17179733.552000] usb 3-2: can't set config #1, error -71

And thats it. This should work with the avision driver and there is a (commented out as its not needed) line for it in /etc/sane.d/avision.conf

http://www.sane-project.org/cgi-bin/driver.pl?manu=&model=5300c&bus=any&v=&p=

This machine is an up to date edgy box with sane installed etc. Sane finds the webcam I have (when I plug it in) fine.

[Kevin (kevin-redhat-bugs)]

Description of problem: Preview fails in xsane with a ScanJet 5370C using the
avision sane backend.

On the first attempt, the preview scan is successful. On the second, and all
further, attempts the scan head moves back and forth a small amount (initial
alignment?), then makes the noise (possibly motor strain?) or trying to make the
preview scan - but the scan head doesn't move.

All further attempts fail until _all_ the following have been performed:
1) unplug the scanner from mains and USB
2) modprobe out, then modprobe in ehci_usb (I can't try uhci_usb due to bug 200122)
3) plug the scanner back in
4) run a preview scan in VueScan

Now, 4) seems odd - but if I don't do this then xsane hangs on startup with
device I/O errors. This behavior bears a striking similarity to the problems I
had in bug 205092 comment 1; indeed after the first failed preview scan, if I
unplug the scanners USB cable then plug it back in (without bus or scanner
reset) I get the error:

Sep 12 00:13:10 localhost kernel: usb 1-1.3: new full speed USB device using
ehci_hcd and address 8
Sep 12 00:13:13 localhost kernel: usb 1-1.3: device descriptor read/64, error -110

This is also the "another (different again) USB" error of bug 205092 comment 1;
this bug is now solved, but the behavior seems similar. I don't know what's
going on in the avision backend, but it seems almost as though it puts the
scanner into some kind of undefined state.

Version-Release number of selected component (if applicable):
sane-backends-1.0.18-2.fc5

How reproducible: Once triggered, always.

[Kevin (kevin-redhat-bugs)]

Created attachment 136043
xsane output with successful preview scan

[Kevin (kevin-redhat-bugs)]

Created attachment 136044
xsane debug with a preview scan that fails

[jcfp (jcfp)]

Changing package to kernel, since this problem is in basic usb connectivity which has little to do with sane-backends. See http://lkml.org/lkml/2006/9/16/66 and http://bugzilla.kernel.org/show_bug.cgi?id=6078

[Thomas Hotz (thotz-deactivatedaccount)]

This also happens on a HP ScanJet 5370C.

[17183061.948000] usb 4-2: new full speed USB device using uhci_hcd and address 2
[17183072.136000] usb 4-2: configuration #1 chosen from 1 choice
[17183072.140000] usb 4-2: can't set config #1, error -71

[SteveCoast (steve-asklater)]

I'm happy to debug this using usbmon etc with a few pointers. I seem to need a dbg kernel for a start?

http://www.mjmwired.net/kernel/Documentation/usb/usbmon.txt

[SteveCoast (steve-asklater)]

This still exists in Feisty :-(

[Nils (nils-redhat-bugs)]

Sorry for taking so long to respond. The needed rmmod/insmod thing and the
device I/O error hint at a kernel problem though.

Changing component to kernel.

[Kevin (kevin-redhat-bugs)]

Created attachment 156852
Mail to sane-avision list

[Kevin (kevin-redhat-bugs)]

I'm not convinced this is a kernel problem.

N.B. I only get the I/O errors _after_ the problem has been triggered in SANE.
i.e. I suspect I only need to use rmmod/insmod to reset the USB bus, kicking the
scanner out of the invalid state it seems to have been placed into (by SANE?
Could SANE do this?).

I posted some progress earlier in the year to the sane-avision mailing list, but
haven't had a chance to do anything further recently. This email is attached.

This is a regression, as this scanner is known to have worked in earlier versions.

[Nils (nils-redhat-bugs)]

Changing back the component to sane-backends.

Kevin, unfortunately the amount of scanner hardware I have is rather limited but
theoretically the sane backend could "confuse" your scanner enough that
power-cycling it is needed. If I understand your mail to the list correctly,
there have been some improvements in the SVN version of the time of your mail
(Jan 2007), but some regressions as well. Are there any changes -- good or bad
-- with the current SVN version?

[Kevin (kevin-redhat-bugs)]

I have re-tested with sane-backends-1.0.18-5.fc6, and also a rebuild of the
package with the latest CVS versions of avision.c and avision.h applied.

The "stuck head" problem (the scanhead doesn't move on any preview scan after
the first) happens with both; once in this state, it can only be cleared by the
process described in comment 0.

Interestingly, the if the following sequence if followed:
1) start scanner
2) perform colour preview scan
3) perform colour full scan
4) perform gray preview scan
5) perform gray full scan

the head _doesn't_ become stuck.

Unfortunately, the scanner is remotely located, so I need assistance at the
remote end to perform any tests which end up in the stuck-head state. This means
I don't really have the time or ability to exhaustively test all combinations of
scanning order.

Further:
patching sane-backends-1.0.18-5.fc6 to set dpi_range.min to 100 rather than 80
gives good scans (without this the gray fullscan is unusably dark).

Unfortunately, the CVS versions don't scan well - all colour scans are heavily
tinted in blue, and the gray full scan is unusably dark (even with
dpi_range.min=100).

I will attach 3 further debug outputs.

I also include a summary of some tests I made back in January, trying to
pinpoint which CVS revision broke this scanner.

Hardware for all is:
[avision] attach: Inquiry gives mfg=HP, model=ScanJet 5370C, product revision=3.00.
[avision] attach: Found model: 51

[Kevin (kevin-redhat-bugs)]

Created attachment 156996
sane-backends-1.0.18-5 patched with latest CVS - colour preview scan working

debug-sane-backends-1.0.18-5.krp1-colour-preview

[Kevin (kevin-redhat-bugs)]

Created attachment 156997
sane-backends-1.0.18-5 patched with latest CVS - colour preview FAILS - stuck scan head

debug-sane-backends-1.0.18-5.krp1-colour-preview-STUCKHEAD

[Kevin (kevin-redhat-bugs)]

Created attachment 156998
sane-backends-1.0.18-5 with dpi_range.min=100 (otherwise unpatched) - colour preview scan FAILS - stuck scan head

debug-sane-backends-1.0.18-5.fc6_range100-colour-preview-STUCKHEAD

unfortunately I don't consider the corresponding
debug-sane-backends-1.0.18-5.fc6_range100-colour-preview to be reliable - I
screwed up when collecting that particular log :(

[Kevin (kevin-redhat-bugs)]

Created attachment 157002
Analysing changes in avision CVS revisions

From these, and further test, I'd guess the "stuck-head" problem was introduced
between r209 and r210.

The avision developer prefers to work through the sane-avision mailing list;
unfortunately there isn't currently an archive.

[Kevin (kevin-redhat-bugs)]

Nils, would it help if you had the hardware?

[Nils (nils-redhat-bugs)]

Kevin, because I don't possess the hardware I'm not familiar with the backend
code and I'd need quite some time to become that. Unfortunately, the time I can
spend on sane-backends is rather limited, so I guess your problem will be solved
faster if you work with upstream (as there should be developers who own the
hardware and know the code). I'd be glad if you let me know when there are
improvements that I can massage back into the package (sane-backends is not that
frequent with releases).

I'll close this as UPSTREAM, meaning I can't help you right now. Please reopen
this BZ when there are changes upstream that may help with your problem so I can
possibly update the package with a fix.

[Kevin (kevin-redhat-bugs)]

Progress upstream is, unfortunately, very slow and I don't think I've really got
anywhere in 6 months. I've collected a lot of debug information and I think I've
narrowed down the point at which the regression occured, but I'm also unfamiliar
 with the backend code, so unable to guess the consequenses of reverting any code.

I fear that changes made for newer hardware have caused this regression breaking
the driver for older hardware - I guess this once working hardware will now just
have to be chalked up as incompatible on Fedora/Redhat (and probably most other
distributions).

[Nils (nils-redhat-bugs)]

Kevin, I've put sane-backends-1.0.18-12 into updates-testing which contains a
lot of fixes pertaining to USB scanners. You might want to try it out even
though I know there aren't any special changes for the avision backend. Check
your kernel version though if you use F7 -- see bug #243953.

[Kevin (kevin-redhat-bugs)]

Using sane-backends-1.0.18-12 and the latest F7 kernel:

- any user except root cannot access the scanner. It looks like the bug you
references, but I didn't have time to investigate further, and it's irrelevant
since...

- I still have the preview scan / stuck head failures

[Nils (nils-redhat-bugs)]

Is that the -33 or -41 kernel?

[Kevin (kevin-redhat-bugs)]

kernel-2.6.22.1-33.fc7 - I'll track the device access / udev issues via bug
243953, where it looks like they're fixed.

(I recently tested some upstream changes re: the stuck head problem, but to no
avail).

[panzi (grosser-meister-morti)]

Since the last kernel update a few days ago it stopped to work for me!! How do I downgrade? These regressions are unbearable.
My system is:
$ cat /proc/version
Linux version 2.6.20-16-generic (root@terranova) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #2 SMP Sun Sep 23 19:50:39 UTC 2007

[Leann Ogasawara (leannogasawara)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Now that the 7.10 Gutsy Gibbon release of Ubuntu is out, we were wondering if you can still reproduce this issue. Could you please download and try the new version of Ubuntu from http://www.ubuntu.com/getubuntu/download and report back your results. If the issue is still present in the new release, please attach the following information:

* uname -a > uname-a.log
* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

Please be sure to attach each file as a separate attachment. For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

[Thomas Novin (thomasn80)]

Hello

I have the same problem with ScanJet 6300C. I'm using Gutsy Gibbon with kernel 2.6.22-14.

Nov 1 18:56:54 localhost kernel: [ 105.520000] usb 1-8.2: new full speed USB device using ehci_hcd and address 7
Nov 1 18:56:59 localhost kernel: [ 110.616000] usb 1-8.2: configuration #1 chosen from 1 choice
Nov 1 18:56:59 localhost kernel: [ 110.616000] usb 1-8.2: can't set config #1, error -32

I'm attaching all requested output.

Importance must be raised since this seems to affect not only that specific model but many scanners. I've googled the issue and it seems to be a big problem.

[martine (martine-rolle)]

I ve got the exact same problem as ThomasNovin.
(Since i have the same uname -a and the same version-signature, i dont post them)

[Leann Ogasawara (leannogasawara)]

I'm retargeting this bug towards the upcoming Hardy kernel. I've tagged this as "hardy-kernel-candidate" so that we make sure to retarget this report once the new release is out. However against the linux-source-2.6.22 package this is being marked as "Won't Fix" as it does not meet the criteria for a stable release update. To learn more about the stable release update process please refer to https://wiki.ubuntu.com/StableReleaseUpdates . Thanks!

[Thomas Novin (thomasn80)]

It can probably be fixed by using the Hardy kernel in Gutsy once it's arrives.

A Google search seems helpful (here on how to use Gutsy kernel in Feisty)

http://www.google.com/search?hl=en&q=gutsy+kernel+feisty

[Leann Ogasawara (leannogasawara)]

The Hardy Heron Alpha2 release will be coming out soon (around Dec 20). It will have an updated version of the kernel (Hardy Alpha1 still had the previous Gutsy kernel). It would be great if you could test with this new release if this issue still exists. I'll be sure to update this report when Alpha2 is available. Thanks!

[Thomas Novin (thomasn80)]

Works now :)

[Leann Ogasawara (leannogasawara)]

Hi Thomas,

Thanks for the update. I'm glad to hear things are working again so I'll be closing this bug report. Feel free to report any future bugs you may find, it's much appreciated. Thanks!

[Kevin (kevin-redhat-bugs)]

This wasn't resolved upstream, unfortunately. I eventually received some help
from the developer, but he has a different revision of the hardware which
doesn't exhibit this problem. I provided copious amounts of debug, and narrowed
the problem down to a few sections of code, but this didn't really get me
anywhere. It's older hardware, and there can't be many users - so I can see why
there's little interest in fixing it... it not really worth expending any more
time on. Annoyingly there's no archive of the sane-avision list.

So, as of Fedora 8 there are definitely some revisions of this scanner (with C5
ASICs) that don't work. The particular 5370C in question was retired after a
year of trying.

[polo (guzowskip)]

Greetings from a new member....

When my previous scanner died, I specifically bought a used HP Scanjet 5300C because the SANE website said it worked completely. When I try to use it with Linux I have the same problem noted previously in this thread. Scanner works fine in Windows so no hardware problem. Under Gutsy with 2.6.22 kernel, Gutsy with 2.6.24-generic kernel, and after upgrading to Hardy (beta) with 2.6.24-generic kernel, I get the same results. Scanner will preview fine but when I go final (with or without a preview), it hangs somewhere around 15-20% complete. When I peek under the lid, the lamp is stopped just where the end of the original document is. I've tried using Kooka so I could control the scan background recognition and I've tried turning off calibration and quality in XSane and nothing so far has worked. Thanks in advance for any assistance.

[Patricio (patricio-stwing)]

I love ubuntu, I think you guys are amazing. I also see this problem with 5300C. Here are my notes. Can I provide any more information ? I am new at this.

patricio@patricio-desktop:~$ uname -s -r
Linux 2.6.24-16-generic
patricio@patricio-desktop:~$ lsusb
Bus 002 Device 003: ID 0d49:7110 Maxtor
Bus 002 Device 002: ID 03f0:3d11 Hewlett-Packard OfficeJet 4215
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 015: ID 03f0:0701 Hewlett-Packard ScanJet 5300c/5370c
Bus 001 Device 001: ID 0000:0000
patricio@patricio-desktop:~$ kooka
kbuildsycoca running...
libkscan: WARNING: Trying to copy a not healthy option (no name nor desc)
libkscan: WARNING: Trying to copy a not healthy option (no name nor desc)
KCrash: Application 'kooka' crashing...
Could not find 'drkonqi' executable.
KCrash cannot reach kdeinit, launching directly.
patricio@patricio-desktop:~$ kooka
kbuildsycoca running...
libkscan: WARNING: Trying to copy a not healthy option (no name nor desc)
libkscan: WARNING: Trying to copy a not healthy option (no name nor desc)
Terminated

As you see I tried a couple of times. The first I change a couple of resolution settings. The second I just press scan.
Thanks!
Patriico

[Patricio (patricio-stwing)]

I also tried xsane and I get:

Error while loading device settings:
/home/patricio/.sane/xsane/Hewlett-Packard:ScanJet5300C.drc is not a device-rc-file !!!

Thanks!
Patricio

[Patricio (patricio-stwing)]

I think this is still a problem. It doesn't work in Hardy.
Thanks!
Patricio

[Patricio (patricio-stwing)]

I don't know if I am allow to confirm bugs, but this seems to be pretty clear. I have seen several people reporting problems with 5300C.

[Patricio (patricio-stwing)]

It seems that Vuescan knows how to solve this.
It also seems that somebody knows how to compile this in Linux, but I am too new to try this. Can somebody post detailed instructions for Ubuntu?
http://members.chello.nl/~j.schoone/scanning.html

[Leann Ogasawara (leannogasawara)]

Hi Patricio,

After you attempt to scan an image and run into errors, can you capture and attach your dmesg output? Could you also attach /var/log/syslog ? Thanks.

[miguelquiros (mquiros)]

My scanner HP 5300C worked perfectly until I upgraded to Ubuntu 8.04 TLS. After upgrading, when connecting the scanner, the /dev/bus/usb device is created but is not longer assigned to the group "scanner" but to the group "root", so if I start xsane (as normal user) the device is not detected. If I manually change the device group to "scanner" and then start xsane, the scanner is detected, the program starts but it either segfaults or hangs when I try either the preview or a direct scan.
I have solved the problem simply by downgrading libsane back to the 1.0.18-3ubuntu1 version. After restarting dbus and plugging the scanner off and on again, the device is created properly with "scanner" group and xsane works fine. So it is clear there has been a regression here for libsane.
The only problem now is that update-manager keeps continously annoying me trying to convince me to upgrade again!

[Patricio (patricio-stwing)]

Miguel, I am kind of new. Can you post instructions to downgrade libsane? I usually use synaptic, Package->Force Version is not available.
Thanks,
Patricio

[miguelquiros (mquiros)]

To downgrade, first you need to download the deb file, in this case from:
http://archive.ubuntu.com/ubuntu/pool/main/s/sane-backends/
Download at any directory the file libsane_1.0.18-3ubuntu1_i386.deb
Then, in a terminal, move to the directory where the file has been downloaded and execute:
sudo dpkg -i --force-downgrade libsane_1.0.18-3ubuntu1_i386.deb
Good luck.

[Patricio (patricio-stwing)]

I had tried to remove the libsane and then installed, but it broke a bunch of dependences: xane, sane-utils
Then I installed them back with no luck.
Then I tried your command, well no luck. Sorry I think I broke your solution by running the wrong commands before you posted.
After running your command I did:
lsusb
Bus 001 Device 009: ID 03f0:0701 Hewlett-Packard ScanJet 5300c/5370c
scanimage -L
nothing
then
sudo chgrp scanner /dev/bus/usb/001/009 since it was not in the scanner group
and
scanimage -L
device `avision:libusb:001:009' is a Hewlett-Packard ScanJet 5300C flatbed scanner
but when I run xsane I get the usual error: Hewlett-Pacard:ScanJet5300C.drc is not a device-rc file !!!
Thanks!
Patricio

[miguelquiros (mquiros)]

Sorry. I think that my problem is not the same as yours. I have never seen the "....drc" error. Perhaps you have some sort of wrong configuration file somewhere. If you may delete any configuration file in your home directory related with xsane ... (but I do not where such configuration files might be, perhaps in the directory ~/.sane).

[Patricio (patricio-stwing)]

Any chance this will be fixed?
Thanks,
Patricio

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[polo (guzowskip)]

 Can't speak for 2.6.26 but I tried 2.6.27 kernel and no luck. Sane-find-scanner lists both my 5300C scanner and my Pinnacle HDTV usb stick but when I run Xsane or Kooka, neither finds the scanner. I'm back to 2.6.24 kernel for now due to other problems but am hopeful this issue will be resolved soon because I really hate not being able to use the scanner I bought specifically because it is "fully supported" by SANE.

[Alan Lord (theopensourcerer)]

I can confirm this. I have an up-to-date Intrepid release as of this morning and my Scanjet 5300C does not get recognised when running XSane.

# uname -a
Linux lobsang 2.6.27-3-generic #1 SMP Wed Sep 10 16:02:00 UTC 2008 i686 GNU/Linux

However sane-find-scanner reports the following:

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

found USB scanner (vendor=0x03f0 [Hewlett Packard], product=0x0701 [Hewlett Packard ScanJet 5300C/5370C ]) at libusb:005:005
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.

  # You may want to run this program as root to find all devices. Once you
  # found the scanner devices, be sure to adjust access permissions as
  # necessary.

[Michael McAllister (m-d-mcallister)]

I have been using Kubuntu for over a year now with no issues. Started in 7.10(?) and then did the upgrade to 8.04. I had used my ScanJet 5370C without issue prior to the upgrade to 8.04. Tried tonight and it did not work, Looked into Ubuntu forums, found the info from miguelquiros about downgrading the libsane deb package, applied it now my scanner works.

Just want to say thanks to everyone. Will this be corrected in the next upgrade? I will download the next test releases, but can only try it from the Live CDs. I will post back my results.

[Bruce Crowther (bwucie)]

Since 7.04 I have had to fight Ubuntu to get my scanner (Brother DCP130C) to work. Usually I have to resort to using sudo xsane to get it to launch, then chmod 666 the images after scanning.
I got it going in 8.10 Alpha 6 by going to users and groups and putting a tick in EVERY heading's properties where our name was, and changing the authorisations for directly access scanner, then after updating to the Beta I need to use sudo again.
Likewise I have an issue with syncing my palm, and I think the whole permissions setup for USB devices in UDEV is a nightmare: once things used to work (Gutsy), now (Hardy/Intrepid) they are broken, to all intents and purposes.
Regression indeed - Ubuntu was starting to look like the flavour of Linux that anyone could use, now it has become a geek plaything, and I am not a geek.
Regards,
Bruce

[bhmb (bourlierbernard)]

Hi Miguel, I am new to Ubuntu (8.04 version) and after spending 2 days configurating my wifi card I am glad to find this forum about my 5300C. I did the downgrade as you suggested it but now when I try to launch Applications, Graphisme, Scanneur it shows "no peripherical available" (before it would identify the 5300C but crash after trying a scan).
Should I launch the scan from somewhere else and with what commands ?
I join the screen I got after downgrading and it seemed correct to me ?

[miguelquiros (mquiros)]

Hello. Perhaps the scanner is recognised but the permissions for
accessing it are wrongly set (because of mixing packages of different
Ubuntu versions). Install the package sane-utils (if not already
installed) and try the following commands (with the scanner connected of
course) in a terminal and see what are the replies:

sudo sane-find-scanner

sudo scanimage -L

sane-find-scanner

scanimage -L

It there is a different reply "with sudo" and "without sudo", the
problem is wrongly set device permissions and I will suggest you what to
do in this case.

>From your screenshot, it seems that the downgraded package has been
correctly installed (at the second try, in the first it seems that the
deb file was not found...)

El jue, 16-10-2008 a las 09:30 +0000, bhmb escribió:
> Hi Miguel, I am new to Ubuntu (8.04 version) and after spending 2 days configurating my wifi card I am glad to find this forum about my 5300C. I did the downgrade as you suggested it but now when I try to launch Applications, Graphisme, Scanneur it shows "no peripherical available" (before it would identify the 5300C but crash after trying a scan).
> Should I launch the scan from somewhere else and with what commands ?
> I join the screen I got after downgrading and it seemed correct to me ?
>
>
> ** Attachment added: "downgrading display"
> http://launchpadlibrarian.net/18604062/downgrade.png
>
--
Miguel Quirós Olozábal
Departamento de Química Inorgánica. Facultad de Ciencias.
Universidad de Granada. 18071 Granada. SPAIN.
email: mquiros<at>ugr<dot>es
       mquiros<arroba>ugr<punto>es

[Patricio (patricio-stwing)]

I am in the same situation that bhmb
sudo sane-find-scanner
found USB scanner (vendor=0x03f0 [Hewlett Packard], product=0x0701 [Hewlett Packard ScanJet 5300C/5370C ]) at libusb:002:002

sudo scanimage -L
device `avision:libusb:002:002' is a Hewlett-Packard ScanJet 5300C flatbed scanner

sane-find-scanner
found USB scanner (vendor=0x03f0, product=0x0701) at libusb:002:002

scanimage -L
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).

[miguelquiros (mquiros)]

The scanimage -L command works as root but not as normal user. Assuming that the normal user does belong to the scanner group (it may be checked by: cat /etc/group | grep scanner), it seems that the device node has not been created belonging to the "scanner" group.
In one case, I have found that the problem lies in the file /etc/udev/rules.d/45-libsane.rules, which should be the responsible por properly setting the scanner device. I think that this file, included in the libsane downgraded package, uses an outdated way of detecting the devices. Near of the begining of the file there is a line that says as follows:
SUBSYSTEM!="usb_device", GOTO="libsane_rules_end"
This line is designed for older udev versions than that present in Ubuntu Hardy. In hardy, it makes that the file is fully skipped and then the scanner device is not properly set.
For me, it has worked simply to comment out this line by inserting a # symbol at the beginning of the line and the file is then processed and the device group is then properly set. (After modifying the file, you should restart the computer or perhaphs it just suffices with unplugging and plugging back the scanner).

Good luck.

[bhmb (bourlierbernard)]

Back from windows (still on dual boot as long as Ubuntu not fully working) thank you Miguel for these quick replies. I am not so lucky as Patricio (see joined screenshot) as there is no difference between sudo and not sudo as it seems ? Bernard

[miguelquiros (mquiros)]

bhmb:
It seems that you have not the package sane-utils installed. Please go to synaptic and install this package before using the commands sane-find-scanner and scanimage.

[bhmb (bourlierbernard)]

Hello Miguel. Thank you for your reply. I tried to correct everything :
1/ I used synaptic and intalled sane-utils
2/ Using the sudo gedit command I modified the 45-libsane.rules file
and checked that modification had been saved (see joined screenshot)
3/ I restarted the system and then used the sane-find-scanner and scanimage command (screenshot joined).
It seems that I am now in the same position as Fabricio was
I also notice that if the scanner has been identified by the terminal command, it is no longer identified through the graphical menu Applications, graphisme, scanneur Xsane.

[Patricio (patricio-stwing)]

Now I get:
scanimage -L
device `avision:libusb:002:003' is a Hewlett-Packard ScanJet 5300C
flatbed scanner

when I scan the lamp moves to the end of the scan area and then it
stops. After a while starts flashing. Xsane is says "error during read:
Error during device I/O".

On Thu, 2008-10-16 at 13:14 +0000, miguelquiros wrote:
> The scanimage -L command works as root but not as normal user. Assuming that the normal user does belong to the scanner group (it may be checked by: cat /etc/group | grep scanner), it seems that the device node has not been created belonging to the "scanner" group.
> In one case, I have found that the problem lies in the file /etc/udev/rules.d/45-libsane.rules, which should be the responsible por properly setting the scanner device. I think that this file, included in the libsane downgraded package, uses an outdated way of detecting the devices. Near of the begining of the file there is a line that says as follows:
> SUBSYSTEM!="usb_device", GOTO="libsane_rules_end"
> This line is designed for older udev versions than that present in Ubuntu Hardy. In hardy, it makes that the file is fully skipped and then the scanner device is not properly set.
> For me, it has worked simply to comment out this line by inserting a # symbol at the beginning of the line and the file is then processed and the device group is then properly set. (After modifying the file, you should restart the computer or perhaphs it just suffices with unplugging and plugging back the scanner).
>
> Good luck.
>

[miguelquiros (mquiros)]

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"

[Patricio (patricio-stwing)]

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"
>

[bhmb (bourlierbernard)]

Thank you Miguel,

1/ You were right concerning the authorisation for scanner, I authorised it (see joined text)
2/ I then used the same commands (see joined text) as yesterday and it seems to work well until the last one "scanimage -L" where no scanner is identified (see joined text). It seems this time I am where Fabricio was yesterday.
3/ I then used the command you suggested in your answer to Fabricio with no satifactory result (see joined text)
4/ I may misunderstand what Fabricio did, but doing the same I keep with "no device found".
   - Did-it improve anything to use the other scanner before ?
   - Is there any scanner pilot compatible with 5300C which could be forced to be used ?

[Patricio (patricio-stwing)]

bhmb,
Just to clarify what I did:
1) Downgraded libsane back to the 1.0.18-3ubuntu1 version
2) Commented SUBSYSTEM!="usb_device", GOTO="libsane_rules_end" as Miguel
suggested (this did improve the situation as the scanner was now
recognized by scanimage -L).

But now... very curious, I found out that I had downloaded (a long time
ago) "kooka" a scanning program from KDE. And guess what.... it works.
Which is curious to me because it says it uses "sane", probably in a
different way that scanimage uses "sane".
Patricio

On Fri, 2008-10-17 at 15:02 +0000, bhmb wrote:
> Thank you Miguel,
>
> 1/ You were right concerning the authorisation for scanner, I authorised it (see joined text)
> 2/ I then used the same commands (see joined text) as yesterday and it seems to work well until the last one "scanimage -L" where no scanner is identified (see joined text). It seems this time I am where Fabricio was yesterday.
> 3/ I then used the command you suggested in your answer to Fabricio with no satifactory result (see joined text)
> 4/ I may misunderstand what Fabricio did, but doing the same I keep with "no device found".
> - Did-it improve anything to use the other scanner before ?
> - Is there any scanner pilot compatible with 5300C which could be forced to be used ?
>
>
> ** Attachment added: "Miguel 1"
> http://launchpadlibrarian.net/18641031/Miguel%201
>

[bhmb (bourlierbernard)]

Thank you Patricio

What is funny is that I also did step 1 and 2. I had also needed to be declared as a sane user due to the downgrading ?
I think I am now where you were before setp 2 as the "scanimage -L" in my Terminal says no scanner available.
I shall try to load kooka and see if there is an improvement

[bhmb (bourlierbernard)]

Hi Miguel and Patricio and thank you both of you

Patricio : it seems kooka should not be necessary as you will see : I thought I had restarted the system but may be I did not and going back from Windows where I still work upon receipt of your mail to Ubuntu I just made a test from Applications, graphisme, and choosing scanner : my 5300C HP was identified again. I then made a testscan and it crashed. After unpluging the scanner and powering it off and on and repluging I rememberd Miguel observation not to use 150 dpi but 300 dpi and there it just worked beautifully. So for me 3 steps were necessary as explained above by Miguel :

1/ downgrade to the earlier "sane" version. Download from http://archive.ubuntu.com/ubuntu/pool/main/s/sane-backends/ the file libsane_1.0.18-3ubuntu1_i386.deb Then copy the file in the current directory of the open Terminal and execute:
sudo dpkg -i --force-downgrade libsane_1.0.18-3ubuntu1_i386.deb

2/ use the system, admnistration, user and group menu to tick the user name as authorised to scanner in "propiétés" of the user

3/ execute the file : sudo gedit /etc/udev/rules.d/45-libsane.rules and cancel by commenting (using "#") the line SUBSYSTEM!="usb_device", GOTO="libsane_rules_end"

and restart and after calling the scanner from Application, graphisme, scanner, once 5300C HP identified, change the 150 dpi resolution to 300 dpi

3 days for the scanner now I am going to work on my connextant modem !

[Patricio (patricio-stwing)]

That is great! Works for me too. I found this
http://ubuntuforums.org/showthread.php?t=354551
Thanks for your help.
Patricio

On Fri, 2008-10-17 at 18:33 +0000, bhmb wrote:
> Hi Miguel and Patricio and thank you both of you
>
> Patricio : it seems kooka should not be necessary as you will see : I
> thought I had restarted the system but may be I did not and going back
> from Windows where I still work upon receipt of your mail to Ubuntu I
> just made a test from Applications, graphisme, and choosing scanner : my
> 5300C HP was identified again. I then made a testscan and it crashed.
> After unpluging the scanner and powering it off and on and repluging I
> rememberd Miguel observation not to use 150 dpi but 300 dpi and there it
> just worked beautifully. So for me 3 steps were necessary as explained
> above by Miguel :
>
> 1/ downgrade to the earlier "sane" version. Download from http://archive.ubuntu.com/ubuntu/pool/main/s/sane-backends/ the file libsane_1.0.18-3ubuntu1_i386.deb Then copy the file in the current directory of the open Terminal and execute:
> sudo dpkg -i --force-downgrade libsane_1.0.18-3ubuntu1_i386.deb
>
> 2/ use the system, admnistration, user and group menu to tick the user
> name as authorised to scanner in "propiétés" of the user
>
> 3/ execute the file : sudo gedit /etc/udev/rules.d/45-libsane.rules and
> cancel by commenting (using "#") the line SUBSYSTEM!="usb_device",
> GOTO="libsane_rules_end"
>
> and restart and after calling the scanner from Application, graphisme,
> scanner, once 5300C HP identified, change the 150 dpi resolution to 300
> dpi
>
> 3 days for the scanner now I am going to work on my connextant modem !
>

[miguelquiros (mquiros)]

Hello. I am glad that you get the scanner to work. Regarding resolution, I use 200 dpi in a standard basis and switch to 300 when I want better resolution. I am not sure if I have ever tried 150, perhaps not.
Greetings,
Miguel

[polo (guzowskip)]

Miguel, Patricio, and bhmb....

I want to thank you all in public for your persistence in pursuing a solution to this vexing problem. Following through on your suggestions I finally got my HP 5300c working again in Ubuntu. I used to use Kooka under KDE under a different Linux distribution and am sad to see it is no longer supported nor included in KDE. That said, XSane will do what I need to do so am grateful.

On a final note, after I downgraded libsane to get the scanner working, I kept getting a notice that an update of that package was available. Since I don't want to upgrade that package for the time being, I would like to know how to turn off the notification. I found ways to put the package on hold here: http://ubuntuforums.org/showthread.php?t=137100 but I am still getting the notification. Does anyone know how to tell the updater to ignore this package?

Thanks again in advance,

Paul in Florida, USA

[Psykotik (linux-ikiru)]

Since I upgraded to last libsane (1.0.19-1ubuntu3), using xsane restarts gdm. Reverted back to libsane_1.0.19~cvs20070505-3ubuntu2 and everything works again.

Looks like last libsane doesn't handle correctly HP 5300c

[bhmb (bourlierbernard)]

Hello,

Sorry Polo, I hope I am not going to moderate your joy too much by making following comment

As I said before, my next step would be to install 56 K modem (for fax). As one is never too rich I have got a true external 56K and a winmodem connextant (2 modems). I started with the easier the Olitec V92 and went through installation thanks to a very good forum (but in French). I could send a fax using a ps file but then I remembered that I used to fax through my 5300C HP and I went back to Xsane and tried to do the same. My scanner freezes. I checked after plugging off and on that it was working for scan (yes) copy (yes)and email (yes) but I do not succeed with the fax menu.

I use Efax and I set parameters in the configuration fax menu on "efax" cliking on its icon, I use evince as ps viewer which I mentionned in the relevant configuration box.

I went to a forum concerning Efax but could not find anything concerning this point and I wonder wether it is not another HP5300C/Xsane issue ? Anyway has anyone had such a fax problem ? do you have any idea on where does that problem come from ? Miguel would you suggest any other downgrade plus some commenting of antoher mysterious(to me) file of yours ? or did I mis-install something (I have reinstalled efax and efax-gtk twice with no impact) ?

[miguelquiros (mquiros)]

Polo:

For me, the following command:
sudo echo -e "libsane hold" | dpkg --set-selections
has succeeded in putting the libsane package in "hold" status, so update-notifier does not bother me any more asking me to upgrade it.
I just have to be careful when I update other packages via update-manager that libsane, still appearing in the list, is not marked and so, it is not unintendedly upgraded.

You can check whether libsane is or is not in hold status by the comand
dpkg -l libsane
The first letter in the last line of the reply should be an "h" if the package is in fact in hold status (an "i" if it is not).

[polo (guzowskip)]

Thanks, Miguel. I had tried two different 'hold' commands in a terminal and they didn't seem to work. I'm not sure if the one you suggest was one of them. Finally, I checked in synaptic package manager (Ubuntu) and libsane was not marked as locked so I locked it from ther and now things are fine. It sure is nice to finally have my scanner working again. Thanks for your help.

Paul in Northwest Florida, USA

> ----- Original Message -----
> From: miguelquiros <email address hidden>
> To: <email address hidden>
> Subject: [Bug 83587] Re: HP ScanJet 5300C doesn't work
> Date: Tue, 28 Oct 2008 08:16:30 -0000
>
>
> Polo:
>
> For me, the following command:
> sudo echo -e "libsane hold" | dpkg --set-selections
> has succeeded in putting the libsane package in "hold" status, so
> update-notifier does not bother me any more asking me to upgrade it.
> I just have to be careful when I update other packages via
> update-manager that libsane, still appearing in the list, is not
> marked and so, it is not unintendedly upgraded.
>
> You can check whether libsane is or is not in hold status by the comand
> dpkg -l libsane
> The first letter in the last line of the reply should be an "h" if
> the package is in fact in hold status (an "i" if it is not).
>
> --
> HP ScanJet 5300C doesn't work
> https://bugs.launchpad.net/bugs/83587
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” source package in Ubuntu: Confirmed
> Status in “linux-source-2.6.17” source package in Ubuntu: Won't Fix
> Status in “linux-source-2.6.20” source package in Ubuntu: Won't Fix
> Status in “linux-source-2.6.22” source package in Ubuntu: Won't Fix
> Status in “sane-backends” source package in Ubuntu: Confirmed
>
> Bug description:
> Plugging in a 5300C with USB results in this:
>
> [17179723.368000] usb 3-2: new full speed USB device using uhci_hcd
> and address 3
> [17179733.548000] usb 3-2: configuration #1 chosen from 1 choice
> [17179733.552000] usb 3-2: can't set config #1, error -71
>
> And thats it. This should work with the avision driver and there is
> a (commented out as its not needed) line for it in
> /etc/sane.d/avision.conf
>
> http://www.sane-project.org/cgi-bin/driver.pl?manu=&model=5300c&bus=any&v=&p=
>
> This machine is an up to date edgy box with sane installed etc.
> Sane finds the webcam I have (when I plug it in) fine.

>

=
Download Quicken 2009
Save up to 36% on Quicken Deluxe, Premier, Home & Business. Free ship.
http://a8-asy.a8ww.net/a8-ads/adftrclick?redirectid=e37210492866fe949bd4faea402f01f8

--
Powered by Outblaze

[Psykotik (linux-ikiru)]

It still does occur with Ubuntu 8.10 (kernel 2.6.27-9).

[Alan Lord (theopensourcerer)]

Hi,

I'm using an up-to-date Jaunty and have experienced the above problem ever since switching to Linux.

However today I thought I'd try again.

Initially I had the same problems: Xsane identified the scanner but would stall at about 25% and freeze.

I read through many of the older posts here and tried a couple of things.

* I added myself (as a user) to the saned group.
* I installed gnome-scan to try something different (it worked to a fashion but would crash often so I removed it).
* I used the sane-utils package to test for correct scanner detection
* I then rebooted (with the scanner connected and powered) and retried xsane but adjusted the resolution from 150dpi to 300dpi.

Subsequently scanning worked. I scanned multiple pages and saved as both png and pdf.

Work that one out...

[polo (guzowskip)]

 I am running Ubunty Jaunty and my HP Scanjet 5300C works, albeit not
flawlessly as advertised by SANE.�� I bought it used because it was
advertised to operated fully with SANE and it did work OK at first but
somewhere in the upgrades (I believe from Feisty to Gutsy), it started
exhibiting all the behavior described in this thread.� The only way I
could get it working again was to force the downgrade of libsane to
version 1.0.18-3ubuntu1 and lock it so it would not be upgraded.� I still
have an occasional problem (it seems to be related to resolution choices)
but most of the time it works with XSane although the preview window
doesn't always load correctly.� Pretty frustrating for an older piece of
hardware that is supposedly fully supported by the SANE backend and
avision driver.

Paul in NW FL.

  ----- Original Message -----
  From: Tony
  To: <email address hidden>
  Subject: [Bug 83587] Re: HP ScanJet 5300C doesn't work
  Date: Sat, 04 Jul 2009 22:06:28 -0000

  ** Branch linked: lp:~theundecided/openable/0.0.1

  --
  HP ScanJet 5300C doesn't work
  https://bugs.launchpad.net/bugs/83587
  You received this bug notification because you are a direct
  subscriber
  of the bug.

  Status in Linux ACPI client: Invalid
  Status in “linux” package in Ubuntu: Confirmed
  Status in “linux-source-2.6.17” package in Ubuntu: Won't Fix
  Status in “linux-source-2.6.20” package in Ubuntu: Won't Fix
  Status in “linux-source-2.6.22” package in Ubuntu: Won't Fix
  Status in “sane-backends” package in Ubuntu: Confirmed

  Bug description:
  Plugging in a 5300C with USB results in this:

  [17179723.368000] usb 3-2: new full speed USB device using uhci_hcd
  and address 3
  [17179733.548000] usb 3-2: configuration #1 chosen from 1 choice
  [17179733.552000] usb 3-2: can't set config #1, error -71

  And thats it. This should work with the avision driver and there is
  a (commented out as its not needed) line for it in
  /etc/sane.d/avision.conf

  http://www.sane-project.org/cgi-bin/driver.pl?manu=&model=5300c&bus=any&v=&p=

  This machine is an up to date edgy box with sane installed etc.
  Sane finds the webcam I have (when I plug it in) fine.

--
Be Yourself @ mail.com!
Choose From 200+ Email Addresses
Get a Free Account at www.mail.com

[Michal Suchanek (hramrach)]

ScanJet 5300C works for me on Intrepid but scanning on it crashes xsane.

[meral (meral)]

This error still occurs in xsane under karmic koala. It seems like an "ignore"-action until no one owns this device any more...

[Michal Suchanek (hramrach)]

Actually I think this should work in Lucid because back then I solved the issue by using newer sane packages from Debian.

The issue with scan stopping 15-20% through the image is caused by selecting a resolution not supported by the scanner/driver.

You can select resolution in 1dpi step but supported resolutions are typically multiples of 200 or 300 dpi. With correct resolution selected the scanner works.

[miguelquiros (mquiros)]

Yes, it works for me in Lucid. At least at 200 dpi.

[Benji (benjim)]

I can confirm it: I have a Hp ScanJet 5300C.
Downgrading libsane also works out for me.

1.0.21 woks (was not necessary to go back to 1.0.19). 1.0.22 doesn't.

apt-cache policy libsane
libsane:
  Installed: 1.0.21-2ubuntu2
  Candidate: 1.0.22-2ubuntu2
  Version table:
     1.0.22-2ubuntu2 0
        500 http://de.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
 *** 1.0.21-2ubuntu2 0
        100 /var/lib/dpkg/status

[Benji (benjim)]

I'm trying to find out, which commit caused this issu.

http://anonscm.debian.org/gitweb/?p=sane/sane-backends.git;a=shortlog;h=refs/tags/RELEASE_1_0_22

My first guess is a change at the avision backend.