Summary: | Crash after Alt+Shift+F12 | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Andras888 <andrew> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian stable | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Andras888
2012-06-02 13:38:53 UTC
"kcmshell4 kwincompositing", disable blur effect (2nd tab) and set the scale method to smooth (3rd tab) for the records please also specify your gpu and mesa/driver version - in doubt run "kwin --replace&" fro konsole and post the output. Thanks. *** This bug has been marked as a duplicate of bug 270818 *** andras@andras-desktop ~ $ QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory QFileSystemWatcher: failed to add paths: /home/andras/.config/ibus/bus OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: ATI Radeon HD 3200 Graphics OpenGL version string: 1.4 (2.1 (3.3.11554 Compatibility Profile Context)) Driver: Catalyst Driver version: 2.1 GPU class: R600 OpenGL version: 1.4 X server version: 1.10.4 Linux kernel version: 3.0 Direct rendering: no Requires strict binding: yes GLSL shaders: no Texture NPOT support: yes kwin(6344): glCheckFramebufferStatus failed: "GL_NO_ERROR" kwin(6344): Failed to compile fragment program: kwin(6344): Shaders are not supported kwin(6344): Shaders are not supported kwin(6344): Shaders are not supported kwin(6344): Shaders are not supported andras@andras-desktop ~ $ kwin(6344) KWin::checkGLError: GL error ( PostPaint ): "GL_INVALID_ENUM" [1]- Done kwin --replace andras@andras-desktop ~ $ Thomas, Thanks for your quick responce. If I understand this correctly, the bug is "resolved downstream". I believe my system us up-to-date. How do I fix this then? Thank you, Andras888 "resolved" does not mean "solved" - just that the bug is outside our scope (in the up/downstream case) and no open task. however, while being the same trigger and result, the other bug was caused by a software gl installation, but fglrx causes the very same. you can - try the radeon driver (xf86-video-ati/ati-dri) - try fglx with enforced direct rendering (late versions have been reported to be reliable) "KWIN_DIRECT_GL=1 kwin --replace &" - remain staying away from the ARB shader using code (as hinted) - ensure that this issue in fglrx is not caused by it's setup demands (afaik one has to run some script after un/installing it) |