Bug#580578: It's probably a libsane problem

On Saturday 08 May 2010, Julien BLACHE wrote: > Michael Schuerig wrote: > > Hi, > > > After upgrading libusb-1.0-0 to version 2:1.0.8-1, the problem > > disappeared. > > Funny, because libsane doesn't actually use libusb-1.0 ... Yes, I had noticed that. I have no idea what the root cause might

Bug#580578: It's probably a libsane problem

Michael Schuerig wrote: Hi, > After upgrading libusb-1.0-0 to version 2:1.0.8-1, the problem > disappeared. Funny, because libsane doesn't actually use libusb-1.0 ... JB. -- Julien BLACHE - Debian & GNU/Linux Developer - Public key available on - KeyID: F5D6 5

Bug#580578: It's probably a libsane problem

On Saturday 08 May 2010, Julien BLACHE wrote: > 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 tri

Bug#580578: It's probably a libsane problem

Michael Schuerig 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

Bug#580578: It's probably a libsane problem

I've removed everything from /usr/lib/sane except the libs needed by my scanner, an Epson V200 Photo, installed by Avasys iscan package. Now, at least I can scan again. As I don't think that these drivers do something magically different than all the others, my hypothesis is that the real prob