[wellylug] xsane failure scanning on HP Officejet 6500A

[Jeff Hunt]

Hi guys,
my friend using Ubuntu 12.04, xsane and a 3 in 1 Hp Officejet 6500A
which worked out of the box apart from this, gets an 'I/O error
scanner not found' after doing 0 to 8 scans.

The syslog read

**--**--**
Aug 29 11:53:23 pressy xsane: scan/sane/http.c 189: timeout reading
data sec_timeout=5
Aug 29 11:53:35 pressy xsane: io/hpmud/hpmud.c 214: io/hpmud/hpmud.c:
service_to_channel(): sn=HP-LEDM-SCAN
Aug 29 11:56:23 pressy xsane: io/hpmud/hpmud.c 214: io/hpmud/hpmud.c:
service_to_channel(): sn=HP-LEDM-SCAN
Aug 29 11:56:28  xsane: last message repeated 2 times
Aug 29 11:56:28 pressy xsane: scan/sane/http.c 189: timeout reading
data sec_timeout=5
Aug 29 11:56:30 pressy xsane: io/hpmud/hpmud.c 214: io/hpmud/hpmud.c:
service_to_channel(): sn=HP-LEDM-SCAN
Aug 29 11:56:58  xsane: last message repeated 3 times
Aug 29 11:56:58 pressy xsane: scan/sane/http.c 189: timeout reading
data sec_timeout=1
Aug 29 11:56:58 pressy xsane: io/hpmud/hpmud.c 214: io/hpmud/hpmud.c:
service_to_channel(): sn=HP-LEDM-SCAN
Aug 29 12:03:03 pressy xsane: io/hpmud/hpmud.c 214: io/hpmud/hpmud.c:
service_to_channel(): sn=HP-LEDM-SCAN
Aug 29 12:03:04  xsane: last message repeated 2 times
Aug 29 12:03:04 pressy xsane: scan/sane/http.c 189: timeout reading
data sec_timeout=1
Aug 29 12:03:04 pressy xsane: io/hpmud/hpmud.c 214: io/hpmud/hpmud.c:
service_to_channel(): sn=HP-LEDM-SCAN
Aug 29 12:03:56  xsane: last message repeated 3 times
Aug 29 12:03:56 pressy xsane: scan/sane/http.c 189: timeout reading
data sec_timeout=1
Aug 29 12:03:56 pressy xsane: io/hpmud/hpmud.c 214: io/hpmud/hpmud.c:
service_to_channel(): sn=HP-LEDM-SCAN
Aug 29 12:06:15 pressy dbus[712]: [system] Activating service
name='org.debian.apt' (using servicehelper)
Aug 29 12:06:17 pressy AptDaemon: INFO: Initializing daemon
Aug 29 12:06:17 pressy dbus[712]: [system] Successfully activated
service 'org.debian.apt'
Aug 29 12:06:17 pressy AptDaemon.PackageKit: INFO: Initializing
PackageKit compat layer
Aug 29 12:11:18 pressy AptDaemon: INFO: Quitting due to inactivity
Aug 29 12:11:18 pressy AptDaemon: INFO: Quitting was requested
Aug 29 12:17:01 pressy CRON[5264]: (root) CMD (   cd / && run-parts
--report /etc/cron.hourly)

**--/**--

The failure seemed to happen when the timeout changed from 5 to 1
So clutching at straws I assume that something is changing the timeout
to the point where the hardware can't keep up. Another likely
explanation is that it doesn't have anything to do with this ??...

Any help or suggestions welcome.