Now I'm seeing that GVolumeManager is emitting the wrong signals when a loopback device is mounted or unmounted -- it is emitting exactly the opposite signals it should.
$ ./gio-test &
$ sudo losetup /dev/loop0 /your/favorite.iso
$ sudo mount -t iso9660 /dev/loop0 /mnt
** (process:28520): DEBUG: received drive-disconnected event for '731 MB File'.
** (process:28520): DEBUG: received volume-removed event for 'Ubuntu 10.04 LTS amd64'.
$ sudo umount /mnt
** (process:28520): DEBUG: received drive-connected event for '731 MB File'.
** (process:28520): DEBUG: received volume-added event for 'Ubuntu 10.04 LTS amd64'.
Note that when you mount the device, we get a drive-disconnected and volume-removed event and when we unmount the device, we get a drive-connected and volume-added event.
But when I mount other devices, gio-test displays the expected output.
Now I'm seeing that GVolumeManager is emitting the wrong signals when a loopback device is mounted or unmounted -- it is emitting exactly the opposite signals it should.
First run this test program: /code.launchpad .net/~ayan/ +junk/gio- test
https:/
This is what I get:
$ ./gio-test &
$ sudo losetup /dev/loop0 /your/favorite.iso
$ sudo mount -t iso9660 /dev/loop0 /mnt
** (process:28520): DEBUG: received drive-disconnected event for '731 MB File'.
** (process:28520): DEBUG: received volume-removed event for 'Ubuntu 10.04 LTS amd64'.
$ sudo umount /mnt
** (process:28520): DEBUG: received drive-connected event for '731 MB File'.
** (process:28520): DEBUG: received volume-added event for 'Ubuntu 10.04 LTS amd64'.
Note that when you mount the device, we get a drive-disconnected and volume-removed event and when we unmount the device, we get a drive-connected and volume-added event.
But when I mount other devices, gio-test displays the expected output.