I agree in an ideal world all software, at least core software like gdm3, should handle such errors more gracefully and keep working. However finding the time and expertise to make that a reality means it's probably not realistic any time soon.
A more realistic fix is to find what's using up all the resources (if not disk space) and fix/remove that. Please confirm for us if removing/disabling "crashplan" does also workaround the problem, or if the trigger lays in some other software package.
Dan,
I agree in an ideal world all software, at least core software like gdm3, should handle such errors more gracefully and keep working. However finding the time and expertise to make that a reality means it's probably not realistic any time soon.
A more realistic fix is to find what's using up all the resources (if not disk space) and fix/remove that. Please confirm for us if removing/disabling "crashplan" does also workaround the problem, or if the trigger lays in some other software package.