public inbox for
help / color / mirror / Atom feed
From: Markus Hoenicka <>
Cc: paul <>
Subject: Re: Xserver corresponds to display :1.0 instead of :0.0
Date: Fri, 16 Oct 2015 07:10:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

At 2015-10-16 07:41, paul was heard to say:
> I have a very simple ~/.startxwinrc:
>    xrdb -load $HOME/.Xresources
>    xterm -display :0.0 # xterm &
>    exec sleep infinity
> Recently, I found that the xterm wasn't launching.  I googled, read
> some cygwin threads about X authorities, but have to admit, I have a
> lot to learn about X windows.  Anyway, since I could open an xterm by
> right clicking on the Cygwin/Xserver:1.0 app in the notification area
> of Windows 7, I sneakily (OK, it wasn't the craftiest thing in the
> world) echo'd $DISPLAY.  Lo, it was 1.0, and the following works fine:
>    xterm -display :1.0 &
> Yes, I know it says 1.0 in the tip for the Cygwin/Xserver:1.0 app, but
> I didn't actually look at that detail until now, as I'm posting.
> A google for the following doesn't turn up anything:
>    cygwin xterm "-display :0.0" "display :1.0"
> I'm wondering if this was a planned change in how X-windows works or
> if something is awry with my setup, causing a server with display :0.0
> to fail, and making go to :1.0.  I did a browse of the cygin announce
> list on gmane (since the X-windows announce list is now obsolete), but
> no joy.  And I would have expected anything to show up in my google
> search.
> Can anyone point me to the description of this change?  If it is not a
> deliberate change, what would be a good approach to troubleshoot it?
> I have a file ~/.xsession-errors, but it is dated 2015-09-16, and I've
> used X-windows plenty since then.


you may have a leftover lock file from a crashed X session. Check if 
there is a /tmp/.X0-lock (IIRC) before you start your X server.


Markus Hoenicka
AQ score 38

Unsubscribe info:
Problem reports:

  reply	other threads:[~2015-10-16  7:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16  5:43 paul
2015-10-16  7:10 ` Markus Hoenicka [this message]
2015-10-17  4:40   ` paul

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