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
[email protected]
https://lists.x2go.org/listinfo/x2go-user
