Bug Description

Binary package hint: gnome-vfs-obexftp

When I view my phone in nautilus using obex://, I can acces the phone's filesystem fine, including the 2 GB SD in it. My phone has about 5 MB free, the SD card is nearly empty. gnome-vfs-obexftp is only reporting the free space in the phone's memory; it does not recognize that the folder that represents the SD card can have a different amount of free space than the phone itself.

The upshot is that I can only copy files over in chunks that are smaller than the amount of free space on the phone.

It seems like this should be reproducible by
- setting up a phone with a micro SD card to work with blutooth
- browsing to the phone in nautilus using obex://
- Checking the free space that nautilus reports
- Navigating to the folder that contains the SD card data
- Verify that the phone memory free space is still being reported, not the SD card free space

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:

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 ...

Just tried restarting Nautilus again, and things started working. Nautilus now shows 25.2MB free on the memory card, and it let me copy a file to the memory card that wouldn't fit on the phone's memory.

So this bug will be fixed for the 0.3 release (provided you have a Nokia phone, or one that provides the same data in folder listings).

I have tried both 0.2 and 0.3 with my SonyEriksson z710. Both versions report 0 bytes free space, so I can't copy anyting to the phone. I tried 0.2 with my old phone K610 and that worked, but that phone didn't have a memory card.

So in short... this bug still is valid for new SonyEricsson mobiles with memory cards

Just to be sure I tested again and restarted everyting (including phone, nautilus, bluez, gnome-vfs-daemon) and still not working.
The phone is paired, and I can access the phone and browse the content, copy from the phone to the desktop but not to the phone.

Matthias: I don't think your problem is related to this bug report -- this one is about distinguishing what volume a particular directory resides on and returning the appropriate free space. Your one sounds more like faulty reporting of free space.

I've heard of a few other people having trouble with Sony phones, but don't have the hardware to debug it. If you would like to help me debug the problem, I suggest opening a new bug report. I've got a few commands you could run to collect data that would be useful in tracking down the problems.

I Had a similar problem with a Sony Ericsson W595 with a 2GB M2 memory card, and resorted to purchasing a external card reader for a few pounds. I do have to admit this was an easy way out and avoided correcting the real problem. :(