Created attachment 440740 [details] "hp-check -t" log Description of problem: I have HP MFU Photosmart C4100 series which works fine in Fedora 11. After update to Fedora 13 it does not even detected as scanner. BTW sane-find-scanner can see it: $ sane-find-scanner [skip] # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. found USB scanner (vendor=0x03f0 [HP], product=0x5711 [Photosmart C4100 series]) at libusb:001:012 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. [skip] $ scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). Version-Release number of selected component (if applicable): $ rpm -qa 'hp*' '*sane*' libsane-hpaio-3.10.6-1.fc13.i686 hplip-libs-3.10.6-1.fc13.i686 hplip-3.10.6-1.fc13.i686 hplip-common-3.10.6-1.fc13.i686 hplip-gui-3.10.6-1.fc13.i686 xsane-0.997-10.fc13.i686 hpijs-3.10.6-1.fc13.i686 sane-backends-libs-1.0.21-2.fc13.i686 sane-backends-1.0.21-2.fc13.i686 xsane-common-0.997-10.fc13.i686 How reproducible: Always
*** This bug has been marked as a duplicate of bug 622730 ***
I didn't check the versions of packages, sorry, reopening. Please attach the files /etc/sane.d/dll.conf and /etc/sane.d/dll.d/hpaio to this report.
Created attachment 440888 [details] /etc/sane.d/dll.conf
Created attachment 440889 [details] /etc/sane.d/dll.d/hpaio
Is there any progress? Can I help you to resolve this problem?
I'm kill many time on this weekend to find reason... What is very interesting here - it work without any manipulation just after connect on my notebook also with Fedora 13. Both system is up to date (but notebook also have enabled updates-testing repository, but I think it is irrelevant there) I try compare installed components and configs - nothing found interesting. But I think it may be related. After plug in cable in log appeared: Sep 26 23:16:27 x-www kernel: usb 1-1: new high speed USB device using ehci_hcd and address 58 Sep 26 23:16:27 x-www kernel: usb 1-1: New USB device found, idVendor=03f0, idProduct=5711 Sep 26 23:16:27 x-www kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Sep 26 23:16:27 x-www kernel: usb 1-1: Product: Photosmart C4100 series Sep 26 23:16:27 x-www kernel: usb 1-1: Manufacturer: HP Sep 26 23:16:27 x-www kernel: usb 1-1: SerialNumber: MY67AC10PM04J7 Sep 26 23:16:27 x-www kernel: usblp0: USB Bidirectional printer dev 58 if 1 alt 0 proto 2 vid 0x03F0 pid 0x5711 Sep 26 23:16:27 x-www kernel: scsi44 : usb-storage 1-1:1.3 Sep 26 23:16:27 x-www udev-configure-printer: invalid or missing IEEE 1284 Device ID Sep 26 23:16:28 x-www kernel: scsi 44:0:0:0: Direct-Access HP Photosmart C4183 1.00 PQ: 0 ANSI: 2 Sep 26 23:16:28 x-www kernel: sd 44:0:0:0: Attached scsi generic sg3 type 0 Sep 26 23:16:28 x-www kernel: sd 44:0:0:0: [sdd] Attached SCSI removable disk Sep 26 23:16:28 x-www hp[7113]: io/hpmud/pp.c 627: unable to read device-id ret=-1 Sep 26 23:16:29 x-www python: io/hpmud/pp.c 627: unable to read device-id ret=-1 Sep 26 23:16:29 x-www udev-configure-printer: Re-enabled printer ipp://localhost:631/printers/HP_PhotoSmart_C4183 Sep 26 23:16:29 x-www udev-configure-printer: Re-enabled printer ipp://localhost:631/printers/HP_PhotoSmart_C4183 Though, device is found, but communication with it is unsuccessful (io/hpmud/pp.c 627: unable to read device-id ret=-1). What I can do with it now? In what side dig?
What does 'SANE_DEBUG_HPAIO=255 scanimage -L' show?
Nothing interesting I think: $ SANE_DEBUG_HPAIO=255 scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages).
Looks like the 'hpaio' device is not even enabled. Here's what I get with no devices connected: $ SANE_DEBUG_HPAIO=255 scanimage -L [sanei_debug] Setting debug level of hpaio to 255. [hpaio] sane_hpaio_init(): scan/sane/hpaio.c 1593 [hpaio] sane_hpaio_get_devices(local=0): scan/sane/hpaio.c 1612 No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). [hpaio] sane_hpaio_exit(): scan/sane/hpaio.c 1606 How about this?: SANE_DEBUG_DLL=255 scanimage -L
Why is not enabled? It already listed in USB: $ lsusb Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 006: ID 03f0:5711 Hewlett-Packard PhotoSmart C4100 series Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub But still does not in HPIO: $ SANE_DEBUG_DLL=255 scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages).
Er... you don't get any debug output at all from the dll backend, even? Are you using a different shell than bash, perhaps? Try this: SANE_DEBUG_DLL=255 export SANE_DEBUG_DLL scanimage -L You should get loads of output like this: [dll] load: searching backend `epson2' in `/usr/lib64/sane' [dll] load: trying to load `/usr/lib64/sane/libsane-epson2.so.1' [dll] load: dlopen()ing `/usr/lib64/sane/libsane-epson2.so.1' [dll] init: initializing backend `epson2' [dll] init: backend `epson2' is version 1.0.124
No, I use bash version 4.1.7. [pasha@x-www temp]$ SANE_DEBUG_DLL=255 [pasha@x-www temp]$ export SANE_DEBUG_DLL [pasha@x-www temp]$ scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages).
Changing component back to sane-backends.
Nils: any idea why we can't get debug information out of scanimage?
Tim: This is really strange... Pavel, Tim: which version of sane-backends do you both have installed?
$ rpm -q sane-backends sane-backends-1.0.21-4.fc13.i686
Hm. I can only guess that "something" (whatever) filters away stderr output. Let's try this a bit differently: SANE_DEBUG_DLL=255 scanimage -L 2>&1 >&2 | tee /tmp/scanimage.out Please run the above and tell us if there is more output, if yes, attach the resulting /tmp/scanimage.out file. Thanks.
Uhm that was a bit excessive, try this instead: SANE_DEBUG_DLL=255 scanimage -L 2>&1 | tee /tmp/scanimage.out
No it is not true: $ SANE_DEBUG_DLL=255 scanimage -L 2>&1 | tee /tmp/scanimage.out No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). [pasha@x-www temp]$ [pasha@x-www temp]$ cat /tmp/scanimage.out No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). I think it happened because your scanner identified and then wirk with it delegated to particular backand. In my case it is not found at all.
If look to strace of scanimage -L run for scanner device it is opened, some information read from it, then it sucessfully closed. Nope. No other actions: getdents(3, /* 4 entries */, 32768) = 64 open("/dev/bus/usb/001/003", O_RDWR) = 4 ioctl(4, USBDEVFS_CONNECTINFO, 0xbfb0ea38) = 0 read(4, "\22\1\0\2\0\0\0@\360\3\21W\0\1\1\2\3\1", 18) = 18 read(4, "\t\2\203\0\4\1\0\300", 8) = 8 read(4, "\1\t\4\0\0\3\377\314\0\0\7\5\1\2\0\2\0\7\5\202\2\0\2\0\7\5\203\3\10\0\7\t"..., 123) = 123 close(4) = 0 open("/dev/bus/usb/001/001", O_RDWR) = -1 EACCES (Permission denied) What is very interesting, lsusb according strace do absolutely the same steps to get USBDEVFS_CONNECTINFO and then print device information at least.
(In reply to comment #19) > I think it happened because your scanner identified and then wirk with it > delegated to particular backand. > > In my case it is not found at all. This is beginning to get weird -- I don't have any scanners connected and to be safe, I retried this on my Rawhide VM (1005 no scanner hardware connected there ;-): --- 8< --- nils@rawhide:~> scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). nils@rawhide:~> scanimage -L 2>&1 | wc -l 5 nils@rawhide:~> SANE_DEBUG_DLL=255 scanimage -L 2>&1 | wc -l 484 --- >8 --- So regardless of your configuration you should at least get these lines at the beginning (version numbers may differ): --- 8< --- [sanei_debug] Setting debug level of dll to 255. [dll] sane_init: SANE dll backend version 1.0.12 from sane-backends 1.0.21 [dll] sane_init/read_dlld: processing /etc/sane.d/dll.d ... [dll] sane_init/read_dlld: done. [dll] sane_init/read_config: reading dll.conf ... --- >8 --- I'm at a loss why you don't see anything... Can you try this out with a different user, on a different machine?
On different machine, my previous notebook with clear Fedora 14 installation, not upgraded it was worked out of the box. On this machine I tried from two users - one limited and from root. If you want, I can provide ssh access on that machine. If it helps, please contact me and sent public rsa key,
(In reply to comment #22) > On different machine, my previous notebook with clear Fedora 14 installation, > not upgraded it was worked out of the box. Do you mean the scanner works there, or the debugging output shows? > On this machine I tried from two users - one limited and from root. > > If you want, I can provide ssh access on that machine. If it helps, please > contact me and sent public rsa key, Oh, I'd like to avoid that unless we've run out of other options. In order to have something comparable (we're trying to find out why debugging output doesn't work right now, apparently this is not related to your scanner), please detach your scanner from the machine, then run these commands as root: strace SANE_DEBUG_DLL=255 strace -o /tmp/scanimage-strace.out scanimage -L bzip2 /tmp/scanimage-strace.out Afterwards, please attach the resulting file /tmp/scanimage-strace.out. Thanks.
Created attachment 462911 [details] scanimage-strace.out.bz2 (In reply to comment #23) > (In reply to comment #22) > > On different machine, my previous notebook with clear Fedora 14 installation, > > not upgraded it was worked out of the box. > > Do you mean the scanner works there, or the debugging output shows? Scanner work out of the box. > In order to have something comparable (we're trying to find out why debugging > output doesn't work right now, apparently this is not related to your scanner), > please detach your scanner from the machine, then run these commands as root: > > strace SANE_DEBUG_DLL=255 strace -o /tmp/scanimage-strace.out scanimage -L > bzip2 /tmp/scanimage-strace.out > > Afterwards, please attach the resulting file /tmp/scanimage-strace.out. Thanks. I think you mean SANE_DEBUG_DLL=255 strace -o /tmp/scanimage-strace.out scanimage -L because. This output attached.
I am also experiencing the same issue with Fedora 14 (upgraded to latest version as of this past weekend): [myusbpc@i5dell Downloads]$ sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. found USB scanner (vendor=0x03f0 [HP], product=0x5711 [Photosmart C4100 series]) at libusb:002:006 found USB scanner (vendor=0x8086, product=0x0188) at libusb:002:005 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. # You may want to run this program as root to find all devices. Once you # found the scanner devices, be sure to adjust access permissions as # necessary. [myusbpc@i5dell Downloads]$ scanimage -L device `v4l:/dev/video0' is a Noname Laptop_Integrated_Webcam_1.3M virtual device [myusbpc@i5dell Downloads]$ scanimage -L device `v4l:/dev/video0' is a Noname Laptop_Integrated_Webcam_1.3M virtual device [myusbpc@i5dell Downloads]$ A ---------- I can print to the HP C4100 but it won't scan ---------- It used to work with Fedora 13 without any issues. Thanks, ---Daniel
[myusbpc@i5dell Downloads]$ rpm -qa 'hp*' '*sane*' sane-backends-libs-1.0.21-5.fc14.i686 hplip-common-3.10.9-14.fc14.i686 hplip-libs-3.10.9-14.fc14.i686 sane-backends-1.0.21-5.fc14.i686 hpijs-3.10.9-14.fc14.i686 sane-backends-libs-gphoto2-1.0.21-5.fc14.i686
You don't have libsane-hpaio installed.
I have: $ rpm -q libsane-hpaio libsane-hpaio-3.10.9-14.fc13.i686
Pavel, what does 'rpm -V sane-backends' say?
$ rpm -V sane-backends S.5....T. c /etc/sane.d/dll.conf
A new upstream version with many bugfixes and enhancements has been released. Please check whether debugging works with this updated package: https://admin.fedoraproject.org/updates/sane-backends-1.0.22-1.fc13
Ok, I've install it: $ rpm -q sane-backends sane-backends-1.0.22-1.fc14.i686 Nothing changed for me at all: $ sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. found USB scanner (vendor=0x03f0, product=0x5711) at libusb:001:004 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. # You may want to run this program as root to find all devices. Once you # found the scanner devices, be sure to adjust access permissions as # necessary $ scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). $ SANE_DEBUG_DLL=255 scanimage -L 2>&1 No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages).
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
It seems I've dropped this, sorry. I've just rechecked that setting SANE_DEBUG_DLL=255 in the environment lets "scanimage -L" spew out lots of debugging information. Would you please recheck this with current updates? I still don't have a clue why you don't see any debugging output, but would you run the following alternative commands and post their output? Thanks. which scanimage env -i SANE_DEBUG_DLL=255 scanimage -L
I also don't understand what happened. [pasha@x-www ~]$ which scanimage /usr/bin/scanimage [pasha@x-www ~]$ env -i SANE_DEBUG_DLL=255 scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages).
Something seems to throw away stderr here, I am totally puzzled about this. Pavel, can you please describe exactly what the environment is that you use: - Which shell do you use? Do you have any non-standard bashrc/profile snippets in use? - Are you logged in via a graphical terminal (which one), SSH, or at a virtual console? - Do you see this only as a normal user, or also as "root"? Have you tried this from a different, freshly created user?
Nils, sorry for the delay. I use bash as by shell. $ rpm -q bash bash-4.1.7-3.fc14.i686 Sometimes SSH, sometimes graphical terminal emulator. In most cases it is Terminal, Konsole, tilda or yakuake. I think it have no mater there. Try as root too: # env -i SANE_DEBUG_DLL=255 scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). Can new created user change anything??
Hm. Probably a stupid question, but I need to check if this is specific to sane or not: Do you get anything on stderr, I mean any error message from other commands? What does running the following give? echo line one; echo line two >&2; echo line three
Another thing to check: Please switch SELinux into permissive mode and check if this command finally gives you any debugging output: SANE_DEBUG_DLL=255 scanimage -L
>Hm. Probably a stupid question, but I need to check if this is specific to sane or not We should exclude all possible variants :) $ echo line one; echo line two >&2; echo line three line one line two line three There no SELinux on that machine enabled: $ getenforce Disabled
It seems as if by concentrating on the environment variables I've been up a blind alley. Anyway, the following line from the strace output above in comment #24 indicates that you don't really use the packaged SANE library but a different (probably self-built) one: [...] open("/usr/lib/sane/libsane.so.1", O_RDONLY) = 3 [...] The library that should rather be used would be in /usr/lib/libsane.so.1 (note the missing /sane/ directory). It would be helpful if you moved this file (and other self-built ones if there are any) out of the way, verified that the SANE packages are intact ("rpm -Va sane-backends\*") and retried running scanimage: SANE_DEBUG_DLL=255 scanimage -L
I do not understand why there symlink to libsane-xerox_mfp.so.1.0.22, but all from Fedora repos: # ll /usr/lib/sane/libsane.so.1 lrwxrwxrwx 1 root root 27 Апр 5 14:41 /usr/lib/sane/libsane.so.1 -> libsane-xerox_mfp.so.1.0.22 # rpm -qf /usr/lib/sane/libsane-xerox_mfp.so.1.0.22 sane-backends-libs-1.0.22-3.fc14.i686 # rpm -Va sane-backends\* S.5....T. c /etc/sane.d/dll.conf I think I shouldn't delete manually there anything.
Meantime I've tried delete symlink /usr/lib/sane/libsane.so.1 and yes, debug output processed, and scanner found!!! I do not remember what I make such link manually. Furthermore I have not Xerox device and never had not... Thank you very much.
(In reply to comment #43) > Meantime I've tried delete symlink /usr/lib/sane/libsane.so.1 and yes, debug > output processed, and scanner found!!! I take it that your original issue is solved then, so I'll close the bug. > I do not remember what I make such link manually. Furthermore I have not Xerox > device and never had not... A possible culprit of this could be if someone or something had run ldconfig in /usr/lib/sane: for reasons I don't understand all sane backend driver modules have the same SONAME as the main library and ldconfig, if run in that directory, would have just installed this symlink to one of them.
>A possible culprit of this could be if someone or something had run ldconfig in /usr/lib/sane: for reasons I don't understand all sane backend driver modules have the same SONAME as the main library and ldconfig, if run in that directory, would have just installed this symlink to one of them. If so, it should be fixed in any case.