Connecting with Canon GX6050 MFP network scanner

[hnimmo]

@hnimmo

@deano_ferrari

If you have the requisite entries in /etc/sane.d/escl.conf and ‘escl’ is uncommented in /etc/sane.d/dll.conf that should be sufficient for the Document Scanner (simple-scan) application to attempt to connect with the scanner device of interest.

Unfortunately, with those two settings I get

~> simple-scan
Segmentation fault (core dumped)

And, by the way, document Scanner does not start.

Any idea what other settings might be causing the screw-up?

I now have removed the entries in escl.conf again and the problem looks the Gnome Document Scanner is ‘Ready to Scan’. But it ‘Failed to scan’ because it is ‘Unable to connect to scanner’. …nearly there?

[hnimmo]

@hnimmo

I now have removed the entries in escl.conf again and the problem looks the Gnome Document Scanner is ‘Ready to Scan’. But it ‘Failed to scan’ because it is ‘Unable to connect to scanner’. …nearly there?

However, simple-scan does actually scan with the above settings.
So simple-scan and Document Scanner behave differently to one another in that case.

[deano_ferrari]

@hnimmo

Judging from the appearance of Document Scanner, I guess that it is just simple-scan called from the Gnome environment. So, I imagine, when simple-scan works from the terminal, Document Scanner will work from Gnome.

Yeah, they’re one and the same (as evident by the title bar when simple-scan is launched).

@hnimmo

I now have removed the entries in escl.conf again and the problem looks the Gnome Document Scanner is ‘Ready to Scan’. But it ‘Failed to scan’ because it is ‘Unable to connect to scanner’. …nearly there?

No, not really. For whatever reason, the scanner discovery (via Avahi) is not not working with SANE. Hence, the necessity to declare it explicitly when using scanimage or simple-scan. (The same can be done with xsane front-end actually).

[hnimmo]

@deano_ferrari

scanimage -L

@deano_ferrari

For whatever reason, the scanner discovery (via Avahi) is not not working with SANE. Hence, the necessity to declare it explicitly when using scanimage or simple-scan. (The same can be done with xsane front-end actually).

Results now from scanimage

~> scanimage -L
device `escl:https://192.168.178.5:443' is a Canon GX6000 series platen,adf scanner
device `escl:http://CanonGX6050.fritzbox:80' is a ESCL Unknown model flatbed or ADF scanner

[deano_ferrari]

That’s more like what is expected. I note than in addition to supporting ‘http’ protocol, the ‘https’ protocol is also supported. The Document Scanner should be able to find the scanner as it is discovered by scanimage.

[hnimmo]

@hnimmo

Results now from scanimage

~> scanimage -L
device `escl:https://192.168.178.5:443' is a Canon GX6000 series platen,adf scanner
device `escl:http://CanonGX6050.fritzbox:80' is a ESCL Unknown model flatbed or ADF scanner

Where does the port 443 come from?
I have just discovered the app gscan2pdf v2.13.2. It uses scanimage frontend.
It recognises the GX6050, but fails to scan:

Unknown message: scanimage: open of device escl:https://192.168.178.5:443 failed: Invalid argument

[deano_ferrari]

@hnimmo

Where does the port 443 come from?

It’s the standard port for the https protocol. As is shows up in the scanimage discovery results, I assume it is advertised as such by your network scanner?

[hnimmo]

OK. What argument is invalid?

[deano_ferrari]

It is a fairly generic error unfortunately. I’m not sure if that is an application-specific error? Once again compare with

simple-scan escl:https://192.168.178.5:443

Does that work, or does it produce errors as well?

[hnimmo]

Same behaviour as before, i.e opens Document Scanner, detects the scanner,

'Ready to Scan',

but

 'Unable to connect to scanner'

[deano_ferrari]

I think we’ve gone as far as we can here. I recommend you raise a bug report.

SANE - Reporting Bugs

[hnimmo]

@deano_ferrari

I think we’ve gone as far as we can here. I recommend you raise a bug report.

SANE - Reporting Bugs

I am totally unfamiliar with the GitLab process, but I have raised an issue and pointed back to this topic, hopefully correctly. Thanks for all your help

[deano_ferrari]

Maybe include a link to it from here as well.

[hnimmo]

Here is the link to the issue in the sane project

https://gitlab.com/sane-project/frontends/-/issues/39

[hnimmo]

The SANE project tells me we are using an old SANE version 1.0.32 here, Version 1.2.1 has been around for a long while. And also 1.3.1 is a recent release. (Might not be related to this problem, though).

[deano_ferrari]

Subscribe to the graphics repo. It currently has version1.3.1…

sudo zypper addrepo https://download.opensuse.org/repositories/graphics/15.6/graphics.repo

sudo zypper refresh

sudo zypper install sane-backends

[hnimmo]

@deano_ferrari

Subscribe to the graphics repo. It currently has version1.3.1…

Did that. Doesn’t solve the problem.

[hnimmo]

I notice that the sane-backends-autoconfig package is still at version 1.0.32. does that matter?

[deano_ferrari]

It should have updated that package as well. You can do that manually, but not relevant here. Even the maintainer was not certain that the issue you are having would be fixed with the update. Stay with that support case as it looks like you are getting the attention of the maintainer who can help with this.