Original Fedora bugreport against Darktable package
(In reply to August Schwerdfeger from comment #0)
> Description of problem:
> Since updating to Darktable 1.6, I have been able to launch it only by
> providing the command-line parameter '--disable-opencl'. Attempting to
> launch it normally (e.g., by clicking its icon in the "Applications" menu)
> results in the process aborting unexpectedly, with the following output to
> the terminal:
> DRM_IOCTL_I915_GEM_APERTURE failed: No such file or directory
> Assuming 131072kB available aperture size.
> May lead to reduced performance or incorrect rendering.
> get chip id failed: -1 
> param: 4, val: 0
> intel_driver_memman_init: Assertion `driver->bufmgr' failed.
> ABRT associates this crash report with the failure:
(In reply to Germano Massullo from comment #1)
> Intel driver bug. Reassigning it...
> **Answer from Darktable's OpenCL specialist Ulrich Pegelow:**
> 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 suggested in the manual.
> Does the driver need to be shipped with debugging enabled? With debugging
> disabled at least the assert statement will not cause the driver to
This bug has been fixed in the master branch. Could you help to try it in your system?
(In reply to Zhigang Gong from comment #1)
> This bug has been fixed in the master branch. Could you help to try it in
> your system?
Yes, I just alerted the Fedora bugreporter