12:28 p.m.
Hi,
System: Debian stable, with some add-on (KDE 3.1.3, kernel 2.4.20, etc...)
Xemacs from Debian stable packages
In terminal mode (not X-session) starts OK, but without graphic tool bars.
In terminal on X-session:
-------------------------------------------------------------------------------------------
debian:/home/oscar# xemacs&
[1] 1278
debian:/home/oscar# Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Initialization error: X server not responding
: ":0.0"
__________________________________________________
In terminal on X-session:
-------------------------------------------------------------------------------------------
oscar＠debian:~$ xemacs
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 `crashes(a)xemacs.org'.
*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" 0x25b5>)
frame-initialize()
# bind (debugger debug-on-error command-line-args-left)
command-line()
# (unwind-protect ...)
normal-top-level()
# (condition-case ... . error)
# (catch top-level ...)
Violación de segmento
oscar＠debian:~$ su
Password:
debian:/home/oscar# gdb /usr/bin/xemacs /dev/core
GNU gdb 5.3-debian
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-linux"...(no debugging symbols found)...
warning: core file may not match specified executable file.
Core was generated by `BOOT_IMAGE=Linux ro root=303 2.4.20'.
#0 0x00000000 in ?? ()
(gdb) where
#0 0x00000000 in ?? ()
(gdb)
------------------------------------------------------------------------------------------------
Thanks,
Oscar
12:39 a.m.
>>>> "Oscar" == Oscar Martín
<ombatres(a)ya.com> writes:
Oscar> debian:/home/oscar# Xlib: connection to ":0.0" refused by server
Root doesn't have permission to access the server. Not an XEmacs bug.
Oscar> oscar＠debian:~$ xemacs
Oscar> Warning: Missing charsets in String to FontSet conversion
Oscar> Warning: Unable to load any usable fontset
These warnings are probably harmless (you probably have a UTF-8 or
＠euro LANG set).
Oscar> # bind (frame-being-created)
Oscar> make-frame(nil #<x-device on ":0.0" 0x25b5>)
There have been a number of bugs that result in this signature fixed
in recent versions. Please do M-x report-xemacs-bug so that we get as
full environment and configuration information as possible.
Oscar> debian:/home/oscar# gdb /usr/bin/xemacs /dev/core
Nope, that's not a core file, that's core memory. The core file is a
regular file normally in the directory where you started XEmacs
(definitely not in /dev), and since you're running Debian, you
probably don't have a core file. Enable it with bash's "ulimit -c
unlimited" command.
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
7:22 p.m.
New subject: Missing fontsets, Xaw, UTF8 (was: Re: Xemacs don't start)
On Mon, 2003-10-27 at 02:39, Stephen J. Turnbull wrote:
>>>>> "Oscar" == Oscar Martín
<ombatres(a)ya.com> writes:
Oscar> oscar＠debian:~$ xemacs
Oscar> Warning: Missing charsets in String to FontSet conversion
Oscar> Warning: Unable to load any usable fontset
These warnings are probably harmless (you probably have a UTF-8 or
＠euro LANG set).
FWIW, I have en_US.UTF-8 and for 21.4.1[34] built with Xaw3d [1], the
attached patch suppresses the "Missing charsets" warning. Would it be
acceptable for inclusion?
[1] When built with Motif, those warnings didn't show up.
--- xemacs-21.4.13/etc/Emacs.ad~ 2002-12-12 08:21:12.000000000 +0200
+++ xemacs-21.4.13/etc/Emacs.ad 2003-07-13 19:47:48.000000000 +0300
＠＠ -203,11 +203,13 ＠＠
*menubar*FontSet: -*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*, \
-*-*-*-*-*-*-*-120-*-iso10646-1, \
-*-*-*-*-*-*-*-120-*-jisx0208.1983-0, \
- -*-*-*-*-*-*-*-120-*-jisx0201.1976-0
+ -*-*-*-*-*-*-*-120-*-jisx0201.1976-0, \
+ -*-*-*-*-*-*-*-120-*-*-*
*popup*FontSet: -*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*, \
-*-*-*-*-*-*-*-120-*-iso10646-1, \
-*-*-*-*-*-*-*-120-*-jisx0208.1983-0, \
- -*-*-*-*-*-*-*-120-*-jisx0201.1976-0
+ -*-*-*-*-*-*-*-120-*-jisx0201.1976-0, \
+ -*-*-*-*-*-*-*-120-*-*-*
! Gui elements share this font
!
8:58 p.m.
New subject: Missing fontsets, Xaw, UTF8 (was: Re: Xemacs don't start)
On Fri, 31 Oct 2003 21:22:30 +0200, Ville =?ISO-8859-1?Q?Skytt=E4?=
<scop(a)xemacs.org> said:
- -*-*-*-*-*-*-*-120-*-jisx0201.1976-0
+ -*-*-*-*-*-*-*-120-*-jisx0201.1976-0, \
+ -*-*-*-*-*-*-*-120-*-*-*
Gaak. Excuse me while I vomit.
This last means "pick any old font with ptSz=120" no matter how inappropriate
it is. And on my system, the font this gets ls <drum roll>:
-daewoo-gothic-medium-r-normal--16-120-100-100-c-160-ksc5601.1987-0
(I've attached a PNG of what xfontsel thinks of this font).
The reason this is silly is because if I didn't have daewoo fonts installed,
the font that would have been selected is:
-isas-fangsong ti-medium-r-normal--17-120-100-100-c-0-gb2312.1980-0
If we're going to patch this, let's either not be wildcarding it quite so much,
or add some code to tell us why there's a problem (see the 21.5 input-method-xlib.c
code for an example)
9:15 p.m.
New subject: Missing fontsets, Xaw, UTF8 (was: Re: Xemacs don't start)
On Fri, 2003-10-31 at 22:58, Valdis.Kletnieks(a)vt.edu wrote:
On Fri, 31 Oct 2003 21:22:30 +0200, Ville =?ISO-8859-1?Q?Skytt=E4?=
<scop(a)xemacs.org> said:
> - -*-*-*-*-*-*-*-120-*-jisx0201.1976-0
> + -*-*-*-*-*-*-*-120-*-jisx0201.1976-0, \
> + -*-*-*-*-*-*-*-120-*-*-*
Gaak. Excuse me while I vomit.
I kind of expected this, that's what the "FWIW" was there for ;)
This last means "pick any old font with ptSz=120" no matter
how inappropriate
it is.
I know, but what [I don't know is what really happens] if the
"catch-all" isn't there? Guess: the same thing, but with a "Missing
fontsets" warning? I just wanted to get rid of the warning because
things just seem to work with or without the patch and I didn't want to
see it any more :)
If we're going to patch this, let's either not be
wildcarding it quite so much,
or add some code to tell us why there's a problem (see the 21.5 input-method-xlib.c
code for an example)
Yep, a real fix would of course be very welcome.
1:11 p.m.
New subject: Missing fontsets, Xaw, UTF8
>>>> "Ville" == Ville Skytt <Ville>
writes:
> If we're going to patch this, let's either not be
wildcarding
> it quite so much, or add some code to tell us why there's a
> problem (see the 21.5 input-method-xlib.c code for an example)
Ville> Yep, a real fix would of course be very welcome.
Don't hold your breath, it's an XFree86 bug (IMHO). What's happening
is that XFree86 apparently deals with a "utf-8" character set, but
doesn't know what "ISO 10646-1" is. I don't understand how an
organization where Markus Kuhn regularly posts to its I18N list can
get I18N so wrong, but they do. :-(
Ville's patch isn't actually as bad as it looks because what actually
happens (in theory, remember we're talking XFree86 I18N here) is that
each charset used by the locale is matched against each XLFD. So
something like
-adobe-courier-medium-r-*--*-120-*-*-*-*-iso8859-*, (more stuff)
actually will start by collecting as many Latin-* Adobe Courier fonts
as are relevant to the locale (which for UTF-8 is all of them, even if
it's actually en_US.utf8, how broken do you want it, we can give it to
you ;-), then go on to handle (more stuff) in the same way for any
desired charsets not yet added to the X Font Set.
Still, it's really preferable to have the users, not us and not X,
making decisions about what fonts are (a) common (last ditch resort)
and (b) good-looking and common enough to deserve a try in the defaults.
The best way to suppress the warning is change LANG to something other
than *.utf8.
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
7692
days inactive
7698
days old
5 comments
4 participants
participants (4)
-
Oscar Martín -
Stephen J. Turnbull -
Valdis Kl=?iso8859-4?Q?=BA?=tnieks -
Ville Skyttä