xfwm4 question regarding window position

[Victor Leschuk]

Hello, 

I found a strange behavior of xfwm4 after reconfiguring display. The
situation is the following: 

1) Open any (gtk, or qt) window. For example a Terminal instance.
2) Make sure it is not maximized and move it to right side of the
screen.
3) Reconfigure display output. There are several situation when the
problem appears: waking up after opening laptop lid, returning from a
full-screen application, etc. The easiest way to reproduce is running
the following script: 

$ cat screen_test.sh 
#!/bin/bash
xrandr --output LVDS1 --off
xrandr --output LVDS1 --auto

4) The window will move from right side of the screen to the left.

I thought this maybe a problem in X itself however with different
window manager (fluxbox) the problem doesn't appear. Enabling/disabling
compositing doesn't affect problem.

Here are some details about my system: 

[del at del-arch ~]$ pacman -Qi xfwm4|grep Version
Version        : 4.6.2-1
[del at del-arch ~]$ uname -rm
2.6.35-ARCH x86_64
[del at del-arch ~]$ lspci|grep -i vga
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series
Chipset Integrated Graphics Controller (rev 07) [del at del-arch ~]$ lspci
-vnn|grep -i vga 00:02.0 VGA compatible controller [0300]: Intel
Corporation Mobile 4 Series Chipset Integrated Graphics Controller
[8086:2a42] (rev 07) (prog-if 00 [VGA controller]) [del at del-arch ~]$
pacman -Qi xfwm4|grep Version Version        : 4.6.2-1 [del at del-arch
~]$ uname -rm 2.6.35-ARCH x86_64
[del at del-arch ~]$ lspci -vnn|grep -i vga
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4
Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
(prog-if 00 [VGA controller]) 
[del at del-arch ~]$ X -version
X.Org X Server 1.8.1.902 (1.8.2 RC 2)

I will check if the situation can be reproduced at my work machine
where I am running Fedora 13 and xfwm4-4.6.2-1.fc13.x86_64 with nvidia
card and proprietary driver.

But any advice of how this can be localized and investigated in order to
place a correct bug report (maybe this is not even a bug) is highly
 appreciated. 

Thank you.

--

Victor