Bug 1195367 - Darktable 1.6 will not launch unless OpenCL is disabled.
Summary: Darktable 1.6 will not launch unless OpenCL is disabled.
Alias: None
Product: Fedora
Classification: Fedora
Component: beignet
Version: 21
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Igor Gnatenko
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2015-02-23 16:25 UTC by August Schwerdfeger
Modified: 2015-12-02 17:30 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-12-02 09:22:22 UTC
Type: Bug

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
FreeDesktop.org 89424 0 None None None Never

Description August Schwerdfeger 2015-02-23 16:25:31 UTC
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 [22]
  param: 4, val: 0
  darktable: /builddir/build/BUILD/Beignet-1.0.1-Source/src/intel/intel_driver.c:131: intel_driver_memman_init: Assertion `driver->bufmgr' failed.

ABRT associates this crash report with the failure:


Comment 1 Germano Massullo 2015-03-04 14:02:15 UTC
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 terminate.


Comment 2 Germano Massullo 2015-03-05 08:06:45 UTC
August, upstream mantainer is asking for your help in testing the patch

Comment 3 August Schwerdfeger 2015-03-05 16:21:11 UTC
(In reply to Germano Massullo from comment #2)
> August, upstream mantainer is asking for your help in testing the patch
> https://bugs.freedesktop.org/show_bug.cgi?id=89424#c1

Compiling a version of Beignet from their Git repository for testing appears to be a task taking more time than I have available.

Comment 4 Fedora End Of Life 2015-11-04 15:39:29 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2015-12-02 09:22:25 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.