Dfficulty with xorg-server-1.17.1-2.

Dfficulty with xorg-server-1.17.1-2.

[GEORGE BARRICK]

                                    2015.02.24.09:26:38 EST

Hey cygwin folks,

     I've been using xlaunch with a windows desktop shortcut for
about a year to start a multi-window instance of xwin on my Win7
computers.  This is cygwin32 on an installation of Win7_x86-64.
The command within the shortcut is:

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

and I've defined the ~-directory to be C:\cygwin\home\gbarrick
using the HOME variable in the Win7 environment.  My .xlaunch-file
is just:

<file: C:/cygwin/home/gbarrick/config/config.xlaunch >
<?xml version="1.0" encoding="UTF-8"?>
<XLaunch WindowMode="MultiWindow" ClientMode="StartProgram"
  LocalClient="True" Display="0" RemoteProtocol=""
  LocalProgram="xterm -rw -sb -rightbar -geometry 128x44+72+60 -bg goldenrod"
  RemoteProgram="" RemoteHost="" RemoteUser="" XDMCPHost=""
  XDMCPBroadcast="False" XDMCPIndirect="False" Clipboard="True"
  ExtraParams="" Wgl="True" DisableAC="False" XDMCPTerminate="False"
  SSHKeyChain="False" SSHTerminal="True" ExtraSSH=""/>
</file>

(without the "file:"-tags).  This setup successfully gives me
the multi-window instance of xwin, and generates a
/var/log/xwin/Xwin.0.log file as follows.  The only thing that
I've done is to edit the log-file to better fit the width for
an e-mail message.

<file: C:/cygwin/var/log/xwin/xwin.0.log >
Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.16.3.0
OS: CYGWIN_NT-6.1-WOW WC-BARRICK 1.7.34(0.285/5/3) 2015-02-04 12:12 i686
OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (WoW64)
Package: version 1.16.3-1 built 2014-12-30

XWin was started with the following command line:

XWin :0 -multiwindow -clipboard -wgl

ddxProcessArgument - Initializing default screens
winInitializeScreenDefaults - primary monitor w 1680 h 1050
winInitializeScreenDefaults - native DPI x 120 y 120
[  1668.181] (II) xorg.conf is not supported
[  1668.181] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html
     for more information
[  1668.181] LoadPreferences: /home/gbarrick/.XWinrc not found
[  1668.212] LoadPreferences: Loading /etc/X11/system.XWinrc
[  1668.227] LoadPreferences: Done parsing the configuration file...
[  1668.243] winDetectSupportedEngines - DirectDraw4 installed,
     allowing ShadowDDNL
[  1668.259] winDetectSupportedEngines - Returning, supported
     engines 00000015
[  1668.259] winSetEngine - Multi Window or Rootless => ShadowGDI
[  1668.259] winScreenInit - Using Windows display depth of 32 bits
     per pixel
[  1668.259] winAllocateFBShadowGDI - Creating DIB with width:
     1680 height: 1050 depth: 32
[  1668.259] winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff
[  1668.259] winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff
     BPRGB 8 d 24 bpp 32
[  1668.274] MIT-SHM extension disabled due to lack of kernel support
[  1668.305] XFree86-Bigfont extension local-client optimization disabled
     due to lack of shared memory support in the kernel
[  1668.337] glWinSelectGLimplementation: Loaded 'cygnativeGLthunk.dll'
[  1668.586] (II) AIGLX: Testing pixelFormatIndex 1
[  1668.773] GL_VERSION:     2.1.0 - Build 8.15.10.2869
[  1668.773] GL_VENDOR:      Intel
[  1668.773] GL_RENDERER:    Intel(R) 4 Series Internal Chipset
[  1668.773] (II) AIGLX: enabled GLX_SGI_make_current_read
[  1668.773] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[  1668.773] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[  1668.773] (II) AIGLX: enabled GLX_SGIX_pbuffer
[  1668.773] (II) 51 pixel formats reported by wglGetPixelFormatAttribivARB
[  1668.773] (II) AIGLX: Set GLX version to 1.3
[  1668.789] (II) 6 fbConfigs
[  1668.789] (II) ignored pixel formats: 0 not OpenGL, 6 RBGA float,
     3 RGBA unsigned float, 0 unknown pixel type, 36 unaccelerated
[  1668.789] (II) GLX: Initialized Win32 native WGL GL provider for screen 0
[  1669.678] winPointerWarpCursor - Discarding first warp: 840 525
[  1669.678] (--) 3 mouse buttons found
[  1669.678] (--) Setting autorepeat to delay=500, rate=31
[  1669.678] (--) Windows keyboard layout: "00000409" (00000409) "US", type 4
[  1669.678] (--) Found matching XKB configuration "English (USA)"
[  1669.678] (--) Model = "pc105" Layout = "us" Variant = "none"
     Options = "none"
[  1669.678] Rules = "base" Model = "pc105" Layout = "us" Variant = "none"
     Options = "none"
[  1669.694] winMultiWindowXMsgProc - DISPLAY=:0.0
[  1669.694] winInitMultiWindowWM - DISPLAY=:0.0
[  1669.694] winProcEstablishConnection - winInitClipboard returned.
[  1669.694] winClipboardThreadProc - DISPLAY=:0.0
[  1669.694] OS maintains clipboard viewer chain: yes
[  1669.694] winMultiWindowXMsgProc - XOpenDisplay () returned and
     successfully opened the display.
[  1669.694] winClipboardProc - XOpenDisplay () returned and
     successfully opened the display.
[  1669.694] winInitMultiWindowWM - XOpenDisplay () returned and
     successfully opened the display.
</file>

     OK.  Now for the difficulty.  I recently (today) updated my
cygwin system to include the newest xorg-server, xorg-server-common
and xorg-server-dmx (the 1.17.1-2 versions) as well as
xf86-video-dummy_0.3.7-3 xf86-video-nested-0.1.0-6 and xinit_1.3.4-5,
and have found that xlaunch no longer seems capable of finding my
.xlaunch-file.  It starts X as before, but does not automatically spin
up the xterm that my .xlaunch-file requests.  I wind up having to start
an xterm manually from the xwin "Applications" menu.

     In summary, I have changed _nothing_ except for the new X-stuff,
and have this problem.  The log-file from xwin does not seem radically
different:

<file: C:/cygwin/var/log/xwin/xwin.0.log >
Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.17.1.0
OS: CYGWIN_NT-6.1-WOW WC-BARRICK 1.7.34(0.285/5/3) 2015-02-04 12:12 i686
OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (WoW64)
Package: version 1.17.1-2 built 2015-02-23

XWin was started with the following command line:

XWin :0 -multiwindow -clipboard -wgl

ddxProcessArgument - Initializing default screens
winInitializeScreenDefaults - primary monitor w 1680 h 1050
winInitializeScreenDefaults - native DPI x 120 y 120
[  4313.630] (II) xorg.conf is not supported
[  4313.630] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html
     for more information
[  4313.630] LoadPreferences: /home/gbarrick/.XWinrc not found
[  4313.630] LoadPreferences: Loading /etc/X11/system.XWinrc
[  4313.630] LoadPreferences: Done parsing the configuration file...
[  4313.646] winDetectSupportedEngines - DirectDraw4 installed,
     allowing ShadowDDNL
[  4313.646] winDetectSupportedEngines - Returning,
     supported engines 00000005
[  4313.646] winSetEngine - Multi Window or Rootless => ShadowGDI
[  4313.646] winScreenInit - Using Windows display depth of 32 bits per pixel
[  4313.661] winAllocateFBShadowGDI - Creating DIB with width:
     1680 height: 1050 depth: 32
[  4313.661] winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff
[  4313.661] winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff
     BPRGB 8 d 24 bpp 32
[  4313.661] MIT-SHM extension disabled due to lack of kernel support
[  4313.692] XFree86-Bigfont extension local-client optimization disabled
     due to lack of shared memory support in the kernel
[  4313.692] glWinSelectGLimplementation: Loaded 'cygnativeGLthunk.dll'
[  4313.708] (II) AIGLX: Testing pixelFormatIndex 1
[  4313.724] GL_VERSION:     2.1.0 - Build 8.15.10.2869
[  4313.724] GL_VENDOR:      Intel
[  4313.724] GL_RENDERER:    Intel(R) 4 Series Internal Chipset
[  4313.724] (II) AIGLX: enabled GLX_SGI_make_current_read
[  4313.724] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[  4313.724] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[  4313.724] (II) AIGLX: enabled GLX_SGIX_pbuffer
[  4313.724] (II) 51 pixel formats reported by wglGetPixelFormatAttribivARB
[  4313.739] (II) AIGLX: Set GLX version to 1.3
[  4313.739] (II) 6 fbConfigs
[  4313.739] (II) ignored pixel formats: 0 not OpenGL, 6 RBGA float,
     3 RGBA unsigned float, 0 unknown pixel type, 36 unaccelerated
[  4313.739] (II) GLX: Initialized Win32 native WGL GL provider for screen 0
[  4313.926] winPointerWarpCursor - Discarding first warp: 840 525
[  4313.926] (--) 3 mouse buttons found
[  4313.926] (--) Setting autorepeat to delay=500, rate=31
[  4313.926] (--) Windows keyboard layout: "00000409" (00000409) "US", type 4
[  4313.926] (--) Found matching XKB configuration "English (USA)"
[  4313.926] (--) Model = "pc105" Layout = "us" Variant = "none"
     Options = "none"
[  4313.926] Rules = "base" Model = "pc105" Layout = "us" Variant = "none"
     Options = "none"
[  4313.926] winInitMultiWindowWM - DISPLAY=:0.0
[  4313.926] winMultiWindowXMsgProc - DISPLAY=:0.0
[  4313.926] winProcEstablishConnection - winInitClipboard returned.
[  4313.926] winClipboardThreadProc - DISPLAY=:0.0
[  4313.926] OS maintains clipboard viewer chain: yes
[  4313.926] winInitMultiWindowWM - XOpenDisplay () returned and successfully
     opened the display.
[  4313.926] winMultiWindowXMsgProc - XOpenDisplay () returned and successfully
     opened the display.
[  4313.926] winClipboardProc - XOpenDisplay () returned and successfully
     opened the display.
[  4328.575] executing 'xterm', pid 3100
[  4328.746] (pid 3100 stderr) Warning: Missing charsets in String to
     FontSet conversion
</file>

     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.

     Is it possible that the new xinit is the cause of the problem?
I noticed that there's some mention in the cygwin-x mailing list of
the -listen -nolisten flags; but I do not know enough to figure out
whether it's relevant to my issue.  Also, should I really have all
six of these X-packages for a cygwin system that does not use
3D/high-end video?  Note: I installed the font packages font-isas-misc,
font-jis-misc and font-daewoo-misc to try and obviate the xterm warning,
but this does not change the nature of the problem.

     If everything that I reported seems to be OK, and my message
does not strike any bells in people's brains, can you point me towards
a test or further gathering of data that might help to reproduce and
circumvent this minor difficulty?

Thanks,

George                         gee_barrick_at_kent_dot_edu

P.S.  Excuse verbosity of this report; I've tried to give complete
        description.

--
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: Dfficulty with xorg-server-1.17.1-2.

[Jim Reisert AD1C]

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.

- Jim

-- 
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us

--
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: Dfficulty with xorg-server-1.17.1-2.

[Jon TURNEY]

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

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

Re: Dfficulty with xorg-server-1.17.1-2.

[Jon TURNEY]

On 24/02/2015 18:03, GEORGE BARRICK wrote:
>       I've been using xlaunch with a windows desktop shortcut for
> about a year to start a multi-window instance of xwin on my Win7
> computers.
[snip]
>       OK.  Now for the difficulty.  I recently (today) updated my
> cygwin system to include the newest xorg-server, xorg-server-common
> and xorg-server-dmx (the 1.17.1-2 versions) as well as
> xf86-video-dummy_0.3.7-3 xf86-video-nested-0.1.0-6 and xinit_1.3.4-5,
> and have found that xlaunch no longer seems capable of finding my
> .xlaunch-file.  It starts X as before, but does not automatically spin
> up the xterm that my .xlaunch-file requests.  I wind up having to start
> an xterm manually from the xwin "Applications" menu.
>
>       In summary, I have changed _nothing_ except for the new X-stuff,
> and have this problem.  The log-file from xwin does not seem radically
> different:
[snip]
>       The other notable problem to report is that my X-server now
> crashes after about 5-10 minutes of use.
[snip]
> P.S.  Excuse verbosity of this report; I've tried to give complete
>          description.

Thanks for providing such a detailed report, this enabled me to quickly 
reproduce what I think is the issue.

This seems to be a problem with xlaunch, which needs a small update to 
work correctly with xserver 1.17.

I've just uploaded xlaunch-20150224-1, which should fix this.

I think this is actually also the cause of your 'crashes' as well. 
After about 12 minutes, xlaunch is deciding that the X server hasn't 
started successfully and is killing it.

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

Re: Dfficulty with xorg-server-1.17.1-2.

[Jon TURNEY]

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/

Re: Dfficulty with xorg-server-1.17.1-2.

[GEORGE BARRICK]

                                           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.turney@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/

Re: Dfficulty with xorg-server-1.17.1-2.

[Jim Reisert AD1C]

On Tue, Feb 24, 2015 at 12:35 PM, Jon TURNEY wrote:

> 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

This isn't a backtrace, but it's what caused the X server to crash
(while I was at work):

[   164.799] winClipboardProc - winClipboardFlushWindowsMessageQueue
trapped WM_QUIT message, exiting main loop.

I'll follow these steps before I leave for work tomororw.  There is no
specific action, but I'll attach gdb and let it just sit there.

- Generating a backtrace when some specific action is making the X server crash

-- 
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us

--
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: Dfficulty with xorg-server-1.17.1-2.

[Jim Reisert AD1C]

> 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

gdb won't let  me continue:

# gdb --pid=`pidof /usr/bin/XWin`
...
Reading symbols from /usr/bin/XWin.exe...Reading symbols from /cygdrive/c/Cygwin
/lib/debug//usr/bin/XWin.exe.dbg...Can't read data for section '.debug_frame' in
 file '/cygdrive/c/Cygwin/lib/debug/usr/bin/XWin.exe.dbg'
(gdb) c
Continuing.
Cannot execute this command while the selected thread is running.
(gdb)


At this point, I can not right-click on the 'X' icon to do anything.
Once I exit gdb, then I can. How can I get past this?

-- 
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us

--
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: Dfficulty with xorg-server-1.17.1-2.

[Jon TURNEY]

On 25/02/2015 04:35, Jim Reisert AD1C wrote:
> # gdb --pid=`pidof /usr/bin/XWin`
> ...
> Reading symbols from /usr/bin/XWin.exe...Reading symbols from /cygdrive/c/Cygwin
> /lib/debug//usr/bin/XWin.exe.dbg...Can't read data for section '.debug_frame' in
>   file '/cygdrive/c/Cygwin/lib/debug/usr/bin/XWin.exe.dbg'
> (gdb) c
> Continuing.
> Cannot execute this command while the selected thread is running.
> (gdb)
>
> At this point, I can not right-click on the 'X' icon to do anything.
> Once I exit gdb, then I can. How can I get past this?

Odd.  Are you sure you are using the current, cygwin gdb?

But let's step back a moment, since I don't think you have the same 
problem as the OP.

> [   164.799] winClipboardProc - winClipboardFlushWindowsMessageQueue
> trapped WM_QUIT message, exiting main loop.

Perhaps we need to be a little more specific about what we mean by 
'crashing'.

This log message probably means that the X server is just spontaneously 
deciding it should exit, rather than exiting due to a program error 
signal with the "A fatal error has occurred" dialog.

Can you provide a full Xwin.0.log file, please?

I am assuming that this problem started with xorg-server 1.17 and 
reverting to 1.16.3-1 fixes it?

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

Re: Dfficulty with xorg-server-1.17.1-2.

[GEORGE BARRICK]

                                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 <gbarrick@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.turney@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/

Re: Dfficulty with xorg-server-1.17.1-2.

[GEORGE BARRICK]

                                    2015.03.01.09:06:13 EST

Hi Jon,

       Thanks for the tips.

George                       gee_barrick_at_kent_dot_edu


On 2/28/15, Jon TURNEY <jon.turney@dronecode.org.uk> wrote:
> On 25/02/2015 14:30, GEORGE BARRICK wrote:
>>     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.
>
> You need to quote the whole command line for bash after the -c,
> otherwise bash treats words after the first one as positional parameters.
>
> However, getting this quotation passed correctly through run requires a
> little bit of gymnastics, but this should work:
>
> C:\cygwin\bin\run.exe --quote /usr/bin/bash.exe -l -c "xlaunch -run
> ~/config/config.xlaunch"
>
>> 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 not quite equivalent as there is no login shell in the ancestry
> of whatever your config.xlaunch starts, so your ~/.profile may not have
> been read.
>
> For that reason, using 'bash -l -c ""' is preferred and that's what
> start menu links that cygwin installs generally use.
>
> --
> 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/