Bug 143674 - window manager crashes when other programs crash or have errors
Summary: window manager crashes when other programs crash or have errors
Status: RESOLVED REMIND
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-31 18:51 UTC by thomas
Modified: 2007-07-17 12:11 UTC (History)
0 users

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 thomas 2007-03-31 18:51:17 UTC
Version:            (using KDE KDE 3.5.6)
Installed from:    Compiled From Sources
Compiler:          gcc 3.4.4 pre 
OS:                Linux

When some programs (like bittorrent, kwifimanager) crash or report errors,
the window decorations disappear and the keyboard is unresponsive.  The
mouse still seems to work, but cannot select a window or raise it.  Often,
the panel disappears, too.  The only fix is ctl-alt-bs and start all over.
I can easily reproduce this by trying to connect to an ad-hoc router in
kwifimanager.  That always crashes kwifimanager, brings up a KDE crash report
window, and all window decorations etc. disappear.
Comment 1 thomas 2007-04-01 20:47:55 UTC
KWin may not be the problem.  Evidence:  I compiled and
installed KWin from KDE 3.3.1 on top of KDE 3.5.6, and
the problem persists.
Comment 2 Lubos Lunak 2007-06-01 15:51:33 UTC
Can you provide some other way to reproduce?
Comment 3 thomas 2007-06-01 16:48:03 UTC
To reproduce:  make any kde application crash.
The window manager then crashes too, and does
not restart.

Maybe you could write a small KDE app that
does nothing but segfault when you press a
button.  I would do it, but I don't know how.

Meanwhile, I am using KDE 3.3.1 because 3.5.6
is completely unusable in this condition (esp.
since konqueror crashes sometimes, and this
brings down kwin).
Comment 4 thomas 2007-06-01 17:05:38 UTC
Here, this reproduces it:

konqueror &
pkill -11 konqueror
Comment 5 jos poortvliet 2007-06-01 18:02:16 UTC
I have Kwin 3.5.7, and it never crashes (and apps DO crash here now and then).
Comment 6 Bram Schoenmakers 2007-06-01 22:24:49 UTC
You happen to use third party 3d drivers or special effects which don't come with kwin by default? I really wonder if this is a KWin bug at all.

Can you get your hand on a backtrace?
Comment 7 thomas 2007-06-02 00:38:56 UTC
> You happen to use third party 3d drivers ... ?

I have the nVidia driver for X11 (and its own libGL).
KDE 3.3.1 does not crash like this, with the same
nVidia driver.

> Can you get your hand on a backtrace?

How?  I do not have gdb.

> I really wonder if this is a KWin bug at all.

I share your suspicion, as I have said, this bug
happens to me with kdelibs 3.5.6 and kdebase 3.3.1
on top of it, as well as with the correct combination
kdelibs 3.5.6 and kdebase 3.5.6.  I don't have the
expertise to track it down further than that.

Comment 8 thomas 2007-06-03 18:44:41 UTC
OK, so I spent a few hours installing 3.5.7
libs and base.  Killing konqueror does not
crash the new kwin, but this does:

kcontrol &
pkill -11 kcontrol

Two crash windows come up, all window decorations
disappear on all windows, and the keyboard does
not respond.  The mouse still works well enough
to end the kde session.
Comment 9 jos poortvliet 2007-06-03 18:56:46 UTC
I can't reproduce this. Kcontrol crashes, but then nothing happens (besides the kde crash handler showing up).

I suspect it could be something in your configuration. You could try to mv the kwin config file (~/.kde/share/config/kwinrc or something) to a new file, and re-try. I expect no crash ;-)

Maybe then Lubos might want the config file which causes a crash, though I'm not sure of that - he might also want to spend his time elsewhere.
Comment 10 Lubos Lunak 2007-06-03 19:59:44 UTC
Add the run applet(the small command line) to your panel before the crash (the small command line). After the crash it should be able to focus it with the mouse and enter 'kwin' there - that should start another kwin and make you able to get the backtrace of the kwin crash.
Comment 11 thomas 2007-06-04 03:10:41 UTC
I moved kwinrc to a place that KDE wouldn't look for it.
I am still able to crash the window manager or the panel with
pkill -11 <name of some app>, for example, konqueror,
k3b, kwifimanager.  When kwin crashes, I get at least
two (I've seen three) crash dialogs.
Comment 12 Lubos Lunak 2007-07-17 10:57:52 UTC
I need the backtrace from the crash dialog, otherwise there's no way to help.
Comment 13 Bram Schoenmakers 2007-07-17 12:11:31 UTC
Please read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports if you want to reopen this bug.