Bug 29165 - gthumb 3.8.3
Summary: gthumb 3.8.3
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA7-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2021-06-21 23:12 CEST by David Walser
Modified: 2021-06-28 23:18 CEST (History)
4 users (show)

See Also:
Source RPM: gthumb-3.7.2-2.1.mga7.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description David Walser 2021-06-21 23:12:23 CEST 
Advisory:
----------------------------------------

The gthumb package has been updated to version 3.8.3, fixing several bugs.

See the upstream NEWS file for details.

References:
https://gitlab.gnome.org/GNOME/gthumb/-/blob/gthumb-3-8/NEWS
----------------------------------------

Updated packages in core/updates_testing:
----------------------------------------
gthumb-3.8.3-1.mga7
gthumb-devel-3.8.3-1.mga7

from gthumb-3.8.3-1.mga7.src.rpm
Comment 1 David Walser 2021-06-21 23:12:56 CEST 
See Bug 26084 to see where this came from.
Comment 2 Len Lawrence 2021-06-24 20:34:35 CEST 
mga7, x64
Quick look before updating showed that gthumb was working OK.
After updates perused a folder containing astronomical images.
Some of them contained extensive comments which showed up in the EXIF data column.  RGB histograms displayed OK, rotations and image panning at full size worked OK.

Whiteboard: (none) => MGA7-64-OK
CC: (none) => tarazed25

Comment 3 Thomas Andrews 2021-06-27 02:55:33 CEST 
Validating. Advisory in Comment 0.

CC: (none) => andrewsfarm, sysadmin-bugs
Keywords: (none) => validated_update

Aurelien Oudelet 2021-06-28 21:18:51 CEST

CC: (none) => ouaurelien
Keywords: (none) => advisory

Comment 4 Mageia Robot 2021-06-28 23:18:12 CEST 
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2021-0139.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.