← Back to team overview

simple-scan-team team mailing list archive

[Bug 897469] Re: Simple Scan crashes result in preventable data loss

 

For the record, here's my comment about my branch that I wrote to Robert
earlier.

I'm still struggling with the last pieces. What I'm doing is scan a page, simulate a crash with ctrl+c, and then start a new instance. This should load the old page automatically. This is almost happening as it should. The pixel data is loaded correctly because I can export
it to pdf, but it is not shown on screen. I'm probably missing atrigger somewhere. Can you easily spot what I'm missing?

I used a Sqlite database to save all the data. I tried to work with
libgda-4.0 first, but the vala bindings are too buggy to rely on. Now
I'm using sqlite directly.

-- 
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:
  Triaged

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


References