Bug#983332: sane-utils: incorrectly identifies Wifi USB dongles as scanners
On Thu, Feb 17, 2022 at 6:07 AM David Ward wrote: > > On 2/23/2021 8:13 AM, Martin-Éric Racine wrote: > > $ sudo sane-find-scanner > > found USB scanner (vendor=0x04a9 [Canon], product=0x2220 [CanoScan], > > chip=LM9830) at libusb:002:003 > > found USB scanner (vendor=0x0411 [Ralink], product=0x00e8 [802.11 n > > WLAN]) at libusb:001:004 > > found USB scanner (vendor=0x0b05 [Ralink], product=0x179d [802.11 n > > WLAN]) at libusb:001:003 > > What is the output of: > $ sudo sane-find-scanner -v -v Attached. > The relevant source code is here: > https://gitlab.com/sane-project/backends/-/blob/1.1.1/tools/sane-find-scanner.c#L1039-1060 > > Apparently, this assumes that if your USB device exposes even /one/ > interface where the device class or interface class is > "vendor-specific", then it is a scanner. That is almost certainly the > problem. That's probably it. Martin-Éric This is sane-find-scanner from sane-backends 1.0.31-debian # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. searching for SCSI scanners: checking /dev/scanner... failed to open (Invalid argument) checking /dev/sg0... failed to open (Invalid argument) checking /dev/sg1... failed to open (Invalid argument) checking /dev/sg2... failed to open (Invalid argument) checking /dev/sg3... failed to open (Invalid argument) checking /dev/sg4... failed to open (Invalid argument) checking /dev/sg5... failed to open (Invalid argument) checking /dev/sg6... failed to open (Invalid argument) checking /dev/sg7... failed to open (Invalid argument) checking /dev/sg8... failed to open (Invalid argument) checking /dev/sg9... failed to open (Invalid argument) checking /dev/sga... failed to open (Invalid argument) checking /dev/sgb... failed to open (Invalid argument) checking /dev/sgc... failed to open (Invalid argument) checking /dev/sgd... failed to open (Invalid argument) checking /dev/sge... failed to open (Invalid argument) checking /dev/sgf... failed to open (Invalid argument) checking /dev/sgg... failed to open (Invalid argument) checking /dev/sgh... failed to open (Invalid argument) checking /dev/sgi... failed to open (Invalid argument) checking /dev/sgj... failed to open (Invalid argument) checking /dev/sgk... failed to open (Invalid argument) checking /dev/sgl... failed to open (Invalid argument) checking /dev/sgm... failed to open (Invalid argument) checking /dev/sgn... failed to open (Invalid argument) checking /dev/sgo... failed to open (Invalid argument) checking /dev/sgp... failed to open (Invalid argument) checking /dev/sgq... failed to open (Invalid argument) checking /dev/sgr... failed to open (Invalid argument) checking /dev/sgs... failed to open (Invalid argument) checking /dev/sgt... failed to open (Invalid argument) checking /dev/sgu... failed to open (Invalid argument) checking /dev/sgv... failed to open (Invalid argument) checking /dev/sgw... failed to open (Invalid argument) checking /dev/sgx... failed to open (Invalid argument) checking /dev/sgy... failed to open (Invalid argument) checking /dev/sgz... failed to open (Invalid argument) # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. searching for USB scanners: checking /dev/usb/scanner... failed to open (Invalid argument) checking /dev/usb/scanner0... failed to open (Invalid argument) checking /dev/usb/scanner1... failed to open (Invalid argument) checking /dev/usb/scanner2... failed to open (Invalid argument) checking /dev/usb/scanner3... failed to open (Invalid argument) checking /dev/usb/scanner4... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner7... failed to open (Invalid argument) checking /dev/usb/scanner8... failed to open (Invalid argument) checking /dev/usb/scanner9... failed to open (Invalid argument) checking /dev/usb/scanner10... failed to open (Invalid argument) checking /dev/usb/scanner11... failed to open (Invalid argument) checking /dev/usb/scanner12... failed to open (Invalid argument) checking /dev/usb/scanner13... failed to open (Invalid argument) checking /dev/usb/scanner14... failed to open (Invalid argument) checking /dev/usb/scanner15... failed to open (Invalid argument) checking /dev/usbscanner... failed to open (Invalid argument) checking /dev/usbscanner0... failed to open (Invalid argument) checking /dev/usbscanner1... failed to open (Invalid argument) checking /dev/usbscanner2... failed to open (Invalid argument) checking /dev/usbscanner3... failed to open (Invalid argument) checking /dev/usbscanner4... failed to open (Invalid argument) checking /dev/usbscanner5... failed to open (Invalid argument) checking /dev/usbscanner6... failed to open (Invalid argument)
Bug#983332: sane-utils: incorrectly identifies Wifi USB dongles as scanners
On 2/23/2021 8:13 AM, Martin-Éric Racine wrote: $ sudo sane-find-scanner found USB scanner (vendor=0x04a9 [Canon], product=0x2220 [CanoScan], chip=LM9830) at libusb:002:003 found USB scanner (vendor=0x0411 [Ralink], product=0x00e8 [802.11 n WLAN]) at libusb:001:004 found USB scanner (vendor=0x0b05 [Ralink], product=0x179d [802.11 n WLAN]) at libusb:001:003 What is the output of: $ sudo sane-find-scanner -v -v The relevant source code is here: https://gitlab.com/sane-project/backends/-/blob/1.1.1/tools/sane-find-scanner.c#L1039-1060 Apparently, this assumes that if your USB device exposes even /one/ interface where the device class or interface class is "vendor-specific", then it is a scanner. That is almost certainly the problem.
Bug#983332: sane-utils: incorrectly identifies Wifi USB dongles as scanners
Control: reassign -1 sane-utils 1.0.27-3.2 Hi Eric, On Thu, Aug 26, 2021 at 09:14:02AM +0300, Martin-Éric Racine wrote: > They are supported by the kernel. They work just fine as WiFi dongles. > > They simply are NOT scanning devices. SANE makes the wrong assumption. > This has NOTHING to do with the kernel. Thanks, in this case let's reassign it back to sane-utils, as there does not seems something to be done on src:linux side for it? Regards, Salvatore
Bug#983332: sane-utils: incorrectly identifies Wifi USB dongles as scanners
$ lsusb Bus 002 Device 019: ID 8564:4000 Transcend Information, Inc. microSD/SD/CF UHS-II Card Reader [RDF8, RDF9] Bus 002 Device 018: ID 076b:1021 OmniKey AG CardMan 1021 Bus 002 Device 017: ID 05e3:0605 Genesys Logic, Inc. Hub Bus 002 Device 020: ID 04a9:2220 Canon, Inc. CanoScan LIDE 25 Bus 002 Device 016: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 002 Device 003: ID 05e3:0607 Genesys Logic, Inc. Logitech G110 Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0411:00e8 BUFFALO INC. (formerly MelCo., Inc.) WLI-UC-G300N Wireless LAN Adapter [Ralink RT2870] Bus 001 Device 003: ID 0b05:179d ASUSTek Computer, Inc. USB-N53 802.11abgn Network Adapter [Ralink RT3572] Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Please go ahead and tell me which of these is not supported by the kernel. to 26. elok. 2021 klo 9.14 Martin-Éric Racine (martin-eric.rac...@iki.fi) kirjoitti: > > They are supported by the kernel. They work just fine as WiFi dongles. > > They simply are NOT scanning devices. SANE makes the wrong assumption. > This has NOTHING to do with the kernel. > > to 26. elok. 2021 klo 8.58 Jörg Frings-Fürst (debian@jff.email) kirjoitti: > > > > reassign 983332 linux-signed-amd64 > > thanks > > > > > > Hello, > > > > at [1] the device IDs 0x0b05, 0x179d and 0x0411, 0x00e8 are not listed. > > > > Both devices are not supported by kernel. > > > > I reassign this bug to linux-signed-amd64 > > > > CU > > Jörg > > > > [1] https://wiki.debian.org/DeviceDatabase/USB > > > > -- > > 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. > >
Bug#983332: sane-utils: incorrectly identifies Wifi USB dongles as scanners
They are supported by the kernel. They work just fine as WiFi dongles. They simply are NOT scanning devices. SANE makes the wrong assumption. This has NOTHING to do with the kernel. to 26. elok. 2021 klo 8.58 Jörg Frings-Fürst (debian@jff.email) kirjoitti: > > reassign 983332 linux-signed-amd64 > thanks > > > Hello, > > at [1] the device IDs 0x0b05, 0x179d and 0x0411, 0x00e8 are not listed. > > Both devices are not supported by kernel. > > I reassign this bug to linux-signed-amd64 > > CU > Jörg > > [1] https://wiki.debian.org/DeviceDatabase/USB > > -- > 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. >
Bug#983332: sane-utils: incorrectly identifies Wifi USB dongles as scanners
reassign 983332 linux-signed-amd64 thanks Hello, at [1] the device IDs 0x0b05, 0x179d and 0x0411, 0x00e8 are not listed. Both devices are not supported by kernel. I reassign this bug to linux-signed-amd64 CU Jörg [1] https://wiki.debian.org/DeviceDatabase/USB -- 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#983332: sane-utils: incorrectly identifies Wifi USB dongles as scanners
$ sudo sane-find-scanner found USB scanner (vendor=0x04a9 [Canon], product=0x2220 [CanoScan], chip=LM9830) at libusb:002:003 found USB scanner (vendor=0x0411 [Ralink], product=0x00e8 [802.11 n WLAN]) at libusb:001:004 found USB scanner (vendor=0x0b05 [Ralink], product=0x179d [802.11 n WLAN]) at libusb:001:003 ti 23. helmik. 2021 klo 15.01 Jörg Frings-Fürst (debian@jff.email) kirjoitti: > > Hello Martin-Éric, > > > thank you for spending your time helping to make Debian better with > this bug report. > > Without further information on the "WiFi USB dongle", it is not > possible to reproduce the error. I am therefore closing this bug > report. > > CU > Jörg > > > Am Montag, dem 22.02.2021 um 16:19 +0200 schrieb Martin-Éric Racine: > > Package: sane-utils > > Version: 1.0.27-3.2 > > Severity: normal > > > > sane-find-scanner incorrectly identifies WiFi USB dongles as > > scanners. This makes sane fail to scan documents because it tries to > > connect to the wrong device. > > > > -- System Information: > > Debian Release: 10.8 > > APT prefers stable-debug > > APT policy: (500, 'stable-debug'), (500, 'stable') > > Architecture: amd64 (x86_64) > > > > Kernel: Linux 4.19.0-14-amd64 (SMP w/8 CPU cores) > > Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8), > > LANGUAGE=fi_FI.utf8 (charmap=UTF-8) > > Shell: /bin/sh linked to /bin/dash > > Init: systemd (via /run/systemd/system) > > LSM: AppArmor: enabled > > > > Versions of packages sane-utils depends on: > > ii adduser3.118 > > ii debconf [debconf-2.0] 1.5.71 > > ii libavahi-client3 0.7-4+b1 > > ii libavahi-common3 0.7-4+b1 > > ii libc6 2.28-10 > > ii libieee1284-3 0.2.11-13 > > ii libjpeg62-turbo1:1.5.2-2+deb10u1 > > ii libpng16-161.6.36-6 > > ii libsane1.0.27-3.2 > > ii libsystemd0241-7~deb10u6 > > ii libusb-1.0-0 2:1.0.22-2 > > ii lsb-base 10.2019051400 > > ii update-inetd 4.49 > > > > sane-utils recommends no packages. > > > > Versions of packages sane-utils suggests: > > ii avahi-daemon 0.7-4+b1 > > pn unpaper > > > > -- Configuration Files: > > /etc/sane.d/saned.conf changed: > > localhost > > > > > > -- debconf information: > > sane-utils/saned_run: false > > sane-utils/saned_scanner_group: true > > > > -- > 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. >
Bug#983332: sane-utils: incorrectly identifies Wifi USB dongles as scanners
Why don't you ask for the info you need instead? ti 23. helmik. 2021 klo 15.01 Jörg Frings-Fürst (debian@jff.email) kirjoitti: > > Hello Martin-Éric, > > > thank you for spending your time helping to make Debian better with > this bug report. > > Without further information on the "WiFi USB dongle", it is not > possible to reproduce the error. I am therefore closing this bug > report. > > CU > Jörg > > > Am Montag, dem 22.02.2021 um 16:19 +0200 schrieb Martin-Éric Racine: > > Package: sane-utils > > Version: 1.0.27-3.2 > > Severity: normal > > > > sane-find-scanner incorrectly identifies WiFi USB dongles as > > scanners. This makes sane fail to scan documents because it tries to > > connect to the wrong device. > > > > -- System Information: > > Debian Release: 10.8 > > APT prefers stable-debug > > APT policy: (500, 'stable-debug'), (500, 'stable') > > Architecture: amd64 (x86_64) > > > > Kernel: Linux 4.19.0-14-amd64 (SMP w/8 CPU cores) > > Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8), > > LANGUAGE=fi_FI.utf8 (charmap=UTF-8) > > Shell: /bin/sh linked to /bin/dash > > Init: systemd (via /run/systemd/system) > > LSM: AppArmor: enabled > > > > Versions of packages sane-utils depends on: > > ii adduser3.118 > > ii debconf [debconf-2.0] 1.5.71 > > ii libavahi-client3 0.7-4+b1 > > ii libavahi-common3 0.7-4+b1 > > ii libc6 2.28-10 > > ii libieee1284-3 0.2.11-13 > > ii libjpeg62-turbo1:1.5.2-2+deb10u1 > > ii libpng16-161.6.36-6 > > ii libsane1.0.27-3.2 > > ii libsystemd0241-7~deb10u6 > > ii libusb-1.0-0 2:1.0.22-2 > > ii lsb-base 10.2019051400 > > ii update-inetd 4.49 > > > > sane-utils recommends no packages. > > > > Versions of packages sane-utils suggests: > > ii avahi-daemon 0.7-4+b1 > > pn unpaper > > > > -- Configuration Files: > > /etc/sane.d/saned.conf changed: > > localhost > > > > > > -- debconf information: > > sane-utils/saned_run: false > > sane-utils/saned_scanner_group: true > > > > -- > 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. >
Bug#983332: sane-utils: incorrectly identifies Wifi USB dongles as scanners
Hello Martin-Éric, thank you for spending your time helping to make Debian better with this bug report. Without further information on the "WiFi USB dongle", it is not possible to reproduce the error. I am therefore closing this bug report. CU Jörg Am Montag, dem 22.02.2021 um 16:19 +0200 schrieb Martin-Éric Racine: > Package: sane-utils > Version: 1.0.27-3.2 > Severity: normal > > sane-find-scanner incorrectly identifies WiFi USB dongles as > scanners. This makes sane fail to scan documents because it tries to > connect to the wrong device. > > -- System Information: > Debian Release: 10.8 > APT prefers stable-debug > APT policy: (500, 'stable-debug'), (500, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.19.0-14-amd64 (SMP w/8 CPU cores) > Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8), > LANGUAGE=fi_FI.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages sane-utils depends on: > ii adduser 3.118 > ii debconf [debconf-2.0] 1.5.71 > ii libavahi-client3 0.7-4+b1 > ii libavahi-common3 0.7-4+b1 > ii libc6 2.28-10 > ii libieee1284-3 0.2.11-13 > ii libjpeg62-turbo 1:1.5.2-2+deb10u1 > ii libpng16-16 1.6.36-6 > ii libsane 1.0.27-3.2 > ii libsystemd0 241-7~deb10u6 > ii libusb-1.0-0 2:1.0.22-2 > ii lsb-base 10.2019051400 > ii update-inetd 4.49 > > sane-utils recommends no packages. > > Versions of packages sane-utils suggests: > ii avahi-daemon 0.7-4+b1 > pn unpaper > > -- Configuration Files: > /etc/sane.d/saned.conf changed: > localhost > > > -- debconf information: > sane-utils/saned_run: false > sane-utils/saned_scanner_group: true > -- 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#983332: sane-utils: incorrectly identifies Wifi USB dongles as scanners
Package: sane-utils Version: 1.0.27-3.2 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 sane-find-scanner incorrectly identifies WiFi USB dongles as scanners. This makes sane fail to scan documents because it tries to connect to the wrong device. - -- System Information: Debian Release: 10.8 APT prefers stable-debug APT policy: (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-14-amd64 (SMP w/8 CPU cores) Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8), LANGUAGE=fi_FI.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sane-utils depends on: ii adduser3.118 ii debconf [debconf-2.0] 1.5.71 ii libavahi-client3 0.7-4+b1 ii libavahi-common3 0.7-4+b1 ii libc6 2.28-10 ii libieee1284-3 0.2.11-13 ii libjpeg62-turbo1:1.5.2-2+deb10u1 ii libpng16-161.6.36-6 ii libsane1.0.27-3.2 ii libsystemd0241-7~deb10u6 ii libusb-1.0-0 2:1.0.22-2 ii lsb-base 10.2019051400 ii update-inetd 4.49 sane-utils recommends no packages. Versions of packages sane-utils suggests: ii avahi-daemon 0.7-4+b1 pn unpaper - -- Configuration Files: /etc/sane.d/saned.conf changed: localhost - -- debconf information: sane-utils/saned_run: false sane-utils/saned_scanner_group: true -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmAzvWMACgkQrh+Cd8S0 17bkog//Q9WBgfcI6YiQkp5thOA1G/GUBRxahqGU0tNBhc5WY3tndH/s7Lcd9kkw 0kELmulQ2zmMf42iNgi49W/o1HZo/HUbIQSuUKQJLU1/oeG5r8pj5EZ/i+DZzWMc j3jF3sCBUBQw97GqFx0dbR62B2EraI46fdzHz4GwwPJ+bV/7lbuS4Eu/n9TE48rx a3aeIuCsUgGh4/ghvfWINBG4mKLuZy59TnKUFsEq4u2KIe4LxLyjE5qGGZSYOkKc 8qP6g6AEtv19QJQLwgwLjO31jwShf79gWpXsNoDnS1kqDtIWUrUbET+xaLjDyi9u Zlvp4tP6MV6KhZ+1A2h3OGG1c1kOylDhDxKDtAKPZg84Cj9hwttpt/Hud6YDPcKt 7QjTVDqaGooHiSr1kakfBJJkhBQ8qeaxJTJnORuPRl2X1xAHDZ4tRanafxoDgKL8 2eBGTDDD16Zgt8V52HVRceGWHsgiBd2fUyXeRsh4ksgvNsFUa5KSSXt2+QRhw8SR Cn+RZqSeJoKEdaoUTJFqIbU/5wc9bn67RMNGfwktZ2K4GKyETUTos9tDdc40h+H/ QzJ1ctHBG19F20dFyq+mQJ7/yFzGeewu4hKCEJyTvse3UiyTrRLIUbxqrG5ssGsc TLyqDnCaZ0nKnbFenvSHLvQtwkAA3ifXwzJWDJwp33OBNrZ4cI0= =VmtJ -END PGP SIGNATURE-
