Bug 134785

Summary:	KWin crashes with dualhead xinerama when performing various Firefox operations.
Product:	[Plasma] kwin	Reporter:	Stefán Freyr Stefánsson <stefan.freyr>
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Stefán Freyr Stefánsson 2006-09-28 15:37:02 UTC

Version:            (using KDE KDE 3.5.4)
Installed from:    Ubuntu Packages
OS:                Linux

I have a dualhead setup using Xinerama on Kubuntu with the KDE 3.5.4 packages.

I've been experiencing KWin crashes every once in a while and recently discovered that it seems to happen when I am doing things in Firefox.

Now, for example, KWin has crashed (so no titlebars, no kicker and generally no way of doing anything except close everything, log out and log back in). In this particular case I was switching between tabs in Firefox (using the mouse, clicking on a new tab).

One question: is there any way of getting kwin back up again without closing everything and logging out? I hate to say it but this is possible in Windows when explorer crashes.

Following you can find the "stacktrace" that was reported by the crash window that pops up. I'm not sure if it helps but here it is anyways:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/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)
(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 -1231903040 (LWP 5656)]
(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  0xb67b1bdf in KWinInternal::Client::screen ()
   from /usr/lib/libkdeinit_kwin.so
#7  0xb67ecdce in KWinInternal::Workspace::activateNextClient ()
   from /usr/lib/libkdeinit_kwin.so
#8  0xb67fb0be in KWinInternal::Workspace::workspaceEvent ()
   from /usr/lib/libkdeinit_kwin.so
#9  0xb67fb114 in KWinInternal::Application::x11EventFilter ()
   from /usr/lib/libkdeinit_kwin.so
#10 0xb71e0457 in qt_set_x11_event_filter () from /usr/lib/libqt-mt.so.3
#11 0xb71ed74c in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#12 0xb72074db in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#13 0xb727b947 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#14 0xb727b86a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#15 0xb7261965 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#16 0xb67fca63 in kdemain () from /usr/lib/libkdeinit_kwin.so
#17 0xb7fda4f0 in kdeinitmain () from /usr/lib/kde3/kwin.so
#18 0x0804e173 in ?? ()
#19 0x00000001 in ?? ()
#20 0x0813e308 in ?? ()
#21 0x00000001 in ?? ()
#22 0x00000000 in ?? ()

Comment 1 Lubos Lunak 2006-09-28 17:19:00 UTC

You can get kwin back by adding the run command kicker applet and typing kwin there - it can get focus even without kwin running.


*** This bug has been marked as a duplicate of 131905 ***

Comment 2 Stefán Freyr Stefánsson 2006-09-28 20:08:00 UTC

Thanks for your reply... and sorry that I didn't find that duplicate, don't really understand how that got past me (I did perform a search before posting) :-(

I don't quite get how the run command kicker applet will help me since kicker disappears entirely when this happens?

I did however, follow your advice that you posted for bug 131905 ("In kwinrc, group [Windows] set key SeparateScreenFocus to false as a workaround.") and now it remains to be seen if KWin crashes stop occurring. I'll post back on that bug if I experience this behavior again.