xsane crashed with SIGFPE

Bug #204621 reported by Åskar
38
This bug affects 3 people
Affects Status Importance Assigned to Milestone
xsane (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: xsane

Crashed when trying to scan with canoscan 3200F

ProblemType: Crash
Architecture: i386
Date: Fri Mar 21 14:08:10 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/xsane
NonfreeKernelModules: ath_hal
Package: xsane 0.995-1ubuntu1
PackageArchitecture: i386
ProcCmdline: xsusernamene
ProcEnviron:
 PATH=/usr/locusernamel/sbin:/usr/locusernamel/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/gusernamemes
 LANG=en_US.UTF-8
 SHELL=/bin/busernamesh
Signal: 8
SourcePackage: xsane
Stacktrace:
 #0 0x080b5674 in ?? ()
 #1 0x08458010 in ?? ()
 #2 0x00000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
ThreadStacktrace:
 .
 Threusernamed 1 (process 16218):
 #0 0x080b5674 in ?? ()
 #1 0x08458010 in ?? ()
 #2 0x00000000 in ?? ()
Title: xsane crashed with SIGFPE
Uname: Linux 2.6.24-12-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

Tags: apport-crash
Revision history for this message
Åskar (olskar) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:xsane_scan_done (status=SANE_STATUS_EOF) at xsane-scan.c:1055
xsane_read_image_data (data=0x0, source=-1, cond=GDK_INPUT_READ)
xsane_start_scan () at xsane-scan.c:1860
xsane_scan_dialog (data=0x0) at xsane-scan.c:2160
xsane_scan_callback () at xsane.c:3922

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in xsane:
importance: Undecided → Medium
Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Confirming this bug, because it happens to several users.

Changed in xsane (Ubuntu):
status: New → Confirmed
Revision history for this message
dino99 (9d9) wrote :

That version has died long ago; no more supported

Changed in xsane (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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