From da761575541809a3a91fad3e469aa3079f435f65 Mon Sep 17 00:00:00 2001 From: "kali kaneko (leap communications)" Date: Thu, 11 Mar 2021 04:37:51 +0100 Subject: [bug] fail gracefully on connection initialization errors There's some corner cases that were very badly captured. On the first place, it's confusing to quit on connection errors. Secondly, a side-effect of aborting the initialization of the bitmask object was a semi-random segfault when trying to access the object. Here I pass any connection errors to the gui, but leave to the user to quit the app. This probably will need more work when we want to terminate the app on unrecoverable errors (no polkit, etc...), but for now it makes the systray much more usable. - Resolves: #465 --- gui/qml/FailDialog.qml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'gui/qml') diff --git a/gui/qml/FailDialog.qml b/gui/qml/FailDialog.qml index a78690e..d151feb 100644 --- a/gui/qml/FailDialog.qml +++ b/gui/qml/FailDialog.qml @@ -16,7 +16,11 @@ MessageDialog { if (ctx.loginDialog == 'true') { login.visible = true } else { - backend.quit() + // FIXME - we probably want to distinguish + // fatal from recoverable errors. For the time being + // we can avoid quitting so that people can try reconnects if it's + // a network problem, it's confusing to quit the app. + // backend.quit() } } } -- cgit v1.2.3