Scanimage failed: Invalid argument

Recently I'm having issues getting my wireless scanner to work. The same error comes back after running XSane. In the Arch wiki #Invalid_argument they describe the issue with possible solutions, but I can't figure it out. Reinstalled the sane and brscan3 drivers for my Brother DCP-J715W multifunction printer/scanner. Did I miss something?

╰─ ► scanimage -L                                                                   
device `brother3:net1;dev0' is a Brother DCP-J715W Brother_DCP-J715W
╰─ ► scanimage --test 'brother3:net1;dev0'  
scanimage: open of device brother3:net1;dev0 failed: Invalid argument

I'm able to ping to my scanner:

╰─ ► brsaneconfig3 -p                       
test Brother_DCP-J715W
ping 192.168.002.099 -w 10

PING 192.168.002.099 (192.168.2.99) 56(84) bytes of data.
64 bytes from 192.168.2.99 (192.168.2.99): icmp_seq=1 ttl=255 time=104 ms
64 bytes from 192.168.2.99 (192.168.2.99): icmp_seq=2 ttl=255 time=27.4 ms
64 bytes from 192.168.2.99 (192.168.2.99): icmp_seq=3 ttl=255 time=32.3 ms
64 bytes from 192.168.2.99 (192.168.2.99): icmp_seq=4 ttl=255 time=28.8 ms
..........

--- 192.168.002.099 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9014ms
rtt min/avg/max/mdev = 11.941/31.251/104.762/25.170 ms

Debugging:

╰─ ► SANE_DEBUG_BROTHER3=255 scanimage                                              
[sanei_debug] Setting debug level of brother3 to 255.
[brother3] brother init
[brother3] brother version: 1000001
[brother3] starting bus scan
[brother3] scanning bus 004
[brother3] found dev 046D/C52B
[brother3] found dev 8087/0024
[brother3] found dev 1D6B/0002
[brother3] scanning bus 003
[brother3] found dev 1D6B/0003
[brother3] scanning bus 002
[brother3] found dev 1D6B/0002
[brother3] scanning bus 001
[brother3] found dev 8087/0024
[brother3] found dev 1D6B/0002
scanimage: open of device brother3:net1;dev0 failed: Invalid argument

@flipper Google is Your Master :wink:

As suggested in this topic, I downgraded sane to an earlier version.
Then I ran for my network scanner brsaneconfig3 -d , and it's working again :yum:

Forum kindly sponsored by