Font Server unusable after reboot

  • This topic is empty.
Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #247
    • Total Post: 2
    • Newbie

    i’m working with V50 with linux 6.3.0 (and above).

    I’m trying to use them to acces to FreeBSDs server via XDMCP (via chooser)

    Font server seems to be unusable after a reboot, and the
    XDMCP Query fails.

    So I need to reconfigure each time after a reboot (make a minor
    change like adding a “;” or suppressing it)

    This happen with wlx.ini configuration but also with
    local panel configuration.

    This is very ugly because i need to let high privilege on the term
    to let the users correct the problem.

    Upgrading to 6.3.1_21, and XDMCP upgrade doesn’t solve tis.

    Does anybody would have a solution to cure this problem ?

    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    Hmm, that’s a good one. Since 6.3.0_14 the XDMCP/Xnest connection will check if the font server is available first if one is configured and then connect. Not fonts, no connection.

    The fact that it fails says it held the font server config, is it possible to do a ethereal capture of when it connects to the font server to see what happens? Failing that its one for Wyse support sorry.


Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.