I ave already created a new bug #1835647
On Wed, 2019-07-10 at 00:37 +, Christopher M. Penalver wrote:
> Raphael Mankin, as this report is closed, you don't have the same
> problem, or root cause (although similar symptom).
>
> Despite this, if you would like your issue addressed, please pro
Raphael Mankin, as this report is closed, you don't have the same
problem, or root cause (although similar symptom).
Despite this, if you would like your issue addressed, please provide necessary
debugging information by filing a new report via a terminal:
ubuntu-bug sane-backends
Please feel fr
I am having the same problem on Ubuntu 18.04. It was working on both 16
and 18 until recently.
root@T550:~# systemctl status saned.socket
● saned.socket - saned incoming socket
Loaded: loaded (/lib/systemd/system/saned.socket; enabled; vendor preset: ena
Active: active (listening) since Fri
Alvaro Gil, the original reporter's problem noted in the Bug Description
is the scope of this long closed report.
Despite this, when stating documentation you are referring to
https://help.ubuntu.com/community/SaneDaemonTutorial to advise, this was tested
working in Xenial at the time of its cre
The problem is the documentation is not correct, it states:
for systemd we need to add 2 configuation files in
/etc/systemd/system.
This is incorrect, move the two files to:
/etc/systemd/
---
after continue with the tutorial.
sudo s
This is still a problem with Yaketty Yak.
It looks like the systemd configuration files are messed up and urgently
need to be fixed.
In my configuration (Epson RX420 scanner/printer) connected via USB with the
local user trying to scan:
found USB scanner (vendor=0x04b8 [EPSON], product=0x080f [U
Thanks for the reply. I was able to get my scanner to work by following
a different route.
1. Uninstalled and re-installed sane and sane-utils (not sure this step was
necessary)
2. Downloaded and installed the drivers from the official Brother website (in
order to use their brsaneconfig4 util)
3
intuiter, if you followed the previously provided instructions and it
still doesn't work, then you have a problem that has nothing to do with
this now closed report.
Hence, you would want to file a new report via a terminal:
ubuntu-bug sane-backends
Please feel free to subscribe me to it.
--
Yo
I am experiencing the same issue after upgrading from 14.04 to 16.04. I have a
Brother MFC-L8850CDW network printer/scanner and it used to be detected
automatically and work fine with the SimpleScan application. After the upgrade
the scanner cannot be detected anymore. The printer still works fi
Kjetil Thuen, instructions for running saned via systemd are now
available from https://help.ubuntu.com/community/SaneDaemonTutorial .
** Changed in: sane-backends (Ubuntu)
Importance: Medium => Undecided
** Changed in: sane-backends (Ubuntu)
Status: Confirmed => Invalid
--
You receiv
I'm also having the same or similar problem with my Epson WF-3520. Worked find
at 15.10, nothing after 16.04 upgrade. I was a little confused about which set
up some of the comments described here. Mine is a printer / scanner directly
connected to the router and accessed wirelessly. So in theory
I think this is more an 'rules' thing. In post #18 I said that I did not
know what made it work but it did. I think it is because I downloaded
and installed Scangear from Canon's website. I did this to test the
printer and after that I removed the package again. However, it left a
'rules' files beh
Hi!
I tried to start simple scan with
#SANE_NET_HOSTS=XXX.XXX.XXX.XX simple-scan
and after some time it actually started, using the network scanner on
XXX.XXX.XXX.XX, using a saned process.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Hi!
I guess that is a Simple Scan problem - afaik Simple Scan is not able to
use network scanners; at least I can't use network scanners with it, and
can't recall that it was possible with earlier versions. Have you tried
xsane? If scanimage -L finds the network scanner, xsane should work too.
--
I'm on Linux Mint 18 which is based on Ubuntu 16.04 and have exactly the
same problem. Unfortunately the solutions provided here did not work for
me. If I understand correctly, the fix should be:
# sudo systemctl start saned.socket
# sudo systemctl enable saned.socket
Still simple scan doesn't wo
With systemd used in 16.04 (xenial is 16.04, not 16.10, that will be
released in october...) saned is not meant to be started manually.
saned.socket is listening for incoming requests. saned is started when a
program like XSane or scanimage are started and request a start of
saned, too. There are q
I'm running xenial (16.10) and I'm unable to start saned.
A strange thing I see is that the service is linked to /dev/null:
# ls -l /lib/systemd/system/saned.service
lrwxrwxrwx 1 root root 9 mag 19 17:35 /lib/systemd/system/saned.service ->
/dev/null
Why is that? Do I need to remove that symlink
I checked the whole procedure on a fresh 16.04 install.
To start saned.socket first I needed to run
`sudo systemctl start saned.socket`
However, in /usr/share/doc/sane-utils/README.Debian I found the
solution: To use socket.saned from startup, you have to run
`sudo systemctl enable saned.socket
** Summary changed:
- sane service masked and cannot be unmasked
+ saned.service masked and cannot be unmasked
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577137
Title:
saned.service masked and
19 matches
Mail list logo
