[Bug 1166004] New: Canon LiDE 700F not working with sane-backends 1.0.29-1.1
http://bugzilla.opensuse.org/show_bug.cgi?id=1166004 Bug ID: 1166004 Summary: Canon LiDE 700F not working with sane-backends 1.0.29-1.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs@suse.de Reporter: suse.junky@t-online.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I have a Canon LiDE 700F flatbed scanner connected via USB to an USB3.0-port of my machine.
scanimage -L device `genesys:libusb:001:006' is a Canon LiDE 700F flatbed scanner
My machine runs openSUSE Tumbleweed with Kernel 5.5.7-1-default sane-backends 1.0.29-1.1 libsane1 1.0.29-1.1 xsane 0.999-2.10 Using sane-backends 1.0.27. scanning worked fine but last week my machine received an update to sane-backends 1.0.29 and scanning does not work any longer. When i use xsane and do a preview i can see the page being build up but at the end when the scan-bar has been moved back to its start position the preview gets deleted and xsane gives an device-I/O-error. When i use xsane and do a normal scan at the end when the scan-bar has been moved back to its start position xsane gives an device-I/O-error. When i use scanimage at the end when the scan-bar has been moved back to its start position scanimage tries to kill my scanner (horrible noises come from my scanner) and i have to unplug it in order to avoid that my scanner gets damaged. I did export SANE_DEBUG_GENESYS=255 export SANE_DEBUG_GENESYS_LOW=255 export SANE_DEBUG_GENESYS_GL124=255 export SANE_DEBUG_GENESYS_GL646=255 export SANE_DEBUG_GENESYS_GL841=255 export SANE_DEBUG_GENESYS_GL843=255 export SANE_DEBUG_GENESYS_GL847=255 export SANE_DEBUG_SANEI_USB=128 and then scanimage -T 2>sane_T.log it produced the files 15278 gl_pipeline_1_0_before_swap.pnm 15278 gl_pipeline_1_1_after_swap.pnm 15278 gl_pipeline_1_2_after_shift.pnm 15278 gl_pipeline_1_3_after_stagger.pnm 1241280 sane_T.log Then i did scanimage --clear-calibration --preview --mode Color 1>calibrate.pnm 2>sane_P.log 3>sane_P_err.log it produced the files 0 sane_P_err.log 41493738 sane_P.log 1671443 calibrate.pnm 31144 gl847_led_00.pnm 31144 gl847_led_01.pnm 31144 gl847_led_02.pnm 31144 gl847_led_03.pnm 31144 gl_black__average.pnm 2178977 gl_black__shading.pnm 1673332 gl_pipeline_6_0_before_swap.pnm 1673332 gl_pipeline_6_1_after_swap.pnm 1673331 gl_pipeline_6_2_after_shift.pnm 1673331 gl_pipeline_6_3_after_stagger.pnm 31144 gl_white__average.pnm 2178977 gl_white__shading.pnm The files sane_T.log and sane_P.log are obviously too large to be attached here but i can provide them if necessary (or search them if told what to search for). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1166004
http://bugzilla.opensuse.org/show_bug.cgi?id=1166004#c1
--- Comment #1 from Bit Juggler
http://bugzilla.opensuse.org/show_bug.cgi?id=1166004
http://bugzilla.opensuse.org/show_bug.cgi?id=1166004#c2
Bit Juggler
http://bugzilla.opensuse.org/show_bug.cgi?id=1166004
http://bugzilla.opensuse.org/show_bug.cgi?id=1166004#c5
Bit Juggler
As you found out, this is an upstream problem. Please proceed there.
As downgrading would be a regression for other drivers now, this is not an option.
This bug renders a Canon LiDE 700F completely useless. Would those "regressions" be that serious as well? Anyway, from my past time experience i should have known that reporting bugs here is just a waste of time. However THIS PROBLEM IS NOT SOLVED! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1166004
http://bugzilla.opensuse.org/show_bug.cgi?id=1166004#c6
Stefan Brüns
http://bugzilla.opensuse.org/show_bug.cgi?id=1166004
http://bugzilla.opensuse.org/show_bug.cgi?id=1166004#c7
--- Comment #7 from Bit Juggler
Calm down, stop SHOUTING, won't help your case.
The problem has to be solved by upstream developers, but by (open)SUSE packagers.
??? So who is the one to solve it ???
It is not a packaging bug.
Ahhh! This place here is only to report "packaging bugs"! Sorry, i was not aware of this (and i have to admit that i have no idea what a "packaging bug" is).
If you want progress, work with the upstream developers.
Reporting bugs here is not useless,
As you said. It is useless for non-packaging bugs.
but in this case its just the wrong place. As soon as the problem is solved *upstream*, *and* the fix is not packaged, feel free to report back.
Sane 1.0.28/1.0.29 adds support for dozens of devices from several vendors, and fixes bugs for many devices. So from a pure numbers point you definitely loose, but you could have checked that yourself.
-- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com