Bug 101968 - Crash on startup with OpenGL enabled using proprietary NVIDIA drivers on Ubuntu 16.04
Summary: Crash on startup with OpenGL enabled using proprietary NVIDIA drivers on Ubun...
Status: RESOLVED DUPLICATE of bug 97160
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.2.1.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: haveBacktrace
Depends on:
Blocks:
 
Reported: 2016-09-07 15:40 UTC by Element Green
Modified: 2016-09-24 19:19 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
GDB backtrace of SIGSEV crash when OpenGL is enabled. (12.52 KB, text/x-log)
2016-09-07 15:40 UTC, Element Green 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Element Green 2016-09-07 15:40:38 UTC 
Created attachment 127202 [details]
GDB backtrace of SIGSEV crash when OpenGL is enabled.

I'm trying to get OpenGL working in order to use OpenGL capture utilities to record the output of Impress.  However, once OpenGL is enabled LibreOffice crashes (regardless of which application is started).

I've tested two recent versions of LibreOffice.  ppa:libreoffice/libreoffice-5-2 which currently is currently at 5.2.1.2 Build ID: 1:5.2.1~rc2-0ubuntu1-xenial0.  The other one I tried is the tar archive download from the main LibreOffice website which is currently at LibreOffice_5.2.1_Linux_x86-64_rpm.tar.gz.  Both behave the same in regards to this issue.

Attached is a GDB backtrace using the "--backtrace" command line switch to libreoffice.

System details:
Ubuntu 16.04 on x86_64
Nvidia GeForce GTX 960
Binary driver version: 367.35

I wouldn't care so much about getting OpenGL working if I knew of a better way to capture an Impress presentation with animations to a video.
Comment 1 Buovjaga 2016-09-24 19:19:45 UTC 

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