04e8:3441 14.04 won't scan via Samsung SCX-3200 Multi-Function Printer

Bug #1312594 reported by Theor
76
This bug affects 15 people
Affects Status Importance Assigned to Milestone
sane-backends (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

My multifunction Samsung SCX3200 printer is not detected by sane, but printing is fine. This scanner is faily generic and supported out of the box by the Xerox MFP driver (sane default).

Printer/scanner as seen by the kernel, device 007 : ID 04e8:3441

--------------------------------------------------------------------------------------------
$ lsusb
Bus 002 Device 003: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
Bus 003 Device 007: ID 04e8:3441 Samsung Electronics Co., Ltd
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
--------------------------------------------------------------------------------------------

The IDs are properly set in udev and sane.d configuration:

--------------------------------------------------------------------------------------------
$ cat /lib/udev/rules.d/40-libsane.rules | grep 3441
ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="3441", ENV{libsane_matched}="yes"

$ cat /etc/sane.d/xerox_mfp.conf | grep 3441
usb 0x04e8 0x3441
--------------------------------------------------------------------------------------------

Problem: sane-find-scanner can't find the scanner:

--------------------------------------------------------------------------------------------
$ sudo sane-find-scanner -q
$ (no output)
$ sudo 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).
$
--------------------------------------------------------------------------------------------

The kernel module is properly loaded when the printer is connected, no blacklisting :

--------------------------------------------------------------------------------------------
$ sudo lsmod | grep usblp
usblp 22891 0

$ modinfo usblp
filename: /lib/modules/3.13.0-24-generic/kernel/drivers/usb/class/usblp.ko
license: GPL
description: USB Printer Device Class driver
author: Michael Gee, Pavel Machek, Vojtech Pavlik, Randy Dunlap, Pete Zaitcev, David Paschal
srcversion: BD8A318D5C286F1E78768B9
alias: usb:v04B8p0202d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v*p*d*dc*dsc*dp*ic07isc01ip03in*
alias: usb:v*p*d*dc*dsc*dp*ic07isc01ip02in*
alias: usb:v*p*d*dc*dsc*dp*ic07isc01ip01in*
alias: usb:v*p*d*dc07dsc01dp03ic*isc*ip*in*
alias: usb:v*p*d*dc07dsc01dp02ic*isc*ip*in*
alias: usb:v*p*d*dc07dsc01dp01ic*isc*ip*in*
depends:
intree: Y
vermagic: 3.13.0-24-generic SMP mod_unload modversions
signer: Magrathea: Glacier signing key
sig_key: 00:A5:A6:57:59:DE:47:4B:C5:C4:31:20:88:0C:1B:94:A5:39:F4:31
sig_hashalgo: sha512
parm: proto_bias:Favourite protocol number (int)
--------------------------------------------------------------------------------------------

Simple-scan will just show a "Unable to start scan" error.

Also tried:
- Running simple-scan and xscan as root
- Adding myself to lp, saned and scanner groups, then log off + log on
- Power cyling the printer, disconnected and plugged back in
- Switching USB port (USB2 <-> USB3)
- Restarting the udev service

This scanner is faily generic and is supposed to be working OOTB since 12.04:
http://askubuntu.com/questions/88700/how-do-i-get-a-samsung-scx3200-multifunction-printer-scanner-working
http://ubuntuforums.org/showthread.php?t=1857478

I think this may be a bug with libsane.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1312594/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Theor (theor) wrote :

Assigning to libsane as only scanning is impacted. This might possibly be related to another package though.

affects: ubuntu → sane-backends (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in sane-backends (Ubuntu):
status: New → Confirmed
Revision history for this message
steve cohen (steve-si9yrl01qsu4bt4tonx56g) wrote :

i also have an out of the box fujitsu fi-6110 which function perfectly on 12.04 and i believe new install of 13.10 but the upgrade of 13.10 to 14.04 made the scanner invisible to sane-find-scanner and sanimage -L.

also noted udev did detect the scanner as above and shown in the logs below, however it never created the node scanner in /dev or /dev/usb as would be indicated by the udev rules listed below.

lsusb -> Bus 003 Device 011: ID 04c5:11fc Fujitsu, Ltd

/lib/udev/rules.d/40-libsane.rules:
# Fujitsu fi-6110
ATTRS{idVendor}=="04c5", ATTRS{idProduct}=="11fc", ENV{libsane_matched}="yes"
.
ENV{libsane_matched}=="yes", RUN+="/bin/setfacl -m g:scanner:rw $env{DEVNAME}"

syslog:
Jul 3 14:25:34 alicia kernel: [17927.333603] usb 3-2: new high-speed USB device number 6 using xhci_hcd
Jul 3 14:25:34 alicia kernel: [17927.356763] usb 3-2: New USB device found, idVendor=04c5, idProduct=11fc
Jul 3 14:25:34 alicia kernel: [17927.356774] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 3 14:25:34 alicia kernel: [17927.357015] usb 3-2: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes
Jul 3 14:25:34 alicia kernel: [17927.357030] usb 3-2: ep 0x2 - rounding interval to 128 microframes, ep desc says 255 microframes
Jul 3 14:25:34 alicia kernel: [17927.364588] WARNING! power/level is deprecated; use power/control instead
Jul 3 14:25:34 alicia colord: Device added: sysfs-04c5-11fc

Revision history for this message
steve cohen (steve-si9yrl01qsu4bt4tonx56g) wrote :

update:
older system had /dev/usb/scanner
12.04 only created entries ini udev
the new addition to the logs appear to use colord in 14.04
hope this is helpful

Revision history for this message
Lex Ross (lross) wrote :

I've got Canon CanoScan LIDE 25 scanner that stopped working following Ubuntu 14.04 upgrade. The scanner is recognized by system (kernel and sane-find-scanner) and shows up it Simple Scan options dialogue. Yet the scan action fails with the scanner not powering itself up and not doing anything.

syslog:

[ 5717.924791] usb 3-2: USB disconnect, device number 3
[ 5725.935931] usb 3-2: new full-speed USB device number 4 using xhci_hcd
[ 5725.953233] usb 3-2: New USB device found, idVendor=04a9, idProduct=2220
[ 5725.953244] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 5725.953250] usb 3-2: Product: CanoScan
[ 5725.953256] usb 3-2: Manufacturer: Canon

sane-find-scanner output:

found USB scanner (vendor=0x04a9 [Canon], product=0x2220 [CanoScan]) at libusb:003:004

Revision history for this message
Linda (elindarie) wrote :
Download full text (5.1 KiB)

I'm having a similar problem. I have an old 32-bit Debian laptop on which my scanner is working fine, and a new 64-bit Ubuntu 14.04 laptop on which the scanner is not working. The scanner is connected via USB cable. It is part of a Brother DCP-8155DN (multifunction black and white laser printer, copier, and scanner). The copier is working, and the printer part is working with CUPS just fine as far as I can tell.

The scanner seems to be detected, but then gscan2pdf and Simple Scan give errors, and sane-find-scanner can not find it. Scanimage sees it but cannot produce an output image. I tried these as root and not root.

I have sane 1.0.14-9 and sane-utils 1.0.23-3. The kernel is Linux version 3.13.0-32-generic.

lsusb:

   Bus 003 Device 006: ID 04f9:0293 Brother Industries, Ltd

grep bro /etc/sane.d/dll.conf

   brother4

locate libsane | grep rules

   /etc/udev/rules.d/40-brother-libsane-type1.rules
   /lib/udev/rules.d/40-libsane.rules

grep 0293 /lib/udev/rules.d/40-libsane.rules

   ATTRS{idVendor}=="04f9", ATTRS{idProduct}=="0293", ENV{libsane_matched}="yes"

scanimage -L

   device `brother4:bus2;dev1' is a Brother DCP-8155DN USB scanner

sudo scanimage -T

   scanimage: rounded value of br-x from 215.9 to 215.88
   scanimage: rounded value of br-y from 355.6 to 355.567
   scanimage: sane_start: Invalid argument

sudo sane-find-scanner

   # No USB scanners found. If you expected something different, make sure that
   # you have loaded a kernel driver for your USB host controller and have setup
   # the USB system correctly. See man sane-usb for details.

When I ran gscan2pdf as root from the command line, it gave a command line error:

   ERROR - opening device 'brother4:bus2;dev1': Invalid argument

*************************************************************************************

sudo SANE_DEBUG_SANEI_USB=255 sane-find-scanner

[sanei_debug] Setting debug level of sanei_usb to 255.
[sanei_usb] sanei_usb_init: marking existing devices
[sanei_usb] sanei_usb_init: Looking for kernel scanner devices
[sanei_usb] sanei_usb_init: initializing libusb-1.0
[sanei_usb] sanei_usb_init: Looking for libusb-1.0 devices
...
[sanei_usb] sanei_usb_init: device 0x04f9/0x0293, interface 0 doesn't look like a scan
ner (0/7)
[sanei_usb] sanei_usb_init: found libusb-1.0 device (0x04f9/0x0293) interface 1 at lib
usb:003:006
[sanei_usb] store_device: add dn 0 with libusb:003:006
[sanei_usb] sanei_usb_init: found 1 devices
[sanei_usb] sanei_usb_init: device 00 is libusb:003:006
[sanei_usb] sanei_usb_open: trying to open device `/dev/usb/scanner'
[sanei_usb] sanei_usb_open: can't find device `/dev/usb/scanner' in list
...
[sanei_usb] sanei_usb_open: trying to open device `/dev/usbscanner'
[sanei_usb] sanei_usb_open: can't find device `/dev/usbscanner' in list
...
  # No USB scanners found. If you expected something different, make sure that
  # you have loaded a kernel driver for your USB host controller and have setup
  # the USB system correctly. See man sane-usb for details.

******************************************************************************

sudo SANE_DEBUG_SANEI_USB=255 scanimage -T

[sanei_debug] Setting debug level of sane...

Read more...

Revision history for this message
Linda (elindarie) wrote :

I'm confused about what is the sane frontend or backend, or whether I should download/install another frontend or backend, if there is one. I'm not sure, but from the following, it seems like, on Ubuntu, that "sane" is the frontend, and "sane-utils" is the backend (???) .

dpkg -l | grep -i sane

ii libcommon-sense-perl 3.72-2build1 amd64 module that implements some sane defaults for Perl programs
ii libsane:amd64 1.0.23-3ubuntu3.1 amd64 API library for scanners
ii libsane-common 1.0.23-3ubuntu3.1 amd64 API library for scanners -- documentation and support files
ii libsane-hpaio 3.14.3-0ubuntu3.2 amd64 HP SANE backend for multi-function peripherals
ii libsane-perl 0.05-2build1 amd64 Perl bindings for the SANE (Scanner Access Now Easy) Project
ii sane 1.0.14-9 amd64 scanner graphical frontends
ii sane-utils 1.0.23-3ubuntu3.1 amd64 API library for scanners -- utilities

Also, the SANE website, http://www.sane-project.org, says the latest backend is 1.0.24, as of Sept. 30, 2013. The Ubuntu Software Center seems to have version 1.0.23 for sane-utils . If that is the same as the sane backend, maybe upgrading to 1.0.24 would fix this. Their web site says the changes from 1.0.23 to 1.0.24 have some bug fixes and improved USB support, etc.

I don't know if it's possible, but maybe it would be simpler if the names of the sane-related files on ubuntu were the same as those at the www.sane-project.org.

Revision history for this message
Richard Appleby (disposable01) wrote :
Download full text (9.7 KiB)

Same problem, in my case with a USB-attached Canon Canoscan N650U (an ancient, well supported scanner, that was working just fine on 12.04LTS).

$ lsusb
Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 012: ID 04a9:2206 Canon, Inc. CanoScan N650U/N656U
Bus 001 Device 008: ID 04b3:301b IBM Corp. SK-8815 Keyboard
Bus 001 Device 004: ID 0557:8021 ATEN International Co., Ltd
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 011: ID 1941:8021 Dream Link WH1080 Weather Station / USB Missile Launcher
Bus 001 Device 010: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Bus 001 Device 007: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub
Bus 001 Device 006: ID 0baf:0303 U.S. Robotics
Bus 001 Device 002: ID 174c:2074 ASMedia Technology Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

/lib/udev/rules.d/40-libsane.rules looks like it ought to be detecting it ...

$ cat /lib/udev/rules.d/40-libsane.rules | grep 2206
ATTRS{idVendor}=="04a9", ATTRS{idProduct}=="2206", ENV{libsane_matched}="yes"

But I get nothing created in /dev ...

And trying to search for the scanner produces no results, though some slightly odd looking intermediate debug information:

$ sudo SANE_DEBUG_SANEI_USB=255 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.

[sanei_debug] Setting debug level of sanei_usb to 255.
[sanei_usb] sanei_usb_init: marking existing devices
[sanei_usb] sanei_usb_init: Looking for kernel scanner devices
[sanei_usb] sanei_usb_init: can't stat /dev/usb/: No such file or directory
[sanei_usb] sanei_usb_init: initializing libusb-1.0
[sanei_usb] sanei_usb_init: Looking for libusb-1.0 devices
[sanei_usb] sanei_usb_init: device 0x174c/0x3074, interface 0 doesn't look like a scanner (9/9)
[sanei_usb] sanei_usb_init: device 0x174c/0x3074 at 002:002: no suitable interfaces
[sanei_usb] sanei_usb_init: device 0x1d6b/0x0003, interface 0 doesn't look like a scanner (9/9)
[sanei_usb] sanei_usb_init: device 0x1d6b/0x0003 at 002:001: no suitable interfaces
[sanei_usb] sanei_usb_init: found libusb-1.0 device (0x04a9/0x2206) interface 0 at libusb:001:012
[sanei_usb] store_device: add dn 0 with libusb:001:012
[sanei_usb] sanei_usb_init: device 0x04b3/0x301b, interface 0 doesn't look like a scanner (0/3)
[sanei_usb] sanei_usb_init: device 0x04b3/0x301b, interface 1 doesn't look like a scanner (0/3)
[sanei_usb] sanei_usb_init: device 0x04b3/0x301b, interface 2 doesn't look like a scanner (0/3)
[sanei_usb] sanei_usb_init: device 0x04b3/0x301b at 001:008: no suitable interfaces
[sanei_usb] sanei_usb_init: device 0x0557/0x8021, interface 0 doesn't look like a scanner (9/9)
[sanei_usb] sanei_usb_init: device 0x0557/0x8021 at 001:004: no suitable interfaces
[sanei_usb] sanei_usb_init: devic...

Read more...

Revision history for this message
morebikethanman (morebikethanman) wrote :
Download full text (6.8 KiB)

I am experiencing the same problems with an HP Laserjet 1220 scanner. From what is listed below, there seems to be some problem starting with sane_open(). The first time it runs on a new device it claims to be successful, but that message is never repeated until the device is removed and replaced. Details below:

My system is Ubuntu 14.04.1 LTS.
$uname -a
 Linux computer 3.13.0-34-generic #60-Ubuntu SMP Wed Aug 13 15:45:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

There were no udev rules or associated .conf file so I created hpaio.conf and added
 usb 0x03f0 0x0417
I also added the following lines to /lib/udev/rules.d/40-libsane.rules
 # Hewlett-Packard LaserJet 1220
 ATTRS{idVendor}=="03f0", ATTRS{idProduct}=="0417", ENV{libsane_matched}="yes"
though neither of these seemed to change things.

After unplugging and replugging the device, with SANE_DEBUG_DLL=128, the first time I got:
<pre>
[sanei_debug] Setting debug level of dll to 128.
[dll] sane_init: SANE dll backend version 1.0.13 from sane-backends 1.0.23
[dll] sane_init/read_dlld: attempting to open directory `./dll.d'
[dll] sane_init/read_dlld: attempting to open directory `/etc/sane.d/dll.d'
[dll] sane_init/read_dlld: using config directory `/etc/sane.d/dll.d'
[dll] sane_init/read_dlld: considering /etc/sane.d/dll.d/hplip
[dll] sane_init/read_config: reading dll.d/hplip
[dll] add_backend: adding backend `hpaio'
[dll] sane_init/read_dlld: done.
[dll] sane_init/read_config: reading dll.conf
[dll] add_backend: adding backend `hp'
[dll] add_backend: adding backend `hpaio'
[dll] add_backend: `hpaio' is already there
[dll] sane_get_devices
[dll] load: searching backend `hpaio' in `/usr/lib/x86_64-linux-gnu/sane:/usr/lib/sane'
[dll] load: trying to load `/usr/lib/x86_64-linux-gnu/sane/libsane-hpaio.so.1'
[dll] load: couldn't open `/usr/lib/x86_64-linux-gnu/sane/libsane-hpaio.so.1' (No such file or directory)
[dll] load: trying to load `/usr/lib/sane/libsane-hpaio.so.1'
[dll] load: dlopen()ing `/usr/lib/sane/libsane-hpaio.so.1'
[dll] init: initializing backend `hpaio'
[dll] init: backend `hpaio' is version 1.0.0
[dll] load: searching backend `hp' in `/usr/lib/x86_64-linux-gnu/sane:/usr/lib/sane'
[dll] load: trying to load `/usr/lib/x86_64-linux-gnu/sane/libsane-hp.so.1'
[dll] load: dlopen()ing `/usr/lib/x86_64-linux-gnu/sane/libsane-hp.so.1'
[dll] init: initializing backend `hp'
[dll] init: backend `hp' is version 1.0.8
[dll] sane_get_devices: found 1 devices
[dll] sane_open: trying to open `hpaio:/usb/HP_LaserJet_1220?serial=00XXXXXXXXXX'
[dll] sane_open: open successful
[dll] sane_get_option_descriptor(handle=0x7fa9a801b480,option=0)
[dll] sane_get_option_descriptor(handle=0x7fa9a801b480,option=1)
[dll] sane_get_option_descriptor(handle=0x7fa9a801b480,option=2)
[dll] sane_get_option_descriptor(handle=0x7fa9a801b480,option=3)
[dll] sane_get_option_descriptor(handle=0x7fa9a801b480,option=4)
[dll] sane_get_option_descriptor(handle=0x7fa9a801b480,option=5)
[dll] sane_get_option_descriptor(handle=0x7fa9a801b480,option=6)
[dll] sane_get_option_descriptor(handle=0x7fa9a801b480,option=7)
[dll] sane_get_option_descriptor(handle=0x7fa9a801b480,option=8)
[dll] sane_get_option_descriptor(handle=0...

Read more...

Revision history for this message
PeterPall (peterpall) wrote :

Found a workaround:
The error message "rounding interval to 128 microframes, ep desc says 255 microframes" seems to be caused by the xhci driver that handles USB3.0 ports. Using a USB2.0 port works fine. The same happens with some memory sticks and my Epson Perfection V10 scanner. Will go and buy an old USB2.0 hub to see if that solves the problem and look if I can somehow link this bug to the kernel since the problem seems to lie there.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux (Ubuntu):
status: New → Confirmed
Brad Figg (brad-figg)
affects: linux-meta (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
PeterPall (peterpall) wrote :

Did try to make my scanner work with the latest upstream kernel. Seems like the problem is valid there, too.

Revision history for this message
PeterPall (peterpall) wrote :

Did test if the problm persists with the latest vanilla kernel (it does) so I sent a bug report via mail to the maintainer of the xhci kernel driver.

Revision history for this message
morebikethanman (morebikethanman) wrote :

I can confirm that scanning seems to be working when using the USB2.0 port on my machine. I can't believe I didn't try that. Thank you for the advice - hopefully it will be addressed with the upstream kernel.

Changed in linux (Ubuntu):
importance: Undecided → Medium
penalvch (penalvch)
summary: - 14.04 won't detect common USB scanner
+ 04e8:3441 14.04 won't scan via Samsung SCX-3200 Multi-Function Printer
no longer affects: linux (Ubuntu)
Revision history for this message
penalvch (penalvch) wrote :

Theor, did this problem not occur for you personally (not someone else on another report of forum) in a release prior to Trusty?

steve cohen / Lex Ross / Linda / SixedUp / morebikethanman / PeterPall, thank you for your comment. Unfortunately, this bug report is not scoped to you, your hardware, or your problem. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal:
ubuntu-bug cups

Please ensure you provide the required debugging information following https://wiki.ubuntu.com/DebuggingPrintingProblems .

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in sane-backends (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Linda (elindarie) wrote :

Christopher, are you sure you want this reported as a cups bug? I have a multifunction printer/scanner, and the printer functions are fine, as far as I can tell -- my only problem is scanning.

Revision history for this message
Linda (elindarie) wrote :

I would be happy to help debug this bug:

Can someone tell me how and where I can get and build the scanner software (in a development folder on my computer - a folder other than the regular system location) so I can run it and step through it on both my Ubuntu (where the scanner is not working) and Debian (where the scanner is working) machines, to compare the output?

Thank you.

Revision history for this message
penalvch (penalvch) wrote :

Linda, sane-backends would be fine if you don't have a printing problem. However, posting "Me too!" comments with completely different hardware is just simply not helpful here. Instead, please file a new report via a terminal:
ubuntu-bug sane-backends

Revision history for this message
Theor (theor) wrote :

Christopher,
"Theor, did this problem not occur for you personally (not someone else on another report of forum) in a release prior to Trusty?"
The previous releases were not LTS and I wouldn't use them natively, so I can't tell. It used to work with 12.04LTS though.

I notice that some people claim it works if they switch from an USB3 to an USB2 port. As mentionned in the first post, I did try that and it didn't change anything, so I doubt this is the root cause.

Revision history for this message
penalvch (penalvch) wrote :

Theor, please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1312594

tags: added: regression-release trusty
Revision history for this message
Theor (theor) wrote :

$ apport-collect 1312594
Package sane-backends not installed and no hook available, ignoring

$ sudo apt-get install sane-backends
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package sane-backends

For your information, this is a default install, I don't remember removing any libsane package.

Revision history for this message
penalvch (penalvch) wrote :

Theor, could you please test the latest release (live environment is fine) via http://cdimage.ubuntu.com/daily-live/current/ ?

Revision history for this message
Linda (elindarie) wrote : Re: [Bug 1312594] Re: 04e8:3441 14.04 won't scan via Samsung SCX-3200 Multi-Function Printer
Download full text (5.3 KiB)

> I notice that some people claim it works if they switch
> from an USB3 to an USB2 port. As mentioned in the
> first post, I did try that and it didn't change anything,
> so I doubt this is the root cause.

Same here. I have both USB3 and USB2 on my computer, and connecting the
scanner to the USB2 port didn't fix it.

On Tue, Nov 11, 2014 at 5:57 AM, Theor <email address hidden> wrote:

> Christopher,
> "Theor, did this problem not occur for you personally (not someone else on
> another report of forum) in a release prior to Trusty?"
> The previous releases were not LTS and I wouldn't use them natively, so I
> can't tell. It used to work with 12.04LTS though.
>
> I notice that some people claim it works if they switch from an USB3 to
> an USB2 port. As mentionned in the first post, I did try that and it
> didn't change anything, so I doubt this is the root cause.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1312594
>
> Title:
> 04e8:3441 14.04 won't scan via Samsung SCX-3200 Multi-Function Printer
>
> Status in “sane-backends” package in Ubuntu:
> Incomplete
>
> Bug description:
> My multifunction Samsung SCX3200 printer is not detected by sane, but
> printing is fine. This scanner is faily generic and supported out of
> the box by the Xerox MFP driver (sane default).
>
> Printer/scanner as seen by the kernel, device 007 : ID 04e8:3441
>
>
> --------------------------------------------------------------------------------------------
> $ lsusb
> Bus 002 Device 003: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure
> Applications Processor
> Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
> Bus 003 Device 007: ID 04e8:3441 Samsung Electronics Co., Ltd
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> --------------------------------------------------------------------------------------------
>
> The IDs are properly set in udev and sane.d configuration:
>
>
> --------------------------------------------------------------------------------------------
> $ cat /lib/udev/rules.d/40-libsane.rules | grep 3441
> ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="3441",
> ENV{libsane_matched}="yes"
>
> $ cat /etc/sane.d/xerox_mfp.conf | grep 3441
> usb 0x04e8 0x3441
>
> --------------------------------------------------------------------------------------------
>
> Problem: sane-find-scanner can't find the scanner:
>
>
> --------------------------------------------------------------------------------------------
> $ sudo sane-find-scanner -q
> $ (no output)
> $ sudo 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-scanne...

Read more...

Revision history for this message
Gael (gael-legoff) wrote :

Same problem here (on a different scanner though).

Booting on the Vivid ISO from Nov. 14th worked like a charm on a HP PSC 2400 using a USB3 port.
Thanks.

Revision history for this message
penalvch (penalvch) wrote :

Gael, if you want that issue addressed in a release prior to Vivid, please file a new report via a terminal:
ubuntu-bug sane-backends

Revision history for this message
Chris (kabkrzys) wrote :

have the same problem ( scx 3200 print but not scan ), usb 3.0.

solution:
download latest samsung linux driver ( http://downloadcenter.samsung.com/content/DR/201407/20140709152909044/ULD_V1.00.27.04.tar.gz )
unpack, "./install.sh" - now scanning work fine ;)

Revision history for this message
penalvch (penalvch) wrote :

Chris, if you want that issue addressed in in Ubuntu, please file a new report via a terminal:
ubuntu-bug sane-backends

As well, please feel free to subscribe me to it.

Revision history for this message
Theor (theor) wrote :

Chistopher,
Just tried a 15.04 Vivid VM and indeed it works out of the box, unlike Trusty.

Chris,
Of course it works if you install the proprietary drivers, but it's merely a workaround. Who wants to install ~30mb of proprietary blobs when the OSS driver works fine.

Revision history for this message
penalvch (penalvch) wrote :

Theor, thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because as per your comment https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1312594/comments/29 the bug has been fixed in the latest development version of Ubuntu - Vivid Vervet.

This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in sane-backends (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
Theor (theor) wrote :

Thank you Christopher for your follow-up, it's a pleasure to help.

Since Trusty is an LTS release and will be there for quite some time, I think it is more than appropriate to backport this fix before more users run into this issue. I will get in touch with the ubuntu-bug control team and see what can be done.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.