Bug 760545 - saned does not return any scanners in response to SANE_NET_GET_DEVICES
Summary: saned does not return any scanners in response to SANE_NET_GET_DEVICES
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: sane-backends
Version: 19
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Nils Philippsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-06 13:34 UTC by Jeff Layton
Modified: 2015-02-17 13:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 13:59:58 UTC
Type: ---


Attachments (Terms of Use)
saned debug log (3.97 KB, text/plain)
2011-12-06 13:34 UTC, Jeff Layton
no flags Details
capture of traffic between client and server (580 bytes, application/octet-stream)
2011-12-06 13:39 UTC, Jeff Layton
no flags Details
scanimage -L with SANE_DEBUG_DLL=128 (1.55 KB, text/plain)
2012-01-19 15:24 UTC, Gene Stuckey
no flags Details
saned -d0 with SANE_DEBUG_DLL=128 (1.20 KB, text/plain)
2012-01-19 15:24 UTC, Gene Stuckey
no flags Details

Description Jeff Layton 2011-12-06 13:34:23 UTC
Created attachment 541393 [details]
saned debug log

I recently upgraded one of my servers to F16. That host runs saned, to allow other hosts to use the scanner it drives.

When I run "scanimage -L" on the host itself, it sees the scanner:

$ scanimage -L
device `hpaio:/net/HP_LaserJet_CM1415fnw?zc=NPIC3B49B' is a Hewlett-Packard HP_LaserJet_CM1415fnw all-in-one

...however when I try to run scanimage -L on a remote host, the server doesn't seem to send any scanners in the list.

Attaching a log of "saned -d128"

Comment 1 Jeff Layton 2011-12-06 13:39:39 UTC
Created attachment 541394 [details]
capture of traffic between client and server

Capture of traffic on sane-port from server. Looks like the server is getting the request, and not returning any scanners for some reason.

Comment 2 Gene Stuckey 2012-01-19 15:24:26 UTC
Created attachment 556302 [details]
scanimage -L with SANE_DEBUG_DLL=128

Comment 3 Gene Stuckey 2012-01-19 15:24:59 UTC
Created attachment 556303 [details]
saned -d0 with SANE_DEBUG_DLL=128

Comment 4 Gene Stuckey 2012-01-19 15:25:17 UTC
I'm seeing the same problem on an recently upgraded Fedora 16 system. It worked fine with Fedora 14.

scanimage -L on the server sees the scanner, while saned does not seem to see it.

Using on the server:
  SANE_DEBUG_DLL=128 scanimage -L
I get:
...
  [dll] sane_get_devices: found 1 devices
  device `hpaio:/net/Photosmart_C6100_series?ip=192.168.10.198' is a Hewlett-Packard Photosmart_C6100_series all-in-one

While on the server:
  SANE_DEBUG_DLL=128  saned -d0
And running from the client:
  scanimage -L
I see on the server:
...
  [dll] sane_get_devices: found 0 devices

Full debug logs attached.

Comment 5 Fedora End Of Life 2013-01-16 21:47:18 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Nils Philippsen 2013-01-17 09:53:04 UTC
Dropped the ball on this, moving to Rawhide.

Comment 7 Fedora End Of Life 2013-04-03 18:18:53 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 9 Fedora End Of Life 2015-01-09 16:54:07 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 10 Fedora End Of Life 2015-02-17 13:59:58 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.