Can't use -fullscreen with two screens - XWin fatal server error: InitOutput - Couldn't add screen 1

Can't use -fullscreen with two screens - XWin fatal server error: InitOutput - Couldn't add screen 1

[Alexander Pokluda]

[-- Attachment #1: Type: text/plain, Size: 950 bytes --]

Hi,

When I give the -fullscreen argument to XWin using two screens, a
window pops up with the error

InitOutput - Couldn't add screen 1

and

Aborted (core dumped)

is printed in the bash shell.

The following command lines work perfectly:

XWin -fullscreen -screen 0 @2 -query 10.3.22.73
XWin +xinerama -screen 0 @2 -screen 1 @1 -query 10.3.22.73

but the command line

XWin +xinerama -fullscreen -screen 0 @2 -screen 1 @1 -query 10.3.22.73

produces the errors described above. I've attached the log and core
dump files that were produced when running this command. Placing the
-fullscreen argument at different locations in the command line, or
using -fullscreen once for each -screen argument, seems to have
slightly different effects (I got a segmentation fault once for
instance), but the result is more or less the same. Can anyone tell me
if it is possible to use two screens and have them both fullscreen?

Thanks in advance for your help!

[-- Attachment #2: XWin.exe.stackdump --]
[-- Type: application/octet-stream, Size: 1086 bytes --]

Stack trace:
Frame     Function  Args
0028C1E8  76FF1184  (000002E0, 0000EA60, 00000000, 0028C30C)
0028C1FC  76FF1138  (000002E0, 0000EA60, 000000A4, 0028C2F0)
0028C30C  610C6013  (00000000, 000002E0, 0028C32C, 00000000)
0028C3EC  610C2CA7  (00000000, 00000000, 00000000, 00000000)
0028C43C  610C30BB  (00000A68, 0028C464, 0028C44C, 005AC960)
0028C4FC  610C31E1  (00000A68, 00000006, 0028C52C, 610C3285)
0028C50C  610C321C  (00000006, 0028CE80, 00000000, 00000000)
0028C52C  610C3285  (005AC960, 0028C548, 0028C54C, 005782F7)
0028C53C  0057B010  (005DBB8C, 0028C558, 0028C56C, 00583D13)
0028C54C  005782F7  (005DDDF0, 0000000B, 0028DA4C, 0028C5BC)
0028C56C  00583D13  (0000000B, 0028C5BC, 00000000, 00000001)
0028C65C  610291B4  (000002E0, 0000EA60, 000000A4, 0028C750)
0028C76C  610C60ED  (65736165, 0028C834, 0000001C, 76B8501E)
0028C85C  610288D9  (0028C948, 0028FF30, 0028C998, 0028C91C)
0028C880  77956AC9  (0028C948, 0028FF30, 0028C998, 0028C91C)
0028C930  77956A9B  (0028C948, 0028C998, 0028C948, 0028C998)
End of stack trace (more stack frames may be present)

[-- Attachment #3: XWin.0.log --]
[-- Type: application/octet-stream, Size: 2054 bytes --]

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.9.3.0 (10903000)
Package version 1.9.3-2 built 2011-01-05

XWin was started with the following command line:

XWin +xinerama -fullscreen -screen 0 @2 -screen 1 @1 -query 10.3.22.73 

ddxProcessArgument - Initializing default screens
winInitializeScreenDefaults - primary monitor w 1680 h 1050
winInitializeDefaultScreens - native DPI x 96 y 96
winInitializeScreens - 1
winInitializeScreen - 0
ddxProcessArgument - screen - Found Valid ``@Monitor'' = 2 arg
winInitializeScreens - 2
winInitializeScreen - 1
ddxProcessArgument - screen - Found Valid ``@Monitor'' = 1 arg
[  1600.102] (II) xorg.conf is not supported
[  1600.102] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
[  1600.102] LoadPreferences: /cygdrive/c/Users/alpokluda/.XWinrc not found
[  1600.102] LoadPreferences: Loading /etc/X11/system.XWinrc
[  1600.102] LoadPreferences: Done parsing the configuration file...
[  1600.102] winGetDisplay: DISPLAY=:0.0
[  1600.102] winDetectSupportedEngines - Windows NT/2000/XP
[  1600.133] winDetectSupportedEngines - DirectDraw installed
[  1600.133] winDetectSupportedEngines - Allowing PrimaryDD
[  1600.133] winDetectSupportedEngines - DirectDraw4 installed
[  1600.195] winDetectSupportedEngines - Returning, supported engines 0000001f
[  1600.195] winSetEngine - Using Shadow DirectDraw NonLocking
[  1600.195] winScreenInit - Using Windows display depth of 32 bits per pixel
[  1600.445] winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff
[  1600.445] Screen 0 added at virtual desktop coordinate (1680,0).
[  1600.445] winSetEngine - Using Shadow DirectDraw NonLocking
[  1600.445] winScreenInit - Using Windows display depth of 32 bits per pixel
[  1601.771] winAllocateFBShadowDDNL - Could not set cooperative level: 88760245
[  1601.771] winFinishScreenInitFB - Could not allocate framebuffer
[  1601.771] winScreenInit - winFinishScreenInit () failed
[  1601.771] 
Fatal server error:
[  1601.771] InitOutput - Couldn't add screen 1

[-- Attachment #4: Type: text/plain, Size: 223 bytes --]

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/

Re: Can't use -fullscreen with two screens - XWin fatal server error: InitOutput - Couldn't add screen 1

[Jon TURNEY]

On 18/02/2011 17:52, Alexander Pokluda wrote:
> When I give the -fullscreen argument to XWin using two screens, a
> window pops up with the error
> 
> InitOutput - Couldn't add screen 1
> 
> and
> 
> Aborted (core dumped)
> 
> is printed in the bash shell.
> 
> The following command lines work perfectly:
> 
> XWin -fullscreen -screen 0 @2 -query 10.3.22.73
> XWin +xinerama -screen 0 @2 -screen 1 @1 -query 10.3.22.73
> 
> but the command line
> 
> XWin +xinerama -fullscreen -screen 0 @2 -screen 1 @1 -query 10.3.22.73
> 
> produces the errors described above. I've attached the log and core
> dump files that were produced when running this command. Placing the
> -fullscreen argument at different locations in the command line, or
> using -fullscreen once for each -screen argument, seems to have
> slightly different effects (I got a segmentation fault once for
> instance), but the result is more or less the same. Can anyone tell me
> if it is possible to use two screens and have them both fullscreen?

This is an interesting problem, I don't think anyone has tried that
configuration before, and it exposes a limitation I wasn't previously aware of :-)

> [  1601.771] winAllocateFBShadowDDNL - Could not set cooperative level: 88760245
> [  1601.771] winFinishScreenInitFB - Could not allocate framebuffer
> [  1601.771] winScreenInit - winFinishScreenInit () failed
> [  1601.771] Fatal server error: InitOutput - Couldn't add screen 1

Error 88760245 is DDERR_EXCLUSIVEMODEALREADYSET

At the moment, XWin always puts exclusive full-screen windows on monitor 0, so
-fullscreen is only practically useful with a single X screen window, and this
isn't going to work the way you want to.  I think it could be made to work
that way, but from a brief investigation it would require using a later
version of the DirectX API than it's currently written to in order to put
full-screen windows other than on monitor 0.

For the moment, I think I shall add a fix so it doesn't crash when given this
combination of options, and document this limitation to -fullscreen.

As a workaround, I'd suggest you use -nodecoration instead of -fullscreen,
which should be almost as good.

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/

Re: Can't use -fullscreen with two screens - XWin fatal server error: InitOutput - Couldn't add screen 1

[Alexander Pokluda]

As a work around, I have been using -nodecoration and setting my
Windows taskbar to auto hide. This does exactly what I want and I
think it is just as good as -fullscreen.

Thanks for your help Jon.

-Alex

On Sat, Mar 5, 2011 at 12:50 PM, Jon TURNEY <jon.turney@dronecode.org.uk> wrote:
>
> On 18/02/2011 17:52, Alexander Pokluda wrote:
> > When I give the -fullscreen argument to XWin using two screens, a
> > window pops up with the error
> >
> > InitOutput - Couldn't add screen 1
> >
> > and
> >
> > Aborted (core dumped)
> >
> > is printed in the bash shell.
> >
> > The following command lines work perfectly:
> >
> > XWin -fullscreen -screen 0 @2 -query 10.3.22.73
> > XWin +xinerama -screen 0 @2 -screen 1 @1 -query 10.3.22.73
> >
> > but the command line
> >
> > XWin +xinerama -fullscreen -screen 0 @2 -screen 1 @1 -query 10.3.22.73
> >
> > produces the errors described above. I've attached the log and core
> > dump files that were produced when running this command. Placing the
> > -fullscreen argument at different locations in the command line, or
> > using -fullscreen once for each -screen argument, seems to have
> > slightly different effects (I got a segmentation fault once for
> > instance), but the result is more or less the same. Can anyone tell me
> > if it is possible to use two screens and have them both fullscreen?
>
> This is an interesting problem, I don't think anyone has tried that
> configuration before, and it exposes a limitation I wasn't previously aware of :-)
>
> > [  1601.771] winAllocateFBShadowDDNL - Could not set cooperative level: 88760245
> > [  1601.771] winFinishScreenInitFB - Could not allocate framebuffer
> > [  1601.771] winScreenInit - winFinishScreenInit () failed
> > [  1601.771] Fatal server error: InitOutput - Couldn't add screen 1
>
> Error 88760245 is DDERR_EXCLUSIVEMODEALREADYSET
>
> At the moment, XWin always puts exclusive full-screen windows on monitor 0, so
> -fullscreen is only practically useful with a single X screen window, and this
> isn't going to work the way you want to.  I think it could be made to work
> that way, but from a brief investigation it would require using a later
> version of the DirectX API than it's currently written to in order to put
> full-screen windows other than on monitor 0.
>
> For the moment, I think I shall add a fix so it doesn't crash when given this
> combination of options, and document this limitation to -fullscreen.
>
> As a workaround, I'd suggest you use -nodecoration instead of -fullscreen,
> which should be almost as good.
>
> --
> Jon TURNEY
> Volunteer Cygwin/X X Server maintainer

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/