Skanlite quits when it starts saving an image

Bug #437841 reported by jarkod
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
sane-backends (Ubuntu)
Invalid
Undecided
Unassigned
Nominated for Karmic by Raul Morera

Bug Description

Binary package hint: skanlite

Kubuntu 9.10 Alpha 6

skanlite 0.3-kde4.3.0-ubuntu1~ppa1
libsane 1.0.20-4ubuntu2
sane-utils 1.0.20-4ubuntu2
libksane 4:4.3.1-0ubuntu2

Every time I want to save a scanned image (no matter pre-scanned or scanned) skanlite quits without an error message. I tried to run it from a konsole but no information (reasons for quitting) was shown. The same happens when I used quiteinsane or xsane so the bug doesn't necessarily has to be skanlite related. The scanner I use is HP scanjet 3530c which is recognised correctly. If I choose an another source for a skanlite (Winfast TV-card), images are correctly saved.

ProblemType: Bug
Architecture: i386
Date: Sun Sep 27 22:55:47 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: skanlite 0.3-kde4.3.0-0ubuntu1~ppa1
ProcEnviron:
 LANGUAGE=
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SourcePackage: skanlite
Uname: Linux 2.6.31-11-generic i686

Revision history for this message
jarkod (rydberg-o2) wrote :
affects: skanlite (Ubuntu) → kdegraphics (Ubuntu)
affects: kdegraphics (Ubuntu) → sane-backends (Ubuntu)
Revision history for this message
penalvch (penalvch) wrote :

jarkod, 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.