Bug 28741 - Darktable: various problems, recognised upstream. A newer corrected version is available, 3.4.1; please update.
Summary: Darktable: various problems, recognised upstream. A newer corrected version i...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA8-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2021-04-07 06:00 CEST by Thierry Houx
Modified: 2021-05-07 07:36 CEST (History)
6 users (show)

See Also:
Source RPM: darktable-3.4.0-1.mga8.src.rpm
CVE:
Status comment:


Attachments

Description Thierry Houx 2021-04-07 06:00:35 CEST
Description of problem:
When applying the module "basic adjustment", after clicking on "auto", the picture of the photo becomes black. You must then return to the light table and then return to the darkroom.
There are also other problems frequently encountered by others, I quote this one because it is the one that disturbs me the most.

Those problems have bee identified by darktable team who produces a corrected version 3.4.1

Version-Release number of selected component (if applicable):
darktable-3.4.0-1.mga8

How reproducible:
With some RAW files produced by Lumix GX9 in my case.
Not specific to my camera.

Steps to Reproduce:
As described above
1.
2.
3.
Comment 1 Lewis Smith 2021-04-07 21:52:29 CEST
Thank you for the report & upstream pointer.

Assigning to Rémi for this SRPM. Cauldron already has 3.4.1.1 (thanks to dlucio, unsure whether we can assign to him).

Assignee: bugsquad => rverschelde
Summary: When using some modules as "base adjustment", frequently whe obtains a black image in photo viewing => Darktable: various problems, recognised upstream. A newer corrected version is available, 3.4.1; please update.

Morgan Leijström 2021-04-07 22:17:29 CEST

CC: (none) => fri

Comment 2 Rémi Verschelde 2021-05-04 16:26:38 CEST
Advisory:
=========

Updated darktable package provides maintenance release

  This update provides darktable 3.4.1, maintenance release in the 3.4 branch,
  fixing various bugs in that branch. See the referenced release notes for
  details.

References:

 - https://github.com/darktable-org/darktable/releases/tag/release-3.4.1

SRPM in core/updates_testing:
=============================

darktable-3.4.1-1.mga8

RPM in core/updates_testing:
============================

darktable-3.4.1-1.mga8

Assignee: rverschelde => qa-bugs
CC: (none) => rverschelde

Comment 3 Thomas Andrews 2021-05-05 21:31:48 CEST
I was unable to reproduce the fault described in Comment 0, possibly because of inexperience with the software.

No installation issues on the update.

I'm definitely not an expert with this software, and it would take an expert to fully evaluate all of its functions. However, I did load a few photos into it, and played with this and that, not seeing anything that looked like it wasn't working.

OKing and Validating. Advisory in Comment 2.

Keywords: (none) => validated_update
CC: (none) => andrewsfarm, sysadmin-bugs
Whiteboard: (none) => MGA8-64-OK

Comment 4 Jose Manuel López 2021-05-05 21:51:01 CEST
Hi all, I have updated the new version, works ok, I have applied unsharp masks, contrast equalizer, basic adjustments, levels, tones, and various other modules without any problem.

I have exported the raw file to both jpg and png without errors. I think it is ready to validate.

Greetings!

CC: (none) => joselp

Comment 5 Thierry Houx 2021-05-06 05:47:34 CEST
I have tested this release, about 50 RAW done and works well.
I think this release can be considered like validated.
Thanks for this work.
Aurelien Oudelet 2021-05-06 20:11:06 CEST

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

Comment 6 Mageia Robot 2021-05-07 07:36:56 CEST
An update for this issue has been pushed to the Mageia Updates repository.

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

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.