[sane-devel] USB Epson Perfection 1250: "sane_start: Device busy"

[Tim Waugh]

--3Gf/FFewwPeBMqCJ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

I've had a report that with sane-backends 1.0.14 and 1.0.15, SANE
applications are giving this error when trying to scan with a USB
Epson Perfection 1250:

  sane_start: Device busy

Logs with SANEI_DEBUG_ variables set can be found here:

  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=140248

It isn't a permissions problem: the /proc/bus/usb node is opened
without problem.

This part of the debug output might be relevant:

[sanei_usb] sanei_usb_get_vendor_product: device 0: vendorID: 0x04b8, 
productID: 0x010f
[sanei_usb] sanei_usb_write_bulk: trying to write 2 bytes
[sanei_usb] : 1B 40   
.@..
[sanei_usb] sanei_usb_write_bulk: wanted 2 bytes, wrote 2 bytes
[sanei_usb] sanei_usb_read_bulk: trying to read 1 bytes
USB error: error reading from bulk endpoint 0x82: Connection timed out
[sanei_usb] sanei_usb_read_bulk: read failed: Connection timed out
[sanei_usb] sanei_usb_write_bulk: trying to write 2 bytes
[sanei_usb] : 1B 49   
.I..
[sanei_usb] sanei_usb_write_bulk: wanted 2 bytes, wrote 2 bytes
[sanei_usb] sanei_usb_read_bulk: trying to read 4 bytes
USB error: error reading from bulk endpoint 0x82: Connection timed out
[sanei_usb] sanei_usb_read_bulk: read failed: Connection timed out

Any ideas?

Tim.
*/

--3Gf/FFewwPeBMqCJ
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFBrKgdHU/d4jnpWe0RAp4NAJ0WBKgiQoxEcps4ozzCJsF3WN6aSgCfeajx
QOMCTbW2fdzKo+/G3JELYeU=
=kEM3
-END PGP SIGNATURE-

--3Gf/FFewwPeBMqCJ--

[sane-devel] USB Epson Perfection 1250: "sane_start: Device busy"

[Tim Waugh]

--UExESr5xZTMxdOWv
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Nov 30, 2004 at 07:57:20PM +0100, Till Kamppeter wrote:

> During some period of time around SANE 1.0.14 the Epson Perfection 1250=
=20
> and 1260 where accidentally entered as supported models in the "epson"=20
> backend, so the "epson" backend was hanging on them and so the "plustek"=
=20
> backend, which really supports them, could not access them any more. So=
=20
> the quick solution is commenting out "epson" in the=20
> /etc/sane.d/dll.conf, the correct solution is removing the appropriate=20
> entries in the source code of the "epson" backend.

Well this still seems to be affecting 1.0.15 even with the epson
backend change.  Commenting out the epson line in dll.conf makes
things work; they don't work if the line is uncommented.

Tim.
*/


--UExESr5xZTMxdOWv
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFBrgpYHU/d4jnpWe0RAv+KAJ4s1yq5kU5UBQnoKwsBN42aVOJ69gCfaWsX
hGZv09EfVAoUxG8BbrtZDrI=
=nRJz
-END PGP SIGNATURE-

--UExESr5xZTMxdOWv--

[sane-devel] USB Epson Perfection 1250: "sane_start: Device busy"

[Tim Waugh]

--E75mJrUy8lRi9cGN
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, Dec 02, 2004 at 06:41:05AM +0100, Gerhard Jaeger wrote:

> The 1250 works here with latest CVS and 1.0.15.
> IDs: 04b8:010f

This ID matches the one that is reported not to work with 1.0.15.

See comment #24:
  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=140248#c24

Tim.
*/

--E75mJrUy8lRi9cGN
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFBr06bHU/d4jnpWe0RAkOZAJ490FOWnDjrwinHJaiuRO3aibBakQCeIqfY
EgrNBFNK2dFCwmsjKXlIL9o=
=n0IH
-END PGP SIGNATURE-

--E75mJrUy8lRi9cGN--

[sane-devel] libsane.usermap addition for Epson Corp.|Perfection 4870 Photo

[Tim Waugh]

--LYDt+Tnt2WQ/hIRe
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

This report:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=3D135802

contains the following addition for libsane.usermap, which doesn't
appear to be in CVS yet:

# Epson Corp.|Perfection 4870 Photo
libusbscanner 0x0003  0x04b8   0x01280x \
   0x   0x00 0x000x000x00\=20
   0x00   0x00   0x

The contributor says:

=3D=3D>
'scanimage -L' reports:

  device `epson:libusb:001:002' is a Epson GT-X700 flatbed scanner

This is correct.  GT-X700 is a marketting name used in Asia for
the same machine known in North America and Europe as "Perfection
4870 Photo"
<=3D=3D

Tim.
*/

--LYDt+Tnt2WQ/hIRe
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFBsJO1HU/d4jnpWe0RApRQAJ9FbszGd5KgkGww6c6ISlZZaWypjgCdH45b
t5cl+NCMrZGMhEVtsQr3C/E=
=fNjt
-END PGP SIGNATURE-

--LYDt+Tnt2WQ/hIRe--

[sane-devel] USB Epson Perfection 1250: "sane_start: Device busy"

[Tim Waugh]

--V/YKEhZ4Pe4jxeTU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

This turned out to be due to a misconfiguration of the epson backend.
1.0.15 does indeed fix this problem.

Sorry for the noise,
Tim.
*/

--V/YKEhZ4Pe4jxeTU
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFBtJiDHU/d4jnpWe0RAuJTAJ0WYitcCdi3zq3zhCiemZTpenTQ7wCdECJj
CZhAX9a8Wck6nJPmO/1bniY=
=aZXB
-END PGP SIGNATURE-

--V/YKEhZ4Pe4jxeTU--

[sane-devel] local user using scanner

[Tim Waugh]

--EnT6sQnqsTJq4oDy
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, May 12, 2005 at 04:51:38PM -0400, Terry D. Boldt wrote:

> Just installed Fedora Core 3 (had been using RH8 Linux Kernal 2.4.20).
>=20
> Am having trouble getting permission for the local user (non-root) to use=
 the=20
> scanners.  I can run xsane (and vuescan) as root and the scanners are fou=
nd=20
> and used no problem. But cannot do the same as a non-root user.

Have you installed all the updates?

Tim.
*/

--EnT6sQnqsTJq4oDy
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFChNqdHU/d4jnpWe0RAog0AJ9Jrg3RkghMtfTy1Dk0i3+/QXW3BgCfc0sz
BiUjURhIE8tHqPpYt1hHOl0=
=OJ2y
-END PGP SIGNATURE-

--EnT6sQnqsTJq4oDy--

[sane-devel] local user using scanner

[Tim Waugh]

--CYbV4jyGkzCEppMb
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, May 13, 2005 at 03:02:25PM -0400, Terry D. Boldt wrote:

> On Friday 13 May 2005 12:49 pm, Tim Waugh wrote:
> > On Thu, May 12, 2005 at 04:51:38PM -0400, Terry D. Boldt wrote:
> > > Just installed Fedora Core 3 (had been using RH8 Linux Kernal 2.4.20).
> > >
> > > Am having trouble getting permission for the local user (non-root) to=
 use
> > > the scanners.  I can run xsane (and vuescan) as root and the scanners=
 are
> > > found and used no problem. But cannot do the same as a non-root user.
> >
> > Have you installed all the updates?
>=20
> The problem is getting the "/proc/bus/usb/0001/003" file set to "rw" by a=
ll=20
> users not just root. I can do so after boot, but would like it done=20
> automatically at boot.

Right, but have you installed all the updates?  Specifically I'm
thinking of:

https://www.redhat.com/archives/fedora-announce-list/2005-January/msg00077.=
html

but there are some others that it depends on too.

Tim.
*/

--CYbV4jyGkzCEppMb
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFChe7wHU/d4jnpWe0RAovjAJ9luLpL13lAnVd3mpbcyh3Rx2kACgCdHYZq
n55C5VudZJKhLFOsHT8ctJk=
=Gyzm
-END PGP SIGNATURE-

--CYbV4jyGkzCEppMb--

[sane-devel] local user using scanner

[Tim Waugh]

--8RzCspYsRAU9V6Ra
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Sat, May 14, 2005 at 01:28:32PM +0100, Tim Waugh wrote:

> Right, but have you installed all the updates?

Let me say it explicitly: the installing the Fedora Core updates
should fix this issue for you.

Tim.
*/

--8RzCspYsRAU9V6Ra
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFChfBpHU/d4jnpWe0RApT3AKCbgGyW3db8qI1CVQsxy4a0sBT/lwCfY4sX
lU2n5lRzm1lMTQCIo/t4prk=
=506r
-END PGP SIGNATURE-

--8RzCspYsRAU9V6Ra--

[sane-devel] local user using scanner

[Tim Waugh]

--j5904Piqecmxrsp+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, May 15, 2005 at 07:42:02PM -0400, Terry D. Boldt wrote:

> I guess I will have to live with a broken FC3 until I can find another di=
stro=20
> that isn't as badly broken or wait for FC4 - hopefully these problems wil=
l be=20
> fixed there since you indicate the updated FC3 fixes the problem. Unless,=
=20
> that is, somebody distributes the updates on CD-ROM, then I could use tha=
t.

Or you could run 'up2date sane-backends', which will update that
package and those it depends on.  I seem to recall there are two other
packages which needed to be upgraded.

Tim.
*/

--j5904Piqecmxrsp+
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCiF4bHU/d4jnpWe0RApQ2AJ9WRe/Kjo7s4W2976fpRwAC8HzU7gCglB23
NWAt1Ru3wIAPFq+fhlhOKwY=
=AZUn
-END PGP SIGNATURE-

--j5904Piqecmxrsp+--

[sane-devel] Redhat 9 and XSane .89

[Tim Waugh]

--fNagykWcDoSVAmSd
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Fri, Jun 06, 2003 at 09:51:20AM +0200, Henning Meier-Geinitz wrote:

> You mean xsane is started when you log into X? Oh well...

That might be the case if he has put it in his GNOME session; it's not
something Red Hat Linux does by default (of course).

Tim.
*/

--fNagykWcDoSVAmSd
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE+4FXKtO8Ac4jnUq4RAh8eAKCQRB4p5Ham0NyynnaSk4W93EtIEgCdHCmc
L4MEe6ALlSdZRXcrgG7wgVE=
=V3CX
-END PGP SIGNATURE-

--fNagykWcDoSVAmSd--

[sane-devel] segfault

[Tim Waugh]

--2fSbKhQ/kwrfWINy
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, May 02, 2002 at 11:12:04PM -0400, Vladimir Dergachev wrote:

> Program received signal SIGSEGV, Segmentation fault.
> sane_sm3600_init (version_code=0xb278, authCB=0x8049270
> )
> at sm3600.c:384
> 384   DBG(DEBUG_JUNK,"found dev %04X/%04X\n",
> (gdb) list
> 379   DBG(DEBUG_JUNK,"scanning bus %s\n", pbus->dirname);
> 380   for (pdev=pbus->devices; pdev; pdev  = pdev->next)
> 381 {
> 382   unsigned short *pidProduct;
> 383   iDev++;
> 384   DBG(DEBUG_JUNK,"found dev %04X/%04X\n",
> 385   pdev->descriptor.idVendor,
> 386   pdev->descriptor.idProduct);
> 387   /* the loop is not SO effective, but straight! */
> 388   for (pidProduct=aidProduct; *pidProduct; pidProduct++)

Hmm, smells like the same thing the gPhoto2 people have been seeing
with libusb.

> (gdb) print pdev

..but unfortunately, you didn't include enough information to be
sure.  Does a recompile of libusb, and the sane, fix the problem?

Tim.
*/

--2fSbKhQ/kwrfWINy
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE80jpxyaXy9qA00+cRAjY1AKCAKCbR+SwgUhemFk0JtltYIp3/aACdFWUf
jhiWHf81h8nTMXMf/8URmSU=
=7HPR
-END PGP SIGNATURE-

--2fSbKhQ/kwrfWINy--

[sane-devel] Problem with network scanning Linux/win98

[Tim Waugh]

--azLHFNyN32YCQGCU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, May 06, 2002 at 06:18:20PM +0200, Edvard Rognlid wrote:
> The newst rpm for redhat 7.2 I could find vas for version 1.0.5-4.

Red Hat Linux 7.3 comes with SANE 1.0.7.  Just grab that packages from
there.

Tim.
*/

--azLHFNyN32YCQGCU
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE813YDyaXy9qA00+cRAv6BAKCb+7TZzpqhbcGqqZ5PiulI3x1KuQCgsqHh
0uuyW5TvOjcfxUkVofkWED4=
=5lKr
-END PGP SIGNATURE-

--azLHFNyN32YCQGCU--

[sane-devel] On upgrading to version 1.0.7 my scsi HP IIcx stops working

[Tim Waugh]

--fQa200R4EO7jAQ6Z
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, May 11, 2002 at 10:02:42PM -0700, Jost Diederichs wrote:

> Thanks to a previous post by Oliver Schwartz=20
> (http://www.mostang.com/pipermail/sane-devel/2002-May/003603.html) that m=
y=20
> problem appears to be caused by a problem with the particular rpm. On=20
> upgrading some links don't get fixed.

Which links?

Tim.
*/

--fQa200R4EO7jAQ6Z
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE83jmgyaXy9qA00+cRAisUAJ9uBc7xwa6TJGLbzpzetiJ74QsaVwCfW/Vs
Fq2ro75IwFnrOV0MLAT4FDw=
=fJ32
-END PGP SIGNATURE-

--fQa200R4EO7jAQ6Z--

[sane-devel] On upgrading to version 1.0.7 my scsi HP IIcx stops working

[Tim Waugh]

--vr1sEM+RgL05fCrX
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, May 12, 2002 at 05:24:39PM -0700, Jost Diederichs wrote:

> I was simply referring to the post of Oliver Schwartz=20
> (http://www.mostang.com/pipermail/sane-devel/2002-May/003603.html).
> Apparently, after upgrading from version 1.0.5 some symbolic links in the=
=20
> lib/sane directory still point to 1.0.5 versions of libraries and become=
=20
> broken.

*sigh*

Which _ones_?  This doesn't happen for me, and without knowing exactly
what to look for I can't fix it in the next version.

> an output of `ln -l | grep >` in the lib/sane directory looks like the=20

That should probably be 'ls -l'.

Tim.
*/

--vr1sEM+RgL05fCrX
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8323JyaXy9qA00+cRArhvAJ9vRP+SNIhZVDzdJFvkbQMiDsu7HACfekKR
lpZhVxBtb9pDeIJXapzObck=
=g012
-END PGP SIGNATURE-

--vr1sEM+RgL05fCrX--

[sane-devel] trouble with sane-1.0.7

[Tim Waugh]

--Iy2CUD6FdotTkhwY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Sun, May 12, 2002 at 05:08:37PM -0700, Jost Diederichs wrote:

> Try completely uninstalling sane. Make sure the lib/sane directory
> is gone and do a fresh install. There a re some previous posts on
> this.  Did you upgrade using the rpm that comes with RedHat 7.3?

No, don't do this---if you do, all evidence of what went wrong will be
lost, and the bug (whatever it is) will never have a chance of being
found.

Instead, why not enable debugging (see the man page) and show us the
output?

Tim.
*/

--Iy2CUD6FdotTkhwY
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE833EvyaXy9qA00+cRAu8xAJ9g16+P/174ahHaABXnGOx9QaghCACglLrc
UpuRdqCx/u4mJUXG5rJVrB4=
=YWdu
-END PGP SIGNATURE-

--Iy2CUD6FdotTkhwY--

[sane-devel] trouble with sane-1.0.7

[Tim Waugh]

--6lCXDTVICvIQMz0h
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, May 13, 2002 at 11:39:04AM -0700, Jost Diederichs wrote:

> I can reproduce the problem
> I rolled back to 1.0.3, upgraded to 1.0.5 and then upgraded to 1.0.7
> See the session log below:

This turned out to be because ldconfig was run before the old files
were cleaned up.  Fixed, and the work-around is to run
'/sbin/ldconfig' as root after upgrading.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=64964

Tim.
*/

--6lCXDTVICvIQMz0h
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE84j+vyaXy9qA00+cRAkm0AJ9rnRiEDo+13zAvgEh66HClWRdJJQCfYTOW
w/uEaNJR2q43nL5XtOqz0vw=
=qJlX
-END PGP SIGNATURE-

--6lCXDTVICvIQMz0h--

[sane-devel] sane-find-scanner finds it, scanimage does not

[Tim Waugh]

--b1ERR0FXR0PvNIRE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Sun, May 26, 2002 at 09:09:45PM -0500, Joel Uckelman wrote:

> I upgraded to RedHat 7.3 yesterday, which apparently has caused my
> Epson 610 to stop working.

This is a known issue that will be addressed shortly.  In the mean
time, you should be able to work around the problem like this:

rpm -e --nodeps sane-backends
rpm -ivh sane-backends-1.0.7-6.i386.rpm

Tim.
*/



--b1ERR0FXR0PvNIRE
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE88eEHyaXy9qA00+cRAmGaAKCSDUtLf+dBiGOtdmgYFXPP+8LCIQCgksI/
4ef4EUsYjGDna6ON/9BQWXU=
=GH1l
-END PGP SIGNATURE-

--b1ERR0FXR0PvNIRE--

[sane-devel] sane-find-scanner finds it, scanimage does not

[Tim Waugh]

--oNLI4EWr1RPQuPCf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, May 27, 2002 at 02:13:10PM -0500, Joel Uckelman wrote:

> Thanks! That did the trick. What does reinstalling the sane-backends=20
> package do that fixes the problem?

It avoids a buggy %postun script in the package being replaced.

Tim.
*/

--oNLI4EWr1RPQuPCf
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE88qt3yaXy9qA00+cRAne7AJ9C1zKS/UGp30xs7D/23BV9iDbrLwCffnCu
jLXBj6/vte6DBm6SjmcVFzE=
=2TKm
-END PGP SIGNATURE-

--oNLI4EWr1RPQuPCf--

[sane-devel] [Fwd: Sane-1.0.8 Compile Failure]

[Tim Waugh]

--IQJz6/4+fVNDccxB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, May 30, 2002 at 05:41:19PM +0200, Henning Meier-Geinitz wrote:

> Has anyone else tested SANE with gcc 3.1? Any problems?

I'm using a GCC 3.1-compiled sane-backends here without any trouble at
all.

Tim.
*/

--IQJz6/4+fVNDccxB
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE89ksWyaXy9qA00+cRAoHoAJwKSBrBtL2gsL5kOBnC8AS0B0PFHQCgq/G+
sjizgFhYKduToksvOM8Ti8A=
=aYs2
-END PGP SIGNATURE-

--IQJz6/4+fVNDccxB--

[ot] Re: [sane-devel] [Fwd: Sane-1.0.8 Compile Failure]

[Tim Waugh]

--FBZZyUSgjpMOo1m2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, May 30, 2002 at 04:09:31PM -0400, Gene Heskett wrote:

> I put it in this morning, then built a bootable kernel with it.  But
> guess what...  Installing it removes a library that much of kde3.0
> needs, so things like kmail and knode won't run if gcc "3.1-4" has
> been installed from a rawhide mirror.  It sure would be nice if the
> left hand had a clue what the right one was doing.

You need a matching set of hands.  Use the KDE 3.0.1 RPMs, also from
rawhide.

Tim.
*/

--FBZZyUSgjpMOo1m2
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE89oPpyaXy9qA00+cRApGfAJ4tulZhAP7aVgHqlNIMUTxOSwXqoACdHhRt
K8hDuM/f6CoV1YILeiKAnrA=
=e9LO
-END PGP SIGNATURE-

--FBZZyUSgjpMOo1m2--

[sane-devel] Found: why Sane make barfed under RH6.1

[Tim Waugh]

--Qn4G1eBrv+t66M9q
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, Mar 14, 2002 at 10:10:15AM +0300, Max Ushakov wrote:

> So maybe it is still correct to use all kernel includes instead
> of the corresponding glibc includes.

It is not.

Tim.
*/

--Qn4G1eBrv+t66M9q
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8kGrJyaXy9qA00+cRAoEgAJ9Cfe1WTngQ+d9d8PIHegimSAJCtQCgml7O
m2ztuq/rc0Ntih7Yv7fvmMg=
=lmv2
-END PGP SIGNATURE-

--Qn4G1eBrv+t66M9q--

[sane-devel] RedHat 7.3 + scanimage (no scanners identified)

[Tim Waugh]

--6HG4v7gMkvDRbcUW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, Jun 03, 2002 at 05:49:23PM +, snowkr...@altavista.nl wrote:

> I've done a fresh RH 7.3 install last weekend.

Apply the updates (use up2date).  This bug is fixed.

Tim.
*/

--6HG4v7gMkvDRbcUW
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9AiWxyaXy9qA00+cRAohMAJwMJmdPY5lifcEPGI8I+tD8z7TSqQCgmL6w
E5HxTqpUi1SCzDUA8fry4sA=
=/KYY
-END PGP SIGNATURE-

--6HG4v7gMkvDRbcUW--

[sane-devel] Epson GT-8200U: "Could not send command to scanner"

[Tim Waugh]

--YCD1IDpPCSHWAycC
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, Jun 20, 2002 at 07:05:21PM -0700, Steve Frampton wrote:

>   sane-backends-1.0.7-6

You want to fetch the updated package (1.0.7-6.1) for 7.3 from
updates.redhat.com.

Tim.
*/

--YCD1IDpPCSHWAycC
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9Eso+yaXy9qA00+cRAlJ3AJoCqxFfm9vc4rPfopyxVSurT/V2DgCghZhV
McVu+QeeinWFl4QYDYJBbF0=
=rUWe
-END PGP SIGNATURE-

--YCD1IDpPCSHWAycC--

[sane-devel] Default path for USB device .conf files

[Tim Waugh]

--lVyydWNEvA8xBB0C
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Is there any good reason not to use (for example) '/dev/usb/scanner0'
instead of '/dev/usbscanner0' in the various SANE .conf files?

Tim.
*/

--lVyydWNEvA8xBB0C
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9Ev/9yaXy9qA00+cRAqDjAJ4n/7AF9EFfnEnSrQ/tYwBTksUzSACfV3+O
ov1eeyEAWWesSF4pQoBrPnM=
=v2Zu
-END PGP SIGNATURE-

--lVyydWNEvA8xBB0C--

[sane-devel] ppdev bug?

[Tim Waugh]

--fUvfsPTz/SzOZDdw
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

What is the 'ppdev bug' mentioned in the recent sane CVS commit
message?

Tim.
*/

--fUvfsPTz/SzOZDdw
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9HbQQyaXy9qA00+cRApbFAJ9Cb+3UWhbpi65AA8i4W72e4R4B2QCgs6hO
vvXOaJCijenO3F5BBAiZOg8=
=tHuJ
-END PGP SIGNATURE-

--fUvfsPTz/SzOZDdw--

[sane-devel] ppdev bug?

[Tim Waugh]

--6CiRFyVmOOJ3DkBX
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Sat, Jun 29, 2002 at 11:34:02PM +1000, Matthew Duggan wrote:

> I mentioned it in linux-parport and cc'd you..  it can block
> indefinately on 0 byte reads.

Oh that, okay.

Thanks for the patch by the way; it looks right to me.

Tim.
*/

--6CiRFyVmOOJ3DkBX
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9HcPLyaXy9qA00+cRAk61AJ9w7Xk82s0wcax2ExytMEktlsm+wgCeOe44
GzGqQpVvkCR+xRv+n8SJ4fg=
=1tLo
-END PGP SIGNATURE-

--6CiRFyVmOOJ3DkBX--

[sane-devel] HP ScanJet 5p on RH7.3 Linux?

[Tim Waugh]

--eZmbrWU10I35niuH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Aug 28, 2002 at 01:15:28AM +0300, Otto J. Makela wrote:

> In principle, the HP ScanJet 5p should be a easy, SCSI-attached
> scanner well-supported by Linux.
>=20
> But no, I can't quite get it working when attached to a BusLogic SCSI
> card I have on my RH7.3 machine (I didn't even bother trying the
> pseudo-SCSI card that came with the scanner):

It works for me, connected to an Adaptec aic7870.

Tim.
*/

--eZmbrWU10I35niuH
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9a/wOyaXy9qA00+cRAtnCAKCugcECbLw0neWs1z65z7pwLaDirQCfWhe4
6MnXLGo960We8Z9HOL/Dz0U=
=FiIL
-END PGP SIGNATURE-

--eZmbrWU10I35niuH--

[sane-devel] 'read more data than announced by backend'

[Tim Waugh]

--AQYPrgrEUc/1pSX1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

I received this bug report:



"I have a Microtek ScanMaker E6.  I have sane-backends-1.0.7-6 and
 related versions installed.  I am running kernel 2.4.18-ac3.

 Every time I scan a LineArt image with scanimage, I get this message
 at the end:

 scanimage: WARNING: read more data than announced by backend
 (4203960/4198236)

 Then, the next time I attempt to use scanimage, the scanner clicks a
 couple of times and does nothing, and then scanimage reports:

 scanimage: sane_start: Error during device I/O

 While this is happening, these messages show up in my dmesg output:

 scsi0:0:4:0: Attempting to queue a TARGET RESET message
 scsi0:0:4:0: Command not found
 aic7xxx_dev_reset returns 0x2002
 scsi: device set offline - not ready or command retry failed after bus
 reset: host 0 channel 0 id 4 lun 0

 The only way I've found to get the scanner working again at this
 point is to use "echo scsi remove-single-device ... >
 /proc/scsi/scsi" and then "echo scsi add-single-device ... >
 /proc/scsi/scsi".

 Note: I don't know if the "read more data" problem is related to the
 other problem, but I'm mentioning it just in case it is.

 Note 2: The data read by the scanimage, when it's working, seems just
 fine.

 Note 3: This happens whether I pass "--calib_once no" or
 "--calib_once yes" to scanimage."

I don't really know where to start with this.  Does it sound like a
SANE problem or a kernel one?

Thanks,
Tim.
*/

--AQYPrgrEUc/1pSX1
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8tCL6yaXy9qA00+cRAkqsAJ9rb08reUduOAjg4xstlcS1YDd8MACgu2E+
9e9w+wiZrhnDE/f/2aOSOHk=
=JWLe
-END PGP SIGNATURE-

--AQYPrgrEUc/1pSX1--

[sane-devel] [patch] Fix up error checking in canon backend

[Tim Waugh]

Hi,

Here is a patch to fix a crash in the canon backend.  More details at:
.

Tim.
*/

--- sane-backends-1.0.9/backend/canon-sane.c.errorchk   2003-01-09 
11:52:50.0 +
+++ sane-backends-1.0.9/backend/canon-sane.c2003-01-09 11:54:30.0 
+
@@ -1242,7 +1242,9 @@
   if ((s->hw->info.model != FB620) &&  /* modification for FB620S */
   (s->val[OPT_PREVIEW].w == SANE_FALSE) && (s->AF_NOW == SANE_TRUE))
 {
-  do_focus (s);
+  status = do_focus (s);
+  if (status != SANE_STATUS_GOOD)
+   return status;
   if (s->val[OPT_AF_ONCE].w == SANE_TRUE)
{
  s->AF_NOW = SANE_FALSE;
@@ -1251,7 +1253,9 @@
 
   if (s->val[OPT_CUSTOM_GAMMA].w == 1)
 {
-  do_gamma (s);
+  status = do_gamma (s);
+  if (status != SANE_STATUS_GOOD)
+   return status;
 }
 
 #if 1

[sane-devel] Where can I find ppscsi driver?

[Tim Waugh]

--+ts6NCQ4mrNQIV8p
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, Jan 16, 2003 at 09:04:54AM +0100, Marcel Pol wrote:

> There doesn't seem to be a patch for 2.4, but there is one for 2.5.
> The cvs patch should contain the ppscsi drivers too though I do not know if
> that is for 2.4 or 2.5.
> http://people.redhat.com/twaugh/ftp/patches/
> Maybe the best thing is to ask Tim Waugh directly?

No, don't do that. :-)

> Maybe the 2.5 patch works
> ok for 2.4 too. He should also be able to tell if it is being maintained or
> not. Last thing I know was that he was looking for a maintainer because he
> didn't have time for it.

I think Jon Miner has been doing some work on ppSCSI.
https://trainguy.dyn.dhs.org/ppSCSI/

Tim.
*/

--+ts6NCQ4mrNQIV8p
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+Jn/CtO8Ac4jnUq4RAo4EAKCUJRnVthZW3G10zxP4ihBxrUDtAgCeNaUx
f6aZXxD5vGle17KFjeSSmt8=
=BwC+
-END PGP SIGNATURE-

--+ts6NCQ4mrNQIV8p--

[sane-devel] XSane-0.90 released

[Tim Waugh]

--x8hBN3jcr0uqJpm2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hi Oliver,

It would be nice to have a configure option for which browser to use
for displaying HTML help.  Currently 'netscape' seems to be interwoven
into the source code, and I'm scared to change it. :-)

Tim.
*/

--x8hBN3jcr0uqJpm2
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+k9pjtO8Ac4jnUq4RAn6RAJ0S7sYBbP6N+26ntENTpHqgH5f6JwCgo2rw
5ZhhRjL6tXzPl2b+88YkMok=
=HKuA
-END PGP SIGNATURE-

--x8hBN3jcr0uqJpm2--

[sane-devel] Re: ppscsi for kernel 2.4

[Tim Waugh]

--iig7nzZQzi/oiJm2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Apr 20, 2003 at 01:32:35AM +0200, Till Kamppeter wrote:

> Tim, can you perhaps put the patch for kernel 2.4.21 onto your FTP site?=
=20
> Thank you.

I'm afraid I no longer maintain the ppSCSI patch due to lack of time.

Sorry,
Tim.
*/

--iig7nzZQzi/oiJm2
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+qYC2tO8Ac4jnUq4RAiqoAJ9xD8Q0lAUW3lawk3WQBAeCE5qLZACgvNIX
FSbdxrNy2u7gATmt8/rsBAQ=
=jgXF
-END PGP SIGNATURE-

--iig7nzZQzi/oiJm2--

[sane-devel] Re: ppscsi for kernel 2.4

[Tim Waugh]

--7phR3qVEw/4Cnor3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Apr 25, 2003 at 08:45:13PM +0200, Till Kamppeter wrote:

> Will someone else at Red Hat do it or will the patch be removed from the=
=20
> Red Hat kernels?

Red Hat doesn't ship this patch.  Perhaps someone at Mandrake should
take over maintenance of it. ;-)

> Anyone on the list who wants to overtake the maintainership of this=20
> patch so that parallel scanners stay supported under Linux?

FWIW, I already asked several times last year on the linux-parport
list, but there was no response.

> Tim, can you make a tarball of the web site and the downloadable
> stuff before you shut down the site, so that it can be moved to a
> new place?

Easier for me to just not shut it down.  I don't tend to remove stuff
unless I need to.

Tim.
*/

--7phR3qVEw/4Cnor3
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+q6JitO8Ac4jnUq4RAkn/AJ97Ffx/Nmg0z7zksIFwnCdpAjXP3QCfYpIh
wjA1qGVNsjCOaK609/AAVu4=
=pZ8u
-END PGP SIGNATURE-

--7phR3qVEw/4Cnor3--

[sane-devel] Sane Question--umax_pp

[Tim Waugh]

--AA9g+nFNFPYNJKiL
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Dec 28, 2001 at 12:38:39AM +, Timothy Johnson wrote:

> creating a ppdev character device.  I read somewhere that the ppdev=20
> module uses the parport, but I also seem to remember the documentation=20
> saying that a ppdev character device may need to be created in order to=
=20
> use the scanner as a regular user.  How does this fit together?

There was a bug in an earlier 2.4.x kernel that you might be running
into: is the parport_pc module also loaded?  If not you'll need to
load it.

ppdev is the device driver (kernel module) behind /dev/parport0; if
you don't have that you'll need to create it first with 'mknod
/dev/parport0 c 99 0'.  The ppdev device driver, in turn, uses the
parport subsystem, which is contained in the 'parport' kernel module.
That driver just provides port sharing and some common port
operations, leaving the actual mechanics of driving the port up to the
'parport_pc' kernel module (for PC-style ports).

For ppdev to provide port access to a non-root user, all three of the
above modules need to be loaded, and /dev/parport0 needs to exist and
be accessible (rw).

Tim.
*/

--AA9g+nFNFPYNJKiL
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8NEhzyaXy9qA00+cRAqkNAJsHDVaN0MzqbvUrc1poqzZ0RIsxxwCfY1rF
R69f11ou7gXN6rU7w5Lw0Ag=
=40ls
-END PGP SIGNATURE-

--AA9g+nFNFPYNJKiL--

[sane-devel] Temp file races

[Tim Waugh]

--l118U0+vX1D/6gtA
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Jan 18, 2002 at 12:25:34AM +0100, abel deuring wrote:

> Henning Meier-Geinitz wrote:
>=20
> > There are some ways to avoid this:
> >=20
> > * don't use temp files at all
> > * don't create them in a world writeable directory, use the HOME direct=
ory
> > * use open together with the flag O_EXCL and O_CREAT to make sure, that=
 the
> >   file (or a symlink) doesn't exist.
> > * use mkstemp. This is probably the best but I don't know how many plat=
forms
> >   support it.
>=20
> What about a library function?

Indeed: mkstemp(3) is there for you to use (and you can use fdopen(3)
on the file descriptor to get a FILE*).  Also there is tmpfile(3),
which should also be safe.

Basically: if it's a temporary file, use one of those two functions,
and not open or fopen.

Tim.
*/

--l118U0+vX1D/6gtA
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8R+A3yaXy9qA00+cRAk6LAKCjCaLFgGAr+5Ohs3sZDNQSoOHPXgCgk+2u
AbJ6StfsTLZColJ5jRAGjTw=
=Z6iS
-END PGP SIGNATURE-

--l118U0+vX1D/6gtA--

[sane-devel] C undefined operations in sane-backends-1.0.7-beta1

[Tim Waugh]

--YhFoJY/gx7awiIuK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

I get these warnings when compiling sane-backends-1.0.7-beta1.  They
are for things like:

bit = ++bit % 8;

which are indeed undefined.

Tim.
*/

microtek2.c:8054: warning: operation on `bit' may be undefined
mustek.c:4574: warning: operation on `ptr' may be undefined
mustek.c:4584: warning: operation on `ptr' may be undefined
mustek_usb.c:1294: warning: operation on `status' may be undefined
plustek-usbshading.c:1056: warning: operation on `wR' may be undefined
plustek-usbshading.c:1059: warning: operation on `wG' may be undefined
plustek-usbshading.c:1062: warning: operation on `wB' may be undefined
plustek-usbshading.c:1090: warning: operation on `wR' may be undefined
plustek-usbshading.c:1092: warning: operation on `wG' may be undefined
plustek-usbshading.c:1094: warning: operation on `wB' may be undefined
plustek-usbshading.c:1168: warning: operation on `wV' may be undefined
plustek-usbshading.c:1186: warning: operation on `wV' may be undefined

--YhFoJY/gx7awiIuK
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8ToiqyaXy9qA00+cRAifSAJ9t7YiqfCCIqBDNRkQ05FHuWL6whQCghgPe
fTQAc0m1kjfLAVCy1ge5//s=
=322a
-END PGP SIGNATURE-

--YhFoJY/gx7awiIuK--

[sane-devel] C undefined operations in sane-backends-1.0.7-beta1

[Tim Waugh]

--2mNuWrpDTYoom6W8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Jan 23, 2002 at 09:43:35PM +0100, Henning Meier-Geinitz wrote:

> This is with gcc-3.x? I don't get them with gcc 2.95.4.

Yes.

> > They
> > are for things like:
> >=20
> > bit =3D ++bit % 8;
> >=20
> > which are indeed undefined.
>=20
> Because it's not clear if bit should be incremented and then the right
> side assigned to it or vice versa? Or what's the excat problem?

Yes, that's right.  There is only one sequence point in 'bit =3D ++bit %
8;', at the end, and so the operations can happen in any order.  There
are two assignments to 'bit': the '=3D' operation and the '++'
operation.

Tim.
*/

--2mNuWrpDTYoom6W8
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8TzyfyaXy9qA00+cRAjx6AJ9M1v7C2u+fXf5O8WlnLHa+ycLdDwCgiSrC
sv/4ha/l/xyC63xuKYVeaEI=
=Af0O
-END PGP SIGNATURE-

--2mNuWrpDTYoom6W8--

[sane-devel] C undefined operations in sane-backends-1.0.7-beta1

[Tim Waugh]

--sdOeJE8sLwpQaOMV
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, Jan 24, 2002 at 08:12:53AM +0100, Karsten Festag wrote:

> in the two lines
>  bit = ++bit;

This will give the same warning of course!

>  bit %= 8;

Why not just use bit = (bit + 1) % 8, which appears to be the intent?

Tim.
*/

--sdOeJE8sLwpQaOMV
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8T8+YyaXy9qA00+cRAn2hAKCu5uULGFaFXiIkf1Eb5IsHPnDTgQCgtLNB
Snsqq7qACLMKYMaxVE4/5lM=
=yBzt
-END PGP SIGNATURE-

--sdOeJE8sLwpQaOMV--

[sane-devel] C undefined operations in sane-backends-1.0.7-b

[Tim Waugh]

--RacQGezy2Y99S6cT
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, Jan 24, 2002 at 08:49:56AM +0100, Joachim Backes wrote:

> 1. Since 20 years, C is my favorite programming language

C has become defined better in recent years.  Take a read of C99, for
instance.

> 2. Since some years, I give classes in C
> 3. The code line "bit = ++bit % 8", is fully correct.
>Reason:
>   a) ++ has higher priority than %
>   b) What happens: i) bit will be incremented
>ii) the modulo 8 operation is done
>iii) the result will be stored in bit

There are two assignments to the same variable with no sequence points
in between, and so the compiler is free to order them any way it feels
is better.  Take a read of C99.

> 4. Meaning of "bit = ++bit"??? The same does "++bit"

Well, only because either order happens to produce the same result.

> 5. None of my C compilers (gcc or IRIX c compiler) report
>any warning.

GCC doesn't yet, but it will.  Try CVS, for instance (which is what
I'm using).

I don't expect that any compilers you are using issue warnings for (to
take a wild example) spelling mistakes in string literals either!  It
doesn't mean that there are none.

> 7. The compiler which produces the warning is buggy!

You'd better stay away from GCC then, for fear of 'bugs'.

This list is hardly a good forum for this issue though; perhaps
comp.std.c or something would be a better place for you to raise your
concern.

Tim.
*/

--RacQGezy2Y99S6cT
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8T9DCyaXy9qA00+cRArmAAJwOAbib/gm0oT7VZ9yDsiTC3bIsOgCgo/cq
N/1LaZ80CRZf0avoXA2eo6k=
=rEZy
-END PGP SIGNATURE-

--RacQGezy2Y99S6cT--

[sane-devel] C undefined operations in sane-backends-1.0.7-beta1

[Tim Waugh]

--WulRBKvtygI9tSt8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Jan 24, 2002 at 08:17:25PM +0100, Karsten Festag wrote:

> I read somewhere that ++bit would give faster code than bit =3D bit + 1.
> Now my question (as a non-expierienced programmer) is if
>=20
> ++bit;
> bit %=3D 8;
>=20
> is faster than your suggestion or do you think it makes no difference?

I think it can only be slower, since unless bit is a register then it
requires another memory store.

In general, write code for maintainability rather than speed; compiler
optimizations get better with time, and particular problem areas can
be found using profiling tools if need be.

Tim.
*/

--WulRBKvtygI9tSt8
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8UICMyaXy9qA00+cRAtU9AJ9nGXQBodYKBaIVWwB3czmW1YTo1gCfcuVb
U/ef3nkseGFublhH4KmnSj0=
=udFI
-END PGP SIGNATURE-

--WulRBKvtygI9tSt8--

[sane-devel] C undefined operations in sane-backends-1.0.7-beta1

[Tim Waugh]

--lBe/Si07TENnq+bY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Jan 25, 2002 at 12:27:03PM +0100, Jaeger, Gerhard wrote:

> Hi there,=20
>=20
> let's have a look at the warnings from the Plustek backend.
> The lines that produce the problem include the following statement:
>=20
> _SWAP(x,y)(x)^=3D(y)^=3D(x)^=3D(y)
>=20
> So what? Where's the problem here?

I think the problem is that there are two assignments to x with no
intervening sequence point.  Although the expression (x)^=3D(y) is
_evaluated_ first, it doesn't mean that the resulting value is then
assigned to x before the result of the expression (y)^=3D(x)^=3D(y) is;
the compiler is free to do it the other way around.

Tim.
*/

--lBe/Si07TENnq+bY
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8UUOeyaXy9qA00+cRAru7AJ9odTewG5E6uSArWyUQwHxl5m7KSwCeN25M
IUdaBZk4qW0I/MTNe7zUkiw=
=WpiC
-END PGP SIGNATURE-

--lBe/Si07TENnq+bY--

[sane-devel] only grey scans from epson backend?

[Tim Waugh]

--m+Z5/NEwv9nnRDo7
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

I received the following bug report:



"When scanning using the Epson backend, colour scans come out in
 greyscale only. This is with xsane, xscanimage and scanimage.
 [...]
 I'm using an Epson GT7000 SCSI scanner, connected to a Tekram
 DC-395UW SCSI controller. Kernel is 2.4.17, with Kurt Garloff's
 Tekram driver patch.

 This same setup (an earlier kernel, with the same patch) worked
 fine on RH7.1 on the same machine. When I upgraded to 7.2, it
 refused to scan in colour."

(Red Hat Linux 7.2 comes with SANE 1.0.5.)

Has anyone else seen this?

Tim.
*/

--m+Z5/NEwv9nnRDo7
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8YXCPyaXy9qA00+cRArjfAJ9twfbHcyBHSE8E6Vl5FjOloWqdmwCfWomP
5rggfQesYAj4zhwypGt4upw=
=a457
-END PGP SIGNATURE-

--m+Z5/NEwv9nnRDo7--

[sane-devel] only grey scans from epson backend?

[Tim Waugh]

--PZMMlDKQNsLDNvB8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

> 

Oh, never mind, false alarm.

Tim.
*/

--PZMMlDKQNsLDNvB8
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8YbKnyaXy9qA00+cRApcsAJ9v5OAmj/5lgA2R6tKiDNIZHHBr8ACdEj+t
A2TYnV3Ef9cxVPdOXY3qwHg=
=ayO7
-END PGP SIGNATURE-

--PZMMlDKQNsLDNvB8--

[sane-devel] sane-config --cflags output

[Tim Waugh]

sane-config --cflags shouldn't say '-I/usr/include', since that's the
default include path anyway; similarly, sane-config --libs shouldn't
say '-lc' (and it doesn't).

Here is a patch to fix the output of sane-config --cflags.

Tim.
*/

--- sane-backends-1.0.7/tools/sane-config.in.defaultinclMon Feb 11 
09:38:25 2002
+++ sane-backends-1.0.7/tools/sane-config.inMon Feb 11 09:39:37 2002
@@ -92,7 +92,10 @@
   echo "-lsane ${LIBS}"
   ;;
 --cflags)
-  unique_cflags="-I${includedir}"
+  unique_cflags=
+  if test "${includedir}" != "/usr/include"; then
+unique_cflags="${unique_cflags} -I${includedir}"
+  fi
   for i in $cflags; do
 if test $i != $includedir; then
   unique_cflags="${unique_cflags} $i"

[sane-devel] sane-config --cflags output

[Tim Waugh]

--v541l457l4DThMFo
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, Feb 11, 2002 at 08:47:56PM +0100, Henning Meier-Geinitz wrote:

> What is the problem with explicitely mentioning "/usr/include"? Does
> it break anything or makes it much slower?

The specific problem is that newer GCCs will emit a warning, like
this:

cc1: warning: changing search order for system directory "/usr/include"
cc1: warning:   as it has already been specified as a non-system directory

In some cases this can break configure scripts, unfortunately.

Tim.
*/

--v541l457l4DThMFo
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8aEvVyaXy9qA00+cRAiRkAKC3L9qPfC5flaPAuprQ9mF1UcR+XwCeIKi9
ESyjPxnEVKBRUHx2mSWZGlk=
=+4XU
-END PGP SIGNATURE-

--v541l457l4DThMFo--

[sane-devel] 'scanimage -L' fails first time with modular SCSI drivers

[Tim Waugh]

--gdTfX7fkYsEEjebm
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Linux, when the SCSI drivers are compiled modular, 'scanimage -L'
fails unless they modules are loaded.

After running it once (and it fails), the drivers appear to have been
automatically loaded (by an open("/dev/sg0") I think), and so a
subsequent 'scanimage -L' works.

[root@cyberelk root]# scanimage -L

No scanners were identified. If you were expecting something
different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
[root@cyberelk root]# scanimage -L
device `hp:/dev/sg0' is a Hewlett-Packard C5110A flatbed scanner

Curiously enough, if I create a link /dev/scanner -> sg0, I don't see
this behaviour and the first 'scanimage -L' succeeds.

I'm trying this with SANE 1.0.7.

Tim.
*/

--gdTfX7fkYsEEjebm
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8cmPXyaXy9qA00+cRAvbKAKC6xkBEvVFm6Uwaw2oab1um3kJ21wCfQYqZ
3QiE99c/ABsBTQy/cOUS09k=
=lEak
-END PGP SIGNATURE-

--gdTfX7fkYsEEjebm--

[sane-devel] 'scanimage -L' fails first time with modular SCSI drivers

[Tim Waugh]

--nywXBoy70X0GaB8B
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Tue, Feb 19, 2002 at 04:13:00PM +0100, abel deuring wrote:

> Don't know, if this is related, but the Sharp backend has the bug that
> it considers the REQUEST SENSE result "power on reset" to be an error.
> So, if you have only /dev/sg0, no /dev/scanner, scanimage -L fails, if
> the scanner was power-cycled after the SCSI driver module has been
> loaded. With /dev/scanner present, detecting the scanner at either
> /dev/scanner or /dev/sg0 (the one being accessed first, don't know which
> it is...) will fail, but accessing the second device file will succeed.
> A second "scanimage -L" will then show two scanners, attached to
> /dev/sg0 and /dev/scanner.

This sounds like it might be a separate problem: I am using the hp
backend.  Also, the scanner remains powered throughout.

Tim.
*/

--nywXBoy70X0GaB8B
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8cmvmyaXy9qA00+cRAvrWAJwOPkK6hgwGt0V3iZlN6LZMQc1PXgCgjQ+q
t4worzrWjMrxqFPKgTJ6yX0=
=Fj4F
-END PGP SIGNATURE-

--nywXBoy70X0GaB8B--

[sane-devel] 'scanimage -L' fails first time with modular SCSI drivers

[Tim Waugh]

--4HoONH8zr3Mj5MZN
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Tue, Feb 19, 2002 at 08:05:20PM +0100, Henning Meier-Geinitz wrote:

> I think the analysis of Andras is right.

Could we add some hook to try to get the modules loaded if
/proc/scsi/scsi doesn't exist?  Just opening a generic SCSI device is
enough to load them.

Tim.
*/


--4HoONH8zr3Mj5MZN
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8dk9myaXy9qA00+cRAj1fAJ4rU0UfH5znIHEYT0y7OnxkcM2FyACgkI6q
oQ+W/mf5k6nmly+NurZhoNw=
=yAIV
-END PGP SIGNATURE-

--4HoONH8zr3Mj5MZN--

[sane-devel] 'scanimage -L' fails first time with modular SCSI drivers

[Tim Waugh]

--Sh9dYexoRflRb0jn
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Feb 24, 2002 at 02:38:25PM +0100, Henning Meier-Geinitz wrote:

> On Fri, Feb 22, 2002 at 02:02:14PM +0000, Tim Waugh wrote:
> > Could we add some hook to try to get the modules loaded if
> > /proc/scsi/scsi doesn't exist?  Just opening a generic SCSI device is
> > enough to load them.
>=20
> Is anybody against the following patch?

Perhaps I should have tested my theory first, before suggesting it.
I've tried this patch, and it does exactly as advertised (the modules
are now loaded and /proc/scsi/scsi contains useful information when
read), but for some reason it doesn't fix the problem.

It still fails the first time, and succeeds the next.  The output of
'strace -eopen,read,ioctl scanimage -L' differs between the first and
second times only in two respects:

a) the first contains some open() retries for /dev/sg0, since the
   modules are being loaded (this is expected);
b) the information read from /dev/sg0 is different.

I can't quite figure out why this is happening.  Perhaps it's a timing
thing, but I tried putting a 10-second sleep as a post-install for the
sg module, and it made no difference.

Besides this, I think that the patch is good. ;-)  It is a necessary
hook I think.  As Oliver said though, perhaps it should be a list.

Tim.
*/

--Sh9dYexoRflRb0jn
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8ell3yaXy9qA00+cRAqKtAJoCUm/Fox+8/Ae2BFB4XAMfg3ASfQCaA+ee
vzZQfPYat/vC2ZrNaG0ENaU=
=uXnO
-END PGP SIGNATURE-

--Sh9dYexoRflRb0jn--

[sane-devel] 'scanimage -L' fails first time with modular SCSI drivers

[Tim Waugh]

--zGX6P/PxmcOG18lb
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, Feb 25, 2002 at 11:24:44PM +0100, Oliver Rauch wrote:

> BTW: What happens when the user does not have the correct permissions
> for /dev/sg0 (or the device that is used to load modules)?

Oh, good point: really it ought to try /dev/sg0, /dev/sg1, etc until
it finds one that works.

Tim.
*/

--zGX6P/PxmcOG18lb
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8er02yaXy9qA00+cRAlKvAJ9zfEM//HHBCXaX2y8/EjrpOErAeACePKda
Lsc+SrVyzd7d4b2C/hOSyuE=
=ggHe
-END PGP SIGNATURE-

--zGX6P/PxmcOG18lb--

[sane-devel] sanei_parport

[Tim Waugh]

--l+LxDeyHMCBjwres
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Feb 26, 2002 at 05:29:46PM +0300, Max Vorobiev wrote:

> Is there are any discussion threads or requirements for sanei_parport=20
> interface?

Take a look at libieee1284: basically there shouldn't be a lot of
extra code needed to make sanei_parport.

Tim.
*/

--l+LxDeyHMCBjwres
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8e5zPyaXy9qA00+cRAlOkAJ46ima2jWypY4X7NZXJcjB13xFIIQCdH3Tc
1vwZi4KIz7VfuqmJttnY5MQ=
=58D1
-END PGP SIGNATURE-

--l+LxDeyHMCBjwres--

[sane-devel] Download problem @ ftp.mostang.com/pub/sane/sane-1.0.5

[Tim Waugh]

--o99acAvKqrTZeiCU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Sep 27, 2001 at 05:24:59AM +, Graeme Nichols wrote:

> As far as finding an rpm for RedHat 7.1 is concerned the only rpm is=20
> 1.0.3. (and that's for RH 7.0) That's the only rpm for RH listed on the=
=20
> mostang site as well.

The current Red Hat Rawhide tree has SANE 1.0.5, and so does the
latest Red Hat Linux beta release (Roswell).

ftp:///redhat/linux/rawhide/i386/RedHat/RPMS

Note that it is now packaged in two parts: sane-frontends and
sane-backends.

Tim.
*/

--o99acAvKqrTZeiCU
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7sv51yaXy9qA00+cRAj6gAJ9y95yeBVM6smWI5UqinMTumfmkvACePozx
fTwlHHf2Tvh8Cx7URQe7SLk=
=+3Hw
-END PGP SIGNATURE-

--o99acAvKqrTZeiCU--

[sane-devel] sane nikon coolscan

[Tim Waugh]

--JaBjgNvtdKe5H086
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Oct 13, 2001 at 11:39:39PM -0700, Hidong Kim wrote:

> I'm trying to install a Nikon Coolscan LS-2000 on my Red Hat 7.1=20
> machine.  I recompiled the 2.4.2-2 kernel to support the SCSI interface=
=20
> for this scanner, an Adaptec AVA-2903B.  (It uses the aic7xxx driver.) =
=20
> The computer appears to recognize the SCSI host and the scanner fine. =20
[...]

As Abel Deuring pointed out, this is likely to be due to not having
the permissions on the device.

If you make a symbolic link '/dev/camera' to the right device
(probably sg0), then it will be accessible to you when you log in at
the console.

ln -sf sg0 /dev/camera

Tim.
*/

--JaBjgNvtdKe5H086
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7ygHPyaXy9qA00+cRAsxaAKCVmOJUjDjpvPnZd2wl8sgs4sNtRQCdEh8J
RhL4V2Nto/4HYBJpmTolSFE=
=O87i
-END PGP SIGNATURE-

--JaBjgNvtdKe5H086--

[sane-devel] [patch] fix SCSI device matching

[Tim Waugh]

When a SCSI device returns a blank string field (such as the vendor
field), sanei_scsi_find_devices gets confused.

See .

I append a patch that I think will fix it.  What do you think?

Tim.
*/

Index: sane-backends/sanei/sanei_scsi.c
===
RCS file: /cvsroot/external/sane/sane-backends/sanei/sanei_scsi.c,v
retrieving revision 1.25
diff -d -u -r1.25 sanei_scsi.c
--- sanei_scsi.c2001/09/21 11:29:13 1.25
+++ sanei_scsi.c2001/10/25 17:19:29
@@ -2511,6 +2511,13 @@
  else
 *param[i].u.i = 0;
}
+ else if (i < NELEMS (param) &&
+  strncmp (string, param[i + 1].name,
+   param[i + 1].name_len) == 0)
+   {
+ /* Seems like this field is all whitespace */
+ param[i].u.str[0] = '\0';
+   }
  else
{
  strncpy (param[i].u.str, string, 32);

[sane-devel] [patch] fix SCSI device matching

[Tim Waugh]

--JXp+Qf9qmD+BnmMb
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Oh, never mind, I just saw the patch in CVS which does this already
(albeit with slightly more code).

Tim.
*/

--JXp+Qf9qmD+BnmMb
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE72TKQyaXy9qA00+cRAntbAKCHUFQQ0DHyffkqC+dYOn3xAAVMhgCfW5Rg
iIDESHmli+ZDizfQpGIB1q8=
=6sqs
-END PGP SIGNATURE-

--JXp+Qf9qmD+BnmMb--

[sane-devel] Querying scanner buttons

[Tim Waugh]

--mpbdVK9pqhR9zQdg
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, Oct 29, 2001 at 11:12:25AM +0100, Michael Piotrowski wrote:

> Now, since my EPSON 1640 scanner has a button, it would be nice if I
> could "read" it in the script above instead of having to hit Return on
> the keyboard (which is sometimes difficult while trying to make sure
> that the source on the scanner doesn't move).

Does '--button-wait=yes' work for your scanner?

Tim.
*/

--mpbdVK9pqhR9zQdg
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE73TCIyaXy9qA00+cRAtoNAJoCODWPrkKgeIIFSoFx+QxTReI77QCgn6TG
EEoBSq+6yFwUDe/0W5YxOPo=
=vfF5
-END PGP SIGNATURE-

--mpbdVK9pqhR9zQdg--

[sane-devel] Querying scanner buttons

[Tim Waugh]

--6rcv1UvST9/bVzIi
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, Oct 29, 2001 at 11:41:31AM +0100, Michael Piotrowski wrote:

> Is that a CVS feature? Or is it backend-specific? My scanimage 1.0.5
> with the EPSON backend doesn't know it.

I think it must be a backend-specific one (I am using the hp backend).

Tim.
*/

--6rcv1UvST9/bVzIi
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE73Tx3yaXy9qA00+cRArYHAKCQNUQf5Dd8nlOW6Us0nsPD1/kKLwCfQDF5
CVlfySdqDTd2PfC3lrsSRGw=
=FzNA
-END PGP SIGNATURE-

--6rcv1UvST9/bVzIi--

[sane-devel] gphoto2 backend

[Tim Waugh]

--HtRZva1Vzv8iP5ye
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

The gphoto2 CVS no longer has a gphoto2-core.h, but aclocal.m4 and
acinclude.m4 check for it.

Tim.
*/

--HtRZva1Vzv8iP5ye
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE73suHyaXy9qA00+cRAnJtAJ96tw6VyvLC/hYngVJsLwcbpA8dpACdHBmI
xLvqutNSWSf6EfBl/FUvndg=
=7FEV
-END PGP SIGNATURE-

--HtRZva1Vzv8iP5ye--

[sane-devel] [dev] CVS tree closed for release

[Tim Waugh]

--5IYJRsx6KNVuKrR5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Nov 04, 2001 at 02:47:19PM +0100, abel deuring wrote:

> Eric observed this for kernel 2.4.9; I saw it for 2.4.5 and 2.4.13,
> while 2.4.0 works fine.
>=20
> I know that Sane 1.0.6 is due to be released, but I'm afraid that we'll
> get more and more error reports as people will install newer kernels.
> OTOH, the fix is really simple. It is sufficient to disable lines 2179
> ..2183 in sanei_scsi.c:

Is the kernel fix known?

Tim.
*/

--5IYJRsx6KNVuKrR5
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE75Un9yaXy9qA00+cRAhe6AKCRcBolFeSvI9sP3jhlMCTaWXzKHQCfeGWZ
xF9r2pH8MVt9YARuqFny/Gk=
=315F
-END PGP SIGNATURE-

--5IYJRsx6KNVuKrR5--

[sane-devel] permissions for parallel port scanners

[Tim Waugh]

--QK8nhFMwR+o7J1de
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Sun, Jul 22, 2001 at 03:37:22PM +0200, Oliver Rauch wrote:

> So I want to ask all authors of backends that support
> parallel port scanners to work out a common way
> (sanei_parallel_*) to talk as user to the scanner.
> These sanei_parallel_* routines should run on
> as much systems as possible (not only linux!).

Please see sf.net/projects/libieee1284.

Tim.
*/

--QK8nhFMwR+o7J1de
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7W1MwONXnILZ4yVIRAjpXAJ9xc7WG2Z/z9D4EFwEw0chn+Gi8bwCfdFf9
tiTaI78gYMcioCNTI2Hzn0g=
=5Uer
-END PGP SIGNATURE-

--QK8nhFMwR+o7J1de--

[sane-devel] microtek2 backend bug?

[Tim Waugh]

--Vsi50HYs5tPfr+1I
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

In  a bug
in the microtek2 backend is detailed.  It is alleged that it doesn't
return SANE_STATUS_NO_DOCS when it should, but instead just returns an
I/O error.

Does anyone know what would be involved in fixing that?

Thanks,
Tim.
*/

--Vsi50HYs5tPfr+1I
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8GkCEyaXy9qA00+cRAt7kAJ9ymh77UJFEs0VxPyszz0rRNzf9qQCeMeIJ
AtIa07MqtfOeZNH6np4aBAU=
=wNk/
-END PGP SIGNATURE-

--Vsi50HYs5tPfr+1I--

[sane-devel] microtek2 backend bug?

[Tim Waugh]

--0ZpWocbG2H/Vq+uQ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Fri, Dec 14, 2001 at 08:26:05PM +0100, Henning Meier-Geinitz wrote:

> A debugging output (SANE_DEBUG_SANEI_SCSI=255 SANE_DEBUG_MICROTEK2=255
> in this case) may help to find the exact source.

Yes, it would, but unfortunately neither I nor the original reporter
of bug have access to this device (any longer). :-(

Tim.
*/

--0ZpWocbG2H/Vq+uQ
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8Go6/yaXy9qA00+cRAqhoAJ9u6E1P7KT0NaLZK+1LyHdF39iWaQCfbmNq
Sz2+nNbr5kZP6uOPzHhZnaw=
=wBKS
-END PGP SIGNATURE-

--0ZpWocbG2H/Vq+uQ--

[sane-devel] pale negative scans

[Tim Waugh]

--zywvytGCXzdVpkje
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

I received this bug report via Bugzilla for Roswell, the current Red
Hat Linux beta:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=50880

(It has sane 1.0.5.)

"I have a scanner - Epson Perfection 1240U (usb) - which works very
 well with sane/xsane for ordinary scanning, but when I'm scanning
 negatives (photos) the result is useless because it is very pale. I
 still have to scan my negatives in Win2000.

 Should be possible to get better colors for the negatives as well?"

Tim.
*/

--zywvytGCXzdVpkje
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7a91vONXnILZ4yVIRAkPOAJ4snq+WaxWtNgJs80osj2eX467KCACfbx+L
vyq/Cc2QewxqwOjDQY+D5DQ=
=wP7l
-END PGP SIGNATURE-

--zywvytGCXzdVpkje--

[sane-devel] Questions from new backend developers

[Tim Waugh]

--cDtQGJ/EJIRf/Cpq
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Aug 10, 2001 at 07:35:11PM +0200, Henning Meier-Geinitz wrote:

> > On an aside, I noticed there have been a few questions about
> > running parallel scanners non-root today. Has anyone got any ideas
> > about this? Since I use libieee1284, my backend runs perfectly as
> > a user.
>=20
> How does it work? Does it use a kernel driver?

It tries to use ppdev if it is available; if not, it tries ioperm or
/dev/port.  The idea is that it tries all available methods until it
finds one that works. (Under FreeBSD, it would try /dev/io, for
instance, although that code isn't written yet.)

> I think it's ok to include libieee1284 into SANE. But before the
> backend authors will use it instead of their own impementations, it
> should support the platforms that are currently supported (at least
> that would be my opinion, if I maintained a parport backend).

Of course.  The other thing to bear in mind at this stage is that the
API for libieee1284 will change when I get some time to code on it.
There are several missing features that need to be added, and there
might be incompatible interface changes to come.

> I'm not sure if this works for all the parport backends/drivers (e.g.
> sanei_ab306 or sanei_pa4s2).

It would be great if someone could port this code into libieee1284
so that other applications can benefit from it..

Tim.
*/

--cDtQGJ/EJIRf/Cpq
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7dGAFONXnILZ4yVIRAiIDAKCbtkKNNKtLdjs6Z1JWnDUIP4UVfQCfTMJM
jThoos7cpzARsIZ/IZgzSLM=
=E2GA
-END PGP SIGNATURE-

--cDtQGJ/EJIRf/Cpq--

[sane-devel] Questions from new backend developers

[Tim Waugh]

--Y+Z5jE7Arku/2GrR
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Sat, Aug 11, 2001 at 12:47:21AM +0200, Jochen Eisinger wrote:

> Could somebody give me a pointer to libieee1284? if it works, I'll soon
> add support for it to sanei_pa4s2. A sanei_ieee1284 could be used to
> ensure, that the interface remains the same during development of that
> lib.

http://people.redhat.com/twaugh/libieee1284/>.  CVS is at
sourceforge.

Tim.
*/

--Y+Z5jE7Arku/2GrR
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7dPHgONXnILZ4yVIRAmCtAJ9q+yYvpef3ukYSw3hlFZ9usM6YJgCeKKx3
7eZOfoZCnWkv8RDzvtsTjqA=
=56na
-END PGP SIGNATURE-

--Y+Z5jE7Arku/2GrR--

[sane-devel] Questions from new backend developers

[Tim Waugh]

--nrXiCraHbXeog9mY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Sat, Aug 11, 2001 at 01:41:53PM +0200, Henning Meier-Geinitz wrote:

> sanei_ab306 supports the Mustek 600IIN which has it's own ISA i/o
> card. However, this card is very similar to a parport. So I need a way
> to access some ports directly and send data to them (e.g. 0x379). Can
> this be done with libieee1284?

Yes, for the SPP registers (data, control, status).

> I had a quick look at ieee1284.h. What is "the name of a parallel port"?

An arbitrary name, like "parport0" or "0x378".  For presenting to the
user so that they can select a port if they want.

> As you asked for comments: Please don't use "//" for comments, if the
> code should be included into SANE. This will make trouble with older
> compilers on several platforms.

Added to the todo list.

Tim.
*/

--nrXiCraHbXeog9mY
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7dScDONXnILZ4yVIRAhORAJ9UZ7PW7fgYL1cunmFkhMcwoxpgTQCeMT4q
qdu0/u5cGrBb72x60na3FHA=
=vk9W
-END PGP SIGNATURE-

--nrXiCraHbXeog9mY--

[sane-devel] Umax Ultraslim 1220

[Tim Waugh]

--5vNYLRcllDrimb99
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, Sep 30, 2002 at 08:00:27PM +0200, Henning Meier-Geinitz wrote:

> All this is only true for backends that directly access the parport
> (/dev/port or inb/outb).

> Using a special kernel module or libieee1284 (?) should work as
> normal user.

Indeed.  Of course, you'll need to set the appropriate permissions for
/dev/parport*.  If need be, any drivers that use /dev/port could be
made to run as root by setting permissive permissions on /dev/port,
although of course that's far less than ideal!

The libieee1284 project is progressing quite well.  We support several
different platforms now.

Tim.
*/

--5vNYLRcllDrimb99
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9mK4NtO8Ac4jnUq4RAje9AKCSqrYp2vvPDXbhX5X8SbbPRzrmagCeOAyx
0Nj6H83IANev6wOjz8VKX2U=
=Ar1r
-END PGP SIGNATURE-

--5vNYLRcllDrimb99--

[sane-devel] Umax Ultraslim 1220

[Tim Waugh]

--mSxgbZZZvrAyzONB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, Sep 30, 2002 at 10:14:51PM +0200, Henning Meier-Geinitz wrote:

> The last time I checked this didn't work. Even with chmod a+rw the
> kernel insisted on beeing root to access /dev/port. I think this was
> changed sometime. Some years ago it worked that way.

Oh, of course you're right.  Sorry for the misinformation.

Tim.
*/

--mSxgbZZZvrAyzONB
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9mMkJtO8Ac4jnUq4RAiXMAJ0Uy3p3fUFy/oMEdn5qk1RY7zvDtwCeNfJr
QMcrY9EyFhtiPeGkS1IV7pA=
=cA1Q
-END PGP SIGNATURE-

--mSxgbZZZvrAyzONB--

[sane-devel] freebsd parallel port scanner

[Tim Waugh]

--x0PBmTWHB3bjoOVh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, Jul 10, 2003 at 12:03:27PM +0200, Henning Meier-Geinitz wrote:

> Some of the other parport scanners are accessed without kernel
> modules, e.g. by using inb/outb. That should work with FreeBSD also.
> The Mustek Paragon 600 II N is not really a parallel port scanner but
> uses its own ISA card which is very similar to a parport card. As far
> as I know, it works on FreeBSD also.

Any driver using libieee1284 ought to work on FreeBSD I think.

Tim.
*/

--x0PBmTWHB3bjoOVh
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/DUMztO8Ac4jnUq4RAs3/AKCGHbK7L0vDE4hUuQNFVEsPkCYqQwCcCF+s
yg+rb6P5eUrdhR9y6aeo+Qc=
=Zr2Y
-END PGP SIGNATURE-

--x0PBmTWHB3bjoOVh--

[sane-devel] Epson Perfection 2400 on RH 9

[Tim Waugh]

--niUlcCfh/sMBwTxc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, Dec 15, 2003 at 12:07:46AM +0100, Henning Meier-Geinitz wrote:

> I haven't looked at the details but I think they linked scanimage with
> /usr/lib/sane/libsane.so which is libsane-vl4.so for some reason. At
> least that's what I found out after a similar bug report.

Actually it was the screw-ball hack to ltmain.sh in the tarball -- it
gave *every* back-end the soname 'libsane.so.1', and so ldconfig
creates the symlink for every back-end.

Fixed packages are in the pipeline.

Tim.
*/

--niUlcCfh/sMBwTxc
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/3PRR9gevn0C09XYRAgBPAKCGIB+xq0C+TNRT8kUy8R3aKZ6EqgCeMrtP
2KJ1u9duUbMxTQC64RJ7nCs=
=5SwF
-END PGP SIGNATURE-

--niUlcCfh/sMBwTxc--

[sane-devel] Epson Perfection 2400 on RH 9

[Tim Waugh]

--TG7lY2/6mW/akb80
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, Dec 15, 2003 at 12:52:14AM +0100, Oliver Rauch wrote:

> The soname of all sane libraries have to be "libsane.so.1"
> or you will not be able to make a frontend to load
> any backend.

I don't believe that's true actually: in current sane-backends
(1.0.13), the soname hack seems to have been taken out of ltmain.sh,
and the sonames of the backends are all sensible.

> The important thing is that the sane-libraries are not in a standard
> library path of the system.

Okay, it seems that when SANE was originally packaged for Red Hat it
*was* added to ld.so.conf, so I'll take that out.

Tim.
*/

--TG7lY2/6mW/akb80
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/3PvY9gevn0C09XYRAvrQAKDLHE1AUIwh+XZiAPIEA4vA/PHBtACfZmjP
liSZjqnvhHszZEUwREzzYXQ=
=RAHT
-END PGP SIGNATURE-

--TG7lY2/6mW/akb80--

[sane-devel] Epson 1640SU, no devices found, RH 8.0

[Tim Waugh]

--EgVrEAR5UttbsTXg
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Oliver,

See my previous email, in which I explained the situation.  There are
some errors in your text, which I'll correct:

On Mon, Dec 15, 2003 at 08:28:56PM +0100, Oliver Rauch wrote:

> The problem is that in redhat 9.0 there is listed /usr/lib/sane in=20
> /etc/ld.so.conf
> the second problem is that there is a link /usr/lib/sane/libsane.so.1 to
> a libsane library in the same directory. (this makes ldconfig changing th=
e=20
> link).

ldconfig will create links for sonames when they are missing.

> There also is a copy of a libsane.so.1 library in /usr/lib but this=20
> seems not to be used ( I think /usr/lib/sane is searched before /usr/lib =
),

It is used, of course, as ldd will tell you.  However, the search
order that glibc uses recently changed.

> It is a buggy configuration in redhat 9.0 and this also causes
> problems when the rpm is uninstalled and sane-backends is
> installed from source with -prefix=3D/usr because the entry /usr/lib/sane
> is not removed from /etc/ld.so.conf when the sane-backends rpm
> is uninstalled.

Did you test this?  I believe it to be incorrect, and I think that the
entry is removed.

In any case, I already explained that future sane-backends packages
will omit the ld.so.conf tampering.  In fact, the current development
Fedora package has this removed right now.

At present there is a sane-backends package in the works which undoes
the hacky (IMHO) libsane.so.1-force in ltmain.sh.  I understand that
your preferred solution would be to remove the incorrect ld.so.conf
tampering; however starting with new fixed packages at this stage
would only delay things, while the difference between the two fixes is
quite minimal and will be largely unnoticed.  At this stage I'd rather
get SANE working again on Red Hat Linux systems.

Tim.
*/

--EgVrEAR5UttbsTXg
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/3i7p9gevn0C09XYRArRJAKDRYQjndcXt4dkarGy1VG+a3zsbgwCfZYt4
PmTD0upXt/Bl+75ZJbWq7oI=
=RRAt
-END PGP SIGNATURE-

--EgVrEAR5UttbsTXg--

[sane-devel] Epson 1640SU, no devices found, RH 8.0

[Tim Waugh]

--HB4mHL4PVvkpZAgW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Dec 15, 2003 at 11:35:38PM +0100, Henning Meier-Geinitz wrote:

> If you remove the ltmain.sh hack, how do you want to get the linking
> independent of the the dll backend working?
>=20
> Most people won't use that feature but it's advertised in the SANE
> standard so it's a basic feature of SANE. I wouldn't call removing a
> feature "a fix". Well, it may be a temporary workaround but we all
> know how long "temporary" can take :-)

If you would rather I start the errata process all over again with the
better fix (of removing the ld.so.conf stuff) -- which will lead to a
longer time before fixed packages are ready -- I will do that.  Let me
know.

Thanks,
Tim.
*/

--HB4mHL4PVvkpZAgW
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/3tEi9gevn0C09XYRAiTgAKCMiH5Piw9zhgLCDhEOOvSv5xGfVACgumqc
SvoZrmr0JQJxRnsEjrErY6Q=
=gBPY
-END PGP SIGNATURE-

--HB4mHL4PVvkpZAgW--

[sane-devel] Please test fixed Red Hat Linux 9 packages

[Tim Waugh]

--LvlcLv3JjFtLV6y2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

If you are having trouble scanning using Red Hat Linux 9 since
applying official updates, please test these packages:

http://www.cyberelk.net/tim/data/tmp/sane-backends-*

Let me know if they fail or succeed in fixing the problem.

Thanks,
Tim.
*/

--LvlcLv3JjFtLV6y2
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/6cgz9gevn0C09XYRArg1AJ9jUVF7gNqWYIb9hswyW3CvhSckcgCeJ6TH
qEeZJrwfg+g5pE7ugg2kbys=
=HkXt
-END PGP SIGNATURE-

--LvlcLv3JjFtLV6y2--

[sane-devel] Problem with Fedora Core 2

[Tim Waugh]

--xYxgRrcmUCOORODc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jun 29, 2004 at 03:57:40PM +0300, Panos Katergiathis wrote:

> Hello
>=20
> I have configured my scanner with sane running in Fedora Core 2.=20
> Whenever i try to run xsane or 'scanimage -L' the system does not find=20
> any scanner attached... until i unplug the usb cable, wait a couple of=20
> seconds and plug it back again. The whole time, the Fedora's hardware=20
> browser DOES detect the scanner attached properly. The symptom=20
> re-appears after rebooting. Each time, after replugging the cable=20
> everything works perfectly.
>=20
> Any help will be appreciated.

This has been discussed a-plenty on the fedora-list, for instance
here:

http://www.redhat.com/archives/fedora-list/2004-June/msg00279.html

and also in bugzilla:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=3D121511

Short story: this needs a fix in the hotplug script of some sort, but
it isn't yet clear what is needed.

Tim.
*/

--xYxgRrcmUCOORODc
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA4XIu9gevn0C09XYRAjShAKCkME1y6YfJD10z5qMTigGLyvTFDwCgx7Tg
QjPeQmcD3553wbGm+lwDOSo=
=9T8E
-END PGP SIGNATURE-

--xYxgRrcmUCOORODc--