SCX-3405FW fails to scan over network

[roadnottaken2718]

I recently bought a Samsung SCX-3405FW, and have had no issues printing with it.  Unfortunately the scanner is a bit more troublesome.  Under usb, sane-find-scanner detected the scanner, but I needed to force the xerox_mfp driver in order to get scanimage working (perhaps this model could be added to samsungmfp-scanner-sane-fix{,-multiarch}; the identifier is 04e8:344f).

Unfortunately, I haven't yet had much luck scanning over the network.  At first, I could only detect the printer through netdiscovery; it wouldn't appear as a scanner either in scanimage or the configurator (although clicking on the configurator's scanner panel would cause the printer to emit warm-up noises).  By clicking back and forth between the configurator's printer and scanner panels enough time, the scanner appeared, and also began to appear in the output of 'scanimage -L' (using the smfp backend, rather than the xerox_mfp backend).  However, if I attempt to scan from this device, scanimage promptly segfaults.  Additionally, if I click Properties in the configurator's scanner tab, it opens a new window which then closes almost instantly (I suspect this is the same issue augusto is experiencing).

Any help you can give would be appreciated.  In particular, how can I force the xerox_mfp backend when connected over the network?  I suspect that that by itself might solve my remaining scanning issues.

[bchemnet]

I recently bought a Samsung SCX-3405FW, and have had no issues printing with it.  Unfortunately the scanner is a bit more troublesome.  Under usb, sane-find-scanner detected the scanner, but I needed to force the xerox_mfp driver in order to get scanimage working (perhaps this model could be added to samsungmfp-scanner-sane-fix{,-multiarch}; the identifier is 04e8:344f).

I will do that when I next update the package.  Thanks for the ID.

Unfortunately, I haven't yet had much luck scanning over the network.  At first, I could only detect the printer through netdiscovery; it wouldn't appear as a scanner either in scanimage or the configurator (although clicking on the configurator's scanner panel would cause the printer to emit warm-up noises).  By clicking back and forth between the configurator's printer and scanner panels enough time, the scanner appeared, and also began to appear in the output of 'scanimage -L' (using the smfp backend, rather than the xerox_mfp backend).  However, if I attempt to scan from this device, scanimage promptly segfaults.

Can you post the file that results from "strace /opt/Samsung/mfp/bin/Configurator 2> strace.txt" during which you cause it to segfault?  This is sort of unusual behavior, and it's possible something will show up there that I can make sense of.

Additionally, if I click Properties in the configurator's scanner tab, it opens a new window which then closes almost instantly (I suspect this is the same issue augusto is experiencing).

Possibly, but the behavior you're getting is slightly different, which might be useful for diagnosing the problem.

Any help you can give would be appreciated.  In particular, how can I force the xerox_mfp backend when connected over the network?  I suspect that that by itself might solve my remaining scanning issues.

You can't.  The majority of sane backends are USB only; network scanning is only supported for a few scanners with a couple of the other backends, and as far as I know none of the Samsung printers work with anything other than smfp over the network.

[roadnottaken2718]

Scanimage is the program which segfaults when attempting to access the printer.  The Configurator just has the behavior where the properties window closes as soon as it opens.  I've attached the strace output from both scanimage, but the one from Configurator is too large to attach (1.6M).  I've uploaded it at https://docs.google.com/open?id=0B7jQVjFs8qZ6LXB3Qkhwek1UMDg .

[roadnottaken2718]

I managed to get scanimage to stop crashing by disabling the file I added to /etc/udev/rules.d and restarting udev.  Scanning from the command line now works fine with the caveat that often the first scanimage -L after the printer has been idle won't detect it (I think it times out before the printer finishes waking up; at any rate any further scanimage commands work without issue).

The properties page on the Configurator still closes as soon as it opens, but that's not something I particularly care about any more.  I'm willing to help with further debugging, though, in case tracking it down might help other users.

One final comment: I'm not sure if the udev rules.d stanza mentioned on the scanner troubleshooting page is necessary for some models, but it turned out not to be needed for this one (just adding the id to xerox_mfp.conf was sufficient), and actively interfered with the wireless scanning.  It might be helpful to add a note to that page clarifying the situation.

[bchemnet]

I managed to get scanimage to stop crashing by disabling the file I added to /etc/udev/rules.d and restarting udev.  Scanning from the command line now works fine with the caveat that often the first scanimage -L after the printer has been idle won't detect it (I think it times out before the printer finishes waking up; at any rate any further scanimage commands work without issue).

Glad to hear it.

The properties page on the Configurator still closes as soon as it opens, but that's not something I particularly care about any more.  I'm willing to help with further debugging, though, in case tracking it down might help other users.

I'll let you know after I've had some time to look through the traces - it may be a while.

One final comment: I'm not sure if the udev rules.d stanza mentioned on the scanner troubleshooting page is necessary for some models, but it turned out not to be needed for this one (just adding the id to xerox_mfp.conf was sufficient), and actively interfered with the wireless scanning.  It might be helpful to add a note to that page clarifying the situation.

Good to know, but odd.  I'll look into this some more as well.

[bchemnet]

Long delay, but a new driver/configurator version is available, and it is possible that it resolves this issue.

[roadnottaken2718]

I updated to the new driver version, but the configurator shows no change in behavior.

[bchemnet]

I'll continue to think about what it could be as I have time.

Scanning still works otherwise with the latest driver?

[roadnottaken2718]

The only difference in scanning from the command line since upgrading is that I need to manually run the netdiscovery binary to bring the scanner out of its sleep mode, rather than being able to just wake it up with a scanimage command.

[bchemnet]

If you are inclined to do so, please test whether making the following replacements has any effect:
(1) only netdiscovery with the one from the samsungmfp-network 4.00.35-2 package
(2) only /usr/lib/sane/libsane-smfp.so.1.0.1 with the one from the samsungmfp-driver-4.00.35 4.0035.-2 package
(3) both of the above

[roadnottaken2718]

(1) causes scanimage to fail to detect the printer even directly after a netdiscovery invocation.  (this is a difference from when all components are taken from .39)
(2) causes the first scanimage or netdiscovery attempt to fail but wake the printer from its low-power mode.  Further attempts with either utility succeed until the printer drops back into low-power mode.
(3) gives the same behavior as (2)

As an additional data point, I just noticed that the .39 version of netdiscovery prints "WARNING: configuration file not found" as its first line of output, while the .35 version does not.  The only other change in the output format is that the new version adds a vendor field to the line identifying the printer, rather than setting the vendor as the first token of the dsc: field.

[bchemnet]

Clearly Samsung made some sort of major change to their library files; you are the second person to report that the old libsane-smfp works better.  Unfortunately, they didn't increment the version, so dealing with this is more complicated than it should be.  I'll look into it when I have some time.

Regarding the configuration file warning, that is due to the new wrapper scripts Samsung is using on all their custom binaries; as near as I can tell, most of the binaries never generate or try to read a configuration file, so the warning is pointless.

[travsback]

I recently bought a Samsung SCX-3405FW, and have had no issues printing with it.  Unfortunately the scanner is a bit more troublesome.  Under usb, sane-find-scanner detected the scanner, but I needed to force the xerox_mfp driver in order to get scanimage working (perhaps this model could be added to samsungmfp-scanner-sane-fix{,-multiarch}; the identifier is 04e8:344f).

Hi,

I have the exact same problem with a aSmsung SCX-3405W. The suld drivers worked flawlessly over network (both the printer and scanner) in Kubuntu 13.10, but after doing a fresh install of Kubuntu 14.04, I can no longer get the scanner to work (printing works fine)

Installed, just as the previous time, "suld-driver-4.00.36" and "suld-configurator-2-qt4".

None of my scanning apps detects the scanner (Skanlight, Xsane...). Suld-configurator doesn't detect it either. I removed "suld-driver-4.00.36" and installed 4.00.39.

No changes.


$ sudo scanimage -L

Code: [Select]

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

- "suld-network-2" is the latest version.

- Have already gone through all the steps in "Scanner Questions".

- Added my user to the "lp" group

- "/opt/Samsung/mfp/bin/netdiscovery --all --scanner" finds nothing.

Code: [Select]

# DEBUG: Network printers discovery utility
- "/opt/Samsung/mfp/bin/netdiscovery -s --snmp" does comes back the same:

Code: [Select]

# DEBUG: Network printers discovery utility
- Both devices (laptop and scanner) are on the same network.

- Firewall is disabled

- Scanner works fine on my other laptop (Xubuntu 13.10 amd64) using 4.00.36 drivers.

Any ideas what I could do to solve this?

Thanks in advance!

[travsback]

Clearly Samsung made some sort of major change to their library files; you are the second person to report that the old libsane-smfp works better.  Unfortunately, they didn't increment the version, so dealing with this is more complicated than it should be.  I'll look into it when I have some time.

@bchemnet Are there any updates on this front? Any extra info I can provide that might help with this issue? Thanks!!!

[bchemnet]

I suspect that something, perhaps the SANE version, that changed from 13.10 to 14.04 is the actual problem.  However, the latest drivers ("driver2") use a different set of Samsung libraries, and perhaps that will resolve the problem.

If not, I suggest filing a bug with Ubuntu or the SANE project, because a change there appears to be at fault.  Otherwise, I'm sorry but I do not have any other ideas.

[travsback]

I suspect that something, perhaps the SANE version, that changed from 13.10 to 14.04 is the actual problem.  However, the latest drivers ("driver2") use a different set of Samsung libraries, and perhaps that will resolve the problem.

If not, I suggest filing a bug with Ubuntu or the SANE project, because a change there appears to be at fault.  Otherwise, I'm sorry but I do not have any other ideas.

Hi bchemnet, and thanks for your reply.

Checking through the compatibility list, I didn't see driver2 listed as compatible with my particular printer model (Samsung SCX3405W). So...remove "suld-driver-4.00.36" and install...what?

[travsback]

I suspect that something, perhaps the SANE version, that changed from 13.10 to 14.04 is the actual problem. 

You were right, the problem came from SANE. Looking through their documentation, I was able to find that the problem resided in /etc/sane.d/xerox_mfp.conf; the line for my printer was commented, and the printer was set in USB mode:

Code: [Select]

#Samsung SCX-3205W, usb mode
I uninstalled suld-driver-4.00.39 and installed 4.00.36, since, for some reason, 4.00.39 only lets me add the printer in DNS-SD mode (as opposed to tcp host address +port)

Rebooted, added the printer again via network address+port, then uncommented and edited the pertinent line in /etc/sane.d/xerox_mfp.conf so it looks like this:

Code: [Select]

#Samsung SCX-3205W, network mode
tcp host_address [port]
Problem solved. :)

Thanks for pointing me in the right direction! I hope this comes in handy - for future reference - for anyone else experiencing the same kind of problem.


EDIT:

Just for the record, for some reason, in Kubuntu 14.10 amd64, certain apps (e.g. Okular) are unable/unwilling to print when this printer is used in tcp address+port mode.

To get it to work, I had to add the printer again as an LPD network printer (DNS-SD) and make this printer default, while leaving the TCP-mode printer (how it was previously installed) untouched, so as to maintain scanner functionality.

[travsback]

Hi,

Just writing to update on the issue. The fix described in my previous post no longer works, I'm guessing something must have changed in SANE. Until recently, I've been using the scanner in a WinX host via Virtualbox, but for some reason, that has stopped working too, so I'm stuck without a scanner for the time being.

Have there been any developments on this front?

Thanks!

[bchemnet]

Have there been any developments on this front?

None that I am aware of.