Summary: | Crash when changing opengl 2.0 -> opengl 3.1 | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Pascal d'Hermilly <pascal> |
Component: | compositing | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Kubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Pascal d'Hermilly
2015-03-02 09:29:13 UTC
Driver bug. Simply don't try - the GPU doesn't support GL 3 anyway. *** This bug has been marked as a duplicate of bug 327310 *** Why is possible to switch it into something that we apparently know is unsupported? The config dialog does not test the GPU and the context creation does not work this way. First, because accessing GL, what might - and in the past *did* - crash, in the dialog to configure the GL system turned out to be an ultimately bad idea. Second, because the context creation arb works by "try to create this context" "worked?" "no?" "try fallback context creation" The driver should just skip the GL3 context creation so we walk on to a GL2 context. ok. I just assumed the GPU in some way declared it's capabilities. Thanks "It is" - but the process is a bit hackish (you create a basic 1.3 context to use it to query the supported version by some legacy GL API) See eg. https://bugs.kde.org/show_bug.cgi?id=327310#c28 For the config module: in an ideal world, where drivers would never crash on even most basic calls, we'd just check capabilities, yes :-( |