Connecting with Canon GX6050 MFP network scanner

English Hardware
21

That error seems unrelated to the backend that is in use though? I assume it happens at launch? I would run gdb (GNU debugger utility) on it like this

gdb simple-scan
22

gdb simple-scan returns this message

Reading symbols from simple-scan...
(No debugging symbols found in simple-scan)
Missing separate debuginfos, use: zypper install simple-scan-debuginfo-3.34.2-1.82.x86_64
(gdb) 
(gdb) 

zypper install simple-scan-debuginfo-3.34.2-1.82.x86_64

Cannot find debuginfo tool in my OS-repos.

23

Does xsane work? If you don’t enable the escl backend, do you still get the same error? (All that should happen is no scanner found.)

1 Like
24 
xsane
[08:40:54.064981] [bjnp] bjnp_allocate_device: ERROR - Cannot resolve host: CanonGX6050.linux-lueh.fritzbox port 8612
25

Can you ping this device by name?

ping CanonGX6050.linux-lueh.fritzbox
1 Like
26

No. not with this address. It was the one I had hopefully entered in pixma.conf, I believed, according to the syntax required there.

But the following works.

ping CanonGX6050.fritz.box
PING CanonGX6050.fritz.box (192.168.178.5) 56(84) bytes of data.
64 bytes from CanonGX6050.fritz.box (192.168.178.5): icmp_seq=1 ttl=64 time=0.909 ms

xsane does not work, as before.

27

Ok, then you should remove any stale config in the ~/.sane/xsane/ directory.

1 Like
28

Try invoking

scanimage -v -d escl:http://192.168.178.5:80 > out.pnm
29

That works and does a scan. But setting those parameters in escl.conf has no effect. xsane continues not to find the scanner.

30

there is only one file called xsane.rc there.

31

Yes, remove it.

1 Like
32

I did. It appears again as soon as I start xsane.

33

It will do. I was referring to the stale config containing ‘CanonGX6050.linux-lueh.fritzbox’. :wink:

1 Like
34

Good to know that scrimmage does produce a working scanned image using the escl backend.

35

Now try invoking simple-scan like this:

simple-scan 'escl:http://192.168.178.5:80'
1 Like
36

It works!!! ‘Ready to Scan’ Great stuff. Thanks.

But where do these data have to be stored so that ‘Document Scanner’ finds them each time?

37

I think previous connection history is stored in the Gnome database for simple-scan. I’m not familiar with Document Scanner as I’m not a Gnome user. Anyway, try launching simple-scan again without explicitly including the connection string. It should remember the history.

1 Like
38

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.

1 Like
39

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.

40

Unfortunately, with thos 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?