Summary: | kwin crashes on startup, so I have to switch to openbox to have window decorations. | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | chous |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | mchugh19, toba |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | New crash information added by DrKonqi |
Description
chous
2010-03-07 12:00:28 UTC
This is a driver issue. There is nothing we can do about it. In 4.4 we have a workaround for those crashy drivers. *** This bug has been marked as a duplicate of bug 213182 *** Created attachment 71832 [details]
New crash information added by DrKonqi
kwin (4.8.3 (4.8.3)) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1
- What I was doing when the application crashed: just tried to boot up, when KDE greeted me with this crash log.
-- Backtrace (Reduced):
#6 0x00007f0defe1c100 in xcb_glx_query_server_string_string_length () from /usr/lib/x86_64-linux-gnu/libxcb-glx.so.0
#7 0x00007f0df7e15444 in __glXQueryServerString (dpy=<optimized out>, opcode=<optimized out>, screen=0, name=2) at glx_query.c:58
#8 0x00007f0df7df5348 in AllocAndFetchScreenConfigs (priv=0x13cab90, dpy=0x1319a60) at glxext.c:770
#9 __glXInitialize (dpy=0x1319a60) at glxext.c:885
#10 __glXInitialize (dpy=0x1319a60) at glxext.c:803
See comments - the bug is in the OpenGL implementation of the driver and the workaround is to disable OpenGL compositing when this happens and not easily try again to use it (also iirc CompositingPrefs are no longer used and the check will happen in a second process only in 4.9) You can try whether this is due to conditions when X11 starts up (but you can enable OpenGL compositing afterwards) or use the XRender backend or omit compositing. For the records, please name you GPU and driver (as this has not been recorded for a long time now) Graphic card: Asus HD-6670. I had an out of date proprietary driver (amd-driver-installer-12-3-x86.x86_64.run) Installed the newest (amd-driver-installer-12-4-x86.x86_64.run) since then. This may have fixed it for me. *** Bug 306361 has been marked as a duplicate of this bug. *** *** Bug 323298 has been marked as a duplicate of this bug. *** |