| Summary: | KWin crash after applying new font size | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Hrvoje Senjan <hrvoje.senjan> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Hrvoje Senjan
2012-06-19 20:43:20 UTC
#15 0x00007f1d3282b85b in ?? () from /usr/lib/fglrx/libGL.so.1 #16 0x00007f1d36432e4c in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so #17 0x00007f1d36433470 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so #18 0x00007f1d36415ff2 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so Unfortunately the relevant libraries are stripped. a) Can you compile with debug enabled? b) The backtrace ends in fglxr and is most likely a driver issue. c) it might only occur on the very first execution after booting (undefined state in the driver), pot. it re-occurs after logging out and back in. Do you force direct GL? If not you can *try* exporting KWIN_DIRECT_GL=1 temporarily run KWIN_DIRECT_GL=1 kwin --replace & for long time setting, add an *executable* shell script to ~/.kde/env -------- snip force_dri.sh ------------ #!/bin/sh export KWIN_DIRECT_GL=1 -------- /snip force_dri.sh ------------ DRI with fglrx used to fail but latter reports suggest it meanwhile works (better than indirect rendering) Thomas, i'm sorry for missing backtraces, drkonqi fooled me with it's 3 little stars, i didn't noticed i don't have kde-workspace debug package installed, and backtraces anyway look like hieroglyphs to me :) (other than library names). So far i didn't manage trigger the crash, and i am not forcing direct rendering, these newer, "better" working drivers don't cover my hardware anymore, and lately fglrx has been behaving pretty good (no crashes for a long time, until this one). Do you have any idea what could trigger the crash? (If that does mean anything, systemsettings window was maximized.) (In reply to comment #2) > Do you have any idea what could trigger the crash? (If that does mean > anything, systemsettings window was maximized.) Nope, sorry - not w/o a backtrace ;-) However the xio error seems to be usually caused by some installation issues, remaining mesa installation, whatever - esp. ensure you ran "/usr/bin/aticonfig --initial" I'll close this for now, cause can't get the crash anymore.
Thomas:
ldconfig -p | grep libGL
libGLU.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libGLU.so.1
libGLU.so.1 (libc6) => /usr/lib/i386-linux-gnu/libGLU.so.1
libGLU.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libGLU.so
libGLEW.so.1.5 (libc6,x86-64) => /usr/lib/libGLEW.so.1.5
libGLEW.so (libc6,x86-64) => /usr/lib/libGLEW.so
libGLESv2.so.2 (libc6,x86-64, OS ABI: Linux 2.4.20) => /usr/lib/x86_64-linux-gnu/mesa-egl/libGLESv2.so.2
libGL.so.1 (libc6,x86-64) => /usr/lib/fglrx/libGL.so.1
libGL.so.1 (libc6) => /usr/lib32/fglrx/libGL.so.1
libGL.so (libc6,x86-64, OS ABI: Linux 2.4.20) => /usr/lib/x86_64-linux-gnu/libGL.so
libGL.so (libc6,x86-64) => /usr/lib/fglrx/libGL.so
|