simple-scan-team team mailing list archive

[Michael Nagel <ubuntu@xxxxxxxxxxxxxxxxx>]

Hi Timo,

thanks for getting active! I have not tried your code yet, but from looking at your commits this looks great!
Ultimately Robert has to approve a possible merge, though :)

two comments from my point of view:

1- how does sqlite handle crashing? this patch will not improve the
situation if one ends up with a corrupted sqlite database... does it do
transactions or do you have something like fsync to force writeout ...

2- as far as i can tell the feature request from (amongst other reports)
Bug #483392 -- namely: resuming a previous session -- could be trivially
solved with the same underlying code if there was an option to
gracefully exit simple-scan while leaving behind the sqlite-entry that
will tigger "recovery" on the next startup. could you look into adding
this?

Let me know if I can do something for you!

Best Regards
Michael

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