Bug 142011

Summary:	Title-bars of windows disappear. Then, unpossible to change the main window.
Product:	[Plasma] kwin	Reporter:	Mathieu Schopfer <mat.schopfer>
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED REMIND
Severity:	crash	CC:	daniel.dumitrache, joe.zweck
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Mathieu Schopfer 2007-02-21 10:36:56 UTC

Version:            (using KDE KDE 3.5.6)
Installed from:    Fedora RPMs
OS:                Linux

I totally normally use my computer when suddenly Kwin crashes. Then, the title-bar of the windows disappears, so I can't close them, I can't reduce them. Note that Kicker is also unusable.
Anyway, the tool-bar doesn't disappear. So I can close each window and restart my computer.


(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(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 -1208628544 (LWP 2510)]
(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)
[KCrash handler]
#6  0x0024b8b2 in KWinInternal::Workspace::updateMinimizedOfTransients ()
   from /usr/lib/libkdeinit_kwin.so
#7  0x0022ef1a in KWinInternal::Client::unminimize ()
   from /usr/lib/libkdeinit_kwin.so
#8  0x0021b983 in KWinInternal::Workspace::resetShowingDesktop ()
   from /usr/lib/libkdeinit_kwin.so
#9  0x00251409 in KWinInternal::Client::manage ()
   from /usr/lib/libkdeinit_kwin.so
#10 0x00224236 in KWinInternal::Workspace::createClient ()
   from /usr/lib/libkdeinit_kwin.so
#11 0x00245b87 in KWinInternal::Workspace::workspaceEvent ()
   from /usr/lib/libkdeinit_kwin.so
#12 0x00237b9e in KWinInternal::Application::x11EventFilter ()
   from /usr/lib/libkdeinit_kwin.so
#13 0x04c8f784 in ?? () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#14 0x04c9ff93 in QApplication::x11ProcessEvent ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#15 0x04cb214b in QEventLoop::processEvents ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#16 0x04d233f0 in QEventLoop::enterLoop ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#17 0x04d232a6 in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#18 0x04d0997f in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#19 0x00238b70 in kdemain () from /usr/lib/libkdeinit_kwin.so
#20 0x08048472 in ?? ()
#21 0x008c4f2c in __libc_start_main () from /lib/libc.so.6
#22 0x080483c1 in ?? ()

Comment 1 jos poortvliet 2007-02-21 12:22:23 UTC

Well, the crash should be fixed, but at least there is a solution for you: start kwin again with the command kwin on a commandline... Without windowmanager it can be dificult to GET to a commandline, tough ;-)

Does alt-F2 still work? Or a button on kicker?

Comment 2 Lubos Lunak 2007-02-22 14:25:33 UTC

The backtrace alone is unsufficient. What are the steps to reproduce the problem?

Comment 3 Mathieu Schopfer 2007-02-23 09:17:12 UTC

Quote : The backtrace alone is unsufficient. What are the steps to reproduce the problem?

Oh, ok. I'm sorry, but I don't know. It seemed to happen reason less, when the micro-processor was too busy. But the problem didn't happen again since two days.

Comment 4 Mathieu Schopfer 2007-02-23 10:25:11 UTC

Well, it just crashed again. I was deleting a rather big file (4.4 GiB, oh what the hell could it be ?) and I tried to open a new window. Kwin crashed at this moment.

Then, I was able to open a command line, but I can't type any text in it. The command Alt+F2 stopped working also.

Comment 5 Lubos Lunak 2007-02-23 11:59:37 UTC

It you add the run command applet to panel, you can type commands there even without KWin running (and launch it again, or some other WM like metacity).

And from the backtrace it's visible that the crash came when you had show desktop activated and opened a new window, but if you cannot provide a way to reproduce the problem I'm afraid I can't help.

Comment 6 Bram Schoenmakers 2007-03-22 20:21:53 UTC

Insufficient info. Please reopen whenever there are steps to reproduce available.

Comment 7 Lubos Lunak 2007-03-23 15:26:37 UTC

Not enough info to reproduce/fix.

Comment 8 Tommi Tervo 2007-04-11 08:22:06 UTC

*** Bug 144060 has been marked as a duplicate of this bug. ***