Summary: | Since 4.12.0 Creating the OpenGL rendering failed: "Could not initialize the buffer" in KWin | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Oliver Maurhart <dyle71> |
Component: | compositing | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | dyle71, ganellon, sgh |
Priority: | NOR | ||
Version: | 4.11.4 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
output of glxinfo
output of qdbus org.kde.kwin /KWin supportInformation |
Description
Oliver Maurhart
2014-01-13 10:06:37 UTC
please attach the full output of "glxinfo" and "qdbus org.kde.kwin /KWin supportInformation" On a wild guess: don't try to use OpenGL 3.0, but provide the requested information anyway. Created attachment 84622 [details]
output of glxinfo
Created attachment 84623 [details]
output of qdbus org.kde.kwin /KWin supportInformation
attached files as requested. wired. Kwin reports itself as 4.11.5 ... $ cat kwin.supportinformation.txt | grep -A 4 '^Version' Version ======= KWin version: 4.11.5 KDE SC version (runtime): 4.12.0 KDE SC version (compile): 4.12.0 Huh? (In reply to comment #1) > On a wild guess: don't try to use OpenGL 3.0, but provide the requested > information anyway. In the SystemSettings I can chose between "OpenGL 3.1", "OpenGL 2.0", "OpenGL 1.2" and XRender. It is set to "OpenGL 3.1", changing the value in the drop-down to "OpenGL 2.0" or "OpenGL 1.2" results into an error messages and it changes back to "OpenGL 3.1". Didn't try XRender ... run kquitapp kwin; sleep 1; kwriteconfig --file kwinrc --group Compositing --key GLCore false; kwin & The driver will likely end in an invalid state after trying to create the GL3 context and subsequently fail. See bug #327310 (In reply to comment #6) > run > kquitapp kwin; sleep 1; kwriteconfig --file kwinrc --group Compositing --key > GLCore false; kwin & > > The driver will likely end in an invalid state after trying to create the > GL3 context and subsequently fail. > > See bug #327310 Tried "kquitapp kwin; sleep 1; kwriteconfig --file kwinrc --group Compositing --key GLCore false; kwin &" but didn't change anything. Kwin also does not crash. KDE renders 2D only like 10 years ago. So, is this a driver bug in the Intel HD Graphics? It has been working with recent kernels but my current 3.12.7 / KDE 4.12 installment. Try restarting X11, eventually rebooting (or reloading the intel kernel module) If this line: "Failed to get visual from fbconfig" is still present afterwards, it's "real" and a different issue. (glXGetVisualFromFBConfig fails for unknown reasons) Back in the office. Just booted the machine. OpenGL and composite working ... don't know why. Confused. Anything I can post to light up the behavior? I'm fairly sure that this is bug #327310 It's likely that the (legal) attempt to create a GL3 context put the driver/kernel module into an invalid state. @Martin Should we better - *sigh* - blacklist intel from OGL3? *** This bug has been marked as a duplicate of bug 327310 *** I believe that this is not an intel fault. At least not always. I have, sometimes(!), same problem. If I log in to second session (different user) compositing will work. If I start receive message "kwin(...): Failed to get visual from fbconfig" then it's does not matter which OpenGL version I will choose in settings - kwin can't start with any OpenGL variation as compositing type (only xrandr still work). And, at the same time second X server working, with another kwin and allow me to choose any compositing type option. First time this bug appeared some time ago, I just restart X server few times unless compositing start to work and, because my laptop usually have big uptime, it didn't bothered me often. But now it became annoying. Currently I run KWin version: 4.11.5 KDE SC version (runtime): 4.12.1 KDE SC version (compile): 4.12.1 Qt Version: 4.8.5 Most settings same as in attachments that is already there. And last but not least: kwin not crashed when it failed with fbconfig, it just disable compositing. So I don't understand why this bug is closed as dup of completely different bug. Also there are another bug https://bugs.freedesktop.org/show_bug.cgi?id=70706 in which xorg server is blamed as root cause. (sorry for spam) Forgot to add that in my case glxinfo still show that everything is okay, while glxinfo report attached to bug on freedesktop say "Error: couldn't find RGB GLX visual or fbconfig". The link is bug #330440 (the source of your fdo bug and probably exact dupe) From our POV it's just that as soon as we try to create a core profile context, MESA/Xorg/Intel/Radeon start/s to act unpredictably - you might very well run into the crash once the (apparent) Xorg bug is resolved and if we'd still try to create a core context. The target bug got dated in it's attributes though, yes. Okay then. But isn't it's strange that {glx,egl}{info,gears} work as usual while kwin still failed to do his "fbconfig" stuff? I tried to restart kwin many times, with different initial setting and env variables, to get some more info or clue what happens, but it still failed to turn on compositing. At the same time glx/eglgears works in same x server. matter between "modern" glXCreateContextAttribsARB and glXCreateNewContext creation. Using these extensions does not work: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness |