Bug 185140

Summary: M-x man netstat in 'xemacs -f shell' gives a segmentation fault
Product: [Fedora] Fedora Reporter: Will Partain <will>
Component: xemacsAssignee: Ville Skyttä <scop>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: petersen
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-03-13 07:14:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Will Partain 2006-03-10 21:19:06 UTC
Description of problem:
XEmacs crashes whenever I do 'M-x man <return> netstat <return>'

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. start up: xemacs -f shell
2. M-x man RET netstat RET
Actual results:
xemacs crashes

Expected results:

Additional info:
Obviously, there may be something weird in my xemacs setup that makes the
problem not reproducible.  (There is, of course, a bug in xemacs, because it
should never seg fault; but this report is only about the apparently-obvious case).

Comment 1 Jens Petersen 2006-03-13 02:01:44 UTC
xemacs is now in Extras, changing product.

Comment 2 Jens Petersen 2006-03-13 02:02:49 UTC
Can you reproduce with "xemacs -vanilla" or "xemacs -q"?

Comment 3 Ville Skyttä 2006-03-13 07:14:39 UTC

*** This bug has been marked as a duplicate of 183643 ***

Comment 4 Will Partain 2006-03-13 09:15:24 UTC
Yes, it crashes with 'xemacs -q'.  (It doesn't with 'xemacs -q -nw')
This is all with 'yum update' as of about Mar 9 but w/ kernel 2025.

(In general, this xemacs is pretty crashy, certainly compared to the current FC4
one, which almost never crashes.  I supplied this example because the recipe is

Keep up the good work!

Comment 5 Ville Skyttä 2006-03-13 16:37:52 UTC
I'm observing the same thing; xemacs is currently somewhat unstable and crashy
on FC5tX.  I'm pretty certain that this has to do with FC5's font/UTF-8
configuration issues (see bug 180284) which triggers a bug elsewhere in XEmacs
resulting in these crashes.  Note that (at least for me) starting up in a
non-UTF8 locale, eg. with "LANG=C xemacs", avoids this crash just like in bug