public inbox for
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 :
* 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 ), 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.


Unsubscribe info:
Problem reports:

^ 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).