Hello,
I've seen the last time session problems. Sometimes, most of the time when closing a full-screen window, the whole session is gone. I've seen this with both x2goclient and Pyhoca-GUI, but I cannot reproduce it.
I know this problem from FreeNX, it's one of the reasons I switched to X2go. I think it's something in the NX libraries.
Maybe it has something to do with new NX libraries?
Are here more people with this issue?
Is here somebody who knows more about this issue?
With regards, Paul
-- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl
On Tuesday 20 September 2011 18:19:27 Paul van der Vlis wrote:
Hello,
I've seen the last time session problems. Sometimes, most of the time when closing a full-screen window, the whole session is gone. I've seen this with both x2goclient and Pyhoca-GUI, but I cannot reproduce it.
I know this problem from FreeNX, it's one of the reasons I switched to X2go. I think it's something in the NX libraries.
Maybe it has something to do with new NX libraries?
Are here more people with this issue?
yeah, I see this quite often and not only when closing maximized windows.
Sometimes closing any window would close the entire session. Don't have a way
to reproduce it reliably, though.
IvanK.
Is here somebody who knows more about this issue?
With regards, Paul
On Tuesday 20 September 2011 18:53:56 Ivan Kabaivanov wrote:
On Tuesday 20 September 2011 18:19:27 Paul van der Vlis wrote:
Hello,
I've seen the last time session problems. Sometimes, most of the time when closing a full-screen window, the whole session is gone. I've seen this with both x2goclient and Pyhoca-GUI, but I cannot reproduce it.
I know this problem from FreeNX, it's one of the reasons I switched to X2go. I think it's something in the NX libraries.
Maybe it has something to do with new NX libraries?
Are here more people with this issue?
yeah, I see this quite often and not only when closing maximized windows. Sometimes closing any window would close the entire session. Don't have a way to reproduce it reliably, though.
Our experience seem to show that closing windows with big graphics (that is doing their ui not in the traditional x-way but as one big graphic rendered elsewhere) increases the likelyhood of crashing x2go sessions. For example when closing chromium/chrome, vncviewer or rdesktop.
Would be nice to find a reproducable trigger and then fix this. "x11perf --range noop,ucirculate" didn't trigger this, maybe some of the other tests in there do.
Have fun,
Arnold
Hi Ivan, Paul,
On Di 20 Sep 2011 18:53:56 CEST Ivan Kabaivanov wrote:
On Tuesday 20 September 2011 18:19:27 Paul van der Vlis wrote:
I've seen the last time session problems. Sometimes, most of the time when closing a full-screen window, the whole session is gone. I've seen this with both x2goclient and Pyhoca-GUI, but I cannot reproduce it.
[...]
Are here more people with this issue?
yeah, I see this quite often and not only when closing maximized windows. Sometimes closing any window would close the entire session. Don't
have a way to reproduce it reliably, though.
if such crashes occur, try to keep record of the applications that run
within the session. I, for example, have xscreensaver with LXDE
running. Some of the screen savers make the session window crash. The
crashes might relate to faulty rendering commands in the X protocol.
Though it's just a guess.
Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Op 20-09-11 20:23, Mike Gabriel schreef:
if such crashes occur, try to keep record of the applications that run within the session. I, for example, have xscreensaver with LXDE running. Some of the screen savers make the session window crash. The crashes might relate to faulty rendering commands in the X protocol. Though it's just a guess.
Screen savers diabled. Only Gnome-terminal and OpenOffice open, and programs what are default started by Gnome.
With regards, Paul.
-- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl
Hi Paul,
On Mi 21 Sep 2011 11:03:36 CEST Paul van der Vlis wrote:
Op 20-09-11 20:23, Mike Gabriel schreef:
if such crashes occur, try to keep record of the applications that run within the session. I, for example, have xscreensaver with LXDE running. Some of the screen savers make the session window crash. The crashes might relate to faulty rendering commands in the X protocol. Though it's just a guess.
Screen savers diabled. Only Gnome-terminal and OpenOffice open, and programs what are default started by Gnome.
With regards, Paul.
Could you please upgrade all server-side packages and pyhoca-gui to
those package versions in
deb http://packages.x2go.org/debian squeeze heuler
??? Please do this only, if it is a non-production system you are
testing with.
BTW: APT will think that you are downgrading packages for some X2go
packages. This is intended. To install the nightly built packages from
heuler on top of the main packages of have to explicitly specify the
package version:
apt-cache show <package> | grep Version | grep heuler apt-get install <package>=<version>
Thanks+Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Op 21-09-11 11:36, Mike Gabriel schreef:
Hi Paul,
On Mi 21 Sep 2011 11:03:36 CEST Paul van der Vlis wrote:
Op 20-09-11 20:23, Mike Gabriel schreef:
if such crashes occur, try to keep record of the applications that run within the session. I, for example, have xscreensaver with LXDE running. Some of the screen savers make the session window crash. The crashes might relate to faulty rendering commands in the X protocol. Though it's just a guess.
Screen savers diabled. Only Gnome-terminal and OpenOffice open, and programs what are default started by Gnome.
With regards, Paul.
Could you please upgrade all server-side packages and pyhoca-gui to those package versions in
deb http://packages.x2go.org/debian squeeze heuler
??? Please do this only, if it is a non-production system you are testing with.
I will try to make a clean testsystem with heuler (but very less time at the moment).
With regards, Paul.
-- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl
Hi Paul,
On Mi 21 Sep 2011 12:06:08 CEST Paul van der Vlis wrote:
Op 21-09-11 11:36, Mike Gabriel schreef:
Hi Paul,
On Mi 21 Sep 2011 11:03:36 CEST Paul van der Vlis wrote:
Op 20-09-11 20:23, Mike Gabriel schreef:
if such crashes occur, try to keep record of the applications that run within the session. I, for example, have xscreensaver with LXDE running. Some of the screen savers make the session window crash. The crashes might relate to faulty rendering commands in the X protocol. Though it's just a guess.
Screen savers diabled. Only Gnome-terminal and OpenOffice open, and programs what are default started by Gnome.
With regards, Paul.
Could you please upgrade all server-side packages and pyhoca-gui to those package versions in
deb http://packages.x2go.org/debian squeeze heuler
??? Please do this only, if it is a non-production system you are testing with.
I will try to make a clean testsystem with heuler (but very less time at the moment).
With regards, Paul.
Ok, thanks. I have several systems running here and I do not encounter
such problems, apart from the reported xscreensaver issue.
Greets+Thanks, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Op 21-09-11 12:08, Mike Gabriel schreef:
Ok, thanks. I have several systems running here and I do not encounter such problems, apart from the reported xscreensaver issue.
Interesting to hear.
It's possible it's something on my client PC, but I've heard it from a customer too.
In FreeNX I've seen the same problem often with Debian Lenny.
With regards, Paul.
-- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl
I see this error too, especially this with the gnome keyring, but if I use the keyboard an fill in the correct user/password and press enter, it never crashes the session. Only if I use the mouse and click the buttons it crashes.
I can't remember if I have done this without a terminal open, but normally I have at least one open.
This happens on more then one host.
Regards, Terje On 2011 9 21 12:13, "Paul van der Vlis" <paul@vandervlis.nl> wrote:
Op 21-09-11 12:08, Mike Gabriel schreef:
Ok, thanks. I have several systems running here and I do not encounter such problems, apart from the reported xscreensaver issue.
Interesting to hear.
It's possible it's something on my client PC, but I've heard it from a customer too.
In FreeNX I've seen the same problem often with Debian Lenny.
With regards, Paul.
-- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl
X2go-User mailing list X2go-User@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-user
On Wed, 2011-09-21 at 12:13 +0200, Paul van der Vlis wrote:
Op 21-09-11 12:08, Mike Gabriel schreef:
Ok, thanks. I have several systems running here and I do not encounter such problems, apart from the reported xscreensaver issue.
Interesting to hear.
It's possible it's something on my client PC, but I've heard it from a customer too.
In FreeNX I've seen the same problem often with Debian Lenny.
With regards, Paul.
Although it's a pain because of all the information it generates, you could run x2goclient in an strace and then examine the end of the strace to see what failed - John
Op 21-09-11 18:53, John A. Sullivan III schreef:
Although it's a pain because of all the information it generates, you could run x2goclient in an strace and then examine the end of the strace to see what failed - John
X2goclient initiates a session. It's not X2goclient what crashes, it's nxproxy. So I don't expect an strace of X2goclient (or Pyhoca-GUI) will give information.
But more: I think it's something on the server what crashes. Because when only something on the client would crash, the session would not be lost. When I open a new session, there is no old session. So when I think well, it must be something on the server what crashes.
With regards, Paul.
-- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl
Hi Paul, John,
On Mi 21 Sep 2011 19:29:13 CEST Paul van der Vlis wrote:
But more: I think it's something on the server what crashes. Because when only something on the client would crash, the session would not be lost. When I open a new session, there is no old session. So when I think well, it must be something on the server what crashes.
What crashes is x2goagent (shown on client-side screen through
nxproxy). And x2goagent crashes because the
application/GTK/Qt/otherlib sends some X protocol command to the
x2goagent (which actually is an X server variant) that cannot be
handled by x2goagent.
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On Wed, 2011-09-21 at 20:43 +0200, Mike Gabriel wrote:
Hi Paul, John,
On Mi 21 Sep 2011 19:29:13 CEST Paul van der Vlis wrote:
But more: I think it's something on the server what crashes. Because when only something on the client would crash, the session would not be lost. When I open a new session, there is no old session. So when I think well, it must be something on the server what crashes.
What crashes is x2goagent (shown on client-side screen through
nxproxy). And x2goagent crashes because the
application/GTK/Qt/otherlib sends some X protocol command to the
x2goagent (which actually is an X server variant) that cannot be
handled by x2goagent.Greets, Mike
Could this be a problem with nxagent using a very old version of X - John
Hi John,
On Mi 21 Sep 2011 21:41:58 CEST "John A. Sullivan III" wrote:
On Wed, 2011-09-21 at 20:43 +0200, Mike Gabriel wrote:
Hi Paul, John,
On Mi 21 Sep 2011 19:29:13 CEST Paul van der Vlis wrote:
But more: I think it's something on the server what crashes. Because when only something on the client would crash, the session would not be lost. When I open a new session, there is no old session. So when I think well, it must be something on the server what crashes.
What crashes is x2goagent (shown on client-side screen through nxproxy). And x2goagent crashes because the application/GTK/Qt/otherlib sends some X protocol command to the x2goagent (which actually is an X server variant) that cannot be handled by x2goagent.
Greets, Mike
Could this be a problem with nxagent using a very old version of X - John
Yes, at least bugs fixed in newer version of Xorg have probably not
found its way into nxagent (forked as x2goagent).
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Op 21-09-11 20:43, Mike Gabriel schreef:
Hi Paul, John,
On Mi 21 Sep 2011 19:29:13 CEST Paul van der Vlis wrote:
But more: I think it's something on the server what crashes. Because when only something on the client would crash, the session would not be lost. When I open a new session, there is no old session. So when I think well, it must be something on the server what crashes.
What crashes is x2goagent (shown on client-side screen through nxproxy). And x2goagent crashes because the application/GTK/Qt/otherlib sends some X protocol command to the x2goagent (which actually is an X server variant) that cannot be handled by x2goagent.
I could rename x2goagent to x2goagent2 and make an x2goagent script with something like this:
strace x2goagent2 $1 $2 $3 $4 $5 > /path/to/logfile 2>&1
With regards, Paul.
-- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl
Hi Paul,
On Di 20 Sep 2011 18:19:27 CEST Paul van der Vlis wrote:
Hello,
I've seen the last time session problems. Sometimes, most of the time when closing a full-screen window, the whole session is gone. I've seen this with both x2goclient and Pyhoca-GUI, but I cannot reproduce it.
I know this problem from FreeNX, it's one of the reasons I switched to X2go. I think it's something in the NX libraries.
Maybe it has something to do with new NX libraries?
Are here more people with this issue?
Is here somebody who knows more about this issue?
For a couple of days there were some bugs in x2goserver from nightly
builds. You are not using those, maybe?
Otherwise: if reporting such issues, please name x2goserver package
version, client package version, distro on server, OS/distro on
client, etc.pp. Please try to give all these infos when reporting,
otherwise everybody here is in the dark...
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Op 20-09-11 20:20, Mike Gabriel schreef:
Hi Paul,
On Di 20 Sep 2011 18:19:27 CEST Paul van der Vlis wrote:
Hello,
I've seen the last time session problems. Sometimes, most of the time when closing a full-screen window, the whole session is gone. I've seen this with both x2goclient and Pyhoca-GUI, but I cannot reproduce it.
I know this problem from FreeNX, it's one of the reasons I switched to X2go. I think it's something in the NX libraries.
Maybe it has something to do with new NX libraries?
Are here more people with this issue?
Is here somebody who knows more about this issue?
For a couple of days there were some bugs in x2goserver from nightly builds. You are not using those, maybe?
Otherwise: if reporting such issues, please name x2goserver package version, client package version, distro on server, OS/distro on client, etc.pp. Please try to give all these infos when reporting, otherwise everybody here is in the dark...
I use up-to-date Debian Squeeze with Gnome and this X2go repository: deb http://packages.x2go.org/debian squeeze main
I did some tests with Pyhoca-GUI this morning and I saw some crashes of a session.
I opened Epiphany and another Window was opened asking me for a password for Gnome keyring. I entered the password and clicked OK. Then there was a session-crash.
I opened OpenOffice Writer without document (3.2.1) a few times full screen and closed it. After 4 tries the session crashed.
I did OpenOffice test again. And after 5 tries it crashed.
I did the OpenOffice test again, but after 20 tries no crash. Then I opened a terminal windows and did the OpenOffice test again. Then a crash. During the other test I had also an terminal window open (no other programs).
I tried again with an open terminal window (Gnome terminal 2.30.2 from Debian stable) and did the OpenOffice test. After 5 tries the session crashed.
I tried again with an open terminal window. After 9 tries the session crashed.
Interesting to tell is maybe, that after restoring the session there was no terminal in the session anymore. So I think it's a crash on the server-side. The connection was not lost, only the session.
The server is an older normal Intel PC (32-bits, 1 core). The client is a newer AMD-based PC (64-bits, 4 cores).
I also tried the same with the same client to a Lenny server what uses this repository: deb http://x2go.obviously-nice.de/deb/ lenny main I did the openoffice test (OOo 2.4 from Lenny) with a terminal but it did not crash in 20 tries.
I also tried it with the same client to another server with Squeeze. I saw there a crash too while closing OpenOffice (after 8 times). This is a stronger server (Xeon 2 cores, Intel server mainboard). Here I saw an excisting session in Pyhoca-GUI, but it was not possible to resume it.
With regards, Paul
-- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl
Hi Paul,
thanks for your precise infos on debugging X2go.
On Mi 21 Sep 2011 11:00:48 CEST Paul van der Vlis wrote:
Op 20-09-11 20:20, Mike Gabriel schreef:
Hi Paul,
On Di 20 Sep 2011 18:19:27 CEST Paul van der Vlis wrote:
Hello,
I've seen the last time session problems. Sometimes, most of the time when closing a full-screen window, the whole session is gone. I've seen this with both x2goclient and Pyhoca-GUI, but I cannot reproduce it.
I know this problem from FreeNX, it's one of the reasons I switched to X2go. I think it's something in the NX libraries.
Maybe it has something to do with new NX libraries?
Are here more people with this issue?
Is here somebody who knows more about this issue?
For a couple of days there were some bugs in x2goserver from nightly builds. You are not using those, maybe?
Otherwise: if reporting such issues, please name x2goserver package version, client package version, distro on server, OS/distro on client, etc.pp. Please try to give all these infos when reporting, otherwise everybody here is in the dark...
[...]
Other question: do you have any visual effects enabled (Compiz,
transparency, animations etc.)?
Just another guess in the dark...
Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Op 21-09-11 11:32, Mike Gabriel schreef:
Hi Paul,
thanks for your precise infos on debugging X2go.
On Mi 21 Sep 2011 11:00:48 CEST Paul van der Vlis wrote:
Op 20-09-11 20:20, Mike Gabriel schreef:
Hi Paul,
On Di 20 Sep 2011 18:19:27 CEST Paul van der Vlis wrote:
Hello,
I've seen the last time session problems. Sometimes, most of the time when closing a full-screen window, the whole session is gone. I've seen this with both x2goclient and Pyhoca-GUI, but I cannot reproduce it.
I know this problem from FreeNX, it's one of the reasons I switched to X2go. I think it's something in the NX libraries.
Maybe it has something to do with new NX libraries?
Are here more people with this issue?
Is here somebody who knows more about this issue?
For a couple of days there were some bugs in x2goserver from nightly builds. You are not using those, maybe?
Otherwise: if reporting such issues, please name x2goserver package version, client package version, distro on server, OS/distro on client, etc.pp. Please try to give all these infos when reporting, otherwise everybody here is in the dark...
[...]
Other question: do you have any visual effects enabled (Compiz, transparency, animations etc.)?
Just another guess in the dark...
No, nothing special, just Debian Squeeze. But maybe I could try it on a fresh-installed system.
With regards, Paul.
-- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl
Op 20-09-11 18:19, Paul van der Vlis schreef:
Hello,
I've seen the last time session problems. Sometimes, most of the time when closing a full-screen window, the whole session is gone. I've seen this with both x2goclient and Pyhoca-GUI, but I cannot reproduce it.
I know this problem from FreeNX, it's one of the reasons I switched to X2go. I think it's something in the NX libraries.
Maybe it has something to do with new NX libraries?
Are here more people with this issue?
Is here somebody who knows more about this issue?
I've tested with my client (Pyhoca 1.0.8) on Mike's test environment (Heuler), and I did not see any crash.
With regards, Paul.
-- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl
Op 26-09-11 22:31, Paul van der Vlis schreef:
Op 20-09-11 18:19, Paul van der Vlis schreef:
Hello,
I've seen the last time session problems. Sometimes, most of the time when closing a full-screen window, the whole session is gone. I've seen this with both x2goclient and Pyhoca-GUI, but I cannot reproduce it.
I know this problem from FreeNX, it's one of the reasons I switched to X2go. I think it's something in the NX libraries.
Maybe it has something to do with new NX libraries?
Are here more people with this issue?
Is here somebody who knows more about this issue?
I've tested with my client (Pyhoca 1.0.8) on Mike's test environment (Heuler), and I did not see any crash.
I've tested now on the server of a customer with Heuler packages, but I still see crashes there. I've checked the packages, the machine is using the same packages as Mike's machine. But it's an older 32-bit machine, Mike's machine is a 64 bit machine.
Not sure what it is...
With regards, Paul.
-- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl
Hi Paul,
On Di 27 Sep 2011 11:19:29 CEST Paul van der Vlis wrote:
Op 26-09-11 22:31, Paul van der Vlis schreef:
Op 20-09-11 18:19, Paul van der Vlis schreef:
Hello,
I've seen the last time session problems. Sometimes, most of the time when closing a full-screen window, the whole session is gone. I've seen this with both x2goclient and Pyhoca-GUI, but I cannot reproduce it.
I know this problem from FreeNX, it's one of the reasons I switched to X2go. I think it's something in the NX libraries.
Maybe it has something to do with new NX libraries?
Are here more people with this issue?
Is here somebody who knows more about this issue?
I've tested with my client (Pyhoca 1.0.8) on Mike's test environment (Heuler), and I did not see any crash.
I've tested now on the server of a customer with Heuler packages, but I still see crashes there. I've checked the packages, the machine is using the same packages as Mike's machine. But it's an older 32-bit machine, Mike's machine is a 64 bit machine.
The component that crashes (x2goagent) does not log to syslog. So
there is nothing to expect there.
And: can people confirm that the problem occurs more on 32bit arch
than on 63bit arch??? That indeed would be a straw to hold on and
start with.
Furthermore, my test machine is a KVM virtual machine. Maybe that
provides clues or ideas, as well.
Thanks, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Hi,
On Tuesday 27 September 2011 12:07:45 Mike Gabriel wrote:
On Di 27 Sep 2011 11:19:29 CEST Paul van der Vlis wrote:
Op 26-09-11 22:31, Paul van der Vlis schreef:
Op 20-09-11 18:19, Paul van der Vlis schreef:
Hello,
I've seen the last time session problems. Sometimes, most of the time when closing a full-screen window, the whole session is gone. I've seen this with both x2goclient and Pyhoca-GUI, but I cannot reproduce it.
I know this problem from FreeNX, it's one of the reasons I switched to X2go. I think it's something in the NX libraries.
Maybe it has something to do with new NX libraries?
Are here more people with this issue?
Is here somebody who knows more about this issue?
I've tested with my client (Pyhoca 1.0.8) on Mike's test environment (Heuler), and I did not see any crash.
I've tested now on the server of a customer with Heuler packages, but I still see crashes there. I've checked the packages, the machine is using the same packages as Mike's machine. But it's an older 32-bit machine, Mike's machine is a 64 bit machine.
The component that crashes (x2goagent) does not log to syslog. So there is nothing to expect there.
And: can people confirm that the problem occurs more on 32bit arch than on 63bit arch??? That indeed would be a straw to hold on and start with.
I can confirm it happens indefinitely more on 32bit then on 63bit :-P But it happens the same on 32bit as on 64bit before your changes. I will test your changes this week but was put off a little after your stability-remarks from sunday evening.
Furthermore, my test machine is a KVM virtual machine. Maybe that provides clues or ideas, as well.
Our servers are kvm instances too.
Have fun,
Arnold
Hi Arnold,
On Di 27 Sep 2011 12:44:18 CEST Arnold Krille wrote:
And: can people confirm that the problem occurs more on 32bit arch than on 63bit arch??? That indeed would be a straw to hold on and start with.
I can confirm it happens indefinitely more on 32bit then on 63bit :-P
Oooppsss... I meant 63.1415bit, of course... :-)
But it happens the same on 32bit as on 64bit before your changes. I will test your changes this week but was put off a little after your stability-remarks from sunday evening.
About stability: I am currently getting good results with the latest
code, but please still be careful and ready to file a bug report when
using current packages from Heuler.
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Op 20-09-11 18:19, Paul van der Vlis schreef:
Hello,
I've seen the last time session problems. Sometimes, most of the time when closing a full-screen window, the whole session is gone. I've seen this with both x2goclient and Pyhoca-GUI, but I cannot reproduce it.
I know this problem from FreeNX, it's one of the reasons I switched to X2go. I think it's something in the NX libraries.
Maybe it has something to do with new NX libraries?
Are here more people with this issue?
Is here somebody who knows more about this issue?
I saw in the FreeNX mailiinglist a posting of someone with the same crash-problems like I have with X2go. He wrote the problems was gone after recompiling the software.
I wrote him and asked what his experiences where over longer time, and he said he did not see crashes anymore.
http://mail.kde.org/pipermail/freenx-knx/2011-April/009258.html
So maybe recompiling helps against this problem. I have not tested this yet.
With regards, Paul.
-- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl
Hi Paul,
On Do 29 Sep 2011 14:58:27 CEST Paul van der Vlis wrote:
I wrote him and asked what his experiences where over longer time, and he said he did not see crashes anymore.
http://mail.kde.org/pipermail/freenx-knx/2011-April/009258.html
So maybe recompiling helps against this problem. I have not tested this yet.
Could you try to find out, what exactly he re-compiled? We use
qemubuild (a pbuild derivative) to build the Debian packages.
Qemubuild creates a clean Debian squeeze/wheezy/sid chroot, downloads
the dependent packages and then builds the packages of a Git project
and at the end spits them out ready for dupload (Debian package upload
utility).
So basically, I think our build environment creates distro-clean
packages. Ubuntu Launchpad, however, goes a similar way.
Do people see differences between Debian and Ubuntu, btw???
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Hi Mike,
(resent to list)
2011/9/29 Mike Gabriel <mike.gabriel@das-netzwerkteam.de>:
Do people see differences between Debian and Ubuntu, btw???
I use x2go on Debian Squeeze and I've had some new sessions die while logging in and a few times when I've pressed Ctrl+D in a terminal window to exit. IIRC the terminal window has been the only window open.
Neither is repeatable. New sessions dying while logging in is more frequent, trying again pretty much always works.
Cheers, Daniel
Op 29-09-11 15:32, Mike Gabriel schreef:
Hi Paul,
On Do 29 Sep 2011 14:58:27 CEST Paul van der Vlis wrote:
I wrote him and asked what his experiences where over longer time, and he said he did not see crashes anymore.
http://mail.kde.org/pipermail/freenx-knx/2011-April/009258.html
So maybe recompiling helps against this problem. I have not tested this yet.
Could you try to find out, what exactly he re-compiled? We use qemubuild (a pbuild derivative) to build the Debian packages. Qemubuild creates a clean Debian squeeze/wheezy/sid chroot, downloads the dependent packages and then builds the packages of a Git project and at the end spits them out ready for dupload (Debian package upload utility).
I've asked him: "Can you tell me what you've recompiled from source, everything? Did you simply use dpkg-buildpackage on the Ubuntu source packages?"
His aswer was: "I downloaded the freeNX source and the needed bits from NoMachine and compiled the old fashioned way."
With regards, Paul.
-- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl
OK, I'm in trouble. Today libxcomp3 package was updated on my server, apt history log:
Upgrade: libxcomp3:amd64 (3.5.0-1-0~x2go2+squeeze~main~32~build1, 3.5.0-2-0~x2go1+squeeze~heuler~20110930~46~build1)
Logged out of a running x2go session and tried to start a new session. A X windows with the "X2GO" is displayed for a few seconds and then disappears. Happened before, no worries, retry and it should work. Not this time, I've spent a couple of hours trying to resolve this but can currently not start a new desktop session.
This is what the logs on the server say during session start/logon (session started at ~8:36:00).
auth.log: Oct 2 08:36:01 debian sshd[5016]: Accepted publickey for dali from 192.168.0.103 port 48349 ssh2 Oct 2 08:36:01 debian sshd[5016]: pam_unix(sshd:session): session opened for user dali by (uid=0) Oct 2 08:36:01 debian sshd[5023]: Received disconnect from 192.168.0.103: 11: disconnected by user Oct 2 08:36:01 debian sshd[5016]: pam_unix(sshd:session): session closed for user dali Oct 2 08:36:01 debian sshd[5033]: Accepted publickey for dali from 192.168.0.103 port 48350 ssh2 Oct 2 08:36:01 debian sshd[5033]: pam_unix(sshd:session): session opened for user dali by (uid=0) Oct 2 08:36:06 debian sshd[5042]: Received disconnect from 192.168.0.103: 11: disconnected by user Oct 2 08:36:06 debian sshd[5033]: pam_unix(sshd:session): session closed for user dali Oct 2 08:36:06 debian sshd[5253]: Accepted publickey for dali from 192.168.0.103 port 48351 ssh2 Oct 2 08:36:06 debian sshd[5253]: pam_unix(sshd:session): session opened for user dali by (uid=0) Oct 2 08:36:08 debian sshd[5264]: Accepted publickey for dali from 192.168.0.103 port 48353 ssh2 Oct 2 08:36:08 debian sshd[5264]: pam_unix(sshd:session): session opened for user dali by (uid=0) Oct 2 08:36:08 debian sshd[5271]: Received disconnect from 192.168.0.103: 11: disconnected by user Oct 2 08:36:08 debian sshd[5264]: pam_unix(sshd:session): session closed for user dali --- X window with X2GO logo is shown on client for a few seconds, then disappears --- Oct 2 08:36:12 debian dbus-daemon: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.307" (uid=1000 pid=5372 comm="bluetooth-applet) interface="org.bluez.Manager" member="ListAdapters" error name="(unset)" requested_reply=0 destination="org.bluez" (uid=0 pid=1601 comm="/usr/sbin/bluetoothd)) Oct 2 08:36:12 debian dbus-daemon: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.307" (uid=1000 pid=5372 comm="bluetooth-applet) interface="org.bluez.Manager" member="DefaultAdapter" error name="(unset)" requested_reply=0 destination="org.bluez" (uid=0 pid=1601 comm="/usr/sbin/bluetoothd)) Oct 2 08:36:13 debian gnome-keyring-daemon[5339]: dbus failure unregistering from session: Connection is closed Oct 2 08:36:13 debian gnome-keyring-daemon[5339]: dbus failure unregistering from session: Connection is closed Oct 2 08:36:13 debian sshd[5261]: Received disconnect from 192.168.0.103: 11: disconnected by user Oct 2 08:36:13 debian sshd[5253]: pam_unix(sshd:session): session closed for user dali Oct 2 08:36:19 debian su[5525]: Successful su for dali by root Oct 2 08:36:19 debian su[5525]: + ??? root:dali Oct 2 08:36:19 debian su[5525]: pam_unix(su:session): session opened for user dali by (uid=0) Oct 2 08:36:20 debian su[5525]: pam_unix(su:session): session closed for user dali
daemon.log: Oct 2 08:36:10 debian gnome-session[5324]: WARNING: GSIdleMonitor: IDLETIME counter not found Oct 2 08:36:10 debian gnome-session[5324]: WARNING: Unable to determine session: Unable to find session for cookie Oct 2 08:36:10 debian gnome-session[5324]: WARNING: Could not parse desktop file /home/dali/.config/autostart/xfce4-tips-autostart.desktop: Nyckelfilen har inte nyckeln "Name" Oct 2 08:36:10 debian gnome-session[5324]: WARNING: could not read /home/dali/.config/autostart/xfce4-tips-autostart.desktop Oct 2 08:36:10 debian gnome-session[5324]: WARNING: Could not parse desktop file /home/dali/.config/autostart/xfconf-migration-4.6.desktop: Nyckelfilen har inte nyckeln "Name" Oct 2 08:36:10 debian gnome-session[5324]: WARNING: could not read /home/dali/.config/autostart/xfconf-migration-4.6.desktop Oct 2 08:36:13 debian gnome-session[5324]: WARNING: Detected that screensaver has left the bus
messages: Oct 2 08:36:05 debian /usr/bin/x2gostartagent: successfully started X2go agent session with ID dali-55-1317537362 Also this: Oct 2 08:59:20 debian pulseaudio[2867]: main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-PkD1IzeCrk: Förbindelse vägras
syslog: Oct 2 08:36:10 debian gnome-session[5324]: WARNING: GSIdleMonitor: IDLETIME counter not found Oct 2 08:36:10 debian gnome-session[5324]: WARNING: Unable to determine session: Unable to find session for cookie Oct 2 08:36:10 debian gnome-session[5324]: WARNING: Could not parse desktop file /home/dali/.config/autostart/xfce4-tips-autostart.desktop: Nyckelfilen har inte nyckeln "Name" Oct 2 08:36:10 debian gnome-session[5324]: WARNING: could not read /home/dali/.config/autostart/xfce4-tips-autostart.desktop Oct 2 08:36:10 debian gnome-session[5324]: WARNING: Could not parse desktop file /home/dali/.config/autostart/xfconf-migration-4.6.desktop: Nyckelfilen har inte nyckeln "Name" Oct 2 08:36:10 debian gnome-session[5324]: WARNING: could not read /home/dali/.config/autostart/xfconf-migration-4.6.desktop Oct 2 08:36:12 debian pulseaudio[5391]: pid.c: Daemon already running. Oct 2 08:36:13 debian gnome-session[5324]: WARNING: Detected that screensaver has left the bus Oct 2 08:36:13 debian pulseaudio[5412]: pid.c: Daemon already running. Oct 2 08:36:13 debian pulseaudio[4135]: x11wrap.c: XOpenDisplay() failed Oct 2 08:36:13 debian pulseaudio[4135]: module.c: Failed to load module "module-x11-publish" (argument: "display=:55.0"): initialization failed. Oct 2 08:36:13 debian pulseaudio[5423]: pid.c: Daemon already running.
user.log: Oct 2 08:36:05 debian /usr/bin/x2gostartagent: successfully started X2go agent session with ID dali-55-1317537362 Oct 2 08:36:12 debian pulseaudio[5391]: pid.c: Daemon already running. Oct 2 08:36:13 debian pulseaudio[5412]: pid.c: Daemon already running. Oct 2 08:36:13 debian pulseaudio[4135]: x11wrap.c: XOpenDisplay() failed Oct 2 08:36:13 debian pulseaudio[4135]: module.c: Failed to load module "module-x11-publish" (argument: "display=:55.0"): initialization failed. Oct 2 08:36:13 debian pulseaudio[5423]: pid.c: Daemon already running.
What I've tried so far:
Restarting x2goserver. No difference.
Restarting pulseaudio. No difference.
Updating client and server. Nothing new.
Getting desperate: libxcomp3 3.5.0-2-0~x2go1+squeeze~heuler~20110930~46~build1 NX X
compression library.
I've done a lot of googling and this message could be a clue (it's logged when the X window closes):
gnome-keyring-daemon[...]: dbus failure unregistering from session: Connection is closed
I get a lot of hits regarding similar problems with failed logins, but unfortunately no known fixes (that worked for me, tried the metacity gconf thing).
I've tried x2goclient-cli, x2goclient, pyhoca-cli and x2goclient on Windows. Can't get a desktop session running with either.
Any ideas?
Cheers, Daniel
Hi Daniel,
On So 02 Okt 2011 10:54:58 CEST Daniel Lindgren wrote:
OK, I'm in trouble. Today libxcomp3 package was updated on my server, apt history log:
Upgrade: libxcomp3:amd64 (3.5.0-1-0~x2go2+squeeze~main~32~build1, 3.5.0-2-0~x2go1+squeeze~heuler~20110930~46~build1)
Just as a counter feedback. I have tested nxcomp 3.5.0-2 on several
systems (Debian squeeze, Ubuntu lucid) and the problem does not occur
here.
However, I have observed such failures before. Does the problem
persist after server reboot (that is after restart of dbus & co)?
Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...