simple-scan segfaults with "Floating point exception (core dumped)"

[Raphael]

simple-scan and xsane both segfault every time I press "scan" in them. The details I see from apport get reported automatically but I can't tell how to see them locally. However, by visual inspection they look a lot like

https://bugs.launchpad.net/ubuntu/+source/xsane/+bug/204621

My scanner is a Canon lide 210

How can I include the information apport automatically catches when it segfaults?

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: simple-scan 3.12.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Oct 25 09:56:05 2014
DriverPackageVersions:
 libsane 1.0.23-3ubuntu3.1
 libsane-extras N/A
 hplip 3.14.3-0ubuntu3.2
 hpoj N/A
InstallationDate: Installed on 2013-10-01 (388 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=80919e96-e83b-4c88-b30e-8673e1faa3b4 ro quiet splash vt.handoff=7
SourcePackage: simple-scan
UpgradeStatus: Upgraded to trusty on 2014-04-22 (185 days ago)
dmi.bios.date: 02/18/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.name: 880GM-LE FX
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd02/18/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn880GM-LEFX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Raphael (drraph)]

I do have a file https://bugs.launchpad.net/ubuntu/+source/xsane/+bug/204621 so maybe that would be helpful?

In the meantime I ran it in gdb and get

(gdb) run
Starting program: /usr/bin/simple-scan
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffee301700 (LWP 30100)]
[New Thread 0x7fffedb00700 (LWP 30101)]
[New Thread 0x7fffe534d700 (LWP 30102)]
[New Thread 0x7fffdd10a700 (LWP 30103)]
[New Thread 0x7fffdc909700 (LWP 30104)]
[New Thread 0x7fffd7fff700 (LWP 30105)]
[New Thread 0x7fffd77fe700 (LWP 30106)]
[Thread 0x7fffd7fff700 (LWP 30105) exited]
[New Thread 0x7fffd7fff700 (LWP 30108)]

Program received signal SIGFPE, Arithmetic exception.
[Switching to Thread 0x7fffe534d700 (LWP 30102)]
0x00007fffc34f3a9b in ?? () from /usr/lib/x86_64-linux-gnu/sane/libsane-genesys.so.1
(gdb) bt
#0 0x00007fffc34f3a9b in ?? () from /usr/lib/x86_64-linux-gnu/sane/libsane-genesys.so.1
#1 0x00007fffc34c6cb5 in ?? () from /usr/lib/x86_64-linux-gnu/sane/libsane-genesys.so.1
#2 0x00007fffc34cdd30 in sane_genesys_start () from /usr/lib/x86_64-linux-gnu/sane/libsane-genesys.so.1
#3 0x0000000000423f8d in ?? ()
#4 0x00007ffff6275f15 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x00007ffff58c2182 in start_thread (arg=0x7fffe534d700) at pthread_create.c:312
#6 0x00007ffff55eefbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

[Simeon-miteff (simeon-miteff)]

A calibration step in libsane's genesys_gl124.c measures the average illumination (line ~3062) and then uses that value in a division on line ~3090.

The divisor would probably never be zero if your scanner is working, but if the LEDs are not turning on then all bets are off!

I plugged my scanner into a different USB port, and that fixed it. I suspect it is a USB power supply issue preventing the LEDs from working.

[penalvch (penalvch)]

Raphael, 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