Am 10.01.2013 17:29, schrieb Johannes Meixner:
Hello,
On Jan 10 16:58 Wilhelm wrote (excerpt):
recently I had problems with my old EPSON 1670 Scanner, because it
doesn't support usb autosuspend that most distros enable by default in
the linux kernel. That causes scanimage or other
Louis,
Thank you.
When I posted the integration tweaks the service complained on startup as
simple with a dbus name. This was solved with changing the type to dbus. I
have since settled on type simple and no dbus name, and it's working fine
with no complaining.
FYI startup and shutdown:
On Fri, 2013-01-11 at 08:38 -0500, Michael Watson wrote:
Louis,
Thank you.
When I posted the integration tweaks the service complained on startup as
simple with a dbus name. This was solved with changing the type to dbus. I
have since settled on type simple and no dbus name, and it's
Hi Patrick,
I have no idea about your sine-find-scanner problem. Maybe somebody else
on the ml has an idea?
A complete pnm scan @ 1200 dpi should work without any problem.
Please try to fetch a copy from git and install sane 1.0.24. The
installation is described in README.linux.
Cheers,
Rolf
I am sorry for the long post, but I am afraid that I need to provide
a lot of background.
The issues
As you may recall I am packaging scanbd for Fedora. There are a few
issues that make this a bit challenging:
1) In order to create a good user experience, I want the package to
Louis,
Thank you.
The summary looked at 2 cases, to see if there were any differences between
utilizing scanbm.socket or xinetd. They both work. Which one is
cleaner/more secure?
FYI with version 1.2.1 both scanbd and xinetd were started by
/usr/lib/udev/rules.d/99-local.rules:
# Scan Button
