Version: (using Devel) Installed from: Compiled sources OS: Linux Using krandrtray to resize desktop size to 1680 x 1050 causes kwin to crash. 1680 x 1050 seems to be highest available resolution. I have a HP 24" LCD monitor (1900x1220? native), Intel graphics. Application: KWin (kwin), signal SIGSEGV (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6540ac0 (LWP 4679)] [New Thread 0xb49b7b90 (LWP 5562)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall () [Current thread is 0 (LWP 4679)] Thread 2 (Thread 0xb49b7b90 (LWP 5562)): #0 0xffffe410 in __kernel_vsyscall () #1 0xb7e7f771 in select () from /lib/i686/cmov/libc.so.6 #2 0xb71639e0 in ?? () from /usr/lib/libQtCore.so.4 #3 0xb7095322 in ?? () from /usr/lib/libQtCore.so.4 #4 0xb68b84b0 in start_thread () from /lib/i686/cmov/libpthread.so.0 #5 0xb7e8738e in clone () from /lib/i686/cmov/libc.so.6 Thread 1 (Thread 0xb6540ac0 (LWP 4679)): #0 0xffffe410 in __kernel_vsyscall () #1 0xb7e42dc6 in nanosleep () from /lib/i686/cmov/libc.so.6 #2 0xb7e42bdf in sleep () from /lib/i686/cmov/libc.so.6 #3 0xb6f1be96 in ?? () from /usr/lib/libkdeui.so.5 #4 0x00000000 in ?? () #0 0xffffe410 in __kernel_vsyscall ()
This type of backtrace is not very useful, you should install the -debug enabled packages. You should read this page for the instructions: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports *** This bug has been marked as a duplicate of 154245 ***