Description of problem: Version-Release number of selected component (if applicable): libusb-0.1.12-22.fc12.i686 How reproducible: 100% Steps to Reproduce: 1. No scanners attached 2. valgrind sane-find-scanner Actual results: ==12848== Invalid read of size 1 ==12848== at 0x31AEE43: usb_parse_descriptor (in /usr/lib/libusb-0.1.so.4.4.4) ==12848== by 0x31AF0FF: usb_parse_configuration (in /usr/lib/libusb-0.1.so.4.4.4) ==12848== by 0x31B10AD: usb_os_find_devices (in /usr/lib/libusb-0.1.so.4.4.4) ==12848== by 0x31AE5F1: usb_find_devices (in /usr/lib/libusb-0.1.so.4.4.4) ==12848== by 0x805B846: ??? (in /usr/bin/sane-find-scanner) ==12848== by 0x804BFB3: ??? (in /usr/bin/sane-find-scanner) ==12848== by 0x7F1BB5: (below main) (in /lib/libc-2.11.1.so) ==12848== Address 0x408da79 is 0 bytes after a block of size 193 alloc'd ==12848== at 0x4005BDC: malloc (vg_replace_malloc.c:195) ==12848== by 0x31B1046: usb_os_find_devices (in /usr/lib/libusb-0.1.so.4.4.4) ==12848== by 0x31AE5F1: usb_find_devices (in /usr/lib/libusb-0.1.so.4.4.4) ==12848== by 0x805B846: ??? (in /usr/bin/sane-find-scanner) ==12848== by 0x804BFB3: ??? (in /usr/bin/sane-find-scanner) ==12848== by 0x7F1BB5: (below main) (in /lib/libc-2.11.1.so) Expected results: Additional info:
Created attachment 394591 [details] possible fix This might be the right fix, maybe.
I don't manage to reproduce the bug. Please, can you provide more information about installed packages? Especially I'm interested in the versions of: sane-backends glibc kernel
Don't have a F-12 on the exact same hardware anymore, but on another box (without any scanners either) the problem doesn't appear anymore
As I can't reproduce the bug and as there were no upstream changes in potential source code (descriptors.c), I'm closing this bug now.
Sorry. Reopening. I haven't noticed added external bug. This needs more investigation.
libusb-0.1.12-23.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/libusb-0.1.12-23.fc12
libusb-0.1.12-23.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/libusb-0.1.12-23.fc13
libusb-0.1.12-23.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update libusb'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/libusb-0.1.12-23.fc12
libusb-0.1.12-23.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.