Re: [sane-devel] dbus error with scanbd
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. policy user=saned* ! Arch Linux user=quot;daemonquot; /* You only experience this with 1.4.2 but not 1.4.1? Debian still has 1.4.1 so it must be unrelated, then? -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] dbus error with scanbd
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: not well-formed (invalid token)#012' while parsing '/etc/dbus-1/system.d/scanbd_dbus.conf' Quite possibly related to the error that lintian reports about the file https://lintian.debian.org/tags/dbus-policy-without-send-destination.html -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] making scanbd work OOTB in debian - question about supported backends
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 might be able to profit from some of that work. -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] making scanbd work OOTB in debian - question about supported backends
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 separate from SANE_CONFIG_DIR that wouldn't be necessary with obvious benefits to everyone. All SANE desktop applications use SANE_CONFIG_DIR. scanbd must use saned with a different dll.conf and therefore sets SANE_CONFIG_DIR before invoking saned. SANElib looks for that dll.conf and config-files in there and dll.d. The point is, that you can't direct SANE to another dll.conf. And I don't see what the help of SANE_BACKEND_CONFIG_DIR could be in this respect. But: is SANE_BACKEND_CONFIG_DIR a SANElib env-variable? Don't know about it. I am coming purely from a package maintainer's POV. I haven't looked deeply into the interaction between scanbd and saned. And I know very little about the limitations imposed on that interaction by the design of saned. It seems that me looking for a way to split the general scanbd configuration from the location of the backends can only be done if saned supports that and then indeed your suggestion of the -c and -d parameters is probably the way to go. -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] making scanbd work OOTB in debian - question about supported backends
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/tree/doc/README.txt -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] scanbd and actually scanning over the LAN
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? This will have implications for my packaging as well. I guess scenario A ought to be possible by adding something like 192.168.0.0/24 to /etc/sane.d/saned.conf on SH, while scenario B would require adding the IP or hostname of LS to /etc/sane.d/net.conf on SES. So far, so (theoretically) good? I wonder especially if scenario B isn't going to blow up in my face. Regards Rolf -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] making scanbd work OOTB in debian - question about supported backends
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 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 troubleshoot (I wrote to this ML about it last year) is that the SANE backend configurations need to be present both in /etc/sane.d and /etc/scanbd. This is due to the nature scanbd sits on top of SANE. I still wonder if scanbd couldn't be made to have an explicit SANE_BACKEND_CONFIG_DIR in addition to the SANE_CONFIG_DIR?! That would eliminate the need for what I am about to explain. What should be the effect of this env-variable SANE_BACKEND_CONFIG_DIR? I think it would be best, if the SANE lib would support setting explicitly the config file (dll.conf) and / or the config dir. Then saned could use this and introduced a -c config-file and / or -ddir options. And in turn scanbd can make use of this. I thought I had already replied to this message but I cannot see it in the archive. My apologies if this comes out as a double-post. 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 separate from SANE_CONFIG_DIR that wouldn't be necessary with obvious benefits to everyone. I do believe that your suggestion of saned having a -d or -c parameter would likely achieve the same result, alas, we don't have it and it's not clear it will arrive. -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] making scanbd work OOTB in debian - question about supported backends
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 troubleshoot (I wrote to this ML about it last year) is that the SANE backend configurations need to be present both in /etc/sane.d and /etc/scanbd. This is due to the nature scanbd sits on top of SANE. I still wonder if scanbd couldn't be made to have an explicit SANE_BACKEND_CONFIG_DIR in addition to the SANE_CONFIG_DIR?! That would eliminate the need for what I am about to explain. During installation of the binary package, I intend to create links from all the relevant backends /etc/sane.d/*.conf to /etc/scanbd. I don't think all backends have scanner buttons. I cannot imagine the v4l backend having scanner buttons (what does it do anyhow?) Same goes for the test backend. Would you advise to keep a positive list of which backends to include in the linking or rather of which ones to exclude (such as dll.conf which is not a backend configuration at all). QUESTION: Can anyone point me to which backends have and don't have scanner buttons? Regards Rolf -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] improve scanbd for Debian
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 action is triggered from the scanner (once in this log). Hello Wilhelm, thank you for the quick response. Like I said, the binary package and my installation still has many rough edges. They will need to be dealt with one at a time, in the proper order. The part you refer to is the one that is actually working, where the call to the script at least happens. Maybe the script does not exist but that is irrelevant at this time because I want to start scanbd from init but it doesn't even try to call any script (existing or non-existing). It only does that when I call it from the command-line. Lines 71 to 503 are the ones that show the call where button presses do not trigger any kind of response. Regards Rolf -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] improve scanbd for Debian
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 the same symptoms, though. I can crank up the debug-logging to level 7 and rerun the test, but I felt it was giving me too much. Currently there is nothing in the log to give any clue as to what is going wrong in one case but not the other? What could I do to get that information? Any hunch as to what might be the problem? The scanner is actually being recognized by scanbd in both cases. -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] improve scanbd for Debian
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 me any reaction at times when scanbd had been started from init. -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] improve scanbd for Debian
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 quite possible that my memory of what I was doing at what point in time was faulty. My apologies about that. I am only starting to learn how to decipher the logs on my own (totally impossible feat at log level 7, hahaha). Given that you were unable to see any difference I started a re-run and inserted some markers into syslog with the logger command to make sure I will be able to gather what happened when this time. From what I understand now, it seems that the scanner is indeed NOT recognized. How can that come about, especially given that on a call from the command-line things work just fine with the same configuration? FTR, I started scandbd from the command-line, waited a few seconds and then pressed each button once. This seems to have been successful. In the case of init, I started the program via the services command, realized the scanner was NOT recognized, unplugged and replugged it and then pressed all buttons (even though apparently the scanner had not been recognized). Regards Rolf scanbd.new-log.tar.bz2 Description: application/bzip -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] improve scanbd for Debian
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 command line as scanbd -f even for an ordinary user. Buttons are recognized and scripts called. I recently added the upstream init script to the package (patched to include a call to status) and that doesn't seem to work properly. My machine runs Ubuntu Trusty and sysvrc. scanbd seems to start up fine from init as verified with ps faux. saned21838 0.0 0.0 33252 1552 ?Sl 13:35 0:00 \_ /usr/sbin/scanbd -c /etc/scanbd/scanbd.conf But there is no reaction to button presses on the scanner. I have uploaded one log with successful button presses when the program is started directly by the user and one where the program is started from init and no reactions occur. Hopefully someone can spot something in there or otherwise suggest something for triage to move this along. I also reported this as https://bugs.launchpad.net/bugs/1401389 The attached tar-file contains the log from the console in scanbd.console-log and from syslog in scanbd-syslog.log First is a startup via init (19:00:53 to 19:07:46, lines 71 to 503). This is followed by a call to scanbd straight from the user command line (19:08:04 to 19:08:56, lines 504 to 1999). The Canon device is found in both cases (19:07:42, line 84 and 19:08:07, line 517). A file button press is registered at 19:08:42 that triggers the copy.script (line 1655). Line numbers refer to the syslog since only that one has time-stamps. Regards Rolf scanbd.log.tar.bz2 Description: application/bzip -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Canoscan LIDE 35 not working: open of device failed - invalid argument
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.24. I did some research myself, the results are: backends 1.0.23 does work backends 1.0.24 does not backends 1.0.25 from git does not I have the same scanner and 1.0.23 works for me as well. Not sure about the other releases. -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Canoscan LIDE 35 not working: open of device failed - invalid argument
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.24. I did some research myself, the results are: backends 1.0.23 does work backends 1.0.24 does not backends 1.0.25 from git does not I have the same scanner and 1.0.23 works for me as well. Not sure about the other releases. -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] HP ScanJet 4c - no b/w?
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.
[sane-devel] HP ScanJet 4c - no b/w?
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
[sane-devel] HP LaserJet M1005 sane backend
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.
