headers
Phil Betts | 1 Sep 2009 13:58
Favicon

RE: Problems starting "rxvt" from startxwin.bat

Jose Luis wrote:
> I can start "xterm" from startxwin.bat:
> 
>         %RUN% xterm -e /usr/bin/bash -l
> 
> but no "rxvt":
> 
>         %RUN% rxvt -bg white -fg black -e /bin/bash
> 
> although it can be started from command line:
> 
>          jlfdiaz <at> JLFDIAZWXP ~
>          $ rxvt -bg white -fg black -e /bin/bash  &
> 
> 
> Why does rvxt starting from startxwin.bat fail?

This is almost certainly a timing issue.  The line in the batch file
that starts the server uses %RUN% to start it in the background.  This
means that the following commands in the batch file may execute before
the X server has completed (or even started) its initialisation.

I suspect that the reason the two terminals behave differently is
that, xterm tries to connect to the server a number of times before
giving up, whereas rxvt gives up at the first failure.

Because the time taken to initialise the X server can vary, rather
than using just sleep, I have added the following:

REM wait up to 30 seconds for the X server
(Continue reading)

Permalink | Reply | 3 comments |
headers
Mike Ayers | 2 Sep 2009 00:42

RE: Problems starting "rxvt" from startxwin.bat

> From: cygwin-xfree-owner <at> cygwin.com [mailto:cygwin-xfree-
> owner <at> cygwin.com] On Behalf Of Phil Betts

> Jose Luis wrote:
> > I can start "xterm" from startxwin.bat:
> >
> >         %RUN% xterm -e /usr/bin/bash -l
> >
> > but no "rxvt":
> >
> >         %RUN% rxvt -bg white -fg black -e /bin/bash
> >
> > although it can be started from command line:
> >
> >          jlfdiaz <at> JLFDIAZWXP ~
> >          $ rxvt -bg white -fg black -e /bin/bash  &

	Brutality is fun!

%RUN% xterm -e "sh -c '(nohup rxvt -bg white -fg black -e /bin/bash &) && sleep 1'"


	HTH,

Mike
Permalink | Reply | 0 comments |
headers
Jeff Forbes | 3 Sep 2009 15:51
Picon

composite extension

Hi,

I have been unable to find how to disable
the composite extension.
Can anyone tell me how this can be done.

Jeff

--
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/
Permalink | Reply | 1 comment |
headers
Jon TURNEY | 3 Sep 2009 17:13
Picon
Favicon
Gravatar

Re: composite extension

On 03/09/2009 14:51, Jeff Forbes wrote:
> Hi,
>
> I have been unable to find how to disable
> the composite extension.
> Can anyone tell me how this can be done.

from 'man Xserver'

>
>        −extension extensionName
>                disables  named  extension.    If  an  unknown  extension  name is specified, a list of
>                accepted extension names is printed.
>
>        +extension extensionName
>                enables named extension.   If an  unknown  extension  name  is  specified,  a  list  of
>                accepted extension names is printed.

So adding '-extension Composite' to the command line used to start the X 
server should do what you want.

Just out of curiosity: why do you want to disable the composite extension?

--

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jon TURNEY | 3 Sep 2009 18:11
Picon
Favicon
Gravatar

Re: Problems starting "rxvt" from startxwin.bat

On 01/09/2009 12:58, Phil Betts wrote:
> Jose Luis wrote:
>> I can start "xterm" from startxwin.bat:
>>
>>          %RUN% xterm -e /usr/bin/bash -l
>>
>> but no "rxvt":
>>
>>          %RUN% rxvt -bg white -fg black -e /bin/bash
>>
>> although it can be started from command line:
>>
>>           jlfdiaz <at> JLFDIAZWXP ~
>>           $ rxvt -bg white -fg black -e /bin/bash&
>>
>>
>> Why does rvxt starting from startxwin.bat fail?
>
> This is almost certainly a timing issue.  The line in the batch file
> that starts the server uses %RUN% to start it in the background.  This
> means that the following commands in the batch file may execute before
> the X server has completed (or even started) its initialisation.

Argh, yes.

> I suspect that the reason the two terminals behave differently is
> that, xterm tries to connect to the server a number of times before
> giving up, whereas rxvt gives up at the first failure.
>
> Because the time taken to initialise the X server can vary, rather
(Continue reading)

Permalink | Reply | 1 comment |
headers
Charles Wilson | 3 Sep 2009 19:15
Favicon

Re: Problems starting "rxvt" from startxwin.bat

Jon TURNEY wrote:

> Is there a reason why we can't do 'checkx -d %DISPLAY% -t 30' rather
> than counting up to 30 ourselves?

Well, -t with a number larger than 12 is not useful. Xlib itself will
timeout after 12 seconds if it can't contact the xserver.  The -t option
for checkx (and run2) simply says how long checkx will wait for the
worker thread that's actually trying to contact the Xserver, before
giving up and detaching the thread.

--
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/
Permalink | Reply | 0 comments |
headers
Charles Wilson | 4 Sep 2009 23:11
Favicon

Re: [1.7] On checkX

Angelo Graziosi wrote:
> Charles Wilson wrote:
>> Unfortunately, I can't reproduce.
> 
> Ugh! I forgot to say that I start those scripts with links on desktop...
> 
> For example:
> 
> mkshortcut -AD \
>     -n "${urxvt}" \
>     -a "bash -l start_urxvt.sh" \
>     -i /usr/bin/XWin.exe \
>     -d "Console unicode" \
>     /usr/bin/run.exe

Using a short cut to my script, just like your shortcut (except mine is
on my own desktop, not all-users'), I...can't reproduce your problem. WJJFM.

> Indeed, if I start the script from Cygwin.bat, there is not
> checkX.exe.stackdump in the HOME! It is created ONLY starting the script
> with the link...
> 
> ...and, in that case, the lines:
> 
> [...]
> while ! /usr/bin/checkX
> do
>   printf "waiting for xserver to start\n"
>   sleep 1
> done
(Continue reading)

Permalink | Reply | 1 comment |
headers
Charles Wilson | 4 Sep 2009 23:27
Favicon

Re: [1.7] On checkX

Charles Wilson wrote:
> Angelo Graziosi wrote:
>> Charles Wilson wrote:
>>> Unfortunately, I can't reproduce.
>> Ugh! I forgot to say that I start those scripts with links on desktop...
>>
>> For example:
>>
>> mkshortcut -AD \
>>     -n "${urxvt}" \
>>     -a "bash -l start_urxvt.sh" \
>>     -i /usr/bin/XWin.exe \
>>     -d "Console unicode" \
>>     /usr/bin/run.exe
> 
> Using a short cut to my script, just like your shortcut (except mine is
> on my own desktop, not all-users'), I...can't reproduce your problem. WJJFM.

Hmm. Spoke too soon.  It appears, that if I turn on --debug, then I get the

      5 [main] checkX 5048 fhandler_console::fixup_after_fork_exec:
error opening input console handle for /dev/console after fork/exec,
errno 13, Win32 error 5
   2342 [main] checkX 5048 fhandler_console::fixup_after_fork_exec:
error opening output console handle for /dev/console after fork/exec,
errno 13, Win32 error

errors in my log, but only when launching from a shortcut.  However, I
think that's expected...since checkX deliberately does not allocate a
console, and is *supposed* to use the presence/absence of a console to
(Continue reading)

Permalink | Reply | 0 comments |
headers
Angelo Graziosi | 5 Sep 2009 10:30
Picon

Re: [1.7] On checkX

Charles Wilson wrote:
> Try this:

I have tried your script. It creates 6 logs (attached) and NO 
stackdump!!. But if one tries to copy/paste something, the 
'clipboard'/system hangs...

> Try adding --notty to each invocation of checkX...that works for me.

It seems that it works also for me! It creates only 2 logs (without 
stackdump and clipboard problems):

$ cat checkX_0.log checkX_1.log
       5 [main] checkX 3612 fhandler_console::fixup_after_fork_exec: 
error opening input console handle for /dev/console after fork/exec, 
errno 13, Win32 error 5
     958 [main] checkX 3612 fhandler_console::fixup_after_fork_exec: 
error opening output console handle for /dev/console after fork/exec, 
errno 13, Win32 error 5
starting xserver
       4 [main] checkX 3876 fhandler_console::fixup_after_fork_exec: 
error opening input console handle for /dev/console after fork/exec, 
errno 13, Win32 error 5
   19455 [main] checkX 3876 fhandler_console::fixup_after_fork_exec: 
error opening output console handle for /dev/console after fork/exec, 
errno 13, Win32 error 5

but the massages of checkX are flagged by Windows to which one should 
click OK, OK,...
(Continue reading)

Permalink | Reply | 3 comments |
headers
Yaakov (Cygwin/X | 6 Sep 2009 06:28
Picon
Gravatar

[ANNOUNCEMENT] [1.7] Updated: fontconfig-2.7.1-1

The following packages have been updated for Cygwin 1.7:

*** fontconfig-2.7.1-1
*** libfontconfig1-2.7.1-1
*** libfontconfig-devel-2.7.1-1

This is an update to the latest upstream release.

The Ghostscript font directory and the two most common Windows font 
directories have been added to the default search path, so most users 
should find many more fonts available.  I hope to provide a more 
foolproof handling of the Windows font directory in future releases.

Yaakov
Cygwin/X

CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO
======================================

If you want to unsubscribe from the cygwin-xfree-announce mailing list, 
please use the automated form at:

http://cygwin.com/lists.html#subscribe-unsubscribe

If this does not work, then look at the "List-Unsubscribe: " tag in the
email header of this message.  Send email to the address specified
there.  It will be in the format:

cygwin-xfree-announce-unsubscribe-you=yourdomain.com <at> cygwin.com
(Continue reading)

Permalink | Reply | 0 comments |

Gmane