Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open nx et al. #194

Open
karalets opened this issue Dec 5, 2014 · 4 comments
Open

Open nx et al. #194

karalets opened this issue Dec 5, 2014 · 4 comments
Assignees

Comments

@karalets
Copy link

karalets commented Dec 5, 2014

Hi,

Paul, I wanted to relate this post to the issue of openNx and the potential replacements we talked about in person. It would be great to look at the issue with the keyboard existing in OpenNx and see what causes this, how we can fix it and if we should consider changing client altogether instead of debugging.

Best,

Theo

@tatarsky
Copy link
Contributor

tatarsky commented Dec 8, 2014

Noting that we should do some tests of x2go. The heir apparent to NX opensource. I will see if they can co-exist.

http://wiki.x2go.org/doku.php

@tatarsky
Copy link
Contributor

I will look at this shortly.

@tatarsky tatarsky self-assigned this Dec 11, 2014
@tatarsky
Copy link
Contributor

For the xmodmap path (aka fixing the keybindings from the mac) does the following item resolve it? I still have no Mac to test from but will try to arrange one.

http://superuser.com/questions/147039/getting-freenx-client-to-work-on-mac-os-again

@tatarsky
Copy link
Contributor

I am looking also at what is involved in getting x2go working in a way that does not conflict with the current nxserver.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants