While the systemd related updates fixed sane again as I could find the
pixma scanner again... However, it turned out to be a scanner from the
office downstairs (lol, saves me some electricity but I am not sure
whether they would be happy with that ;) ).
To find my own scanner (pixma MG5700 series)
There actually was an update for systemd (as jurgen already posted), so
probably there was a "fix" includes, who knows...
I can confirm that my setup is back to stock config, since I even reinstalled
sane-utils to make sure. I don't have to explicitly start saned.socket, it
works after every re
Right!
I never tried issuing the start command without the files in /etc. At
that point I assumed it should just start working when I put the files
there. Removing the files in /etc and explicitly stopping/restarting the
saned.socket service, it indeed still works.
But this means the system is ba
I don't need the files in /etc/systemd/system, the default ones work
after I removed the "new" ones:
Loaded: loaded (/lib/systemd/system/saned.socket; enabled; vendor preset:
enabled)
.
Loaded: loaded (/lib/systemd/system/saned@.service; indirect; vendor preset:
enabled)
I don't recall using so
I can confirm that for me, with all packages updated, copying the
saned*service files from /lib/systemd/system/ to /etc/systemd/ and then
running systemctl start saned.socket made everything work again.
Yay!
I would still say this is a (packaging) bug though. It should work out
of the box. Withou
Hold on a minute!
I just received some updates:
libudev1 (229-4ubuntu5) to 229-4ubuntu6
libudev1:i386 (229-4ubuntu5) to 229-4ubuntu6
python3-urllib3 (1.13.1-2) to 1.13.1-2ubuntu0.16.04.1
systemd (229-4ubuntu5) to 229-4ubuntu6
systemd-sysv (229-4ubuntu5) to 229-4ubuntu6
udev (229-4ubuntu5) to 229-4
That is silly of me, I didn't notice you typo (just copy pasted it) :)
Anyway 'sudo systemctl status saned.socket' results in:
● saned.socket - saned incoming socket
Loaded: loaded (/etc/systemd/system/saned.socket; enabled; vendor preset:
enabled)
Active: active (listening) since Thu 2016-
I don't know if kubuntu ships systemd. The command is `systemctl status
saned.socket`, sorry about that typo in the post above...
If you just used the scanner plugged into an usb socket of your machine,
and not the net-backend, there was no need to configure sane manually...
We are talking about
This is very interesting.
A few notes however. Before 16.04 (kubuntu) I never had to configure sane
manually, it just worked as it picked up my scanner (pixma MG5700). Furthermore
'sudo systemtctl status saned.socked' only results in 'sudo: systemtctl:
command not found'.
I have a fresh 16.04
After doing some research I believe this is not a bug, but a
misunderstanding. With systemd in use in 16.04 saned is started only "on
demand", when a program calls for it.
The solution from the manpage I described above is actually realised
with the sane-utils package, the files are part of that p
Another Workaround: Don't use systemd for saned. I removed
/lib/systemd/system/saned.service
/lib/systemd/system/saned.socket
/lib/systemd/system/saned@.service,
as well as the "new" files I added in
/etc/systemd/system/saned.socket
/etc/systemd/system/saned@.service,
configured saned as usual,
Thanks, I am Dutch (Holland) but I can indeed read and speak German :)
--
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:
sane service masked and cannot be unmasked
To manage notification
@ jurgen:
Perhaps you should have a look at https://wiki.ubuntuusers.de/SANE-
Scanserver_im_Netzwerk/, judging from your email address you might be
able to read german. Much about saned is documented there, I added my
solution just the other day.
--
You received this bug notification because you
Hanky, I just tried your solution but without any luck. So I just made
those two file and saved them in the path... do I need to do something
with permissions?
Bother, this is a very annoying bug as I use the scanner a lot.
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: "saned.socket"
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1577137/+attachment/4666733/+files/saned.socket
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/157713
I have the same problem, but at least found a workaround.
The man-page for saned
(http://manpages.ubuntu.com/manpages/xenial/man8/saned.8.html) shows a
solution using systemd. Two config-files are needed in
/etc/systemd/system, saned.socket and saned@.service.
With those files saned seem to work
** Changed in: sane-backends (Ubuntu)
Importance: Undecided => Medium
--
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:
sane service masked and cannot be unmasked
To manage notificati
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: sane-backends (Ubuntu)
Status: New => Confirmed
--
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
18 matches
Mail list logo
