Created attachment 143015 [details] [review]
also set the fast content type

This started with bug 594632. Somehow, the gphoto backend reports a null
content type for the files on a camera. I haven't figured out why. We worked
around this by adding a call to g_content_type_guess, but that shouldn't be
needed
(http://git.gnome.org/cgit/gthumb/commit/?h=ext&id=b7e343131581aea8bbc39291f85b887a1de53796).

Things got really weird when debugging this with gvfs-info. Look at this:


[mjc@xena ~]$ gvfs-info gphoto2://[usb:001,005]/DCIM/100_FUJI/
display name: 100_FUJI
name: 100_FUJI
type: directory
size: 0
attributes:
  standard::name: 100_FUJI
[..snip..]


[mjc@xena ~]$ gvfs-info gphoto2://[usb:001,005]/DCIM/100_FUJI/DSCF0993.JPG
Error getting info: No such file or directory


[mjc@xena ~]$ cd .gvfs/gphoto2\ mount\ on\ usb%3A001\,005/DCIM/100_FUJI/


[mjc@xena 100_FUJI]$ gvfs-info
gphoto2://[usb:001,005]/DCIM/100_FUJI/DSCF0993.JPG
display name: DSCF0993.JPG
[..snip..]
attributes:
  standard::name: DSCF0993.JPG
[..snip..]
  standard::content-type: image/jpeg
[..snip..]
  preview::icon: GVfsIcon:0x1894c40


Summary: gvfs-info reports that the folder "100_FUJI" exists, but denies that
the photo inside exists until I "cd" to that folder. Why would it do that?


Lastly, the gphoto backend should also set the fast content type, like most
other backends. Patch attached.


- Mike