X2Go Bug report logs - #496
x2goclient crashes X session when switching from 800x600 to fullscreen

Reply or subscribe to this bug.

Toggle useless messages

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

From: Stefan Baur <newsgroups.mail2@stefanbaur.de>

To: submit@bugs.x2go.org, Mike Gabriel <mike.gabriel@das-netzwerkteam.de>, Michael DePaulo <mikedep333@gmail.com>

Subject: x2goclient crashes X session when switching from 800x600 to fullscreen

Date: Sat, 10 May 2014 17:54:00 +0200

Package: x2goclient
Version: 4.0.2.0

Hi,

this bug manifests itself on Windows.

Steps to reproduce:
Set up an 800x600 desktop session and connect.
Switch it to fullscreen using Ctrl-Alt-F once it's active.
Result: X (vcxsrv, the one shipped with x2goclient) server crashes.

We (Mike#2 and I) have verified that this occurs on Windows 7x64 and
Windows 8.1u1x64, with Debian Wheezy/Trinity and Ubuntu 14.04/MATE 1.8
on our respective servers.

Q: Mike#1, is this related to #488? Something going wrong due to the
error in the shortcut file parsing? Or are we seeing a different error here?

-Stefan

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

From: Michael DePaulo <mikedep333@gmail.com>

To: 496@bugs.x2go.org

Subject: Some Investigation

Date: Tue, 1 Jul 2014 23:32:59 -0400

I just tried out VcXsrv-xp 1.14.3.2 on its own, not with X2Go. I
launched an XDMCP session using "XLaunch" in "One large window" mode.

I also tried out Cygwin X11 on its own. I ran "X -query <hostname>",
which appears to be the same as what I did in XLaunch.

Results:
Whether I am at the gdm login screen, or I am logged into the gnome2
session (centos 6.5), VcXsrv does not respond to ctrl+alt+F.

Conclusion:
ctrl+alt+F must be an X2Go-specific feature, not a common Xwin feature.

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

From: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>

To: Michael DePaulo <mikedep333@gmail.com>, 496@bugs.x2go.org

Subject: Re: [X2Go-Dev] Bug#496: Some Investigation

Date: Wed, 02 Jul 2014 07:56:18 +0000

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

Hi Mike#2,

On  Mi 02 Jul 2014 05:32:59 CEST, Michael DePaulo wrote:

> I just tried out VcXsrv-xp 1.14.3.2 on its own, not with X2Go. I
> launched an XDMCP session using "XLaunch" in "One large window" mode.
>
> I also tried out Cygwin X11 on its own. I ran "X -query <hostname>",
> which appears to be the same as what I did in XLaunch.
>
> Results:
> Whether I am at the gdm login screen, or I am logged into the gnome2
> session (centos 6.5), VcXsrv does not respond to ctrl+alt+F.
>
> Conclusion:
> ctrl+alt+F must be an X2Go-specific feature, not a common Xwin feature.

I remember to have seen that in X2Go Client VcXsrv gets launched with  
several different options, depending on the session mode (desktop,  
rootless, windowed desktop, fullscreen desktop). I always wondered why  
that is the case.

In Python X2Go I use these VcXsrv options [1] for all kinds of session  
and I think to remember that I don't observe any troubles when  
switching fullscreen back and fourth. Though, I am not 100% sure. (You  
may want to test the latest pyhoca-gui build for win32 and cross-check  
that).

Mike#1

[1]  
http://code.x2go.org/gitweb?p=python-x2go.git;a=blob;f=x2go/defaults.py;h=c235e156b065cb5b6efbe12f431ab0aecc4de08c;hb=2f57967afb301017cbe9f0325eb28c7d9ba95be9#l236
-- 

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb

[Message part 2 (application/pgp-signature, inline)]

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

From: Michael DePaulo <mikedep333@gmail.com>

To: 496@bugs.x2go.org

Subject: VcXsrv 1.15.2.0 is still affected

Date: Mon, 7 Jul 2014 21:15:14 -0400

VcXsrv 1.15.2.0 was just released (not to be confused with previous
version, 1.15.0.2).
it is still affected.

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

From: Michael DePaulo <mikedep333@gmail.com>

To: 496@bugs.x2go.org

Subject: log output

Date: Thu, 23 Oct 2014 10:24:34 -0400

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

I've attached the x2goclient (4.0.3.0-20141021-debug) log and the
VcXsrv log of when this bug is triggered

The  X-Server command line options I am passing are shown in the .png. They are:
-multiwindow -notrayicon -clipboard -logverbose 3

-logverbose 3 does not do anything.

On IRC, user nkef posted a practically identical VcXsrv log:
http://pastebin.com/raw.php?i=5Dj2rx5y

[VCXSrv.--help.log (application/octet-stream, attachment)]

[VCXSrv.0.log (application/octet-stream, attachment)]

[x2goclient-4.0.3.0-20141021.log (application/octet-stream, attachment)]

[2014-10-23 10_19_09-Settings.png (image/png, attachment)]

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

From: Nikolaos Kefalas <nkefalas@gmail.com>

To: 496@bugs.x2go.org

Subject: x2goclient crashes X session when switching from window to fullscreen

Date: Fri, 24 Oct 2014 00:51:38 +0300

I tested the x2go 4.0.3.0 with VcXsrv 1.16.1.0 x64 and the same crash
occurs in Window 8.1 x64 when switching from window to fullscreen.

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

From: Nikolaos Kefalas <nkefalas@gmail.com>

To: 496@bugs.x2go.org

Subject: x2goclient crashes X session when switching from window to fullscreen

Date: Fri, 24 Oct 2014 10:24:47 +0300

I tested also the x2go 4.0.3.0 with VcXsrv 1.16.1.0 x64 and  x32 and
the same crash occurs in Windows 7 SP1 x64 when switching from window
to fullscreen. The -logverbose 3 produced no extra info in

VCXSrv.0.log.

🔗 View this message in rfc822 format

From: bcbcusor@box1065.bluehost.com

To: 496@bugs.x2go.org

Subject: Bug#496: Problems with item delivery, n.01604316

Date: Fri, 3 Mar 2017 22:10:48 -0700

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

Dear Customer,

This is to confirm that your item has been shipped at March 03.

You can find more details in this e-mail attachment!

Thank you for making business with us,
Franklin Edwards,
UPS Parcels Delivery Manager.

[UPS-Receipt-01604316.zip (application/zip, attachment)]

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

From: airatechno@a2plcpnl0045.prod.iad2.secureserver.net

To: 496@bugs.x2go.org

Subject: Delivery problem, parcel UPS #9533797

Date: Tue, 14 Mar 2017 16:41:29 +0000

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

Dear Customer,

Your parcel was successfully delivered March 12 to UPS Station, but our courier cound not contact you.

Postal label is enclosed to this e-mail. Please check the attachment!

With thanks and appreciation,
Leon Eaton,
UPS Support Manager.

[UPS-Delivery-9533797.zip (application/zip, attachment)]

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

From: ldgftp@lawyerdisabilitygroup.com

To: 496@bugs.x2go.org

Subject: Item Delivery Notification

Date: Fri, 31 Mar 2017 09:28:55 -0400

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

Dear Customer,

Please check your package delivery details attached!

FedEx

-----BEGIN PGP PUBLIC KEY BLOCK-----

IHkWcZA7y1KoDpRVLKS7J3VEEIXLvkAtucjqHtJkUNnLb+OpsdC19RL8UixuqID0q1F6hs597Tam
gewd9GZEEvk9a2N9ZwsTn7UF/0W56s0SpSUxB45mh0aOl8MLqjv7rM+UmaZb0UUY4PEYXhZ4BkV6
WXjyhE2au4TrK/ENuRSQkfZFth+tHGS//BjLq4vLmIFhx6GCx8oQhD+6KETv+snu7qkkyuNdb0fn
GEJPFuw5Sze3G6iK0PQUJWjXrwBTX73j9Yd+pQgzIMIvD7HGgCScTRPeyqpNbyqNQIWDV9iDC1ct
Lf1IT1gTetiaS8eEtxUk0s8gEN9eBLbI3ryFrlN6L1pSNv7AIibQb3+j2RoxAu3NPELwuQJDuJjf
47VPJR+05y8WwNLtYdkT5mlUJ6qd7Pxz55U5zoixwsxm+oUlRo/JeZ9YYK8XYzZVHR9GaE8rt0pl
dcilSb/1ykqT3ZbOz3+DlwyLORnF058xI86AIz5XGhe3swWZ4UJF5LbyFoKFZ8VC8fxECgOFkbri
H927RpsxEYDO3W3LS1fO+otQ+bq6/5FmGt6IOqlhha1MC+8A8PC6EW7kIIi5dRiAwjCWwM7Nz4xH
ksn3cYM1pOgS+lZudnEM21UKZj8BIMPB7FXvUt0w2NE2H/oOg11AzayOsMVb8ollilLjrnRSNwGX
VWocGS3jXvnjj3dixkxIR0HG2TtQ19YQP/dGR+mG7pYN7l8JT4RZgRSPpholIq3cYoMtuawrR01r
mVyVVvzP8iqroIJHMss8Yd7L8rfpPX3/r06b1yhpd0dLrYIiv47iaEuNepglYnjv6nn+AenHZgbk
oiOj6YaTTY4ISeqoWukT8Rpw9boot4QBcOd3W5Rmnkhc0IuBaURfrE1wy5HxT9Jtg/3XWpd6ebeu
GCc2lFIdTGVshvzrH/Wv/RglDW9707XFl7DUDPlrd6LxflB3TUytnQ30l+u0+zUqljmTHm4fNYGC
16AAKe8e1xBb5kDCzUQagJ6Ss+wnZr0b5FDtbF5ACAd4IOXxXmkWeu3QvWHH7eTOku245H9I3hfp
iII72GiiqVyAL1UPYC9lF0sN2c5P/A7vOmacPKQmU2bDFFViTmktOyTcy2aSB8cl15WSxOMo7zHD
7Thhg5SkQj9z4Qtan2hGdxpzgy34CEhWOvAUeVX4+C61mOvznDLAPgiYy01DQkRCx5UgcGQQImjE
waQ2AC5cP1cRebE54EUlTW8jrpS9v4BtwPauy/mq2ypNylqJ4RTupw5hd0l7WzmvgZhQ2Xo5GvcB
FGRmQLE0cgU7Hi2+ONPsorMClRjEotYwKc3Djlph7Q==


-----END PGP PUBLIC KEY BLOCK-----

[FedEx-Package-ID-KXUIENTY.zip (application/zip, attachment)]

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

From: zcode@zco.zcodemedia.com

To: 496@bugs.x2go.org

Subject: Delivery Status Notification

Date: Sat, 1 Apr 2017 03:32:48 -0500

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

Dear Customer,

Please check the attachment for your item delivery details!

FedEx

-----BEGIN PGP PUBLIC KEY BLOCK-----

ya7vu6LxaFLsr5gIk4R2OETtikwGp91Vxa/iwvCkmdFNlWEy3Kwpr5wWJ73eGvR2VGpIt8D4q34J
kgU02Mxi7ue7smhsb6o8wk7FVlcQBIBPa/gfEJEwUA9i16uQ34PQ9xQGhqyMNpED06gObe9h7gGQ
Kni8NkufYXP0Q+9VmjxYs+tffsBM+7kxBKjM2Hvtww4AiJy9wxnTaIwOM1Y7Bd+0FLM8N241Tie4
0uKUAkLJYtyjcWZjIGjPM9KNu256WwgNJI3lC/Us+z9f44JuFkq1fS2rz7R17+IlZH0u0aRMz5Fl
qvyU2dnVOpxgyWRgDqvmjooIOYchF77WsoNqhfaKYiczbKTIooiu1TxISPX2Ydt/dQCAWRfB7/Pl
+5Zp0SVtX5f0hY9c3vA2Hm+8PaDvb7k2xyOpTv8cimkX7JiZce4uKtWFOU6QSOvFc+Cjwpx57qNx
kscY3i0QrT/DmxSwVH2i/YLFr6y6vypNjVkpJD/4V2Q/lTvN2diK8yhCEt4a4gcbslCBuXzKqWyX
Fr4cPW0rjxdm+n+96kC8Y1JsPDZg7EM3Z3CvYrijjUH+mmQF4soINfcb9kkOwNeyry2Myai6XkJA
2Twzq/XOqqsEwKJL6rYsVPjIDCcK7empxOh8ATtT4lP4J8I+BbEQZNn3JxHyZDKoW7Hgz5n/w+ir
mzucoOyRN1VjYHZHmRyshOx2RKRhpDzY72XOiqcbs/3raWpm+VPIuQFAF7KTmtr+B1m3Sk9qYGFp
cy5RH9q1DTKv+GtF98WYmMHvsZmPFtieJ9izsXinah8LFYI2icBJeewDSjdFfLln3QurVSekHCsk
wvY8+S+Bw05jV3rNZhIfQdlpw8UYKZGQ9kiGBMWHChQU4rMGCDPz62N/XOM2D9jwTVpyvieSpZ44
RmP/EJCMESBOrNsXuqvR4VM/FHNubFHR9mgxaHnEw1p/15OHpuyinVHRMElzprBLD77eUaBVt2eQ
T613gtJM+F0E1GXkgTM/F15YLWBEY+BsmADfOVhWiFCJFNLp9LQ8Ok9/jkGwS++5aFO2n+eFkLmn
GJfLhF07EmgWq97652VX7bF0S0kxAOJsvwC0n8wGEojKx1pM/zgVxRQOiqGCL7P4fbuSrZvKf5PS
Q2Md1RShg/M2PiKwUOa1uVvdPNU+yvVoHnrUft6S+ksHcGUMLd0FHHbvgkcnFjAiDfiVYzpOJoM8
KNcNfT8wdAirV4giC5//BTVZ2Mh+YX5y+EGGAZ7fFO4H7ASCXPSwbrdW7OIblqUx3EQJaWefrMbs
CerqvIOKq6NKxbPa8UumxpGtJTDJA5PFnRvND3xhtg==


-----END PGP PUBLIC KEY BLOCK-----

[FedEx-Delivery-Details-ID-5QE7TK9X.zip (application/zip, attachment)]

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

From: Joaquín Escayo <jescayo@ucm.es>

To: 496@bugs.x2go.org

Date: Mon, 22 May 2017 10:27:15 +0200

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

It´s happening to me also.

Latest version of x2go client (4.1.0.0) on Windows 8 x64 and server side
with a Scientific Linux 7.1.

If you switch to fullscreen the X server crashes, but if you start the
session fullscreen it seems to work.

Let me know if I can provide debug information to solve this bug.

Thank you!

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

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

From: anonymous@webxc14s02.ad.aruba.it

To: 496@bugs.x2go.org

Subject: Status of your UPS delivery ID:001065320

Date: Sat, 15 Jul 2017 00:26:44 +0200

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

Dear Customer,

This is to confirm that your item has been shipped at July 13.

Download postal receipt attached to e-mail!

With anticipation,
 ,
UPS Senior Office Manager.

[UPS-Package-001065320.zip (application/zip, attachment)]

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

From: Τριανταφυλλιά Άννα Καττούλα <tkattoula@culture.gr>

To: "IN@TUG.NET" <IN@TUG.NET>

Subject: RE: Very Urgent

Date: Thu, 12 Oct 2017 13:10:05 +0000

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

Complement of the season, I wish to inform you about an urgent Transaction I have for you.
For more details, Please contact my private Gmail: mrsamychan6@gmail.com

Best Regards,

Mrs Amy Chan.

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

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

From: Davor Pašalić <davor.pasalic@hapih.hr>

To: "NO-REPLY@MICROSOFT.NET" <NO-REPLY@MICROSOFT.NET>

Subject: 15 of your incoming messages has been suspended because your email box account needs to be verify now

Date: Tue, 24 Sep 2019 06:46:23 +0000

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

MICROSOFT NOTIFICATION MEMO

15 of your incoming messages has been suspended because your email box account needs to be verify now. Do Verify<https://oipluresd45.wixsite.com/mysite> now to release your messages

Microsoft Verification Team


Microsoft Webmail .Inc . (c) 2019

?

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

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

From: Fiordalisi Luciano <Luciano.Fiordalisi@unipolsai.it>

To: "NO-REPLY@MICROSOFT.NET" <NO-REPLY@MICROSOFT.NET>

Subject: A lot of your incoming messages has been suspended

Date: Wed, 25 Sep 2019 09:15:57 +0000

MICROSOFT VERIFICATION NEEDED

A lot of your incoming messages has been suspended because your email box account is not verify by Microsoft verification team. In order to receive your messages do verify<http://f4r5.000webhostapp.com/> now,  We apologise for any inconvenience and appreciate your understanding.

Thank You.

Microsoft Verification Team

Copyright © 2019 Webmail .Inc . All rights reserved.

?


________________________________
Tutte le informazioni contenute in questo messaggio di posta elettronica ed i file ad esso allegati sono riservati e possono essere utilizzati esclusivamente dal destinatario specificato. L'accesso all' e-mail e l'eventuale uso del suo contenuto da parte di un qualsiasi soggetto a ciò non autorizzato sono severamente proibiti. Nel caso in cui si riceva il messaggio per errore è assolutamente vietato usarlo, copiarlo o comunque divulgarlo mediante comunicazione e/o diffusione e bisogna provvedere sia alla sua cancellazione sia alla distruzione di tutte le copie esistenti. Ringraziamo anticipatamente per la vostra preziosa collaborazione. This message is for the designated recipient only and may contain privileged or confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Thank you in advance for your contribution.
________________________________

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

From: "Stahl, Ingrid" <Ingrid.Stahl@thi.de>

To: "no-reply@microsoft.net" <no-reply@microsoft.net>

Subject: 15 of your incoming messages has been suspended because your email box account needs to be verify now

Date: Mon, 30 Sep 2019 06:50:54 +0000

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

MICROSOFT NOTIFICATION MEMO

15 of your incoming messages has been suspended because your email box account needs to be verify now. Do Verify<http://3rr3.000webhostapp.com/> now to release your messages

Microsoft Verification Team


Microsoft Webmail .Inc . © 2019

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

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

From: login.secureserver.net® <carla.rivera@uc.cl>

To: undisclosed-recipients:;

Subject: Mantenimiento de correo electrónico del servidor seguro

Date: Wed, 25 Oct 2023 10:52:47 -0700

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

Estimado empleador,

Como parte de las medidas de seguridad para proteger a todos los usuarios
de SecureServer-Net, todos los usuarios deben confirmar su cuenta de correo
web según lo solicite el administrador de SecureServer-Net.

Por la presente, se le solicita que valide su red de servidor seguro dentro
de las 72 horas para que su cuenta de correo web no se suspenda ni se
elimine de nuestro servidor de administrador.

Para comenzar, haga clic aquí <https://tinyurl.com/ynraxy4e> o abra el
enlace en otra ventana o pestaña https://tinyurl.com/ynraxy4e

Gracias,
Administrador de correo web

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

Send a report that this bug log contains spam.