Font Error using Linux font server [12]

I have studied the different articles about font problems, but there seems to be an other dificulty too, which I figured out during the last days

On my Linux host (the same machine I use to login via XDMCP port 177) I run "Xfs" the X Window System font server which does his font service on port 7100.

Now, if I try to include this fontserver into Xmanagers fontlist I run into troubles.

When I put it in the first position of the font-list, I get Xmanagers Error-Message "could not open default font 'fixed' ". When I try to position it after "MISC" or later, I get the linux login window, but XDM could not start the X-Desktop. It uses to hang when the desktop is prepared to display and I get no more response from Xmanager.

I got the beta of Xmanager 2.0 which seems to have the same troubles. See attachment1, which is an extract of "kdm.log"

Once you get a linux login window, the font server is working well. If Xmanager hangs after login, you need to check your login scripts for a possible error.

If a $DISPLAY variable is set in shell scripts such as .profile, you must comment it out. Try to create a new user account and login to that account.

----
Technical Support

Sorry, this seems not to be the solution. I had a look at the different scripts like .profile ... but there was no expicite setting of DISPLAY variable.
I set up a total new standard user but he has exactly the same problems.

Remember the folowing fact:

a) if I don't configure any font server, Xmanager works

b) if the font server is the first entry in the fonts list, Xmanager shows the error message "could not open default font 'fixed'" before any X-Window shows up

c) if font server entry stands at any position after "MISC", I get the Login Window, but enything hangs when X window manager starts

d) there is no difference which user logs in

e) X-Server on the linux host gets all its fonts from the font server I try to use with Xmanager too. The only FontPath entry in XF86Config is
Section "Files"
FontPath "unix/:7100"

W. Braun

Thanks for your feedback.

Now Xmanager 1.3.9 fixes the font server problem. You can download it at:

/download/download.html

You don't have to move down the font server entry below the MISC fonts. Please try it and let us know if the problem persists.

Thanks again for your cooperation.

----
Technical Support

Thanks,

now it is possible to position the font server entry at any position in the fonts list, but...

a) I allways get the XDM login window, even if the only entry in the font list is the font server

b) X-session hangs after user login (same as before)

c) if there is absolutely no font entry, Xmanager tells "default font path not found" (I tested this to see if there is a hidden fontpath in this version, but it reacts as supposed)

So I think, the main problem still is Xmanager could not fully interact with the font server.
Please see attached file /home/username/.xsession-errors for more details

W. Braun

We found the same error in the KDE of RedHat 9. The problem was caused by an unexpected reply from the font server.

Please uncompress the attached file and copy it to "C:\Program Files\Xmanager1.3.9" folder.

If the problem persists, let us know the vendor and version of your Linux machine.

We would appreciate your feedback.

Thanks for your cooperation.

----
Technical Support

OK, fine !

Now it works fine. For your info I attach .xsession-.errors and the Xmanager ini-file.

There are two problems left, I could't understand:

a) after XMD login when everything seems to be OK, sometimes Xmanager hangs. In Taskmanager I can see Xmanager to use about 99% of CPU.
Stopping Xmanager and starting it again works.

b) as you can see, there are still some errors I can't understand in .xsession-errors

Thanks W. Braun

We have tried to reproduce the same error but Xmanager worked well with our Linux servers. Could you please let us know what X application you are using?

Also, try Xmanager 2.0 beta 2 at:

/products/xmg_2beta.html

The xsession-errors file has several error messages regarding XInputExtension and DCOP communication errors. You can just igore the XInputExtension errors. For other errors, we think the Qt library and DCOP server are the reason of the problem.

----
Technical Support

OK, now I installed Beta 2.0 from 8th of march. The configuration I use is the same as in version 1.39

.xsession-errors still shows a lot of errors, see attachment. If you tell me where I can find the actual configuration of Xmanager, I could send it to you too.

Here are the versions of X I use, but also see Attachment2 for more info and errors.
This is the X application I use:
xloader System/X11/Servers/XF86_4 Version 4.2.0-188 rom UnitedLinux LLC for i586
XFree86 Version 4.2.0 / X Window System
(protocol Version 11, revision 0, vendor release 6600)

The desktop runs with KDE Version 3.0.3-232

thanks so far Wolfgang

The errors included on your previous message are not affecting Xmanager to run.

We are still having a difficulty to reproduce the same problem you have. Please provide us specific information to reproduce your problem.

----
Technical Support

Hi Wolfgang,

Got some questions about your Linux server.

1. Is it Suse Linux? If it is, what version?
2. Have the xloader rpm installed seperately? (After Suse 8.2, no xloader rpm included in the distribution.)
3. What version of xloader rpm is installed?
4. Does your CPU problem occur randomly?
5. Did that happen when you try to run a specific X application or after you just login?
6. Have you try with other desktop environment such as GNOME?

Your answers plus more information might help to define the problem.

Ron

Hi Ron,

thanks for your interest. Here my answers:
1. SuSE Linux Enterprise Server 8.0 which is periodic updated by SuSE support connection

2. No separate xloader installed
3. xloader 4.2.0-188 is installed
4. No, the errors which I attached to my last article occur every time I start a new X-Session after XDM-login. It doesn't matter which user logs in.
5. after login
6. no, kde and failsafe are the only desktops in XDM selection. Failsafe doesn't produce any errors.

See attached .xsession-errors which is produced as follows:
a) old file deleted
b) x-session started with Xmanager 2.0 beta
c) user logged in
d) command shell started nothing else
e) x-session finished regularly
f) .xsession-errors attached here

We would like to clarify what have been discussed so far. The problem of yours is as follows:

- When using a font server, CPU load is getting increased excessively and Xmanager stops to run.

To solve this issue, we recommend installing a necessary font into your PC instead of using the font server.

The errors printed out in .xsession-errors are the errors that can be generated when using KDE. It is all right to ignore the error messages unless you have a problem on using various kinds of programs in KDE after login.

----
Technical Support