summaryrefslogtreecommitdiff
path: root/daemon
diff options
context:
space:
mode:
authorBastien Nocera <hadess@hadess.net>2016-06-08 16:34:45 +0200
committerBastien Nocera <hadess@hadess.net>2016-06-09 11:57:50 +0200
commit8c8aa6a8f790b1db546fbc2e81c7127172d5e2bf (patch)
tree1149ba59a86eb35d0d1cd8537e5cbaff95eebe56 /daemon
parent478b0691b3ec4f9829e2d05e692187f0f29ba513 (diff)
downloadgvfs-8c8aa6a8f790b1db546fbc2e81c7127172d5e2bf.tar.gz
afc: Fix mount failing after trusting device
After having trusted the device, if we are too quick at clicking the "Try Again" button, the creation will fail with an unknown error. Try again silently up to the maximum number of retries after a short sleep. https://bugzilla.gnome.org/show_bug.cgi?id=767399
Diffstat (limited to 'daemon')
-rw-r--r--daemon/gvfsbackendafc.c8
1 files changed, 8 insertions, 0 deletions
diff --git a/daemon/gvfsbackendafc.c b/daemon/gvfsbackendafc.c
index 57d21a49..3da3cafa 100644
--- a/daemon/gvfsbackendafc.c
+++ b/daemon/gvfsbackendafc.c
@@ -616,6 +616,14 @@ g_vfs_backend_afc_mount (GVfsBackend *backend,
break;
}
+ /* An unknown error? Let's try again without prompting */
+ if (lerr == LOCKDOWN_E_UNKNOWN_ERROR)
+ {
+ g_debug ("Got an unknown lockdown error, retrying after a short sleep\n");
+ g_usleep (G_USEC_PER_SEC);
+ continue;
+ }
+
if (lerr != LOCKDOWN_E_PASSWORD_PROTECTED &&
lerr != LOCKDOWN_E_PAIRING_DIALOG_RESPONSE_PENDING)
break;