Description of problem: M6 can't open any of my work files - all grey-scale jpeg. Checking for my return to work in the morning. Cannot open any of my 15,000 work jpeg files. Error is 'unsupported number of color components'. This is critical. From the archlinux reference above, it seems they forgot to allow for greyscale images. According to the quoted web reference, downgrading the package to gdk-pixbuf2 version 2.36.6.2 'fixed' the problem. Version-Release number of selected component (if applicable): 2.36.7 How reproducible: applies to all the jpeg viewers I tried Steps to Reproduce: 1. 2. 3.
and later in that archlinux thread, I see gdk-pixbuf2-2.36.8.1 (by their numbering) is the fixed and available version
Indeed the fix for this is in the news file for 2.36.8 upstream. There is also a 2.36.9 bugfix version: https://download.gnome.org/sources/gdk-pixbuf/2.36/gdk-pixbuf-2.36.8.news https://download.gnome.org/sources/gdk-pixbuf/2.36/gdk-pixbuf-2.36.9.news 2.36.9 is committed in SVN for Cauldron but not built. I'm guessing there's a build problem with it. We'll need to fix that so that we can also build it for Mageia 6.
Assignee: bugsquad => olavSource RPM: gdk-pixbuf2.0 version 2.36.7 => gdk-pixbuf2.0-2.36.7-1.mga6.src.rpm
2.36.10 is out now, and actually built in Cauldron, so we can update this: https://download.gnome.org/sources/gdk-pixbuf/2.36/gdk-pixbuf-2.36.10.news
CC: (none) => luigiwalser
Timeline for distributing this in M6?
Advisory: ---------------------------------------- The gdk-pixbuf2.0 package has been upgraded to version 2.36.10, fixing display of grayscale images, as well other issues. See the upstream news files for details. References: https://download.gnome.org/sources/gdk-pixbuf/2.36/gdk-pixbuf-2.36.8.news https://download.gnome.org/sources/gdk-pixbuf/2.36/gdk-pixbuf-2.36.9.news https://download.gnome.org/sources/gdk-pixbuf/2.36/gdk-pixbuf-2.36.10.news ---------------------------------------- Updated packages in core/updates_testing: ---------------------------------------- gdk-pixbuf2.0-2.36.10-1.mga6 libgdk_pixbuf2.0_0-2.36.10-1.mga6 libgdk_pixbuf2.0-devel-2.36.10-1.mga6 libgdk_pixbuf-gir2.0-2.36.10-1.mga6 from gdk-pixbuf2.0-2.36.10-1.mga6.src.rpm
Assignee: olav => qa-bugs
Thanks David. For the moment, pkgs not actually made it there yet? I'm still only seeing 2.36.7 with updates-testing enabled. Mirror issue? I'll try again later. Much obliged, Tony
MGA6-32 on Asus A6000VM MATE No installation issues. Used at CLI $ convert slide001.jpg -colorspace Gray grayslide1.jpg to create a grayscale image. Before update could not open it in ristretto with error 'unsupported number of color components' after update opens perfectly.
CC: (none) => herman.viaeneWhiteboard: (none) => MGA6-32-OK
Testing M6/64 Thank you Herman for this neat way of creating a greyscale image. (I was going to use Gimp). It seems to keep the colour version somehow. Under LXDE: BEFORE update: gdk-pixbuf2.0-2.36.7-1.mga6 lib64gdk_pixbuf2.0_0-2.36.7-1.mga6 lib64gdk_pixbuf-gir2.0-2.36.7-1.mga6 With Shotwell, it displayed briefly the colour original, then the gresycale. With Gwenview & Okular, it displayed correctly the greyscale image. With Ristretto and Image viewer = gpicview it showed the "Unsupported number of color components (1)" message. AFTER update: - gdk-pixbuf2.0-2.36.10-1.mga6.x86_64 - lib64gdk_pixbuf-gir2.0-2.36.10-1.mga6.x86_64 - lib64gdk_pixbuf2.0_0-2.36.10-1.mga6.x86_64 With Ristretto & Gpicview the greyscale image was correctly displayed. OK. Validating.
Whiteboard: MGA6-32-OK => MGA6-32-OK MGA6-64-OKKeywords: (none) => advisory, validated_updateCC: (none) => lewyssmith, sysadmin-bugs
red-face: what am I doing wrong? IN M6 with updates-testing enabled, I'm not seeing the recent packages. They are in M6 updates-testing, not just in cauldron??
I never used cauldron before. I'm on the Belgian mirror, and that one usually takes a day to synchronize.
Yes they are in Mageia 6 updates_testing. Enabling that through our GUI tools usually isn't enough to see the packages there because it doesn't let you enable it as an updates repository. You have to edit /etc/urpmi/urpmi.cfg manually and add an update line to that media.
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2017-0088.html
Status: NEW => RESOLVEDResolution: (none) => FIXED