From brian.a.town@nasa.gov  Mon Jan 16 17:25:59 2017
Received: (at 1132) by bugs.x2go.org; 16 Jan 2017 16:26:02 +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.5 required=3.0 tests=BAYES_05,URIBL_BLOCKED
	autolearn=ham version=3.3.2
Received: from localhost (localhost [127.0.0.1])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 8344E5DAAB
	for <1132@bugs.x2go.org>; Mon, 16 Jan 2017 17:25:59 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at ymir.das-netzwerkteam.de
Received: from ymir.das-netzwerkteam.de ([127.0.0.1])
	by localhost (ymir.das-netzwerkteam.de [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id b0rlHDWHRrxe for <1132@bugs.x2go.org>;
	Mon, 16 Jan 2017 17:25:52 +0100 (CET)
Received: from ndjsvnpf104.ndc.nasa.gov (NDJSVNPF104.ndc.nasa.gov [198.117.1.154])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 4EF415DAA7
	for <1132@bugs.x2go.org>; Mon, 16 Jan 2017 17:25:50 +0100 (CET)
X-Comment: SPF check N/A for local connections - client-ip=198.117.0.69; helo=ndmsppt104.ndc.nasa.gov; envelope-from=brian.a.town@nasa.gov; receiver=1132@bugs.x2go.org 
Received: from ndmsppt104.ndc.nasa.gov (ndmsppt104.ndc.nasa.gov [198.117.0.69])
	by ndjsvnpf104.ndc.nasa.gov (Postfix) with ESMTP id B70974005E62;
	Mon, 16 Jan 2017 10:25:37 -0600 (CST)
Received: from pps.filterd (ndmsppt104.ndc.nasa.gov [127.0.0.1])
	by ndmsppt104.ndc.nasa.gov (8.16.0.20/8.16.0.20) with SMTP id v0GGLdNj016062;
	Mon, 16 Jan 2017 10:25:37 -0600
Received: from ndmscht108.ndc.nasa.gov (ndmscht108-pub.ndc.nasa.gov [198.117.0.208])
	by ndmsppt104.ndc.nasa.gov with ESMTP id 27ygbc4pmu-1;
	Mon, 16 Jan 2017 10:25:37 -0600
Received: from NDMSMBX301.ndc.nasa.gov ([169.254.4.197]) by
 NDMSCHT108.ndc.nasa.gov ([198.117.0.178]) with mapi id 14.03.0319.002; Mon,
 16 Jan 2017 10:25:36 -0600
From: "Town, Brian A. (GSFC-428.0)[Embedded Flight Systems, Inc]"
	<brian.a.town@nasa.gov>
To: Stefan Baur <X2Go-ML-1@baur-itcs.de>,
        "1132@bugs.x2go.org"
	<1132@bugs.x2go.org>
Subject: Re: [X2Go-Dev] Bug#1132: Color issue with x2go not present in NX
 with certain applications
Thread-Topic: [X2Go-Dev] Bug#1132: Color issue with x2go not present in NX
 with certain applications
Thread-Index: AdJqgk0rLKKPZ1VSSRKw2ct7xbTB8wASFvsAAAx5ieABAOr6gA==
Date: Mon, 16 Jan 2017 16:25:36 +0000
Message-ID: <483F0E8D-3FC4-480A-A2E2-87FCABA96EAA@nasa.gov>
References: <2565EDE93CACC9478E32CA6681CC015E0AB82718@NDMSMBX301.ndc.nasa.gov>
 <00aced92-99b4-ce71-b6ff-25ed36e89bba@baur-itcs.de>
 <2565EDE93CACC9478E32CA6681CC015E0AB82811@NDMSMBX301.ndc.nasa.gov>
In-Reply-To: <2565EDE93CACC9478E32CA6681CC015E0AB82811@NDMSMBX301.ndc.nasa.gov>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [96.255.203.231]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <EF7DD6B9C5D572448E04FC1242D3D7CC@mail.nasa.gov>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-01-16_13:,,
 signatures=0

I forgot to mention by the looks of your link is testing currently only wor=
king on debian based systems? We=92re using Rhel6 systems with x2goserver i=
nstalled on them. I did notice in the git repo for Artica nxlibs there is a=
 section for building out a rpm. Little out of my depth here though so I mi=
ght be not looking at the correct thing.


> On Jan 9, 2017, at 11:58 AM, Town, Brian A. (GSFC-428.0)[Embedded Flight =
Systems, Inc] <brian.a.town@nasa.gov> wrote:
>=20
> Darn was hoping to have won the prize! Haha
>=20
> I have tested a few different compression/slider options but still going =
through and see what each option gives me in. The software being used is op=
en source for NASA missions I believe but closed outside of that, so not su=
re what all I can share on that just yet, I'll have to check.
>=20
> I did notice that selecting the "local desktop" option via the client on =
x2go provides me with the correct color, however it also produces a great d=
eal of lag. Is the local desktop option doing basic VNC connection or Xforw=
arding? I couldn't find any information on that.
>=20
> I'm utilizing x2go in conjunction with a LTSP set up. If I use basic Xfor=
warding through the terminal I get the colors I need displayed properly. I'=
m not sure exactly where it's hanging up through the x2go client window.
>=20
> For the unix_kde_depth option, is there a setting to have it exceed 24? S=
ome blogs I've noticed people their session.log files showing unix_kde_dept=
h32 however mine is always at 24 and unsure where that setting would be loc=
ated at.
>=20
> Brian Town
> Landsat 8
> Goddard Space Flight Center
>=20
>=20
> -----Original Message-----
> From: Stefan Baur [mailto:X2Go-ML-1@baur-itcs.de]=20
> Sent: Monday, January 09, 2017 11:50 AM
> To: Town, Brian A. (GSFC-428.0)[Embedded Flight Systems, Inc] <brian.a.to=
wn@nasa.gov>; 1132@bugs.x2go.org
> Subject: Re: [X2Go-Dev] Bug#1132: Color issue with x2go not present in NX=
 with certain applications
>=20
> Hi, Brian!
>=20
> First of all, welcome to X2Go!  You're actually the third NASA employee h=
itting our list (the other two were from JSC-EG311 and JPL-392K).
> Sorry, that doesn't mean you've won a prize. ;-)
>=20
> Some things I would like to ask you to do/try:
>=20
> 1) Please let us know the name of the software that has these issues with=
 X2Go; if it is non-free and/or something NASA developed internally, you mi=
ght want to get the developers of that software involved as well so they ca=
n talk to ours.
> Screenshots would help, too - but please remember to black out confidenti=
al information that might be visible on it.
>=20
> 2) Please try different slider settings and image compression algorithms =
in the connection settings.  Maybe it only affects JPG, or only PNG, ...
>=20
> 3) Also, please try running the software with X2Go in single application/=
published application mode (IOW, rootless mode) vs.
> fullscreen/windowed mode.  This is becahse parts of the screen drawing pr=
ocess work differently in rootless mode.
>=20
> 4) If you have a chance to run this software along with X2Go in a separat=
e testing environment, you could try following these steps and see if it ch=
anges anything - but please do not do this on a production
> system:
> http://wiki.x2go.org/doku.php/doc:howto:nx-libs-betatesting
> (Note that at present, this probably only works for Debian-based distribu=
tions, not for Redhat - but if you have a test lab available to you, you co=
uld "ssh -X brian@redhat-test-box" from the Debian box within the X2Go sess=
ion.)
>=20
> 5) We'd love to hear how you use or intend to use X2Go, so we can publish=
 your testimonial on our success stories page in the wiki.
> Since you seem to be working with weather satellites, that sounds like a =
rather interesting use case for X2Go.
>=20
> Last, I hope you don't mind that I mention this ...
>=20
> <shameless plug>
> X2Go also has a commercial side, where various companies - including my o=
wn - offer support contracts with guaranteed response times as well as cons=
ultancy and paid-for development work if someone wants to see a bug fixed o=
r a new feature added in a certain time frame. What makes my company specia=
l is, IMHO:
>=20
> 1) I'm the current X2Go Project/Community Coordinator, so the development=
 lead and the developers tend to listen to me.
> 2) As far as I know, we are the only company providing X2Go support that =
isn't a one-man-show.
> 3) We sub-contract other developers from the X2Go community on demand, so=
 you only have one person you need to talk to - me - and you will only rece=
ive one invoice, even if the task involved several freelance or part-time X=
2Go developers.
>=20
> Our hourly rate for consultancy work and fixing issues outside of a suppo=
rt contract is 110 EUR. With a support contract, you get guaranteed respons=
e times (starting at 400 EUR/month for 24h response time during business ho=
urs in the CET/CEST time zone from Monday to Friday, German holidays exclud=
ed) and lower hourly rates if you buy a certain amount of hours in advance.
> </shameless plug>
>=20
> Kind Regards,
> Stefan Baur
>=20
> Am 09.01.2017 um 15:13 schrieb Town, Brian A. (GSFC-428.0)[Embedded Fligh=
t Systems, Inc]:
>> Package: x2goclient
>>=20
>> Version: 4.0.5.2
>>=20
>>=20
>>=20
>> Connecting to remote RHEL system using x2go has color issues with=20
>> certain panels of an application on that system. When connecting via=20
>> NoMachine the panels show up as they should, black background, white=20
>> text. However with x2go the panel shows up as a grey background with=20
>> black text, and some text are just black boxes (the major issue is the=20
>> black boxes obscuring text).
>>=20
>>=20
>>=20
>> I noticed a bug along these lines from back in 2013 (#262 )
>> (http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=3D262)
>>=20
>>=20
>>=20
>> Brian Town
>>=20
>> Landsat 8
>>=20
>> Goddard Space Flight Center
>>=20
>> sig
>>=20
>>=20
>>=20
>>=20
>>=20
>> _______________________________________________
>> x2go-dev mailing list
>> x2go-dev@lists.x2go.org
>> http://lists.x2go.org/listinfo/x2go-dev
>>=20
>=20
>=20
> --
> BAUR-ITCS UG (haftungsbeschr=E4nkt)
> Gesch=E4ftsf=FChrer: Stefan Baur
> Eichen=E4ckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax =
0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
>=20

