If OpenGL acceleration is enabled but hardware does not support it, LO fails to start silently.
Either error message should appear, or LO should prompt user to disable it automatically.
@Urmas, could you let us know which hardware you tested this on and how does one enable opengl acceleration.
CCing Markus as he's the OpenGL man. :D
Settings/View/Use OpenGL for all rendering
In my case that was VirtualBox VM.
I cant see any setting called 'Use OpenGL for all rendering' in master. Do you have a screenshot?
Created attachment 111276 [details]
Thanks for the screenshot. Seems my current build from 12-12 doesnt have it in it but i see it in the latest build. :D
I think it would be good for you to send in a backtrace so someone can see why it silently fails. I've had similar opengl crashes in the past, like in bug 80448.
Don't use that setting right now. We have horrible issues with memory corruption and race conditions.
Created attachment 112955 [details]
ODT file detailing this issue
(In reply to Dave Barton from comment #7)
> Created attachment 112955 [details]
> ODT file detailing this issue
Looks like we have an issue with our self hosted bugzilla. The attachment was sent without the following text comment:
This issue exists in both:
Version: 184.108.40.206 Build ID: de093506bcdc5fafd9023ee680b8c60e3e0645d7
Version: 220.127.116.11.alpha0+ Build ID: 309574394bd4ae3e9e10e5ff0d64bdd7bbbc8b83
My experience is that LO does not fail to start silently, but opens in a totally unusable state, from which the "average" (non-technical) user cannot recover.
(In reply to Dave Barton from comment #8)
> This issue exists in both:
> Version: 18.104.22.168 Build ID: de093506bcdc5fafd9023ee680b8c60e3e0645d7
> Version: 22.214.171.124.alpha0+ Build ID: 309574394bd4ae3e9e10e5ff0d64bdd7bbbc8b83
Status -> NEW
> My experience is that LO does not fail to start silently, but opens in a
> totally unusable state, from which the "average" (non-technical) user cannot
(Dave: What you're experiencing might be a different issue, but markus will have more insight here)
*** Bug 88800 has been marked as a duplicate of this bug. ***
I can confirm same problem on my laptop.
here's how it looks like:
win7x64, i7 3GHz, 8GB RAM, IntelHD4000 & Nvidia NVS 5200M 1GB, 2 monitors attached to each, 4 in total.
Generally, I can run both OpenGL and DirectX games on this laptop.
Wrt. focusing on the initial issue here; I believe we need to catch badness, particularly crashes during rendering operations and present a native-dialog on-start / recovery to allow the option of disabling GL. Luckily VCL provides a native dialog API to allow by-passing the necessity of using VCL, and (I hope) we could detect this rather early in the startup cf.
virtual int ShowNativeMessageBox( const OUString& rTitle,
const OUString& rMessage,
bool bUseResources ) = 0;
Which was previously used to explain accessibility problems rather early in the startup, but seems like a great match for this use-case too.
My hope is that this is handled by a combination of the white/black lists cf. bug#93662 (pending merge) - and also the crash / hang catching logic we added in bug#93547 and bug#93614.
Thanks for reporting !
When i enabled 'Use OpenGL for all rendering' and 'Force OpenGL even if blacklisted' and it crashed, it would automatically disable 'Use OpenGL for all rendering' on load but wouldnt disable 'Force OpenGL even if blacklisted' resulting in it not opening. Should i report this as a new bug?
Build ID: cf9fbdb379e2935677a73ced513d7faf855c299c
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2015-09-05_00:34:47
Locale: en-US (en_US.UTF-8)