network backend won't connect to saned on ubuntu (9.04)

Bug #456177 reported by knorr
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sane-backends (Ubuntu)
Invalid
Undecided
Rolf Leggewie

Bug Description

Description: Ubuntu karmic (development branch)
Release: 9.10

sane net-backend cannot connect to saned running on Ubuntu 9.04
here is debug output

SANE_DEBUG_NET=128 scanimage -L

[sanei_debug] Setting debug level of net to 128.
[net] sane_init: authorize = 0x804d790, version_code = 0xbf83f6dc
[net] net_avahi_browse_callback: CACHE_EXHAUSTED
[net] sane_init: SANE net backend version 1.0.14 (AF-indep+IPv6) from sane-backends 1.0.20
[net] sane_init: Client has little endian byte order
[net] sane_init: searching for config file
[net] sane_init: trying to add amigo
[net] add_device: adding backend amigo
[net] add_device: backend amigo added
[net] sane_init: trying to add 192.168.0.2
[net] add_device: adding backend 192.168.0.2
[net] add_device: backend 192.168.0.2 added
[net] sane_init: done reading config
[net] sane_init: evaluating environment variable SANE_NET_HOSTS
[net] sane_init: evaluating environment variable SANE_NET_TIMEOUT
[net] sane_init: done
[net] sane_get_devices: local_only = 0
[net] connect_dev: trying to connect to 192.168.0.2
[net] connect_dev: [0] connection succeeded (IPv4)
[net] connect_dev: sanei_w_init
[net] connect_dev: net_init (user=knorr, local version=1.0.3)
[net] connect_dev: freeing init reply (status=Success, remote version=1.0.3)
[net] connect_dev: done
[sanei_wire] sanei_w_array: DECODE: maximum amount of allocated memory exceeded (limit: 1048576, new allocation: 624499944, total: 625548520 bytes)
[net] sane_get_devices: ignoring rpc-returned status Unknown SANE status code 1463898702
[net] connect_dev: trying to connect to amigo
[net] connect_dev: [0] connection succeeded (IPv4)
[net] connect_dev: sanei_w_init
[net] connect_dev: net_init (user=knorr, local version=1.0.3)
[net] connect_dev: freeing init reply (status=Success, remote version=1.0.3)
[net] connect_dev: done
[sanei_wire] sanei_w_array: DECODE: maximum amount of allocated memory exceeded (limit: 1048576, new allocation: 624499944, total: 625548520 bytes)
[net] sane_get_devices: ignoring rpc-returned status Unknown SANE status code 1463898702
[net] sane_get_devices: finished (0 devices)

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
[net] sane_exit: exiting
[net] net_avahi_cleanup: stopping thread
[net] net_avahi_cleanup: done
[net] sane_exit: closing dev 0x8631ec0, ctl=6
[net] sane_exit: closing dev 0x8631e58, ctl=7
[net] sane_exit: finished.

ProblemType: Bug
Architecture: i386
CheckboxSubmission: 1afde1366a7b1795bb99068a39ded88f
CheckboxSystem: 2ac50da664fc513894ca7032810c84ee
Date: Tue Oct 20 18:47:16 2009
DistroRelease: Ubuntu 9.10
Package: libsane 1.0.20-4ubuntu3
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.47-386
SourcePackage: sane-backends
Uname: Linux 2.6.31-14-386 i686

Revision history for this message
knorr (a-sokolov) wrote :
Revision history for this message
Rolf Leggewie (r0lf) wrote :

does this ever occur in trusty or later?

Changed in sane-backends (Ubuntu):
assignee: nobody → Rolf Leggewie (r0lf)
status: New → Incomplete
Revision history for this message
Rolf Leggewie (r0lf) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in sane-backends (Ubuntu):
status: Incomplete → Invalid
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.