hplip-3.14.10 does not scan cutout smaller than 49mm x 49mm

[Kai Wüstermann]

Since switching to net-print/hplip with a LaserJet pro 200 color I can not scan small images.

don't work:
scanimage -y 49 -x 48 --format=pnm > aktuell.pnm
scanimage: sane_start: Invalid argument
---------------------------------------------------

work:
scanimage -y 49 -x 49 --format=pnm > aktuell.pnm
---------------------------------------------------

He has the same problem:
https://sejh.wordpress.com/2014/11/07/xsane-konnte-scanner-nicht-starten-ungultiges-argument/

This bug infects all my linux installations: gentoo and ubuntu (different releases)

[Kai Wüstermann (k-wuestermann)]

Since switching from epson-sane-backend to net-print/hplip with a LaserJet pro 200 color I can not scan small images.

don't work:
scanimage -y 49 -x 48 --format=pnm > aktuell.pnm
scanimage: sane_start: Invalid argument
---------------------------------------------------

work:
scanimage -y 49 -x 49 --format=pnm > aktuell.pnm
---------------------------------------------------

He has the same problem:
https://sejh.wordpress.com/2014/11/07/xsane-konnte-scanner-nicht-starten-ungultiges-argument/

Reproducible: Always

Steps to Reproduce:
1.scanimage -y 49 -x 48 --format=pnm > aktuell.pnm
Actual Results:
scanimage: sane_start: Invalid argument

Expected Results:
should scan

scanimage -L
device `hpaio:/net/HP_LaserJet_200_colorMFP_M276n?ip=192.168.1.11' is a Hewlett-Packard HP_LaserJet_200_colorMFP_M276n all-in-one
---------------------------------------------------

hp-query -a -d "hp:/net/HP_LaserJet_200_colorMFP_M276n?ip=192.168.1.11"
align-type=0
clean-type=0
color-cal-type=0
copy-type=0
embedded-server-type=0
fax-type=7
fw-download=False
icon=hp_color_laserjet_cm1312_mfp.png
io-mfp-mode=1
io-mode=1
io-support=6
job-storage=0
linefeed-cal-type=0
model1=HP LaserJet Pro 200 color MFP M276n
monitor-type=0
panel-check-type=0
pcard-type=0
plugin=1
plugin-reason=64
power-settings=0
ppd-name=laserjet_200_colormfp_m276
pq-diag-type=0
r-type=0
r0-agent1-kind=4
r0-agent1-sku=CF210A/CF210X
r0-agent1-type=1
r0-agent2-kind=4
r0-agent2-sku=CF211A
r0-agent2-type=4
r0-agent3-kind=4
r0-agent3-sku=CF213A
r0-agent3-type=5
r0-agent4-kind=4
r0-agent4-sku=CF212A
r0-agent4-type=6
scan-src=3
scan-type=5
status-battery-check=0
status-dynamic-counters=0
status-type=10
support-released=True
support-subtype=2202411
support-type=2
support-ver=3.12.9
tech-class=['Postscript']
tech-subclass=['Normal']
tech-type=4
usb-pid=4650
usb-vid=1008
wifi-config=0
--------------------------------------------

emerge --info
Portage 2.2.18 (python 2.7.9-final-0, default/linux/amd64/13.0/desktop, gcc-4.8.4, glibc-2.20-r2, 3.18.11-gentoo x86_64)
=================================================================
System uname: Linux-3.18.11-gentoo-x86_64-Intel-R-_Core-TM-2_Quad_CPU_Q8200_@_2.33GHz-with-gentoo-2.2
KiB Mem: 4046972 total, 961228 free
KiB Swap: 4194300 total, 4194300 free
Timestamp of repository gentoo: Sat, 02 May 2015 14:45:01 +0000
sh dash 0.5.7.4
ld GNU ld (Gentoo 2.24 p1.4) 2.24
ccache version 3.1.9 [enabled]
app-shells/bash: 4.2_p53::gentoo
dev-java/java-config: 2.2.0::gentoo
dev-lang/perl: 5.20.2::gentoo
dev-lang/python: 2.7.9-r1::gentoo, 3.3.5-r1::gentoo, 3.4.1::gentoo
dev-util/ccache: 3.1.9-r4::gentoo
dev-util/cmake: 2.8.12.2-r1::gentoo
dev-util/pkgconfig: 0.28-r2::gentoo
sys-apps/baselayout: 2.2::gentoo
sys-apps/openrc: 0.13.11::gentoo
sys-apps/sandbox: 2.6-r1::gentoo
sys-devel/autoconf: 2.13::gentoo, 2.69::gentoo
sys-devel/automake: 1.10.3-r1::gentoo, 1.11.6-r1::gentoo, 1.12.6::gentoo, 1.13.4::gentoo
sys-devel/binutils: 2.24-r3::gentoo
sys-devel/gcc: 4.8.4::gentoo
sys-devel/gcc-config: 1.7.3::gentoo
sys-devel/libtool: 2.4.6::gento...

[Billie-gentoo (billie-gentoo)]

I can not reproduce this issue here, so this looks like a device specific issue. It is probably better to report this issue at the upstream bug tracker (https://bugs.launchpad.net/hplip/).

Another thing to check! Your device seems to require a binary plugin. Please make sure it is installed correctly.

[Kai Wüstermann (k-wuestermann)]

(In reply to Daniel Pielmeier from comment #1)
> I can not reproduce this issue here, so this looks like a device specific
> issue. It is probably better to report this issue at the upstream bug
> tracker (https://bugs.launchpad.net/hplip/).

I did it.
https://bugs.launchpad.net/hplip/+bug/1451980