Michael Schuerig <mich...@schuerig.de> wrote: Hi,
> Also, it's pretty clear that xsane is not the culprit. More likely > libsane is. However, I have reinstalled 1.0.20-13, a version of which I > know that is has worked before, and there the segfault occurs, too. If 1.0.20 segfaults now and did not segfault in the past, I'm afraid the problem could lie somewhere else :/ That said, if you can still reproduce the segfault with 1.0.21, could you try to pinpoint which backend is the buggy one? Start by disabling the libsane-extras backends in /etc/sane.d/dll.d/libsane-extras and see if the segfault still occurs. Then, disable the epkowa backend from avasys and see if the segfault still occurs. If it does, disable the libsane backends one by one in /etc/sane.d/dll.conf until the segfault no longer occurs. At that point, disable all backends except the one you just disabled. If the segfault happens with just this backend, you're done. If not, enable the backends listed in the config file after that one one by one until the segfault occurs again. If it still segfaults, send me the list of backends you've enabled at that point and I'll see if I can reproduce the issue here. Unfortunately, I couldn't hit the problem here with the default libsane configuration :/ Your backtrace points at the umax1220u backend, but that doesn't mean this backend is at fault (especially given the segfault actually happens in libusb). It's possible that a previous backend messed something up and it's just umax1220u that trips up on that. JB. -- Julien BLACHE - Debian & GNU/Linux Developer - <jbla...@debian.org> Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
