[X2Go-User] PulseAudio understanding problem (Windows client)

[Ingo Brückl]

Ulrich Sibiller <uli42 at gmx.de> wrote on Sat, 30 Mar 2019 13:14:11 +0100:

> Normally you should have more than "built-ins",

That's the least strange thing.

> nxagent uses these defaults if no fontpath is specified (using -fp) on
> startup:

None of the paths apply in my case: /usr/share/fonts/{75dpi,misc}, so I don't
wonder about having only "built-ins".

> If you run xset q inside the x2go session you will see the settings of
> x2go's X server (x2goagent/nxagent).

Oh, I see. I didn't know nxagent is a nested Xserver.

> To check the font settings of the Vcxsrv.exe you have two options:
> - check the logfile (I am not sure if that is always created; cannot
> check right now)

There is one, but no information about the font settings in it.

> - run xset q against the vcxsrv's display

Wouldn't I need an xset binary (and more?) for Windows to do that?

> If you fontpath inside the session if only "built-ins" none of the
> mentioned dirs is existing on your server. Can you please verify?

Yes, I can confirm.

> Now the question: where's you special font located?

Currently on both the Linux machine and a copy on Windows.

> What does xset q report if you just open a simple session with an xterm
> and nothing else?

I don't know what you mean by "a simple session".

> What does it report for a full session (before applying your fix)?.

"built-ins" only.

Ingo