public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: t s <furriner67@hotmail.com>
To: "cygwin-xfree@cygwin.com" <cygwin-xfree@cygwin.com>,
"marco.atzeri@gmail.com" <marco.atzeri@gmail.com>
Subject: FW: cygwin-xfree Digest 5 Sep 2014 16:55:49 -0000 Issue 3554
Date: Thu, 11 Sep 2014 09:51:00 -0000 [thread overview]
Message-ID: <COL125-W956DAF3B7D8736304DC7CCDCC0@phx.gbl> (raw)
In-Reply-To: <COL125-W250F93A09DC0B28B2E6B07CDCC0@phx.gbl>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 6423 bytes --]
From: furriner67@hotmail.com
To: cygwin-xfree@cygwin.com; marco.atzeri@gmail.com
Subject: FW: cygwin-xfree Digest 5 Sep 2014 16:55:49 -0000 Issue 3554
Date: Thu, 11 Sep 2014 05:49:53 -0400
fwd
please see file;
cpm86.com/cygcheck.out
why are my posts to cygwin-xfree@cygwin.com not going through?
thank you
From: furriner67@hotmail.com
To: cygwin-xfree@cygwin.com
Subject: RE: cygwin-xfree Digest 5 Sep 2014 16:55:49 -0000 Issue 3554
Date: Fri, 5 Sep 2014 19:04:34 -0400
cpm86.com/cygcheck.out
thanks
From: furriner67@hotmail.com
To: cygwin-xfree@cygwin.com
Subject: RE: cygwin-xfree Digest 5 Sep 2014 16:55:49 -0000 Issue 3554
Date: Fri, 5 Sep 2014 19:01:01 -0400
Can you also please also follow
"Run cygcheck -s -v -r> cygcheck.out and include that file as an
attachment in your report. Please do not compress or otherwise encode
the output. Just attach it as a straight text file so that it can be
easily viewed. "
done
Date: Fri, 5 Sep 2014 16:55:49 +0000
From: cygwin-xfree-digest-help@cygwin.com
To: cygwin-xfree@cygwin.com
Subject: cygwin-xfree Digest 5 Sep 2014 16:55:49 -0000 Issue 3554
cygwin-xfree Digest 5 Sep 2014 16:55:49 -0000 Issue 3554
Topics (messages 31775 through 31777):
problems installing Cygwin/xþþ
31775 by: t s
31776 by: Marco Atzeri
Possible X11 server bug
31777 by: mathog
Administrivia:
To subscribe to the digest, e-mail:
cygwin-xfree-digest-subscribe@cygwin.com
To unsubscribe from the digest, e-mail:
cygwin-xfree-digest-unsubscribe@cygwin.com
To post to the list, e-mail:
cygwin-xfree@cygwin.com
----------------------------------------------------------------------
--Forwarded Message Attachment--
From: furriner67@hotmail.com
To: cygwin-xfree@cygwin.com
Subject: problems installing Cygwin/xââ
Date: Thu, 4 Sep 2014 13:33:20 -0400
I can't get cygwin/x to run. I downloaded the latest revision. Here is what happened.
$ Xwin :0 -multiwindow -clipboard -wgl
Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.15.1.0
OS: CYGWIN_NT-6.1 SONYZ 1.7.32(0.274/5/3) 2014-08-13 23:06 x86_64
OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (Win64)
Package: version 1.15.1-4 built 2014-07-18
XWin was started with the following command line:
Xwin :0 -multiwindow -clipboard -wgl
_XSERVTransmkdir: Mode of /tmp/.X11-unix should be set to 1777
_XSERVTransmkdir: this may cause subsequent errors
(EE) Fatal server error:
(EE) Can't read lock file /tmp/.X0-lock
(EE) Server terminated with error (1). Closing log file.
winDeinitMultiWindowWM - Noting shutdown in progress
$
Help, please?
My post to this mailing list of two weeks ago was deleted. It's impolite to delete a post without giving a reason. Please allow this post. Thank you.
--Forwarded Message Attachment--
Date: Thu, 4 Sep 2014 19:46:26 +0200
From: marco.atzeri@gmail.com
To: cygwin-xfree@cygwin.com
Subject: Re: problems installing Cygwin/xââ
On 04/09/2014 19:33, t s wrote:
> I can't get cygwin/x to run. I downloaded the latest revision. Here is what happened.
>
>
>
> $ Xwin :0 -multiwindow -clipboard -wgl
>
> Welcome to the XWin X Server
>
> Vendor: The Cygwin/X Project
>
> Release: 1.15.1.0
>
> OS: CYGWIN_NT-6.1 SONYZ 1.7.32(0.274/5/3) 2014-08-13 23:06 x86_64
>
> OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (Win64)
>
> Package: version 1.15.1-4 built 2014-07-18
>
> XWin was started with the following command line:
>
> Xwin :0 -multiwindow -clipboard -wgl
>
> _XSERVTransmkdir: Mode of /tmp/.X11-unix should be set to 1777
>
> _XSERVTransmkdir: this may cause subsequent errors
>
> (EE) Fatal server error:
>
> (EE) Can't read lock file /tmp/.X0-lock
>
> (EE) Server terminated with error (1). Closing log file.
>
> winDeinitMultiWindowWM - Noting shutdown in progress
>
> $
>
>
> Help, please?
>
> My post to this mailing list of two weeks ago was deleted. It's impolite to delete a post without giving a reason. Please allow this post. Thank you.
Hi TS
your mail was probably rejected by the SPAM filter. possibly as there as
something looking
as a raw email address.
Can you also please also follow
"Run cygcheck -s -v -r> cygcheck.out and include that file as an
attachment in your report. Please do not compress or otherwise encode
the output. Just attach it as a straight text file so that it can be
easily viewed. "
as reported
https://cygwin.com/problems.html
Regards
Marco
--Forwarded Message Attachment--
To: cygwin-xfree@cygwin.com
Subject: Possible X11 server bug
Date: Fri, 5 Sep 2014 09:55:44 -0700
From: mathog@caltech.edu
I have run into an issue which _may_ indicate a bug in the cygwin X11
server. The issue is documented here:
https://bugs.launchpad.net/inkscape/+bug/1365153
In brief, for certain test files viewed in Inkscape (current trunk at
least) over a putty ssh tunnel from an Ubuntu 12.04lts system to the
cygwin 1.14.1.0 X11 server there are glitches in the image when it is
zoomed in and out. This does not occur if the same program is run
locally on the console of the test machine. It also does not happen if
I run a native Windows version (not cygwin, not X11) of Inkscape on the
same PC which hosts that X11 server on the same test files. The glitch
does not occur with a huge number of other test files I have looked at
over the years. It seems there is something specific to the clipping
code in Inkscape and this particular X11 transport path/server
combination. Moreover, it looks like the problem is only manifested (or
only manifested frequently) when the clipping path consists of two (or
more?) disjoint sections.
When the glitches occur nothing is added to XWin.0.log.
Also this X11 server is not running in the full cygwin environment, but
rather in one edited down to just the minimum needed to run the X11
server. I distribute this version here:
http://sourceforge.net/projects/minimalcygwinx/
I don't think this is a factor though, since all of the action is going
on inside the X11 server process(es).
Thanks,
David Mathog
mathog@caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech \x16º&s(0|_ç«zÛ«}{ób²Ö«r\x172\b§ÅúÞ
next parent reply other threads:[~2014-09-11 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1409936149.13241.ezmlm@cygwin.com>
[not found] ` <COL125-W1346CBD65023D838F0ACB8CDC20@phx.gbl>
[not found] ` <COL125-W5887A7E0F8D2567BF7462CDC20@phx.gbl>
[not found] ` <COL125-W250F93A09DC0B28B2E6B07CDCC0@phx.gbl>
2014-09-11 9:51 ` t s [this message]
[not found] ` <54118820.8060608@gmail.com>
[not found] ` <COL125-W34A0E712C7A9C08BE76AE4CDCC0@phx.gbl>
[not found] ` <COL125-W80864F85F364811814B4ECDCC0@phx.gbl>
2014-09-16 17:06 ` t s
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=COL125-W956DAF3B7D8736304DC7CCDCC0@phx.gbl \
--to=furriner67@hotmail.com \
--cc=cygwin-xfree@cygwin.com \
--cc=marco.atzeri@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).