desktop-packages team mailing list archive

[jpeg <1388580@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

(This is my first bug report.)
Simple-scan was not able to start after a previous crash.
The first crash is not my concern.
My concern was that I could not restart Simple-scan.

I found the way to restart simple scan: I deleted the folder ~/.cache/simple-scan/
I think this comes from the autosave feature that tries to reload the previously scanned page when application restarts.
In my case the scanned page that caused the original crash was 1,7 GB big (the size of the file 166455856.pixels in ~/.cache/simple-scan/autosaves) since I used the highest resolution (2400 ppp). So I did not want to reload this file, I wanted to be able to start a new scan.

I attached the debug output of a "simple-scan -d" launch. Maybe simple-
scan could be made immune from glib errors at startup and start without
loading the previously scanned document in this case.

I think it will be in the attached debug information but I mention it to be sure: I am running Ubuntu 14.10.
And for information, the original crash that happened when I scanned with a too high resolution was on Ubuntu 14.04.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: simple-scan 3.14.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8
Architecture: i386
CurrentDesktop: Unity
Date: Sun Nov  2 16:31:20 2014
InstallationDate: Installed on 2012-08-25 (798 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Build i386 LIVE Binary 20120426-12:41
MachineType: Hewlett-Packard p6-2040fr
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=140c6c6b-3b6a-439d-ac98-b314bac9bdd5 ro quiet splash
SourcePackage: simple-scan
UpgradeStatus: Upgraded to utopic on 2014-10-30 (3 days ago)
dmi.bios.date: 09/28/2011
dmi.bios.vendor: AMI
dmi.bios.version: 7.13
dmi.board.name: 2ABF
dmi.board.vendor: Foxconn
dmi.board.version: 1.20
dmi.chassis.asset.tag: CZC1422Q45
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnAMI:bvr7.13:bd09/28/2011:svnHewlett-Packard:pnp6-2040fr:pvr:rvnFoxconn:rn2ABF:rvr1.20:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: p6-2040fr
dmi.sys.vendor: Hewlett-Packard

** Affects: simple-scan (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-bug i386 utopic

** Attachment added: "debug_output.txt"
   https://bugs.launchpad.net/bugs/1388580/+attachment/4251374/+files/debug_output.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
https://bugs.launchpad.net/bugs/1388580

Title:
  Application crash when scanning a big file with high resolution, not
  able to restart simple-scan

Status in “simple-scan” package in Ubuntu:
  New

Bug description:
  (This is my first bug report.)
  Simple-scan was not able to start after a previous crash.
  The first crash is not my concern.
  My concern was that I could not restart Simple-scan.

  I found the way to restart simple scan: I deleted the folder ~/.cache/simple-scan/
  I think this comes from the autosave feature that tries to reload the previously scanned page when application restarts.
  In my case the scanned page that caused the original crash was 1,7 GB big (the size of the file 166455856.pixels in ~/.cache/simple-scan/autosaves) since I used the highest resolution (2400 ppp). So I did not want to reload this file, I wanted to be able to start a new scan.

  I attached the debug output of a "simple-scan -d" launch. Maybe
  simple-scan could be made immune from glib errors at startup and start
  without loading the previously scanned document in this case.

  I think it will be in the attached debug information but I mention it to be sure: I am running Ubuntu 14.10.
  And for information, the original crash that happened when I scanned with a too high resolution was on Ubuntu 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: simple-scan 3.14.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sun Nov  2 16:31:20 2014
  InstallationDate: Installed on 2012-08-25 (798 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build i386 LIVE Binary 20120426-12:41
  MachineType: Hewlett-Packard p6-2040fr
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=140c6c6b-3b6a-439d-ac98-b314bac9bdd5 ro quiet splash
  SourcePackage: simple-scan
  UpgradeStatus: Upgraded to utopic on 2014-10-30 (3 days ago)
  dmi.bios.date: 09/28/2011
  dmi.bios.vendor: AMI
  dmi.bios.version: 7.13
  dmi.board.name: 2ABF
  dmi.board.vendor: Foxconn
  dmi.board.version: 1.20
  dmi.chassis.asset.tag: CZC1422Q45
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: dmi:bvnAMI:bvr7.13:bd09/28/2011:svnHewlett-Packard:pnp6-2040fr:pvr:rvnFoxconn:rn2ABF:rvr1.20:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6-2040fr
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1388580/+subscriptions