public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Mark Hansen <meh@winfirst.com>
To: cygwin-xfree@cygwin.com
Subject: Re: Problem launching XTerm on new Cygwin installation
Date: Fri, 07 Mar 2014 22:00:00 -0000	[thread overview]
Message-ID: <531A4180.9070509@winfirst.com> (raw)
In-Reply-To: <531A24A0.7010400@winfirst.com>

On 3/7/2014 11:57 AM, 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.
>
> 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
>
> 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 127.0.0.1:0.0 -ls /bin/zsh -l
>
> I've searched for this XTERM_SHELL error, but can't find anything. Can anybody help me?
>
> Thanks,

Well, I did the following two things:

1. I changed the group id for my entry in the /etc/passwd file from 10530 (or whatever
that value was) to 545 (Users) and the first error went away.

2. I changed the shortcut I use to launch the XTerms and removed the shell name at
the end, so it now looks like this:

C:\Apps\cygwin\bin\run.exe
           -p /usr/X11R6/bin xterm +tb -sb -sl 5000 -display 127.0.0.1:0.0 -ls

and now the XTerm is started without any errors.

I guess it's working now, but I'm curious why these problems happened on the laptop
installation and not on the desktop installation.

Especially why the XTerm launch command had to change. The one I showed first I've
been using for years without problems. I don't remember how I came up with it now,
but I remember spending a lot of time putting that together. Also, that original
launch command is working on my other PC (the desktop) as well as my other machines
running the 32-bit version of Cygwin.

Thanks for any feedback/clarification.



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


  parent reply	other threads:[~2014-03-07 22:00 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
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 [this message]
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=531A4180.9070509@winfirst.com \
    --to=meh@winfirst.com \
    --cc=cygwin-xfree@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

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