X Server no longer launches urxvtc-X

X Server no longer launches urxvtc-X

[Jay Goldman]

I have the following menu items in my .XWinrc:
       Black EXEC  "/bin/urxvtc-X -fg green -bg black   -cr dodgerblue -g 80x40 -e /bin/bash -l -I"
       dodger EXEC  "urxvtc-X -fg white -bg dodgerblue   -cr blue -g 80x42 -e /bin/bash -l -I"

Which have been working for months .

Today I upgraded my cygwin install and all my menu items like the above no longer work.
(as noted above I've tried both simply urxvtc-X and /bin/urxvtc-X
If, however, I open up a command window using rxvt and then enter the above 
Line (by copy and paste) it works fine. 

Note, menu items like:
                Xterm exec "xterm"
Work correctly, 
While menu items such as:
                Notepad exec "notepad"
Do not.
                

Does anyone know what has changed in cygwin and/or cygwinX that would cause this?
Could this be related to the change to the windows working directory?

TIA,
Jay


--
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/

Re: X Server no longer launches urxvtc-X

[Charles Wilson]

On 8/20/2010 10:48 AM, Jay Goldman wrote:
> I have the following menu items in my .XWinrc:
>         Black EXEC  "/bin/urxvtc-X -fg green -bg black   -cr dodgerblue -g 80x40 -e /bin/bash -l -I"
>         dodger EXEC  "urxvtc-X -fg white -bg dodgerblue   -cr blue -g 80x42 -e /bin/bash -l -I"
>
> Which have been working for months .
>
> Today I upgraded my cygwin install and all my menu items like the above no longer work.
> (as noted above I've tried both simply urxvtc-X and /bin/urxvtc-X
> If, however, I open up a command window using rxvt and then enter the above
> Line (by copy and paste) it works fine.

My first guess was that the urxvt daemon (urxvtd-X) was not running, so 
the client failed. But if you can launch the client using some 
incantation, then that means the daemon is running.

>
> Note, menu items like:
>                  Xterm exec "xterm"
> Work correctly,
> While menu items such as:
>                  Notepad exec "notepad"
> Do not.

Ah. Here's the clue: launching a native win32 program fails.  I bet this 
is related to the change in cygwin-1.7.6 where the cygwin "current 
working directory" and the win32 CWD are no longer automatically kept in 
sync (there are good reasons for this new behavior).

This change has caused a number of problems, and it is not yet clear how 
they will be resolved.  Stay tuned to the main cygwin list -- and 
meanwhile, revert to cygwin-1.7.5.

--
Chuck

--
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/

RE: X Server no longer launches urxvtc-X

[Jay Goldman]

Chuck - thanks for the reply. This is what I had concluded but it's nice to get some confirmation.
For the next few days I can live with 'manually' starting urxvtc-X via individual batch files.

Thanks,
Jay

-----Original Message-----
From: cygwin-xfree-owner@cygwin.com [mailto:cygwin-xfree-owner@cygwin.com] On Behalf Of Charles Wilson
Sent: Friday, August 20, 2010 10:54 AM
To: cygwin-xfree@cygwin.com
Subject: Re: X Server no longer launches urxvtc-X

On 8/20/2010 10:48 AM, Jay Goldman wrote:
> I have the following menu items in my .XWinrc:
>         Black EXEC  "/bin/urxvtc-X -fg green -bg black   -cr dodgerblue -g 80x40 -e /bin/bash -l -I"
>         dodger EXEC  "urxvtc-X -fg white -bg dodgerblue   -cr blue -g 80x42 -e /bin/bash -l -I"
>
> Which have been working for months .
>
> Today I upgraded my cygwin install and all my menu items like the above no longer work.
> (as noted above I've tried both simply urxvtc-X and /bin/urxvtc-X
> If, however, I open up a command window using rxvt and then enter the above
> Line (by copy and paste) it works fine.

My first guess was that the urxvt daemon (urxvtd-X) was not running, so 
the client failed. But if you can launch the client using some 
incantation, then that means the daemon is running.

>
> Note, menu items like:
>                  Xterm exec "xterm"
> Work correctly,
> While menu items such as:
>                  Notepad exec "notepad"
> Do not.

Ah. Here's the clue: launching a native win32 program fails.  I bet this 
is related to the change in cygwin-1.7.6 where the cygwin "current 
working directory" and the win32 CWD are no longer automatically kept in 
sync (there are good reasons for this new behavior).

This change has caused a number of problems, and it is not yet clear how 
they will be resolved.  Stay tuned to the main cygwin list -- and 
meanwhile, revert to cygwin-1.7.5.

--
Chuck

--
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/


--
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/

Re: X Server no longer launches urxvtc-X

[Corinna Vinschen]

On Aug 20 10:54, Charles Wilson wrote:
> On 8/20/2010 10:48 AM, Jay Goldman wrote:
> >I have the following menu items in my .XWinrc:
> >        Black EXEC  "/bin/urxvtc-X -fg green -bg black   -cr dodgerblue -g 80x40 -e /bin/bash -l -I"
> >        dodger EXEC  "urxvtc-X -fg white -bg dodgerblue   -cr blue -g 80x42 -e /bin/bash -l -I"
> >
> >Which have been working for months .
> >
> >Today I upgraded my cygwin install and all my menu items like the above no longer work.
> >(as noted above I've tried both simply urxvtc-X and /bin/urxvtc-X
> >If, however, I open up a command window using rxvt and then enter the above
> >Line (by copy and paste) it works fine.
> 
> My first guess was that the urxvt daemon (urxvtd-X) was not running,
> so the client failed. But if you can launch the client using some
> incantation, then that means the daemon is running.
> 
> >
> >Note, menu items like:
> >                 Xterm exec "xterm"
> >Work correctly,
> >While menu items such as:
> >                 Notepad exec "notepad"
> >Do not.
> 
> Ah. Here's the clue: launching a native win32 program fails.  I bet
> this is related to the change in cygwin-1.7.6 where the cygwin
> "current working directory" and the win32 CWD are no longer
> automatically kept in sync (there are good reasons for this new
> behavior).

Maybe that's related, but why?  Does urxvtc-X start applications using
CreateProcess?

I'm asking because if they are started via fork/exec, the cwd for the
child process gets set to the Cygwin cwd if the child is a native Win32
process, like Notepad.  Cygwin executables OTOH shouldn't be affected,
unless, again, they use native Win32 calls.

And that also doesn't answer the question why starting /bin/urxvtc-X in
the menu entries at the start of the mail are not working anymore, at
least unless /bin/urxvtc-X is not a Cygwin application.

> This change has caused a number of problems, and it is not yet clear
> how they will be resolved.

In the first place: http://cygwin.com/ml/cygwin/2010-08/msg00554.html
and http://cygwin.com/ml/cygwin/2010-08/msg00562.html


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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/

RE: X Server no longer launches urxvtc-X

[Jay Goldman]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 3102 bytes --]

Another data point, when I try:
	black  EXEC "/bin/rxvt -fg green -bg black -cr dodgerblue -g 80x40 -e /bin/bash -l -i "
rxvt successfully starts up but displays:
	/bin/find: failed to restore initial working directory: No such file or directory
Before .bash_profile is invoked

-----Original Message-----
From: cygwin-xfree-owner@cygwin.com [mailto:cygwin-xfree-owner@cygwin.com] On Behalf Of Corinna Vinschen
Sent: Friday, August 20, 2010 1:57 PM
To: cygwin-xfree@cygwin.com
Subject: Re: X Server no longer launches urxvtc-X

On Aug 20 10:54, Charles Wilson wrote:
> On 8/20/2010 10:48 AM, Jay Goldman wrote:
> >I have the following menu items in my .XWinrc:
> >        Black EXEC  "/bin/urxvtc-X -fg green -bg black   -cr dodgerblue -g 80x40 -e /bin/bash -l -I"
> >        dodger EXEC  "urxvtc-X -fg white -bg dodgerblue   -cr blue -g 80x42 -e /bin/bash -l -I"
> >
> >Which have been working for months .
> >
> >Today I upgraded my cygwin install and all my menu items like the above no longer work.
> >(as noted above I've tried both simply urxvtc-X and /bin/urxvtc-X
> >If, however, I open up a command window using rxvt and then enter the above
> >Line (by copy and paste) it works fine.
> 
> My first guess was that the urxvt daemon (urxvtd-X) was not running,
> so the client failed. But if you can launch the client using some
> incantation, then that means the daemon is running.
> 
> >
> >Note, menu items like:
> >                 Xterm exec "xterm"
> >Work correctly,
> >While menu items such as:
> >                 Notepad exec "notepad"
> >Do not.
> 
> Ah. Here's the clue: launching a native win32 program fails.  I bet
> this is related to the change in cygwin-1.7.6 where the cygwin
> "current working directory" and the win32 CWD are no longer
> automatically kept in sync (there are good reasons for this new
> behavior).

Maybe that's related, but why?  Does urxvtc-X start applications using
CreateProcess?

I'm asking because if they are started via fork/exec, the cwd for the
child process gets set to the Cygwin cwd if the child is a native Win32
process, like Notepad.  Cygwin executables OTOH shouldn't be affected,
unless, again, they use native Win32 calls.

And that also doesn't answer the question why starting /bin/urxvtc-X in
the menu entries at the start of the mail are not working anymore, at
least unless /bin/urxvtc-X is not a Cygwin application.

> This change has caused a number of problems, and it is not yet clear
> how they will be resolved.

In the first place: http://cygwin.com/ml/cygwin/2010-08/msg00554.html
and http://cygwin.com/ml/cygwin/2010-08/msg00562.html


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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/

\x16º&s(0Š|_­ç«zÛ«Ÿo|Ó©b²Ö«r\x172ƒ\b§ÅúÞ

RE: X Server no longer launches urxvtc-X

[Jay Goldman]

When I just replace the cygwin1.dll bash,
	\bin\bash.exe -login -i
From cmd window results in:
	The procedure entry point CreateProcessAsUserW could not be located in the dynamic link library KERNEL32.dll

I have no idea where find is being invoked when I execute rxvt, since it is invoked before .bash_profile is invoked.

> -----Original Message-----
> On August 20, 2010 3:06 PM, Corinna Vinschen wrote:> 

> 
> Please dont top-post.
> 
> 
> On Aug 20 14:14, Jay Goldman wrote:
> > Another data point, when I try:
> > 	black  EXEC "/bin/rxvt -fg green -bg black -cr dodgerblue -g
> 80x40 -e /bin/bash -l -i "
> > rxvt successfully starts up but displays:
> > 	/bin/find: failed to restore initial working directory: No such
> file or directory
> > Before .bash_profile is invoked
> 
> Works for me without such a message.  Do you know from where find is
> called?
> 
> > -----Original Message-----
> > From: Corinna Vinschen
> > On Aug 20 10:54, Charles Wilson wrote:
> > > On 8/20/2010 10:48 AM, Jay Goldman wrote:
> > > >I have the following menu items in my .XWinrc:
> > > >        Black EXEC  "/bin/urxvtc-X -fg green -bg black   -cr
> dodgerblue -g 80x40 -e /bin/bash -l -I"
> > > >        dodger EXEC  "urxvtc-X -fg white -bg dodgerblue   -cr blue
> -g 80x42 -e /bin/bash -l -I"
> > > >
> > > >Which have been working for months .
> 
> Doesn't work for me either, but has apparently nothing to do with
> the CWD issue.  This looks more like a rebase problem.
> 
> > > >Note, menu items like:
> > > >                 Xterm exec "xterm"
> > > >Work correctly,
> > > >While menu items such as:
> > > >                 Notepad exec "notepad"
> > > >Do not.
> 
> I tried this as well now, and both menu entries work for me.
> 
> Maybe the difference is the Cygwin DLL.  Can you please try the latest
> Cygwin DLL from the developer snapshots at http://cygwin.com/snapshots/
> and report back if this works better for you?
> 
> 
> Thanks,
> Corinna
> 
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin
> to
> Cygwin Project Co-Leader          cygwin AT cygwin DOT com
> Red Hat
> 
> --
> 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/

RE: X Server no longer launches urxvtc-X

[Jay Goldman]

Thanks Bob,
this eliminates the '/bin/find' error when starting rxvt or urxvt.
I just added
	cd / 
before the PATH= line.

Still cannot run urxvtc from X server tray app.

> -----Original Message-----
> From: cygwin-xfree-owner@cygwin.com [mailto:cygwin-xfree-
> owner@cygwin.com] On Behalf Of Rob Gillen
> Sent: Tuesday, August 24, 2010 4:27 PM
> To: cygwin-xfree@cygwin.com
> Subject: RE: X Server no longer launches urxvtc-X
> 
> > Another data point, when I try:
> > 	black  EXEC "/bin/rxvt -fg green -bg black -cr dodgerblue -g
> 80x40 -e /bin/bash -l -i "
> > rxvt successfully starts up but displays:
> > 	/bin/find: failed to restore initial working directory: No such
> file or directory
> > Before .bash_profile is invoked
> 
> Jay, I resolved the "find" issue by modifying the /etc/profile file.
> The real issue is the change made in the latest release of the
> cygwin1.dll where the current working directory is set to an invalid
> directory.  Until you set the current working directory to something
> when find is called, you'll continue to see this.  Try moving this
> portion of the /etc/profile script:
> 
>     # Make sure we start in home unless invoked by CHERE
>     if [ ! -z "${CHERE_INVOKING}" ]; then
>     	unset CHERE_INVOKING
>     else
>     	cd "${HOME}"
>     fi
> 
> so that it is located before the execution of all the /etc/profile.d
> scripts.
> 
> --
> 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/


--
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/