public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Gilles Detillieux <grdetil@scrc.umanitoba.ca>
To: cygwin@cygwin.com
Cc: karl.peterson@gmail.com
Subject: Re: XTerm(330) fails to open window in latest cygwin-x64 under Windows 10
Date: Tue, 24 Apr 2018 21:54:00 -0000	[thread overview]
Message-ID: <6163af78-bce6-6e23-eb8f-4a7cc586f75a@scrc.umanitoba.ca> (raw)

Karl, you might want to try reverting to the previous version of 
libharfbuzz0 and libfreetype6. I'm running into problems with those 
libraries on the 32-bit version of cygwin, causing occasional crashes of 
xterm, and frequent crashes of xwin-xdg-menu under Windows 10. I'm just 
wondering if your issue is related to those same problems in these 
libraries, only it's manifesting differently under the 64-bit version of 
cygwin. It may be a long-shot, but if our experiences corroborate each 
other it might help nail down these font-related issues.

In any case, check to see if there's an xterm.exe.stackdump file in the 
directory from which you ran xterm. If there is, try running something 
like "strace xterm.exe > xterm.log" and see what xterm is doing before 
it crashes.

Hope this helps.

Gilles

On Wed, 18 Apr 2018 09:48:08, Karl Peterson wrote:

> The only output is:
> karpeterson@DFWLW1041HJTC2 /var/log/xwin
> $ xterm
> xterm: cannot load font
> "-Misc-Fixed-bold-R-*-*-13-120-75-75-C-120-ISO10646-1"
> 
> XWin.0.log contains:
> [  1471.843] IsOverrideRedirect: Failed to get window attributes
> 
> This message only gets printed when I use my favorite xterm options: "-fg
> white -bg black -sl 5000" No other output is printed, and xterm exits with
> RC=0. Other locally run X programs work fine, such as xeyes and emacs.
> 
> 
> What can I do to debug this?

-- 
Gilles R. Detillieux              E-mail: <grdetil@scrc.umanitoba.ca>
Spinal Cord Research Centre       WWW:    http://www.scrc.umanitoba.ca/
Dept. of Physiology and Pathophysiology, Rady Faculty of Health Sciences,
Univ. of Manitoba  Winnipeg, MB  R3E 0J9  (Canada)


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2018-04-24 21:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24 21:54 Gilles Detillieux [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-04-18 14:48 Karl Peterson

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=6163af78-bce6-6e23-eb8f-4a7cc586f75a@scrc.umanitoba.ca \
    --to=grdetil@scrc.umanitoba.ca \
    --cc=cygwin@cygwin.com \
    --cc=karl.peterson@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).