simple-scan-team team mailing list archive

[Timo Kluck <897469@xxxxxxxxxxxxxxxxxx>]

I'm not currently working on this. I have no way to reproduce the
errors Robert is seeing and it works for me. Given the limited time I
can spend on this (having an unrelated job and all) it would be much
more efficient if someone experiencing the issue could try some
debugging on their machine.

Your testing would be more than welcome. Here's how to go about it:

sudo apt-get build-dep simple-scan
sudo apt-get install libsqlite3-dev
bzr branch lp:~tkluck/simple-scan/autosaves simple-scan-autosaves
cd simple-scan-autosaves
./autogen.sh && ./configure && make
src/simple-scan test

(now click "scan", wait for the scan to finish, and interrupt the
process using ctrl+C in the terminal

src/simple-scan test

(now you should see the scanned document reappear)

-- 
You received this bug notification because you are a member of Simple
Scan Development Team, which is the registrant for Simple Scan.
https://bugs.launchpad.net/bugs/897469

Title:
  Simple Scan crashes result in preventable data loss

Status in Simple Scan:
  In Progress

Bug description:
  As a matter of fact Simple Scan crashes often. Bad drivers, Out Of
  Memory Problems, ...

  These problems should be fixed, but for the meanwhile it would be worthwhile to minimize data and time lost in such cases.
  For the bad drivers cases there already is Bug #564357 but especially for the OOM problem and to take some pressure from the complex Bug #564357 I suggest to look for other ways to minimize data loss.

  Ideas: 
  - save work to temporary files, and optimally allow to recover from such files (can perfectly be combined with the feature request to manually load a file at startup to add pages to that file).
  - ...

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