Fedora has issued an advisory on January 14: https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/thread/XRPXTW3IARYQVKZBPIPIEKABN7DSS5XY/ The issue is fixed upstream in 1.5.1. Mageia 8 is also affected.
Whiteboard: (none) => MGA8TOOStatus comment: (none) => Fixed upstream in 1.5.1
Done for both Cauldron and mga8!
CC: (none) => geiger.david68210
jpegoptim-1.5.1-1.mga8 from jpegoptim-1.5.1-1.mga8.src.rpm
Version: Cauldron => 8Assignee: bugsquad => qa-bugsStatus comment: Fixed upstream in 1.5.1 => (none)Whiteboard: MGA8TOO => (none)
MGA8-64 MATE on Acer Aspire 5253 No installation issues No wiki, no previous updates, found https://www.mankier.com/1/jpegoptim and tried command $ jpegoptim -d testjpegopt/ -v -m 100 D053.jpg D078.jpg flipped.jpg withcomment.jpg work1.jpg work2.jpg work3.jpg work4.jpg Image quality limit set to: 100 D053.jpg 1656x988 24bit N JFIF [OK] (retry w/lossless) 125813 --> 116929 bytes (7.06%), optimized. D078.jpg 903x988 24bit N Exif JFIF [OK] (retry w/lossless) 99741 --> 87785 bytes (11.99%), optimized. flipped.jpg 903x988 24bit N JFIF [OK] (retry w/lossless) 99759 --> 87824 bytes (11.96%), optimized. withcomment.jpg 1656x988 24bit N JFIF [OK] (retry w/lossless) 125827 --> 116943 bytes (7.06%), optimized. work1.jpg 988x1656 24bit N JFIF [OK] (retry w/lossless) 124326 --> 115552 bytes (7.06%), optimized. work2.jpg 988x1656 24bit N JFIF [OK] (retry w/lossless) 124367 --> 115563 bytes (7.08%), optimized. work3.jpg 1656x988 24bit N JFIF [OK] (retry w/lossless) 125857 --> 117003 bytes (7.03%), optimized. work4.jpg 812x648 24bit N JFIF [OK] (retry w/lossless) 47818 --> 44914 bytes (6.07%), optimized. And indeed, size was reduced and at the same time in plain view and zoomed in, the resulting pictures seem somewhat crispier in details. Fine with me.
CC: (none) => herman.viaeneWhiteboard: (none) => MGA8-64-OK
Validating.
Keywords: (none) => validated_updateCC: (none) => andrewsfarm, sysadmin-bugs
CC: (none) => davidwhodginsKeywords: (none) => advisory
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGASA-2023-0023.html
Status: NEW => RESOLVEDResolution: (none) => FIXED