Xnest used top work fine but now I am using the xorg version Xnest complains with the following message: Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! Fatal server error: could not open default font 'fixed' and then immediately aborts. I have tried using the -fp command line option and then specifying the fontserver as my main X11 display uses a font server but this also fails with the same message.
edit your /etc/X11/xorg.conf file and look for font directories /usr/X11R6/lib/X11/fonts/* is the old deprecated place for fonts they should be in /usr/share/fonts/* now some docs in 6.8.0 still has not been updated with the new font path but normally, distro packagers would certainly put symlink to make applications using the old directory layout work also, please tell exactly which xorg version you used (6.7.0/6.8.0 or any RC)
My xorg.cong file does not make any mention of the font path you mentioned. It only mentions the font server and which port to connect on: Section "Files" # RgbPath is the location of the RGB database. Note, this is the name of the # file minus the extension (like ".txt" or ".db"). There is normally # no need to change the default. # Multiple FontPath entries are allowed (they are concatenated together) # By default, Red Hat 6.0 and later now use a font server independent of # the X server to render fonts. RgbPath "/usr/X11R6/lib/X11/rgb" FontPath "unix/:7100" EndSection I am using 6.7.0.
Xnest does not use xorg.conf. You have to specify the fontpath with the -fp option (eg Xnest -fp tcp/fontserver:7100) about /usr/share/fonts/*: Xnest uses the fontpath configured while building X11. If you configure X11 to search fonts in /usr/share/fonts at buildtime then Xnest will find then. Unless you do so Xnest will use ProjectRoot/lib/X11/fonts as its fontdir
Read the information in comment #3 (closing, since it looks like it was resolved but nobody bothered to mark it as such).
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.