VolueMonitor returns misleading information
I'm using Gio.VolumeManager to track mounted disks/volumes as was proposed here: https://github.com/quodlibet/quodlibet/blob/32b4f0ca4d2eb0cb2dc0497aaef3e85fbf0f6178/quodlibet/quodlibet/ext/events/automask.py#L21
The problem is here:
- When I iterate over disks -> volumes -> mounts [https://paste.gnome.org/pyhaxih0u] to see all mount points - I see that no mount point for device [ASUS BW-16D1HT] [https://paste.gnome.org/pim6o2wrk]. But I can see them already mounted in Nautilus, and "gio mount -l" shows I have mounted point.
- When I call get_mounts() directly I see that mount point, but get_drive() and get_volume() returns None. But as shown in screenshot "gio mount -l" shows I have full hierarchy "Device [ASUS BW-16D1HT] -> Volume(0): Audio Disc -> Mount(0): Audio Disc -> cdda://sr0/".
- Call handler is invoked "mount-added" every time I run application regardless I haven't changed anything with this drive / volume / disk.
What I think how this should work:
- Mount point (for Audio disk) (even it GVFS emultation) should always have correct volume / drive. How is that possible I have mounted Audio Disk inserted in Optical disc drive (which is device) and get None from get_drive() and get_volume() (Disk Utility shows I have volume too)?
- Don not emit / call callback for "mount-added" signal, as nothing has changed ( I didn't added / removed / ejected audio disk) (and this happens only for Audio Disk, for already inserted USB drive this signal is not emmited)
Edited by Christoph Reiter