(this form is stupid) Reproducible: Sometimes Steps to Reproduce: 1. go to "desktop effects" => "advanced" 2. switch "compositing type" from "opengl 2.0" to "xrender" or vice versa 3. hit apply Actual Results: message box "Failed to activate desktop effects using the given configuration options. Settings will be reverted to their previous values." pops up. it doesn't happen always, and i wasn't able to find any pattern behind it. it doesn't appear to matter whether desktop effects are currently enabled or not. for a while it started to work after i toggled effects, but that may have been timing or just coincidence. fwiw, it's not obvious what the right component is. systemsettings has no kcm_kwin or related component, and kwin has no kcm component.
Does it depend on changing the graphicssystem? (raster <-> native)
nope
I cannot reproduce the issue, though I cannot change to OpenGL 3.1 (that gets always reverted). <offtopic>We don't use a generic kcm section, but consider the kcms as parts of the area of KWin which is configured with it. So in this case: compositing.</offtopic>
Created attachment 84999 [details] Output directly after kde start
Created attachment 85000 [details] Output after enabling OpenGL3.1
Created attachment 85001 [details] output from glxinfo
Here is the same on ATI-Graphics, using r600 (radeon). Somtimes i could change the compositing type, sometimes not. At kde startup, there is XRender/Native on. I apply 2 attachments, the output from "qdbus-qt4 org.kde.kwin /KWin supportInformation" One shows the result directly after login, the other one after changing to OpenGL 3.1/Native. As i described above, sometimes i could not change the Compositing type, then it fails with the message "Failed to activate desktop effects using the given configuration options. ..." A output from glxinfo is attached too.
Created attachment 85002 [details] output from glxinfo
If i try to restart kwin i get this: $ kwin --replace & [1] 19641 [kaputtnik@kaputtnik-arch ~$ QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread kwin(19641): Failed to get visual from fbconfig kwin(19641) KWin::OpenGLBackend::setFailed: Creating the OpenGL rendering failed: "Could not initialize the buffer" QObject::connect: Cannot connect (null)::resetCompositing() to KWin::Compositor::restart() kwin(19641): Failed to initialize compositing, compositing disabled kwin(19641): Consult http://techbase.kde.org/Projects/KWin/4.0-release-notes#Setting_up What means "could not initialize the buffer"?
Think, this is a duplicate of #327310
your bug is in particular bug #320011 and not related to this one. Should be fixed in 4.11.7
Oh, thanks :-)
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Can't reproduce this anymore with: KWin version: 5.14.3 Qt Version: 5.11.2 Qt compile version: 5.11.2 XCB compile version: 1.13.1 I think this bug can marked fixed, or so :-)
Thanks for the update!