Messages

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

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.

Starting from the 4.00.39 packages, replacing just /usr/lib/sane/libsane-smfp.so.1.0.1 with the one from the version driver 4.00.35-2 allowed me to get scanning working the way it had been (scanimage works even from the other subnet with the hardcoded netdiscovery workaround).

Update: I have a relatively minimal installation with just -common, -driver-##, -data, -network, and -scanner installed.  This workaround works flawlessly for me with all components at version 4.00.35-2, but on upgrade, scanimage -L from my computer on the other subnet no longer finds the printer (the failure was both with 4.00.39 across the board, and with the driver at 4.00.35-3 while the other components upgraded to 4.00.39-1).  Downgrading everything to 4.00.35-2 restored the workaround's viability.

Edited to add: on further investigation, this looks like this is only partially related to the "different subnets" issue.  I just tested on another computer which is connecting to the same router as the printer, and under the 4.00.39 driver, it seems to only be able to find the printer with scanimage after manually running the netdiscovery binary, whereas under 4.00.35 I could find the scanner just by running scanimage twice.  It may be that in one of the recent driver updates, Samsung changed the semantics of how the printer gets woken from an idle state.

I've used this workaround on my home network, and it works without a hitch.  The only change I would suggest is that, instead of using mv to rename the original binary, you move it with

Code Select Expand

dpkg-divert --local --rename --divert /opt/Samsung/mfp/bin/netdiscovery-org /opt/Samsung/mfp/bin/netdiscovery

That way any upgrades to samsungmfp-network will overwrite the original binary rather than clobbering the script.

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

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.

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 .

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.