X2Go Bug report logs - #1383
x2go-client crashes after reconnect to full display session when multiple displays are used

Reply or subscribe to this bug.

Toggle useless messages

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

From: Pär G Larsson <Par.G.Larsson@regionvasterbotten.se>

To: "submit@bugs.x2go.org" <submit@bugs.x2go.org>

Subject: x2go-client crashes after reconnect to full display session when multiple displays are used

Date: Wed, 10 Apr 2019 11:24:05 +0000

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

Package: x2go-client
Version: v.4.1.0.0

When reconnecting to an existing session where full display was used previously, and when multiple monitors exist, the x2go-client tries to display the remote desktop spanning both monitors. It subsequently crashes.

Im on a win10 machine but I think it is the same on win7. It does not seem to matter if Xinerama is checked in the client settings.

The server is running Centos 7.6 and the following packages are installed:

x2goagent.x86_64                            4.1.0.3-1.el7         @epel
x2goserver.x86_64                            4.1.0.3-1.el7         @epel
x2goserver-common.noarch             4.1.0.3-1.el7         @epel
x2goserver-xsession.noarch             4.1.0.3-1.el7         @epel

Thank you for making x2go, it's great!! Let me know if you need more info.

Kind regards,

Pär Larsson

________________________________________________________
Pär Larsson, PhD
Bioinformatician

Region Västerbotten
Umeå University Hospital, Clinical Genetics
+46 90 785 28 02
par.g.larsson@regionvasterbotten.se<par.g.larsson@regionvasterbotten.se%20>
regionvasterbotten.se
1177.se/vasterbotten

Postal address: SE 901 85 Umeå
Visiting address: Laboratory Medicine, Building 6M, 2nd floor
----
Umeå University
Dept. of Medical Biosciences
901 87 Umeå
+46 70 618 99 95
par.larsson@umu.se<mailto:par.larsson@umu.se>

Postal address: SE 901 87 Umeå
Visiting address: Laboratory Medicine, Building 6M, 3nd floor

[Message part 2 (text/html, inline)]

Send a report that this bug log contains spam.