Opened 14 years ago

Last modified 7 years ago

#23795 new defect

GIMP xsane plugin does not recognize scanners

Reported by: asgalon Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.8.2
Keywords: Cc: mklein-de (Michael Klein), elelay (Eric Le Lay)
Port: sane-backends xsane

Description

Before I forget again to report it:

The xsane plugin for Gimp delivered with macports has never worked for me. Each time I have to get the sources and rebuild it all before I can use my scanner again. Maybe this has to do with the fact that xsane explicitly states that it does not support sane changes between 1.0.19 and 1.0.20, maybe something else goes wrong. The fact that gimp depends on xsane and sane-backends (1.0.20) does not make it easier. At present I am struggling with the sane / xsane sources again, since my old xsane 0.994 installation which worked perfectly now has the wrong architecture on Mac OS 10.6

Change History (9)

comment:1 Changed 14 years ago by asgalon

and here is my complete workaround:

  • deactivate sane-backends

-compile sane-backends, install them in /usr/local, add /usr/local/lib to ld config, /usr/local/bin to path

-compile and install xsane 0.994

-change xsane and scanimage in /opt/local/bin to softlinks to /usr/local/bin/scanimage and /usr/local/bin/xsane

comment:2 Changed 14 years ago by mf2k (Frank Schima)

Port: gimp removed

Did you update from Mac OS X 10.5 to Mac OS X 10.6 with Macports installed? Did you follow the migration instructions?

comment:3 in reply to:  2 ; Changed 14 years ago by asgalon

Replying to macsforever2000@…:

Did you update from Mac OS X 10.5 to Mac OS X 10.6 with Macports installed? Did you follow the migration instructions?

Yes. It is not that the xsane plugin would not run, it only does not recognize my scanner. I had that problem with gimp and xsane right from the start after I installed it for the first time in 2007. I just looked into time machine, the last copy of the xsane source directory dates from september 2008.

More precisely, with the standard ports installation, sane-find-scanner tells me it has found it, but scanimage -L tells me there is no scanner:

Caribe[533]> sane-find-scanner 

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

found USB scanner (vendor=0x07b3 [Plustek Inc.], product=0x0015 [USB SCANNER], chip=LM9832/3) at libusb:253:007
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.

  # You may want to run this program as root to find all devices. Once you
  # found the scanner devices, be sure to adjust access permissions as
  # necessary.
Caribe[534]> 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).

)))


After building sane-backend and xsane from sources, everything works fine:

{{{
Caribe[577]> /usr/local/bin/scanimage -L
device `plustek:libusb:006:007-07b3-0015-00-00' is a Plustek OpticPro U24 flatbed scanner

}}}

comment:4 in reply to:  3 Changed 14 years ago by elelay (Eric Le Lay)

Replying to peter@…:

Replying to macsforever2000@…: More precisely, with the standard ports installation, sane-find-scanner tells me it has found it, but scanimage -L tells me there is no scanner:

I got the same problem with an HP ScanJet 2200c (also a Plustek USB scanner) and solved it by creating a /opt/local/var/lock/sane directory. This post helped me to see the problem.

Please try

export SANE_DEBUG_PLUSTEK=20; scanimage -L

and check if you have such output in the end :

[sanei_access] sanei_access_lock: open >/opt/local/var/lock/sane/
LCK..libusb:005:002-1606-0060-00-00< failed: No such file or directory
[plustek] sanei_access_lock failed: 11

if so, simply type :

sudo mkdir /opt/local/var/lock/sane
sudo chmod a+w /opt/local/var/lock/sane

and retry scanimage -L

comment:5 Changed 14 years ago by elelay (Eric Le Lay)

Cc: elelay@… added

Cc Me!

comment:6 Changed 13 years ago by jmroot (Joshua Root)

Cc: aguynamedryan+sane@… michael.klein@… added

comment:7 Changed 12 years ago by gabor@…

I have a Lexmark X3470 scanner (also printer) and I have a similar problem:

$ sane-find-scanner

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

found USB scanner (vendor=0x043d [Lexmark], product=0x00f6 [ 3400 Series]) at libusb:250:007
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.

  # You may want to run this program as root to find all devices. Once you
  # found the scanner devices, be sure to adjust access permissions as
  # necessary.

$ 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).

$ SANE_DEBUG_LEXMARK=20 scanimage -L

[sanei_debug] Setting debug level of lexmark to 20.
[lexmark] SANE Lexmark backend version 1.0.30-devel
[lexmark] sane_init: version_code=0x7fff5fbfef74
[lexmark] sane_get_devices: device_list=0x7fff5fbfefc0, local_only=0

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).
[lexmark] sane_exit

Any help appreciated.

comment:8 in reply to:  7 Changed 12 years ago by aguynamedryan+macports@…

Replying to gabor@…:

I have a Lexmark X3470 scanner (also printer) and I have a similar problem:

I Googled your problem and the second hit indicates that your scanner is most likely not supported.

So checked the list of supported devices and found a match for your scanner's vendor/product ID. It matches to an X3450 and that scanner is unsupported.

You might want to contact the SANE developers to see if you can get the scanner supported.

Once SANE supports it upstream, I can update the MacPorts with that support. Hope this helps!

comment:9 Changed 7 years ago by mf2k (Frank Schima)

Cc: aguynamedryan+sane@… removed
Note: See TracTickets for help on using tickets.