[sane-devel] libsane-problem?

2013-08-22 Thread Betreuungsbüro Jenetzky
Hi Olaf,

am 22.08.2013 02:03, schrieb Olaf Meeuwissen:

> Could you tell me the
> versions of the interpreter and iscan-data packages you use?
iscan 2.29.1-5.usb0.1tdl7
iscan-data 1.23.0-1
iscan-plugin-gt-1500 2.2.0-1

> FWIW, the
> latest versions are 2.2.0-1 and 1.23.0-1, respectively.
Looks like I am up to date.

> Just to rule out the possibility that this is caused by interference
> with your other scanner(s), have you tried using gscan2pdf or scanimage
> with just a single scanner attached?
Tried both scanners without the other.
The Brother always used to respond under gscan2pdf, even if I called the 
Epson. The Epson would not work, even if the Brother was off at boot time.

Since I have a new router since last Friday, the scanner of the Brother 
(wireless) doesn't work anymore so far, though the printer of the device 
is still responding.
I meanwhile had no time to check on this, since I had outbound calls to do.

> Did you create the log with any other scanner(s) attached?  If so, I'd
> like another log taken with only the GT-1500 attached.  If not, the
> previous log will do.
I attached the same with the Brother shut off and rebooted.
Doesn't seem to be different in any way.
(And compressing makes it work without admin action...)

> You can compress logs and if you still think there too big, feel free to
> send me the log off-list.
I could have thought for myself before posting.^^

Thank you.

Regards

-jj-
-- 
Betreuungsb?ro J?rg Jenetzky
Postfach 500 640 * 22706 Hamburg
Telefon: 040 - 55 77 35 50
Telefax: 040 - 55 77 35 51
B?rozeiten MO, MI, FR, 10.00 - 14.00 Uhr

-- next part --
A non-text attachment was scrubbed...
Name: 20130822_Brother_off_reboot_gt-1500.log.tar.gz
Type: application/x-gzip
Size: 12706 bytes
Desc: not available
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130822/f8cf26ca/attachment-0001.bin>


[sane-devel] scanbd with old udev version

2013-08-22 Thread Sander Devrieze
2013/8/22 Wilhelm 

> Am 22.08.2013 08:58, schrieb Sander Devrieze:
>
>>

> 
>>
>

> This is the current status:
>> 1) saned not running + scanbd not running + scanimage -L --> scanner found
>>
>
> this is not intended to work: scanimage should use the net backend and if
> saned isn't running it shouldn't work
>
>
>  2) saned not running + scanbd running + manually running scanbm --> the
>> logs show scanbd is interrupted for a short moment
>>
>
> ok
>
>
>  3) saned not running + scanbd running + scanimage -L --> scanner *not*
>> found
>>
>> Why is case #3 not working?
>>
>
> Presumably, scanimage is using the wrong dll.conf.
>
>
I got a bit further this evening:

1) saned not running + /usr/local/sbin/scanbm & sleep 1 &&
SANE_CONFIG_DIR=/usr/local/etc/scanbd/ scanimage -L --> found
2) saned not running +/usr/local/sbin/scanbm & sleep 1 && scanimage -L -->
not found
3) saned running + scanimage -L --> not found
4) saned running + SANE_CONFIG_DIR=/usr/local/etc/scanbd/ scanimage -L -->
found

What to try next?

Please note I also still getting this error as in the beginning:

libudev: udev_monitor_enable_receiving: bind failed: Operation not permitted
/usr/local/sbin/scanbd: Can't enable udev receiving
/usr/local/sbin/scanbd: Can't init udev
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130822/bc845bd0/attachment.html>


[sane-devel] special scanning purpose

2013-08-22 Thread Stef
On 22/08/2013 18:39, c.. g.. wrote:
> Dear mailing list,
> sorry if this would be the wrong list to ask my question.
> I am looking for a good quality scanner where it is possible to modify 
> the driver, so that the internal scanner light can be turned off when 
> scanning. I want to use a external infrared light source, so a recent 
> ccd chip (showing low noise characteristics) would be needed.
> I'm using a Epson Perfection V600 Photo (epkowa backend) for normal 
> scans but I think it is not possible to get the source of this backend?
> Could anyone suggest me a scanner and the according backend which 
> would fit my requirements?
> Thanks,
> Christian
>
>
 Hello,

 the genesys backend has an option just for this purpose (lamp off 
during scan). So any supported CCD scanner could be an option, like the  
Panasonic KV-SS080 and the HP G4050.

Regards,
 Stef
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130822/9b3c2d69/attachment-0001.html>


[sane-devel] 【Sane Develop】Can you help me

2013-08-22 Thread Stef
On 22/08/2013 15:20, m. allan noah wrote:
> We have a debugging library which is part of sane-backends. It allows 
> you to set an environment variable, and which causes the backend to 
> print messages to STDERR. If your backend is part of sane-backends, 
> you can use this library. If you backend is outside of sane-backends, 
> you can certainly setup something similar in your backend. You should 
> not have to recompile the frontend.
>
> allan
>
>
> On Thu, Aug 22, 2013 at 6:46 AM,  <mailto:YiHao at rst.ricoh.com>> wrote:
>
>
> Dear Sir or Madam:
>
> I want to know,
> How can I debug the sane-backend by frontend(e.g. scanimage),
>
> How to enter the backend's breakpoint,
> Do I need to compile the frontend if I want to know  whether the
> backend
> receives the Frontend command.
>
>
>
>
>
> Can you give me some advise, Thank you.
> Best Regard
>
> Yours Sincerely, Yihao
>
>
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> <mailto:sane-devel at 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-request at lists.alioth.debian.org
> <mailto:sane-devel-request at lists.alioth.debian.org>
>
>
>
>
> -- 
> "The truth is an offense, but not a sin"
>
>
 Hello,

 you may also consider compiling with debug option, by default the 
-O2 option ins SANE build system will optimize out many information. 
When debugging I add the -ggdb option to configure to be able to step 
into code with gdb:
CFLAGS="-ggdb" ./configure \
--prefix=/usr \
--sysconfdir=/etc \
--libdir=/usr/lib64 \
--enable-parport-directio \
--enable-pnm-backend \
--enable-libusb_1_0 \
--enable-pthread \
--enable-locking \
--with-group=scanner \
--without-snmp

Then you can debug your backend even used through a frontend like xsane 
with:

gdb /usr/bin/xsane

Then you can set breakpoint, gdb will warned if function aren't resolved 
yet, but it will work here a sample session for the genesys backend:

(gdb) b genesys_sane_start
Function "genesys_sane_start" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 3 (genesys_sane_start) pending.
(gdb) r
Starting program: /usr/bin/xsane
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
Traceback (most recent call last):
   File 
"/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3600.4-gdb.py", l
ine 9, in 
 from gobject import register
   File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in 
 import gdb.backtrace
ImportError: No module named backtrace
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffeb5cb700 (LWP 2593)]

Breakpoint 2, sane_start (h=0x7a43a0) at genesys-s.c:48

Regards,
 Stef



-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130822/1c3f61ff/attachment.html>


[sane-devel] 【Sane Develop】Can you help me

2013-08-22 Thread yi...@rst.ricoh.com

Dear Sir or Madam:

I want to know,
How can I debug the sane-backend by frontend(e.g. scanimage),

How to enter the backend's breakpoint,
Do I need to compile the frontend if I want to know  whether the backend
receives the Frontend command.

  

  

  


Can you give me some advise, Thank you.
Best Regard

Yours Sincerely, Yihao




[sane-devel] special scanning purpose

2013-08-22 Thread c...... g......
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130822/f618a8ce/attachment.html>


[sane-devel] Epson2 backend and ADF

2013-08-22 Thread Michael Koltan
Am 19.08.2013 02:56, schrieb Olaf Meeuwissen:
>
> Michael Koltan writes:
>
>> Am 03.08.2013 05:28, schrieb Olaf Meeuwissen:
>>>
>>> Olaf Meeuwissen writes:
 Precompiled binaries are available from:

 http://download.ebz.epson.net/dsc/search/01/search/?OSC=LX
>>
>> The binaries didn't install because of a missing dependency,
>
> Which one?
>

Asking the question was to solve it. The missing dependency was ltdl3 
and when I looked at the filename which explicitely stated, that it was 
compiled for ltdl3 I devined, that there is probably a binary for ltdl7. 
This installs flawlessly.

>> but I was
>> able to compile a deb-package for wheezy (after turning off the tests).
>> But it didn't work correctly, and searching the error drove me nearly
>> crazy until I realized, I was fighting with a hardware problem, not a
>> software problem. After solving the problem with the adf, the epkowa
>> driver now works perfectly without any changes! Thank you very much.
>
> Care to explain the hardware problem briefly?

In fact there were two problems. First: The transport belt of the ADF 
gets slightly stuck when it is not used for several days. It is easy to 
solve this if you just move it some centimeters, but we didn't realize 
this for weeks.
I had the suspicion, that I was fighting against a hardware problem, so 
I made a second mistake: Since we own two GT-1+ I put the ADF from 
one scanner to the other without realizing, that there is some rail 
installed at the scanner (not the ADF) to guide the paper. So the 
scanner did some very funny things with the paper.
Installing the ADF back to the first scanner and slightly moving the 
transport belt before scanning worked miracles after weeks of frustration.

>
>> I am now trying to change the epson2 driver accordingly; since the
>> epkowa driver supports the nifty feature to determine automatically the
>> scan area for paper from the adf I will try to incorporate this in the
>> epson2 driver.
>
> Why bother if you can just use the epkowa driver?
> # I'm solliciting user input here.  I can think of a few reasons myself
> # but I'd like to back them up with user feedback.
>

First of all, I think, sane should work out of the box and that you 
shouldn't have to install third party modules. Most users will give up 
frustrated when they install sane, get their scanner working somehow 
(with the epson2 backend) and then realize, that features are missing. 
Most users won't google around and search if there is another backend 
they might install. I would think that at that point about 90% of the 
users are giving up. This is bad advertising for open source software.

Secondly I'm not sure how long Epson will provide the epkowa backend for 
newer versions of linux. There is always a chance, that it will disappear.

And then I have at least one of the virtues of a good programmer: I'm 
lazy. If I have fixed the epson2 backend, further updates will require 
much less work. And programming is much more fun (if you aren't stuck 
with hardware problems) than searching for additional packages on the 
internet.

Thanks again for your help

Michael




[sane-devel] scanbd with old udev version

2013-08-22 Thread Sander Devrieze
2013/8/22 Wilhelm 

> Am 22.08.2013 08:58, schrieb Sander Devrieze:
>
>> 2013/8/22 Wilhelm mailto:wilhelm.meier at 
>> fh-kl.de*
>> *>>
>>
>>
>>
>> This is the current status:
>> 1) saned not running + scanbd not running + scanimage -L --> scanner found
>>
>
> this is not intended to work: scanimage should use the net backend and if
> saned isn't running it shouldn't work
>
>
>  2) saned not running + scanbd running + manually running scanbm --> the
>> logs show scanbd is interrupted for a short moment
>>
>
> ok
>
>
>  3) saned not running + scanbd running + scanimage -L --> scanner *not*
>> found
>>
>> Why is case #3 not working?
>>
>
> Presumably, scanimage is using the wrong dll.conf.
>
>
How can I check this?
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130822/724fe20d/attachment.html>


[sane-devel] scanbd with old udev version

2013-08-22 Thread Wilhelm
Am 22.08.2013 08:58, schrieb Sander Devrieze:
> 2013/8/22 Wilhelm mailto:wilhelm.meier at 
> fh-kl.de>>
>
> Am 21.08.2013 23:27, schrieb Sander Devrieze:
>
> 2013/8/21 Wilhelm    __>>
>
>  Am 21.08.2013 16:04, schrieb Sander Devrieze:
>
>  2013/8/21 Wilhelm  
>   __>
> 
>
>   __>>
>
>
> 
>
>  Mmh, looks good.
>
>  So, if scanimage finds the scanner (started with the
> uid/gid as in
>  scanbd.conf), scanbd should find it too, if started as root
> and the
>  env-var SANE_CONFIG_DIR set.
>
>
> Scanimage does not find the scanner right now. It did only find the
> scanner when not using the net backend os sane.
>
>
> That's ok. For a desktop machine using scanbd and local scanning
> apps (like scanimage), scanbd / scanbm must be running. Please read
> 0.1) solution from the README.txt: scanbm acts as a proxy for saned.
>
>
> In that case, the
> genesys backend was immediately chosen. What else can I try?
>
>
> The below log shows, that scanbd recognizes the scanner and his
> options. So now you have to figure out which buttons correlate to
> which option value changes: just press a button and watch the log.
> Then you can tweak the scripts for the button actions.
>
>
> This is the current status:
> 1) saned not running + scanbd not running + scanimage -L --> scanner found

this is not intended to work: scanimage should use the net backend and 
if saned isn't running it shouldn't work

> 2) saned not running + scanbd running + manually running scanbm --> the
> logs show scanbd is interrupted for a short moment

ok

> 3) saned not running + scanbd running + scanimage -L --> scanner *not* found
>
> Why is case #3 not working?

Presumably, scanimage is using the wrong dll.conf.

-- 
Wilhelm
w.meier at unix.net



[sane-devel] 【Sane Develop】Can you help me

2013-08-22 Thread m. allan noah
We have a debugging library which is part of sane-backends. It allows you
to set an environment variable, and which causes the backend to print
messages to STDERR. If your backend is part of sane-backends, you can use
this library. If you backend is outside of sane-backends, you can certainly
setup something similar in your backend. You should not have to recompile
the frontend.

allan


On Thu, Aug 22, 2013 at 6:46 AM,  wrote:

>
> Dear Sir or Madam:
>
> I want to know,
> How can I debug the sane-backend by frontend(e.g. scanimage),
>
> How to enter the backend's breakpoint,
> Do I need to compile the frontend if I want to know  whether the backend
> receives the Frontend command.
>
>
>
>
>
> Can you give me some advise, Thank you.
> Best Regard
>
> Yours Sincerely, Yihao
>
>
> --
> sane-devel mailing list: sane-devel at 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-request at lists.alioth.debian.org
>



-- 
"The truth is an offense, but not a sin"
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130822/fe7fc492/attachment.html>


[sane-devel] libsane-problem?

2013-08-22 Thread Olaf Meeuwissen
Betreuungsb?ro Jenetzky writes:

> Sorry for being late.
> I had been out of office until tonight.

No problem.

> Am 19.08.2013 03:03, schrieb Olaf Meeuwissen:
>> Can you provide debug logs obtained using scanimage?
>>
>>$ SANE_DEBUG_EPKOWA=HEX scanimage --device=epkowa:interpreter:002:004 
>> --help 2> gt-1500.log
> Here we go.
> Attached is the output file.

I had a look and everything looks fine up until the second invocation of
sane_get_devices().  Up until that point all communication with the
interpreter plugin and device is going all right.  I have no clue (yet)
as to why things go wrong upon the second invocation.

I have filed in internal bug report for this.  Could you tell me the
versions of the interpreter and iscan-data packages you use?  FWIW, the
latest versions are 2.2.0-1 and 1.23.0-1, respectively.

Just to rule out the possibility that this is caused by interference
with your other scanner(s), have you tried using gscan2pdf or scanimage
with just a single scanner attached?

Did you create the log with any other scanner(s) attached?  If so, I'd
like another log taken with only the GT-1500 attached.  If not, the
previous log will do.

> Sorry, if there are no binairies wanted here, I could also post the 
> output, if desired.

You can compress logs and if you still think there too big, feel free to
send me the log off-list.

Hope this helps,
-- 
Olaf Meeuwissen, LPIC-2   FLOSS Engineer -- AVASYS CORPORATION
FSF Associate Member #1962   Help support software freedom
 http://www.fsf.org/jf?referrer=1962



[sane-devel] scanbd with old udev version

2013-08-22 Thread Sander Devrieze
2013/8/22 Wilhelm 

> Am 21.08.2013 23:27, schrieb Sander Devrieze:
>
>> 2013/8/21 Wilhelm mailto:wilhelm.meier at 
>> fh-kl.de*
>> *>>
>>
>> Am 21.08.2013 16:04, schrieb Sander Devrieze:
>>
>> 2013/8/21 Wilhelm > <mailto:wilhelm.meier at fh-kl.de**> <mailto:wilhelm.meier at 
>> fh-kl.de
>>
>> <mailto:wilhelm.meier at fh-kl.de**>>
>>
>>
>> 
>>
>> Mmh, looks good.
>>
>> So, if scanimage finds the scanner (started with the uid/gid as in
>> scanbd.conf), scanbd should find it too, if started as root and the
>> env-var SANE_CONFIG_DIR set.
>>
>>
>> Scanimage does not find the scanner right now. It did only find the
>> scanner when not using the net backend os sane.
>>
>
> That's ok. For a desktop machine using scanbd and local scanning apps
> (like scanimage), scanbd / scanbm must be running. Please read 0.1)
> solution from the README.txt: scanbm acts as a proxy for saned.
>
>
>  In that case, the
>> genesys backend was immediately chosen. What else can I try?
>>
>
> The below log shows, that scanbd recognizes the scanner and his options.
> So now you have to figure out which buttons correlate to which option value
> changes: just press a button and watch the log. Then you can tweak the
> scripts for the button actions.


This is the current status:
1) saned not running + scanbd not running + scanimage -L --> scanner found
2) saned not running + scanbd running + manually running scanbm --> the
logs show scanbd is interrupted for a short moment
3) saned not running + scanbd running + scanimage -L --> scanner *not* found

Why is case #3 not working?
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130822/42a51c95/attachment-0001.html>


[sane-devel] scanbd with old udev version

2013-08-22 Thread Wilhelm
Am 21.08.2013 23:27, schrieb Sander Devrieze:
> 2013/8/21 Wilhelm mailto:wilhelm.meier at 
> fh-kl.de>>
>
> Am 21.08.2013 16:04, schrieb Sander Devrieze:
>
> 2013/8/21 Wilhelm    >
>
>
> 
>
> Mmh, looks good.
>
> So, if scanimage finds the scanner (started with the uid/gid as in
> scanbd.conf), scanbd should find it too, if started as root and the
> env-var SANE_CONFIG_DIR set.
>
>
> Scanimage does not find the scanner right now. It did only find the
> scanner when not using the net backend os sane.

That's ok. For a desktop machine using scanbd and local scanning apps 
(like scanimage), scanbd / scanbm must be running. Please read 0.1) 
solution from the README.txt: scanbm acts as a proxy for saned.

> In that case, the
> genesys backend was immediately chosen. What else can I try?

The below log shows, that scanbd recognizes the scanner and his options. 
So now you have to figure out which buttons correlate to which option 
value changes: just press a button and watch the log. Then you can tweak 
the scripts for the button actions.

>
> Line in /etc/passwd
> saned:x:104:109::/home/saned:/bin/false
>
> This uid and gid do match with scandb:
>
> /usr/local/sbin/scanbd: foreground
> /usr/local/sbin/scanbd: config-file: /usr/local/etc/scanbd/scanbd.conf
> /usr/local/sbin/scanbd: reading config file
> /usr/local/etc/scanbd/scanbd.conf
> /usr/local/sbin/scanbd: debug on: level: 7
> /usr/local/sbin/scanbd: dropping privs to uid saned
> /usr/local/sbin/scanbd: dropping privs to gid saned
> /usr/local/sbin/scanbd: drop privileges to gid: 109
> /usr/local/sbin/scanbd: Running as effective gid 109
> /usr/local/sbin/scanbd: drop privileges to uid: 104
> /usr/local/sbin/scanbd: Running as effective uid 104
> /usr/local/sbin/scanbd: dbus_init
> /usr/local/sbin/scanbd: dbus match
> type='signal',interface='org.freedesktop.Hal.Manager'
> /usr/local/sbin/scanbd: sane version 1.0
> /usr/local/sbin/scanbd: Scanning for local-only devices
> /usr/local/sbin/scanbd: found device: genesys:libusb:001:005 Canon LiDE
> 110 flatbed scanner
> /usr/local/sbin/scanbd: start_sane_threads
> /usr/local/sbin/scanbd: Starting poll thread for genesys:libusb:001:005
> /usr/local/sbin/scanbd: sane_poll
> /usr/local/sbin/scanbd: Thread started for device genesys:libusb:001:005
> /usr/local/sbin/scanbd: start dbus thread
> /usr/local/sbin/scanbd: timeout: 500 ms
> /usr/local/sbin/scanbd: Iteration on dbus call
> /usr/local/sbin/scanbd: udev init
> /usr/local/sbin/scanbd: get udev monitor
> libudev: udev_monitor_enable_receiving: bind failed: Operation not permitted
> /usr/local/sbin/scanbd: Can't enable udev receiving
> /usr/local/sbin/scanbd: Can't init udev
> /usr/local/sbin/scanbd: found 41 options for device genesys:libusb:001:005
> /usr/local/sbin/scanbd: sane_find_matching_options
> /usr/local/sbin/scanbd: found 5 actions in section (null)
>


-- 
Wilhelm
w.meier at unix.net