Adam Tkac wrote: > If I start without -fp parameter all works fine. Btw newer Xorg > doesn't use xfs nor "standard" /usr/share/X11/fonts directory and > friends. > >>> commit r3725 caused regression on all new systems. For example Xorg in >>> Fedora 11 handles font via "font catalogue" (/etc/X11/fontpath.d) and >>> it doesn't use xfs. >>> >>> I recommend this approach: >>> - try start Xvnc with no -fp parameter >>> - if start is not successful then use current logic >>> >>> In my opinion in vast majority of cases no -fp parameter is fine. >>> >>> - reference: https://bugzilla.redhat.com/show_bug.cgi?id=494801 >>> I was finally able to get my build back up. As I suspected (and remembered from having to go through this previously with TurboVNC), passing no -fp argument to Xvnc causes it to use a hard-coded (and incorrect) font path on older systems, which I guess is the default behavior when no font catalog is available. I'm in the process of installing Fedora 11 so I can get a better understanding of how things work on the newer systems that you kids are running these days.
Anyway, I changed vncserver so that it does the following: 1) Attempts to bind to XFS running on unix:7100 or inet:7100. If successful, then it passes the appropriate -fp argument to Xvnc to tell it to use XFS. 2) If XFS isn't running, vncserver attempts to start Xvnc with no -fp argument. 3) If (1) or (2) fails, then vncserver will attempt to determine an appropriate font path and use that. ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
