Bug 1504976

Summary: LibreOffice crashes at startup
Product: [Fedora] Fedora Reporter: Heiko Adams <bugzilla>
Component: libreofficeAssignee: Caolan McNamara <caolanm>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 27CC: caolanm, dtardon, erack, mstahl, sbergman
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-10-21 06:12:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Heiko Adams 2017-10-20 21:26:32 UTC 
Description of problem:
Libreoffice crashes at startup. When running from terminal the following output is shown:
$  libreoffice writer
X server found. dri2 connection failed! 
X server found. dri2 connection failed! 
cl_get_gt_device(): error, unknown device: 46
X server found. dri2 connection failed! 
X server found. dri2 connection failed! 
cl_get_gt_device(): error, unknown device: 46
X server found. dri2 connection failed! 
cl_get_gt_device(): error, unknown device: 46
X server found. dri2 connection failed! 
cl_get_gt_device(): error, unknown device: 46
X server found. dri2 connection failed! 
cl_get_gt_device(): error, unknown device: 46
sh: /usr/bin/clang++: Datei oder Verzeichnis nicht gefunden
soffice.bin: /builddir/build/BUILD/pocl-0.14/lib/CL/devices/common.c:127: llvm_codegen: Zusicherung »error == 0« nicht erfüllt.

Version-Release number of selected component (if applicable):
$  rpm -q libreoffice
libreoffice-5.4.2.2-2.fc27.x86_64

How reproducible:
allways

Steps to Reproduce:
1. Open a terminal
2. start LO Writer from terminal
3.

Actual results:
LO crashes at startup

Expected results:


Additional info:
Comment 1 David Tardon 2017-10-21 06:12:33 UTC 

*** This bug has been marked as a duplicate of bug 1489731 ***