Red Hat Bugzilla – Bug 161451
xscreensaver-demo crashes when clicking Documentation menu ( in Help menu )
Last modified: 2007-11-30 17:11:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4
Description of problem:
The xscreensaver configuration tool crashes when I click the documenation menu.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. open terminal ( xterm, gnome-terminal, etc )
2. type 'xscreensaver-demo' without quote
3. click Help menu
4. click Documentation
Actual Results: Segmentation fault, babe
Expected Results: The documentation of xscreensaver appears
This is the default installation of fedora core 4. I only installed xscreensaver-base. I don't install xscreensaver-extra.
Created attachment 116349 [details]
ps output when seeing xscreensaver documentation
For me, seeing xscreensaver documentation by clicking Document sometimes
crashes X server.
It seems that this is because when clicking Document, the command "man" is
looking at not the (gzipped) documentation file but at the binary file of the
command ( which is at /usr/libexec/xscreensaver/...) , which is probably due
to the PATCH3 or PATCH4 in xscreensaver-4.21-4.src.rpm .
See the attached file, which is the output of "ps auwwxf" when I browse a
documentation of xscreensaver
Created attachment 116732 [details]
Patch for man command to use the basename of screenhacks
A workaround patch for man command to use the basename of screenhacks.
In the defalut setting, the manual page name of a screenhacks is
the same as that of the screenhacks and all the manal pages are
in the path of "manpath". So using the basename of the screenhacks works
under the current fc4 setting.
If the directory of the manual pages is changed, this patch no longer
My comment is moved to bug 167708.
This report targets the FC3 or FC4 products, which have now been EOL'd.
Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?
*** This bug has been marked as a duplicate of 167708 ***