Hi,
On Wed, Apr 8, 2009 at 4:58 PM, Oscar del Rio del...@mie.utoronto.cawrote:
Yiannis Mavroukakis wrote:
More pain from the update..TwinView refuses to behave correctly and spans
windows across the entire desktop..svn_110 BE works perfectly..does anyone
what changed?
(adding
Ewald Ertl wrote:
Hi,
On Wed, Apr 8, 2009 at 4:58 PM, Oscar del Rio del...@mie.utoronto.ca
mailto:del...@mie.utoronto.ca wrote:
Yiannis Mavroukakis wrote:
More pain from the update..TwinView refuses to behave
correctly and spans windows across the entire desktop..svn_110
Hi
On Thu, Apr 9, 2009 at 2:19 PM, John Martin john.m.mar...@sun.com wrote:
Ewald Ertl wrote:
Hi,
On Wed, Apr 8, 2009 at 4:58 PM, Oscar del Rio del...@mie.utoronto.camailto:
del...@mie.utoronto.ca wrote:
Yiannis Mavroukakis wrote:
More pain from the update..TwinView refuses
One of the differences I can see doing this in svn_110 is that I get two
instances of XINERAMA
xdpyinfo -ext XINERAMA
name of display::0.0
version number:11.0
vendor string:Sun Microsystems, Inc.
vendor release number:10503000
maximum request size: 16777212 bytes
motion buffer
John Martin wrote:
What does xdpyinfo -ext XINERAMA report when you enable
the external monitor with xrandr?
Couple of differences I noticed on my system (Ultra 24, Quadro FX 370):
snv_110:
XINERAMA version 1.1 opcode: 153
snv_111:
XINERAMA version 1.1 opcode: 152
SGI-GLX extension
John Martin wrote:
Oscar del Rio wrote:
John Martin wrote:
What does xdpyinfo -ext XINERAMA report when you enable
the external monitor with xrandr?
Couple of differences I noticed on my system (Ultra 24, Quadro FX 370):
snv_110:
XINERAMA version 1.1 opcode: 153
snv_111:
XINERAMA
Oscar del Rio wrote:
After applying the workaround for the Nvidia OpenGL vs Mesa bug, the
xdpyinfo output on both 110 and 111 are identical, but the problem is
still there (as expected, it has nothing to do with GLX)
some more info... as John mentioned, the X server seems to be
advertising
