From jim.burnes@ca.com Mon Oct 13 21:45:13 2014 Received: (at 462) by bugs.x2go.org; 13 Oct 2014 19:45:14 +0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on ymir.das-netzwerkteam.de X-Spam-Level: X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50,HTML_MESSAGE autolearn=ham version=3.3.2 X-Greylist: delayed 335 seconds by postgrey-1.34 at ymir.das-netzwerkteam.de; Mon, 13 Oct 2014 21:45:12 CEST Received: from na3sys009aog116.obsmtp.com (na3sys009aog116.obsmtp.com [74.125.149.240]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id AC7295E09F for <462@bugs.x2go.org>; Mon, 13 Oct 2014 21:45:12 +0200 (CEST) Received: from USLIMS190.ca.com ([208.232.182.87]) (using TLSv1) by na3sys009aob116.postini.com ([74.125.148.12]) with SMTP ID DSNKVDwrwftn3OH81o4XE0OFFbBDXV/qN1Np@postini.com; Mon, 13 Oct 2014 12:45:12 PDT Received: from USLIMS171.ca.com (130.200.5.21) by USLIMS190.ca.com (208.232.182.87) with Microsoft SMTP Server (TLS) id 14.3.146.0; Mon, 13 Oct 2014 14:39:27 -0500 Received: from USLIMS112C.ca.com ([169.254.6.90]) by USLIMS171.ca.com ([130.200.5.21]) with mapi id 14.03.0146.000; Mon, 13 Oct 2014 14:39:27 -0500 From: "Burnes, James V" To: "462@bugs.x2go.org" <462@bugs.x2go.org> Subject: Display Size Issue Thread-Topic: Display Size Issue Thread-Index: Ac/nHWWRNK1YqynvS4qyaUnzGkVDjQ== Date: Mon, 13 Oct 2014 19:39:26 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [138.42.44.191] Content-Type: multipart/alternative; boundary="_000_C98413B85231DC45929CA5B0A628CFE602799CD5USLIMS112Ccacom_" MIME-Version: 1.0 --_000_C98413B85231DC45929CA5B0A628CFE602799CD5USLIMS112Ccacom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Sorry for the long delay. Still having this problem. Not sure why. I'm running the latest version of x2go for Ubuntu (4.0.1.180-949), and the = latest Windows client (4.0.1.3 build2) I have a Dell primary and Samsung= secondary display. They are both 1920x1080. I have the desktop set to ex= tended mode. I configure x2go to use the entire display (#2). What happens is I can get it to go full screen, but some reason it only thi= nks my secondary display has 1920x1040 available for it (as reported by xdp= yinfo). I've checked the Windows resolution settings and they say it's a 1= 920x1080 monitor. There might be some sort of issue where 'xrandr' might have set it to the w= rong value. I'll check that, but I don't think that's the issue. Thx Jim burnes --_000_C98413B85231DC45929CA5B0A628CFE602799CD5USLIMS112Ccacom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Sorry for the long delay.  Still having this pr= oblem.  Not sure why.

 

I’m running the latest version of x2go for Ubu= ntu (4.0.1.180-949), and the latest Windows client (4.0.1.3 build2) &n= bsp; I have a Dell  primary and Samsung secondary display.  They = are both 1920x1080.  I have the desktop set to extended mode.  I configure x2go to use the entire display (#2).

 

What happens is I can get it to go full screen, but = some reason it only thinks my secondary display has 1920x1040 available for= it (as reported by xdpyinfo).  I’ve checked the Windows resolut= ion settings and they say it’s a 1920x1080 monitor.

 

There might be some sort of issue where ‘xrand= r’ might have set it to the wrong value.  I’ll check that,= but I don’t think that’s the issue.

 

Thx

 

Jim burnes

 

 

--_000_C98413B85231DC45929CA5B0A628CFE602799CD5USLIMS112Ccacom_--