Pascal Obry wrote:
> No problem, you are not the first one... and probably not the last
> one.
hihi.. +1, long time ago
> It would be nice to know which "old" module is there and
> breaking dt. Probably an old IOP still in gtk2 or something like that.
>
> Next time we'll try to check that by
Le mardi 20 janvier 2015 à 21:47 +0100, Bertwim a écrit :
> Ooof. It was indeed precisely that!
> Thanks for the tip.
No problem, you are not the first one... and probably not the last one.
It would be nice to know which "old" module is there and breaking dt.
Probably an old IOP still in gtk2 or
Ooof. It was indeed precisely that!
Thanks for the tip.
Regards,
Bertwim
On 01/20/2015 09:35 PM, Pascal Obry wrote:
> Le mardi 20 janvier 2015 à 21:06 +0100, Bertwim a écrit :
>> My darktable executable invariably gets into a deadlock situation when I
>> start it.
>>
>> The executable is built
Le mardi 20 janvier 2015 à 21:06 +0100, Bertwim a écrit :
> My darktable executable invariably gets into a deadlock situation when I
> start it.
>
> The executable is built directly from the git repository. No
> modifications made.
> (any recent version from the current head in the repository exh
My darktable executable invariably gets into a deadlock situation when I
start it.
The executable is built directly from the git repository. No
modifications made.
(any recent version from the current head in the repository exhibits the
problem).
the problem seems to be in the function ( .../cont
