Il 04/03/2015 12:15, Ulrich Pegelow ha scritto:
> Obviously the driver is not only nonfunctional for the hardware but
> contains a bug which triggers a SIGABRT. Nothing we can do here as
> long as this doesn't get fixed in the driver code. Only option is to
> run darktable with --disable-opencl as
Am 04.03.2015 um 11:49 schrieb Germano Massullo:
> Ulrich, ping :-)
>
Obviously the driver is not only nonfunctional for the hardware but
contains a bug which triggers a SIGABRT. Nothing we can do here as long
as this doesn't get fixed in the driver code. Only option is to run
darktable with --
Ulrich, ping :-)
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from w
Am Montag, 23. Februar 2015, 18:55:54 schrieb Germano Massullo:
> Hi,
> I am taking care of Fedora's bugreport
> https://bugzilla.redhat.com/show_bug.cgi?id=1195367
> I looked for some suggestions in Darktable IRC channel and LebedevRI said
> it could be an Intel driver bug.
> Before filling a bugr
Hi,
I am taking care of Fedora's bugreport
https://bugzilla.redhat.com/show_bug.cgi?id=1195367
I looked for some suggestions in Darktable IRC channel and LebedevRI said
it could be an Intel driver bug.
Before filling a bugreport against Intel video drivers, I would like to ask
for your opinion. Wha
