# Re: Xsane - winsane? was Re: saned won't run under inetd

From: Paul Nixon (pnixon18@home.com)
Date: Sat May 12 2001 - 05:13:04 PDT

- Next message: Henning Meier-Geinitz: "Re: Xsane - winsane? was Re: saned won't run under inetd"
  - Previous message: regis rampnoux: "Re: Snapscan ... again"
  - In reply to: Henning Meier-Geinitz: "Re: Xsane - winsane? was Re: saned won't run under inetd"
  - Next in thread: Henning Meier-Geinitz: "Re: Xsane - winsane? was Re: saned won't run under inetd"
  - Next in thread: Henning Meier-Geinitz: "Re: Xsane - winsane? was Re: saned won't run under inetd"
  - Reply: Henning Meier-Geinitz: "Re: Xsane - winsane? was Re: saned won't run under inetd"
  - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

  Sadly I killed my /usr/local/lib directory when I was trying to get rid
  of sane. So I had to recompile gimp and sane and now am back in limbo.
  Neither xsane nor xscanimage will properly scan an image (never
  completes). Preview still causes core dump with xscanimage and the
  shredded image in xsane.

  To answer your question about libsane and how it's setup on my system:

  ls -al /usr/local/lib/libsane*
  libsane.a
  libsane.la
  libsane.so -> libsane.so.1.0.4
  libsane.so.1 -> libsane.so.1.0.4

  There is NO libsane.so.1.0.4 in /usr/local/lib/sane. I had to cp
  ../libsane.so.1.0.4 . and then link libsane.so.1 to it. Otherwise
  xscanimage and xsane complained about libsane.so.1: no such file or
  directory.

  Keep in mind that I essentially started from scratch and the above is
  purely the result of ./configure/make/make install for both
  sane-backends and sane-frontends. I then did ldconfig.

  > The second one should also point to ibsane-snapscan.so.1.0.4. Where is
  > libsane-snapscan.so.1.0.4?
  >
  > rm -r /usr/local/lib/libsane* /usr/local/lib/sane /usr/lib/libsane* /usr/lib/sane

  I don't have any sane files in /usr/lib (no libsane and no sane subdir).
  I removed the /usr/local/lib the hard way and recompiled.

  >
  > Oops. May I ask again? Where is the link exactly (/usr/local/lib or
  > /usr/local/lib/sane)? Could you please do a ls -l?
  > I don't understand why ldconfig would do such things. If the link is
  > in /usr/local/lib/sane/ then /etc/ld.so.conf contains
  > "/usr/local/lib/sane".

  I think the v4l linking is something from a past installation. Yes, I do
  have /usr/local/lib/sane in /etc/ld.so.conf. I think I shouldn't,
  correct?

  >
  > > libsane.so.1 -> libsane-dll.so.1.0.4 is how it is linked at present.
  >
  > On my system this isn't a link:

  I created this link for testing purposes.

  > ls -l /usr/local/lib/libsane*
  > -rw-r--r-- 1 root staff 162912 Mai 12 12:49 /usr/local/lib/libsane.a
  > -rwxr-xr-x 1 root staff 664 Mai 12 12:49 /usr/local/lib/libsane.la
  > lrwxrwxrwx 1 root staff 16 Mai 12 12:49 /usr/local/lib/libsane.so -> libsane.so.1.0.4
  > lrwxrwxrwx 1 root staff 16 Mai 12 12:49 /usr/local/lib/libsane.so.1 -> libsane.so.1.0.4
  > -rwxr-xr-x 1 root staff 81965 Mai 12 12:49 /usr/local/lib/libsane.so.1.0.4

  This is what my /usr/local/lib/libsane* looks like as well. :-)

  > /usr/local/lib/sane doesn't contain any libsane.* (and shouldn't).

  Okay, I think I know what happened on my system. /etc/ld.so.conf
  contained /usr/local/lib/sane and so I had to create the libsane.so.1 ->
  libsane.so.1.0.4 link and cp ../libsane.so.1.0.4 here. I have since
  changed /etc/ld.so.conf to point to /usr/local/lib (I thought I read
  this shouldn't be in the file in the first place?) and then erased the
  link and file from /usr/local/lib/sane. It seems to be okay and my file
  structure looks like it is now correct.

  xscanimage still coredumps on preview and fails to complete a scan.
  Normally with my scanner set to 100dpi it can do a photo in a single
  pass in a very short time. Now however it sounds like it scans a bit
  then backtracks, scans a bit more, etc. Xscanimage and xsane now don't
  seem to get a signal from the scanner that it's finished.

  Hope this helps.
  Paul
  P.S. Thanks again for the input.

  >
  > Happy scanning!
  >
  > Henning
  >
  > --
  > Source code, list archive, and docs: http://www.mostang.com/sane/
  > To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com

      --
      Source code, list archive, and docs: http://www.mostang.com/sane/
      To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com

  - Next message: Henning Meier-Geinitz: "Re: Xsane - winsane? was Re: saned won't run under inetd"
  - Previous message: regis rampnoux: "Re: Snapscan ... again"
  - In reply to: Henning Meier-Geinitz: "Re: Xsane - winsane? was Re: saned won't run under inetd"
  - Next in thread: Henning Meier-Geinitz: "Re: Xsane - winsane? was Re: saned won't run under inetd"
  - Next in thread: Henning Meier-Geinitz: "Re: Xsane - winsane? was Re: saned won't run under inetd"
  - Reply: Henning Meier-Geinitz: "Re: Xsane - winsane? was Re: saned won't run under inetd"
  - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

  This archive was generated by hypermail 2b29 : Sat May 12 2001 - 12:02:29 PDT