Created attachment 317745 [details]
Description of problem:
I use DWM window manager (http://dwm.suckless.org), which draws a one-pixel border around client windows with XSetWindowBorder. The border around the current window with focus is a different color from those around other windows. When I upgraded to Fedora 9 and the new xorg-x11-drv-vmware, the borders no longer refresh when (re)drawn. Rather, I have to switch to a different (WinXP) host application and then back to VMware to see the updated borders. I don't see this problem when using xorg-x11-drv-vesa.
Version-Release number of selected component (if applicable):
Host OS: Windows XP SP3
Display Adaptor: Mobile Intel 945GM
VMware Workstation 6.0.5 build-109488
How reproducible: 100%
Steps to Reproduce:
2. launch two xterms and switch between them
3. switch to host app and then back to VMware
In step 2, the borders do not appear. After step 3, the borders appear, but do not update.
The window borders should update as they are drawn and as the focus changes from window to window.
This did not happen with xorg-x11-drv-vmware-10.15.2-1.fc8, but that version is no longer compatible with my xorg-x11-server, probably because of changes relating to libpciaccess.
Created attachment 317746 [details]
Curious. This is unlikely to be the video driver's fault though, the driver has no explicit knowledge of border painting.
The only thing I can think of that might have affected this would be the PaintWindow rewrite since 1.3. Do you see this in a normal (hardware-backed) X server?
Sorry, I don't have a hardware-backed setup handy at the moment. However, I don't see this behavior when I switch to the the VESA driver (xorg-x11-drv-vesa-2.0.0-1.fc9.i386) while keeping the rest of the environment constant.
Created attachment 319145 [details]
Xorg.0.log in the (working) Fedora 8 setup
This is included for contrast with the one from the current non-working setup. Diffing the two, I notice much difference in the PCI info.
Created attachment 319146 [details]
Output of xdpyinfo in the (non-working) Fedora 9 setup
Created attachment 319149 [details]
Output of xdpyinfo in the (working) Fedora 8 setup
This is included for contrast with the one from the current non-working setup. Diffing the two, I find that the current setup has fewer visuals.
Also possibly relevant: my new, Fedora 9, setup no longer detects the default display mode of 1680x1050 ("no mode of this name"). I had to include modelines in xorg.conf to obtain the correct resolution. This was not necessary in my old, Fedora 8, setup.
I downgraded to xorg-x11-server-Xorg-22.214.171.124-47.fc8.i386 and xorg-x11-drv-vmware-10.15.2-1.fc8.i386 and the system is behaving properly again.
This behavior also occurs with VMware Workstation 6.5.1 build-126130. I'm also beginning to suspect the PaintWindow rewrite in the X server.
I upgraded to Fedora 10, with xorg-x11-server-Xorg-1.5.3-5.fc10.i386, and this behavior still occurs.
I upgraded to xorg-x11-server-Xorg-1.5.3-15.fc10.i386, libX11-1.1.5-2.fc10.i386, and VMware 6.5.2 build-156735, but this behavior still occurs.
I upgraded to xorg-x11-server-Xorg-126.96.36.1991-1.fc11.i586,
libX11-1.2.1-2.fc11.i586, and xorg-x11-drv-vmware-10.16.0-3.fc11.i586, but this behavior still occurs.
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command
yum upgrade --enablerepo='*-updates-testing'
Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .
Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.
If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
I upgraded to xorg-x11-server-Xorg-1.6.4-0.1.fc11.i586,
libX11-1.2.2-1.fc11.i586, xorg-x11-drv-vmware-10.16.0-3.fc11.i586, and VMware Workstation 6.5.3 build-185404, on NVIDIA Quadro 290 with 256 MB, but this
behavior still occurs.
I upgraded to Fedora 12, but this behavior still occurs.
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.