With the gdu volume monitor, the handling of floppies in GNOME got broken.

devkit-disks detects the floppy:

which is transformed into a gvfs drive without a volume:

Drive(1): Diskettenlaufwerk
  Type: GProxyDrive (GProxyVolumeMonitorGdu)
  ids:
   unix-device: '/dev/fd0'
  themed icons: [drive-removable-media-floppy] [drive-removable-media] [drive-removable] [drive]
  is_media_removable=1
  has_media=0
  is_media_check_automatic=0
  can_poll_for_media=1
  can_eject=0
  can_start=0
  can_stop=0
  start_stop_type=unknown

(Unlike CD-ROMs, there is no polling for floppy volumes, since that'd keep the drive busy all the time). Now when you try to mount it, gvfs does not have any associated volume and thus fails:

  $ gvfs-mount -d /dev/fd0
  No volume for device file /dev/fd0

Interestingly, when you log into such a box remotely, and you don't have a session bus running, it works: gvfs-mount -oi sees only a volume

Volume(1): floppy0
  Type: GUnixVolume
  ids:
   unix-device: '/dev/fd0'
  themed icons: [drive-removable-media] [drive-removable] [drive]
  can_mount=1
  can_eject=0
  should_automount=1

which you can mount with gvfs-mount -d /dev/fd0 just fine.

For remote reproduction:

   gvfs-mount -li  -> only drive (unmountable)
   dbus-launch gvfs-mount -li  -> only volume (mountable)

If we have a drive with is_media_check_automatic=0 and has_media=0, can we teach gvfs to just try and create a volume anyway?