Subject: xemacs21-mule: xemacs-mule segfaults because of "missing charsets"
Date: Tue, 12 Feb 2002 21:33:18 +0200
Package: xemacs21-mule
Version: 21.4.6-7
Severity: grave
Justification: renders package unusable
I got this when I try to start xemacs under X:
(typing "xemacs" in commandline)
---------------------------------------------
Warning: Missing charsets in String to FontSet conversion
Warning: Unable to load any usable fontset
Fatal error (11).
Your files have been auto-saved.
Use M-x recover-session' to recover them.
If you have access to the PROBLEMS file that came with your
version of XEmacs, please check to see if your crash is described
there, as there may be a workaround available.
Otherwise, please report this bug by running the send-pr
script included with XEmacs, or selecting Send Bug Report'
from the help menu.
As a last resort send ordinary email to [email protected]'.
*MAKE SURE* to include the information in the command
M-x describe-installation.
If at all possible, *please* try to obtain a C stack backtrace;
it will help us immensely in determining what went wrong.
To do this, locate the core file that was produced as a result
of this crash (it's usually called core' and is located in the
directory in which you started the editor, or maybe in your home
directory), and type
gdb /usr/bin/xemacs core
then type where' when the debugger prompt comes up.
(If you don't have GDB on your system, you might have DBX,
or XDB, or SDB. A similar procedure should work for all of
these. Ask your system administrator if you need more help.)
Lisp backtrace follows:
# bind (frame-being-created)
make-frame(nil #<x-device on ":0.0" 0x2411>)
frame-initialize()
# bind (debugger debug-on-error command-line-args-left)
command-line()
# (unwind-protect ...)
normal-top-level()
# (condition-case ... . error)
# (catch top-level ...)
Segmentation fault
-------------------------------------------------
So the program is unusable in X.
It works under text terminal. Xemacs-nomule works both in X and
text mode.
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux val030 2.4.9own #1 to syys 6 20:39:47 EEST 2001 i686
Locale: LANG=C, LC_CTYPE=fi_FI
Versions of packages xemacs21-mule depends on:
ii emacsen-common 1.4.13 Common facilities for all emacsen.
ii libc6 2.2.5-3 GNU C Library: Shared libraries an
ii libcompfaceg1 1989.11.11-23 Compress/decompress images for mai
ii libdb3 3.2.9-14 Berkeley v3 Database Libraries [ru
ii libjpeg62 6b-5 The Independent JPEG Group's JPEG
ii libldap2 2.0.14-1.1 OpenLDAP libraries.
ii libncurses5 5.2.20020112a-3 Shared libraries for terminal hand
ii libpng2 1.0.12-3 PNG library - runtime
ii libtiff3g 3.5.5-6 Tag Image File Format library
ii libxaw7 4.1.0-13 X Athena widget set library
ii xemacs21-basesupport 2001.12.16-1 Editor and kitchen sink -- compile
ii xemacs21-bin 21.4.6-7 Editor and kitchen sink -- support
ii xemacs21-mulesupport 2001.12.16-1 Editor and kitchen sink -- Mule el
ii xemacs21-support 21.4.6-7 Editor and kitchen sink -- archite
ii xlibs 4.1.0-13 X Window System client libraries
ii zlib1g 1:1.1.3-19 compression library - runtime
Subject: Re: Bug#133607: xemacs21-mule: xemacs-mule segfaults because of
"missing charsets"
Date: Tue, 12 Feb 2002 15:06:10 -0500
>>>>> On Tue, 12 Feb 2002 21:33:18 +0200, Eeli K <[email protected]> said:
Eeli> Package: xemacs21-mule Version: 21.4.6-7 Severity: grave
Eeli> Justification: renders package unusable
Eeli> I got this when I try to start xemacs under X: (typing "xemacs"
Eeli> in commandline)
Can you run "xrdb -query | grep macs" and run xemacs as "xemacs
-vanilla" and send me the output for each?
Thanks
Jim
--
@James LewisMoss <[email protected]> | Blessed Be!
@ http://jimdres.home.mindspring.com | Linux is kewl!
@"Argue for your limitations and sure enough, they're yours." Bach
Subject: Re: Bug#133607: xemacs21-mule: xemacs-mule segfaults because of
"missing charsets"
Date: Wed, 13 Feb 2002 01:00:08 +0200
On Tue, 12 Feb 2002, James LewisMoss wrote:
>
> Can you run "xrdb -query | grep macs" and run xemacs as "xemacs
> -vanilla" and send me the output for each?
>
xrdb -query gives nothing (even without grep).
xemacs -vanilla produces exactly the same output than plain xemacs.
I'm not sure if the problem is due to locale or fonts, but here is
some info:
I have a normal testing distribution. All the normal X packages should
be installed, also the font packages. My locale gives:
LANG=C
LC_*="fi_FI"
Sincerely Yours,
Eeli Kaikkonen <[email protected]> Suomi Finland
Subject: Re: Bug#133607: xemacs21-mule: xemacs-mule segfaults because of
"missing charsets"
Date: Thu, 07 Mar 2002 09:54:47 -0500
>>>>> On Thu, 7 Mar 2002 14:57:10 +0200, Eeli Kaikkonen <[email protected]> said:
Eeli> On Fri, 1 Mar 2002, James LewisMoss wrote:
>>
>> OK. I set all my LC env vars to fi_FI and LANG to C and it ran as
>> "xemacs -vanilla" so I've gotta assume I need a font package
>> dependency on xemacs21-mule. Can you try setting the following x
>> resources and see if the problem goes away:
>>
>> XEmacs*fontSet: -*-lucidatypewriter-bold-r-normal-*-10-*
>>
Eeli> Sorry about this taking so long.
Eeli> Resource did not help, but now I noticed that when I run
Eeli> xfontsel from commandline it says:
Eeli> Warning: Missing charsets in String to FontSet conversion
Eeli> Warning: Unable to load any usable fontset
Eeli> Just like when I tried to open xemacs. So, maybe I have some
Eeli> personal trouble with my fonts.
Please keep me informed of anything you find out and if you don't mind
I'm going to drop the severity to normal on the bug until that time.
Let me know.
Thanks
Jim
--
@James LewisMoss <[email protected]> | Blessed Be!
@ http://jimdres.home.mindspring.com | Linux is kewl!
@"Argue for your limitations and sure enough, they're yours." Bach
Subject: Re: Bug#133607: xemacs21-mule: xemacs-mule segfaults because of
"missing charsets"
Date: Thu, 7 Mar 2002 17:12:44 +0200
On Thu, 7 Mar 2002, James LewisMoss wrote:
>
> Please keep me informed of anything you find out and if you don't mind
> I'm going to drop the severity to normal on the bug until that time.
> Let me know.
>
I just re-installed X fonts. I found out that installing
xfonts-base-transcoded and xfonts-100dpi-transcoded resolved the problem.
I have "fi_FI@euro ISO-8859-15" in my /etc/locale.gen. Maybe that have
something to do with the problem, because there is no iso-8859-15 in
ordinary xfonts packages? Probably this should be reported somewhere,
but I don't know where.
Sincerely Yours,
Eeli Kaikkonen <[email protected]> Suomi Finland
Subject: Re: Bug#133607: xemacs21-mule: xemacs-mule segfaults because of
"missing charsets"
Date: Thu, 07 Mar 2002 10:37:43 -0500
>>>>> On Thu, 7 Mar 2002 17:12:44 +0200, Eeli Kaikkonen <[email protected]> said:
Eeli> On Thu, 7 Mar 2002, James LewisMoss wrote:
>>
>> Please keep me informed of anything you find out and if you don't
>> mind I'm going to drop the severity to normal on the bug until
>> that time. Let me know.
>>
Eeli> I just re-installed X fonts. I found out that installing
Eeli> xfonts-base-transcoded and xfonts-100dpi-transcoded resolved
Eeli> the problem.
So you installed these packages new (rather than an update) and the
problem went away?
Eeli> I have "fi_FI@euro ISO-8859-15" in my /etc/locale.gen. Maybe
Eeli> that have something to do with the problem, because there is no
Eeli> iso-8859-15 in ordinary xfonts packages? Probably this should
Eeli> be reported somewhere, but I don't know where.
I'm not sure, but I'm forwarding this to the debian X mailing list
hoping someone there has some wisdom.
Jim
--
@James LewisMoss <[email protected]> | Blessed Be!
@ http://jimdres.home.mindspring.com | Linux is kewl!
@"Argue for your limitations and sure enough, they're yours." Bach
Subject: Re: Bug#133607: xemacs21-mule: xemacs-mule segfaults because of
"missing charsets"
Date: 07 Mar 2002 17:01:49 +0100
On Don, 2002-03-07 at 16:37, James LewisMoss wrote:
> >>>>> On Thu, 7 Mar 2002 17:12:44 +0200, Eeli Kaikkonen <[email protected]> said:
>
> Eeli> On Thu, 7 Mar 2002, James LewisMoss wrote:
> >>
> >> Please keep me informed of anything you find out and if you don't
> >> mind I'm going to drop the severity to normal on the bug until
> >> that time. Let me know.
> >>
>
> Eeli> I just re-installed X fonts. I found out that installing
> Eeli> xfonts-base-transcoded and xfonts-100dpi-transcoded resolved
> Eeli> the problem.
>
> So you installed these packages new (rather than an update) and the
> problem went away?
>
> Eeli> I have "fi_FI@euro ISO-8859-15" in my /etc/locale.gen. Maybe
> Eeli> that have something to do with the problem, because there is no
> Eeli> iso-8859-15 in ordinary xfonts packages? Probably this should
> Eeli> be reported somewhere, but I don't know where.
>
> I'm not sure, but I'm forwarding this to the debian X mailing list
> hoping someone there has some wisdom.
This is documented in the xfonts-* package descriptions.
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
I suddenly experienced very much this bug after an apt-get
dist-upgrade about one week ago, after some package quite unrelated to
xemacs was updated (I run sid on my laptop). After MUCH fiddling with
strace, I found out that for some reason there were some dangling symlinks
to some truetype fonts, both the X server (which loads the xtt module) and
the xfs-xtt font server tried to open them and, upon failing, xemacs died
with a segfault, after saying it could not find the character map for the
fontset. Fixing those dangling symlinks cured the problem completely, but
still I think that no program should segfault upon being unable to load a
font, should it?
Now, to reproduce this you can:
1) find some truetype fonts of the Lucida family and properly install them
2) turn some of them into dangling symlinks, so that they are not found
anymore
-> xemacs21-mule should now segfault.
If/when you can reproduce this, you can try to understand whether this bug
belongs to xemacs21-mule or to the xlibs.
Let me know whether I can help you with any more information.
Bye
Giacomo
--
_________________________________________________________________
Giacomo Mulas <[email protected], [email protected]>
_________________________________________________________________
OSSERVATORIO ASTRONOMICO DI CAGLIARI
Str. 54, Loc. Poggio dei Pini * 09012 Capoterra (CA)
Tel.: +39 070 71180 206 Fax : +39 070 71180 222
_________________________________________________________________
"When the storms are raging around you, stay right where you are"
(Freddy Mercury)
_________________________________________________________________
Subject: Re: Bug#133607: one more piece of information...
Date: Mon, 18 Mar 2002 10:06:19 -0500
>>>>> On Mon, 18 Mar 2002 15:33:25 +0100 (CET), Giacomo Mulas <[email protected]> said:
Giacomo> I suddenly experienced very much this bug after an
Giacomo> apt-get
Giacomo> dist-upgrade about one week ago, after some package quite
Giacomo> unrelated to xemacs was updated (I run sid on my
Giacomo> laptop). After MUCH fiddling with strace, I found out that
Giacomo> for some reason there were some dangling symlinks to some
Giacomo> truetype fonts, both the X server (which loads the xtt
Giacomo> module) and the xfs-xtt font server tried to open them and,
Giacomo> upon failing, xemacs died with a segfault, after saying it
Giacomo> could not find the character map for the fontset. Fixing
Giacomo> those dangling symlinks cured the problem completely, but
Giacomo> still I think that no program should segfault upon being
Giacomo> unable to load a font, should it?
Nope it shouldn't, but I'd appreciate you filing a bug against the
package leaving the dangling symlinks as well.
Giacomo> Now, to reproduce this you can:
Giacomo> 1) find some truetype fonts of the Lucida family and
Giacomo> properly install them
Giacomo> 2) turn some of them into dangling symlinks, so that they
Giacomo> are not found
Giacomo> anymore
-> xemacs21-mule should now segfault.
Giacomo> If/when you can reproduce this, you can try to understand
Giacomo> whether this bug belongs to xemacs21-mule or to the xlibs.
I'll do my best. If I can't figure it out i'll pass it upstream.
Giacomo> Let me know whether I can help you with any more
Giacomo> information.
This is excellent info. Thanks.
Jim
--
@James LewisMoss <[email protected]> | Blessed Be!
@ http://jimdres.home.mindspring.com | Linux is kewl!
@"Argue for your limitations and sure enough, they're yours." Bach
forcemerge 133607 56542 153040 160973 182971 258572 303103 363246 369165 382701 396182
forcemerge 356584 396182
found 133607 21.4.19-2
thanks
I merged all "Segfault on startup" bug reports on xemacs21(-mule) with
"Fatal error (11)." after "Warning: Unable to load any usable fontset".
Since the oldest of the original merge was 133607, I made this merging
around it.
Buy reading all these bug reports over 5 years, I could not find fix
yet. But reducing fonts seems to fix situation as of now. This is
pretty pathetic situation for basic package such as xemacs being so
fragile. It should at least should not segfaults and should produce
meaningful error message.
Following are my review of all these bugs.
-----------------------------------------------------------------------
I have the same xemacs crash issue here under en_US.UTF-8 locale for
xemacs21-mule 21.4.19-2 while my input method is SCIM via XIM and
freetype is used instead of xtt per debconf question default. Let me
recap basic segfault situation here:
* Starting with "LANG=C xemacs" in X brings out X version OK.
* Starting with "LANG=en_US xemacs" in X brings out X version OK.
* Starting with "xemacs -nw" in X brings out no-X version OK.
* Starting with "xemacs" in X segfaults. (See below log)
* Starting with "xemacs -q" in X segfaults.
* Starting with "LANG=ja_JP.UTF-8 xemacs" in X segfaults too.
* Starting with "xemacs" in Linux console brings out no-X version OK.
It seems problem happens when system is loaded with many fonts (my font
situation is listed below.) some of which may be causing some minor
troubles then xemacs exits with segfaults without useful messages.
Since this was reported repeatedly over 6 years without fix and many
reports come from DD, this is not so rare problem.
Since I am not having problem with gvim, this is not necessary a problem
which can be worked around nicely.
(emacs21 now fails to start nicely either but at least it does not
segfaults. See http://bugs.debian.org/405952 )
Although I am not inflating severity of this bug, since UTF-8 is now the
default for etch that prompt more fonts loaded by the Asian uses, this
kind of situation is very undesirable for release.
Since so many bug was filed on seemingly the same issue, let me
summarize them all here. I marked bug reports with "backtrace" and
listed bug submitter email address which were DD (CCed).
(Lines started with "| " are quotation.)
* http://bugs.debian.org/56542 (backtrace) locale=C and en_GB.ISO-8859-1
[email protected]
This is very old bug report from 28 Jan 2000.
Package name then was xemacs21.
Possibly related to the rest of the "segfault on startup bug" reports.
* http://bugs.debian.org/133607 locale=C and fi_FI
Missing required fonts for particular locale [email protected] was
one cause.
"dangling symlinks to some truetype fonts" was identified as a
possible another cause of the segfault.
* http://bugs.debian.org/153040 (backtrace)
[email protected]
There is a suggestion to run "dpkg-reconfigure x-ttcidfont-conf" in this
thread. In my case, it caused following funny errors on my system.
| Can't exec "/usr/bin/mkcfm": No such file or directory at /var/lib/defoma/scripts/x-ttcidfont-conf.defoma line 791.
| ...
| Can't exec "/usr/bin/mkcfm": No such file or directory at /var/lib/defoma/scripts/x-ttcidfont-conf.defoma line 791.
Here line 791 is:
system('/usr/bin/mkcfm', "$PkgDir/dirs/CID");
Hmmm... suspicious system inconsistency on my system.
I also switched to xtt from freetype, things did not change at all.
* http://bugs.debian.org/160973 (backtrace)
Quick fix suggested as:
| apt-get --purge remove 'xfonts*'; rm -f /usr/lib/X11R6/lib/X11/fonts/* and
| then re-install of all xfonts seems to fix the problem.
I tried this as the last resort after everything else. Restarting X
seems to be fixed situation. See below for reduced fonts after this.
xemacs started OK but still output funny message.
| Warning: Missing charsets in String to FontSet conversion
| Warning: Missing charsets in String to FontSet conversion
| Warning: Unable to load any usable fontset
* http://bugs.debian.org/182971 LANG=C, LC_CTYPE=de_DE@euro
[email protected]
* http://bugs.debian.org/258572 en_IE.UTF-8
* http://bugs.debian.org/303103 en_US.UTF-8
Workaround and bug source are reported to be identified.
By adding following 2 line to ~/.Xresources by getting hint from this
bug reports (with few more fixes):
| Emacs*menubar*FontSet: -*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*, \
| -*-*-*-*-*-*-*-120-*-*-*-*-iso10646-1, \
| -*-*-*-*-*-*-*-120-*-*-*-*-jisx0208.1983-0, \
| -*-*-*-*-*-*-*-120-*-*-*-*-jisx0201.1976-0
| Emacs*popup*FontSet: -*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*, \
| -*-*-*-*-*-*-*-120-*-*-*-*-iso10646-1, \
| -*-*-*-*-*-*-*-120-*-*-*-*-jisx0208.1983-0, \
| -*-*-*-*-*-*-*-120-*-*-*-*-jisx0201.1976-0
then this did not work. So I tried simple iso8859 only as below:
| Emacs*menubar*FontSet: -*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*
| Emacs*popup*FontSet: -*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*
xemacs start OK with this workaround but still complains:
| Warning: Missing charsets in String to FontSet conversion
| Warning: Missing charsets in String to FontSet conversion
| Warning: Unable to load any usable fontset
Now quite useful but not quite right since this prevent displaying
non-ASCII like Japanese etc (Hmmm... message is in English now)
By starting it under ja_JP.UTF-8, I get Japanese message on screen but
menu was still in English. Besides, I get error message reported in
356584 and 396182.
| (1) (xim-xlib/warning) Can't get fontset resource for Input Method
* http://bugs.debian.org/363246 (backtrace)
LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (???)
xfontsel program comparison was mentioned on this bug report. It gives
interesting view over the font situation. Here on my system:
| $ LANG=C xfontsel
| ...(start nicely in X)
| $ xfontsel
| ...(start OK in X but put out following to the console)
| Warning: Missing charsets in String to FontSet conversion
| Warning: Unable to load any usable fontset
Enabling xtt freetype to avoid crash was suggested on BTS. But why we
need it if we can fix it with correct font path?
* http://bugs.debian.org/369165 (intensive backtrace info)
LANG=C, LC_CTYPE=en_US.UTF-8
* http://bugs.debian.org/382701 (backtrace but missing symbol) en_US.UTF-8
Similar but error with input method...:
* http://bugs.debian.org/356584 fi_fi.utf8
this is very similar bug but it has extra message of "can't get
fontset resource for input method". not merged but watched.
* http://bugs.debian.org/396182 de_de.utf-8
"(xim-xlib/warning) Can't get fontset resource for Input Method"
(I will keep these 2 bunches of bugs separate but I will close both
bunch with attached patch.)
Related bug reports:
* http://bugs.debian.org/363667 emacs21
* http://bugs.debian.org/363664 emacs21
* http://bugs.debian.org/362894 x11-common
* http://bugs.debian.org/405952 emacs21
Unrelated bug reports (but kind of similar):
* http://bugs.debian.org/382427 (backtrace, different problem)
============== segfault message log of current situation ===============
Script started on Mon 08 Jan 2007 10:43:12 AM JST
osamu@dambo: ~xemacs
Warning: Missing charsets in String to FontSet conversion
Warning: Cannot convert string "-*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*, -*-*-*-*-*-*-*-120-*-iso10646-1, -*-*-*-*-*-*-*-120-*-jisx0208.1983-0, -*-*-*-*-*-*-*-120-*-jisx0201.1976-0" to type FontSet
Warning: Missing charsets in String to FontSet conversion
Warning: Unable to load any usable fontset
Warning: Missing charsets in String to FontSet conversion
Warning: Unable to load any usable fontset
Fatal error (11).
Your files have been auto-saved.
Use `M-x recover-session' to recover them.
Your version of XEmacs was distributed with a PROBLEMS file that may describe
your crash, and with luck a workaround. Please check it first, but do report
the crash anyway. Please report this bug by invoking M-x report-emacs-bug,
or by selecting `Send Bug Report' from the Help menu. If necessary, send
ordinary email to `[email protected]'. *MAKE SURE* to include the XEmacs
configuration from M-x describe-installation, or equivalently the file
Installation in the top of the build tree.
*Please* try *hard* to obtain a C stack backtrace; without it, we are unlikely
to be able to analyse the problem. Locate the core file produced as a result
of this crash (often called `core' or `core.<process-id>', and located in
the directory in which you started XEmacs or your home directory), and type
gdb /usr/bin/xemacs core
then type `where' at the debugger prompt. No GDB on your system? You may
have DBX, or XDB, or SDB. (Ask your system administrator if you need help.)
If no core file was produced, enable them (often with `ulimit -c unlimited'
in case of future recurrence of the crash.
Lisp backtrace follows:
# bind (frame-being-created)
make-frame(nil #<x-device on ":0.0" 0xb10>)
frame-initialize()
# bind (debugger debug-on-error command-line-args-left)
command-line()
# (condition-case ... . ((t (byte-code " §" ... 1))))
# bind (error-data)
normal-top-level()
# (condition-case ... . error)
# (catch top-level ...)
Segmentation fault
osamu@dambo:~$ exit
Script done on Mon 08 Jan 2007 10:43:24 AM JST
(Trailing ^M removed.)
Here, at condition-case line has a funny binary sequence of
00000830 2E 20 2E 20 │ 28 28 74 20 │ 28 62 79 74 │ 65 2D 63 6F . . ((t (byte-co
00000840 64 65 20 22 │ 09 10 81 C2 │ 8F A7 22 20 │ 2E 2E 2E 20 de "...Â.§" ...
00000850 31 29 29 29 │ 29 0D 0A 20 │ 20 23 20 62 │ 69 6E 64 20 1)))).. # bind
I have following xfont* installed:
ii xfonts-100dpi 1.0.0-3 100 dpi fonts for X
ii xfonts-75dpi 1.0.0-3 75 dpi fonts for X
ii xfonts-a12k12 1-8 12-dot Kanji & ASCII fonts for X
ii xfonts-ayu 1.7+0a+0debian1-2 Gothic 18/20 dot Japanese and ISO-8859-1 X11
ii xfonts-baekmuk 2.2-2.1 BAEKMUK Korean fonts for X
ii xfonts-base 1.0.0-4 standard fonts for X
ii xfonts-encodings 1.0.0-6 Encodings for X.Org fonts
ii xfonts-intl-chinese 1.2.1-6 International fonts for X -- Chinese
ii xfonts-intl-chinese-big 1.2.1-6 International fonts for X -- Chinese big
ii xfonts-intl-japanese 1.2.1-6 International fonts for X -- Japanese
ii xfonts-intl-japanese-big 1.2.1-6 International fonts for X -- Japanese big
ii xfonts-kaname 1.1-9 Kaname Cho 12 dot Japanese Kanji, Latin 1 fo
ii xfonts-kappa20 0.396-3 X11 Kappa 20dot Fonts (ISO-8859-1..4/9/10/13
ii xfonts-marumoji 0.2-7 Roundish fonts (marumoji fonts) for X
ii xfonts-mona 2.21-4 proportional fonts for 2ch ASCII art
ii xfonts-mplus 2.2.4-1 M+ bitmap 10/12 dot Latin/Japanese fonts for
ii xfonts-scalable 1.0.0-6 scalable fonts for X
ii xfonts-shinonome 5-1.1 Various 12,14,16 dot Japanese Kanji, iso8859
ii xfonts-utils 1.0.1-1 X Window System font utility programs
--->> After reinstalling fonts
ii xfonts-100dpi 1.0.0-3 100 dpi fonts for X
ii xfonts-75dpi 1.0.0-3 75 dpi fonts for X
ii xfonts-base 1.0.0-4 standard fonts for X
ii xfonts-encodings 1.0.0-6 Encodings for X.Org fonts
ii xfonts-scalable 1.0.0-6 scalable fonts for X
ii xfonts-utils 1.0.1-1 X Window System font utility programs
--
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +++++
Osamu Aoki <[email protected]> Yokohama Japan, GPG-key: A8061F32
.''`. Debian Reference: post-installation user's guide for non-developers
: :' : http://qref.sf.net and http://people.debian.org/~osamu
`. `' "Our Priorities are Our Users and Free Software" --- Social Contract
Hi,
When I wrote previous bug report, I forgot to update 2 lines.
I initially thougt changing fontpath name suggested by
http://bugs.debian.org/303103 fixes these bugs but it did not. Instead
reducing installed fonts fixed it.
Considering this, the following 2 lines from the previous report:
(I will keep these 2 bunches of bugs separate but I will close both
bunch with attached patch.)
should be replaced by
(I will keep these 2 bunches of bugs separate so they can be closed
separastely or together by the maintainer.)
Osamu
reassign 133607 xemacs21-mule
reassign 56542 xemacs21-mule
reassign 153040 xemacs21-mule
reassign 160973 xemacs21-mule
reassign 182971 xemacs21-mule
reassign 258572 xemacs21-mule
reassign 303103 xemacs21-mule
reassign 382701 xemacs21-mule
forcemerge 133607 56542 153040 160973 182971 303103 363246 369165 382701
thanks
Hi,
when I wrore previous message, I thought forcemerge will merge all bugs
under the same source tree but it was for binary package. It is a bit
more careful :-)
Thus I an sending this BTS clean up message again.
Basically, apt-get install xemacs21 installs xemacs21-mule as default.
Unless explicitly identified otherwise, I assumed this family of bug
symptom is -mule thing due to the reference to the complicated font
scheme.
As reported in 160973 segfault bug is in the binary provided by the
-mule while -nomule still is not perfect. (I have not tested
xemacs21-gnome-mule-canna-wnn under tough font environment). So I will
merge all these bugs under -mule. xemacs21 is just dummy binary
package.
303103 was filed under xemacs21-bin but its report contents point to -mule.
258572 was -mule bug but I was not 100% sure this is the same as others.
So I dropped it from merge.
--
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +++++
Osamu Aoki <[email protected]> Yokohama Japan, GPG-key: A8061F32
.''`. Debian Reference: post-installation user's guide for non-developers
: :' : http://qref.sf.net and http://people.debian.org/~osamu
`. `' "Our Priorities are Our Users and Free Software" --- Social Contract
As I read back my summary, I realize that I do not have CID font now on
system and problem is gone.
As I wrote:
| * http://bugs.debian.org/153040 (backtrace)
| [email protected]
| There is a suggestion to run "dpkg-reconfigure x-ttcidfont-conf" in this
| thread. In my case, it caused following funny errors on my system.
|
| | Can't exec "/usr/bin/mkcfm": No such file or directory at /var/lib/defoma/scripts/x-ttcidfont-conf.defoma line 791.
| | ...
| | Can't exec "/usr/bin/mkcfm": No such file or directory at /var/lib/defoma/scripts/x-ttcidfont-conf.defoma line 791.
|
| Here line 791 is:
| system('/usr/bin/mkcfm', "$PkgDir/dirs/CID");
|
| Hmmm... suspicious system inconsistency on my system.
This may be the source of problem.
--
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +++++
Osamu Aoki <[email protected]> Yokohama Japan, GPG-key: A8061F32
.''`. Debian Reference: post-installation user's guide for non-developers
: :' : http://qref.sf.net and http://people.debian.org/~osamu
`. `' "Our Priorities are Our Users and Free Software" --- Social Contract
Subject: xemacs21-mule segfault -- avoided for now....
Date: Wed, 10 Jan 2007 23:25:50 +0900
Hmmm.... Now I see what has happened.
In short, the bug of xemacs21-mule is fragility of handling buggy/broken
font situation.
As I checked and confirmed that /usr/bin/mkcfm is missing on my system.
This is a program to generate font metrics file for adobe CID fonts
(Asian PS fonts http://en.wikipedia.org/wiki/CID_fonts ). So noise over
mkcfm with x-ttcidfont -conf was caused by this missing mkcfm.
Then I found that debian changelog "xorg (7.0.0-0ubuntu1) dapper;
urgency=low which removed mkcfm. Also upstrean dropped it.
https://bugs.freedesktop.org/show_bug.cgi?id=5553
So CID font is not supported under current X and Type 1 font is not
used.
Since I may have had some old CID fonts before and may have been removed
them. Then, due to missing mkcfm, the generated font metrics file etc
was out of sync with the current reality. That was buggy font
situation. Now that I am CID font free, I am safe.
This is quite consistent with how the previous bug reports ended. For
msttcorefonts reinstall fixed situation etc. Most reports seem to be
fixed when font is reinstalled etc. This also explains why bug was not
reproducible.
My guess from FDT 5553 bug discussion is that the avoiding of Type1
fonts (Including CID ones) altogether in the xemacs may fix this
situation. According to this discussion, error handling of this font is
"abort" and that may be the cause of segfault.
Anyway, I have usable xemacs21-mule now. (emacs21-mule under X still
has funny boxes. That seems different problem.)
Osamu
--
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +++++
Osamu Aoki <[email protected]> Yokohama Japan, GPG-key: A8061F32
.''`. Debian Reference: post-installation user's guide for non-developers
: :' : http://qref.sf.net and http://people.debian.org/~osamu
`. `' "Our Priorities are Our Users and Free Software" --- Social Contract
Subject: xemacs21-mule segfault - found a workaround
Date: Fri, 06 Jul 2012 10:51:23 +0200
Hi,
I also suffered from this problem on Debian squeeze:
"Warning: Cannot convert string
"-*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*" to type FontStruct
Warning: Missing charsets in String to FontSet conversion
Warning: Cannot convert string
"-*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*,
-*-*-*-*-*-*-*-120-*-iso10646-1,
-*-*-*-*-*-*-*-120-*-jisx0208.1983-0,
-*-*-*-*-*-*-*-120-*-jisx0201.1976-0" to type FontSet
Warning: Missing charsets in String to FontSet conversion
Warning: Unable to load any usable fontset
Warning: Missing charsets in String to FontSet conversion
Warning: Unable to load any usable fontset
Fatal error (11)."
I found a workaround, but this workaround may not work for others though
as the system setup I use is a bit special: I use NX
(http://www.nomachine.com, it's a remote control software) to connect to
the PC on which I use Debian/xemacs. NX adds its own fonts to the font path.
Anyway, the workarounds I found are:
- "export LANG=C;xemacs" by default I use de_DE.UTF-8 LANG
- "xset fp default; xemacs" when I check with "xset q" the font path
before and after the difference is that the entry
/usr/NX/share/fonts/TTF/ right at the beginning of the font path gets
removed. The fonts.dir file in that directory looks like this:
luximr.ttf -b&h-Luxi Mono-medium-r-normal--0-0-0-0-m-0-iso8859-1
[...]
luximb.ttf -b&h-Luxi Mono-bold-r-normal--0-0-0-0-m-0-iso8859-1
[...]
[and so on]
This directory includes a few fonts of the luxi fonts family, so it
looks like those fonts are causing this problem. xemacs21-nomule works
fine without any workaround.
Frank
Subject: Bug#725883: Removed package(s) from unstable
Date: Sun, 13 Oct 2013 09:54:29 +0000
Version: 21.4.22-4+rm
Dear submitter,
as the package xemacs21 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see http://bugs.debian.org/725883
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)
Debbugs is free software and licensed under the terms of the GNU General
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.