https://bugzilla.novell.com/show_bug.cgi?id=470959 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=470959#c1 Johannes Meixner <jsmeix@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #1 from Johannes Meixner <jsmeix@novell.com> 2009-01-30 06:46:46 MST --- I assume it does not only happen with xscanimage but alos with xsane and scanimage so that it is a general device I/O issue. In the past any "error during device I/O" has always been a lower-level USB issue where I cannot help at all so that I close it as "wontfix" which actually means "cantfix". (Or I could close it with "worksforme" because for me it works - but I don't have your model.) For debugging have a look at 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)" Setting the SANE_DEBUG_HPAIO environment variable will display the following messages to stderr. SANE_DEBUG_HPAIO=2 (error messages) SANE_DEBUG_HPAIO=6 (error messages + device info) SANE_DEBUG_HPAIO=8 (error messages + device info + sane api calls) Also use "dmesg" to check for lower level USB errors. What might help: Often it helps to 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) via unloading/loading appropriate kernel module(s). -- 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.