*** This bug is a duplicate of bug 57586 ***
https://bugs.launchpad.net/bugs/57586
** This bug has been marked a duplicate of bug 57586
XEmacs segfaults on startup in Edgy
--
xemacs segfaults on edgy powerpc system
https://bugs.launchpad.net/bugs/58856
You received this bug notification
well, this bug is not confined to powerpc systems, and it still exists
on all machines that are upgraded from breezy to edgy. Please confirm
this bug and push it out to the X11 maintainers so they can check for
the condition of an upgrade and do something intelligent about the font
paths in the
Okay... I have a functional workaround for this bug, but the segfault
itself should still be pushed upstream so that the xemacs devs can fix
it. The application is choking when it can't populate a font struct
during initialisation; I guess they never try to clean up for this
condition, which is
this appears to duplicate the bug at:
https://launchpad.net/distros/ubuntu/+source/xemacs21/+bug/57586
... although the traces there aren't complete. I think these two reports
should be merged, and probably the bug marked as verified.
Brian
--
xemacs segfaults on edgy powerpc system
At the request of Mithrandir in #ubuntu-dev, I rebuilt my xemacs package
with unstripped binaries. This is the backtrace he requested.
Reading symbols from /usr/lib/libXaw.so.7...done.
Loaded symbols for /usr/lib/libXaw.so.7
Reading symbols from /usr/lib/libtiff.so.4...done.
Loaded symbols for
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
