I am running x2goclient on my laptop and the x2go server is on my dekstop, both systems are running xubuntu 20.10.
Running an xfce session works perfectly but running a single application session doesn't. It appears to work until the application pops up momentarily and then disappears. The application *is* still running but is not displayed.
The end of the session.log shows:-
Info: keyboard blocking directory created:
'/home/chris/.x2go/C-chris-50-1610816188_stRdigikam_>
Info: Keycode conversion is off
Session: Session started at 'Sat Jan 16 16:56:30 2021'.
nxagentImportProperty: WARNING! Failed to convert remote window
[79978240] importing property [>
WARNING: Invalid window in ClientMessage xclient.window [0x7a6].
WARNING: Invalid window in ClientMessage xclient.window [0x7a6].
WARNING: Invalid window in ClientMessage xclient.window [0x7a6].
WARNING: Invalid window in ClientMessage xclient.window [0x7a6].
WARNING: Invalid window in ClientMessage xclient.window [0x7a6].
WARNING: Invalid window in ClientMessage xclient.window [0x4a00072].
WARNING: Invalid window in ClientMessage xclient.window [0x4a00072].
WARNING: Invalid window in ClientMessage xclient.window [0x4a0007b].
WARNING: Invalid window in ClientMessage xclient.window [0x4a0007b].
WARNING: Invalid window in ClientMessage xclient.window [0x4a00082].
WARNING: Invalid window in ClientMessage xclient.window [0x4a00082].
Does this indicate what the problem might be?
-- Chris Green
Hmm, what version of nxagent are you using?
On Mon, Jan 18, 2021 at 11:31 AM Chris Green <cl@isbd.net> wrote:
I am running x2goclient on my laptop and the x2go server is on my dekstop, both systems are running xubuntu 20.10.
Running an xfce session works perfectly but running a single application session doesn't. It appears to work until the application pops up momentarily and then disappears. The application *is* still running but is not displayed.
The end of the session.log shows:-
Info: keyboard blocking directory created: '/home/chris/.x2go/C-chris-50-1610816188_stRdigikam_> Info: Keycode conversion is off Session: Session started at 'Sat Jan 16 16:56:30 2021'. nxagentImportProperty: WARNING! Failed to convert remote window [79978240] importing property [> WARNING: Invalid window in ClientMessage xclient.window [0x7a6]. WARNING: Invalid window in ClientMessage xclient.window [0x7a6]. WARNING: Invalid window in ClientMessage xclient.window [0x7a6]. WARNING: Invalid window in ClientMessage xclient.window [0x7a6]. WARNING: Invalid window in ClientMessage xclient.window [0x7a6]. WARNING: Invalid window in ClientMessage xclient.window [0x4a00072]. WARNING: Invalid window in ClientMessage xclient.window [0x4a00072]. WARNING: Invalid window in ClientMessage xclient.window [0x4a0007b]. WARNING: Invalid window in ClientMessage xclient.window [0x4a0007b]. WARNING: Invalid window in ClientMessage xclient.window [0x4a00082]. WARNING: Invalid window in ClientMessage xclient.window [0x4a00082].
Does this indicate what the problem might be?
-- Chris Green
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
The corresponding code is this: fprintf(stderr, "%s: WARNING! Failed to convert remote window [%ld] importing property [%ld]" " of type WM_STATE", __func__, (long int) wmState.icon, (long int) property);
So the whole second line is missing in your output which is strange at least. Also the property in the [] should be a number but shows up as ">" which should not be possible at all.
Uli
On Mon, Jan 18, 2021 at 11:44 AM Ulrich Sibiller <uli42@gmx.de> wrote:
Hmm, what version of nxagent are you using?
On Mon, Jan 18, 2021 at 11:31 AM Chris Green <cl@isbd.net> wrote:
I am running x2goclient on my laptop and the x2go server is on my dekstop, both systems are running xubuntu 20.10.
Running an xfce session works perfectly but running a single application session doesn't. It appears to work until the application pops up momentarily and then disappears. The application *is* still running but is not displayed.
The end of the session.log shows:-
Info: keyboard blocking directory created: '/home/chris/.x2go/C-chris-50-1610816188_stRdigikam_> Info: Keycode conversion is off Session: Session started at 'Sat Jan 16 16:56:30 2021'. nxagentImportProperty: WARNING! Failed to convert remote window [79978240] importing property [> WARNING: Invalid window in ClientMessage xclient.window [0x7a6]. WARNING: Invalid window in ClientMessage xclient.window [0x7a6]. WARNING: Invalid window in ClientMessage xclient.window [0x7a6]. WARNING: Invalid window in ClientMessage xclient.window [0x7a6]. WARNING: Invalid window in ClientMessage xclient.window [0x7a6]. WARNING: Invalid window in ClientMessage xclient.window [0x4a00072]. WARNING: Invalid window in ClientMessage xclient.window [0x4a00072]. WARNING: Invalid window in ClientMessage xclient.window [0x4a0007b]. WARNING: Invalid window in ClientMessage xclient.window [0x4a0007b]. WARNING: Invalid window in ClientMessage xclient.window [0x4a00082]. WARNING: Invalid window in ClientMessage xclient.window [0x4a00082].
Does this indicate what the problem might be?
-- Chris Green
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Info: keyboard blocking directory created: '/home/chris/.x2go/C-chris-50-1610816188_stRdigikam_>
Also shows this strange ">" where a number is expected. You are also reporting a crashing window manager. So _maybe_ your system(s) suffer from RAM defects. Can you please run a memtest?
Uli
On Mon, Jan 18, 2021 at 11:48 AM Ulrich Sibiller <uli42@gmx.de> wrote:
The corresponding code is this: fprintf(stderr, "%s: WARNING! Failed to convert remote window [%ld] importing property [%ld]" " of type WM_STATE", __func__, (long int) wmState.icon, (long int) property);
So the whole second line is missing in your output which is strange at least. Also the property in the [] should be a number but shows up as ">" which should not be possible at all.
Uli
On Mon, Jan 18, 2021 at 11:44 AM Ulrich Sibiller <uli42@gmx.de> wrote:
Hmm, what version of nxagent are you using?
On Mon, Jan 18, 2021 at 11:31 AM Chris Green <cl@isbd.net> wrote:
I am running x2goclient on my laptop and the x2go server is on my dekstop, both systems are running xubuntu 20.10.
Running an xfce session works perfectly but running a single application session doesn't. It appears to work until the application pops up momentarily and then disappears. The application *is* still running but is not displayed.
The end of the session.log shows:-
Info: keyboard blocking directory created: '/home/chris/.x2go/C-chris-50-1610816188_stRdigikam_> Info: Keycode conversion is off Session: Session started at 'Sat Jan 16 16:56:30 2021'. nxagentImportProperty: WARNING! Failed to convert remote window [79978240] importing property [> WARNING: Invalid window in ClientMessage xclient.window [0x7a6]. WARNING: Invalid window in ClientMessage xclient.window [0x7a6]. WARNING: Invalid window in ClientMessage xclient.window [0x7a6]. WARNING: Invalid window in ClientMessage xclient.window [0x7a6]. WARNING: Invalid window in ClientMessage xclient.window [0x7a6]. WARNING: Invalid window in ClientMessage xclient.window [0x4a00072]. WARNING: Invalid window in ClientMessage xclient.window [0x4a00072]. WARNING: Invalid window in ClientMessage xclient.window [0x4a0007b]. WARNING: Invalid window in ClientMessage xclient.window [0x4a0007b]. WARNING: Invalid window in ClientMessage xclient.window [0x4a00082]. WARNING: Invalid window in ClientMessage xclient.window [0x4a00082].
Does this indicate what the problem might be?
-- Chris Green
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
On Mon, Jan 18, 2021 at 11:50:11AM +0100, Ulrich Sibiller wrote:
Info: keyboard blocking directory created: '/home/chris/.x2go/C-chris-50-1610816188_stRdigikam_>
Also shows this strange ">" where a number is expected. You are also reporting a crashing window manager. So _maybe_ your system(s) suffer from RAM defects. Can you please run a memtest?
I suspect the > maybe me not noticing a truncated/folded line of text, I'll go and redo the tests.
This system has been running for several years without showing any signs of errors, I don't believe it could do this if there was a memory problme. Absulutely nothing else has shown any problems.
-- Chris Green
On Mon, Jan 18, 2021 at 11:44:13AM +0100, Ulrich Sibiller wrote:
Hmm, what version of nxagent are you using?
nxagent 2:3.5.99.24-1 amd64
It's what comes 'out of the box' when you install x2go server on [x]ubuntu 20.10.
On Mon, Jan 18, 2021 at 11:31 AM Chris Green <cl@isbd.net> wrote:
I am running x2goclient on my laptop and the x2go server is on my dekstop, both systems are running xubuntu 20.10.
Running an xfce session works perfectly but running a single application session doesn't. It appears to work until the application pops up momentarily and then disappears. The application *is* still running but is not displayed.
The end of the session.log shows:-
Info: keyboard blocking directory created: '/home/chris/.x2go/C-chris-50-1610816188_stRdigikam_> Info: Keycode conversion is off Session: Session started at 'Sat Jan 16 16:56:30 2021'. nxagentImportProperty: WARNING! Failed to convert remote window [79978240] importing property [> WARNING: Invalid window in ClientMessage xclient.window [0x7a6]. WARNING: Invalid window in ClientMessage xclient.window [0x7a6]. WARNING: Invalid window in ClientMessage xclient.window [0x7a6]. WARNING: Invalid window in ClientMessage xclient.window [0x7a6]. WARNING: Invalid window in ClientMessage xclient.window [0x7a6]. WARNING: Invalid window in ClientMessage xclient.window [0x4a00072]. WARNING: Invalid window in ClientMessage xclient.window [0x4a00072]. WARNING: Invalid window in ClientMessage xclient.window [0x4a0007b]. WARNING: Invalid window in ClientMessage xclient.window [0x4a0007b]. WARNING: Invalid window in ClientMessage xclient.window [0x4a00082]. WARNING: Invalid window in ClientMessage xclient.window [0x4a00082].
Does this indicate what the problem might be?
-- Chris Green
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
-- Chris Green
On Mon, Jan 18, 2021 at 1:48 PM Chris Green <cl@isbd.net> wrote:
On Mon, Jan 18, 2021 at 11:44:13AM +0100, Ulrich Sibiller wrote:
Hmm, what version of nxagent are you using?
nxagent 2:3.5.99.24-1 amd64
It's what comes 'out of the box' when you install x2go server on [x]ubuntu 20.10.
-25 is current with -26 on the horizon (probably this month). You can try to install newer packages as described here: https://github.com/ArcticaProject/nx-libs/blob/3.6.x/README.md
I suspect the > maybe me not noticing a truncated/folded line of text, I'll go and redo the tests.
thx
This system has been running for several years without showing any signs of errors, I don't believe it could do this if there was a memory problme. Absulutely nothing else has shown any problems.
Well, running a memtest from time to time does not hurt but I agree that if everything else is running fine that chances for defective memory are low. Keep in mind that memory can die anytime, we see that daily at the place I work (one HDDs are dying more often).
Uli
On Mon, Jan 18, 2021 at 02:09:13PM +0100, Ulrich Sibiller wrote:
On Mon, Jan 18, 2021 at 1:48 PM Chris Green <cl@isbd.net> wrote:
On Mon, Jan 18, 2021 at 11:44:13AM +0100, Ulrich Sibiller wrote:
Hmm, what version of nxagent are you using?
nxagent 2:3.5.99.24-1 amd64
It's what comes 'out of the box' when you install x2go server on [x]ubuntu 20.10.
-25 is current with -26 on the horizon (probably this month). You can try to install newer packages as described here: https://github.com/ArcticaProject/nx-libs/blob/3.6.x/README.md
I suspect the > maybe me not noticing a truncated/folded line of text, I'll go and redo the tests.
thx
This system has been running for several years without showing any signs of errors, I don't believe it could do this if there was a memory problme. Absulutely nothing else has shown any problems.
Well, running a memtest from time to time does not hurt but I agree that if everything else is running fine that chances for defective memory are low. Keep in mind that memory can die anytime, we see that daily at the place I work (one HDDs are dying more often).
I just ran memtest, two complete passes with no errors, so I think that's probably ruled out.
I've been playing with this some more and the results seem quite strange, there's some sort of connection between all of the problems I've reported recently (i.e. the xfwm crash and the single process not working, etc.).
I'll spend some time experimenting to see if I can come up with some sort of consistent pattern and then start a new thread.
-- Chris Green