Bug 257243 - Kwin crashes after font or color configuration in systemsettings
Summary: Kwin crashes after font or color configuration in systemsettings
Status: RESOLVED DUPLICATE of bug 241402
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 0.2
Platform: Debian unstable Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-18 13:57 UTC by micu
Modified: 2010-11-18 18:05 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description micu 2010-11-18 13:57:44 UTC 
Version:           0.2 (using KDE 4.5.2) 
OS:                Linux

When setting other fonts or other colors in »Appearance of applications« (»Erscheinungsbild von Anwendungen«), a part of systemsettings, KWin crashes and can only be killed with kill -9

Running aptosid with KDE SC 4.5.2 binaries from http://qt-kde.debian.net/

Reproducible: Sometimes




OS: Linux (x86_64) release 2.6.36-0.slh.5-aptosid-amd64
Compiler: cc
Comment 1 Thomas Lübking 2010-11-18 16:48:03 UTC 
please check whether this is bug #241402 (freeze, mesa < 7.9rc2 bug, fixed in latter mesa versions. can be worked around by "export LIBGL_ALWAYS_INDIRECT=1" in ~/.xprofile)
Comment 2 micu 2010-11-18 18:01:41 UTC 
(In reply to comment #1)

Yepp, it seems to be this issue, as I run mesa version 7.8.2-2 (Debian packages can get a bit old even in sid if a new release is about to come) and, most of all, the workaround with the environment variable does indeed work around the problem.

BTW: I had to put »export »LIBGL_ALWAYS_INDIRECT="1";« in ~/.profile, putting it in ~/.xprofile didn't have any effect here it all. :/

Sorry for causing disturbance and, even more, thanks for helping!
Comment 3 Thomas Lübking 2010-11-18 18:05:48 UTC 
~/.xprofile is interpreted by kdm (and likely gdm as well).
if you use eg. startx you'll oc have to use its init scripts ;-)

*** This bug has been marked as a duplicate of bug 241402 ***