Page MenuHomeSolus

Darktable 2.6.2 2.6.1 & 2.6.0
Closed, InvalidPublic

Description

Hello

I find a bug in Darktable 2.6.2, 2.6.1 and 2.6.0 binary available in Solus repository.

The app is unable to fetch Google Photo/Drive folder list and complain about a picasa library failure :

  • (darktable:3803): CRITICAL **: 11:09:56.665: picasa_parse_response: assertion '(ret)' failed

I first opened a case @Darktable github and got this response :
https://github.com/darktable-org/darktable/issues/2256

Have to compile against an updated Google Photo library. No idea where and how to do it in Solus.

Gon0S created this task.Mar 23 2019, 10:21 AM
Herald removed kyrios123 as the assignee of this task. · View Herald TranscriptMar 23 2019, 10:21 AM
Herald added a subscriber: kyrios123.

I'm not sure what their reply means as in version 2.6.2 the library is still called picasa.c. It's true though, that in the master branch they renamed it to googlephoto.c.
Anyway, I managed to reproduce your error. Honestly I think we should wait for an updated Darktable version... or, maybe, we can dirty patch it by fetching the new file and rename it to picasa.c. Yeah it's ugly as hell.

Gon0S added a comment.Mar 24 2019, 6:01 PM

I will check with Darktable programers and look at the mismatch.

I am unable to get past 2.0.7 on my second rig (not running solus, but old ElementaryOS), so I cannot check if it is a residual file making bugs... I let you know after further investigation.

Thanks you very much for the insights so far.

Gon0S added a comment.Mar 24 2019, 7:26 PM

Just an early notification : the fix already exist but as you discovered it, only in the master branch and not in the released 2.6 branch. They will schedule the update for the already existing fix found into master branch.

We'll have to wait for 2.6.3 or 2.6.4... Thank you very much for your time already passed on this problem.

Jacalz added a subscriber: Jacalz.EditedMar 24 2019, 8:05 PM

We could probably backport the fix and patch the version we have, if it’s necessary.

In T7743#146579, @Gon0S wrote:

Just an early notification : the fix already exist but as you discovered it, only in the master branch and not in the released 2.6 branch. They will schedule the update for the already existing fix found into master branch.

We'll have to wait for 2.6.3 or 2.6.4... Thank you very much for your time already passed on this problem.

You're welcome!

JoshStrobl closed this task as Invalid.Mar 26 2019, 4:20 PM
JoshStrobl edited projects, added Upstream Issue; removed Lacks Project.