2015.02.25.09:27:05

Hey Jon and cygwin staff,

    As you surmised, the difficulty was with xlaunch starting the
new xwin-1.17.2-1.  The xlaunch-20150224-1 that you posted
yesterday works like a charm.

   I have one small note for other folks who might like to run their
system in a way similar to mine.  I like to have xlaunch automatically
start a single colored xterm for me (in multi-window mode).  After
that I just open more from the command line as it suits me.  If I use
the command line embedded in the installed xlaunch.lnk file:

C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/xlaunch.exe

it always prompts me through the tiresome "configure & start" GUI at
the beginning.  Adding the phrase

-run ~/config/config.xlaunch

at the end of that command line always gets ignored in favor of the
"configure & start" GUI.  However, when I strip the invocation of the
bash from that command:

C:\cygwin\bin\run.exe /usr/bin/xlaunch.exe -run ~/config/config.xlaunch

the xlaunch goes right ahead to run the single xterm that's described
in my ~/config/config.xlaunch file.

    This is a petty subtlety, but I know there are a lot of desktop
tweakers out there who might find it a little bit helpful.

George                           gee_barrick_kent_dot_edu


P.S.    Thanks_x_10^{12} to cygwin for your great system and service
          to the FOSS community.

On 2/24/15, GEORGE BARRICK <gbarr...@kent.edu> wrote:
>                                            2015.02.24.18:06:36 EST
>
> Hey Jon,
>
>          Thanks for your attention to all that detail.
> I will test the updated xlaunch-20150224-1 when
> it hits some of the mirrors tomorrow morning.
>
> George                                gee_barrick_at_kent_dot_edu
>
>
> On 2/24/15, Jon TURNEY <jon.tur...@dronecode.org.uk> wrote:
>> On 24/02/2015 19:35, Jon TURNEY wrote:
>>> On 24/02/2015 19:05, Jim Reisert AD1C wrote:
>>>> On Tue, Feb 24, 2015 at 11:03 AM, GEORGE BARRICK wrote:
>>>>
>>>>>       The other notable problem to report is that my X-server now
>>>>> crashes after about 5-10 minutes of use.  Since this issue does
>>>>> not get reported in xwin.0.log or xwin.0.log.old, I do not yet
>>>>> know how to provide more information.
>>>>
>>>> I have seen this also. It only happens on my PC at home, if I leave it
>>>> alone for hours on end.  It's not nearly as frequent as 5-10 minutes.
>>>> I need to check the log files again, but I don't remember seeing
>>>> anything there the first time I looked.
>>>
>>> With regard to the crash problems, can you please try the instructions
>>> at [1] to generate a backtrace.
>>>
>>> [1] http://x.cygwin.com/devel/backtrace.html
>>
>> Possibly this was xlaunch deciding that the X server hasn't started
>> successfully after ~12 minutes or so, and killing it.
>>
>> So don't bother, unless you have crash problems after upgrading to
>> xlaunch-20150224-1, or when not using xlaunch.
>>
>> --
>> Jon TURNEY
>> Volunteer Cygwin/X X Server maintainer
>>
>

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

Reply via email to