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,
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
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
On Fri, Mar 29, 2019 at 8:23 PM Ingo Brückl wrote:
> Because "xset -q" (within the session) still said that the font path is just
> "built-ins", I set the path (and had to use my Linux paths):
This is weird. Normally you should have more than "built-ins", see below.
If you run xset q inside the
Am 29.03.19 um 19:31 schrieb Ingo Brückl:
> So, Mr. Ophthalmologist I'm finally using an X2Go session and am very happy
> about the fullscreen mode (that could not be used with a shadow session due
> to a missing or invisible cursor).
Yay! Please don't forget to make a new appointment in 12
* On 3/28/19 10:40 PM, Ingo Brückl wrote:
> I tried "custom desktop" and simply gave "sh /home/me/.xinitrc" as an
> experiment. Everything shows up like my local desktop with two exceptions.
> Xterm is a very small window with small font in it (as if my X resource
> XTerm.VT100.font: 10x18 would
Stefan Baur wrote on Thu, 28 Mar 2019 18:46:41 +0100:
> Sounds like a DPI issue to me. Have you tried changing the DPI setting
> in the X2GoClient Session Configuration?
Yes, either DPI setting (very low or very high) affects all fonts (like menu
items, window titles, message boxes etc.), but
Ingo Brückl schrieb am Do., 28. März 2019, 18:27:
>
> Stefan Baur wrote on Thu, 28 Mar 2019 13:24:50 +0100:
>
> > What's the reason why you're so eager to use a shadow session instead of
> > an actual X2Go session
>
> There are font issues with a X2Go session that I don't have with a shadow
>
Am 28.03.19 um 17:33 schrieb Ingo Brückl:
> The Windows client has a smaller display (1024x600) than the server
> (1024x768). I'm using a specially designed 10x18 font for both xterm and
> xdosemu that looks great (and big enough) on the server display, but on the
> 1024x600 fullscreen X2Go
Stefan Baur wrote on Thu, 28 Mar 2019 13:24:50 +0100:
> What's the reason why you're so eager to use a shadow session instead of
> an actual X2Go session
There are font issues with a X2Go session that I don't have with a shadow
one.
The Windows client has a smaller display (1024x600) than the
Am 28.03.19 um 12:56 schrieb Ingo Brückl:
> Unfortunately, if shadowSession (local desktop connection, I suppose) is set
> (onmainwindow.cpp:5467) this code won't be executed.
>
> So the question is: why?
Because it is a *shadow* session, meant for remote support, so the
assumption is that there
I wrote on Wed, 27 Mar 2019 04:58:50 +0100:
> My question is: How is the Windows client supposed to pass this information
> to the PC, so that the sound client knows how to reach the pulseaudio
> server?
After taking a look at the client sources, the answer should have been easy:
The client
Also, I would be very surprised if sound works for a shadowing session
(AKA "connect to local desktop").
Am 27.03.19 um 15:03 schrieb Stefan Baur:
> Am 27.03.19 um 14:21 schrieb Ingo Brückl:
>>> I don't know how that works in detail. But the basic principle is to run
>>> an ssh server on the
Am 27.03.19 um 14:21 schrieb Ingo Brückl:
>> I don't know how that works in detail. But the basic principle is to run
>> an ssh server on the windows client and connect to it from the server.
> In order to establish a connection to the Windows client I'd need its current
> IP address and the
On Wed, Mar 27, 2019 at 2:25 PM Ingo Brückl wrote:
>
> Ulrich Sibiller wrote on Wed, 27 Mar 2019
> 07:43:46 +0100:
>
> >> My question is: How is the Windows client supposed to pass this
> >> information to the PC, so that the sound client knows how to reach
> >> the pulseaudio server?
>
> > I
Ulrich Sibiller wrote on Wed, 27 Mar 2019 07:43:46
+0100:
>> My question is: How is the Windows client supposed to pass this
>> information to the PC, so that the sound client knows how to reach
>> the pulseaudio server?
> I don't know how that works in detail. But the basic principle is to
I don't know how that works in detail. But the basic principle is to run an
ssh server on the windows client and connect to it from the server. So
maybe check if your windows firewall is the culprit.
Does file sharing in x2go work?
Uli
Ingo Brückl schrieb am Mi., 27. März 2019, 05:44:
> Hi,
>
17 matches
Mail list logo
