closing a window causes kwin to sigsegv

Bug #57782 reported by Andrew Ash
6
Affects Status Importance Assigned to Milestone
KDE Base
Invalid
High
kdebase (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: kwin

Whenever I close a window with the top-right X, click close on a crash handler box, use location->quit on konqueror, or many other things, kwin crashes. The KDE Crash Handler catches it, and provides me with a backtrace. I'm using KDE 3.5.4 and am running XGL with this line in /etc/kde3/kdm/kdmrc:
ServerCmd=/usr/bin/Xgl :0 -fullscreen -ac -accel glx:pbuffer -accel xv:fbo

Here is my Xorg version:
$ Xorg -version

X Window System Version 7.0.0
Release Date: 21 December 2005
X Protocol Version 11, Revision 0, Release 7.0
Build Operating System:Linux 2.6.15.7 i686
Current Operating System: Linux Dell8400Kubuntu 2.6.15-26-686 #1 SMP PREEMPT Thu Aug 3 03:13:28 UTC 2006 i686
Build Date: 16 March 2006
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Module Loader present
$
==============================
And here is the result of the backtrace:
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1208179008 (LWP 9962)]
(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 0x4103cbdf in KWinInternal::Client::screen ()
   from /usr/lib/libkdeinit_kwin.so
#7 0x41077dce in KWinInternal::Workspace::activateNextClient ()
   from /usr/lib/libkdeinit_kwin.so
#8 0x410860be in KWinInternal::Workspace::workspaceEvent ()
   from /usr/lib/libkdeinit_kwin.so
#9 0x41086114 in KWinInternal::Application::x11EventFilter ()
   from /usr/lib/libkdeinit_kwin.so
#10 0x434e29f7 in qt_set_x11_event_filter () from /usr/lib/libqt-mt.so.3
#11 0x434efcec in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#12 0x43509a7b in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#13 0x4357dee7 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#14 0x4357de0a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#15 0x43563f05 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#16 0x41087a63 in kdemain () from /usr/lib/libkdeinit_kwin.so
#17 0x42dceea2 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#18 0x080483b1 in ?? ()
====================================

By running kwin --replace, I can get back to functioning status again, until I close another window. Hopefully this problem can be resolved soon. At least it's giving me a push to start testing out edgy!

Revision history for this message
Andreas Simon (andreas-w-simon) wrote :

I am not able to reproduce this.

What window decoration do you use? Does the error goes away if you change the decoration (System Settings->Appearance->Window Decorations)?

Revision history for this message
Andrew Ash (ash211) wrote :

I switched from Plastik to Redmond, and still observed the problem. I got an identical backtrace (except the thread number, of course).

Also every time I log in to KDE, I get the KPersonalizer window. Whether I go through the wizard or quit it, KPersonalizer reappears on the next boot (maybe login too, I'm not sure). This could be a related problem or not, I'm not really sure.

I was doing some work compiling some KDE components (RSIBreak) and may have modified system files somehow, though I'm unsure if this is the case.

I realize this isn't a support forum, so don't worry about trying to resolve the issue. I'm just reporting the backtrace in the hopes that if the problem does lie in the system, not my muckings around in it, then it can be prevented for other users.

Revision history for this message
P (p92) wrote :

I also have this on 2 of my desktops since kde 3.5.4
A way to reproduce at will is trying to do a snapshot with ksnapshot in area mode, kwin crashes as soon as the snapshot is taken.

I have submitted upstream and it seems to be a duplicate of another upstream bug with a temporary workaround.

Changed in kdebase:
status: Unconfirmed → Confirmed
Revision history for this message
Andrew Ash (ash211) wrote :

I'm actually not experiencing this problem anymore. The only thing I can think of that I changed was the mouse focus settings, from "click to focus" to "focus under mouse".

Just now I've noticed that by changing it back to "click to focus" I am able to reproduce the crash. Hopefully this information helps fix the bug.

Changed in kdebase:
status: Unknown → Rejected
Revision history for this message
P (p92) wrote :

I am still experiencing this either randomly or by using ksnapshot, though I installed the suggested upstream workaround.

Revision history for this message
P (p92) wrote :

KDE upstream says:
 Additional Comment #11 From Lubos Lunak 2006-09-08 17:37 -------
Invalid means that this is not a KDE bug. Your Kubuntu KDE packages include a 3rd party patch (actually made by me, but still not being officially part of KDE). Kubuntu packagers have been already notified, so you should just upgrade.

but I still see no upgrade for this problem.

Revision history for this message
Andrew Ash (ash211) wrote :

I'm going to go ahead and close this bug I reported since I'm not having problems anymore. If anyone still has this problem, feel free to reopen it.

Changed in kdebase:
status: Confirmed → Rejected
Changed in kdebase:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.