Bug 163318

Summary:	KWin crashes when right-click on column headers in KTorrent
Product:	[Plasma] kwin	Reporter:	Shrikant Khare <shrikantkhare>
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	crash
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	.xsession-errors

Description Shrikant Khare 2008-06-06 00:26:43 UTC

Version:           4.0.81 (using Devel)
Installed from:    Compiled sources
Compiler:          gcc 4.2.1 gcc (GCC) 4.2.1 (SUSE Linux 10.3)
OS:                Linux

Using KDE 4.0.81 from openSUSE 10.3 KDE:/UNSTABLE:/ (Updated 06/06/2008)

In System Setting, after enabling desktop affects, KWin crashes (causing a XServer crash in turn) when a right-click is done on the Column Header in KTorrent. Similar crashes occur when right-clicking any empty space in Dolphin.

This does not happen if XRender is chosen (instead of OpenGL) in the Desktop Affects->Advanced Options->Compositing Type.

Comment 1 Shrikant Khare 2008-06-06 00:28:57 UTC

Created attachment 25144 [details]
.xsession-errors

This is the .xsession-errors file created when KDE crashed

Comment 2 Lubos Lunak 2008-06-06 17:25:32 UTC

There is no mention of KWin crash in the log file, are you sure it's KWin crashing? Were there any other problems before you launched KTorrent? This looks like X/drivers bug.

Comment 3 Shrikant Khare 2008-06-08 08:05:34 UTC

I don't think it is a X/drivers bug because I have been using XGL/Compiz for a long time and it never crashes.

I have no idea how to find out where the problem lies because as soon as I right-click, XServer crashes, there is not even a backtrace. This is a problem since I have started using KDE 4.0. The only workaround I have found is to change OpenGL to XRender in the advanced options.

If you have any suggestion on what I might do to trace the problem, tell me.

Thanks

Comment 4 Lubos Lunak 2008-06-10 16:34:47 UTC

If X server crashes, than it is presumably an X problem -> please report to them.