Bug 229796 - kwin crashes on startup, so I have to switch to openbox to have window decorations.
Summary: kwin crashes on startup, so I have to switch to openbox to have window decora...
Status: RESOLVED DUPLICATE of bug 213182
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
: 306361 323298 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-03-07 12:00 UTC by chous
Modified: 2013-08-08 22:17 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (1.91 KB, text/plain)
2012-06-14 16:03 UTC, toba
Details

Note You need to log in before you can comment on or make changes to this bug.
Description chous 2010-03-07 12:00:28 UTC
Application that crashed: kwin
Version of the application: 4.3.5 (KDE 4.3.5)
KDE Version: 4.3.5 (KDE 4.3.5)
Qt Version: 4.5.3
Operating System: Linux 2.6.30-gentoo-r1 i686

What I was doing when the application crashed:
The same backtrace is thrown when, once within openbox, I try to access 'System settings' > 'Desktop', in order to disable desktop effects.

 -- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
[KCrash Handler]
#6  0xb532aea6 in xcb_glx_query_server_string_string_length () from /usr/lib/libxcb-glx.so.0
#7  0xb6ab0877 in __glXQueryServerString (dpy=0x909cde0, opcode=152, screen=0, name=2) at glx_query.c:61
#8  0xb6a7f7c1 in AllocAndFetchScreenConfigs (dpy=0x909cde0, priv=0x912f900) at glxext.c:604
#9  0xb6a7fb97 in __glXInitialize (dpy=0x909cde0) at glxext.c:736
#10 0xb6a799b0 in glXQueryVersion (dpy=0x909cde0, major=0xbf86c4a0, minor=0xbf86c49c) at glxcmds.c:573
#11 0xb80c8530 in KWin::CompositingPrefs::detect (this=0xbf86c514) at /var/tmp/portage/kde-base/kwin-4.3.5-r1/work/kwin-4.3.5/kwin/compositingprefs.cpp:146
#12 0xb8061db1 in KWin::Options::updateSettings (this=0x90f2788) at /var/tmp/portage/kde-base/kwin-4.3.5-r1/work/kwin-4.3.5/kwin/options.cpp:211
#13 0xb8061fa3 in Options (this=0x90f2788) at /var/tmp/portage/kde-base/kwin-4.3.5-r1/work/kwin-4.3.5/kwin/options.cpp:51
#14 0xb804ea3c in Application (this=0xbf86cc50) at /var/tmp/portage/kde-base/kwin-4.3.5-r1/work/kwin-4.3.5/kwin/main.cpp:317
#15 0xb804f677 in kdemain (argc=3, argv=0xbf86ce24) at /var/tmp/portage/kde-base/kwin-4.3.5-r1/work/kwin-4.3.5/kwin/main.cpp:502
#16 0x08048866 in main (argc=) at /var/tmp/portage/kde-base/kwin-4.3.5-r1/work/kwin-4.3.5_build/kwin/kwin_dummy.cpp:3

Reported using DrKonqi
Comment 1 Martin Flöser 2010-03-07 13:22:07 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 ***
Comment 2 toba 2012-06-14 16:03:35 UTC
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
Comment 3 Thomas Lübking 2012-06-14 16:35:22 UTC
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)
Comment 4 toba 2012-06-15 14:10:29 UTC
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.
Comment 5 Thomas Lübking 2013-08-08 20:05:47 UTC
*** Bug 306361 has been marked as a duplicate of this bug. ***
Comment 6 Thomas Lübking 2013-08-08 22:17:20 UTC
*** Bug 323298 has been marked as a duplicate of this bug. ***