No network scanner autodetection by backend kodakaio

Bug #1062617 reported by Paul Newall
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sane-backends (Ubuntu)
Fix Released
Medium
Rolf Leggewie

Bug Description

sane-backends 1.0,.23 in ubuntu 12.10 has a new backend kodakaio for kodak aio printers
The backend can autodetect network connected scanners using functions in cups.
The auto detect code is only compiled if cups.h is found at compile time.
It seems likely that cups.h was not found at compile time when the package was built?

If I compile and install kodakaio myself, the autodetect works with ubuntu 12.10
Can anyone confirm this diagnosis?
Is it possible to compile sane-backends with cups installed when building this package?
Or is it necessary for me to always compile the autodetect code and check for the presence of cups at run time?

Revision history for this message
Paul Newall (p-newalls) wrote :

Maybe there needs to be a dependency on libcups2-dev added to sane-backends ?

Revision history for this message
Robert Ancell (robert-ancell) wrote :

This will have to be done as a SRU for 12.10 but seems a valid request.

Changed in sane-backends (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Rolf Leggewie (r0lf) wrote :

I don't see libcups2-dev among the build-deps, so I guess this is still a problem even in vivid?

Changed in sane-backends (Ubuntu):
assignee: nobody → Rolf Leggewie (r0lf)
Revision history for this message
Paul Newall (p-newalls) wrote :

Just for information. Later versions of sane-backends will auto detect the kodak AiOs using avahi instead of cups.
But there could be similar problems due to the compiled code depending on the presence/absence of avahi headers.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

Thanks, Paul. Do you still own the scanner in question?

Revision history for this message
Paul Newall (p-newalls) wrote : Re: [Bug 1062617] Re: No network scanner autodetection by backend kodakaio

On 03/03/15 06:19, Rolf Leggewie wrote:
> Thanks, Paul. Do you still own the scanner in question?
>
Yes, I still have kodak aio printer scanners.
I'm not sure if working on this bug is still worth the effort.
Since sane backends 1.0.24 I think we are using avahi instead of cups to
do the network autodiscovery.
There is quite likely a similar problem, except with avahi instead of cups.

Paul

Revision history for this message
Rolf Leggewie (r0lf) wrote :

Paul, thank you for the reply. I am glad to hear you still have access to the hardware. I don't understand why you think working on this bug is still worth the effort when you believe that a similar problem is likely to exist in avahi. Can you elaborate? It would be great if you were able to confirm or refute that suspicion, too.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

I don't understand why you think working on this bug is NOT worth the effort when you believe that a similar problem is likely to exist in avahi.

Revision history for this message
Paul Newall (p-newalls) wrote :

What I meant was that it was not worth working on autodetection using cups, when the method had changed to avahi.
I do not know if the avahi autodetection works for everyone, though I have not seen many complaints about that. But I guess I should be able to test it by seeing if the live DVD can autodetect a kodakaio printer.

Revision history for this message
Paul Newall (p-newalls) wrote :

I did a trial with a live DVD. Ubuntu 16.04
A network connected kodakaio printer can be auto detected. (I think that's with avahi)
scanimage -L lists the printer.

So this bug is solved.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

Thanks, Paul, for sticking with us until the resolution of this issue.

Closing as resolved.

Changed in sane-backends (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.