Created attachment 1297894 [details] Stack trace of crash Description of problem: $ darktable X server found. dri2 connection failed! X server found. dri2 connection failed! X server found. dri2 connection failed! X server found. dri2 connection failed! X server found. dri2 connection failed! X server found. dri2 connection failed! darktable: /usr/include/llvm/Support/Casting.h:236: typename llvm::cast_retty<X, Y*>::ret_type llvm::cast(Y*) [with X = llvm::CompositeType; Y = llvm::Type; typename llvm::cast_retty<X, Y*>::ret_type = llvm::CompositeType*]: Assertion `isa<X>(Val) && "cast<Ty>() argument of incompatible type!"' failed. Aborted (core dumped) Passing the --disable-opencl argument on the CLI allows it to start, but this is not a good user experiance for people. I'm using defualt GNOME on Wayland desktop, The cltest program similarly crashes $ darktable-cltest [opencl_init] opencl related configuration options: [opencl_init] [opencl_init] opencl: 1 [opencl_init] opencl_library: '' [opencl_init] opencl_memory_requirement: 768 [opencl_init] opencl_memory_headroom: 300 [opencl_init] opencl_device_priority: '*/!0,*/*/*' [opencl_init] opencl_size_roundup: 16 [opencl_init] opencl_async_pixelpipe: 0 [opencl_init] opencl_synch_cache: 0 [opencl_init] opencl_number_event_handles: 25 [opencl_init] opencl_micro_nap: 1000 [opencl_init] opencl_use_pinned_memory: 0 [opencl_init] opencl_use_cpu_devices: 0 [opencl_init] opencl_avoid_atomics: 0 [opencl_init] opencl_enable_markesteijn: 1 [opencl_init] [opencl_init] could not find opencl runtime library 'libOpenCL' [opencl_init] could not find opencl runtime library 'libOpenCL.so' [opencl_init] found opencl runtime library 'libOpenCL.so.1' [opencl_init] opencl library 'libOpenCL.so.1' found on your system and loaded X server found. dri2 connection failed! X server found. dri2 connection failed! X server found. dri2 connection failed! X server found. dri2 connection failed! X server found. dri2 connection failed! X server found. dri2 connection failed! darktable-cltest: /usr/include/llvm/Support/Casting.h:236: typename llvm::cast_retty<X, Y*>::ret_type llvm::cast(Y*) [with X = llvm::CompositeType; Y = llvm::Type; typename llvm::cast_retty<X, Y*>::ret_type = llvm::CompositeType*]: Assertion `isa<X>(Val) && "cast<Ty>() argument of incompatible type!"' failed. Aborted (core dumped) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Sorry, hit submit too soon - version is darktable-2.2.5-2.fc26.x86_64. Previously on Fedora 25 it worked fine.
*** This bug has been marked as a duplicate of bug 1468392 ***
Re-opening because expecting people to just uninstall beignet is not disoverable. Darktable RPM should add a conflicts beignet if its incompatible with it..
(In reply to Daniel Berrange from comment #3) > Re-opening because expecting people to just uninstall beignet is not > disoverable. Darktable RPM should add a conflicts beignet if its > incompatible with it.. darktable is not incompatible with it, it is beignet that is poorly developed and tested. I am trying to figure out why it is shipped by default on Fedora ISOs https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/PZSRYVKOW4JA675S5ZQY7EU3C4WLHPDI/ Anyway, I am considering to add Conflicts: beignet into darktable spec file
I'm remarking this as a dup of the beignet bug, since a beignet update was just issued that solves this problem satisfactorily for me. *** This bug has been marked as a duplicate of bug 1468392 ***
(In reply to Daniel Berrange from comment #5) > I'm remarking this as a dup of the beignet bug, since a beignet update was > just issued that solves this problem satisfactorily for me. > > *** This bug has been marked as a duplicate of bug 1468392 *** Yes, after a discussion in #fedora-devel, a new beignet update has been submitted to let it work with llvm update https://bodhi.fedoraproject.org/updates/FEDORA-2017-3aa9e1fe13 So, definitely not a darktable problem