Version: (using KDE KDE 3.2.0) Installed from: Compiled From Sources Compiler: Gcc 3.3.3 OS: Linux Kwin crashes if I move the cursor to a fullscreen shaded-window titlebar and attempt to move the window while the window is in the process of unshading. It first happened with Mozilla 1.6, second with Kword, third time with Moz again. It apparently only happens with fullscreen windows and is difficult to reproduce; after the second crash (kword) I played around for twenty minutes or so before I got it to reproduce with Mozilla (1.6). All the windows remain onscreen but I cannot type in any of them, not even a newly started terminal window. All the window title bars disappear. Most of the running applications exhibit strange behavior. Some applications will not start (notably KDE applications, others seem to work but the keyboard produces no response in some) So far I've been unable to get a backtrace, the bug window freezes when I hit the backtrace button and I'm forced to logout and relogin. Not sure how to restore kwin. The rightclick menu still works. I'm using the default themes and settings. Turning the "hover" setting off *may* stop the crash - at least it hasn't happened since (8 hours ago) - I'll continue to try to reproduce it again and to get a backtrace. Bug 53323 is similar but I do not have Desktop Menu enabled and there are some subtle differences. I installed kde 3.2.0 from source using Konstruct (debian unstable, gcc 3.3.3, glibc 2.2.5- I think) 5 days ago and the crash has happened three times. These are the notes I have so far, if I find out more or get a backtrace I'll add to this. Thanks.
[New Thread 1099434752 (LWP 1079)] 0x4107d3ee in __waitpid_nocancel () from /lib/tls/libpthread.so.0 #0 0x4107d3ee in __waitpid_nocancel () from /lib/tls/libpthread.so.0 #1 0x4078fc04 in KCrash::defaultCrashHandler(int) () from /home/andyg/kde3.2/lib/libkdecore.so.4 #2 <signal handler called> #3 0x41270da9 in raise () from /lib/tls/libc.so.6 #4 0x4137d110 in ?? () from /lib/tls/libc.so.6 #5 0xbfffe6f0 in ?? () #6 0x41272601 in abort () from /lib/tls/libc.so.6
[New Thread 1099434752 (LWP 1346)] 0x4107d3ee in __waitpid_nocancel () from /lib/tls/libpthread.so.0 #0 0x4107d3ee in __waitpid_nocancel () from /lib/tls/libpthread.so.0 #1 0x4078fc04 in KCrash::defaultCrashHandler(int) () from /home/andyg/kde3.2/lib/libkdecore.so.4 #2 <signal handler called> #3 0x41270da9 in raise () from /lib/tls/libc.so.6 #4 0x4137d110 in ?? () from /lib/tls/libc.so.6 #5 0xbfffe6f0 in ?? () #6 0x41272601 in abort () from /lib/tls/libc.so.6
I'm unable to type in the comment box for the backtraces (and unable to save the backtraces due to being unable to type a filename into the saveas dialog); as a matter of fact the keyboard seems completely disabled after the kwin crash, so I can't restart kwin from the Run dialog, so it appears to be KDE related. This crash *only* happens with fullscreen windows. Disabling hover did not make a difference. The first backtrace is from Mozilla; fullscreen, attempted to move window, kwin crashed. The second is from Konqueror; fullscreen, attempted to move window, kwin crashed. I'll note that I'm moving the mouse to the titlebar and click-hold-move. copy/paste continues to work using the rightclick menu, but not keyboard. minimized apps on the taskbar will not maximize Other notes: Panel is set to "shade" itself but does not appear affected by kwin crash. Menus all work. I'm not that familiar with the system calls but it appears to be a bad call or badly handled call to libc.so.6 - is it possible I need to update libc? The installation started as a Knoppix install and has been heavily updated using debian testing and debian unstable binaries, including a global update just before installing kde 3.2 via Konstruct. The install is otherwise very stable.
One more comment: Shaded windows do not exhibit the same behavior; ie, crashing kwin.
I was wrong. Shaded windows *do* exhibit the same behavior, as I just found out. This had not happened before. This seems to be getting progressively worse. I can't move a fullscreened window without a crash now.
Problem may *possibly* have been wmxmms and it's small window; investigating now.
managed to restart kwin from a console (after this crash for some reason the keyboard worked); then crashed it again. Here's the relevant console output: kwin: User timestamp, initial:87763800 kwin: User timestamp, ASN:87763800 kwin: User timestamp, final:87763800 kwin: User timestamp, initial:136482 kwin: User timestamp, ASN:136482 kwin: User timestamp, final:136482 kwin: User timestamp, initial:85732299 kwin: User timestamp, ASN:85732299 kwin: User timestamp, final:85732299 kwin: User timestamp, initial:87729241 kwin: User timestamp, ASN:87729241 kwin: User timestamp, final:87729241 kwin: User timestamp, initial:66014 kwin: User timestamp, ASN:66014 kwin: User timestamp, final:66014 kwin: User timestamp, initial:4294967295 kwin: User timestamp, ASN:4294967295 kwin: User timestamp, final:136666 kwin: User timestamp, initial:4294967295 kwin: User timestamp, ASN:4294967295 kwin: User timestamp, final:31163401 kwin: User timestamp, initial:37798979 kwin: User timestamp, ASN:37798979 kwin: User timestamp, final:37798979 kwin: User timestamp, initial:87790717 kwin: User timestamp, ASN:87790717 kwin: User timestamp, final:87790717 kwin: User timestamp, initial:87838443 kwin: User timestamp, ASN:87838443 kwin: User timestamp, final:87838443 kwin: h:34:t:29:b:8 kwin: geometry.cpp:1136: void KWinInternal::Client::setGeometry(int, int, int, int, KWinInternal::ForceGeometry_t): Assertion `false' failed.
*** Bug 75371 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 82837 ***