A warning about the new ‘scangearmp2’ scanner software - I don’t own Canon hardware, but after installing the 'scangearmp2-3.00-1 RPM, and attempting to run ‘scangearmp2’, I get ‘Segmentation Fault’ and then I remembered this thread describing the same problem
which resulted in a bug report being submitted
One of the developers identified that the scangearmp2 utility calls pthread_mutex_lock with an invalid pointer. So, it is actually a Canon problem, but they don’t acknowledge that.
FWIW, The SANE project doesn support some Pixma models via the sane-pixma backend
There is limited network support for some models using the Canon BNJP protocol, but maybe you model can work with this driver (not all are explicitly listed).
The pixma backend supports network scanners using the so called Canon BJNP protocol. Configuration is
normally not required. The pixma backend will auto-detect your scanner if it is within the same subnet
as your computer if your OS does support this.
If your scanner can not be auto-detected, you can add it to the pixma configuration file (see above).
FIREWALLING FOR NETWORKED SCANNERS
The sane pixma backend communicates with port 8612 on the scanner. So you will have to allow outgoing
traffic TO port 8612 on the common subnet for scanning.
Scanner detection is slightly more complicated. The pixma backend sends a broadcast on all direct con-
nected subnets it can find (provided your OS allows for enumeration of all interfaces). The broadcast is
sent FROM port 8612 TO port 8612 on the broadcast address of each interface. The outgoing packets will
be allowed by the rule described above. Responses from the scanner are sent back to the computer TO port
8612. Connection tracking however does not see a match as the response does not come from the broadcast
address but from the scanners own address. You will therefore have to allow incoming packets TO port
8612 on your computer.
So in short: open the firewall for all traffic from your computer to port 8612 AND to port 8612 to your
With the firewall rules above there is no need to add the scanner to the pixma.conf file, unless the
scanner is on a network that is not directly connected to your computer.
No configuration is normally required to use the SANE backends, but it won’t hurt to explicitly uncomment ‘pixma’ in /etc/sane.d/dll.conf by removing the ‘#’ character.
Anyway, if this backend does work, then ‘simple-scan’ or any other SANE frontend should work ok.