Bug 53323

Summary:	kwin crashes when the desktop menu is enabled and a window is unshaded
Product:	[Plasma] kwin	Reporter:	Duke <duke>
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	trace of the crash another trace of the crash

Description Duke 2003-01-23 16:39:30 UTC

Version:           0.95 (using KDE KDE 3.0.5)
Installed from:    Gentoo Packages
Compiler:          gcc 2.95.3 20010315 (release)
OS:          Linux

After enabling the Desktop Menu from the Control Center, I move my cursor over a shaded window (focus follows mouse, window unshades on mouseover), and kwin crashes.  It's a very reliable bug, happens every time.  If a window isn't shaded, I can shade it, then unshade it, and kwin crashes immediatly.    I tried working in kde as usual, without unshading windows to see if anything else would cause the crash, but havn't been able to reproduce the crash with out unshading a window.

After the crash, all my windows remain on screen, as does the Desktop Menu.  I open File -> Run on the Desktop Menu, and run kwin (I have to open File -> Run twice in order to get the Run dialog box to come up - don't know why, another bug maybe?)  I can then either crash kwin again, or disable the Desktop Menu in the Control Center.

I'm running the Gentoo Linux distribution, which is completely up to date as of this report.  Linux Kernel 2.4.20, XFree86 4.2.1, glibc 2.2.5.

I saved 4 copies of the crash trace, I'll submit a couple of them.

Comment 1 Duke 2003-01-23 16:40:34 UTC

Created attachment 794 [details]
trace of the crash

Comment 2 Duke 2003-01-23 16:41:18 UTC

Created attachment 795 [details]
another trace of the crash

Comment 3 Lubos Lunak 2003-04-14 16:48:32 UTC

Assuming that 'Desktop Menu' is the standalone menubar at the top of the desktop, I cannot 
reproduce this problem with KDE3.1. Please try again with KDE3.1 and reopen this bugreport if 
the problem remains.