[Bug 210172] New: Scanner: Canon CanoScan LiDE 20 USB jams with SANE-1.0.17-18
https://bugzilla.novell.com/show_bug.cgi?id=210172 Summary: Scanner: Canon CanoScan LiDE 20 USB jams with SANE- 1.0.17-18 Product: SUSE Linux 10.1 Version: Final Platform: i686 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Normal Priority: P5 - None Component: Hotplug AssignedTo: ihno@novell.com ReportedBy: mark_1@gmx.de QAContact: qa@suse.de The scanner jams at least every second page during init or after scanning making an ugly noise. Only unplugging helps to stop it. With the package SANE 1.0.15-20 from SUSE 10.0 everything works fine. The scanner was installed with YAST and uses the plustek driver. Scanning was done with xsane. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=210172 ihno@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|ihno@novell.com |jsmeix@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=210172 ------- Comment #1 from jsmeix@novell.com 2007-01-17 01:39 MST ------- If it is a problem in the scanner driver, we cannot fix it because neither do we have this particular scanner model nor do we develop the actual drivers by ourselves. The Suse Linux 10.0 packages should also run without problems on a Suse Linux 10.1 system so that a downgrade to the "sane" package of Suse Linux 10.0 may help. But I guess that it is no problem in the scanner driver because - your model is reletively often in use and if the driver would not work, I should have notices several such bug reports but yours is the only one - if it is a problem in the driver it should happen always but in your case it works sometimes and sometimes not. Such kind of problems are usually USB related problems and usually we can't fix them either because usually such problems depend on your particular USB hardware. See http://en.opensuse.org/SDB:Configuring_Scanners_from_SUSE_LINUX_9.2 in particular "USB Cable Connection and Additional USB Hubs" and "USB Hardware + USB Kernel Modules + hotplug" and "Trouble-Shooting (Debugging)" In any case connet the scanner directly with a short USB cable to the computer. Additionally it may help to use explicitely the slower USB 1 (and not USB 2 which might be too fast for your hardware). Please provide a debug output for exactly one failed attempt as follows: export SANE_DEBUG_DLL=4 export SANE_DEBUG_PLUSTEK=128 export SANE_DEBUG_SANEI_USB=128 scanimage -d Device -T &>/tmp/scanimage.debug bzip2 /tmp/scanimage.debug Replace "Device" either with "plustek" or with a complete SANE device like "plustek:libusb:123:456" (see the "scanimage -L" output). and attach /tmp/scanimage.debug.bz2 to this bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=210172 jsmeix@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |mark_1@gmx.de ------- Comment #2 from jsmeix@novell.com 2007-01-17 01:40 MST ------- See comment #1. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=210172 mark_1@gmx.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|mark_1@gmx.de | ------- Comment #3 from mark_1@gmx.de 2007-01-20 14:14 MST ------- Created an attachment (id=114057) --> (https://bugzilla.novell.com/attachment.cgi?id=114057&action=view) debug output Thanks for your answer. Here's the output. The scanner was connected directly using the cable provided by the manufacturer. The output was generated on SUSE 10.2 with sane 1.0.18-34. You could be right that it's an usb related problem, because i also sometimes observed problems using an usb storage device. It seemed to stall. The "connection" to that device broke down while copying many large files, so i had to unplug and replug it. But i don't understand why the older sane package works. However... :) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=210172 jsmeix@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |mark_1@gmx.de ------- Comment #4 from jsmeix@novell.com 2007-01-22 02:16 MST ------- In attachment #114057 you will see (near the end) various USB related problems: --------------------------------------------------------------------------- [plustek] Available and supported devices: [plustek] Device: >libusb:001:010< - 0x04a9x0x220d .. [sanei_usb] sanei_usb_open: trying to open device `libusb:001:010' .. [sanei_usb] sanei_usb_open: opened usb device `libusb:001:010' (*dn=0) . . . A lot of succesful IO happens but then it starts to break down: . . . [sanei_usb] sanei_usb_read_bulk: trying to read 1 bytes [sanei_usb] sanei_usb_read_bulk: read returned EOF [plustek] UIO error .. USB error: error submitting URB: No such device [sanei_usb] sanei_usb_write_bulk: write failed: No such device .. USB error: could not clear/halt ep 3: No such device [plustek] Scanner not ready!!! .. FAIL Error: Error during device I/O .. USB error: failed to open /dev/bus/usb/001/010: No such file or directory --------------------------------------------------------------------------- First it works to do some IO via the USB device 001:010 but then it breaks down and the device has gone away. My Canon Lide 30 worked and works well with the plustek driver for all Suse Linux versions since 9.0 and for openSUSE 10.2. Therefore I assume it is no problem in the driver but a lower-level USB related problem. Did you use the older sane package on openSUSE 10.2 and then it works o.k. for you or do you mean that you used the older sane package on an older Suse Linux version? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=210172 ------- Comment #5 from mark_1@gmx.de 2007-01-23 01:13 MST ------- When i first reported the problem i used SUSE 10.1 and it worked well with the older sane package from SUSE 10.0. Now i use SUSE 10.2 and it also works well with the old package. So, for me there is no problem. The original packages that came with 10.1 and 10.2 both do not work in my case. But you wrote "you will see (near the end) various USB related problems:". If it is near the end, it is not surprising, because i had to unplug the scanner for scanimage to finish. Ctrl-C did not work and i did not want to kill the process. Sorry, i forgot to write this in my last comment. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=210172 jsmeix@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|mark_1@gmx.de | ------- Comment #6 from jsmeix@novell.com 2007-01-23 02:48 MST ------- So it simply hangs up somehow for you. In your debug log there are zillions of same messages like ------------------------------------------------------------------------- [sanei_usb] sanei_usb_read_bulk: trying to read 1 bytes [sanei_usb] 0000: 02 ................ [sanei_usb] sanei_usb_read_bulk: wanted 1 bytes, got 1 bytes [sanei_usb] sanei_usb_write_bulk: trying to write 4 bytes [sanei_usb] 0000: 01 07 00 01 ................ [sanei_usb] sanei_usb_write_bulk: wanted 4 bytes, wrote 4 bytes ------------------------------------------------------------------------- before finally the "read returned EOF" message which seems to be the moment when you unplugged it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c7 Andreas Schallenberg <andreas.schallenberg@eurobild.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andreas.schallenberg@eurobild.com --- Comment #7 from Andreas Schallenberg <andreas.schallenberg@eurobild.com> 2007-08-07 14:17:01 MST --- I got a very similar behaviour with a CanoScan LiDE 50. The problem seems to apply to quite a lot of USB scanners. The sane bug-tracking system has this entry for the issue: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/85488 It is exposed due to kernels having USB_SUSPEND option being set. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c8 Johannes Meixner <jsmeix@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #8 from Johannes Meixner <jsmeix@novell.com> 2007-08-08 01:17:30 MST --- Very many thanks for comment #7! (I would have searched for ages until I may have found this reason.) And this is the matching explanation on the sane-devel mailing list: http://lists.alioth.debian.org/pipermail/sane-devel/2007-July/019680.html In openSUSE 10.3 beta1 the issue should be solved in the sane-backends package via a udev rule file /etc/udev/rules.d/55-libsane.rules which disables the USB autosuspend feature as described in the above mail on the sane-devel mailing list. Therefore I close the report as fixed (in openSUSE 10.3). For versions before openSUSE 10.3 beta1 you may create a udev rule file like (see "man udev" for details) but I didn't test it: ----------------------------------------------------------------------- ACTION!="add", GOTO="libsane_rules_end" # Canon CanoScan N670U / N676U / LiDE20 SYSFS{idVendor}=="04a9", SYSFS{idProduct}=="220d", MODE="0664", GROUP="lp", ENV{libsane_matched}="yes" # Canon CanoScan LiDE 35 / LiDE 40 / LiDE 50 SYSFS{idVendor}=="04a9", SYSFS{idProduct}=="2213", MODE="0664", GROUP="lp", ENV{libsane_matched}="yes" # The following rule will disable USB autosuspend for the device ENV{libsane_matched}=="yes", RUN+="/bin/sh -c 'test -e /sys/$env{DEVPATH}/power/level && echo on > /sys/$env{DEVPATH}/power/level'" LABEL="libsane_rules_end" ----------------------------------------------------------------------- Long lines are wrapped here at " GROUP" and " RUN" and " &&" in the real file all settings must be on one line. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c9 Andreas Schallenberg <andreas.schallenberg@eurobild.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #9 from Andreas Schallenberg <andreas.schallenberg@eurobild.com> 2007-08-12 15:33:48 MST --- Unfortunately this does not solve the problem here. I just made a fresh install of 10.3 Beta 1 and it still does not work correctly. The slider freezes during scan and the motor makes a screaming noise. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c10 --- Comment #10 from Andreas Schallenberg <andreas.schallenberg@eurobild.com> 2007-08-12 18:36:37 MST --- I tried to build a new kernel on my 10.2 system without USB_SUSPEND. When making cloneconfig I noticed that the current kernel was already built without USB_SUSPEND. However, I can reproduce the bug with the current kernel, too. So there seems to be another reason for this behaviour here. (The current kernel here is: Linux noname 2.6.18.8-0.5-default #1 SMP Fri Jun 22 12:17:53 UTC 2007 i686 athlon i386 GNU/Linux It is a SUSE package.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c11 --- Comment #11 from Johannes Meixner <jsmeix@novell.com> 2007-08-15 04:31:15 MST --- I think it is perhaps no bug in the SANE driver because for the Canon CanoScan LiDE 20 the driver "plustek" is used (my LiDE 30 worked and works well with the "plustek" driver) but for the LiDE 50 the driver "genesys" is used. It looks more like a bug in general USB stuff, perhaps in libusb or whatever kernel related USB, perhaps in SANE's general USB I/O functions. I guess it is the latter because of comment #5. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c12 --- Comment #12 from Andreas Schallenberg <andreas.schallenberg@eurobild.com> 2007-08-26 15:04:29 MST --- Made some additional tests: My computer has a nforce-2 mainboard and an extra USB PCI card with an ALi chipset. The bug is reproducible with USB ports driven by each of the chips. The I upgraded the test partition to 10.3 Beta-2: Bug still there. Then I looked aside and tested the current alpha release of Kubuntu (Gutsy). The scanner works there. Maybe the Ubuntu/Debian guys know more about this topic? (The kernel is named 2.6.22-generic) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c13 --- Comment #13 from Mark Blank <mark_1@gmx.de> 2007-08-27 02:43:27 MST --- All my comments before refer to a Sony VAIO notebook (PCG-FX202). Now I had the possibility to test the LiDE 20 with another system (desktop, 10.2, ASUS mainboard): same problem when using sane 1.0.18-34 (suse 10.2) or 1.0.17-18 (suse 10.1). But again using sane 1.0.15-20 or 1.0.15-20-2 from 10.0 helps and everything works fine. Because I noticed that about two different systems, I think it works not only for me but the bug must be somewhere between sane 1.0.15-20-2 and 1.0.17-18. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c14 --- Comment #14 from Mark Blank <mark_1@gmx.de> 2007-08-27 02:50:38 MST --- to comment #13: "...sane 1.0.18-34 (suse 10.2) or 1.0.17-18 (suse 10.1)." means these are the packages that came with suse 10.2 and 10.1 respectively. All testing with the desktop system of comment #13 was done using suse 10.2. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c15 --- Comment #15 from Andreas Schallenberg <andreas.schallenberg@eurobild.com> 2007-09-10 10:32:49 MST --- The workaround using the 1.0.15 package from SUSE 10.0 does not work for me. It has no support for the LiDE 50 (genesys-backend). Two additional observations: * The scanner does not work (using Windows!) with my ALi PCI card, but works well with the on-board (nforce2) USB ports. So, there seems to be something wrong there, too. * I just tried the sane backend CVS snapshot from 2007-09-08 and it didn't help (tested with onboard-usb port). There should be a fix in CVS (apparently for another issue): http://alioth.debian.org/tracker/?func=detail&group_id=30186 (cont'd) &aid=304154&atid=410366 So I guess there is something other than USB_SUSPEND involved here. Does it make sense to test a specific kernel version? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c16 --- Comment #16 from Andreas Schallenberg <andreas.schallenberg@eurobild.com> 2007-09-16 03:17:39 MST --- Just tested SUSE 10.3 Beta 3, scanner doesn't work. Added my scanner to /usr/src/linux/drivers/usb/core/quirks.c, (04a9:2213 Canon, Inc. LiDE 50/LiDE 35), recompiled it: works! I'm going to add this information to the sane bug #85488. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c17 Johannes Meixner <jsmeix@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |andreas.schallenberg@eurobild.com --- Comment #17 from Johannes Meixner <jsmeix@novell.com> 2007-09-18 07:25:45 MST --- According to my understanding of quirks.c (I am no kernel expert) it is a autosuspend issue or am I wrong? If yes, I wonder why /etc/udev/rules.d/55-libsane.rules doesn't work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c18 Johannes Meixner <jsmeix@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Major --- Comment #18 from Johannes Meixner <jsmeix@novell.com> 2007-09-18 07:34:59 MST --- /etc/udev/rules.d/55-libsane.rules cannot work because it does .. RUN+="/bin/sh -c 'test -e /sys/$env{DEVPATH}/power/level \ && echo on > /sys/$env{DEVPATH}/power/level'" where $env{DEVPATH} evaluates to something like /devices/pci0000:00/0000:00:06.0/0000:02:00.1/usb2/2-1 But on my openSUSE 10.3 beta2 system running the 2.6.22.3-7-default kernel, there is no file /sys/devices/pci0000:00/0000:00:06.0/0000:02:00.1/usb2/2-1/power/level so that the 'test -e /sys/$env{DEVPATH}/power/level' fails. Obviously the above is not the right method to disable USB autosuspend. I asked a kernel guru what the right way is and made this a MAJOR bug because many scanners will not work well if USB autosuspend is not disabled. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172 Johannes Meixner <jsmeix@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Hotplug |Hotplug OS/Version|SuSE Linux 10.1 |openSUSE 10.3 Product|SUSE Linux 10.1 |openSUSE 10.3 Platform|i686 |x86-64 Summary|Scanner: Canon CanoScan LiDE 20 USB jams with |disable USB autosuspend doesn't work |SANE-1.0.17-18 | Version|Final |Beta 2 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c19 Johannes Meixner <jsmeix@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Minor Summary|disable USB autosuspend doesn't work |disable USB autosuspend may not work in any case --- Comment #19 from Johannes Meixner <jsmeix@novell.com> 2007-09-18 08:28:45 MST --- The kernel guru replied: ----------------------------------------------------------------------- This is the correct way, precisely because it does nothing if the file does not exist. These attributes exist only if the kernel supports autosuspend. On my system: oneukum@oenone:~> zcat /proc/config.gz | grep SUSP CONFIG_SOFTWARE_SUSPEND=y CONFIG_SUSPEND_SMP=y # CONFIG_USB_SUSPEND is not set oneukum@oenone:~> uname -r 2.6.22.3-7-default ----------------------------------------------------------------------- It is exactly the same on my openSUSE 10.3 beta2 x86_64 test system: caps:~ # zcat /proc/config.gz | grep SUSP CONFIG_SOFTWARE_SUSPEND=y CONFIG_SUSPEND_SMP=y # CONFIG_USB_SUSPEND is not set caps:~ # uname -r 2.6.22.3-7-default I.e. our default kernel does not do any USB autosuspend. Therefore USB autosuspend it cannot be disabled and therefore I never had this problem on my systems. I reduce the bug severity to MINOR. Did you use a self-compiled kernel? What results the above commands on your systems? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c20 --- Comment #20 from Andreas Schallenberg <andreas.schallenberg@eurobild.com> 2007-09-18 16:25:50 MST --- To comment 17: Yes, I modified the table for autosuspend quirks. To comment 19: Ok, I wiped my test partition and re-installed Beta 3 from scratch. The requested commands produce this: zcat /proc/config.gz | grep SUSP CONFIG_SOFTWARE_SUSPEND=y CONFIG_SUSPEND_SMP=y # CONFIG_APM_IGNORE_USER_SUSPEND is not set CONFIG_X86_GX_SUSPMOD=m # CONFIG_USB_SUSPEND is not set uname -r 2.6.22.5-10-bigsmp The scanner did not work. Then I installed gcc, kernel sources etc. and built a new kernel (without doing any source code changes): CONFIG_SOFTWARE_SUSPEND=y CONFIG_SUSPEND_SMP=y # CONFIG_APM_IGNORE_USER_SUSPEND is not set CONFIG_X86_GX_SUSPMOD=m # CONFIG_USB_SUSPEND is not set uname -r 2.6.22.5-10-ASc1 The scanner didn't work either. Then I made the change to quirks.c again and built a second kernel. To my big suprise, the scanner didn't work now! So it must have been "luck" (???) to get a working scan this way in the first time. In all cases, the slider moves a bit and freezes then, making this screaming noise. I guessed it was the time where the suspend was activated but obviously I must have been wrong...? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c21 Johannes Meixner <jsmeix@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|andreas.schallenberg@eurobild.com | Summary|disable USB autosuspend may not work in any case|sometimes USB scanners jam since sane-backends > | |1.0.15 --- Comment #21 from Johannes Meixner <jsmeix@novell.com> 2007-09-19 00:35:26 MST --- It seems we are back at the beginning: - It is no USB autosuspend problem. (If yes it would have been strange why it can be solved by using an older SANE version.) - It happens only occasionally. - It happens for different SANE backends (see comment #5). - Neither I nor the people of the SANE project can reproduce it nor have an idea what the real cause might be. Currently I am at my wits end but I will keep the bug open for further comments and/or ideas. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c22 --- Comment #22 from Johannes Meixner <jsmeix@novell.com> 2007-09-19 00:43:11 MST --- A typo in comment #21, I meant: - It happens for different SANE backends (see comment #11). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c23 Fibonacci Prower <fibonacci.prower@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fibonacci.prower@gmail.com --- Comment #23 from Fibonacci Prower <fibonacci.prower@gmail.com> 2007-10-09 03:27:25 MST --- I can confirm this happens on both Ubuntu 7.04 and Fedora Core 5, using a CanoScan LiDE 20. On Fedora Core, it didn't happen "only occasionally" - the slider froze on init with the lamps on and making a screaming noise 100% of the time whenever I tried to scan anything, whether I used scanimage or the GUIs. Unplugging the scanner was the only way to, at least, end the noise. I reported it to sane-devel, but my message was ignored. On Ubuntu the success rate is about 50% (i.e. it jams every other scan) using scanimage only, since XSane simply refuses to scan anything (though the jamming is absent when using the GUIs). I have noticed there are certain operations which appear to drastically reduce the success rate: obtaining a preview-quality scan (never works), scanning with a resolution less than 100dpi (rarely works), scanning a large area (where "large" is close to or greater than 150×250 mm; the larger it is, the smaller are the chances of success), and scanning many images in rapid succession (will quickly fail). Not a single case of jamming was observed in either scenario when using the 1.0.15 backends. Furthermore, using an old Knoppix LiveCD which includes those very backends on the same machine in which Fedora and Ubuntu were tested, the scanner works flawlessly. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c24 Mark Blank <mark_1@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Beta 2 |Final --- Comment #24 from Mark Blank <mark_1@gmx.de> 2007-10-15 08:59:03 MST --- Recently I updated my system to openSUSE 10.3. The sane package that came with it (sane-backends-1.0.18-81) did not work with my CanoScan LiDE 20 (ugly noise). The workaround I previously described did also not work because the old sane package (SUSE 10.0) is no longer usable. The sane mailing list shows several reports of the bug I reported here and there it was said to be fixed. So I tried the SUSE factory version (sane-backends-1.0.18-86) but it had the old bug. Today I compiled the cvs version of sane and everything works fine! It really seems to be the plustek driver. I also successfully tested the following: I copied the source of the old plustek backend (version 48-2, http://www.gjaeger.de/scanner/plustek/) into the source of sane-backends-1.0.18.tar.gz and build it. And it also worked fine. (Without this "patch" sane-backends-1.0.18.tar.gz produced the same ugly noise as described above). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c25 --- Comment #25 from Johannes Meixner <jsmeix@novell.com> 2007-10-16 01:50:00 MST --- Mark, very many thanks for your detailed analysis! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c26 --- Comment #26 from Johannes Meixner <jsmeix@novell.com> 2007-10-17 02:33:59 MST --- I will try to provide the old plustek backend or the new one from SANE CVS in our current sane-backends version via our openSUSE build service. This should solve the "plustek" driver issue (but the "genesys" driver issue is still open). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c27 --- Comment #27 from Johannes Meixner <jsmeix@novell.com> 2007-10-25 03:52:20 MST --- I provide for testing sane-backends CVS snapshot dated 2007 Oct 24 for openSUSE 10.2 and openSUSE 10.3 and for the openSUSE development version openSUSE "factory" for 32-bit Intel compatible (i586) and 64-bit AMD (x86_64) via the openSUSE build service at http://software.opensuse.org/download/home:/jsmeix/ The packages are * only for testing * without any guarantee or warranty * without any support As an extreme example, this means that if your complete computer center crashes because of these packages, it is only your problem. In particular note that this is a CVS snapshot which means that there could be whatever unstable or conflicting stuff in the code which may result arbitrary unexpected effects. Nevertheless, I am very interested in your feedback because I don't have a CanoScan LiDE 20 to test it on my own and my CanoScan LiDE 30 works and worked well all the time in particular also with this CVS snapshot. Of course I am also interested if there are other regressions with other scanners or other drivers but then please file separated bug reports and make it obvious which package, which package version, which hardware architecture and which openSUSE version you are talking about, e.g.: "Feedback regarding sane-backends-2007.10.24cvs-66.1.i586.rpm from http://software.opensuse.org/download/home:/jsmeix/ for openSUSE 10.3 used on 64-bit AMD hardware." Ideally provide also the "rpm -q --changelog sane-backends | head" output to make it unambiguous which exact package release you have. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c28 --- Comment #28 from Mark Blank <mark_1@gmx.de> 2007-10-25 04:58:29 MST --- Feedback regarding sane-backends-2007.10.24cvs-66.1.i586.rpm from http://software.opensuse.org/download/home:/jsmeix/ for openSUSE 10.3 (2.6.22.9-0.4-default) used on 32-bit AMD hardware: Works well with CanoScan LiDE 20. No problems so far. Thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c29 Johannes Meixner <jsmeix@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |andreas.schallenberg@eurobild.com --- Comment #29 from Johannes Meixner <jsmeix@novell.com> 2007-10-25 05:32:29 MST --- Regarding the CanoScan LiDE 50 / "genesys" driver: Andreas, does the sane-backends CVS snapshot (see comment #27) work for you? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c30 --- Comment #30 from Andreas Schallenberg <andreas.schallenberg@eurobild.com> 2007-10-26 11:59:58 MST --- Created an attachment (id=180867) --> (https://bugzilla.novell.com/attachment.cgi?id=180867) Debug output of genesys backend Unfortunately this does not solve my problem. I attached a genesys backend log with export SANE_DEBUG_GENESYS=255 # rpmquery -a | grep sane sane-frontends-1.0.14-56.4 sane-backends-2007.10.24cvs-66.1 xsane-0.994-3.3 python-imaging-sane-1.1.5-43 # rpm -q --changelog sane-backends | head * Do Okt 25 2007 - jsmeix@suse.de - Updated to sane-backends CVS snapshot dated 2007 Oct 24: The following patches are removed because the issues are now fixed in the source: fix-ambiguous-post-pre-increment.patch, fujitsu-disable-hw_ink_remain.patch, and replace-HZ-by-sysconf_SC_CLK_TCK.patch. In fix-buffer-overflow.patch the entry regarding backend/epson.c is removed because the issue is now fixed in the source. - Removed the source file libsane.rules.CVS-2007-07-29.using-lp because now create_hal_global_fdi_from_libsane.rules can use Just to make sure I didn't do any silly things here: I had to configure the scanner with yast again. Yast automatically installed the "sane" package. After configure, I removed it manually (rpm -e) again and re-installed your three packages from here: http://software.opensuse.org/download/home:/jsmeix/ Then I used "xsane" for the test. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172 Johannes Meixner <jsmeix@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|andreas.schallenberg@eurobild.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c31 Heinz Altschul <heinz.altschul@bluewin.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |heinz.altschul@bluewin.ch --- Comment #31 from Heinz Altschul <heinz.altschul@bluewin.ch> 2007-11-01 12:17:51 MST --- Now it works fine with my Printer/Scanner/Cardreader Epson Stylus Photo RX700 Files: iscan-free 1.17.0.1-1 sane-backends 2007.10.24cvs-66.1.x86_64.rpm /etc/udev/rules.d/libsane.rules adjusted for the scanner. scanimage -L ---> ok kooka ---> ok xsane ---> ok (rem. with Linux 10.2 there are no problems) thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c32 --- Comment #32 from Fibonacci Prower <fibonacci.prower@gmail.com> 2007-11-03 22:33:41 MST --- I can confirm that the CVS backends from 24th of October, 2007, work fine with my CanoScan LiDE 20. As a side note, they appear to work even *better* than the last known working backends - i.e. 1.0.15. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c33 Johannes Meixner <jsmeix@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |heinz.altschul@bluewin.ch --- Comment #33 from Johannes Meixner <jsmeix@novell.com> 2007-11-06 02:49:03 MST --- Regarding comment #31: What exactly did you do in /etc/udev/rules.d/libsane.rules I.e. what must I do so that the Epson Stylus Photo RX700 works out of the bow? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c34 --- Comment #34 from Heinz Altschul <heinz.altschul@bluewin.ch> 2007-11-08 08:15:54 MST --- Regarding comment #33 changes in /etc/udev/rules.d/libsane.rules (line 617) #Epson PM-A900 | Epson Stylus Photo RX700 | Epson RX-700 J deleted the "#" sign at beginning of the line. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c35 --- Comment #35 from Johannes Meixner <jsmeix@novell.com> 2007-11-08 08:38:10 MST --- The line #Epson PM-A900 | Epson Stylus Photo RX700 | Epson RX-700 is intentionally a comment in /etc/udev/rules.d/55-libsane.rules because it is not a udev rule. The next line is the actual udev rule. You introduced an error in /etc/udev/rules.d/55-libsane.rules and I wonder why it works for you at all. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c36 --- Comment #36 from Heinz Altschul <heinz.altschul@bluewin.ch> 2007-11-09 02:35:52 MST --- Regarding comment 35 You are right. J put the comment sign "#" in on the old place and the scanner still works fine. sorry! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172 Johannes Meixner <jsmeix@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|heinz.altschul@bluewin.ch | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172#c37 --- Comment #37 from Johannes Meixner <jsmeix@novell.com> 2007-11-20 04:54:09 MST --- For the fun ;-) Right now my CanoScan LiDE 30 which worked well all the time (also with sane-backends-2007.10.24cvs) started to make ugly noise. I guess it is just the usual USB crap if it happens or not. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172 User nospam2@vajira.co.uk added comment https://bugzilla.novell.com/show_bug.cgi?id=210172#c38 Mike Shaw <nospam2@vajira.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nospam2@vajira.co.uk --- Comment #38 from Mike Shaw <nospam2@vajira.co.uk> 2008-02-08 06:22:12 MST --- I seem to be suffering from this bug too. In using a canon n670u which starts scanning ok but after about 3cm starts making a horrible noise at which point I pull out the USB cable. The symptoms are exactly like people describe here: http://lists.opensuse.org/opensuse-amd64/2...0/msg00011.html It is not mechanical. If I reboot to windows it works to perfection. Nor did I have problems with suse 10.0 If you would like any specific details of my setup please let me know (you may have to explain to me how to give them). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=210172#c39 --- Comment #39 from Johannes Meixner <jsmeix@novell.com> 2008-02-28 12:00:52 MST --- I provide for testing sane-backends version 1.0.19 for openSUSE 10.2 and openSUSE 10.3 and for the openSUSE development version openSUSE "factory" for 32-bit Intel compatible (i586) and 64-bit AMD (x86_64) via the openSUSE build service at http://software.opensuse.org/download/home:/jsmeix/ The packages are * only for testing * without any guarantee or warranty * without any support As an extreme example, this means that if your complete computer center crashes because of these packages, it is only your problem. Nevertheless, I am very interested in your feedback. In particular my CanoScan LiDE 30 works again well with sane-backends version 1.0.19 (see comment #37). Of course I am also interested if there are other issues with other scanners or other drivers but then please file separated bug reports and make it obvious which package, which package version, which hardware architecture and which openSUSE version you are talking about, e.g.: "Feedback regarding sane-backends-1.0.19-128.1.i586.rpm from http://software.opensuse.org/download/home:/jsmeix/ for openSUSE 10.3 used on 64-bit AMD hardware." Ideally provide also the "rpm -q --changelog sane-backends | head" output to make it unambiguous which exact package release you have. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=210172 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=210172#c40 Johannes Meixner <jsmeix@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #40 from Johannes Meixner <jsmeix@novell.com> 2008-03-19 11:34:05 MST --- It seems the problem is more or less solved since sane-backends version 1.0.19. Therefore I close this bug now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com