[Desktop-packages] [Bug 508866] Re: Remote network scanner is not being detected in "scanimage -L" although being published through avahi (karmic)

2022-05-26 Thread Launchpad Bug Tracker
[Expired for sane-backends (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: sane-backends (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/508866

Title:
  Remote network scanner is not being detected in "scanimage -L"
  although being published through avahi (karmic)

Status in sane-backends package in Ubuntu:
  Expired

Bug description:
  The problem is as following: I got a HP 4400c USB Scanner connected to one 
machine (running karmic 64). The scanner is identified (scanimage -L) and used 
(xsane) without a problem. I was also able to make it accessible to another 
machine (also running karmic 64) by configuring saned on the server and 
net.conf on the client, and then solving the udev permissions issue, which 
seems to be mentioned in a few other bug reports - not relevant to this bug (I 
think).
  However, later I tried to make the remote machine detect the remote scanner 
automatically, through avahi - without having the saned server's IP address 
written manually to net.conf on the client machine. That didn't work. I 
verified that saned on the machine with the scanner publishes a proper service 
messahe in avahi - and it does. However neither "scanimage -L"  nor xsane are 
able to detect the remote scanner. 
  So, my question is - is the sane client configured with avahi support at all? 
If not - is that intentional?
  The package I report this bug on is sane-utils (because of scanimage).

  ProblemType: Bug
  Architecture: amd64
  Date: Sun Jan 17 21:07:14 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  NonfreeKernelModules: nvidia
  Package: sane-utils 1.0.20-4ubuntu3
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
  SourcePackage: sane-backends
  Uname: Linux 2.6.31-17-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/508866/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 508866] Re: Remote network scanner is not being detected in "scanimage -L" although being published through avahi (karmic)

2022-03-27 Thread David Ward
Thank you for reporting this bug to Ubuntu.

Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: sane-backends (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/508866

Title:
  Remote network scanner is not being detected in "scanimage -L"
  although being published through avahi (karmic)

Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  The problem is as following: I got a HP 4400c USB Scanner connected to one 
machine (running karmic 64). The scanner is identified (scanimage -L) and used 
(xsane) without a problem. I was also able to make it accessible to another 
machine (also running karmic 64) by configuring saned on the server and 
net.conf on the client, and then solving the udev permissions issue, which 
seems to be mentioned in a few other bug reports - not relevant to this bug (I 
think).
  However, later I tried to make the remote machine detect the remote scanner 
automatically, through avahi - without having the saned server's IP address 
written manually to net.conf on the client machine. That didn't work. I 
verified that saned on the machine with the scanner publishes a proper service 
messahe in avahi - and it does. However neither "scanimage -L"  nor xsane are 
able to detect the remote scanner. 
  So, my question is - is the sane client configured with avahi support at all? 
If not - is that intentional?
  The package I report this bug on is sane-utils (because of scanimage).

  ProblemType: Bug
  Architecture: amd64
  Date: Sun Jan 17 21:07:14 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  NonfreeKernelModules: nvidia
  Package: sane-utils 1.0.20-4ubuntu3
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
  SourcePackage: sane-backends
  Uname: Linux 2.6.31-17-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/508866/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp