Re: [X2Go-User] PulseAudio understanding problem (Windows client)
Ulrich Sibiller wrote on Sun, 31 Mar 2019 11:59:24 +0200:
> Alright, the problem then is that Linux From Scratch is using
> fontpaths that differ from the default ones.
My font paths may not be pure Linux From Scratch, so don't bother changing
any font path settings in your sources.
Actually, /usr/share/fonts is the default location of fonts in fontconfig
and LFS sets a link for TTF fonts (ln -s $XORG_PREFIX/share/fonts/X11/TTF
/usr/share/fonts/X11-TTF). I decided to put *all* my fonts directly into
/usr/share/fonts. So that's actually not pure LFS.
> Can you please send us the correct list (derived from the defaults I
> posted earlier) for your distribution?
Okay, I've started completely from defaults again. Here is what I had to do
in order to make my special font (actually two of them, one for xterm and one
for xdosemu) working.
1. Adding my non-default (non-LFS) font paths to the script that starts the
session on the Linux PC (for nxagent):
xset fp /usr/share/fonts/75dpi/,/usr/share/fonts/misc/,built-ins
I totally get now why this is necessary.
2. Copying my /usr/share/fonts/{75dpi,misc} to the x2go Windows client to
C:\Program Files\x2goclient\VcXsrv\fonts\{75dpi,misc}.
I still don't get why *this* is necessary, but it is. Without copying it
doesn't work. (Actually, without copying, xterm seems to use my font, but
its window is far too small and glyphs are overlapping; xdosemu wouldn't
use my font at all.)
3. Because the Windows path in 2. is default for VcXsrv, I did *NOT* to have
to change VcXsrv's default command line options (as stated previously). It
is sufficient to select "use integrated X-Server" (with all its defaults).
One other thing:
Apparently, C:\Program Files\x2goclient is the default installation directory
for the Windows client. On the contrary, the fixed path "C:\\program
files\\vcxsrv\\vcxsrv.exe" is used three times in the client source. So when
you'd change to "use custom X-Server" and don't watch out for the default
executable put in there, you're screwed. The client immediately shuts down
with an error at start-up then.
That should be it. Thank you for your support.
Ingo
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] PulseAudio understanding problem (Windows client)
Am 31.03.19 um 11:59 schrieb Ulrich Sibiller: >> I don't know what you mean by "a simple session". > Does not matter now, as we have found the root cause: unusual font > paths on your system. > > A simple session is one that does not start a full desktop environment > like xfce but only a single xterm. You can achieve that by selection > "Application" under "Session Type" and specifying a full path to the > xterm in the right input field. Note that some applications don't like to be started that way, resulting in an instant termination of the session. If that happens, use "Published Applications" instead (this will keep the session running) and select the desired application from the list. -Stefan -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] PulseAudio understanding problem (Windows client)
On Sun, Mar 31, 2019 at 1:14 AM Ingo Brückl wrote:
> > 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?
This is X11, so you only need an xset anywhere and an X server
(vcxsrv) that allows remote access.
I don't a have a windows installation at hand where I could test that,
but in principle it works like this:
So what you do is this:
- run vcxsrv with the option -ac. This will disable access control.
- run xset -display :
Maybe you have to disable the windows firewall for 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.
Alright, the problem then is that Linux From Scratch is using
fontpaths that differ from the default ones. You can pass the correct
font paths by adding the appropriate -fp option to
/etc/x2go/x2goagent.options.
Can you please send us the correct list (derived from the defaults I
posted earlier) for your distribution? We then can add this to source
code (although I think we should revise that code to determine the
system's default patch automatically during build.
> > Now the question: where's you special font located?
>
> Currently on both the Linux machine and a copy on Windows.
I am interested in the path. BTW: I doubt you need the fonts on the
Windows side, so please re-test with the fonts removed from 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".
Does not matter now, as we have found the root cause: unusual font
paths on your system.
A simple session is one that does not start a full desktop environment
like xfce but only a single xterm. You can achieve that by selection
"Application" under "Session Type" and specifying a full path to the
xterm in the right input field.
Uli
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user
