Bug 195304 - kwin/plasam crahs when tapping and one windows is closing
Summary: kwin/plasam crahs when tapping and one windows is closing
Status: RESOLVED DUPLICATE of bug 184602
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-05 10:33 UTC by Jonas Vejlin
Modified: 2009-06-05 13:46 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jonas Vejlin 2009-06-05 10:33:22 UTC
Version:            (using KDE 4.2.4)
OS:                Linux
Installed from:    Debian testing/unstable Packages

I was tapping trough all my porgrams when it crashed. Here the output
Program: KWin (kwin), signal SIGSEGV

Thread 1 (Thread 0xb539f730 (LWP 7510)):
#0  0xb7fa8424 in __kernel_vsyscall ()
#1  0xb7e22350 in nanosleep () from /lib/i686/cmov/libc.so.6
#2  0xb7e2218e in sleep () from /lib/i686/cmov/libc.so.6
#3  0xb7c420f8 in ?? () from /usr/lib/libkdeui.so.5
#4  0x00000000 in ?? ()

way to reproduce it:
Have a windows that is going to close wile tapping
tap unto the window closed.
crash

I was using syanptic and reloding the information about withc package
the repo did have.

After the crash it looks like plasma is reloding but only the Windows that was open before the crahs repair. No backgroud/wallpapir, no menus, no panels
Comment 1 A. Spehr 2009-06-05 11:30:49 UTC
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Will give us a backtrace to double check. That one has too many ??

*** This bug has been marked as a duplicate of bug 195104 ***
Comment 2 A. Spehr 2009-06-05 11:33:16 UTC
Ack. Wrong bug. Fixing.

*** This bug has been marked as a duplicate of bug 184602 ***
Comment 3 Jonas Vejlin 2009-06-05 13:46:44 UTC
I just install some extra package and I got this from gdb;
Dette backtrace synes at være nytteløst.
Det er formodentlig fordi dine pakker er bygget på en måde som forhindrer oprettelse af ordentlige backtrace, eller at stakrammen blev alvorligt korrumperet under sammenbruddet.

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5336730 (LWP 3888)]
0xb7f3f424 in __kernel_vsyscall ()
[Current thread is 0 (process 3888)]

Thread 1 (Thread 0xb5336730 (LWP 3888)):
#0  0xb7f3f424 in __kernel_vsyscall ()
#1  0xb7db9350 in nanosleep () from /lib/i686/cmov/libc.so.6
#2  0xb7db918e in sleep () from /lib/i686/cmov/libc.so.6
#3  0xb7bd90f8 in KCrash::startDrKonqi (argv=0xbfb59f08, argc=17) at ../../kdeui/util/kcrash.cpp:412
#4  0xb7bd9ac4 in KCrash::defaultCrashHandler (sig=11) at ../../kdeui/util/kcrash.cpp:337
#5  <signal handler called>
#6  0x00ff0000 in ?? ()
#7  0xb794a2e2 in KWin::WindowPaintData::WindowPaintData () from /usr/lib/libkwineffects.so.1
#8  0xb33c825c in ?? () from /usr/lib/kde4/kwin4_effect_builtins.so
#9  0xbfb5a680 in ?? ()
#10 0x0a2e5ed8 in ?? ()
#11 0x00000000 in ?? ()
#0  0xb7f3f424 in __kernel_vsyscall ()

Is that a bether backtrace?