Red Hat Bugzilla – Bug 58990
vncserver uses -fp unix/:7100 and Xvnc coredumps when it's not available.
Last modified: 2007-04-18 12:39:29 EDT
1) Stop xfs
2) Try running vncserver (the one in /usr/bin)
Expected: something reasonable.
Actual: Xvnc dies (sometimes with a coredump).
I see at least two issues here:
- vncserver always uses -fp unix/:7100 and there is no way to override that in a
config file (I can edit the /usr/bin/vncserver directly, but that is not a
- Xvnc dies without a meaningful error message when -fp points to a non-existing
P.S. In general, a setup with a central font server and no local ones breaks
many RH scripts... Would it make sense to have an extra configuration file in
sysconfig that everybody (vncserver, Xconfigurator, etc) could use?
With the 7.2 package there was a core dump problem to do with xfs when
_exiting_ Xvnc: could it be that you are seeing? It's been fixed since then..
You can override the font path on the command line using -fp FONTPATH; does that
> With the 7.2 package there was a core dump problem to do with xfs when
> _exiting_ Xvnc: could it be that you are seeing?
No, definitely not - this started happening when I disabled the local server and
went away when I changed the vncviewer script to use the remote server instead.
And it definitely was during startup
> You can override the font path on the command line using -fp FONTPATH; does that
Not really, there are several users besides me who use vncserver and I need a
default that works. Would it be better to extract the default from XF86Config
(or -4) if that config is present? Or should we have a separate configuration
file (that Xconfigurator could consult too)?
For the time being, in lieu of a real configuration file to look at in an easy way,
I used this replacement vnc-fp.patch:
Created attachment 43936 [details]
Patched in vnc-3.3.3r2-26.
*** Bug 60347 has been marked as a duplicate of this bug. ***