Bug 1436011

Summary:	LibreOffice fails to start with 'dri2 connection failed!' error
Product:	[Fedora] Fedora	Reporter:	Jiri Eischmann <jeischma>
Component:	libreoffice	Assignee:	Caolan McNamara <caolanm>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	26	CC:	caolanm, dtardon, erack, mstahl, sbergman
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-27 08:19:13 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 Jiri Eischmann 2017-03-26 17:14:07 UTC

LibreOffice fails to start with the following error output:

missing hardware logical context support
X server found. dri2 connection failed! 
X server found. dri2 connection failed! 
cl_get_gt_device(): error, unknown device: 2a42
X server found. dri2 connection failed! 
X server found. dri2 connection failed! 
cl_get_gt_device(): error, unknown device: 2a42
X server found. dri2 connection failed! 
cl_get_gt_device(): error, unknown device: 2a42
X server found. dri2 connection failed! 
cl_get_gt_device(): error, unknown device: 2a42
X server found. dri2 connection failed! 
cl_get_gt_device(): error, unknown device: 2a42
sh: /usr/bin/clang++: No such file or directory
soffice.bin: /builddir/build/BUILD/pocl-3fef5b58014c40e3e746a7ada281498582d8d569/lib/CL/devices/common.c:127: llvm_codegen: Assertion `error == 0' failed.

Not sure if it's a bug in LibreOffice or lower in the stack, but it doesn't occur with other desktop applications.

I'm using GNOME on Wayland.

Comment 1 Jiri Eischmann 2017-03-26 17:17:56 UTC

BTW LibreOffice 5.3 in Flatpak runs well.

Comment 2 Caolan McNamara 2017-03-27 08:19:13 UTC


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