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 work for me : - with systemd, the /var/lock/sane directory does not survive a reboot because /var/lock is volatile (/var/lock is a link to /var/run, see /usr/lib/tmpfiles.d/legacy.conf). I solved this by creating a tmpd-file with: d /var/lock/sane 0775root scanner - - in it - but it is not enough, I had to put myself in the scanner group, something I did not need with 1.0.27 version. By the way, why giving /var/lock/sane rights to "saned" exclusively instead of "scanner" ? (It is just a question, I do not know myself the right thing to do). The saned group is created when installing sane-utils and by default sane-utils adds "saned" to the scanner group. Moreover, sane-utils is not always installed (not necessary for a local scanner accessed by a client like simple-scan). Best regards Pascal
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 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 the exact numbers; these are the USB idVendor and > idProduct attributes > Without these numbers the "device auto" directive did not work. > > * I had to create the /var/lock/sane directory with correct permissions; > it is missing and without it, the driver says something about "error > -11, lock failed" > The issue with the /var/lock/sane directory is fixed with commit 736573a8db4bd098da28a4831ce4c601f880aacd > HTH > Andreas 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 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54470 Lieser git: https://jff.email/cgit/ Threema: SYR8SJXB Wire: @joergfringsfuerst Skype:joergpenguin Ring: jff Telegram: @joergfringsfuerst My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
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 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 the exact numbers; these are the USB idVendor and
> idProduct attributes
> Without these numbers the "device auto" directive did not work.
>
> * I had to create the /var/lock/sane directory with correct permissions;
> it is missing and without it, the driver says something about "error
> -11, lock failed"
>
> HTH
> Andreas
> --
>("`-''-/").___..--''"`-._
> `o_ o ) `-. ( ).`-.__.`)
> (_Y_.)' ._ ) `._ `. ``-..-'
> _..`--'_..-_/ /--'_.' .'
> (il).-'' (li).' ((!.-'
>
> Andreas Tscharner a...@stupidmail.ch ICQ-No. 14356454
>
> --
> To unsubscribe, send mail to 971584-unsubscr...@bugs.debian.org.
>
--
If 'but' was any useful, it would be a logic operator
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 the exact numbers; these are the USB idVendor and
idProduct attributes
Without these numbers the "device auto" directive did not work.
* I had to create the /var/lock/sane directory with correct permissions;
it is missing and without it, the driver says something about "error
-11, lock failed"
HTH
Andreas
--
("`-''-/").___..--''"`-._
`o_ o ) `-. ( ).`-.__.`)
(_Y_.)' ._ ) `._ `. ``-..-'
_..`--'_..-_/ /--'_.' .'
(il).-'' (li).' ((!.-'
Andreas Tscharner a...@stupidmail.ch ICQ-No. 14356454
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: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54470 Lieser git: https://jff.email/cgit/ Threema: SYR8SJXB Wire: @joergfringsfuerst Skype: joergpenguin Ring: jff Telegram: @joergfringsfuerst My wish list: - Please send me a picture from the nature at your home. Am Donnerstag, den 08.10.2020, 08:00 +0200 schrieb Martin van Es: > 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 my compiled > version. > > So, there seems to be a packaging/compilation problem with the > libsane-plustek.so.1 lib in the current package, both in Debian dev and > Ubuntu 20.10 beta. > > Martin > -- > If 'but' was any useful, it would be a logic operator signature.asc Description: This is a digitally signed message part
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 my compiled version. So, there seems to be a packaging/compilation problem with the libsane-plustek.so.1 lib in the current package, both in Debian dev and Ubuntu 20.10 beta. Martin -- If 'but' was any useful, it would be a logic operator
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: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libsane1 depends on: ii acl2.2.53-8 ii adduser3.118 ii libavahi-client3 0.8-3 ii libavahi-common3 0.8-3 ii libc6 2.31-3 ii libcairo2 1.16.0-4 ii libcurl3-gnutls7.72.0-1 ii libgcc-s1 10.2.0-13 ii libglib2.0-0 2.66.0-2 ii libgphoto2-6 2.5.25-3 ii libgphoto2-port12 2.5.25-3 ii libieee1284-3 0.2.11-14 ii libjpeg62-turbo1:2.0.5-1.1 ii libpng16-161.6.37-3 ii libpoppler-glib8 20.09.0-2 ii libsane-common 1.0.31-2 ii libsnmp40 5.9+dfsg-3 ii libstdc++6 10.2.0-13 ii libtiff5 4.1.0+git191117-2 ii libusb-1.0-0 2:1.0.23-2 ii libxml22.9.10+dfsg-6 ii udev 246.6-1 Versions of packages libsane1 recommends: ii ipp-usb 0.9.13-1 ii sane-utils 1.0.31-2 Versions of packages libsane1 suggests: ii avahi-daemon 0.8-3 pn hplip -- no debconf information
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 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54470 Lieser git: https://jff.email/cgit/ Threema: SYR8SJXB Wire: @joergfringsfuerst Skype:joergpenguin Ring: jff Telegram: @joergfringsfuerst My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
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=LM9832/3) at libusb:002:003 but scanimage -L fails: $ scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). With 1.0.027 version, the scanner is found: $ scanimage -L device `plustek:libusb:002:003' is a Canon CanoScan N1240U/LiDE30 flatbed scanner Best regards -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_USER Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libsane1 depends on: ii acl2.2.53-8 ii adduser3.118 ii libavahi-client3 0.8-3 ii libavahi-common3 0.8-3 ii libc6 2.31-3 ii libcairo2 1.16.0-4 ii libcurl3-gnutls7.72.0-1 ii libgcc-s1 10.2.0-13 ii libglib2.0-0 2.66.0-2 ii libgphoto2-6 2.5.25-3 ii libgphoto2-port12 2.5.25-3 ii libieee1284-3 0.2.11-14 ii libjpeg62-turbo1:2.0.5-1.1 ii libpng16-161.6.37-3 ii libpoppler-glib8 20.09.0-2 ii libsane-common 1.0.31-2 ii libsnmp40 5.9+dfsg-3 ii libstdc++6 10.2.0-13 ii libtiff5 4.1.0+git191117-2 ii libusb-1.0-0 2:1.0.23-2 ii libxml22.9.10+dfsg-6 ii udev 246.6-1 Versions of packages libsane1 recommends: pn ipp-usb ii sane-utils 1.0.31-2 Versions of packages libsane1 suggests: pn avahi-daemon pn hplip -- no debconf information
