App crashes trying a Photo-Scan from MFC-J4420DW

[Locutus of Borg]

Hi,
the problem:

I tried on more than one machine to scan over network a photo using my Brother MFC-J4420DW.
Simple Scan got every time a segmentation fault and crashes, BEFORE the scan can start.
I hear the scanner working an I assume, as soon it starts to transfer the data, simple scan crashes.
I've attached the debug output from simple-scan -d to this bug report (simple-scan.log), it may help.

But more interessting is: if I do a scan with only black/white (text resolution) it works!

The DPI resolution seem to be not relevant for the problem neither in color nor in b/w.

Now I tried both scan types (Color & B/W) with xsane:
ii xsane 0.998-5ubuntu1 amd64 featureful graphical frontend for SANE (Scanner Access Now Easy)
ii xsane-common 0.998-5ubuntu1 all featureful graphical frontend for SANE (Scanner Access Now Easy)

That's working fine, but isn't so comfortable as simple-scan. :-)

Now I assume that it may be not the problem of the brother driver, because xsane is working fine.

The installed drivers from brother:
ii brscan-skey 0.2.4-1 amd64 Brother Linux scanner S-KEY tool
ii brscan4 0.4.2-1 amd64 Brother Scanner Driver

I also own an Brother MFC-J4510DW, with this one I never have such a problem like with the J4420DW.
(It's also only accessible over network like the other one.)

May there is a solution for my problem.

Thx a lot in advance.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: simple-scan 3.12.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jan 8 21:14:35 2015
DriverPackageVersions:
 libsane 1.0.23-3ubuntu3.1
 libsane-extras N/A
 hplip 3.14.3-0ubuntu3.2
 hpoj N/A
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-10-30 (435 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Dell Inc. XPS 8700
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic.efi.signed root=UUID=c8562224-0acf-4c22-a807-f1431050facf ro quiet splash vt.handoff=7
SourcePackage: simple-scan
UpgradeStatus: Upgraded to trusty on 2014-05-10 (243 days ago)
dmi.bios.date: 04/16/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0KWVT8
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA02:cvnDellInc.:ct3:cvr:
dmi.product.name: XPS 8700
dmi.sys.vendor: Dell Inc.

[penalvch (penalvch)]

Locutus of Borg, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing.

Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y dist-upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open a terminal, navigate to your /var/crash directory and file your report with:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

where _my_crash_report.crash is the crash you would like to report. By default, this sends the crash to the Ubuntu Error Tracker infrastructure, which is different than Launchpad. For more on this, please see https://wiki.ubuntu.com/ErrorTracker .

However, if after doing this you would still like to have a crash report posted to Launchpad, for example to ease triage and add others to your report, one would need to open the following file via a terminal:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and file the crash report via:
sudo ubuntu-bug /var/crash/FILENAME.crash

Where FILENAME is the actual name of the file found in the folder.

However, this report is being closed since the process outlined above will deal with this issue more efficiently.

Also, please do not attach your crash report manually to this report and reopen it.

Thank you for your help.

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