Bug 268766 - kwin crashes when changing settings related to kwin
Summary: kwin crashes when changing settings related to kwin
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Chakra Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-17 18:40 UTC by William A.
Modified: 2011-03-17 23:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
this is the backtrace (3.28 KB, application/octet-stream)
2011-03-17 18:40 UTC, William A.
Details

Note You need to log in before you can comment on or make changes to this bug.
Description William A. 2011-03-17 18:40:18 UTC
Created attachment 58127 [details]
this is the backtrace 

Version:           4.6 (using KDE 4.6.0) 
OS:                Linux

after changing the kwin setings the plasma work space goes out for a  minute and then restarts the plasma work space 

Reproducible: Sometimes

Steps to Reproduce:
enabling the desktop effects in kde 

Actual Results:  
it crashed and then restarted after

Expected Results:  
it should of have displayed a error message saying the the desktop effects are not compatible with your graphics card
Comment 1 Christoph Feck 2011-03-17 23:05:32 UTC
KWin tries best to detect features of the video drivers. It can, however, not prevent crashes when there are bugs in the drivers. Please report the bug to https://bugs.freedesktop.org/
Comment 2 Thomas Lübking 2011-03-17 23:16:54 UTC
a) the backtrace is of little use because it lacks important informations about what code was called inside kwin

b) if however results in
#7  0xb3910ab7 in xcb_glx_get_string_string_length () from /usr/lib/libxcb-glx.so.0
#8  0xb6ac1da4 in ?? () from /usr/lib/libGL.so.1
#9  0xb6aa5b34 in ?? () from /usr/lib/libGL.so.1
#10 0xb6aa316f in glXMakeCurrentReadSGI () from /usr/lib/libGL.so.1
#11 0xb6aa3303 in glXMakeCurrent () from /usr/lib/libGL.so.1
what means it's a driver bug

c) for any kind of further assistance we'd need at least to know your GPU/Driver configuration (you likely wish to upgrade Mesa or try "export LIBGL_ALWAYS_INDIRECT=1"

d) This should* happen only once, from now on kwin will likely know about your driver issue and do not attempt to activate compositing w/o further explicit actions.
*but since it's not possible to precisely say where the crash occurs, this can't be said for sure.
Comment 3 Thomas Lübking 2011-03-17 23:17:29 UTC
forgot to tag the bug...