• Xsane hangs while acquiring from saned scanner

    From nmanca@21:1/5 to All on Fri May 9 17:00:01 2025
    Hi,

    I'm trying to setup a shared scanner in my home LAN from a Debian Trixie server. So far, I followed the steps reported in [1]. I avoided the
    ipp-usb protocol and relied on the older implementation based on net
    sane backed as apparently my Samsung SCX-3400 prefers that one.

    The scanner is found on the server and the client finds it over the
    network. I can connect using xsane and launch an acquisition of an image
    or a preview. Im both the cases the scanner runs but the client hangs
    waiting for something that never happens. Do you have any idea where the problem could be or how to identify it?

    I did some diagnostic:

    after a failed scan attempt, apparently the saned socked remain busy
    even after I kill xsane on the client:

    # Client
    # pkill -9 xsane

    ## Server
    # systemctl status saned.socket
    [...]
    Triggers: ● saned@17-192.168.1.1:6566-192.168.1.25:36382.service
    [...]

    In this status the client does not find the shared scanner anymore. If I restart the service on the server the socket is released and the client
    finds again the shared scanner:

    ## Server
    # scanimage -L
    device `xerox_mfp:libusb:001:003' is a Samsung Samsung SCX-3400 Series multi-function peripheral
    device `smfp:usb;04e8;344f;Z6TXB8KC3E01DHE' is a Samsung SCX-3400 Series
    on USB Scanner

    ## Client
    $ scanimage -L
    device `v4l:/dev/video0' is a Noname C270 HD WEBCAM virtual device
    device `net:<server>:xerox_mfp:libusb:001:003' is a Samsung Samsung
    SCX-3400 Series multi-function peripheral
    device `net:<server>:smfp:usb;04e8;344f;Z6TXB8KC3E01DHE' is a Samsung
    SCX-3400 Series on USB Scanner



    Cheers,
    Nicola

    [1] https://wiki.debian.org/SaneOverNetwork

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)