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

[Alexander Pokluda <apokluda at gmail dot com>]

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/