s/1.6.6/1.6.7/ (though the issue also affects 1.6.7, but this package was never pushed to the updates).

Source RPM: darktable-1.6.7-1.mga5 => darktable-1.6.6-1.mga5

Update candidate pushed to Core Updates Testing.


Advisory:
=========

Updated darktable package fixes non-working export function

  The file export function in Darktable could refuse to work in some cases
  due to a wrong permission check in the temporary export directory.

  This issue has been fixed in Darktable 1.6.8, together with other bug fixes
  and enhanced camera compatibility since version 1.6.6.

References:
 - http://redmine.darktable.org/issues/10440
 - http://www.darktable.org/2015/06/released-darktable-1-6-7/
 - http://www.darktable.org/2015/07/released-darktable-1-6-8/


RPMS:
=====
darktable-1.6.8-1.mga5

from SRPM:
darktable-1.6.8-1.mga5.src.rpm

Mageia 5 updated to this date. Darktable installed is 1.6.6.
This version was tested by importing a jpg, making a change, then exporting via the export dialogue to a different disk location. This worked normally and the exported jpg was found in the new location.
I also tried saving a copy to disk through that dialogue, also in lighttable tab and that also worked.
I was therefore unable to reproduce the bug.
The first reference in Comment 0 involved a nef file.
The second reference  (10440) talks about a database corruption, that when cleared, resolved the problem. As I was not able to replicate either of these test cases, I was unable to duplicate the problem.
I will test with 1.6.8 and confirm.

CC: (none) => vzawalin1

Trying MGA5 x64

Installed darktable-1.6.6-1.mga5. Downloaded a RAW image file (I suspect this is what is meant in Comment 0, rather than RAM) and opened it in Darktable. You certainly need its manual!
 http://www.darktable.org/usermanual/index.html.php
I exported it: it defaults to JPEG and puts the result in a sub-directory:
 darktable_exported/
of the original image directory. Like Vladimir Comment 3, it worked without the reported error. FWIW the original RAW file was 86Mb, even the exported JPEG was 14Mb.
We really need the feedback from the reporter to properly test this update:
 http://www.mageialinux-online.org/forum/topic-20833+probleme-d-export-avec-darktable.php

CC: (none) => lewyssmith

The initial reported tested the update candidate and it did not seem to fix his issue, however regenerating the darktable config in ~/.config/darktable fixed it.

I propose to handle this update as a simple update to upstream's latest bugfix version in the 1.6.x branch, without mentioning this particular bug that I was trying to solve.

I'll write an updated advisory soon.

URL: http://redmine.darktable.org/issues/10440 => (none)
Summary: darktable: Export is broken err [imageio_storage_disk] could not export to file: `path\to\exported\file' => darktable bugfix update to 1.6.8

Agree with Comment 5: that this should simply be pushed as an update to version 1.6.8.

Testing Mageia 5 x64 OK

The original complainant found that the update did *not* change his export failure problem; but that it *was* cured by re-initialising the Darktable config file (suggesting it came from there in the first place). He confirmed that the updated Darktable works OK. As do I after updating it to:
 darktable-1.6.8-1.mga5
and wrestling with same (need a box with much more horsepower).

Whiteboard: (none) => MGA5-64-OK

Validating. Advisory uploaded.

Please push to 5 updates

Thanks

Keywords: (none) => validated_update
Whiteboard: MGA5-64-OK => has_procedure advisory MGA5-64-OK
CC: (none) => sysadmin-bugs

An update for this issue has been pushed to Mageia Updates repository.

http://advisories.mageia.org/MGAA-2015-0120.html

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