Opened 10 years ago

Closed 10 years ago

#825 closed defect (duplicate)

Problem with one special jpg

Reported by: janssen Owned by:
Priority: major Milestone:
Component: programming Keywords:
Cc: Parent Tickets:

Description

Hello

I am having problems with one special jpg file. I created it with Darktable. When i do upload this picture, everything works fine, but i can not display it. mediagoblin throws a Server Error (Error - <type 'exceptions.AttributeError'>: type object 'datetime.datetime' has no attribute 'datetime'). If I open this picture in Gimp and export it es jpg (no other changes), the picture can be disbelayed without a problem.

i added both pictures

Change History (7)

comment:1 by janssen, 10 years ago

picuters seems to be too big to upload.

i’ll upload them asap.

comment:2 by janssen, 10 years ago

alright:

file modified with darktable (cannot be displayed): http://aurka.com/pictures/img_0001_darktable.jpg

same file just opened and re-saved with gimp (can be displayed): http://aurka.com/pictures/img_0001_gimp.jpg

any idea?

in reply to:  2 comment:3 by saul, 10 years ago

Replying to janssen:

For whatever it's worth, I encountered no such error when uploading the file:

http://barn.kerosenecow.net/u/saul/m/test-upload-of-jpeg/

comment:4 by Dave Lahn, 10 years ago

I was also able to upload the JPEG without issue.

http://media.lahn.ca/u/delparnel/m/darktable/

comment:5 by janssen, 10 years ago

well, it’s quite odd.

I can shoot a photo with my D7000 dslr in NEF format.

Edit it with darktable:

darktable    1.4.1-1     amd64   virtual lighttable and darkroom for photographers

export as JPG (8bit) and upload it to my mediagoblin instance => failure. Uploading works fine, but image cannot be displayed.

when i open the image with gimp and export it as jpg, it works like a charm :(

comment:6 by Sebastian Hugentobler, 10 years ago

I had the same problem but overlooked this ticket.
So my solution is in #865

Sorry for the oversight.

comment:7 by Christopher Allan Webber, 10 years ago

Resolution: duplicate
Status: newclosed

It sounds like this is fixed then in #865, which is also now fixed!

Horray!

Note: See TracTickets for help on using tickets.