It should be -listen tcp, you can see it picking up -auth as the
argument for that option.
On Tue, Feb 24, 2015 at 10:59 PM, Will Parsons varro@nodomain.invalid wrote:
I'm accustomed to start X via a shortcut which runs the command:
C:\cygwin\bin\run.exe --quote /usr/bin/bash.exe -l \
-c cd;
.
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
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
On 24/02/2015 20:59, Will Parsons wrote:
I'm accustomed to start X via a shortcut which runs the command:
C:\cygwin\bin\run.exe --quote /usr/bin/bash.exe -l \
-c cd; /usr/bin/startxwin -- -listen
[...]
I can't make sense out of what this is telling me about why X failed
to start.
Since
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
I'm accustomed to start X via a shortcut which runs the command:
C:\cygwin\bin\run.exe --quote /usr/bin/bash.exe -l \
-c cd; /usr/bin/startxwin -- -listen
This was working, but now doesn't, with the following shown in the log
file:
Welcome to the XWin X
*** xlaunch-20150224-1
* Fix for X server 1.17
* Close help window when xlaunch is closed
* Use cygpath on path provided to xlaunch for Open/Edit actions
x86:
7afc52b7c36fd076896929d9d45b1632 *xlaunch-20150224-1-src.tar.xz
6fd65620e45b41ddbf1c9359723ecbbb *xlaunch-20150224-1.tar.xz
If I disable auto-wrap, the vi editing at the comand line misbehaves
when the line being edited is long, especially when yanking a lot of
text and pasting it. I suppose that this might be technically correct
behaviour, since an extra long command line needs to wrap in order to
see it properly.
On 24/02/2015 03:57, Michael DePaulo wrote:
I am trying to port this feature of VcXsrv (and XMing also I think) to
Cygwin XLaunch:
https://sourceforge.net/p/vcxsrv/code/ci/460182676a960385dff96c1563f781213060f6fc/
Attached is my WIP patch. (I know it needs the comments updated for main.cc).
On 2015-01-05 05:31, Laurens Blankers wrote:
When using PuTTY with X11 forwarding enabled X clients are no longer
able to connect to the X server running locally. When reverting back to
1.3.2-1 the problem goes away.
This may be related to the -nolisten tcp which is now the default[1]. If
this
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
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
On 24/02/2015 16:55, Fj wrote:
On 2015-01-05 05:31, Laurens Blankers wrote:
When using PuTTY with X11 forwarding enabled X clients are no longer
able to connect to the X server running locally. When reverting back to
1.3.2-1 the problem goes away.
This may be related to the -nolisten tcp
Hi,
Im experiencing an issue where the graphics arent displayed correctly.
When I start LibreOffice on my Fedora 21 Linux system from a cygwin/x
system, the left hand side (open file, template, writer document, etc.)
isnt displayed properly initially. After clicking around some, the
display
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):
[
Jon TURNEY wrote:
On 24/02/2015 20:59, Will Parsons wrote:
I'm accustomed to start X via a shortcut which runs the command:
C:\cygwin\bin\run.exe --quote /usr/bin/bash.exe -l \
-c cd; /usr/bin/startxwin -- -listen
[...]
I can't make sense out of what this is telling me about why X failed
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
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.
Georgegee_barrick_at_kent_dot_edu
18 matches
Mail list logo
