public inbox for
help / color / mirror / Atom feed
From: Mark Hansen <>
Subject: Re: Problem launching XTerm on new Cygwin installation
Date: Fri, 07 Mar 2014 22:04:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 3/7/2014 1:49 PM, Thomas Dickey wrote:
> On Fri, Mar 07, 2014 at 11:57:20AM -0800, Mark Hansen wrote:
>> I just installed the 64-bit version of Cygwin on both a desktop PC and a laptop PC.
>> On the desktop, everything worked as expected without problems. On the laptop, I
>> have the following problems:
>> When I launch a shell window, I get the following error:
>> Your group is currently "mkgroup". This indicates that neither your gid nor your pgsid is in /etc/group.
> (I don't know about this one)
>> Also, when I try to launch an XTerm, I get the following message in the XTerm window for
>> just a few seconds and then the window goes away:
>> /cygdrive/c/Apps/cygwin/bin/xterm: Could not exec XTERM_SHELL=XTERM_SHELL=: No such file or directory
> yes, that's a bug which surfaced in #301, thought it was gone in #302, and _should_ be gone in #303
> (from yesterday)
>> I'm starting the XWin Server using a shortcut with the following:
>> C:\Apps\cygwin\bin\run.exe
>>         /usr/bin/bash.exe -l -c
>>         "/usr/bin/startxwin.exe -- -emulate3buttons -multiwindow -clipboard -swcursor"
>> I'm starting the XTerm using a shortcut with the following:
>> C:\Apps\cygwin\bin\run.exe
>>         -p /usr/X11R6/bin xterm +tb -sb -sl 5000 -display -ls /bin/zsh -l
> I'd try putting "-e" before the "/bin/zsh", which moves it away from the bug noted.
> (actually, the trailing "-l" doesn't look right either)

Thanks. I think the -l was to cause a login shell, but I see now that is what the -ls
argument does. Since I removed the shell argument ("/bin/zsh -l") it is now working.
I'm getting the shell I want, I suspect, because that is the shell mentioned in the
/etc/passwd file for my user.

As a result, it is working so I'll leave it alone.

> fwiw, when I compile #301, #302 and #303 for Cygwin, I don't see the bug.
> However, I was able to analyze it on Linux with valgrind...

Well, I downloaded the Cygwin installation for my desktop last week, and downloaded
the Cygwin for my laptop yesterday. I guess the bug could have been introduced between
those times?

Thanks for your help!

Unsubscribe info:
Problem reports:

  reply	other threads:[~2014-03-07 22:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-07 19:57 Mark Hansen
2014-03-07 21:50 ` Thomas Dickey
2014-03-07 22:04   ` Mark Hansen [this message]
2014-03-07 22:12     ` Thomas Dickey
2014-03-07 23:37       ` Mark Hansen
2014-03-08  0:36         ` Thomas Dickey
2014-03-08  0:43           ` Mark Hansen
2014-03-07 22:00 ` Mark Hansen
2014-03-16 18:48 ` Mark Hansen

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