https://bugzilla.novell.com/show_bug.cgi?id=632306 https://bugzilla.novell.com/show_bug.cgi?id=632306#c1 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #1 from Johannes Meixner 2010-08-18 13:40:51 UTC --- I am confused by the naming of your device: In comment #0 you wrote "Epson Interpret S405" but you use a Lexmark driver for it? According to sane-find-scanner this device identifies itself as a "Lexmark S300-S400 Series" with USB ID 0x043d:0x0180 Was your piece of hardware perhaps re-labeled as "Epson"? Your device is not listed at the SANE project listing of all devices with USB vendor ID 0x043d which are known by the SANE project: http://www.sane-project.org/cgi-bin/driver.pl?v=043d I am afraid but we cannot help you here because we neither have your particular printer/scanner model so that we cannot reproduce any issue with this hardware nor do we have any particular knowledge how to set up this particular third-party driver software. We (i.e. Novell/openSUSE) do not proivide lexmark-inkjet-09-driver. I assume the lexmark-inkjet-09-driver is provided by Lexmark so that from our point of view it is third-party software which makes the bug report invalid for us. Nevertheless some blind guess what might help: If the lexmark-inkjet-09-driver works in compliance how the usual SANE scanner drivers work, it may help to have a look at http://en.opensuse.org/SDB:Configuring_Scanners In short: For each scanner driver which works in compliance how SANE scanner drivers work, there is a matching line in /etc/sane.d/dll.conf Each active line in /etc/sane.d/dll.conf (i.e. without leading '#') stands for an activated scanner driver, see http://en.opensuse.org/SDB:Configuring_Scanners#SANE_Backends Perhaps you only need to add or activate such a line for the lexmark-inkjet-09-driver? Another possible reason is that the lexmark-inkjet-09-driver is 32-bit software. In comment #0 you wrote "lexmark-inkjet-09-driver-1.5-1.i386.rpm" and "i386" indicates 32-bit software. This cannot work in a 64-bit environment. If this is the reason, the simplest solution is to install the 32-bit version of openSUSE 11.3. At least you must remove the 64-bit package versions of the scanner related software and replace them by the 32-bit package versions of those software, in particular sane-backends and a user frontend like e.g. xsane - otherwise no 32-bit scanner driver can work. Some background information: 1. A scanning frontend links with the SANE library libsane.so which is in fact the dll pseudo-driver. 2. The dll pseudo-driver dlopen()s the actual scanner driver which is here the lexmark driver. Therefore on a 64-bit system: If one runs a 64-bit scanning frontend (e.g. the 64-bit version of scanimage or xsane) then it links with the 64-bit version of libsane.so which again wants to link with the 64-bit version of the lexmark driver which fails if only a 32-bit lexmark driver is installed but it would work if a 64-bit lexmark driver was installed. In contrast on a 32-bit system: If one runs a 32-bit scanning frontend (e.g. the 32-bit versions of scanimage or xsane) then it links with the 32-bit version of libsane.so which again links with the 32-bit version of the lexmark driver so that your scanner should work. It should work if one installs on a 64-bit system the full scanning software only as 32-bit software but I never tested this on my own because I do not test scanners which need third-party drivers. By the way: An installed 32-bit version of xsane might require a 32-bit version of gimp (which would require lots of other 32-bit libraries) when the xsane gimp-plugin should be used to acquire an image from the scanner directly from within gimp. Therefore you may need tons of other 32-bit software which is the reason why I wrote above that the simplest solution is to install the 32-bit version of the whole openSUSE 11.3 (at least for a test to find out whether or not the root cause is a 32-bit versus 64-bit issue). If this all does not help to make it work, you should contact those who made the lexmark-inkjet-09-driver (probably Lexmark directly). Perhaps you may ask them for a 64-bit version of their driver. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=632306 https://bugzilla.novell.com/show_bug.cgi?id=632306#c3 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Scanner not recognized on |Scanner Lexmark Interpret |Epson Interpret S405 Usb |S405 does not work on |link |x86_64 with driver from | |Lexmark --- Comment #3 from Johannes Meixner 2010-08-18 15:45:56 UTC --- Again there seems to be some confusion. /etc/sane.d/lexmark.conf and the line "lexmark" in /etc/sane.d/dll.conf belong to the "lexmark" driver in the sane-backends package, see http://www.sane-project.org/sane-backends.html#S-LEXMARK The "lexmark" driver in the sane-backends package does not support the "Lexmark S300-S400 Series". The "lexmark" driver in the sane-backends package supports only those devices which are also listed in /usr/share/sane/descriptions/lexmark.desc which are the Lexmark models X1110, X1130, X1140, X1150, X1170, X1180, X1185, X1195, X12xx and the "Dell A920", see http://en.opensuse.org/SDB:Configuring_Scanners#Scanner Your lexmark-inkjet-09 driver package should provide documentation how to set up this particular driver. I really hope this driver does not somehow overwrite files of the "lexmark" driver in the sane-backends package. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=632306 https://bugzilla.novell.com/show_bug.cgi?id=632306#c5 --- Comment #5 from Johannes Meixner 2010-08-18 16:22:42 UTC --- The list of files in its archive contains one really big file which is more than 90% of the whole data: instarchive_all I guess the other files in its archive are only one more stage of their complicated installer machinery and the final payload (i.e. the actual scanner driver) is in instarchive_all. But I will not further dig into their mess to find out what their driver actually is. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.