public inbox for
help / color / mirror / Atom feed
From: Mark Hansen <>
Subject: Re: 64-bit xfree86 failing
Date: Mon, 01 Dec 2014 20:32:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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
> :
> * 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.
> Thanks,
> 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:
Problem reports:

  reply	other threads:[~2014-12-01 20:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-01 16:35 Tim Kingman
2014-12-01 20:32 ` Mark Hansen [this message]
2014-12-01 21:33   ` Tim Kingman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).