You are not logged in.
I'm trying to transition from VNC to x2go for remote access. One item I've been having trouble with is Docky.
When I connect to my bl helium instance with VNC, the Docky icons bounce and everything works fine.
But when I connect to my instance with x2go, I get a message saying I need compositing turned on for Docky.
My hunch is that connecting with x2go somehow prevents Compton from compositing. But I can't seem to get further in my research to resolve the issue.
Could anyone point me in the right direction? thank you!
Offline
I'm trying to transition from VNC to x2go for remote access. One item I've been having trouble with is Docky.
When I connect to my bl helium instance with VNC, the Docky icons bounce and everything works fine.
But when I connect to my instance with x2go, I get a message saying I need compositing turned on for Docky.
My hunch is that connecting with x2go somehow prevents Compton from compositing. But I can't seem to get further in my research to resolve the issue.
Could anyone point me in the right direction? thank you!
From reading around, it could be that the Xserver x2go is starting (its own implementation?) is incompatible with certain modern Xorg extensions, including Xcomposite which compton requires to work correctly: Apparently, it's been forked from an ancient Xserver 6.9 from 2005! Here's a list of possibly compatible desktop environments / window managers. As they claim that Kwin may work, if you need your windows shadows remotely, you could launch Kwin instead of openbox (without KDE).
Alternatively, make sure that compton is not using the xrandr backend and try again, maybe that works, but I'd surmise it doesn't.
Offline
According to (see this, the very same link nobody posted above)
Always Compatible, but Trivial Workarounds Required
IceWM
In X2Go Client, you must specify the Session Type as: Custom Desktop: icewm-session
OpenBoxIn X2Go Client, You must specify the Session Type as: Custom Desktop: openbox-session
(my bold) it should work with the OpenBox.
Postpone all your duties; if you die, you won't have to do them ..
Offline
^yes, but both are windowmanagers that don't provide compisiting.
as nobody said:
"if you need your windows shadows remotely, you could launch Kwin instead of openbox (without KDE)."
Offline
^Quite, I might be wrong. TBH I admit that I have never tried x2go, and OP haven't said what he/she has or hasn't tried so far ... OTOH, there is explicitly mentioned compatibility with the OpenBox.
...
I have had the best intention(s)
Postpone all your duties; if you die, you won't have to do them ..
Offline
OTOH, there is explicitly mentioned compatibility with the OpenBox.
...
I have had the best intention(s)
oh, you are absolutely correct.
but openbox does not provide compositing, and that is op's sole concern afaics.
because docky (apparently some sort of dock) balks at not hasving a compositor.
Offline
Many thanks to everyone who responded - I installed kde-window-manager and was able to connect using x2go. Unfortunately docky still complained of not having a compositor. And boy, was the KDE interface very slow.
I guess I am wondering if it is possible to connect with x2go and use the standard bl openbox setup that I'm used to with VNC, but with the performance enhancements of newer generation tools like x2go/nx/*rdp and the convenience of straight SSH rather than taking the extra step of tunneling VNC traffic over SSH. Pardon my ignorance regarding the pieces involved in remote GUI access.
As has been pointed out, the x2go documentation says it is compatible with openbox. But it also warns of incompatibility when "The desktop environment requires the X11 extension “Xcomposite”, which nxagent 3.5.0.x and X.org 6.9 do not support."
I understand that bl uses Xcomposite, so maybe this is the end of the road?
For background, my goal is to create remote VMs for my team so that each member can have their own bl desktop. So far we have a few instances that are shared with VNC. But as the team grows, I'd like a separate desktop instance for each user, like how tigervnc or x2go do. I tried NoMachine already, and x2go and tigervnc are up next. The docky app offers my users a familiar looking set of standard tools (our endpoints are mostly macOS).
Offline
As has been pointed out, the x2go documentation says it is compatible with openbox. But it also warns of incompatibility when "The desktop environment requires the X11 extension “Xcomposite”, which nxagent 3.5.0.x and X.org 6.9 do not support."
I understand that bl uses Xcomposite, so maybe this is the end of the road?
i don't understand the drama.
docky isn't even used by BL by default, you must have installed it.
just use another dock, if you must.
honestly, i think docky shouldn't plain refuse to start up if there's no compositor, so judging from your description it's just badly coded(*).
and as was explained already in this thread, BL uses compton for compositing, but you don't really need compositing at all, just disable it (desktop right-click menu => Preferences => compositor).
(*) it's a mono app for $DEITY's sake.
try wbar instead.
Last edited by ohnonot (2018-07-02 08:00:08)
Offline
x2go has worked great for me on multiple machines (BL standard install - no docks). Have used on multiple computers going back to #! days. Occasionally, tint2 will die on the pc being remoted (minor issue since it can easily be restarted). It is my preferred method for secure, remote access of pcs across the internet. Orginally I tried to use x2go with Unity and it was too slow to be usable (which was a major factor in my switching to an openbox distro)
Offline