← Back to team overview

simple-scan-team team mailing list archive

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

 

I haven't been able to resolve the issue with refreshing yet. It would
probably take someone familiar with the rendering code very little time
to find out what's going on.

There's also one more thing. As it is now, the code uses a process id to
know whether simple-scan is running and whether it should recover any
pages. There could be problems if one uses two instances on two
different computers sharing a home directory (via nfs, say). Then one
instance will try to take ownership of the pages of the other. A
possible solution would involve making simple-scan unique (using
GtkApplication) and then using some sort of (dbus?) session id to tag
the autosaves, instead of just the process id.

On the other hand, one could argue that even if two machines share the
same home directory, they should have a local .cache directory. Then the
problem disappears entirely.

I haven't researched this yet, and perhaps it is not the use case we are
aiming for.

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