date:20211108

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] X2Go server on Fedora 35 KDE

2021-11-08 Thread Neal Becker

Maybe I misunderstood.  Is this only a problem running a kde session?

On Mon, Nov 8, 2021, 2:36 PM Michael Eager  wrote:

> There still seems to be a problem.
>
> I installed the new libGL.so incorrectly.  The old one was still
> installed.
>
> When I connect to the F35 VM, I see the Plasma startup screen,
> then the window resizes to full screen, and goes black.
>
> I'll try building an earlier version of Mesa's libGL.so.
>
> On 11/7/21 5:34 PM, Michael Eager wrote:
> > It was unclear what to do with x2goglx or x2goglx2.
> >
> > I built the libGL.so library and installed the directory under
> > /usr/lib64.  I'm now able to connect using x2goclient.
> >
> > On 11/7/21 1:47 PM, Ulrich Sibiller wrote:
> >> That is probably related to kde requiring recent opengl support which
> >> x2go does not offer currently. May try this workaround:
> >> https://wiki.x2go.org/doku.php/wiki:development:glx-xlib-workaround
> >>
> >> Uli
> >>
> >> On Sun, Nov 7, 2021 at 10:31 PM Michael Eager  wrote:
> >>>
> >>> When I try to connect to a F35 LXD VM using x2goclient, I get an
> >>> error "Cannot Exec startkde".  This can be fixed by either
> >>> running "sudo ln -s /usr/bin/startplasma-x11 /usr/bin/startkde"
> >>> in the VM or changing the command in x2goclient.
> >>>
> >>> When a screen is displayed, it is completely black, with an
> >>> arrow cursor.
> >>>
> >>> I've seen a couple bug reports about black screen, but none
> >>> seem to be relevant.
> >>>
> >>> --
> >>> Michael Eager
> >>> ___
> >>> 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
>
> ___
> 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] X2Go server on Fedora 35 KDE

2021-11-08 Thread Michael Eager


There still seems to be a problem.

I installed the new libGL.so incorrectly.  The old one was still
installed.

When I connect to the F35 VM, I see the Plasma startup screen,
then the window resizes to full screen, and goes black.

I'll try building an earlier version of Mesa's libGL.so.

On 11/7/21 5:34 PM, Michael Eager wrote:

It was unclear what to do with x2goglx or x2goglx2.

I built the libGL.so library and installed the directory under
/usr/lib64.  I'm now able to connect using x2goclient.

On 11/7/21 1:47 PM, Ulrich Sibiller wrote:

That is probably related to kde requiring recent opengl support which
x2go does not offer currently. May try this workaround:
https://wiki.x2go.org/doku.php/wiki:development:glx-xlib-workaround

Uli

On Sun, Nov 7, 2021 at 10:31 PM Michael Eager  wrote:


When I try to connect to a F35 LXD VM using x2goclient, I get an
error "Cannot Exec startkde".  This can be fixed by either
running "sudo ln -s /usr/bin/startplasma-x11 /usr/bin/startkde"
in the VM or changing the command in x2goclient.

When a screen is displayed, it is completely black, with an
arrow cursor.

I've seen a couple bug reports about black screen, but none
seem to be relevant.

--
Michael Eager
___
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


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

Re: [X2Go-User] X2Go server on Fedora 35 KDE

2021-11-08 Thread Michael Eager


I did not file a bug report.

On 11/8/21 3:58 AM, Neal Becker wrote:

Was this reported to Fedora bugtracker?  Do we need an update to Fedora package?

On Sun, Nov 7, 2021 at 8:34 PM Michael Eager  wrote:


It was unclear what to do with x2goglx or x2goglx2.

I built the libGL.so library and installed the directory under
/usr/lib64.  I'm now able to connect using x2goclient.

On 11/7/21 1:47 PM, Ulrich Sibiller wrote:

That is probably related to kde requiring recent opengl support which
x2go does not offer currently. May try this workaround:
https://wiki.x2go.org/doku.php/wiki:development:glx-xlib-workaround

Uli

On Sun, Nov 7, 2021 at 10:31 PM Michael Eager  wrote:


When I try to connect to a F35 LXD VM using x2goclient, I get an
error "Cannot Exec startkde".  This can be fixed by either
running "sudo ln -s /usr/bin/startplasma-x11 /usr/bin/startkde"
in the VM or changing the command in x2goclient.

When a screen is displayed, it is completely black, with an
arrow cursor.

I've seen a couple bug reports about black screen, but none
seem to be relevant.

--
Michael Eager
___
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






___
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 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] X2Go server on Fedora 35 KDE

2021-11-08 Thread Neal Becker

Was this reported to Fedora bugtracker?  Do we need an update to Fedora package?

On Sun, Nov 7, 2021 at 8:34 PM Michael Eager  wrote:
>
> It was unclear what to do with x2goglx or x2goglx2.
>
> I built the libGL.so library and installed the directory under
> /usr/lib64.  I'm now able to connect using x2goclient.
>
> On 11/7/21 1:47 PM, Ulrich Sibiller wrote:
> > That is probably related to kde requiring recent opengl support which
> > x2go does not offer currently. May try this workaround:
> > https://wiki.x2go.org/doku.php/wiki:development:glx-xlib-workaround
> >
> > Uli
> >
> > On Sun, Nov 7, 2021 at 10:31 PM Michael Eager  wrote:
> >>
> >> When I try to connect to a F35 LXD VM using x2goclient, I get an
> >> error "Cannot Exec startkde".  This can be fixed by either
> >> running "sudo ln -s /usr/bin/startplasma-x11 /usr/bin/startkde"
> >> in the VM or changing the command in x2goclient.
> >>
> >> When a screen is displayed, it is completely black, with an
> >> arrow cursor.
> >>
> >> I've seen a couple bug reports about black screen, but none
> >> seem to be relevant.
> >>
> >> --
> >> Michael Eager
> >> ___
> >> 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



-- 
Those who don't understand recursion are doomed to repeat it
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

[X2Go-User] X2Go on openSUSE

2021-11-08 Thread Peter Keller


Dear list,

The instructions for installing X2Go on openSUSE systems on the wiki 
page at  seem 
very outdated. The X2Go repositories only provide binaries up to 
openSUSE 15.1. These still worked on 15.2 in my hands, but at the 
current openSUSE release (15.3) support for Qt4 has been dropped and the 
X2Go repository binaries will no longer work on this distribution 
(unless it has been upgraded from 15.2, and the Qt4 libraries retained).


The correct location for X2Go on SUSE systems now seems to be 
https://download.opensuse.org/repositories/X11:/RemoteDesktop:/x2go// 
as mentioned in this forum thread: 
.


Perhaps someone with write access to the wiki could update the SUSE page?

Regards,

P.


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

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

Re: [X2Go-User] X2Go server on Fedora 35 KDE

Re: [X2Go-User] X2Go server on Fedora 35 KDE

Re: [X2Go-User] X2Go server on Fedora 35 KDE

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

Re: [X2Go-User] X2Go server on Fedora 35 KDE

[X2Go-User] X2Go on openSUSE

7 matches

Site Navigation

Mail list logo

Footer information