Re: [X2Go-User] Unable to start a desktop

2021-11-14 Thread Ulrich Sibiller
well, the messages clearly state what is missing: x2goagent is a link
to nxagent. And nxdialog is a relatively new package with just one
binary. You CAN probably replace it by a link to x2goclient if you
cannot make it work on mageia. It is used to display a message dialog
window. So probably nxproxy wants to tell you something ;-)

Uli


On Wed, Nov 10, 2021 at 10:48 PM  wrote:
>
> Hello,
>
> I have tried to install x2goserver on mageia 8 LiveCD:
> As a result, if I connect to this Server I can see on the serverside:
> /usr/bin/x2gostartagent: line 443: x2goagent: command not found
>
> On nxproxy:
> NXTransDialog: WARNING! Couldn't start '/usr/bin/nxdialog'. Error is 2
> 'No such file or directory'.
> NXTransDialog: WARNING! Trying with path
> '/usr/NX/bin:/opt/NX/bin:/usr/local/NX/bin:/usr/local/sbin:/usr/sbin:/usr/local/bin:/usr/bin:/usr/lib64/qt5/bin'.
> NXTransDialog: WARNING! Couldn't start 'nxclient'. Error is 2 'No such
> file or directory'.
> NXTransDialog: WARNING! Couldn't start '/usr/bin/nxdialog'. Error is 2
> 'No such file or directory'.
> NXTransDialog: WARNING! Trying with path
> '/usr/NX/bin:/opt/NX/bin:/usr/local/NX/bin:/usr/local/sbin:/usr/sbin:/usr/local/bin:/usr/bin:/usr/lib64/qt5/bin'.
> NXTransDialog: WARNING! Couldn't start 'nxclient'. Error is 2 'No such
> file or directory'.
>
> It's time to sleep now,
> Good night.
> ___
> 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


Re: [X2Go-User] Unable to start a desktop

2021-11-10 Thread x2go-user

Hello,

I have tried to install x2goserver on mageia 8 LiveCD:
As a result, if I connect to this Server I can see on the serverside:
/usr/bin/x2gostartagent: line 443: x2goagent: command not found

On nxproxy:
NXTransDialog: WARNING! Couldn't start '/usr/bin/nxdialog'. Error is 2
'No such file or directory'.
NXTransDialog: WARNING! Trying with path
'/usr/NX/bin:/opt/NX/bin:/usr/local/NX/bin:/usr/local/sbin:/usr/sbin:/usr/local/bin:/usr/bin:/usr/lib64/qt5/bin'.
NXTransDialog: WARNING! Couldn't start 'nxclient'. Error is 2 'No such
file or directory'.
NXTransDialog: WARNING! Couldn't start '/usr/bin/nxdialog'. Error is 2
'No such file or directory'.
NXTransDialog: WARNING! Trying with path
'/usr/NX/bin:/opt/NX/bin:/usr/local/NX/bin:/usr/local/sbin:/usr/sbin:/usr/local/bin:/usr/bin:/usr/lib64/qt5/bin'.
NXTransDialog: WARNING! Couldn't start 'nxclient'. Error is 2 'No such
file or directory'.

It's time to sleep now,
Good night.
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user


Re: [X2Go-User] Unable to start a desktop

2021-11-10 Thread Papoteur

Le 09/11/2021 à 23:16, x2go-u...@jugra.de a écrit :

Hello,

maybe offtopic here, but where can I get mageia lxc templates for tests?

Best Regards,
Juri Grabowski


Hello,

I didn't find anything for LXC.

But you have a Docker one: https://hub.docker.com/_/mageia

You can also use a Live flavour https://www.mageia.org/fr/downloads/

It depends of what you expect.

Papoteur

___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user


Re: [X2Go-User] Unable to start a desktop

2021-11-09 Thread x2go-user

Hello,

maybe offtopic here, but where can I get mageia lxc templates for tests?

Best Regards,
Juri Grabowski
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user


Re: [X2Go-User] Unable to start a desktop

2021-11-09 Thread Papoteur

Le 09/11/2021 à 00:15, x2go-u...@jugra.de a écrit :

Hello,

can you try please to terminate old server session and start one with 
kdrive

enabled?

Best Regards,
Juri Grabowski


Hello,

I don't have x2gokdrive. It is not yet packaged, I have downloaded the 
source tarball, but I don't an easy way to compile it.


Was it just an idea to run a try, or is it really a way that should 
explored?


Papoteur

___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user


Re: [X2Go-User] Unable to start a desktop

2021-11-08 Thread Papoteur

Le 07/11/2021 à 22:45, Ulrich Sibiller a écrit :

On Sun, Nov 7, 2021 at 10:09 PM Papoteur  wrote:

I'm trying to repair the packaging of x2go in Mageia.

It was functional in Mageia 7, but this is no more the case in Mageia 8
or cauldron (development version).



I use also nxagent-3.5.99.25-1.mga8 and nxproxy-3.5.99.25-1.mga8
packaged for Mageia 8. Thus I have linked xgoagent  to
/usr/lib64/nx/bin/nxagent

Why aren't you using the current 3.5.99.26?


Using pyhoca, I can establish the session with the VM, either with the
main user or with a test user, using password. But when I try to launch
the desktop or a single application like Terminal, this fails. In the
journal of the server, i get:

   sshd[96864]: Accepted password for test from 192.168.1.14 port 35740 ssh2
   systemd-logind[683]: [] New session c25 of user test.
   systemd[1]: Started Session c25 of user test.
   sshd[96864]: pam_unix(sshd:session): session opened for user test by
(uid=0)
   /usr/local/bin/x2gostartagent[97691]: successfully started X2Go Agent
session with ID test-93-1636213441_stDLXQt_dp24
   sshd[96871]: error: connect_to 127.0.0.1 port 51346: failed.
   sshd[96871]: error: connect_to 127.0.0.1 port 51346: failed.

First, as a test, disable printing, sound and file sharing. This will
reduce the number of things that can go wrong.

Then, on the server side you will find the log of the
nxagent/x2goagent in /tmp/.x2go-/C-*/session.log. What do
you see there?


I have now build the package x2goserver with release 3.5.99.26.

I caught the logs of the session:

running as X2Go Agent

NXAGENT - Version 3.5.99.26

Copyright (c) [...]

Info: Agent running with pid '6217'.
Session: Starting session at 'Mon Nov  8 19:00:56 2021'.

Not very useful.

I join an extract from the journal after establishing the session and 
when trying to start the desktop session.




  
nov. 08 21:20:18 VMm8 x2golistsessions[64213]: executing external command 
,,x2gopath'' with args: libexec
nov. 08 21:20:18 VMm8 x2golistsessions[64213]: executing external command 
,,x2gopath'' with args: libexec
nov. 08 21:20:18 VMm8 x2golistsessions[64213]: x2golistsessions has been called 
with no option
nov. 08 21:20:18 VMm8 x2golistsessions[64213]: executing external command 
,,/usr/lib64/x2go/libx2go-server-db-sqlite3-wrapper'' with args: 
listsessions,VMm8
nov. 08 21:20:18 VMm8 x2golistshadowsessions[64227]: executing external command 
,,x2gopath'' with args: libexec 

nov. 08 21:20:18 VMm8 x2golistshadowsessions[64227]: x2golistshadowsessions has 
been called with no option
nov. 08 21:20:18 VMm8 x2golistshadowsessions[64227]: executing external command 
,,/usr/lib64/x2go/libx2go-server-db-sqlite3-wrapper'' with args: 
listshadowsessions,VMm8
nov. 08 21:20:19 VMm8 x2golistmounts[64236]: executing external command 
,,x2gopath'' with args: libexec
nov. 08 21:20:19 VMm8 x2golistmounts[64236]: executing external command 
,,/usr/lib64/x2go/libx2go-server-db-sqlite3-wrapper'' with args: 
getmounts,test-59-1636397571_stDLXQt_dp24  
nov. 08 21:20:19 VMm8 x2golistmounts[64236]: db_getmounts called, session ID: 
test-59-1636397571_stDLXQt_dp24; return value:  
  
nov. 08 21:20:19 VMm8 x2golistmounts[64245]: executing external command 
,,x2gopath'' with args: libexec
nov. 08 21:20:19 VMm8 x2golistmounts[64245]: executing external command 
,,/usr/lib64/x2go/libx2go-server-db-sqlite3-wrapper'' with args: 
getmounts,test-60-1636402364_stDLXQt_dp24  
nov. 08 21:20:19 VMm8 x2golistmounts[64245]: db_getmounts called, session ID: 
test-60-1636402364_stDLXQt_dp24; return value:  
  
nov. 08 21:20:20 VMm8 x2golistsessions[64260]: executing external command 
,,x2gopath'' with args: libexec
nov. 08 21:20:20 VMm8 x2golistsessions[64260]: executing external command 
,,x2gopath'' with args: libexec
nov. 08 21:20:20 VMm8 x2golistsessions[64260]: x2golistsessions has been called 
with no option
nov. 08 21:20:20 VMm8 x2golistsessions[64260]: executing external command 
,,/usr/lib64/x2go/libx2go-server-db-sqlite3-wrapper'' with args: 
listsessions,VMm8
nov. 08 21:20:20 VMm8 /usr/bin/x2gostartagent[64291]: x2gostartagent called 
with options: 1024x768 wan 16m-jpeg-9 unix-kde-depth_24 us auto 1 D LXQt both
nov. 08 21:20:20 VMm8 /usr/lib64/x2go/x2gogetrandomport[64300]: 
x2gogetrandomport called with options:
nov. 08 21:20:20 VMm8 /usr/lib64/x2go/x2gogetrandomport[64303]: Full SSH port 

Re: [X2Go-User] Unable to start a desktop

2021-11-08 Thread Papoteur

Le 07/11/2021 à 22:45, Ulrich Sibiller a écrit :

On Sun, Nov 7, 2021 at 10:09 PM Papoteur  wrote:

I'm trying to repair the packaging of x2go in Mageia.

It was functional in Mageia 7, but this is no more the case in Mageia 8
or cauldron (development version).

I have never used or seen Mageia in action, so I have no idea how
Mageia 7 differs from Mageia 8.

At least, nx-libs has been updated from 3.5.0.33 to 3.5.99.25

I use also nxagent-3.5.99.25-1.mga8 and nxproxy-3.5.99.25-1.mga8
packaged for Mageia 8. Thus I have linked xgoagent  to
/usr/lib64/nx/bin/nxagent

Why aren't you using the current 3.5.99.26?
Because I first try with what is in the current state of  the 
distribution. I will try to update it also.



Using pyhoca, I can establish the session with the VM, either with the
main user or with a test user, using password. But when I try to launch
the desktop or a single application like Terminal, this fails. In the
journal of the server, i get:

   sshd[96864]: Accepted password for test from 192.168.1.14 port 35740 ssh2
   systemd-logind[683]: [] New session c25 of user test.
   systemd[1]: Started Session c25 of user test.
   sshd[96864]: pam_unix(sshd:session): session opened for user test by
(uid=0)
   /usr/local/bin/x2gostartagent[97691]: successfully started X2Go Agent
session with ID test-93-1636213441_stDLXQt_dp24
   sshd[96871]: error: connect_to 127.0.0.1 port 51346: failed.
   sshd[96871]: error: connect_to 127.0.0.1 port 51346: failed.

First, as a test, disable printing, sound and file sharing. This will
reduce the number of things that can go wrong.

Thanks for that tip.


Then, on the server side you will find the log of the
nxagent/x2goagent in /tmp/.x2go-/C-*/session.log. What do
you see there?

Nothing, it doesn't exist.


___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user


Re: [X2Go-User] Unable to start a desktop

2021-11-07 Thread Ulrich Sibiller
On Sun, Nov 7, 2021 at 10:09 PM Papoteur  wrote:
> I'm trying to repair the packaging of x2go in Mageia.
>
> It was functional in Mageia 7, but this is no more the case in Mageia 8
> or cauldron (development version).

I have never used or seen Mageia in action, so I have no idea how
Mageia 7 differs from Mageia 8.

> I have tried 2 clients: x2goclient 4.1.2.2 and pyhoca-gui 0.6.1.1
> packaged for Mageia 8.
>
> For the server, in a virtualbox VM, I tried to install the master
> version of x2goserver; through make && make install.

Unfortunately I have never built the x2goserver so I cannot tell you
for sure if that's the way to do it. Maybe there's more to do than
this.

> I had to change the rights to add write credential on /var/lib/x2go and
> /var/lib/x2go/x2go_session

This is how it looks on my (debian) system:
$ ls -la /var/lib/x2go/
insgesamt 52
drwxrwx---  2 x2gouser x2gouser  4096 Okt 25 22:12 .
drwxr-xr-x 69 root root  4096 Nov  6 13:50 ..
-rw-rw  1 root x2gouser 40960 Okt 25 22:12 x2go_sessions

> I use also nxagent-3.5.99.25-1.mga8 and nxproxy-3.5.99.25-1.mga8
> packaged for Mageia 8. Thus I have linked xgoagent  to
> /usr/lib64/nx/bin/nxagent

Why aren't you using the current 3.5.99.26?

> Using pyhoca, I can establish the session with the VM, either with the
> main user or with a test user, using password. But when I try to launch
> the desktop or a single application like Terminal, this fails. In the
> journal of the server, i get:
>
>   sshd[96864]: Accepted password for test from 192.168.1.14 port 35740 ssh2
>   systemd-logind[683]: [] New session c25 of user test.
>   systemd[1]: Started Session c25 of user test.
>   sshd[96864]: pam_unix(sshd:session): session opened for user test by
> (uid=0)
>   /usr/local/bin/x2gostartagent[97691]: successfully started X2Go Agent
> session with ID test-93-1636213441_stDLXQt_dp24
>   sshd[96871]: error: connect_to 127.0.0.1 port 51346: failed.
>   sshd[96871]: error: connect_to 127.0.0.1 port 51346: failed.

First, as a test, disable printing, sound and file sharing. This will
reduce the number of things that can go wrong.

Then, on the server side you will find the log of the
nxagent/x2goagent in /tmp/.x2go-/C-*/session.log. What do
you see there?

Uli
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user


[X2Go-User] Unable to start a desktop

2021-11-07 Thread Papoteur

Hello,

I'm trying to repair the packaging of x2go in Mageia.

It was functional in Mageia 7, but this is no more the case in Mageia 8 
or cauldron (development version).


I have tried 2 clients: x2goclient 4.1.2.2 and pyhoca-gui 0.6.1.1 
packaged for Mageia 8.


For the server, in a virtualbox VM, I tried to install the master 
version of x2goserver; through make && make install.


I had to change the rights to add write credential on /var/lib/x2go and 
/var/lib/x2go/x2go_session


I use also nxagent-3.5.99.25-1.mga8 and nxproxy-3.5.99.25-1.mga8 
packaged for Mageia 8. Thus I have linked xgoagent  to 
/usr/lib64/nx/bin/nxagent


Using pyhoca, I can establish the session with the VM, either with the 
main user or with a test user, using password. But when I try to launch 
the desktop or a single application like Terminal, this fails. In the 
journal of the server, i get:


 sshd[96864]: Accepted password for test from 192.168.1.14 port 35740 ssh2
 systemd-logind[683]: [] New session c25 of user test.
 systemd[1]: Started Session c25 of user test.
 sshd[96864]: pam_unix(sshd:session): session opened for user test by 
(uid=0)
 /usr/local/bin/x2gostartagent[97691]: successfully started X2Go Agent 
session with ID test-93-1636213441_stDLXQt_dp24

 sshd[96871]: error: connect_to 127.0.0.1 port 51346: failed.
 sshd[96871]: error: connect_to 127.0.0.1 port 51346: failed.


In the same time, I get: this log on the client side:


Info: Proxy running in server mode with pid '2878627'.
Session: Starting session at 'Sat Nov  6 16:46:21 2021'.
Info: Using errors file 
'/home/yves/.x2go/S-test-93-1636213441_stDLXQt_dp24/session.err'.

Info: Using stats file '/home/yves/.x2go/S-93/stats'.
Loop: WARNING! Overriding auxiliary X11 port with new value '1'.
Warning: Overriding auxiliary X11 port with new value '1'.
Info: Using abstract X11 socket in kernel namespace for accessing 
DISPLAY=:0.

Info: Connecting to remote host '127.0.0.1:51346'.
Info: Connected to remote proxy on FD#5.
Loop: PANIC! The remote NX proxy closed the connection.
Error: The remote NX proxy closed the connection.
Loop: PANIC! Failure negotiating the session in stage '7'.
Error: Failure negotiating the session in stage '7'.
Loop: PANIC! Wrong version or invalid session authentication cookie.
Error: Wrong version or invalid session authentication cookie.
Session: Terminating session at 'Sat Nov  6 16:46:29 2021'.
Session: Session terminated at 'Sat Nov  6 16:46:29 2021'.


What surprise me is that the client uses 127.0.0.1 as remote server 
address.


I have tried to open all ports on the server, in case where the firewall 
would be implied, but without more success.


I don't understand what goes wrong and what to do to debug or restore 
the normal behavior.


___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user


[X2Go-User] Unable to start a desktop

2021-11-06 Thread Papoteur

Hello,

I'm trying to repair the packaging of x2go in Mageia.

It was functional in Mageia 7, but this is no more the case in Mageia 8 
or cauldron (development version).


I have tried 2 clients: x2goclient 4.1.2.2 and pyhoca-gui 0.6.1.1 
packaged for Mageia 8.


For the server, in a virtualbox VM, I tried to install the master 
version of x2goserver; through make && make install.


I had to change the rights to add write credential on /var/lib/x2go and 
/var/lib/x2go/x2go_session


I use also nxagent-3.5.99.25-1.mga8 and nxproxy-3.5.99.25-1.mga8 
packaged for Mageia 8. Thus I have linked xgoagent  to 
/usr/lib64/nx/bin/nxagent


Using pyhoca, I can establish the session with the VM, either with the 
main user or with a test user, using password. But when I try to launch 
the desktop or a single application like Terminal, this fails. In the 
journal of the server, i get:


 sshd[96864]: Accepted password for test from 192.168.1.14 port 35740 ssh2
 systemd-logind[683]: [] New session c25 of user test.
 systemd[1]: Started Session c25 of user test.
 sshd[96864]: pam_unix(sshd:session): session opened for user test by 
(uid=0)
 /usr/local/bin/x2gostartagent[97691]: successfully started X2Go Agent 
session with ID test-93-1636213441_stDLXQt_dp24

 sshd[96871]: error: connect_to 127.0.0.1 port 51346: failed.
 sshd[96871]: error: connect_to 127.0.0.1 port 51346: failed.


In the same time, I get: this log on the client side:


Info: Proxy running in server mode with pid '2878627'.
Session: Starting session at 'Sat Nov  6 16:46:21 2021'.
Info: Using errors file 
'/home/yves/.x2go/S-test-93-1636213441_stDLXQt_dp24/session.err'.

Info: Using stats file '/home/yves/.x2go/S-93/stats'.
Loop: WARNING! Overriding auxiliary X11 port with new value '1'.
Warning: Overriding auxiliary X11 port with new value '1'.
Info: Using abstract X11 socket in kernel namespace for accessing 
DISPLAY=:0.

Info: Connecting to remote host '127.0.0.1:51346'.
Info: Connected to remote proxy on FD#5.
Loop: PANIC! The remote NX proxy closed the connection.
Error: The remote NX proxy closed the connection.
Loop: PANIC! Failure negotiating the session in stage '7'.
Error: Failure negotiating the session in stage '7'.
Loop: PANIC! Wrong version or invalid session authentication cookie.
Error: Wrong version or invalid session authentication cookie.
Session: Terminating session at 'Sat Nov  6 16:46:29 2021'.
Session: Session terminated at 'Sat Nov  6 16:46:29 2021'.


What surprise me is that the client uses 127.0.0.1 as remote server address.

I have tried to open all ports on the server, in case where the firewall 
would be implied, but without more success.


I don't understand what goes wrong and what to do to debug or restore 
the normal behavior.


___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user