simple scan crashes when trying to scan at 2400dpi on canon pixma mp160

Bug #560982 reported by malcolm hall
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sane-backends (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: simple-scan

lucid lynx beta2 live cd with canon pixma mp160

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: simple-scan 0.9.10-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
Date: Sun Apr 11 20:45:01 2010
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
MachineType: Compaq Evo N1015v
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   3.3V 32-bit PC Card
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SimpleScanLog:

SourcePackage: simple-scan
dmi.bios.date: 02/10/2003
dmi.bios.vendor: Phoenix
dmi.bios.version: 0F09
dmi.board.name: 07D4h
dmi.board.vendor: Compaq
dmi.board.version: KBC Revision: 1326
dmi.chassis.type: 10
dmi.chassis.vendor: Compaq
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenix:bvr0F09:bd02/10/2003:svnCompaq:pnEvoN1015v:pvr0100:rvnCompaq:rn07D4h:rvrKBCRevision1326:cvnCompaq:ct10:cvrN/A:
dmi.product.name: Evo N1015v
dmi.product.version: 0100
dmi.sys.vendor: Compaq

Revision history for this message
malcolm hall (mal-hall) wrote :
affects: simple-scan (Ubuntu) → sane-backends (Ubuntu)
Revision history for this message
penalvch (penalvch) wrote :

malcolm hall, 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

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

Other bug subscribers

Remote bug watches

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