After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 791971 - Error "Unsupported marker type" when loading JPG files from some cameras
Error "Unsupported marker type" when loading JPG files from some cameras
Status: RESOLVED OBSOLETE
Product: gdk-pixbuf
Classification: Platform
Component: loaders
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gdk-pixbuf-maint
gdk-pixbuf-maint
Depends on:
Blocks:
 
 
Reported: 2017-12-27 02:22 UTC by Mario Sánchez Prada
Modified: 2018-05-22 13:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mario Sánchez Prada 2017-12-27 02:22:17 UTC
As reported originally in 768639, certain types of files (such as [1], reported as a bug for Vimiv [2]) fail to load when using GdkPixbufLoader, resulting in errors such as the following ones:

```
Error interpreting JPEG image file (Unsupported marker type 0xb9)
Error interpreting JPEG image file (Unsupported marker type 0x3e)
Error interpreting JPEG image file (Unsupported marker type 0x1a)
```

As reported in [3] and [4], it's interesting to note that the very same files load fine when using gdk_pixbuf_new_from_file() instead of the GdkPixbufLoader, even though if both code paths end up using the JPEG IO module from gdk-pixbuf.

I've spent some time today debugging this and this looks like a problem in gdk-pixbuf since the problem happens when using gdk_pixbuf_loader_write(), which relies on the internal gdk_pixbuf__jpeg_image_load_increment() function to load the data... well... incrementally. However, the problem doesn't happen when using gdk_pixbuf_new_from_file(), which relies on the internal gdk_pixbuf__jpeg_image_load() function instead (which is much simpler).

If you check bug 768639 you'll see this bug has been reported a while ago already, and initially I thought this might be a problem in the underlying jpeg library, but the more recent comments/experiments point to gdk-pixbuf, so I'm reporting this since I couldn't figure it out by myself yet, in case someone else can help.

FWIW, this seems to be an increasingly annoying problem since, even though originally I could not reproduce it at all, I can now reproduce it very easily with pictures taken with my wife's Moto G3 and my own OnePlus 5 phones, and who knows what else.

[1] https://user-images.githubusercontent.com/7871070/28070025-26867f24-667e-11e7-9ae7-a80290b0c0ff.jpg
[2] https://github.com/karlch/vimiv/issues/49
[3] https://github.com/karlch/vimiv/issues/49#issuecomment-314569184
[4] https://bugzilla.gnome.org/show_bug.cgi?id=768639#c9
Comment 1 GNOME Infrastructure Team 2018-05-22 13:24:54 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gdk-pixbuf/issues/70.