X2Go Bug report logs - #872
Turn xinerama.conf file related code inside X2Go Client into legacy code (for NX agents << 3.6)

Full log

Message #45 received at 872@bugs.x2go.org (full text, mbox, reply):

Received: (at 872) by bugs.x2go.org; 19 May 2015 08:54:23 +0000
From o.shneyder@phoca-gmbh.de  Tue May 19 10:54:21 2015
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,URIBL_BLOCKED
	autolearn=ham version=3.3.2
Received: from mail.cowic.de (mx1.cowic.de [80.190.97.241])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTP id A29E25DA83
	for <872@bugs.x2go.org>; Tue, 19 May 2015 10:54:21 +0200 (CEST)
Received: from [192.168.0.108] (unknown [95.90.221.251])
	by mail.cowic.de (Postfix) with ESMTP id 5BE0F380B9E5;
	Tue, 19 May 2015 10:54:21 +0200 (CEST)
Message-ID: <555AFA2D.9040307@phoca-gmbh.de>
Date: Tue, 19 May 2015 10:54:05 +0200
From: Oleksandr Shneyder <o.shneyder@phoca-gmbh.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.4.0
MIME-Version: 1.0
To: Ulrich Sibiller <uli42@gmx.de>, 872 <872@bugs.x2go.org>
Subject: Re: [X2Go-Dev] Bug#872: Bug#872: Bug#872: Turn xinerama.conf file
 related code inside X2Go Client into legacy code (for NX agents << 3.6)
References: <20150515115912.Horde.GtfqM24QvRXo7Sd2CZWsHw1@mail.das-netzwerkteam.de> <55583925.1040206@phoca-gmbh.de> <20150518084055.Horde.mlraxHD7gXZTq0IPaU98Eg1@mail.das-netzwerkteam.de> <5559AF7A.9070803@phoca-gmbh.de> <CANVnVYJOtianqJR3jOx2TTne0-0xcg4AN7FcLYxQ0V0iMM1cqg@mail.gmail.com> <5559EBF8.5090900@phoca-gmbh.de> <CANVnVY+DLhZuxtFDEwyUrAtaLLYV1+UkxejjpFeBint1GJ-69A@mail.gmail.com> <555AEFD2.2020807@phoca-gmbh.de> <CANVnVYJkOWBG3em2LFDbbBkKR4n_DuHmFLVnUS577ySSBPTLRw@mail.gmail.com>
In-Reply-To: <CANVnVYJkOWBG3em2LFDbbBkKR4n_DuHmFLVnUS577ySSBPTLRw@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="68Vm9l6dU1cQuSh7d6Xx79MOmDm1HSiPv"

[Message part 1 (text/plain, inline)]

Yes, It was exactly the problem, the different WM didn't update the
configuration without resizing.

Am 19.05.2015 um 10:50 schrieb Ulrich Sibiller:
> On Tue, May 19, 2015 at 10:09 AM, Oleksandr Shneyder
> <o.shneyder@phoca-gmbh.de> wrote:
>> Imagine that you have agent window in the middle of two screens. Window
>> size is 1024x768. You current displays configuration in that case is:
>> left-512x768, right-512x768. Imagine, that you moved your window 100 px
>> left. Now your displays configuration is: left-612x768, right-412x768.
>> But from the view of x2goagent nothing is changed, agent has no idea
>> about the display geometry on the client side. This is why client
>> updating xinerama.conf and resizing a window to apply new settings. I
>> hope it's understandable.
> 
> 
> Yes, it is understandable. But this only relevant for xinerama
> information. And that information is coming from the config file
> (which is correctly updated in this case by x2goclient). So I still do
> not see why x2goagent needs to be triggered in any way. If a software
> needs to know the xinerama setup it issues a XineramaQueryScreens()
> request. This is intercepted by the libNX_xinerama.so and answered
> with the information from the config file. The x2goagent does not even
> see this request and thus does noot need to be updated. The only
> problem that your code solves might be the window manager in the
> session that caches xinerama information.
> 
> Do you have a use case that does not work without the resize?
> 
> Uli
> 


-- 
-----------------------------------------------------------
Oleksandr Shneyder        | Email: o.shneyder@phoca-gmbh.de
phoca GmbH                | Tel. : 0911 - 14870374 0
Ludwig-Feuerbach-str. 18  | Fax. : 0911 - 14870374 9
D-90489 Nürnberg          | Mobil: 0163 - 49 64 461

Geschäftsführung:
Dipl.-Inf. Oleksandr Shneyder

Amtsgericht München | http://www.phoca-gmbh.de
HRB 196 658         | http://www.x2go.org
USt-IdNr.: DE281977973
-----------------------------------------------------------

[signature.asc (application/pgp-signature, attachment)]

Send a report that this bug log contains spam.