Forum Replies Created
Can you send us the crash log directly to issues[at]nomachine.com? For some reason the upload wasn’t accepted. Thanks!
If the root user is enabled on your OS X host, then you can enter root credentials, otherwise you can use the credentials of another administrator account.
the short answer to your question is yes!
So far we’ve used the Qt library to switch to fullscreen mode, that didn’t make use of the API supported since OS X 10.7.
We’re now extending the library to use this API and have better integration with Spaces. This will also solve the issues of the fullscreen on secondary monitors occurring on OS X 10.9.
– In the next panel showing all the desktop types available on that server, check ‘Save this setting in the configuration file’.
– Choose and create the desktop you want to connect.
Your server may have only one virtual desktop type available, so the client automatically selects it and doesn’t give the possibility to save the preference. A more correct way to configure the connection consists in clicking the ‘New virtual desktop or custom session’ button. We’ve changed the article accordingly.
2. Reconnection doesn’t work automatically: nxplayer shows me the running sessions (see screenshot)
Trouble Report describing the issue is here: https://www.nomachine.com/TR12K04170
When it’s not possible to use the system tray, access to NoMachine services via the menu should be disabled in order to avoid occupying the whole screen.
There is Trouble Report here: https://www.nomachine.com/TR12K04135
A more elaborate solution using hot-keys to show the menu is already under way.
We rely on Qt to handle the window state changes, so I’d say it doesn’t support reliably this WM or there are problems in Oroborus that we’ll have to work around somehow.
What you may do is press the shortcut Ctrl-Alt-Shift-F when the client starts: this should trigger the fullscreen in Oroborus and the window state will synchronize with the button.
Ah! Forgot to say… You can change the location where the file is saved in the player preferences.
In version 4.0 a connection file is automatically created in Documents/NoMachine.
Is the session working and only that error is the problem?
That error is just a signal interrupting the select, i.e. a perfectly normal condition. That’s not an error, really. We’ll remove that log, since it is clearly misleading.
The NXS files store the connection settings, and you can find them (by default) in your Documents folder under the NoMachine directory.
If you can’t find them there (or if you want to change the default location) click on the Change player settings button in the NoMachine GUI and read the field Connections.
To create a new NXS file you just need to create a new connection: all settings will be set to their default values so we’ll know if your problem is related to a wrong key.