I set up a Fedora 11 test VM, and it appears that Xvnc does not use the font catalog on that system. It instead tries to use the hard coded font path (which is determined by whatever directory you built Xvnc in. In my case, it's /home/drc/tigervnc/unix/xorg.build/lib/X11/fonts/*). This of course means that it fails whenever -fp is not specified.
I'm not sure why my system is different from yours. Are you building with the Xorg 1.6 code maybe? I'm building 1.5. In any case, it seems that passing no -fp argument may not be a good idea as the default. 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. >> > > Yes, it seems fine for me. Unfortunately current vncserver script in > svn is still broken. > > When you run vncserver script it creates socket called 7100 in working > directory: > > $ ls -l 7100 > srwxrwxr-x 1 atkac atkac 0 2009-04-15 10:57 7100 > > It seems there is problem somewhere in CheckXFS function. > > Adam > > ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
