[Bug 905034] New: scanimage produces wrong colours in scan
http://bugzilla.opensuse.org/show_bug.cgi?id=905034 Bug ID: 905034 Summary: scanimage produces wrong colours in scan Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: per@computer.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 613296 --> http://bugzilla.opensuse.org/attachment.cgi?id=613296&action=edit scanimage output, resolution 150 Hardware: lenovo desktop12. Running vanilla openSUSE 13.2 via NFS root. Doing a scan like these: scanimage --mode color --resolution 300 >office12-scan1.pnm scanimage --mode color --resolution 300 >office12-scan2.pnm produces some pretty weird colours, see attached. Omitting the resolution argument or specifying "--resolution 50" both lead to a "Error in `scanimage': double free or corruption (top): ". I have sane-backends-1.0.24-2.1.10.x86_64 installed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
--- Comment #1 from Per Jessen
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
--- Comment #2 from Per Jessen
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
Per Jessen
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
--- Comment #3 from Per Jessen
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
Johannes Meixner
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
Johannes Meixner
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
Johannes Meixner
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
Per Jessen
According to https://bugzilla.opensuse.org/show_bug.cgi?id=903839#c4 it seems to make a difference what HPLIP package versions are installed.
Per Jessen, is this still the case here?
No, as hplip-hpijs and hplip-sane are not needed, I removed them from both desktop systems to eliminate that variable. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
--- Comment #6 from Johannes Meixner
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
--- Comment #9 from Per Jessen
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
Per Jessen
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
--- Comment #11 from Per Jessen
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
--- Comment #12 from Per Jessen
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
--- Comment #13 from Per Jessen
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
--- Comment #14 from Per Jessen
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
--- Comment #15 from Per Jessen
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
--- Comment #16 from Johannes Meixner
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
--- Comment #17 from Per Jessen
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
Johannes Meixner
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
--- Comment #19 from Johannes Meixner
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
--- Comment #20 from Per Jessen
A totally different idea:
Your office12-scanimage.open.strace shows: --------------------------------------------------------------------------- open("/home/per/.sane/hewlett-packard-scanjet-2400c.cal",... --------------------------------------------------------------------------- this together with what "man sane-genesys" tells about calibration in particular things like --------------------------------------------------------------------------- If you plug the scanner in another machine or use it with another account, calibration will have to be redone. --------------------------------------------------------------------------- and --------------------------------------------------------------------------- --threshold percent 0..100% (in steps of 1). Select minimum brightness to get a white point. Pixels whith brightness below that value will be scanned as black. --------------------------------------------------------------------------- and how your office12-scanimage-scan10.pnm looks like:
Perhaps your current calibration is wrong?
Could you move /home/per/.sane/hewlett-packard-scanjet-2400c.cal away and test again and furthermore re-do the calibration and test again?
Okay, I did the following> power off/on scanner (to reset) rm ~/.sane/hewlett-packard-scanjet-2400c.cal scanimage --mode color --resolution 300 >scan001.pnm
weird colours. scanimage --mode color --resolution 150 >scan002.pnm weird colours. scanimage --mode color --resolution 300 >scan003.pnm weird colours.
I have never calibrated this scanner before, it was bought in June 2007, even if it came with a calibration sheet, it is long gone. Also, when I use it from office11 (openSUSE 13.1), it works fine. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
--- Comment #21 from Per Jessen
(In reply to Johannes Meixner from comment #19)
A totally different idea:
Your office12-scanimage.open.strace shows: --------------------------------------------------------------------------- open("/home/per/.sane/hewlett-packard-scanjet-2400c.cal",... --------------------------------------------------------------------------- this together with what "man sane-genesys" tells about calibration in particular things like --------------------------------------------------------------------------- If you plug the scanner in another machine or use it with another account, calibration will have to be redone. --------------------------------------------------------------------------- and --------------------------------------------------------------------------- --threshold percent 0..100% (in steps of 1). Select minimum brightness to get a white point. Pixels whith brightness below that value will be scanned as black. --------------------------------------------------------------------------- and how your office12-scanimage-scan10.pnm looks like:
Perhaps your current calibration is wrong?
Could you move /home/per/.sane/hewlett-packard-scanjet-2400c.cal away and test again and furthermore re-do the calibration and test again?
Okay, I did the following>
power off/on scanner (to reset) rm ~/.sane/hewlett-packard-scanjet-2400c.cal scanimage --mode color --resolution 300 >scan001.pnm
weird colours. scanimage --mode color --resolution 150 >scan002.pnm weird colours. scanimage --mode color --resolution 300 >scan003.pnm weird colours.
I have never calibrated this scanner before, it was bought in June 2007, even if it came with a calibration sheet, it is long gone. Also, when I use it from office11 (openSUSE 13.1), it works fine.
According to "man sane-genesys" : To do calibration, you must insert this target in the feeder then start calibration either by passing the --calibrate option to scanimage I tried that, scanimage does not recognize option --calibrate :-( -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
--- Comment #22 from Per Jessen
Now the scanner itself could be somehow a bit damaged but I think this is unlikely.
Yes, also given that it works fine with another desktop, that seems unlikely.
For now it is only a gut feeling but I think that something goes wrong during USB data transfer in the software that is used for the low-level USB data transfer.
I have been thinking exactly that.
For me it looks as if while the data is being read from the scanner, the data becomes more and more distorted and this seems to indicate that something goes more and more wrong during USB data transfer.
One little hardware difference - office11, where the scanner works, has a local disk as root, office12 and -13 both boot from NFS. It seems like a long shot, but the two NFS-root machines probably have more I/O and interrupts happening during the data transfer. I might try another machine with local disk and see what happens.
Please install kernel-default and boot with it (you may have to manually select it in the Grub boot menue) and then run
# lspci -v | egrep -i 'usb|hci'
# lsmod | egrep 'usb|hci'
and post the output of both commands here.
Willdo. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
--- Comment #23 from Johannes Meixner
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
Per Jessen
(In reply to Johannes Meixner from comment #18)
Now the scanner itself could be somehow a bit damaged but I think this is unlikely.
Yes, also given that it works fine with another desktop, that seems unlikely.
For now it is only a gut feeling but I think that something goes wrong during USB data transfer in the software that is used for the low-level USB data transfer.
I have been thinking exactly that.
For me it looks as if while the data is being read from the scanner, the data becomes more and more distorted and this seems to indicate that something goes more and more wrong during USB data transfer.
One little hardware difference - office11, where the scanner works, has a local disk as root, office12 and -13 both boot from NFS. It seems like a long shot, but the two NFS-root machines probably have more I/O and interrupts happening during the data transfer. I might try another machine with local disk and see what happens.
Please install kernel-default and boot with it (you may have to manually select it in the Grub boot menue) and then run
# lspci -v | egrep -i 'usb|hci'
# lsmod | egrep 'usb|hci'
and post the output of both commands here.
Willdo.
office12a:~ # lspci -v | egrep -i 'usb|hci' 00:1d.0 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 04) (prog-if 00 [UHCI]) Kernel driver in use: uhci_hcd Kernel modules: uhci_hcd 00:1d.1 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 04) (prog-if 00 [UHCI]) Kernel driver in use: uhci_hcd Kernel modules: uhci_hcd 00:1d.2 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 04) (prog-if 00 [UHCI]) Kernel driver in use: uhci_hcd Kernel modules: uhci_hcd 00:1d.7 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 04) (prog-if 20 [EHCI]) Kernel driver in use: ehci-pci Kernel modules: ehci_pci # lsmod | egrep 'usb|hci' usbhid 52574 0 ehci_pci 12914 0 uhci_hcd 49376 0 ehci_hcd 79604 1 ehci_pci usbcore 256127 4 uhci_hcd,ehci_hcd,ehci_pci,usbhid usb_common 13057 1 usbcore # dmesg | grep usb [ 3.745883] usbcore: registered new interface driver usbfs [ 3.745909] usbcore: registered new interface driver hub [ 3.760130] usbcore: registered new device driver usb [ 3.768619] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001 [ 3.768700] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.768806] usb usb1: Product: UHCI Host Controller [ 3.768875] usb usb1: Manufacturer: Linux 3.16.6-2-default uhci_hcd [ 3.768946] usb usb1: SerialNumber: 0000:00:1d.0 [ 3.791767] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 [ 3.791845] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.791952] usb usb2: Product: UHCI Host Controller [ 3.792046] usb usb2: Manufacturer: Linux 3.16.6-2-default uhci_hcd [ 3.792120] usb usb2: SerialNumber: 0000:00:1d.1 [ 3.805173] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 [ 3.805250] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.805357] usb usb3: Product: UHCI Host Controller [ 3.805425] usb usb3: Manufacturer: Linux 3.16.6-2-default uhci_hcd [ 3.805496] usb usb3: SerialNumber: 0000:00:1d.2 [ 3.839068] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002 [ 3.839120] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.839160] usb usb4: Product: EHCI Host Controller [ 3.839195] usb usb4: Manufacturer: Linux 3.16.6-2-default ehci_hcd [ 3.839232] usb usb4: SerialNumber: 0000:00:1d.7 [ 5.092046] usb 1-1: new low-speed USB device number 2 using uhci_hcd [ 5.246101] usb 1-1: New USB device found, idVendor=046a, idProduct=0011 [ 5.246163] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 5.488051] usb 2-2: new low-speed USB device number 2 using uhci_hcd [ 5.664530] usb 2-2: New USB device found, idVendor=046d, idProduct=c03e [ 5.664593] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 5.664645] usb 2-2: Product: USB-PS/2 Optical Mouse [ 5.664682] usb 2-2: Manufacturer: Logitech [ 5.908116] usb 3-1: new full-speed USB device number 2 using uhci_hcd [ 6.093087] usb 3-1: New USB device found, idVendor=03f0, idProduct=0a01 [ 6.093150] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=12 [ 6.093202] usb 3-1: Product: hp scanjet scanner [ 6.093237] usb 3-1: Manufacturer: Hewlett-Packard [ 6.093272] usb 3-1: SerialNumber: CN66PSR1SZ [ 14.146791] usbcore: registered new interface driver usbhid -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
Johannes Meixner
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
--- Comment #26 from Per Jessen
Perhaps you are a venturous openSUSE user who likes to try out if sane-backends development version git20150108 works for you? If you like to try it out, please report whether or not it works for you.
I'll try out it and get back to you. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
--- Comment #27 from Johannes Meixner
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
http://bugzilla.opensuse.org/show_bug.cgi?id=905034#c28
Jon Nelson
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
http://bugzilla.opensuse.org/show_bug.cgi?id=905034#c32
Per Jessen
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
http://bugzilla.opensuse.org/show_bug.cgi?id=905034#c33
--- Comment #33 from Per Jessen
I have just yesterday observed this issue on Leap421. I have a test system which I have been using with my scanner for a good few months, no problems, colours all fine. Yesterday I decided to re-install it, also Leap421+updates, and now I get poor/bad colours on scans.
This was seen with skanlite. Using 'scanimage' gives me a segfault. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
http://bugzilla.opensuse.org/show_bug.cgi?id=905034#c34
--- Comment #34 from Per Jessen
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
http://bugzilla.opensuse.org/show_bug.cgi?id=905034#c35
--- Comment #35 from Per Jessen
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
http://bugzilla.opensuse.org/show_bug.cgi?id=905034#c36
--- Comment #36 from Per Jessen
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
http://bugzilla.opensuse.org/show_bug.cgi?id=905034#c37
--- Comment #37 from Per Jessen
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
http://bugzilla.opensuse.org/show_bug.cgi?id=905034#c38
--- Comment #38 from Per Jessen
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
http://bugzilla.opensuse.org/show_bug.cgi?id=905034#c39
--- Comment #39 from Per Jessen
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
Friedhelm Stappert
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
http://bugzilla.opensuse.org/show_bug.cgi?id=905034#c40
--- Comment #40 from Jon Nelson
Jon Nelson, please post an URL of the sane-backends upstream bug here.
https://alioth.debian.org/tracker/?func=detail&atid=410366&aid=314927&group_id=30186 In that bug I assert that 24ab521a1db259610dcbade7facc66d24ce29058s appears to fix it. It does not, I just re-tested. I re-ran all of the git bisect and came up with this: git bisect good d87619e71f2778fcf8985c057b1b3c70bd13921c # only skipped commits left to test # possible first bad commit: [bc1a14518b8e24600d549877f3a22308425c340d] Updates for recent genesys changes # possible first bad commit: [a5a6543cd0585859a698e44998cbca37bf072c42] support for 5th LiDE 210 button # possible first bad commit: [e1a74a94beda015f13e8c83b06912a3b4e6f5e42] warnings clean up # possible first bad commit: [d62ebea4e85c414051d54e4033cdcc5f510653c1] changelog for genesys update # possible first bad commit: [0897a60c601dc79e596762922ffcbe91b078f258] genesys backend update - groundwork for gl846 support - asic init rework - several refactors This is with LEAP 42.2. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
http://bugzilla.opensuse.org/show_bug.cgi?id=905034#c41
Per Jessen
http://bugzilla.opensuse.org/show_bug.cgi?id=905034
http://bugzilla.opensuse.org/show_bug.cgi?id=905034#c42
Johannes Meixner
participants (1)
-
bugzilla_noreply@novell.com