GNOME Bugzilla – Bug 678241
Selected pictures won't load into the main window
Last modified: 2017-12-26 20:29:08 UTC
I've been using Frogr for more than a year and didn't have any problems until I changed my camera. Pictures from my Canon Powershot X10 IS loaded without any problem, but the ones from my Fujifilm Finepix X-S1 don't. I select the pictures I want to load as usual, but when I click on the Open button on the "Select a picture" window nothing happens, it just returns to the main window where it doesn't appear any photo. I'm running Ubuntu 12.04. You can find a sample picture attached. Thanks is advance
Thanks for the bug report, I'll try to take a look to it as soon as possible. In the meanwhile, would you mind attaching a sample picture? As per your description it seems you already meant to do it, but simply forgot it :)
I'm sorry, I didn't noticed that the file upload went wrong as it exceeds the maximum size for an attachment. You can find it on this URL: http://www.flickr.com/photos/albtotxo/7385161970/in/photostream Full size download is enabled, so you can get the exact same file that I try to load into frogr.
No problem. It happens all the time to me with mails and attachments. Thanks for providing the link!
I've just started looking at this now (sorry for the delay) and realized of the following warnings/errors being printed in the console when I try to load your picture in frogr: ** (frogr:21087): WARNING **: Not able to read pixbuf: Error interpreting JPEG image file (JPEG datastream contains no image) ** (frogr:21087): CRITICAL **: _on_file_loaded: assertion `FROGR_IS_PICTURE (picture)' failed Something is definitely wrong in there, not it's time to figure out what... I'll work on this now.
It seems there might be an issue on how JPEG files are generated with your camera, since googling a bit this seems to be an issue that happens to more people out there in Linux, with different applications. In [1] they suggest that "aparently, conecting the camera directly to ubuntu (via usb cable) instead of removing the memory card and mounting it solves the problem", so perhaps you could give that a try, at least to understand whether you're spotting or not the same problem. [1] http://ubuntuforums.org/showthread.php?t=1629272
I'll try what you say and give you my feedback as soon as possible. Anyway, there must be a way to read the images copied from the memory card, because I don't have this problem with the rest of the applications I use to see and process them (GIMP, XnViewMP and the online version of Flickr Uploadr). Thanks for your time
I've tried what we agreed, but I'm afraid that results were not what we expected. I've taken a photo and then connected the camera to my PC through a USB cable. Then I opened Frogr and tried to add the photo directly from the SD card, with the same results as with the other pictures. Then I copied the image to a folder in my HD and repeated the process, but results didn't change. The error in the console was the same you said: ** (frogr:6175): WARNING **: Not able to write pixbuf: Error interpreting JPEG image file (JPEG datastream contains no image) What can we try next?
Hi, first of all sorry for the delay, I've been a little bit disconnected these days from Bugzilla... Thanks for taking your time to do those experiments and for checking that other apps do well with those pictures. Based on that, I've been doing some experiments too with a different app, EOG in my case, and after checking the code I've realized they are using an slightly modified and more complex method to load images than what I'm doing for frogr (I'm just using GdkPixbufLoader), even if they took some code from the gdk-pixbuf project itself, and that extra bits are the ones that are making a difference. In my case, just using the GdkPixbufLoader API and nothing else is always leading to the GDK_PIXBUF_ERROR_CORRUPT_IMAGE error for your pictures, not sure whether it's because those pictures are actually badly formed or because there's a bug in the gdk-pixbuf library. I'm adding Claudio Saavedra (EOG's developer) to CC to see whether he could help us find out what it's really going on here and, hopefully, whether he has any valuable piece of advice to know how we could fix this in a proper way in frogr.
I think this is a duplicate of bug 768639, which has been fixed in master and will be available from the 1.4 release on. So, resolving as DUPLICATE. Please reopen if you continue to see the issue in future releases. *** This bug has been marked as a duplicate of bug 768639 ***