Bug#971584: libsane1: Scanner no more identified after upgrade to 1.0.31 version

On Mon, 12 Oct 2020 10:47:47 +0200 =?ISO-8859-1?Q?J=F6rg_Frings-F=FCrst? = wrote: > tags 971584 + pending > thanks > The issue with the /var/lock/sane directory is fixed with > > commit736573a8db4bd098da28a4831ce4c601f880aacd > Hello Jörg, I tested the change in the commit but it did not

Bug#971584: libsane1: Scanner no more identified after upgrade to 1.0.31 version

Confirmed: $ ls -ald /var/lock/sane/ drwxrwxr-x 2 saned scanner 40 Oct 12 10:34 /var/lock/sane/ Creating this dir resolves the problem. R. -- richard lucassen http://contact.xaq.nl/

Bug#971584: libsane1: Scanner no more identified after upgrade to 1.0.31 version

tags 971584 + pending thanks Hello Andreas, thanks you for your work. Am Montag, den 12.10.2020, 09:41 +0200 schrieb Andreas Tscharner: > Hello World, > > I've had the same problem with my Canon CanoScan N650U. These are the > following steps that I had to do to make it work again. > > * In

Bug#971584: libsane1: Scanner no more identified after upgrade to 1.0.31 version

I can confirm that creating /var/lock/sane solves the problem for packaged libsane-plustek.so.1.0.31. I don't need to add the USB device id to plustek.conf to make it work though. Martin On Mon, Oct 12, 2020 at 9:51 AM Andreas Tscharner wrote: > Hello World, > > I've had the same problem with m

Bug#971584: libsane1: Scanner no more identified after upgrade to 1.0.31 version

Hello World, I've had the same problem with my Canon CanoScan N650U. These are the following steps that I had to do to make it work again. * In the driver configuration (plustek.conf in my case): instead of just [usb] I had to change this section name to [usb] 0x04A9 0x2209 I'm not sure about

Bug#971584: libsane1: Scanner no more identified after upgrade to 1.0.31 version

Hello Martin, thanks for your work. What changes have you made from the original Debian directory? Can you provide with your buildlog? Thanks in advance CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8C

Bug#971584: libsane1: Scanner no more identified after upgrade to 1.0.31 version

I'm also seeing this problem on a recently updated Ubuntu 20.10 (soon to be release). On request of the ubuntu bug replier, I tried to compile 1.0.31 myself and both master and 1.0.31 don't have this problem. I can even use the packaged scanimage if I replace the packaged libsane-plustek.so.1 with

Bug#971584: libsane1: Scanner no more identified after upgrade to 1.0.31 version

Package: libsane1 Version: 1.0.31-2 Followup-For: Bug #971584 Same here with an Epson Perfection 1260 (plustek backend). -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture

Bug#971584: libsane1: Scanner no more identified after upgrade to 1.0.31 version

I have exactly the same problem os: debian testing kde scanner: canon lide 25

Bug#971584: libsane1: Scanner no more identified after upgrade to 1.0.31 version

Hello, thank you for spending your time helping to make Debian better with this bug report. I will check it this weekend. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 O

Bug#971584: libsane1: Scanner no more identified after upgrade to 1.0.31 version

Package: libsane1 Version: 1.0.31-2 Severity: normal Dear Maintainer, After Ugrading from 1.0.27-3.2+b2 to 1.0.31-2, I have no more access to my USB scanner sane-find-scanner can find the scanner: $ sane-find-scanner found USB scanner (vendor=0x04a9 [Canon], product=0x220e [CanoScan], chip=LM9