Summary: | media-gfx/sane-backends-1.0.21-r1: scanning over network fails | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Joerg Schaible <joerg.schaible> |
Component: | [OLD] Server | Assignee: | Patrick Kursawe (RETIRED) <phosphan> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | CC: | billie, calchan, flameeyes, printing |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
sane-backends-1.0.19.log
sane-backends-1.0.21-r1.log |
Description
Joerg Schaible
2011-01-28 19:38:06 UTC
Could you maybe shut down xinetd, run "saned -d128" and attach the output of another scan attempt? Thank you! Created attachment 261581 [details]
sane-backends-1.0.19.log
Protocol for 1.0.19 (working)
Created attachment 261584 [details]
sane-backends-1.0.21-r1.log
Protocol for 1.0.21-r1 (non-working)
Is this still a problem with .22-r1? Actually I cannot say. Meanwhile I changed hardware and I have now a Brother DCP-90190CN, i.e. I do no longer need the hplip backend (with proprietary drivers). The sane-backend-1.0.21-r1 for this Printer/Copier/Scanner and scanning over network works flawlessly. Looks like this was hplip related, cc-ing hplip maintainers. Ping! Does anyone who cares for hplip read this? (In reply to comment #7) > Ping! Does anyone who cares for hplip read this? Unfortunately I can not help here as I do not own the hardware to scan over the network. Plus, do you really think hplip is at fault when a downgrade of sane-backends to version 1.0.19-r2 fixes it. Sure, it looks unlikely - but if you have a look at the strace logs, you'll see that sane does almost the same stuff in both cases, it's the backend that aborts the scan attempt as far as I interpret it. To me it looks like it is a bug of the backend triggered by slightly different behavior of sane. No idea how to track this down - given no hardware is available. I'll close this as CANTFIX. |