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:
> 
> saned@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:
> 
> saned@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.
> 

This information alone does not show a problem with the systemd package
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.

Regards,
Michael

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to