Hello. I originally filed this bug against eog in Fedora (https://bugzilla.redhat.com/show_bug.cgi?id=846824), and subsequently in Gnome's bugzilla (https://bugzilla.gnome.org/show_bug.cgi?id=682601) where I was told the problem was with libopenraw. Essentially, eog is unable to read my .nef files using the pixbuf backend. This gets printed to the console: (eog:17042): GdkPixbuf-CRITICAL **: gdk_pixbuf_loader_prepare: assertion `pixbuf != NULL' failed (eog:17042): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `GDK_IS_PIXBUF (pixbuf)' failed (eog:17042): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `GDK_IS_PIXBUF (pixbuf)' failed (eog:17042): GdkPixbuf-CRITICAL **: gdk_pixbuf_animation_get_height: assertion `GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:17042): GdkPixbuf-CRITICAL **: gdk_pixbuf_animation_get_width: assertion `GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:17042): GdkPixbuf-CRITICAL **: gdk_pixbuf_animation_is_static_image: assertion `GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:17042): GdkPixbuf-CRITICAL **: gdk_pixbuf_animation_get_iter: assertion `GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:17042): GdkPixbuf-CRITICAL **: gdk_pixbuf_animation_iter_get_pixbuf: assertion `GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed Version-Release number of selected component (if applicable): eog-3.4.3-2.fc17.x86_64 libopenraw-pixbuf-loader-0.0.8-7.fc17.x86_64
I tried attaching a sample nef file but the attachment was too large. You can get the file in the Fedora bugzilla at https://bugzilla.redhat.com/attachment.cgi?id=603275
Which model of Nikon camera.
After this, we get hit by bug 52258.
Fixed in revision 3a87e62ec63b6b4871d138914c62805d4882fc2a But then we hit bug 52258.
The crash is definitely not the same as bug 52258.
This is a 14 bits lossy
(In reply to Hubert Figuiere from comment #6) > This is a 14 bits lossy it is not, but I do have a fix.
Fixed in 8067dba3a031b5d19e1bd3f6503572be58887af4
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.