After installation of Leap 156 I am having trouble getting the network connection to my Canon GX6050 scanner function going again.‘Simple scan’ tells me ‘No scanners detected’.
If I switch off the firewall it works. My conclusion, therefore, is that there is service that should be started in the firewall. I copied a file canon-scan.xml to /etc/firewalld/ and note that a service called canon-scan is now added to the home zone. simple-scan fails to detect the scanner.
The output you’ve shared (home zone) does not include the LAN interface. You’ll need to assign that to the same zone if you want the above to be applicable to it.
My comment was purely about the making sure the interface was a member of the zone you have configured. You can examine
ip a
to see which interface is associated with your local network. Most users only have one interface so eth0 is probably correct, but you don’t need to guess these things. The existing firewall rules may not be sufficient - more analysis would be required to better understand that.
Well, that isn’t surprising really, and I assume that the canon-scan rules you mentioned in your opening post are associated with the scangearmp2 package?
Ok, this shows that in addition to working with the proprietary scangearmp2 application, your network scanner also supports eSCL (AirScan), a driverless scanning protocol.
Based on the avahi-browse output, you could try configuring /etc/sane.d/escl.conf, adding the following
type http
ip 192.168.178.5
port 80
If the scanner device is using DHCP, the IP address might change in the future. You could ensure that it doesn’t by reserving that address in your router for this device (based on its MAC adddress).
After applying the config to escl.conf, try running ‘simple-scan’ again.
FWIW, a similar recent thread discussing a Xerox device using the eSCL protocol:
I guess the support (with respect to the sane-escl backend) is not there for your particular model. In that case, stay with using the proprietary scangeamp2 application.
Doesn’t sound good. I got it working with Leap 155. But which of the many steps were the ones that did the trick? I prefer to use the Document Scanner (i.e. simple-scan under Gnome).
There seem to be several possibilities, (e.g.in /etc/sane.d/dll.conf, canon.conf, canon_dr.conf, escl.conf, pixma.conf. Maybe even in /etc/sane.d/dll.d/canon.conf etc, etc,…) but which ones are applicable in my case? How much confusion can I cause in my configuration?
The documents (e,g, man pages) do not really help me to focus on my case.
Yes, but I did not actually use scangearmp2 finally because my preferred Document Scanner worked as well! Why did simple-scan work then but not now? Scangear is less easy to use (i.e. from terminal), has less document features (e.g. multipage from ADF, etc)
Scangear would be my last resort. Getting scangear working just confirms to me that my desktop is communicating successfully with the MFP GX6050 scan function on the network.
In retrospect, I would put that down to precisely the problem I have now. There were so many adjustments to the system files at that time, including installation of scangearmp2, that I am confused about which one(s) led to the final success, i.e. I only have a vague understanding of it all! That is why I have to go over the ground again.
Well, in this thread and the previous one, you claim that scangearmp2 is working at least. However, it does not involve a SANE compatible driver as such, so you can’t choose to use another scanning utility. Not sure what stops the eSCL driver from working, but you could try explicitly enabling it as I mentioned already. A bug report may be required to help progress this.
