The archive stays mounted and I can stil browse it (i.e. in Nautilus it shows under places and I can navigate its folder structure), but _obviously_ the files cannot be found when trying to read them e.g. when trying to copy a file or reading it in gedit. Unmounting the archive afterwards also goes just fine.
I'm wondering, though, if from a user experience point of view it wouldn't be smarter to either not allow deleting a mounted archive, or to umount it when it is deleted.
I can confirm that gvfsd-archive no longer chrashes with libarchive12 3.0.3-6ubuntu1 in Ubuntu precise/12.04.
$ apt-cache policy libarchive12 archive. ubuntu. com/ubuntu/ precise/main amd64 Packages dpkg/status
libarchive12:
Installed: 3.0.3-6ubuntu1
Candidate: 3.0.3-6ubuntu1
Version table:
*** 3.0.3-6ubuntu1 0
500 http://
100 /var/lib/
The archive stays mounted and I can stil browse it (i.e. in Nautilus it shows under places and I can navigate its folder structure), but _obviously_ the files cannot be found when trying to read them e.g. when trying to copy a file or reading it in gedit. Unmounting the archive afterwards also goes just fine.
I'm wondering, though, if from a user experience point of view it wouldn't be smarter to either not allow deleting a mounted archive, or to umount it when it is deleted.
tl;dr: Fixed.