Bug 121968

Summary:	Kwin incompatibility with DECterm
Product:	[Plasma] kwin	Reporter:	László Taska <laszlo.taska>
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Snapshot before any window manager xwininfo before any window manager Snapshot with wmake xwininfo with wmake Snapshot with kwin xwininfo with kwin Snapshot without any window maneger after kwin xwininfo without any window maneger after kwin xprop for a window which was brought up under kwin

Description László Taska 2006-02-14 18:08:42 UTC

Version: (using KDE KDE 3.5.1)
Installed from: Debian testing/unstable Packages
OS: Linux

I'm working in mixed VMS/Linux environment and I'm using VMS's X terminal
emulator to access VMS nodes. This is called to DECterm. After I upgraded to
kde 3.4.2 it started to behave wrongly. I made some steps to provide better
information (I hope I could).

First I started the X in failsafe mode without any window manager and brought
up a DECterm. The DECTerm's size is 80 columns and 40 rows. In the Decterm I
entered the text "0123456789" more times to indicate the width of the window
and after it I didn't touch the DECterm.

The file decterm_pure.jpeg is a snapshot about the window and
decterm_xwininfo_pure.txt is the output of xwininfo.

After it I started wmaker in my xterm. You can see the snapshot and xwininfo
output in the attachment too. Until this it's still ok.

Then I stopped the wmaker and started kwin as window manager. Here the DECterm
window became a little bit messy (check the snapshot).
- Only 79 columns were displayed but the 80th column was still there I could
type there even it was not displayed. It's interesting that it's hided by the
scrollbar of DECterm.
- an empty, not accessible row appeared at the bottom of the window

Then I stopped the kwin but the DECterm remained messy (check the files
*pure_after_kwin*)

As I interpret the problem kwin sends some message to DECterm and after it
behaves differently. I suspect this because the wrong behaviour's persistent
after starting kwin and independent of kwin is running or not (after it was
started).

I'm expecting to behave DECterm same with kwin as it works with wmaker and as
it worked with kwin before 3.4.2. At this time there was no change in the VMS
environment.

I don't know how to file my snapshots and xwininfo outputs. If you let me know then I'll send them.

Comment 1 László Taska 2006-02-14 18:11:03 UTC

Created attachment 14692 [details]
Snapshot before any window manager

Comment 2 László Taska 2006-02-14 18:11:36 UTC

Created attachment 14693 [details]
xwininfo before any window manager

Comment 3 László Taska 2006-02-14 18:12:08 UTC

Created attachment 14694 [details]
Snapshot with wmake

Comment 4 László Taska 2006-02-14 18:12:44 UTC

Created attachment 14695 [details]
xwininfo with wmake

Comment 5 László Taska 2006-02-14 18:13:16 UTC

Created attachment 14696 [details]
Snapshot with kwin

Comment 6 László Taska 2006-02-14 18:13:40 UTC

Created attachment 14697 [details]
xwininfo with kwin

Comment 7 László Taska 2006-02-14 18:14:17 UTC

Created attachment 14698 [details]
Snapshot without any window maneger after kwin

Comment 8 László Taska 2006-02-14 18:15:04 UTC

Created attachment 14699 [details]
xwininfo without any window maneger after kwin

Comment 9 Lubos Lunak 2006-02-14 18:35:09 UTC

Please attach output from xprop for the window.

Comment 10 László Taska 2006-02-14 18:41:38 UTC

Created attachment 14700 [details]
xprop for a window which was brought up under kwin

Comment 11 László Taska 2006-02-14 18:46:44 UTC

Hi!

I brought up a new window under kwin and run xprop. I've attached to the 
report. Is it enough or you need the xprop for all cases described in the 
report?

Regards (and thanks)
Laszlo


On Tuesday 14 February 2006 18.35, Lubos Lunak wrote:
[bugs.kde.org quoted mail]

Comment 12 Lubos Lunak 2006-02-15 10:55:31 UTC

SVN commit 509608 by lunakl:

Fix setting of minsize used in Client::sizeForClientSize()
if base size is set and minsize is not.
BUG: 121968



 M  +2 -2      geometry.cpp  


--- branches/KDE/3.5/kdebase/kwin/geometry.cpp #509607:509608
@@ -1209,6 +1209,8 @@
         xSizeHint.flags = 0;
     // set defined values for the fields, even if they're not in flags
 
+    if( ! ( xSizeHint.flags & PMinSize ))
+        xSizeHint.min_width = xSizeHint.min_height = 0;
     if( xSizeHint.flags & PBaseSize )
         {
         // PBaseSize is a fallback for PMinSize according to ICCCM 4.1.2.3
@@ -1222,8 +1224,6 @@
         }
     else
         xSizeHint.base_width = xSizeHint.base_height = 0;
-    if( ! ( xSizeHint.flags & PMinSize ))
-        xSizeHint.min_width = xSizeHint.min_height = 0;
     if( ! ( xSizeHint.flags & PMaxSize ))
         xSizeHint.max_width = xSizeHint.max_height = INT_MAX;
     else