[Resent to the correct mailing list. Sorry.]
On 07.05.2014 07:40 AM, Jean Gottschalk wrote:
I am still trying to figure out why the automatic session resizing (when moving between clients with different screens, for example a desktop and a laptop) doesn't work anymore since I started using MATE.
Since the latest x2goclient upgrade, I noticed the following behavior: when I resume a session on a client with a different screen size, the screen will resize, but the session immediately suspends. Then when I login to the same session again (on the same client, so no screen resolution change), the session stays up.
When the session suspends, the log simply looks like this: / / /Session: Session resumed at 'Tue May 6 22:29:08 2014'./ /Info: Screen [0] resized to geometry [1280x1024] fullscreen [1]./ /Session: Suspending session at 'Tue May 6 22:29:10 2014'./
And if I open the same session again (on the same screen), it just stays up although it reports the same resizing procedure being run: / / /Session: Session resumed at 'Tue May 6 22:31:38 2014'./ /Info: Screen [0] resized to geometry [1280x1024] fullscreen [1]./
Not sure if this is related, but if I press CTRL+ALT+R which is the command to switch between auto-resize and viewport mode, the session also immediately suspends, and the logs show this:
/Info: Disabled desktop resize mode in agent./ /Session: Suspending session at 'Tue May 6 22:35:46 2014'./ /Info: Waiting the cleanup timeout to complete./ /Session: Session suspended at 'Tue May 6 22:35:46 2014'./
Is there any additional debug information that I could see anywhere, to see what code is actually being executed when the session goes into resume?
I know you reported this a long time ago, but I'd actually need some additional information about this now, as the bug is reproducible on any system.
The most valuable bit of information would be if resizing and Ctrl-Alt-R ever worked correctly. You say "[since] the latest x2goclient upgrade", which implies the behavior was different before. I don't know which version you were upgrading from/to (both would be interesting.)
Also, you probably did upgrade x2goserver/nx-libs server side, too, right? Working vs. non-working versions would really be helpful here, too.
Mihai