Hello
Reverting made darktable work again.
With respect,
Alexander Rabtchevich
this is darktable 1.7.0+1675~g9555d95 reporting a segfault:
#0 0x7fdde2c2bee9 in __libc_waitpid (pid=pid@entry=10572,
stat_loc=stat_loc@entry=0x0, options=options@entry=0) at
../sysdeps/unix/sysv/linux/waitpid
Le samedi 04 juillet 2015 à 11:32 +0300, Alexander Rabtchevich a écrit
:
> Hello
>
> Reverting made darktable work again.
Can you be more precise? Which commit? Which OS? Which CUPS version?
Thanks,
--
Pascal Obry / Magny Les Hameaux (78)
The best way to travel is by means of imaginatio
The code seems definitely broken, dt is crashing on startup:
https://gist.github.com/pedrocr/8be183e62563d0eec895
Pedro
On Sat, Jul 4, 2015 at 9:46 AM, Pascal Obry wrote:
> Le samedi 04 juillet 2015 à 11:32 +0300, Alexander Rabtchevich a écrit
> :
>> Hello
>>
>> Reverting made darktable work a
Le samedi 04 juillet 2015 à 10:03 +0100, Pedro Côrte-Real a écrit :
> The code seems definitely broken, dt is crashing on startup:
>
> https://gist.github.com/pedrocr/8be183e62563d0eec895
And if you revert 7dacd48e57ee590ccc7e466a693b0ba9791d65b7
$ git revert 7dacd48e57ee590ccc7e466a693b0ba9791d
Le samedi 04 juillet 2015 à 10:03 +0100, Pedro Côrte-Real a écrit :
> The code seems definitely broken, dt is crashing on startup:
>
> https://gist.github.com/pedrocr/8be183e62563d0eec895
Alternatively can you test with current master? I have pushed a
possible fix.
--
Pascal Obry / Magny Les
Pascal Obry wrote:
> Le samedi 04 juillet 2015 à 10:03 +0100, Pedro Côrte-Real a écrit :
>> The code seems definitely broken, dt is crashing on startup:
>>
>> https://gist.github.com/pedrocr/8be183e62563d0eec895
> Alternatively can you test with current master? I have pushed a
> possible fix.
>
You
Alexander,
> You've managed to fix it when I was trying to found the possible
> commit.
> :) Now it works.
Good to hear!
> P.S. Maybe it was 9555d95773af89fde7e7c0d6fa9fd2d9f8067190
Indeed, this correct commit from Roman did trigger a missing
initialization of some variables.
--
Pascal Ob
On Sat, Jul 4, 2015 at 1:09 PM, Pascal Obry wrote:
> Alexander,
>
> > You've managed to fix it when I was trying to found the possible
> > commit.
> > :) Now it works.
>
> Good to hear!
>
> > P.S. Maybe it was 9555d95773af89fde7e7c0d6fa9fd2d9f8067190
>
> Indeed, this correct commit from Roman did
Hello,
I tried to generate denoise profile for Pentax K-S1. At first, gen-profile
script ended silently in the phase of
===> Checking profiling RAW images correctness + Jpeg export
after first image. When started another time it went throuh two images, and
so on. After several restarts when it we
On Sat, Jul 4, 2015 at 11:49 PM, Piotr Ryszkiewicz
wrote:
> Hello,
>
> I tried to generate denoise profile for Pentax K-S1. At first, gen-profile
> script ended silently in the phase of
> ===> Checking profiling RAW images correctness + Jpeg export
> after first image. When started another time
On Sat, Jul 4, 2015 at 10:57 PM, Roman Lebedev wrote:
> On Sat, Jul 4, 2015 at 11:49 PM, Piotr Ryszkiewicz
> wrote:
>
>> Hello,
>>
>>
> I tried to generate denoise profile for Pentax K-S1. At first, gen-profile
>> script ended silently in the phase of
>> ===> Checking profiling RAW images corre
On Sun, Jul 5, 2015 at 12:02 AM, Piotr Ryszkiewicz
wrote:
> On Sat, Jul 4, 2015 at 10:57 PM, Roman Lebedev
> wrote:
>
>> On Sat, Jul 4, 2015 at 11:49 PM, Piotr Ryszkiewicz
>> wrote:
>>
>>> Hello,
>>>
>>>
>> I tried to generate denoise profile for Pentax K-S1. At first,
>>> gen-profile script en
12 matches
Mail list logo
