summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorOndrej Holy <oholy@redhat.com>2022-06-29 08:49:45 +0200
committerOndrej Holy <oholy@redhat.com>2022-07-01 07:30:23 +0000
commit2761d1beb9160416d4a62392fc21cc6d30a7e92c (patch)
treec4a81ed93ec1bd3fc5e9b9434d4f96961c8108e8
parent67783336910eb075e673a6b2ff45f7d3d216407c (diff)
downloadgvfs-2761d1beb9160416d4a62392fc21cc6d30a7e92c.tar.gz
goa: Prevent automounts when resuming from suspension
When on WiFi, the NextCloud account is automatically mounted after resuming from suspension. This is because the `Account.AttentionNeeded` property changes its value and GOA volume monitor calls mount operation in that case. It is not obvious to me why this code is here. Also this is maybe bug on GOA side. But anyway, other backends simply just unmount when something changes, but don't mount again automatically. I suppose we should do the same here as well to avoid these unwanted automounts. Fixes: https://gitlab.gnome.org/GNOME/gvfs/-/issues/634
-rw-r--r--monitor/goa/goavolume.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/monitor/goa/goavolume.c b/monitor/goa/goavolume.c
index 5e9097c6..49906f30 100644
--- a/monitor/goa/goavolume.c
+++ b/monitor/goa/goavolume.c
@@ -99,8 +99,6 @@ account_attention_needed_cb (GObject *_object, GParamSpec *pspec, gpointer user_
g_clear_object (&self->mount);
}
}
- else
- g_volume_mount (G_VOLUME (self), G_MOUNT_MOUNT_NONE, NULL, NULL, NULL, NULL);
}
/* ---------------------------------------------------------------------------------------------------- */