On Sat, Oct 12, 2019 at 5:11 PM Alexanderstr Miete
wrote:
>
> Dear Ulrich and developers
> Thank you for your reply. So as discussed option a) connecting with "Custom
> Desktop" will start a NEW session and results in permission prompts, which
> are not the case with option b.
> Most users I bel
Dear Ulrich and developers
Thank you for your reply. So as discussed option a) connecting with "Custom
Desktop" will start a NEW session and results in permission prompts, which
are not the case with option b.
Most users I believe would like to feel as if they are sitting in front of
their machine,
Well, as far as I know this is how it is supposed to work.
That kind of privileges are handled by policykit, which has a
differentiation between local and remote users. And local users have more
privileges than remote.
When you start a new session with X2go you are definitely remote user,
while wit
On Sun, Sep 1, 2019 at 7:34 PM Alexanderstr Miete wrote:
> I was connecting with session type "Custom Desktop" Command: MATE. This
> worked very well in terms of lag/speed.
> Following your reply I changed to "session type "connect to local desktop)"
> and the permission issue did not appear any
