Description of problem: Starting after a very recent update, GIF are no more not displayed in nautilus, eye of gnome and probably more Version-Release number of selected component (if applicable): How reproducible: systematic Steps to Reproduce: 1. start the file manager or the default image viewer : message "unrecognozed image file format" Hint : /usr/bin/gdk-pixbuf-query-loaders | grep -i gif g_module_open() failed for /usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-gif.so: /usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-gif.so: undefined symbol: g_uint64_checked_mul
Assignee: bugsquad => gnomeCC: (none) => marja11
Advisory: ---------------------------------------- The previous update for gdk-pixbuf2.0 introduced an undefined symbol error in the GIF loader. This error has been corrected. References: https://advisories.mageia.org/MGASA-2018-0090.html ---------------------------------------- Updated packages in core/updates_testing: ---------------------------------------- gdk-pixbuf2.0-2.32.3-1.3.mga5 libgdk_pixbuf2.0_0-2.32.3-1.3.mga5 libgdk_pixbuf2.0-devel-2.32.3-1.3.mga5 libgdk_pixbuf-gir2.0-2.32.3-1.3.mga5 from gdk-pixbuf2.0-2.32.3-1.3.mga5.src.rpm
Assignee: gnome => qa-bugsCC: (none) => luigiwalser
MGA5-32 on Dell Latitude D600 Xfce Hm, all are not the same. Created a gif file from a tif file with GIMP. Started thunar from the desktop and tried to open the gif file. Default is ristretto, but this one opens just the next file in the Pictures folder. Opening ristretto directly at the CLI and trying File - Open does not allow to select the gif file. Right click on the file in thunar and selecting nomacs displays the gif file correctly. I will try to install the update anyway, it shouldn't break anything.
CC: (none) => herman.viaene
Testing M5/64 under XFCE BEFORE update: gdk-pixbuf2.0-2.32.3-1.2.mga5 lib64gdk_pixbuf2.0_0-2.32.3-1.2.mga5 lib64gdk_pixbuf2.0-devel-2.32.3-1.2.mga5 lib64gdk_pixbuf-gir2.0-2.32.3-1.2.mga5 Trying eog on a directory containing .gif files, they are *not* listed in the file selection panel. Trying Nautilus on the same directory crashed it! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! YOUR CODE IS RELYING ON DEPRECATED FUNCTIONALTIY IN THE JASPER LIBRARY. THIS FUNCTIONALITY WILL BE REMOVED IN THE NEAR FUTURE. PLEASE FIX THIS PROBLEM BEFORE YOUR CODE STOPS WORKING! The specific problem is as follows: negative buffer size for jas_stream_memopen Segmentation fault Thunar: *did* show .gif files in the directory. Not to repeat. Ristretto did *not* list .gif files in its open dialogue. UPDATE to: - gdk-pixbuf2.0-2.32.3-1.3.mga5.x86_64 - lib64gdk_pixbuf-gir2.0-2.32.3-1.3.mga5.x86_64 - lib64gdk_pixbuf2.0-devel-2.32.3-1.3.mga5.x86_64 - lib64gdk_pixbuf2.0_0-2.32.3-1.3.mga5.x86_64 Nautilus Still crashed on opening a directory with .gif files, but it *did* briefly list them before disappearing. It may have done that before the update. Fuller output (I truncated the pre-update): $ nautilus (nautilus:5460): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! YOUR CODE IS RELYING ON DEPRECATED FUNCTIONALTIY IN THE JASPER LIBRARY. THIS FUNCTIONALITY WILL BE REMOVED IN THE NEAR FUTURE. PLEASE FIX THIS PROBLEM BEFORE YOUR CODE STOPS WORKING! The specific problem is as follows: negative buffer size for jas_stream_memopen Segmentation fault I am asking for feedback about this. Another bug? eog: *did* now show .gif files in the open dialogue; and displayed all 3 correctly. Ristretto: *did* show the 3 .gif files in its open dialogue. Displaying them was unreliable for 2, but eventually settled down. The 3rd did not show at all. All 3 displayed OK with ImageMagick $ display but the 3rd one disappeared soon, so may have been animated. Perhaps 'feedback' could cover this aspect too, even if it is a different problem.
Keywords: (none) => feedbackCC: (none) => lewyssmith
This is showing up here as well. ImageMagick and GraphicsMagick work but eom, eog do not and GIFs do not appear in ristretto selection lists and gqview does not recognize the format. $ file partlysunny.gif partlysunny.gif: GIF image data, version 89a, 48 x 48 After updating eom and eog could display a set of GIF icons including an animation. OK in ristretto but not in gqview. Still OK with 'display' and 'gm display', There did not appear to be any problem with nautilus. The odd thing there was that nautilus has been configured to use gqview. GIF images display in its folder view and clicking on any one brings it up correctly in gqview (counter to gqview running on its own). If nautilus is run this way: $ nautilus . & [1] 8701 [lcl@vega images]$ (nautilus:8701): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! YOUR CODE IS RELYING ON DEPRECATED FUNCTIONALTIY IN THE JASPER LIBRARY. THIS FUNCTIONALITY WILL BE REMOVED IN THE NEAR FUTURE. PLEASE FIX THIS PROBLEM BEFORE YOUR CODE STOPS WORKING! The specific problem is as follows: negative buffer size for jas_stream_memopen [1]+ Segmentation fault nautilus . which is what Lewis saw. The same thing happens when navigating from the home directory under nautilus to a particular image directory. AFAICR, jasper has something to do with JPEG 2000 formats so I moved .jp2 and .jpc images into a temporary directory and tried again. nautilus functioned normally but navigating to the temporary directory brought on the crash. Using eom or eog on the images in the temporary directory allowed the individual images to be displayed but for each one the "DEPRECATED FUNCTIONALITY" message was issued (no crash). As Lewis notes, this could be another bug, in jasper support.
CC: (none) => tarazed25
Yes jasper is a different library, so that would be a different bug. gqview and imagemagick do not use gdk-pixbuf2.0, but nautilus, eog, eom, and ristretto do. So is this working now? Are there any regressions compared to the version *before* the last update we did?
Keywords: feedback => (none)
(In reply to David Walser from comment #5) > Yes jasper is a different library, so that would be a different bug. > gqview and imagemagick do not use gdk-pixbuf2.0, but nautilus, eog, eom, and > ristretto do. > So is this working now? Are there any regressions compared to the version > *before* the last update we did? This is the nub of the matter. Even though the end result is ropey, I do not think that there are any regressions. And we know that there is some improvement. So giving it OK, validating, will do the advisory. Len's discovery re JPEG2000 matters, because my Nautilus crashes were on a directory which contained some. That is what *that* bug is about. Do we raise one?
Keywords: (none) => advisory, validated_updateWhiteboard: (none) => MGA5-64-OKCC: (none) => sysadmin-bugs
Thanks, I'm glad this update fixes the reported issue. As for jasper, our last update for it was in April, and this is the first I'm hearing of it. I wonder if any of our updates early last year caused that issue as a regression, or if it was always like that. Jasper has had a lot of security issues and it was difficult trying to update and patch it to fix all of them. Nicolas Salguero did an amazing job with that. It almost seems kind of hopeless, especially on Mageia 5. I suppose if you could find a particular update that caused it as a regression, we could look into it, otherwise it's probably too late to worry about it.
@ David Walser, re comment 5. Thanks for the clarification re ImageMagick - should have done my homework. There were no obvious regressions that I could see. Agreeing with Lewis that this is ready for release. I shall have a quick look at jasper in Mageia 6 to see if anything crops up.
Sorry for the late reply, no Mageia 5 handy at home (using Mageia 6). The bug was found at work. I have installed the "testing" repo updates and everything is now fine. Thanks a lot !
Status: NEW => RESOLVEDResolution: (none) => FIXED
It's not fixed until we push the update.
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
Sorry, I'm not familiar with the process !
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2018-0025.html
Status: REOPENED => RESOLVEDResolution: (none) => FIXED