Hello group,
I'm happy to manage to get scanbd into Debian and replace scanbuttond.
The package still has many rough edges and even for me as Maintainer
does not work perfectly. My local setup includes a Canon LiDE 35
connected over USB. scanbd generally works fine when called straight
from the c
On 04.10.2014 16:23, Marc Stürmer wrote:
> Am 02.10.2014 um 20:36 schrieb Marc Stürmer:
>> I am trying to get my CanoSCAN LIDE 35 under Gentoo Linux up and
>> running, so far with no success.
>>
>> The scanner itself is working and not broken.
>>
>> Kernel is 3.14.19, sane-backends is version 1.0.2
On 04.10.2014 16:23, Marc Stürmer wrote:
> Am 02.10.2014 um 20:36 schrieb Marc Stürmer:
>> I am trying to get my CanoSCAN LIDE 35 under Gentoo Linux up and
>> running, so far with no success.
>>
>> The scanner itself is working and not broken.
>>
>> Kernel is 3.14.19, sane-backends is version 1.0.2
On 11.12.2014 15:39, Wilhelm wrote:
> Well, I see for in syslog.log
>
> Nov 15 19:08:43 localhost scanbd: scanbd: exec for
> /usr/share/scanbd/scripts/copy.script
> Nov 15 19:08:43 localhost scanbd: scanbd: execlp: No such file or directory
>
> which meens that your script isn't found ... but the
On 11.12.2014 21:00, Wilhelm wrote:
> Actually I have no debian system at hand ...
>
> Did you try all buttons or only option[34] "file"?
Wilhelm, thank you for the quick response again.
I wonder if this is Debian-specific and you'd need access to a Debian
system. Other Debian users did report
On 11.12.2014 21:00, Wilhelm wrote:
> Did you try all buttons or only option[34] "file"?
During the time of recording the log I sent previously I did not try all
buttons. But in the numerous previous troubleshooting sessions I tried
every single button at least once. None of them would ever give
On 12.12.2014 05:07, Wilhelm wrote:
> I must admit, actually I have no idea whar ist going wrong here. I see
> that the scanner and all options are recognized as in the
> call-from-shell case.
Wilhelm, thank you for having a look. I must admit that the logs were
gotten a few weeks ago. It is qui
Hello,
I am maintaining scanbd in Debian and found scanbd difficult to
configure with lots of possible pitfalls. As much as possible I want to
make it easy and failproof for the ordinary users to install and use
scanbd OOTB.
One of the things that broke things for me and that were hard to
troubl
On 28.02.2015 16:27, Wilhelm wrote:
> Am 25.02.2015 um 07:06 schrieb Rolf Leggewie:
>> Hello,
>>
>> I am maintaining scanbd in Debian and found scanbd difficult to
>> configure with lots of possible pitfalls. As much as possible I want to
>> make it easy and fa
On 04.03.2015 17:23, Louis Lagendijk wrote:
> comments?
I can only comment on the "packaging for a distro" aspect. If ever you
decide to pick up your plans for Fedora, I have recently done some work
and expect to do more to make sure scanbd runs flawlessly OOTB for the
end user. I think you migh
On 04.03.2015 13:46, Wilhelm wrote:
>>> What should be the effect of this env-variable SANE_BACKEND_CONFIG_DIR?
>> As maintainer, I currently need to copy all backend files from
>> /etc/sane.d/*.conf to /etc/scanbd. That is messy to say the least. If
>> SANE_BACKEND_CONFIG_DIR was a variable sep
Hello,
with scanbd sitting on top of the net backend I wonder if and how actual
scanning over the LAN still works. Two scenarios.
a) sharing a scanbd scan host SH via the LAN to scan client SC
b) accessing a saned LAN scanner LS on a scanbd-enabled computer SES
Are both scenarios supported? Th
On 04.03.2015 21:05, m. allan noah wrote:
> I'm not very familiar with scanbd- can someone explain why it needs to
> use saned, and why that running version of saned needs different
> config files?
lines 21 to 62 in the upstream README.txt
http://anonscm.debian.org/cgit/collab-maint/scanbd.git/tr
On 17.03.2015 13:15, Wilhelm wrote:
> Am 17.03.2015 um 03:00 schrieb ylafont:
>> Anyone seen this?
>
> Looks like a stray-character (form-feed?) in the file.
>> Dec 31 19:00:26 raspberry-pi dbus-daemon: Encountered error 'Error in file
>> /etc/dbus-1/system.d/scanbd_dbus.conf, line 4, column 25:
On 18.03.2015 00:03, ylafont wrote:
> Will have to check that one out.
>
> i Compared the file from version 1.4.1 the current version (1.4.2) has a
> second part on that line that it doe not like.
>
> * *
You only experience this with 1.4.2 but not 1.4.1? Debian still has
1.4.1 so it must be
Hello,
I'd like to know if it is possible to have a computer that does
button-triggered scanning via scanbd but also exports the scanner over
the network to be accesible via the common. How would one do that?
Others seem to have the same question:
https://forum.manjaro.org/index.php?topic=29
Hello Wilhelm,
thank you for the quick response.
On 19.02.2016 22:52, Wilhelm wrote:
Am 19.02.2016 um 14:38 schrieb Rolf Leggewie:
Hello,
I'd like to know if it is possible to have a computer that does
button-triggered scanning via scanbd but also exports the scanner over
the network
Couriousous wrote:
> According to the "release early, release often" here is a half-working sane
> backend for the HP LasetJet M1005 MFP.
Cool. I think the best idea might be to attach your work to the bug
tracker. Things tend to get lost and forgotten in mailing lists.
Hi,
am I overlooking something or is the backend for the HP ScanJet 4c SCSI
scanner not capable of producing a black and white scan? So far, I have
only seen a choice for gray-scale.
Regards
Rolf
Skorous wrote:
> Ummm, it can on a IIcx I'm pretty sure. IIRC, --mode=lineart does it
Thank you for the cluestick. You were of course right. For some
strange reason I had associated lineart with something else.
I think it might be a good idea to rename it b/w IMHO.
20 matches
Mail list logo