The issues I hit are all well-described on the Red Hat bugzilla [1]. Reproducible: Sometimes Steps to Reproduce: 1. scanletter … Actual Results: Sometimes it segfaults. Sometimes it writes the image to stdout, but then hangs. Expected Results: Close gracefully after scanning the image. The problem is an atexit call added to libusb-compat in v0.1.5 [2,3] competing with atexit calls in in the sane backends [4]. I upgraded to iscan-2.29.1.5 which has fixed my problems by using libusb:1's API directly (and correctly), although see #500024 for a broken RDEPEND on that front. You could probably also work around this by downgrading to libusb-compat v0.1.4, but I haven't tested that myself. I think iscan 2.29.1.5 should be stabilized to avoid this issue. Alternatively, 2.26 should be bumped to RDEPEND on libusb-compat <= 0.1.4, but with the libusb virtuals that would be ugly. [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1003193 [2]: https://bugzilla.redhat.com/show_bug.cgi?id=1038566 [3]: http://www.libusb.org/ticket/130 [4]: https://bugzilla.redhat.com/show_bug.cgi?id=1003193#c14
Please re-open if you can reproduce this with the v2.30.1.1 version bump and dependency update for libusb.
(In reply to NP-Hardass from comment #1) > Please re-open if you can reproduce this with the v2.30.1.1 version bump and > dependency update for libusb. v2.30.1.1 works for me. However, this bug still affectes to folks like me that would prefer to use a stable ebuild. Can we stabilize iscan-2.29.1.5 (which has been out since 2013 without any other open bugs)?
*iscan-2.30.1.1 (15 Jul 2015) Sad thing is it took months of lack of response and stalling before this finally got a tarball in an accessible location and bumped. Usual time period applies. Matt you can make a stable req bug in anticipation and I can CC arches at the time with the assist of a prompt.
(In reply to Ian Delaney from comment #3) > *iscan-2.30.1.1 (15 Jul 2015) > > Sad thing is it took months of lack of response and stalling before this > finally got a tarball in an accessible location and bumped. Usual time > period applies. Matt you can make a stable req bug in anticipation and I can > CC arches at the time with the assist of a prompt. I created stable requests for the latest iscan-data and iscan packages. It hasn't been 30 days yet but as you said, it's in anticipation.
media-gfx/iscan-2.26.2 is no longer in the tree and media-gfx/iscan-2.30.2.2 is stable so I close this ticket here.
