Failed to import some photos from folder
Submitted by an unknown user
Link to original bug (#718226)
Description
---- Reported by shotwell-maint@gnome.bugs 2011-10-22 17:29:00 -0700 ----
Original Redmine bug id: 4296
Original URL: http://redmine.yorba.org/issues/4296
Searchable id: yorba-bug-4296
Original author: Sat Garcia
Original description:
I use Hugin to create a fair number of panoramas, which I then import into Shotwell with the "import from folder."
Recently, I've started receiving the following type of error for pretty much every panorama I try to import:
2 photos failed to import due to a file or hardware error:
/home/moocow/Pictures/2011/10/02/panorama/PA024255-PA024258.jpg
/home/moocow/Pictures/2011/10/02/panorama/PA024256-PA024257.jpg
The files open fine if in any other photo viewing program and they even open fine if I open them with Shotwell's photo viewer.
I'm still using v.0.11.4 because v0.11.5 hasn't showed up in the ArchLinux repos yet.
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:45:00 -0700 ----
History
Comment 1
Updated by Adam Dingle about 2 years ago
Thanks for the bug report. Could you attach a couple of the photos that fail to import?
Comment 2
Updated by Jim Nelson about 2 years ago
- Category set to 4
Also, could you run Shotwell like this (from the console):
$ SHOTWELL_LOG=1 shotwell
then import those photos again. Close Shotwell and attach the following file to this ticket:
/home/moocow/.cache/shotwell/shotwell.log
Thanks!
Comment 3
Updated by Sat Garcia about 2 years ago
I'm out of town until the end of the week. I'll upload the example image as well as the result of running with SHOTWELL_LOT=1 after I'm back.
Comment 4
Updated by Lucas Beeler about 2 years ago
If you try to import only one of the photos by selecting it in Nautilus and then dragging and dropping it on the Shotwell library window, what happens?
Comment 5
Updated by Sat Garcia about 2 years ago
- File shotwell.log added
@Lucas: same thing happens when I drag and drop from Thunar.
I've attached the shotwell.log file. Unfortunlatey the panoramas I'm having the problems with are larger than 5MB so I can't upload that through redmine.
Comment 6
Updated by Adam Dingle about 2 years ago
@Sat: Since the image files are too large to attach here, could you do either of the following?
-
Upload the files somewhere and post the URL here.
-
Email the files to us at shotwell@yorba.org, including this ticket's bug number (#4296 (closed)) in the subject line.
Comment 7
Updated by Lucas Beeler about 2 years ago
Hi Sat,
Thanks for attaching your log file! It would still be really helpful if we could have a copy of one of the images that causes the problem. Since it's too large to add as an attachment here, could you mail it to shotwell@yorba.org as an attachment?
Lucas
Comment 8
Updated by Sat Garcia about 2 years ago
- File PA024256-PA024257.jpg added
Sorry for the delay. I did find one that is less than 5MB so I have attached it.
Comment 9
Updated by Adam Dingle about 2 years ago
Thanks for the photo. When I try to open it in Eye of GNOME (the default GNOME photo viewer), I see this:
Could not load image 'PA024256-PA024257.jpg'.
Error interpreting JPEG image file (Sorry, there are legal restrictions on arithmetic coding)
So it appears that Hugin is writing the JPEG files using an encoding that the JPEG reader on my system (Ubuntu Oneiric) can't handle.
Comment 10
Updated by Sat Garcia about 2 years ago
Interesting note about the "Legal restrictions on arithmetic code".
Some of the hugin JPEGs import fine; I'm not sure why they would create some with a different coding than other, since the source images I'm using for the panoramas are all from the same camera.
Does this mean you don't consider it an issue with Shotwell?
Comment 11
Updated by Adam Dingle about 2 years ago
- Status changed from Open to 5
- Resolution set to invalid
It seems that Hugin uses enblend, which had a bug which caused all JPEGs to be written using non-portable arithmetic coding. See
https://bugs.launchpad.net/enblend/+bug/798952
http://www.mail-archive.com/hugin-devs@lists.launchpad.net/msg02089.html
Looks like this has been fixed in enblend, so hopefully if you update to a newer version the problem will go away. In any case, it's now clear that this is not a Shotwell bug.
Comment 12
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Invalid
--- Bug imported by chaz@yorba.org 2013-11-25 21:55 UTC ---
This bug was previously known as bug 4296 at http://redmine.yorba.org/show_bug.cgi?id=4296 Imported an attachment (id=262262) Imported an attachment (id=262263)
Unknown Component Using default product and component set in Parameters Unknown version " in product shotwell. Setting version to "!unspecified". Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Resolution: RESOLVED INVALID