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

On Mon, Dec 1, 2014 at 3:32 PM, Mark Hansen <> 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
>> )
>> *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.


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: with a
suggestion to run sleep from .startxwinrc. I haven't tried that yet,
but that may be the best option for now.


Unsubscribe info:
Problem reports:

      reply	other threads:[~2014-12-01 21:33 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
2014-12-01 21:33   ` Tim Kingman [this message]

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 \
    --in-reply-to='' \ \ \

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