Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#933096: libsane-common: Not possible to scan from remote clients
26 views
Skip to first unread message
Alberto Alvarez
Jul 26, 2019, 1:50:04 PM7/26/19
to
Package: libsane-common
Version: 1.0.27-3.2
Severity: important
Dear Maintainer,
* What led up to the situation?
Upgrade to Debian 10
* Description
I cannot scan with my USB MFP Samsung SCX-3200, connected my Scanner server (192.168.8.3) from remote clientes of my LAN.
The scenario is the following:
SERVER, Debian 10 (Linux SERVER 4.19.0-5-686-pae #1 SMP Debian 4.19.37-5 (2019-06-19) i686 GNU/Linux) with scanner connected, which can work normally:
SERVER:~# scanimage -L
device `xerox_mfp:libusb:001:050' is a Samsung Samsung SCX-3200 Series multi-function peripheral
SANED configuration:
SERVER:~# cat /etc/sane.d/saned.conf
192.168.8.0/23
localhost
Any client (192.168.8.7):
CLIENT:~# cat /etc/sane.d/net.conf
connect_timeout = 60
SERVER
Client cannot access to Network scanner:
CLIENT:~# 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).
CLIENT:~# sane-find-scanner
# 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.
# No SCSI scanners found. If you expected something different, make sure that
# you have loaded a kernel SCSI driver for your SCSI adapter.
could not fetch string descriptor: Pipe error
# No USB scanners found. If you expected something different, make sure that
# you have loaded a kernel driver for your USB host controller and have setup
# the USB system correctly. See man sane-usb for details.
# Not checking for parallel port scanners.
# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.
I can reach 6566 port of SERVER from CLIENT:
alberto@CLIENT:~$ telnet SERVER 6566
Trying 192.168.8.3...
Connected to SERVER.
Escape character is '^]'.
quit
Connection closed by foreign host.
And SERVER logs tell me remote access to scanner is OK:
...
Jul 23 09:59:07 SERVER saned[12026]: saned (AF-indep+IPv6+systemd) from sane-backends 1.0.27 starting up
Jul 23 09:59:07 SERVER saned[12026]: check_host: access by remote host: ::ffff:192.168.8.7
Jul 23 09:59:07 SERVER saned[12026]: init: access granted to alberto@::ffff:192.168.8.7
Jul 23 09:59:10 SERVER saned[12026]: saned exiting
Jul 23 09:59:10 SERVER systemd[1]: sa...@7-192.168.8.3:6566-192.168.8.7:52540.service: Succeeded.
...
-- System Information:
Debian Release: 10.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 4.19.0-5-686-pae (SMP w/2 CPU cores)
Locale: LANG=es_ES@euro, LC_CTYPE=es_ES@euro (charmap=UTF-8) (ignored: LC_ALL set to es_ES.utf8), LANGUAGE=es_ES@euro (charmap=UTF-8) (ignored: LC_ALL set to es_ES.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libsane-common depends on:
ii dpkg 1.19.7
libsane-common recommends no packages.
libsane-common suggests no packages.
-- Configuration Files:
/etc/sane.d/net.conf changed:
-- no debconf information
Version: 1.0.27-3.2
Severity: important
Dear Maintainer,
* What led up to the situation?
Upgrade to Debian 10
* Description
I cannot scan with my USB MFP Samsung SCX-3200, connected my Scanner server (192.168.8.3) from remote clientes of my LAN.
The scenario is the following:
SERVER, Debian 10 (Linux SERVER 4.19.0-5-686-pae #1 SMP Debian 4.19.37-5 (2019-06-19) i686 GNU/Linux) with scanner connected, which can work normally:
SERVER:~# scanimage -L
device `xerox_mfp:libusb:001:050' is a Samsung Samsung SCX-3200 Series multi-function peripheral
SANED configuration:
SERVER:~# cat /etc/sane.d/saned.conf
192.168.8.0/23
localhost
Any client (192.168.8.7):
CLIENT:~# cat /etc/sane.d/net.conf
connect_timeout = 60
SERVER
Client cannot access to Network scanner:
CLIENT:~# 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).
CLIENT:~# sane-find-scanner
# 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.
# No SCSI scanners found. If you expected something different, make sure that
# you have loaded a kernel SCSI driver for your SCSI adapter.
could not fetch string descriptor: Pipe error
# No USB scanners found. If you expected something different, make sure that
# you have loaded a kernel driver for your USB host controller and have setup
# the USB system correctly. See man sane-usb for details.
# Not checking for parallel port scanners.
# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.
I can reach 6566 port of SERVER from CLIENT:
alberto@CLIENT:~$ telnet SERVER 6566
Trying 192.168.8.3...
Connected to SERVER.
Escape character is '^]'.
quit
Connection closed by foreign host.
And SERVER logs tell me remote access to scanner is OK:
...
Jul 23 09:59:07 SERVER saned[12026]: saned (AF-indep+IPv6+systemd) from sane-backends 1.0.27 starting up
Jul 23 09:59:07 SERVER saned[12026]: check_host: access by remote host: ::ffff:192.168.8.7
Jul 23 09:59:07 SERVER saned[12026]: init: access granted to alberto@::ffff:192.168.8.7
Jul 23 09:59:10 SERVER saned[12026]: saned exiting
Jul 23 09:59:10 SERVER systemd[1]: sa...@7-192.168.8.3:6566-192.168.8.7:52540.service: Succeeded.
...
-- System Information:
Debian Release: 10.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 4.19.0-5-686-pae (SMP w/2 CPU cores)
Locale: LANG=es_ES@euro, LC_CTYPE=es_ES@euro (charmap=UTF-8) (ignored: LC_ALL set to es_ES.utf8), LANGUAGE=es_ES@euro (charmap=UTF-8) (ignored: LC_ALL set to es_ES.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libsane-common depends on:
ii dpkg 1.19.7
libsane-common recommends no packages.
libsane-common suggests no packages.
-- Configuration Files:
/etc/sane.d/net.conf changed:
-- no debconf information
MAG4 Piemonte
Sep 3, 2019, 9:30:02 AM9/3/19
to
Dear Maintainer, we also confirm the bug upgrading to Debian 10 ...
Regards!
Guido
Regards!
Guido
deb...@bersol.info
Mar 14, 2020, 11:40:03 AM3/14/20
to
On Fri, 26 Jul 2019 19:21:01 +0200 Alberto Alvarez <deb...@bersol.info> wrote:
Complete information...
I've found an command output before upgrade:
sa...@0-192.168.8.3:6566-192.168.8.10:41216.service loaded active running Scanner Service (192.168.8.10:41216) system-saned.slice loaded active active system-saned.slice saned.socket
And now is this:
sa...@6.service loaded inactive dead Scanner Service system-saned.slice loaded active active system-saned.slice saned.socket loaded active listening saned incoming socket
Log telling:
... Mar 14 16:12:29 bare saned[27770]: saned (AF-indep+IPv6+systemd) from sane-backends 1.0.27 starting up Mar 14 16:12:29 bare saned[27770]: check_host: access by remote host: ::ffff:192.168.8.20 Mar 14 16:12:29 bare saned[27770]: init: access granted to saned-user@::ffff:192.168.8.20 Mar 14 16:12:34 bare saned[27770]: process_request: (open) device_list[0] == 0 Mar 14 16:12:38 bare saned[27770]: saned exiting
...
And definitive probe of problem is systemd is that if I run "saned" in debug mode on console from Server, the problem is SOLVED.
~# saned -d [saned] check_host: access by remote host: ::ffff:192.168.8.20 [saned] init: access granted to saned-user@::ffff:192.168.8.20 Corrupt JPEG data: premature end of data segment Corrupt JPEG data: premature end of data segment Corrupt JPEG data: premature end of data segment Corrupt JPEG data: premature end of data segment Corrupt JPEG data: premature end of data segment ^C
Document Scanned succesfully.
Regards,
deb...@bersol.info
Oct 9, 2020, 4:50:03 AM10/9/20
to
Thank you Michael,
I understand, but if Saned Maintainers not show life signals about this
Bug, from 26 Jul 2019 that I opened it...
Do you think they give us some information about right source problem?
Regards
Alberto
On Sun, 4 Oct 2020 18:49:05 +0200 Michael Biebl <bi...@debian.org> wrote:
> Control: reassign -1 sane-utils
>
> Hello
> itself. Keep in mind, that when you run "saned -d" as root on the
> command line, you run it in a completely different context (and possibly
> different configuration).
>
> I'm bouncing this back to the saned maintainers, reassigning to
> sane-utils which ships saned@.service. It's more likely, that this is an
> issue with saned or the saned systemd service file.
>
> If they conclude that this is indeed a systemd problem, please reassign
> back with more information, why you think this is the case.
I understand, but if Saned Maintainers not show life signals about this
Bug, from 26 Jul 2019 that I opened it...
Do you think they give us some information about right source problem?
Regards
Alberto
On Sun, 4 Oct 2020 18:49:05 +0200 Michael Biebl <bi...@debian.org> wrote:
> Control: reassign -1 sane-utils
>
> Hello
>
> On Sat, 14 Mar 2020 16:26:28 +0100 deb...@bersol.info wrote:
> > On Fri, 26 Jul 2019 19:21:01 +0200 Alberto Alvarez <deb...@bersol.info>
> > wrote:
> >
> > Complete information...
> >
> > I've found an command output before upgrade:
> >
> > sa...@0-192.168.8.3:6566-192.168.8.10:41216.service loaded
active running Scanner Service (192.168.8.10:41216)
> > system-saned.slice loaded active active
> > system-saned.slice saned.socket
> >
> > And now is this:
> >
> > sa...@6.service loaded inactive dead Scanner Service
> > system-saned.slice loaded active active system-saned.slice
> > saned.socket loaded active listening saned incoming socket
> >
> > Log telling:
> >
> > ...
> > Mar 14 16:12:29 bare saned[27770]: saned (AF-indep+IPv6+systemd)
> On Sat, 14 Mar 2020 16:26:28 +0100 deb...@bersol.info wrote:
> > On Fri, 26 Jul 2019 19:21:01 +0200 Alberto Alvarez <deb...@bersol.info>
> > wrote:
> >
> > Complete information...
> >
> > I've found an command output before upgrade:
> >
> > sa...@0-192.168.8.3:6566-192.168.8.10:41216.service loaded
active running Scanner Service (192.168.8.10:41216)
> > system-saned.slice loaded active active
> > system-saned.slice saned.socket
> >
> > And now is this:
> >
> > sa...@6.service loaded inactive dead Scanner Service
> > system-saned.slice loaded active active system-saned.slice
> > saned.socket loaded active listening saned incoming socket
> >
> > Log telling:
> >
> > ...
from sane-backends 1.0.27 starting up
> > Mar 14 16:12:29 bare saned[27770]: check_host: access by remote
host: ::ffff:192.168.8.20
> > Mar 14 16:12:29 bare saned[27770]: init: access granted to
saned-user@::ffff:192.168.8.20
> > Mar 14 16:12:34 bare saned[27770]: process_request: (open)
device_list[0] == 0
> > Mar 14 16:12:38 bare saned[27770]: saned exiting
> >
> > ...
> >
> > And definitive probe of problem is systemd is that if I run "saned" in
> > debug mode on console from Server, the problem is SOLVED.
> >
> > *~# saned -d*
host: ::ffff:192.168.8.20
> > Mar 14 16:12:29 bare saned[27770]: init: access granted to
saned-user@::ffff:192.168.8.20
> > Mar 14 16:12:34 bare saned[27770]: process_request: (open)
device_list[0] == 0
> > Mar 14 16:12:38 bare saned[27770]: saned exiting
> >
> > ...
> >
> > And definitive probe of problem is systemd is that if I run "saned" in
> > debug mode on console from Server, the problem is SOLVED.
> >
> > [saned] check_host: access by remote host: ::ffff:192.168.8.20
> > [saned] init: access granted to saned-user@::ffff:192.168.8.20
> > Corrupt JPEG data: premature end of data segment
> > Corrupt JPEG data: premature end of data segment
> > Corrupt JPEG data: premature end of data segment
> > Corrupt JPEG data: premature end of data segment
> > Corrupt JPEG data: premature end of data segment
> > ^C
> >
> > Document Scanned succesfully.
> >
>
> This information alone does not show a problem with the systemd package
> > [saned] init: access granted to saned-user@::ffff:192.168.8.20
> > Corrupt JPEG data: premature end of data segment
> > Corrupt JPEG data: premature end of data segment
> > Corrupt JPEG data: premature end of data segment
> > Corrupt JPEG data: premature end of data segment
> > Corrupt JPEG data: premature end of data segment
> > ^C
> >
> > Document Scanned succesfully.
> >
>
> itself. Keep in mind, that when you run "saned -d" as root on the
> command line, you run it in a completely different context (and possibly
> different configuration).
>
> I'm bouncing this back to the saned maintainers, reassigning to
> sane-utils which ships saned@.service. It's more likely, that this is an
> issue with saned or the saned systemd service file.
>
> If they conclude that this is indeed a systemd problem, please reassign
> back with more information, why you think this is the case.
Jörg Frings-Fürst
Aug 28, 2021, 9:10:03 AM8/28/21
to
tags 933096 + moreinfo
--
Hello,
please can you check if the bug in
- sane-backends 1.0.32-4 (currently in testing)
still exists?
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.
--
Hello,
please can you check if the bug in
- sane-backends 1.0.32-4 (currently in testing)
still exists?
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.
deb...@bersol.info
Oct 7, 2021, 6:30:02 AM10/7/21
to
Hi,
In "libsane-common 1.0.31-4.1", the problem looks solved.
I can access to my Scanner from remote clients, without stopping service
of systemd, and starting in foreground.
Regards,
Alberto
On 9/10/20 10:42, Debian Bug Tracking System wrote:
> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
> Jörg Frings-Fürst <deb...@jff.email>
>
> If you wish to submit further information on this problem, please
> send it to 933...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
In "libsane-common 1.0.31-4.1", the problem looks solved.
I can access to my Scanner from remote clients, without stopping service
of systemd, and starting in foreground.
Regards,
Alberto
On 9/10/20 10:42, Debian Bug Tracking System wrote:
> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
> Jörg Frings-Fürst <deb...@jff.email>
>
> If you wish to submit further information on this problem, please
> send it to 933...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
MAG4 Piemonte
Jan 14, 2022, 6:40:03 AM1/14/22
to
Dear Maintainer, we also confirm the bug looks solved upgrading to Debian 11 (that use libsane-common 1.0.31-4.1) ...
Regards!
Guido
Jörg Frings-Fürst
Feb 5, 2022, 2:40:03 PM2/5/22
to
Hello,
many thanks for your info. I close this bug.
CU
Jörg
--
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key : 8CA1D25D
Skype: joergpenguin
many thanks for your info. I close this bug.
CU
Jörg
--
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key : 8CA1D25D
0 new messages