public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Harold L Hunt II <huntharo@msu.edu> To: cygwin-xfree@cygwin.com Subject: Re: Crashing after two or three server resets Date: Sun, 11 Jan 2004 20:21:00 -0000 [thread overview] Message-ID: <4001B039.5090901@msu.edu> (raw) In-Reply-To: <20040111232749.FFA7.MURAKAMI@ipl.t.u-tokyo.ac.jp> Takuma, Takuma Murakami wrote: > The crash in fontdir.c have been there for a while. At least > most of xserv-2x releases have it. I challenged the problem > several times but I could neither fix, nor unveil how to > reproduce it. I think it occurred on the first reset as well > as plural resets. But it's not certain because I have not yet > encountered it with xorg-based servers. I think the first thing to do is just check if FreeFonts () is being called twice on some server resets. If it is, then the problem is simple: prevent it from being called twice. If FreeFonts () is not called twice, then the problem could be more difficult to track down. > Another problem on server reset is that Japanese keyboard > layout is ignored after server reset in XDMCP sessions. > I attach a patch for the problem. Now I'm missing where > the latest code resides, so I create it against xorg repository > on freedesktop.org. Yes, the latest code for Cygwin/X is in the xorg repository on freedesktop.org, you made your patch against the correct source. Thanks for the patch! By the way, is there anything that makes this just apply to Japanese keyboard layouts, or is it generally applicable to all keyboard layouts being lost on a server reset in Xdcmp sessions? Harold
next prev parent reply other threads:[~2004-01-11 20:21 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-11 3:12 Harold L Hunt II 2004-01-11 14:29 ` Takuma Murakami 2004-01-11 17:17 ` Alexander Gottwald 2004-01-11 17:27 ` Thomas Dickey 2004-01-11 18:00 ` Alexander Gottwald 2004-01-11 17:50 ` Alexander Gottwald 2004-01-11 20:21 ` Harold L Hunt II [this message] 2004-01-12 0:00 ` Alexander Gottwald
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=4001B039.5090901@msu.edu \ --to=huntharo@msu.edu \ --cc=cygwin-xfree@cygwin.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: linkBe 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).