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 changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #1 from Johannes Meixner 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.

https://bugzilla.novell.com/show_bug.cgi?id=470959 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=470959#c3 --- Comment #3 from Johannes Meixner 2009-01-30 07:47:51 MST --- When the other "devices" (printer => mainly output, cardreader => mainly input when reading and mainy output when writing) work correctly it looks more like a possible bug in the scanner driver. Feel free to reopen this bug when you think I should also have a look but probably the very best is to report it directly upstream because you could answer their questions much better than I could because I cannot reproduce it. Please go to http://hplipopensource.com/hplip-web/support.html and follow the instructions there (in particular provide a "hp-check -t" output). Many 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=470959 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=470959#c5 --- Comment #5 from Johannes Meixner 2009-02-03 02:16:46 MST --- Argl! How confusing and misleading the system's messages are! In comment #0 there is in /var/log/messages -------------------------------------------------------------- deviceuri=hp:/usb/Officejet_6300_series?serial=CN69DCH2GW04M4 -------------------------------------------------------------- which is a hp:/... DeviceURI which I expected to see. In the hp-check.log in https://answers.launchpad.net/hplip/+question/59235 there is near the end ---------------------------------------------------------------- Checking output of 'scanimage -L'... device `hpaio:/usb/Officejet_6300_series?serial=CN69DCH2GW04M4' is a Hewlett-Packard Officejet_6300_series all-in-one -------------------------------------------------------------- which also look perfectly correct but actually one has to additionally carefully check in hp-check.log for ------------------------------------------------------------ INSTALLED CUPS PRINTER QUEUES ... warning: No queues found. ------------------------------------------------------------ which indicates that there is actually no hp:/... DeviceURI queue set up. I learned a lot here and perhaps I can somehow use it in yast2-printer and in yast2-scanner (e.g. add a test in yast2-scanner to check for a hp:/... DeviceURI queue). -- 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=470959 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=470959#c7 --- Comment #7 from Johannes Meixner 2009-02-03 03:21:15 MST --- Currently I have no idea what the root cause might have been. Only some guesses: "old printers.conf"? You do re-start the cupsd each time after you manually changed any of its config files? Compare http://en.opensuse.org/SDB:CUPS_in_a_Nutshell ------------------------------------------------------------------------ General information on the command-line tools: .. Do not edit the configuration files in /etc/cups/ manually if suitable command-line tools are available for this purpose. Reason: The configuration files are not reloaded for every print job. Rather, cupsd keeps much of the information in the main memory and writes information back to the configuration files whenever needed. .. Never copy configuration files from other systems to your system unless you know exactly what you are doing. ------------------------------------------------------------------------ A guess regarding HPLIP: Whenever you launch a desktop system (KDE or Gnome) /etc/xdg/autostart/hplip-systray.desktop starts /usr/bin/hp-systray which runs daemon-like in the background and perhaps this tool had some old/outdated data so that scanner access failed for you? Run ps auxw | egrep 'hp|python' to see hp-systray processes. Since HPLIP 2.8.4 the system daemon hpssd has been replaced with hp-systray that loads as a user startup item in the system tray in each user's desktop environment. Another guess regarding HPLIP: When you run in a non-POSIX and non-UTF8 locale, HPLIP fails to "see" its hp:/... CUPS queues. To see this, have a non-POSIX and non-UTF8 locale e.g. via export LANG=en_GB.iso885915; export LC_ALL=en_GB.iso885915 and then run "hp-toolbox". Perhaps the root cause was whatever locale issue? -- 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=470959 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=470959#c9 --- Comment #9 from Johannes Meixner 2009-02-03 03:45:26 MST --- Now I fully understand the final ultimate root cause of the issue: "Something seems to be somehow a bit messed up sometimes!" ;-) -- 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.