Don’t require a GVolumeMonitor reference to use GMount/GVolume/GDrive
Following on from #1458 (closed), it seems that there needs to be a GVolumeMonitor
instance alive in order for any GMount
/GVolume
/GDrive
behaviour to be correct.
This is not documented, and requires people to know about internal GLib behaviour in order to make their applications behave correctly, which is a leak of implementation details.
We should either:
- Internally hold a
GUnixVolumeMonitor
reference fromGUnixMount
/GUnixDrive
/GUnixVolume
in order to get mtab updates for them. - Always have a
GVolumeMonitor
running in the GLib worker thread.