Red Hat Bugzilla – Bug 7918
linuxconf refuses to start, "segmentation error," dumps core
Last modified: 2008-05-01 11:37:53 EDT
With 6.1 fully upgraded and the latest linuxconf posted on Dec. 15, 1999,
linuxconf worked fine for two days, then crashed in the middle of
configuring Samba. Henceforth it refused to start at all from the menu, or
from an X-terminal, or from a text terminal. Error message generated said
only "segmentation error (core dump)" Command "$file core" suggested that
it was a signal 11, memory problem. The rest of Redhat worked fine. So did
Win '98 when I rebooted. Physical memory problem unlikely. I tried many
things and RH tech support scratched their heads too. Then after taking a
break I realized that if linuxconf went terminally insane while configuring
Samba, it might make sense to look at the file /etc/smb.conf. Sure enough!
The Samba configuration file smb.conf was full of non-printing garbage
characters, in such a state as to justify the description "totally gorfed."
Solution: In the Samba section of /usr/doc there is an "examples"
directory. In that directory is a copy of the original Samba configuration
default file. Delete or rename the gorfed smb.conf in /etc and copy the
original Samba configuration file from the Samba "examples" directory into
/etc, taking care to rename it to smb.conf. Now linuxconf works fine once
more. Why it gorfed the smb.conf file in the first place I don't know. If
it will do it again, I don't know that either. Hope not.
I encountered the exact problem after configuring Samba.
*** This bug has been marked as a duplicate of 7874 ***