Hello Gilles CHARABOT, Thanks for the backtrace. I'll start with a few observations:
You're running gvfs 1.34.1-2. Crash (assertion failure) seems to happen when the volume_mount_cb function calls into g_proxy_volume_mount_finish which leads us to g_simple_async_result_propagate_error. Earlier in the backtrace we're coming from g_task_return_now so we're definitely mixing g_task with G_simple_async_result which as smcv already explained it a bad mix. I'm not sure exactly where the problem is initiated or introduced but given that there where so GTask changes introduced in 1.33.3 I'd guess this might be where the problem was introduced: https://git.gnome.org/browse/gvfs/commit/?id=2eae1086656ebfa1b8eb Further GTask porting has been done in the development releases after the stable version currently in debian, and the fix is likely to already be available in them. More exactly I expect this commit to fix your particular issue: https://git.gnome.org/browse/gvfs/commit/?id=1f5fcbe8d7b8a2975ef The above commit together with several other GTask related commits are part of 1.35.3. It would be great if you could provide feedback if the newer version fixes your issue, either once it's available in Debian Experimental or if you could update the package yourself in the meantime. HTH. Regards, Andreas Henriksson
