[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 <per@computer.org> --- Created attachment 613297 --> http://bugzilla.opensuse.org/attachment.cgi?id=613297&action=edit scanimage output, resolution 300 -- 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 #2 from Per Jessen <per@computer.org> --- Created attachment 613300 --> http://bugzilla.opensuse.org/attachment.cgi?id=613300&action=edit scanimage output, resolution 300 (different desktop) This was scanned with the desktop where this scanner is normally attached. It is running openSUSE 13.1 64bit with sane-backends-1.0.24-106.1.x86_64 (as was suggested to me in bug#851543). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905034 Per Jessen <per@computer.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|scanimage produces wrong |scanimage produces wrong |colours in scan |colours in scan (with HP | |Scanjet 2400) -- 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 #3 from Per Jessen <per@computer.org> --- I forgot to mention the scanner hardware - it is an HP Scanjet 2400 connected via USB 2.0. -- 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 <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsmeix@suse.com Found By|--- |Community User Assignee|bnc-team-screening@forge.pr |jsmeix@suse.com |ovo.novell.com | Summary|scanimage produces wrong |sane-backends: scanimage |colours in scan (with HP |produces wrong colours (HP |Scanjet 2400) |Scanjet 2400, genesys | |backend, various | |resolutions) OS|Other |openSUSE 13.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 Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Hardware|Other |x86-64 -- 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 <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |per@computer.org Flags| |needinfo?(per@computer.org) --- Comment #4 from Johannes Meixner <jsmeix@suse.com> --- 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? According to https://bugzilla.opensuse.org/show_bug.cgi?id=903839#c18 it seems to have helped to remove all HPLIP packages and afterwards re-install sane-backends. Does this also help here? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905034 Per Jessen <per@computer.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(per@computer.org) | --- Comment #5 from Per Jessen <per@computer.org> --- (In reply to Johannes Meixner from comment #4)
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 <jsmeix@suse.com> --- Good! So it seems now we have a "clean" issue in sane-backends plus all libraries it pulls in. -- 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 #9 from Per Jessen <per@computer.org> --- Created attachment 613853 --> http://bugzilla.opensuse.org/attachment.cgi?id=613853&action=edit the 300dpi scan bzipped -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905034 Per Jessen <per@computer.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(per@computer.org) | --- Comment #10 from Per Jessen <per@computer.org> --- Created attachment 613854 --> http://bugzilla.opensuse.org/attachment.cgi?id=613854&action=edit the 150dpi scan bzipped -- 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 #11 from Per Jessen <per@computer.org> --- Created attachment 613855 --> http://bugzilla.opensuse.org/attachment.cgi?id=613855&action=edit pnm output as per comment#8 -- 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 #12 from Per Jessen <per@computer.org> --- Created attachment 613856 --> http://bugzilla.opensuse.org/attachment.cgi?id=613856&action=edit strace output as per comment#8 -- 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 #13 from Per Jessen <per@computer.org> --- As the scan in attachment#613855 looks fine, I ran a scan with 300dpi which resulted in the same distorted colours as in attachment#613300. Then I tried to repeat the 150dpi scan with strace, but this resulted in "scanimage: sane_read: Error during device I/O". I'll attach the strace in a minute. -- 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 #14 from Per Jessen <per@computer.org> --- Created attachment 613858 --> http://bugzilla.opensuse.org/attachment.cgi?id=613858&action=edit strace that ended in "scanimage: sane_read: Error during device I/O" -- 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 #15 from Per Jessen <per@computer.org> --- I'm guessing that the scanner was somehow put in an odd state, perhaps because it's been used from the working desktop over the weekend, so I did the following powered the scanner off/on scanimage --mode color --resolution 300 >office12-300dpi-2.pnm (scan worked, colours distorted) scanimage --mode color --resolution 150 >office12-image150-3.pnm (scan worked, colours are fine) strace etc. scanimage --mode color --resolution 300 >office12-300dpi-3.pnm (scan worked, colours distorted) I can attach the last strace if you want. -- 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 #16 from Johannes Meixner <jsmeix@suse.com> --- FYI: According to my personal experience "Error during device I/O" was in the past basically always caused by some low-level hardware related issue for example something like an issue in the scanner device or an issue in the computer (e.g. in the computer's built-in USB hardware) or an issue in some hardware in between (e.g. an USB hub in between) or unreliably working cable connection (e.g. weak USB cable) or USB kernel modules for higher speed USB have been used (like ehci for USB 2.0 or xhci for USB 3.0) but the scanner device needs lower USB speed (e.g. ehci instead of xhci or ohci for USB 1.1 or uhci for USB 1.0 instead of ehci) or whatever other things like that... -- 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 #17 from Per Jessen <per@computer.org> --- Hi Johannes just to rule out some arbitrary hardware issue, I installed 13.2 onto a completely different desktop box yesterday and tried the scanning - same problem. -- 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 <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(per@computer.org) --- Comment #18 from Johannes Meixner <jsmeix@suse.com> --- Many thanks for your test on different hardware! According to https://bugzilla.opensuse.org/show_bug.cgi?id=903839#c15 I don't think the actual hardware is the root cause. But I think the root cause is related to the hardware. Reasoning: Your office12-scanimage-scan11.pnm in attachment#613854 has wrong colors but your office12-image150.pnm in attachment#613855 has right colors and both are made by "scanimage --mode color --resolution 150". When the same scan program runs two times but results different data I cannot imagine a reason how the difference can be caused by the software. Both office12-scanimage-scan11.pnm and office12-image150.pnm have same size so that the same amount of data is read from the scanner but the data itself differs. This indicates that what comes in from the scanner differs. Now the scanner itself could be somehow a bit damaged but I think this is 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 noticed that on your office12-scanimage-scan11.pnm the colors are o.k. on the top and then colors becomes more and more wrong starting at the end of each line but then towards the end more and more the whole lines get more and more wrong colors ("white" gets first yellow and then it becomes red). 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. When it is not the actual hardware, then hardware related issues are basically issues in the hardware related software which is the kernel, low-level libraries (like libusb), and driver software on application level (like the genesys driver in SANE). I would like to see what USB related kernel modules are actually used on your computer. See https://bugzilla.opensuse.org/show_bug.cgi?id=903839#c20 -------------------------------------------------------------------------- When using kernel-desktop (seems to be the default for 13.2) then there are no USB-related kernel modules. When using kernel-default (seems to be not the default for 13.2) then there are USB-related kernel modules. -------------------------------------------------------------------------- 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. -- 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 #19 from Johannes Meixner <jsmeix@suse.com> --- 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? -- 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 #20 from Per Jessen <per@computer.org> --- (In reply to Johannes Meixner from comment #19)
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
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 <per@computer.org> --- (In reply to Per Jessen from comment #20)
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 <per@computer.org> --- (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.
I have been thinking exactly that.
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.
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 <jsmeix@suse.com> --- Please also post the output of: # dmesg | grep usb I am in particular interested if the kernel recognizes your USB scanner device like "new full speed USB device" or as "new high speed USB device" The latter case can cause issues when your USB scanner is acually only a full speed USB device (i.e. USB 1.1) but the kernel operates it as if it was a high speed USB device (i.e. USB 2.0). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905034 Per Jessen <per@computer.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(per@computer.org) | --- Comment #24 from Per Jessen <per@computer.org> --- (In reply to Per Jessen from comment #22)
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 <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(per@computer.org) --- Comment #25 from Johannes Meixner <jsmeix@suse.com> --- Regarding the genesys driver we also got bug#897855 (different symptoms) but there it also had worked on a 13.1 system. According to https://bugzilla.opensuse.org/show_bug.cgi?id=897855#c5 it seems something was fixed regarding the genesys driver in a recent development snapshot at SANE upstream. I made sane-backends version git20150108 RPMs an unstable development source only for testing, without any guarantee or warranty, and without any support in my openSUSE build service home project "home:jsmeix". Please read https://build.opensuse.org/project/show?project=home:jsmeix You can get the packages in the "home:jsmeix" project for example for openSUSE 13.2 from this direct URL http://download.opensuse.org/repositories/home:/jsmeix/openSUSE_13.2/ When you like to upgrade an installed sane-backends 1.0.23 or 1.0.24 to sane-backends development version git20150108 you need to install version git20150108 with plain rpm using "--force" e.g. like # rpm -Uhv --force sane-backends-git20150108-2.1.x86_64.rpm because for rpm the version number git2015010 is lower than the installed version number 1.0.23 or 1.0.24. For my scanner that uses the plustek driver sane-backends development version git20150108 still works for me. 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. Many thanks in advance for testing it and for your feedback! Caution: When you try it out and your scanner makes bad-sounding noises the usual reason is that the scanner's internal moving parts "do bad things" which means the scanner hardware could get damaged. -- 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 #26 from Per Jessen <per@computer.org> --- (In reply to Johannes Meixner from comment #25)
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 <jsmeix@suse.com> --- According to https://bugzilla.opensuse.org/show_bug.cgi?id=897855#c7 it seems sane-backends development version git20150108 may not yet have the actual root cause fixed. Because both in bug#897855 and also here there is "Error during device I/O" I think the root cause is basically the same and I still think the actual root cause is some lover level USB stuff (see also bug#897855). Regardless that you disagree with my reasoning in bug#903839 that I cannot do anything unless I can reprodue your issue on my system, I still think you should really report your issue directly to the sane-backends authors at the SANE project http://www.sane-project.org so that there is a direct communication between you and the upstream authors. It would be best when you report it on the sane-devel mailing list so that the upstream authors plus other interested users can notice the issue, see http://www.sane-project.org/mailing-lists.html -- 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#c28 Jon Nelson <jnelson-suse@jamponi.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jnelson-suse@jamponi.net --- Comment #28 from Jon Nelson <jnelson-suse@jamponi.net> --- I have the same problem. Different hardware, same backend. Newer versions of the software (sane-backends) fixes this nicely. Please consider updating the software. -- 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#c32 Per Jessen <per@computer.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|13.2 |Leap 42.1 OS|openSUSE 13.2 |openSUSE 42.1 --- Comment #32 from Per Jessen <per@computer.org> --- 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. Because the hardware didn't change and I'm pretty certain the software didn't either (can't be 100% certain), it seems it could be some sort of initialisation issue? -- 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#c33 --- Comment #33 from Per Jessen <per@computer.org> --- (In reply to Per Jessen from comment #32)
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 <per@computer.org> --- Created attachment 706176 --> http://bugzilla.opensuse.org/attachment.cgi?id=706176&action=edit scan with 300dpi, This problem seems to be coming round all the time. On a brand new, vanilla Leap422 install, skanlite produces funky colours, depending on the scan resolution. Some times I have been able to get a good scan by alternatiing between 150 and 300dpi, this morning I had to reduce to 100dpi. -- 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#c35 --- Comment #35 from Per Jessen <per@computer.org> --- Created attachment 706177 --> http://bugzilla.opensuse.org/attachment.cgi?id=706177&action=edit 2nd attempt, reduced to 150dpi -- 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#c36 --- Comment #36 from Per Jessen <per@computer.org> --- Created attachment 706178 --> http://bugzilla.opensuse.org/attachment.cgi?id=706178&action=edit 3rd attempt, also 15-dpi -- 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#c37 --- Comment #37 from Per Jessen <per@computer.org> --- Created attachment 706180 --> http://bugzilla.opensuse.org/attachment.cgi?id=706180&action=edit 4th attempt, 300dpi -- 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#c38 --- Comment #38 from Per Jessen <per@computer.org> --- Created attachment 706181 --> http://bugzilla.opensuse.org/attachment.cgi?id=706181&action=edit 5th attempt, 100dpi - this one worked. -- 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#c39 --- Comment #39 from Per Jessen <per@computer.org> --- I have reduced the 300dpi scan to 1200px wide, the originals were 2598px. I have also redacted some details. Sofar this scanner has worked well on openSUSE 13.1, I'll check if that is the case. Not having a working scanner is a bit of a show-stopper wrt Leap42x for the office. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905034 Friedhelm Stappert <friedhelm.stappert@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |friedhelm.stappert@web.de -- 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#c40 --- Comment #40 from Jon Nelson <jnelson-suse@jamponi.net> --- (In reply to Johannes Meixner from comment #31)
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 <per@computer.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Leap 42.1 |Leap 42.2 OS|openSUSE 42.1 |openSUSE 42.2 --- Comment #41 from Per Jessen <per@computer.org> --- Using Skanlite - problem persists in Leap422 with latest updates, although I got a good scan with 150dpi. I also tried VueScan, which worked just fine. Using scanimage - a fairly decent scan in 150dpi, although too dark in the upper end of the scan. Wrong colours in 300dpi and in 600dpi. -- 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#c42 Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UPSTREAM --- Comment #42 from Johannes Meixner <jsmeix@suse.com> --- I do no longer find any time to work on such issues (neither help with debugging nor anything else). In general see https://en.opensuse.org/SDB:Configuring_Scanners therein in particular the section about "RPM packages of the 'sane-backends' scanner drivers" that reads (excerpts): --------------------------------------------------------------------------- In general we (i.e. openSUSE) distribute the "sane-backends" scanner drivers from the SANE project but we do not develop scanner drivers. Usually we do not have all those various kind of scanners for all those various kind of scanner drivers so that usually we cannot do anything when a particular scanner driver does not work. In particular usually we cannot reproduce issues with scanner drivers. When a particular scanner driver is listed at the SANE project that it should work for your particular scanner model but it does not work for you with the currently latest "sane-backends" version that is officially released by the SANE project, then it is recommended to report the issue directly to the driver authors at the SANE project http://www.sane-project.org so that there is a direct communication between you and the upstream authors. --------------------------------------------------------------------------- -- 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 <per@computer.org> --- Created attachment 613297 --> http://bugzilla.opensuse.org/attachment.cgi?id=613297&action=edit scanimage output, resolution 300 -- 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 #2 from Per Jessen <per@computer.org> --- Created attachment 613300 --> http://bugzilla.opensuse.org/attachment.cgi?id=613300&action=edit scanimage output, resolution 300 (different desktop) This was scanned with the desktop where this scanner is normally attached. It is running openSUSE 13.1 64bit with sane-backends-1.0.24-106.1.x86_64 (as was suggested to me in bug#851543). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905034 Per Jessen <per@computer.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|scanimage produces wrong |scanimage produces wrong |colours in scan |colours in scan (with HP | |Scanjet 2400) -- 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 #3 from Per Jessen <per@computer.org> --- I forgot to mention the scanner hardware - it is an HP Scanjet 2400 connected via USB 2.0. -- 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 <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsmeix@suse.com Found By|--- |Community User Assignee|bnc-team-screening@forge.pr |jsmeix@suse.com |ovo.novell.com | Summary|scanimage produces wrong |sane-backends: scanimage |colours in scan (with HP |produces wrong colours (HP |Scanjet 2400) |Scanjet 2400, genesys | |backend, various | |resolutions) OS|Other |openSUSE 13.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 Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Hardware|Other |x86-64 -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com