From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 70706] Regression in fbconfig
Date: Sat, 07 Dec 2013 22:31:02 +0000 [thread overview]
Message-ID: <bug-70706-502-x7MI7uLwVQ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-70706-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2717 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=70706
--- Comment #8 from Dennis Schridde <devurandom@gmx.net> ---
(In reply to comment #7)
> (In reply to comment #5)
> > To me this issue seems to appear randomly - sometimes KDE starts with
> > working compositing, but most often it does not.
>
> Same, here.
> When it starts _with_ compositing, then error message appears.
> _Without _ compositing glxinfo runs OK and GL performance is nearly 25%
> better!
In the current session I did not get compositing but the mentioned message in
~/.xession-errors:
kwin(2492): Failed to get visual from fbconfig
kwin(2492) KWin::OpenGLBackend::setFailed: Creating the OpenGL rendering
failed: "Could not initialize the buffer"
kwin(2492): Failed to initialize compositing, compositing disabled
glxinfo currently does not work, either:
Error: couldn't find RGB GLX visual or fbconfig
Error: couldn't find RGB GLX visual or fbconfig
name of display: :0
[...]
So the current session seems to be a case of "without compositing, with glxinfo
error". Which also seems to make sense: Something is preventing GL apps from
working, which also affects glxinfo.
A quick test shows that EGL does not seem to be affected:
$ eglinfo
EGL API version: 1.4
EGL vendor string: Mesa Project
EGL version string: 1.4 (Gallium)
EGL client APIs: OpenGL OpenGL_ES OpenGL_ES2
[...]
Also the X11 variants of the *gears (egl,es1,es2) programs work:
$ eglgears_x11
EGL_VERSION = 1.4 (Gallium)
But the "screen variants do not (though I do not remember ever before testing
them, so I cannot tell whether this is a regression):
$ eglgears_screen
EGL_VERSION = 1.4 (Gallium)
EGLUT: failed to choose a config
I can confirm this with KWin (stripped from unrelated output):
$ kwin
kwin(3945): Failed to get visual from fbconfig
kwin(3945) KWin::OpenGLBackend::setFailed: Creating the OpenGL rendering
failed: "Could not initialize the buffer"
QObject::connect: Cannot connect (null)::resetCompositing() to
KWin::Compositor::restart()
kwin(3945): Failed to initialize compositing, compositing disabled
kwin(3945): Consult
http://techbase.kde.org/Projects/KWin/4.0-release-notes#Setting_up
$ kwin_gles
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD REDWOOD
OpenGL version string: OpenGL ES 3.0 Mesa 9.2.4
OpenGL shading language version string: OpenGL ES GLSL ES 3.0
[...]
> So is there a possibility, that we can disable compositing on the fly, when
> GL apps starts?
I think that is a completely unrelated issue that belongs on
https://bugs.kde.org/ and should be reported against KWin.
--
You are receiving this mail because:
You are on the CC list for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3760 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-12-07 22:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-70706-502@http.bugs.freedesktop.org/>
2013-12-07 21:55 ` [Bug 70706] Regression in fbconfig bugzilla-daemon
2013-12-07 22:31 ` bugzilla-daemon [this message]
2013-12-17 22:40 ` bugzilla-daemon
2013-12-18 9:37 ` bugzilla-daemon
2013-12-18 9:39 ` bugzilla-daemon
2013-12-24 22:39 ` bugzilla-daemon
2014-01-02 20:17 ` bugzilla-daemon
2014-01-05 9:12 ` bugzilla-daemon
2014-02-01 21:02 ` bugzilla-daemon
2014-02-04 0:40 ` bugzilla-daemon
2014-02-05 17:29 ` bugzilla-daemon
2014-02-15 20:03 ` bugzilla-daemon
2014-02-17 23:47 ` bugzilla-daemon
2014-02-19 19:16 ` bugzilla-daemon
2014-02-25 8:53 ` bugzilla-daemon
2014-04-07 18:03 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-70706-502-x7MI7uLwVQ@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).