Bug 78664

Summary: MultiHead / Xinerama wrong window placement/size for old X-Apps
Product: [Plasma] kwin Reporter: Alexander Schanz <Alexander.Schanz>
Component: xineramaAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed In:

Description Alexander Schanz 2004-03-29 13:28:30 UTC
Version:            (using KDE KDE 3.2.1)
Installed from:    Debian testing/unstable Packages

We are using Nvidia NView with two 1600x1200 Monitors. 

KWin is correctly identifying two screens and you can select to enable or disable multi Monitor virtual desktop support and indeed this has an effect on all ‘modern’ X-Apps. 
 
 However we have quite some old closed source X-APPS which think that the world is flat and all Monitors have to be 4:3. When we start these apps under KDE 3.2.1 the maximize button is missing and they believe that the screen is 3200x1600 and show extreme distortion. 
 
Under KDE 3.1.5 this was different an we could use the old applications.

 Selecting ‘enable multi monitor virtual desktop’ support is not helping a lot. While the apps now start their Windows centred to the Display 1 (or whatever you have selected in the Display dialog) the maximize button is still missing and the display is distorted. 
 
 While playing with the settings I realized that if you enable the virtual desktop support the identify displays button shows a strange behaviour. The Logo for Display 2 is displayed in the upper left corner of display 1 while the display 1 logo is centred in display 1. 
 
 I assume that there is a difference Between KDE 3.1.5 and KDE 3.2.1 in the way old X-Apps receive their information about the screen geometry.
Comment 1 William Leese 2004-04-11 22:00:58 UTC
Confirming the same behavior with regard to the "Identify Screen" functionality on CVS as of yesterday (11th of April).
Comment 2 Lubos Lunak 2006-04-28 19:01:40 UTC
If the application's window contents are distored, it's the application's fault, I don't see how the window manager could affect that in any way.