Description of problem: Just switched from using sane's scanimage program with Epson Perfection V200 Photo on MGA2 system to a MGA4 system, but now having problems: when scanimage should terminate, it instead hangs. Must hit ^-c twice to terminate. Searching Internet finds that this is supposed to be caused by a change made in libusb (compat), and that a fix was made in libusb 0.1.5. The libusb package with MGA4 is lib64usb-compat0.1_4-0.1.5-2.mga4 and supposedly is 0.1.5, but something is wrong that bug still seems to be present. Version-Release number of selected component (if applicable): How reproducible: scanimage always hangs at exit after scanning. Steps to Reproduce: 1.Invoke scanimage appropriately to scan and will hang when should terminate Sample session: $ scanimage > output.pnm libusbx: warning [add_to_flying_list] failed to arm first timerfd (errno 9) libusbx: warning [add_to_flying_list] failed to arm first timerfd (errno 9) libusbx: warning [add_to_flying_list] failed to arm first timerfd (errno 9) libusbx: warning [libusb_close] internal signalling write failed, closing anyway ^Cscanimage: received signal 2 scanimage: trying to stop scanner ^Cscanimage: received signal 2 scanimage: aborting Here are relevant libusb and RedHat bug reports found on web: http://www.libusb.org/ticket/130 https://bugzilla.redhat.com/show_bug.cgi?id=1038566 https://bugzilla.redhat.com/show_bug.cgi?id=1003193 Reproducible: Steps to Reproduce:
Assigning to new maintainer
Assignee: bugsquad => lists.jjorge
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. 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 Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Old
Status: NEW => RESOLVEDResolution: (none) => OLD