Bug 38962 – KDrive binaries point to invalid font paths

• Product: Gentoo Linux
• Status: RESOLVED WONTFIX

[Description James Le Cuirot 2004-01-21 14:20:55 UTC]

When I Xvesa (haven't got a framebuffer to try Xfbdev), the server does start
but outputs the following to the console...

Could not init font path element /var/tmp/portage/kdrive-4.3.0-r3/work/xc/usr/X11R6/lib/X11/fonts/misc/, removing from list!
Could not init font path element /var/tmp/portage/kdrive-4.3.0-r3/work/xc/usr/X11R6/lib/X11/fonts/75dpi/, removing from list!
Could not init font path element /var/tmp/portage/kdrive-4.3.0-r3/work/xc/usr/X11R6/lib/X11/fonts/100dpi/, removing from list!

KDrive does not have any configuration files so I guess these have been
hard-coded incorrectly. But no fonts got installed anyway. How is it supposed to 
work without any fonts? On a related note, I tried to run IceWM but it complained about missing libraries. I then tried to recompile it but it complained about X not being present. Do I really need to have the full X installed? Before finalising a fix on this bug, you should take a look at bug
#38954 as well.

Reproducible: Always
Steps to Reproduce:
1. emerge kdrive
2. cd /usr/X11R6/bin
3. ./startxkd

[Comment 1 Andrew Bevitt 2004-01-22 22:49:50 UTC]

The fonts issue is a hard code by the makefiles IIRC 

I will look fully at this on monday, but fonts are definately not meant to be installed in the build.

In regards to the IceWM problem, you will either yes have to merge a complete X environment, or use the freedesktop xlibs ebuilds available from spyderous's overlay. At least for the time being anyways.

[Comment 2 James Le Cuirot 2004-01-23 07:57:32 UTC]

Ah that's exactly what I need. Thanks! I wish I'd known about that before! But hey, at least I spotted a bug.

[Comment 3 Andrew Bevitt 2004-06-12 00:48:48 UTC]

Closing...