This looks a lot like bug #1452422 which claims to have been fixed already. Can you try to work around it by specifying image-metadata-url? (See comment #4 in that bug)
This looks a lot like bug #1452422 which claims to have been fixed already. Can you try to work around it by specifying image-metadata-url? (See comment #4 in that bug)