Hello everybody,
after noticing this wonderful project, I started with a new openSUSE Build Service repo for x2go today:
https://build.opensuse.org/project/show/home:frispete:RemoteDesktop:x2go
since RemoteDesktop:x2go is somewhat orphaned and suffers from serious bit rot in some auxiliary packages. While at it, I've updated x2goclient to 4.1.0.1 already, and plan to update the other packages, that saw new releases, soon.
Being a heavy remote user of all kinds (ssh, vnc, rdp), this project is a perfect fit. I never got NX to cooperate nicely, but always thought, that the basic concepts are sound.
Anyway, I was able to install the x2goserver and x2goplasmabindings packages on a remote system (Leap 42.3 Virtualbox VM on a 42.3 host), and successfully connect to it with the x2goclient package, reaching out a nice and fresh KDE desktop.
So far for the good news.
After login, powerdevil crashes with signal 6 (related to non existing DimDisplay action). This in turn results in a drkonqi crash (sig 11). Probably related to these, the X2Go PLasma Bindings failed to remove the shut down and reboot actions in the K menu.
Immediately logging out results in a ksmserver crash, that effectively prevents a successful log out, hence the session can only be terminated the hard way from the X2Go client UI.
Parallel ssh sessions to the server appear locked at some point (not immediately after login, but somewhat later on).
There are some konsole related issues, resulting in a delay by 1 to 6 seconds from any pressed key. Interestingly, xterm doesn't suffer from this behaviour.
Are these effects known already? Any ideas/mitigations/workarounds?
The "unboxing" experience is very nice already. The performance is great.
Filing these issues as bugs starts with the question, what package they relate to?
Are you guys still using a patched libssh package?
Thanks in advance.
Cheers, Pete
It probably boils down to KDE requiring Mord OpenGL support than x2go can offer. But you can try to use the current NX beta and see if the situation improves for you. See https://wiki.x2go.org/doku.php/doc:howto:nx-libs-betatesting
Does it work fod you with the mate desktop?
Uli
Am 24.10.2017 19:09 schrieb "Hans-Peter Jansen" <hpj@urpla.net>:
Hello everybody,
after noticing this wonderful project, I started with a new openSUSE Build Service repo for x2go today:
https://build.opensuse.org/project/show/home:frispete:RemoteDesktop:x2go
since RemoteDesktop:x2go is somewhat orphaned and suffers from serious bit rot in some auxiliary packages. While at it, I've updated x2goclient to 4.1.0.1 already, and plan to update the other packages, that saw new releases, soon.
Being a heavy remote user of all kinds (ssh, vnc, rdp), this project is a perfect fit. I never got NX to cooperate nicely, but always thought, that the basic concepts are sound.
Anyway, I was able to install the x2goserver and x2goplasmabindings packages on a remote system (Leap 42.3 Virtualbox VM on a 42.3 host), and successfully connect to it with the x2goclient package, reaching out a nice and fresh KDE desktop.
So far for the good news.
After login, powerdevil crashes with signal 6 (related to non existing DimDisplay action). This in turn results in a drkonqi crash (sig 11).
Probably related to these, the X2Go PLasma Bindings failed to remove the shut down and reboot actions in the K menu.
Immediately logging out results in a ksmserver crash, that effectively prevents a successful log out, hence the session can only be terminated the hard way from the X2Go client UI.
Parallel ssh sessions to the server appear locked at some point (not immediately after login, but somewhat later on).
There are some konsole related issues, resulting in a delay by 1 to 6 seconds from any pressed key. Interestingly, xterm doesn't suffer from this behaviour.
Are these effects known already? Any ideas/mitigations/workarounds?
The "unboxing" experience is very nice already. The performance is great.
Filing these issues as bugs starts with the question, what package they relate to?
Are you guys still using a patched libssh package?
Thanks in advance.
Cheers,
Pete
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
This made me wonder about the state of X2go with compositing desktops?I'm still using Mate so not an issue for me (unless I enable compositing in marco), but would be for Hans-Peter.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Tue, 24 Oct 2017, Hans-Peter Jansen wrote:
Date: Tue, 24 Oct 2017 19:03:21 +0200 From: Hans-Peter Jansen <hpj@urpla.net> To: x2go-user@lists.x2go.org Subject: [X2Go-User] New guy, new OBS repo and some issues
Hello everybody,
after noticing this wonderful project, I started with a new openSUSE Build Service repo for x2go today:
https://build.opensuse.org/project/show/home:frispete:RemoteDesktop:x2go
since RemoteDesktop:x2go is somewhat orphaned and suffers from serious bit rot in some auxiliary packages. While at it, I've updated x2goclient to 4.1.0.1 already, and plan to update the other packages, that saw new releases, soon.
Being a heavy remote user of all kinds (ssh, vnc, rdp), this project is a perfect fit. I never got NX to cooperate nicely, but always thought, that the basic concepts are sound.
Anyway, I was able to install the x2goserver and x2goplasmabindings packages on a remote system (Leap 42.3 Virtualbox VM on a 42.3 host), and successfully connect to it with the x2goclient package, reaching out a nice and fresh KDE desktop.
So far for the good news.
After login, powerdevil crashes with signal 6 (related to non existing DimDisplay action). This in turn results in a drkonqi crash (sig 11). Probably related to these, the X2Go PLasma Bindings failed to remove the shut down and reboot actions in the K menu.
Immediately logging out results in a ksmserver crash, that effectively prevents a successful log out, hence the session can only be terminated the hard way from the X2Go client UI.
Parallel ssh sessions to the server appear locked at some point (not immediately after login, but somewhat later on).
There are some konsole related issues, resulting in a delay by 1 to 6 seconds from any pressed key. Interestingly, xterm doesn't suffer from this behaviour.
Are these effects known already? Any ideas/mitigations/workarounds?
The "unboxing" experience is very nice already. The performance is great.
Filing these issues as bugs starts with the question, what package they relate to?
Are you guys still using a patched libssh package?
Thanks in advance.
Cheers, Pete
On Wed, Oct 25, 2017 at 2:20 AM, Robert Dinse <nanook@eskimo.com> wrote:
This made me wonder about the state of X2go with compositing desktops?I'm still using Mate so not an issue for me (unless I enable compositing in marco), but would be for Hans-Peter.
That's why I was asking for Mate. X2goagent/nxagent does not offer the COMPOSITE extension.
Uli
-
Hans-Peter Jansen -
Robert Dinse -
Ulrich Sibiller -
Ulrich Sibiller