From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25090 invoked by alias); 3 Aug 2010 13:46:39 -0000 Received: (qmail 25070 invoked by uid 22791); 3 Aug 2010 13:46:37 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Received: from mail-qw0-f43.google.com (HELO mail-qw0-f43.google.com) (209.85.216.43) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 03 Aug 2010 13:46:32 +0000 Received: by qwd6 with SMTP id 6so2789282qwd.2 for ; Tue, 03 Aug 2010 06:46:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.233.142 with SMTP id jy14mr1157525qcb.77.1280843190853; Tue, 03 Aug 2010 06:46:30 -0700 (PDT) Received: by 10.229.230.137 with HTTP; Tue, 3 Aug 2010 06:46:30 -0700 (PDT) In-Reply-To: <4C581B24.6050705@dronecode.org.uk> References: <4C57DA24.8090205@ece.cmu.edu> <20100803045917.V3933@mail101.his.com> <4C581B24.6050705@dronecode.org.uk> Date: Tue, 03 Aug 2010 13:46:00 -0000 Message-ID: Subject: Re: Missing charsets in String to FontSet conversion From: Andy Koppe To: cygwin-xfree@cygwin.com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Reply-To: cygwin-xfree@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com X-SW-Source: 2010-08/txt/msg00007.txt.bz2 On 3 August 2010 14:35, Jon TURNEY wrote: > On 03/08/2010 10:00, Thomas Dickey wrote: >> >> On Tue, 3 Aug 2010, Ryan Johnson wrote: >>> >>> At some point an annoyance appeared with my xterm windows: The first time >>> I >>> use [ctrl]+mouse click in any window, that xterm becomes unresponsive for >>> about 5 seconds with the CPU pegged to 100%. After the five seconds is >>> up, >>> whatever shell spawned the xterm receives the following message: >>>> >>>> Warning: Missing charsets in String to FontSet conversion >>> >>> After that all works normally (until I open the next xterm window). >>> >>> Is there a way to diagnose what the problem is? I don't know what FontSet >>> string the error even refers to, let alone which parts of that string >>> were >>> invalid. In any case, it really shouldn't take five seconds of hard CPU >>> crunching to detect and report an invalid input string. > > There's some more discussion at > http://sourceware.org/bugzilla/show_bug.cgi?id=10948 > > Installing the fonts font-isas-misc, font-jis-misc and font-daewoo-misc > should also work around the problem, which can also be seen with other > applications, as that ensures that at least one font exists for every > charset. > > I agree that the error message sucks and should tell you the charsets which > are missing and what string it was attempting to convert. > >> This topic came up last year, iirc the issue was this: >> >> http://invisible-island.net/xterm/xterm.faq.html#slow_menus Could the menuLocale resource setting mentioned there be added to Cygwin xterm's default config at /etc/X11/app-defaults/XTerm? Andy -- 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/