Comment 2 for bug 116912

Daniel: I haven't yet set up a place to report bugs in gnome-vfs-obexftp. I should probably register it on Launchpad ...

The obexftp method is just using the free space number for the first memory type.

I notice the bug on my phone: it is returning the free space for the phone even though I have an MMC card. Looking at a directory listing ("obexftp --bluetooth ... --list"), I see that it does tell me the memory type for each item in the root directory:

  <?xml version="1.0"?>
  <!DOCTYPE folder-listing SYSTEM "obex-folder-listing.dtd"
   [ <!ATTLIST folder mem-type CDATA #IMPLIED> ]>
  <folder-listing version="1.0">
      <folder name="Memory card" user-perm="RW" mem-type="MMC"/>
      <folder name="Images" created="19800101T000008" user-perm="R" mem-type="DEV"/>
      <folder name="Video clips" created="19800101T000008" user-perm="R" mem-type="DEV"/>
      <folder name="Music files" created="19800101T000008" user-perm="R" mem-type="DEV"/>
      <folder name="Graphics" created="19800101T000008" user-perm="R" mem-type="DEV"/>
      <folder name="Tones" created="19800101T000008" user-perm="R" mem-type="DEV"/>
      <folder name="Recordings" created="19800101T000008" user-perm="R" mem-type="DEV"/>
  </folder-listing>

So with this listing, I should be using the "DEV" free space value for "/Images", but the "MMC" free space value for "/Memory card". I've got no idea if there is a more direct way to work this out than listing the parent folder to find the memory type.

So the bug does look fixable, which is good. The alternative would have been to remove the free space calculation code ...