Re: [sane-devel] root can scan, user not...

[Thomas Dahlén]

On 2015-10-21 10:54, Johannes Meixner wrote:


Hello,

On Oct 20 22:56 Thomas Dahlén wrote (excerpt):

udev

...

I am stucked here


In general regarding
"USB scanner access permissions via udev"
and a
"workaround to get those kind of issues out of sight"
you may have a look at
https://en.opensuse.org/SDB:Configuring_Scanners

Regardless that this article is for openSUSE the general
ideas behind should be same on other Linux distributions.


Kind Regards
Johannes Meixner


I tried to follow the instructions in 
https://en.opensuse.org/SDB:Configuring_Scanners

In my Debian/Jessie there is no /etc/udev/rules.d/whatever-libsane.rules
I found /lib/udev/rules.d/60-libsane.rules and tested to create
/etc/udev/rules.d/60-libsane.rules
with the following content:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="04c5", ATTRS{idProduct}=="0132e", 
ENV{libsane_matched}="yes", GROUP="scanner", MODE="0660"


It still have the same problem:
thomas@ws2:~$ scanimage --device-name=fujitsu --format tiff > 
testimage7.tiffscanimage: open of device fujitsu failed: Invalid argument

but it works as root

/Thomas
--

- - - - - - - - - - -
*Thomas Dahlén*
070-710 64 54
-- 
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] Macintosh El Capitan (10.11) and twain sane

[Tom Lists]

Hi,

Has anyone tried making a 10.11 version of Twain-Sane binaries.

Thanks

Tom



-- 
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] Macintosh El Capitan (10.11) and twain sane

[Tom Lists]

Hi,

Has anyone tried making a 10.11 version of Twain-Sane binaries.

Thanks

Tom



-- 
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] 1.0.25 is out, now what?

[Johannes Meixner]

Hello,

On Oct 21 21:32 Olaf Meeuwissen wrote (excerpt):

Alessandro Zummo writes:

 There's probably still some bug in the usb code. I have
 intermittent results with some scanners on usb2
 and with others on usb3. switching among the two usb
 standards solves them all.


I'm curious about USB related issues that other backends
are facing that might be solved by switching to libusb-1
as the default.


At openSUSE we use libusb-1 since openSUSE 12.2
(i.e. we use libusb-1 since about April 2012)
via "configure --enable-libusb_1_0".
I am not aware of issues because of this.


Regarding USB 3, see
https://bugzilla.opensuse.org/show_bug.cgi?id=856794

Summary:
It seems one needs a very current kernel for USB 3.
For me kernel 4.1.6 did not work with sane-backends-1.0.25.
For me kernel-vanilla-4.3.rc5 works where it seems
the xhci USB driver is now at least somewhat fixed.
But I needed additionally the workarounds for
the broken xhci driver in sane-backends-1.0.25
i.e. sane-backends-1.0.24 did not work for me
with kernel-vanilla-4.3.rc5, see
https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c28


Kind Regards
Johannes Meixner
--
SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard,
Graham Norton - HRB 21284 (AG Nuernberg)


--
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] 1.0.25 is out, now what?

[Alessandro Zummo]

On Mon, 19 Oct 2015 22:20:25 +0900
Olaf Meeuwissen  wrote:

> Adding support for new devices, improving functionality for devices that
> are already supported and fixing bugs will be part of 1.0.26 as well but
> I think that that goes without saying.  Said it anyway and maybe that is
> just as well.  Better be explicit.

 Thanks for your hard work. Regarding coolscan3, epson2 and epsonds,
 I have no major additions.

 The first has probably a lot of bugs, but I miss any detailed
 specification from Nikon for most of the scanners.

 epson2 performs quite well, it might have a few bugs too
 but it's surely stable.

 epsonds is a new addition and I was able to test
 it with three quite new scanners. We'll see if there's
 any feedback.

 I welcome C99/C11 and the new libusb.

 There's probably still some bug in the usb code. I have
 intermittent results with some scanners on usb2
 and with others on usb3. switching among the two usb
 standards solves them all.

 Infrared support could be finally enabled as well. my own
 tiffscan frontend already handles it and I had some
 good results using it with coolscan3 and doing
 IR scratch removal with vuescan directly on the produced tiff files.
 
-- 

 Best regards,

 Alessandro Zummo - CEO,
  Tower Technologies - Torino, Italy

  http://www.towertech.it


-- 
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] Scanner CanoScan9000 Mk2

[Hans-Christoph Paul]

I bought this scanner CanoScan9000 Mk2 USB scanner since it is stated some 
fully supported.
It's my daughters PC using OpenSuse 13.1

The software in package is not updated, so I updated to 0.17.25 backend SANE 
driver.
Repository has been set to standard OpenSuse and Packman.

I can see the scanner using "lsusb" both as root and user.
I can see the scanner in Yast.
The Scanner setup in Yast shows the scanner driver, but shows is not configured.

But the front end doesn't see the scanner,  Xsane or simple scan or similar. 
They state, scanner is not visible.

I could find 2 cases in Forums with similar problems. Followed their 
suggestions, without success.

What can I do?


Best regards
Hans-Christoph Paul
-- 
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] 1.0.25 is out, now what?

[Johannes Meixner]

Hello Olaf,

first and foremost many thanks for all your
"SANE Project Janitor" work.

On Oct 19 22:20 Olaf Meeuwissen wrote (excerpt):

... unofficial ... goals for sane-backends-1.0.26.

 - modernize the autofoo bits
 - fix all compiler warnings
 - bump language level to C99
 - default to libusb-1.0

... release by early February 2016.

...

Feedback and suggestions are welcome.



Suggestion for an additional goal for sane-backends-1.0.26:

- drop support for parallel port scanners

My plan is to do this for sane-backends-1.0.25
for openSUSE Tumbleweed but currently I provide
sane-backends-1.0.25 with parallel port scanner support
because I simply had no time yet to do it.
My current plan how to drop it is to keep the backends
for parallel port scanners but to only remove the
entries for parallel port scanners from the description
files which results that the YaST scanner setup no longer
shows parallel port scanners. This way I could get end-user
feedback if parallel port scanners are still of any interest
and if yes, I could tell the user how to enable the matching
backend manually without the need to install a different
sane-backends package to get a parallel port scanner working.


RFC for an additional goal for sane-backends-1.0.26:

- switch to group "lp" instead of "scanner"

Currently SANE upstream creates udev rules with
MODE="0664", GROUP="scanner".

Hereby I ask for comments whether or not SANE upstream
should switch to group "lp" instead of "scanner".

The reason for using "lp" instead of "scanner" is described
at "USB scanner access permissions via udev" in
https://en.opensuse.org/SDB:Configuring_Scanners
(excerpt):
--
For USB multifunction devices the multifunction aspect could
make it troublesome in other Linux distributions that may
use the SANE upstream way to set scanner device nodes to
group "scanner" and add the users to that "scanner" group
which conflicts with the CUPS backend that usually needs
"lp" group read/write access to access the printer unit
so that special setup is needed to make printing work.

In openSUSE there is no group "scanner". Only the "lp" group
exists and is used in /etc/udev/rules.d/55-libsane.rules as
MODE="0664", GROUP="lp".

It is sufficiently secure and reasonable easy to use by default
the same group "lp" for printers and scanners because both kind
of devices usually require physical user access (to get the
printed paper or to place a paper on the scanner) so that both
kind of devices should usually require the same kind of security
and for multifunction devices only one group can be set and
then the "lp" group is the more reasonable default setting. 
--


I do not know how read/write access for USB scanners is done
in other Linux distributions. If also other Linux distributions
set normal-user read/write access for the device node by the
udev "uaccess" tool that sets device node user ACLs, then the
"scanner" group should be no longer actually needed because
normal-user read/write access via ACL is independent of the
device node group so that the device node group could be changed
to "lp" without regressions for normal-user read/write access.


Kind Regards
Johannes Meixner
--
SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard,
Graham Norton - HRB 21284 (AG Nuernberg)


--
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] 1.0.25 is out, now what?

[Olaf Meeuwissen]

Alessandro Zummo writes:

> On Mon, 19 Oct 2015 22:20:25 +0900
> Olaf Meeuwissen  wrote:
>
>> Adding support for new devices, improving functionality for devices that
>> are already supported and fixing bugs will be part of 1.0.26 as well but
>> I think that that goes without saying.  Said it anyway and maybe that is
>> just as well.  Better be explicit.
>
>  Thanks for your hard work.

Thanks for the thanks ;-)  It's nice to know at least some people
appreciate what one's doing.

>  Regarding coolscan3, epson2 and epsonds,
>  I have no major additions.
>
>  The first has probably a lot of bugs, but I miss any detailed
>  specification from Nikon for most of the scanners.

No specs is a problem that probably affects most of the backend
developers.  Reverse engineering is no fun and even less so when you
don't have direct access to a device.  Maybe we could think about how to
approach manufacturers to get access to specs and/or devices (and under
what conditions because we still want to be able to release source
code under LGPL-like conditions!) but that is not for 1.0.26.  Perhaps a
discussion about this is better conducted off-list.  Anyway, this is not
something that affects 1.0.26 directly.

> [snip epson2 and epsonds stuff]

>  I welcome C99/C11 and the new libusb.

C11?  Too early, I think.  C99?  So far we have 3 ayes and 0 nays.

>  There's probably still some bug in the usb code. I have
>  intermittent results with some scanners on usb2
>  and with others on usb3. switching among the two usb
>  standards solves them all.

I'm curious about USB related issues that other backends are facing that
might be solved by switching to libusb-1 as the default.  I intend to
keep libusb-0 as a fallback for 1.0.26.

>  Infrared support could be finally enabled as well. my own
>  tiffscan frontend already handles it and I had some
>  good results using it with coolscan3 and doing
>  IR scratch removal with vuescan directly on the produced tiff files.

IR support?  I knew you were gonna bring that up ;-) but that's a SANE
API change.  Given the schedule for 1.0.26, I don't think that is doable
within that time frame.  If we are going to change the API, there are
probably a *lot* of things we should work out before we can commit to
anything.  One of those things would be a clearly documented mechanism
for API changes so that backends *and* frontends can deal with them in a
graceful and sane manner (pun intended) and changes can be made in a
more incremental fashion than library major so-version bumps (if at all
possible).

There's lots more but I'll keep that for later so I can focus on getting
a 1.0.26 out in time for the major Linux distribution's spring releases.
If there are other releases SANE should care about, please say so!

Hope this helps,
-- 
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
Support Free Software   Support the Free Software Foundation
https://my.fsf.org/donatehttps://my.fsf.org/join
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9

-- 
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] 1.0.25 is out, now what?

[Alessandro Zummo]

On Wed, 21 Oct 2015 21:32:37 +0900
Olaf Meeuwissen  wrote:

> >
> don't have direct access to a device.  Maybe we could think about how to
> approach manufacturers to get access to specs and/or devices (and under
> what conditions because we still want to be able to release source

 Tried many times. Nikon gives out some speca but only 
 for a few devices. too less of a market for them.

> >  Infrared support could be finally enabled as well. my own
> >  tiffscan frontend already handles it and I had some
> >  good results using it with coolscan3 and doing
> >  IR scratch removal with vuescan directly on the produced tiff files.
> 
> IR support?  I knew you were gonna bring that up ;-) but that's a SANE

 I'm not so much interested anymore, I converted my old
 slides a long time ago and my setup works correctly, but I still
 get requests from time to time.

> API change.  Given the schedule for 1.0.26, I don't think that is doable
> within that time frame.  If we are going to change the API, there are
> probably a *lot* of things we should work out before we can commit to

 luckily we have only a few frontends to check for and most of
 them will correctly bail out when given an unknown frame type.

 given that there are a very few users that would try it I do not
 think we will be receiving a lot of reports of bad frontends.

 once xsane, scanimage, gimp and a few others have been verified
 to work we'd have covered the vast majority 

> anything.  One of those things would be a clearly documented mechanism
> for API changes so that backends *and* frontends can deal with them in a
> graceful and sane manner (pun intended) and changes can be made in a

 I haven't checked but I think that it's written somewhere that a frontend
 should correctly behave when given an unknown frame type.

-- 

 Best regards,

 Alessandro Zummo - CEO,
  Tower Technologies - Torino, Italy

  http://www.towertech.it


-- 
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] Scanner CanoScan9000 Mk2

[Johannes Meixner]

Hello,

On Oct 21 07:36 Hans-Christoph Paul wrote (excerpt):

CanoScan9000 Mk2 USB scanner


I neither not have this one nor a similar model
so that I cannot help with model-specific issues.

In general regarding "Trouble-Shooting (Debugging)" see
https://en.opensuse.org/SDB:Configuring_Scanners



OpenSuse 13.1


openSUSE 13.1 provides sane-backends-1.0.23 where
this model in not listed as supported.



I updated to 0.17.25 backend SANE driver


Strange - according to
http://www.sane-project.org/cgi-bin/driver.pl?manu=canon=9000F=any==
the "CanoScan 9000F Mark II" is listed as supported
by the pixma backend versions 0.17.23 and 0.17.24
but 0.17.25 is not (yet?) listed there.

In my current sane-backends-1.0.25 "man sane-pixma"
shows that the "CanoScan 9000F Mark II" works with
this backend.

I assume you have sane-backends-1.0.25 installed.



The Scanner setup in Yast shows the scanner driver,
but shows is not configured.


And what does it show when you configure it?



I could find 2 cases in Forums with similar problems.


What are the URLs of those "2 cases in Forums"
so that we could understand what you are talking about?


Only a guess:

Is your scanner connected to a USB 3 port at the computer?

If yes, this does not work, see
https://bugzilla.opensuse.org/show_bug.cgi?id=856794

You need a newer kernel for USB 3 where the xhci USB driver is
somewhat fixed. But you need additionally sane-backends-1.0.25
that has some additional workarounds for the broken xhci driver.

If possible connect the scanner to a true USB 2 port
this is a USB port where "lsusb -t" does not list
that the kernel-"Driver=xhci" is used for it, cf.
https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c24
(excerpt):
--
For the fun of it:
My machine has 4 USB ports, two labeled with
the "super speed" USB logo (a.k.a. USB 3) and
two labeled with the normal USB logo (a.k.a. USB 2)
but for all 4 ports xhci is used and it fails on all 4 ports.
--


Kind Regards
Johannes Meixner
--
SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard,
Graham Norton - HRB 21284 (AG Nuernberg)


--
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] root can scan, user not...

[Johannes Meixner]

Hello,

On Oct 20 22:56 Thomas Dahlén wrote (excerpt):

udev

...

I am stucked here


In general regarding
"USB scanner access permissions via udev"
and a
"workaround to get those kind of issues out of sight"
you may have a look at
https://en.opensuse.org/SDB:Configuring_Scanners

Regardless that this article is for openSUSE the general
ideas behind should be same on other Linux distributions.


Kind Regards
Johannes Meixner
--
SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard,
Graham Norton - HRB 21284 (AG Nuernberg)
-- 
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