update... Okay, I have relinked this package on my own system in a clean pbuilder chroot, and the symbol complaint is gone, but the failure is the same, although the stack trace seems to have moved out to another lib:
[fade]tantive:~ [Tue Sep 05 <15:44:03>]\>xemacs Warning: Cannot convert string "-*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*" to type FontStruct Warning: Unable to load any usable ISO8859 font Warning: Unable to load any usable ISO8859 font Fatal error (11). Your files have been auto-saved. Use `M-x recover-session' to recover them. [ ...snip xemacs generated debugging info/advice... ] Lisp backtrace follows: # bind (frame-being-created) make-frame(nil #<x-device on ":0.0" 0x322>) 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 ...) zsh: segmentation fault (core dumped) xemacs and this is the c stack trace from gdb: [Tue Sep 05 <15:44:15>]\>gdb /usr/bin/xemacs ./core GNU gdb 6.4.90-debian Copyright (C) 2006 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 "powerpc-linux-gnu"...(no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". Failed to read a valid object file image from memory. Core was generated by `xemacs'. Program terminated with signal 11, Segmentation fault. #0 0x0f7690d8 in ?? () (gdb) where #0 0x0f7690d8 in ?? () #1 0x10073c60 in xemacs_21_4_19_powerpc_debian_linux () #2 0x00100374 in ?? () #3 0x7f844e98 in ?? () #4 0x101c7f08 in xlw_display_menu () #5 0x0fd43b04 in ?? () #6 0x0fd447c4 in ?? () #7 0x0fd4522c in ?? () #8 0x0fd45660 in ?? () #9 0x101cb334 in xlw_pop_up_menu () #10 0x101c1458 in lw_internal_update_other_instances () #11 0x1009ebfc in console_type_create_toolbar_x () #12 0x1019b4b0 in x_any_window_to_frame () #13 0x100f4da8 in syms_of_general () #14 0x100f4da8 in syms_of_general () #15 0x100f4da8 in syms_of_general () #16 0x100f4da8 in syms_of_general () #17 0x100f4da8 in syms_of_general () #18 0x100f4da8 in syms_of_general () #19 0x100f4da8 in syms_of_general () #20 0x100f4da8 in syms_of_general () #21 0x100f4da8 in syms_of_general () #22 0x100f4da8 in syms_of_general () #23 0x100f4da8 in syms_of_general () #24 0x100f4da8 in syms_of_general () #25 0x100f4da8 in syms_of_general () #26 0x100f4da8 in syms_of_general () #27 0x100f4da8 in syms_of_general () #28 0x100f4da8 in syms_of_general () #29 0x100f4da8 in syms_of_general () #30 0x100f4da8 in syms_of_general () #31 0x100f4da8 in syms_of_general () #32 0x100f4da8 in syms_of_general () #33 0x100f4da8 in syms_of_general () #34 0x100f4da8 in syms_of_general () Previous frame inner to this frame (corrupt stack?) also interesting, and probably should be the subject of another bug report is that GNUEmacs fails in a very similar fasion with a complaint about fonts. In the GNUEmacs case, however, the frame comes up, but it is full of hollow rectangles instead of glyphs. Here is the stderr output from a terminal starting emacs: Warning: Cannot convert string "-*-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-*" to type FontStruct Warning: Unable to load any usable ISO8859 font Warning: Cannot convert string "-*-helvetica-medium-r-*--*-120-*-*-*-*-iso8859-1" to type FontStruct Warning: Unable to load any usable ISO8859 font Warning: Unable to load any usable ISO8859 font I have attached a screenshot of the resulting emacs frame. ** Attachment added: "screenshot of an emacs frame without any useful fonts." http://librarian.launchpad.net/4132345/bad_emacs.png -- xemacs segfaults on edgy powerpc system https://launchpad.net/bugs/58856 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
