public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
* Re: 64-bit xfree86 failing
@ 2014-12-01 16:35 Tim Kingman
  2014-12-01 20:32 ` Mark Hansen
  0 siblings, 1 reply; 3+ messages in thread
From: Tim Kingman @ 2014-12-01 16:35 UTC (permalink / raw)
  To: cygwin-xfree

I see the same issue, and it looks like this is because I have an
empty (commented-out) ~/.startxwinrc

Removing this file causes X to open and start an xterm, probably
because it broke several of the new rules in
https://cygwin.com/ml/cygwin-xfree/2014-11/msg00029.html :
* User-defined ~/.startxwinrc files must now be executable, the final
command therein must be run in the foreground, and that command's
exiting will end the X session, just like with startx and ~/.xinitrc
or ~/.Xclients.

This causes another problem for me because my .bashrc calls startxwin
to make sure I always have an X server running ( per
http://stackoverflow.com/a/9301966 ), and then I get caught in a loop
of launching new X servers infinitely (probably from startxwin now
finding a new DISPLAY, and if I specify both :0 and -silent-dup-error,
XWin still writes an error to the console that display 0 is already
active, and displays a Windows dialog with an error about not being
able to move XWin.0.log to XWin.0.log.old ).

I'll keep playing with this to see if I can come up with a solution to
duplicate my previous behavior: Any new bash shell makes sure that X
is running, with no X apps running, and only one X is running, and new
shells don't pop up any "display already exists" errors.

Thanks,
Tim

--
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/


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: 64-bit xfree86 failing
  2014-12-01 16:35 64-bit xfree86 failing Tim Kingman
@ 2014-12-01 20:32 ` Mark Hansen
  2014-12-01 21:33   ` Tim Kingman
  0 siblings, 1 reply; 3+ messages in thread
From: Mark Hansen @ 2014-12-01 20:32 UTC (permalink / raw)
  To: cygwin-xfree

On 12/1/2014 8:35 AM, Tim Kingman wrote:
> I see the same issue, and it looks like this is because I have an
> empty (commented-out) ~/.startxwinrc
>
> Removing this file causes X to open and start an xterm, probably
> because it broke several of the new rules in
> https://cygwin.com/ml/cygwin-xfree/2014-11/msg00029.html :
> * User-defined ~/.startxwinrc files must now be executable, the final
> command therein must be run in the foreground, and that command's
> exiting will end the X session, just like with startx and ~/.xinitrc
> or ~/.Xclients.
>
> This causes another problem for me because my .bashrc calls startxwin
> to make sure I always have an X server running ( per
> http://stackoverflow.com/a/9301966 ), and then I get caught in a loop
> of launching new X servers infinitely (probably from startxwin now
> finding a new DISPLAY, and if I specify both :0 and -silent-dup-error,
> XWin still writes an error to the console that display 0 is already
> active, and displays a Windows dialog with an error about not being
> able to move XWin.0.log to XWin.0.log.old ).
>
> I'll keep playing with this to see if I can come up with a solution to
> duplicate my previous behavior: Any new bash shell makes sure that X
> is running, with no X apps running, and only one X is running, and new
> shells don't pop up any "display already exists" errors.
>
> Thanks,
> Tim
>

Tim,

Are you opposed to having the X Server start when you log into the Windows machine?
This is what I do and it works well. The X server is always running when I need it.

I created a desktop shortcut with the following command:

C:\Apps\cygwin\bin\run.exe /usr/bin/bash.exe -l -c "/usr/bin/startxwin.exe -- -emulate3buttons 100 -multiwindow -clipboard -swcursor"

and then just place that shortcut in the "programs -> startup" start menu folder.





--
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/


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: 64-bit xfree86 failing
  2014-12-01 20:32 ` Mark Hansen
@ 2014-12-01 21:33   ` Tim Kingman
  0 siblings, 0 replies; 3+ messages in thread
From: Tim Kingman @ 2014-12-01 21:33 UTC (permalink / raw)
  To: cygwin-xfree

On Mon, Dec 1, 2014 at 3:32 PM, Mark Hansen <meh@winfirst.com> wrote:
> On 12/1/2014 8:35 AM, Tim Kingman wrote:
>>
>> *snip*
>> my .bashrc calls startxwin
>> to make sure I always have an X server running ( per
>> http://stackoverflow.com/a/9301966 )
>> *snip*
>>
>> I'll keep playing with this to see if I can come up with a solution to
>> duplicate my previous behavior: Any new bash shell makes sure that X
>> is running, with no X apps running, and only one X is running, and new
>> shells don't pop up any "display already exists" errors.
>>
>> Thanks,
>> Tim
>>
>
> Tim,
>
> Are you opposed to having the X Server start when you log into the Windows
> machine?
> This is what I do and it works well. The X server is always running when I
> need it.
>
> I created a desktop shortcut with the following command:
>
> C:\Apps\cygwin\bin\run.exe /usr/bin/bash.exe -l -c "/usr/bin/startxwin.exe
> -- -emulate3buttons 100 -multiwindow -clipboard -swcursor"
>
> and then just place that shortcut in the "programs -> startup" start menu
> folder.
>

Mark,

That's probably what I should be doing to start the X server. That
would avoid the dup-error warnings, and I can manually restart the
server if it dies.

But I think this method won't work with xinit 1.3.4, because
startxwin.bat from xinit 1.3.4 no longer leaves the X server running
after the last command in .startxwinrc (or the default xterm) exits.
Another request for this:
https://cygwin.com/ml/cygwin-xfree/2014-11/msg00039.html with a
suggestion to run sleep from .startxwinrc. I haven't tried that yet,
but that may be the best option for now.

Thanks,
Tim

--
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/


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2014-12-01 21:33 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-12-01 16:35 64-bit xfree86 failing Tim Kingman
2014-12-01 20:32 ` Mark Hansen
2014-12-01 21:33   ` Tim Kingman

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).