Re: [X2Go-User] MATE desktop (Ubuntu Mate 15.10) cannot access in fullscreen mode

2015-11-12 Thread Simon Baev
Robert,

Thank you for the advise, but the are complications...

   - I use this remote desktop from two different machines. One has native
   desktop resolution of 4k (didn't have a chance to try your workarounds on
   it yet) and the other one has native resolution of 1680x1050 I tested your
   workaround for fullscreen on 1680x1050 machine and it almost worked. I can
   select closest mode of 1600x900 and panels work OK. But when I set
   resolution to native 1680x1050 they (panels) are no longer accessible. I
   tried to change resolution in GUI and via xrandr -- result is the same. I
   noticed one fact that list of modes in Fedora (hosting machine where X2Go
   client is running), as reported by xrandr is different from the list of
   modes reported on the remote host, but both show 1680x1050 as an option.
   The only difference would be that in Fedora it comes with 59.95*+ rate but
   in the remote host it comes with 60.00 Could this be a reason for native
   resolution not to work in fullscreen mode as expected (with accessible
   panels)?

   - If I configure the session to use entire display, in my case Display 1
   (the only available option), I can use Ctrl+Alt+ to switch
   workspaces on the remote host but not switch between applications.

Thank you.

--
Simon

On Thu, Nov 12, 2015 at 12:38 PM, Robert Dinse  wrote:

>
>  You've probably got the display on the remote machine desktop set
> larger
> than the resolution of your local screen.  I see this for example if I use
> an
> old 3x4 monitor with 1600x1200 and connect to a machine that I previously
> had
> set to 1680x1050 for a wide screen.  The solution in this case is just to
> go
> into System->Preferences->Hardware-Displays and change the resolution to
> that
> of your local monitor.
>
>  With respect to Fedora intercepting keys, change to Display 1 instead
> of
> Full Screen and then the control-alt-arrows to switch desktops will be
> intercepted locally instead of passed to the remote machine.
>
>
> -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
>  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
>Knowledgeable human assistance, not telephone trees or script readers.
>  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800)
> 246-6874.
>
> On Thu, 12 Nov 2015, Simon Baev wrote:
>
> Date: Thu, 12 Nov 2015 11:52:25 -0500
>> From: Simon Baev 
>> To: x2go-user 
>> Subject: [X2Go-User] MATE desktop (Ubuntu Mate 15.10) cannot access in
>> fullscreen mode
>>
>> Hi All,
>>
>> I am running X2Go server 64-bit on Ubuntu Mate 15.10 from PPA repository:
>>
>> x2goserver: 4.0.1.19
>> x2goserver-extensions: 4.0.1.19
>> x2goserver-xsession: 4.0.1.19
>>
>> This Ubuntu host is virtualized in ESXi 6.0 environment with
>> open-vm-tools.
>>
>> I am using X2Goclient (X2Go Client v. 4.0.5.0 (Qt - 4.8.7) 64 bit) on
>> Fedora 23 with Gnome 3 desktop.
>>
>> Here is the *problem*:
>>
>>   - When I connect to X2Go server in fullscreen mode, both top and bottom
>>   panels are not accessible. The rest is OK.
>>   - When I connect in Window mode (various resolutions) I can access both
>>   panels but unfortunately cannot use Alt+Tab to switch programs inside
>> the
>>   Ubuntu (it is getting intercepted by Fedora).
>>
>> Any help is appreciated. Thank you.
>>
>> --
>> Simon
>>
>>


-- 
Simon
___
x2go-user mailing list
x2go-user@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-user

[X2Go-User] MATE desktop (Ubuntu Mate 15.10) cannot access in fullscreen mode

2015-11-12 Thread Simon Baev
Hi All,

I am running X2Go server 64-bit on Ubuntu Mate 15.10 from PPA repository:

x2goserver: 4.0.1.19
x2goserver-extensions: 4.0.1.19
x2goserver-xsession: 4.0.1.19

This Ubuntu host is virtualized in ESXi 6.0 environment with open-vm-tools.

I am using X2Goclient (X2Go Client v. 4.0.5.0 (Qt - 4.8.7) 64 bit) on
Fedora 23 with Gnome 3 desktop.

Here is the *problem*:

   - When I connect to X2Go server in fullscreen mode, both top and bottom
   panels are not accessible. The rest is OK.
   - When I connect in Window mode (various resolutions) I can access both
   panels but unfortunately cannot use Alt+Tab to switch programs inside the
   Ubuntu (it is getting intercepted by Fedora).

Any help is appreciated. Thank you.

-- 
Simon
___
x2go-user mailing list
x2go-user@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] x2goserver on Ubuntu Mate 15.04 with 4k monitor and high font-rendering DPI

2015-05-21 Thread Simon Baev
I wasn't looking to start a "shadow" session to access existing session. I
just needed to use some software that was installed on that machine so
fresh session worked fine. I will try the "extensions" approach for testing
and will stick with a separate user scenario for main needs in future.
Thank you.

--
Simon

On Thu, May 21, 2015 at 3:23 PM, Mihai Moldovan  wrote:

> On 21.05.2015 08:22 PM, Simon Baev wrote:
> > I saw this setting but for some reason it didn't affect anything when I
> > changed it to 96. Could it be caused by the fact that ongoing (not logged
> > out) session was active on the server (physical console) while I was
> trying
> > to remotely connect to it via X2Go?
>
> What exactly are you doing, anyway? It seems like you are starting a shadow
> session, i.e., connect to the already running "local" X server on the
> server
> machine?
>
> The DPI setting in X2Go Client controls the private X server's - i.e.,
> nxagent's
> - DPI value. There's a caveat though, in the sense that desktop
> environments can
> and most likely will overwrite that.
>
>
> > The only way I found to connect to that server with reasonable DPI was to
> > create a separate user that runs default settings, but that doesn't seem
> to
> > be a good fix.
>
> X2Go provides support for hooks via its "extensions" support. I guess it's
> not
> properly documented anywhere yet, but the basic idea is to put scripts into
> /usr/lib/x2go/extensions/. The "targets" in there are sort-of
> self-explanatory.
>
> N.B.: the amount of "targets" available may differ between release and
> nightly
> versions.
>
>
> All this said, I think a separate user is the "cleanest" and best-working
> idea.
>
>
>
> Mihai
>
>


-- 
Simon
___
x2go-user mailing list
x2go-user@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] x2goserver on Ubuntu Mate 15.04 with 4k monitor and high font-rendering DPI

2015-05-21 Thread Simon Baev
I saw this setting but for some reason it didn't affect anything when I
changed it to 96. Could it be caused by the fact that ongoing (not logged
out) session was active on the server (physical console) while I was trying
to remotely connect to it via X2Go?

The only way I found to connect to that server with reasonable DPI was to
create a separate user that runs default settings, but that doesn't seem to
be a good fix.

--
Simon

Am 21.05.2015 um 20:05 schrieb Simon Baev:
> > Hello,
> >
> > I'm looking for a way to run *x2goserver* on *Ubuntu Mate 15.04*
> > which is living on computer with *4k monitor* attached. I changed
> > *DPI* settings in Control Center -> Appearance -> Fonts -> Details
> > to *168* to let all applications look good when I work on that
> > machine locally.
> >
> > When I connect to this machine using *x2goclient* running on
> > another Ubuntu Mate 15.04 (attached monitor has resolution of
> > 1680x1050, fullscreen mode) I am seeing *huge* fonts (as expected)
> > because it also uses dpi of 168 for that remote connection.
> >
> > *My question*: would it be possible to run *pre-connection* (and
> > then post-connection) script(s) to temporally change DPI to
> > "normal" value of 96 before and recover it back to 168 upon
> > completion of the x2go session? I guess it can be done by running
> > "*gsettings set org.mate.font-rendering dpi 96*" command but I'm
> > not sure where to include this command. And also I'm not sure how
> > to protect against abnormal session termination... what if session
> > will terminate without recovering DPI back to 168?
>
> There's a setting in the X2GoClient GUI to force a DPI value, doesn't
> that work for you?  If no, why?
>
> - -Stefan
>
___
x2go-user mailing list
x2go-user@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-user

[X2Go-User] x2goserver on Ubuntu Mate 15.04 with 4k monitor and high font-rendering DPI

2015-05-21 Thread Simon Baev
Hello,

I'm looking for a way to run *x2goserver* on *Ubuntu Mate 15.04* which is
living on computer with *4k monitor* attached. I changed *DPI* settings in
Control Center -> Appearance -> Fonts -> Details to *168* to let all
applications look good when I work on that machine locally.

When I connect to this machine using *x2goclient* running on
 another Ubuntu Mate 15.04 (attached monitor has resolution of 1680x1050,
fullscreen mode) I am seeing *huge* fonts (as expected) because it also
uses dpi of 168 for that remote connection.

*My question*: would it be possible to run *pre-connection* (and then
post-connection) script(s) to temporally change DPI to "normal" value of 96
before and recover it back to 168 upon completion of the x2go session? I
guess it can be done by running "*gsettings set org.mate.font-rendering dpi
96*" command but I'm not sure where to include this command. And also I'm
not sure how to protect against abnormal session termination... what if
session will terminate without recovering DPI back to 168?

Thanks.

-- 
Simon
___
x2go-user mailing list
x2go-user@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-user

[X2Go-User] x2gobroker-wsgi on Ubuntu 14.04 + Apache2 + libapache2-mod-wsgi

2015-04-12 Thread Simon Baev
Hi All,

I cannot make broker-wsgi to work. What I've done:


   1. I installed x2gobroker-wsgi from package on publicly available host
   2. I installed Apache2 and libapache2-mod-wsgi
   3. I removed /etc/apache2/conf.d/x2gobroker-wsgi
   4. I edited /etc/apache2/sites-available/x2gobroker to
  1. replace SSL certificate data with the real one which is installed
  on the server
  2. replace value of  ServerName directive to match real hostname of
  the server (originally it was set to "localhost")
   5. Restarted apache2 service

When I connect to the server in a web browser (using hostname listed with
ServerName directive) via https:// I'm getting webpage which belongs to
default vhost, i.e. content of index.html file located in /var/www

When I try to navigate to https:///plain/inifile I'm getting 404

I guess I cannot figure out how to deal with wsgi... because for me it
seems like Apache is looking for plain/inifile located in /var/www and
totally ignores wsgi business.

Any help is greatly appreciated.

-- 
Simon
___
x2go-user mailing list
x2go-user@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-user