Forum Replies Created
-
AuthorPosts
-
fra81ModeratorHello.
As for the first issue, we managed to reproduce it in our labs and we’re working on a fix.
To investigate further the second problem we would need log files. You can gather them as explained in https://www.nomachine.com/AR07K00677 and send them to forum[at]nomachine[dot]com.
About the third issue, that setting should be saved in a cookie. Do you have cookies enabled on your browser?
fra81ModeratorHi mo-seph,
this is strange. Since your feedback, we started another run of tests, but all the reports we got so far seem to confirm the problem is fixed.
For further investigations, would you mind sending server side logs as explained here: https://www.nomachine.com/AR07K00677.
You can send them to forum[at]nomachine[dot]com.
fra81ModeratorPlease collect log files as explained here: https://www.nomachine.com/AR07K00677.
You can send them to forum[at]nomachine[dot]com.
fra81ModeratorCurrently NoMachine supports GPU-accelerated H.264 decoding only on Windows and Mac OS X systems.
fra81ModeratorHi,
we weren’t able to reproduce this issue in our labs so far. Can you please send us the “.xsession-error” file located in the home directory of the user owning the desktop?
Also a full set of logs could be useful. You can gather them following the guidelines in this article: https://www.nomachine.com/AR07K00677.
You can send files to forum[at]nomachine[dot]com.
Can you please also explain what you mean exactly with “remote pc freeze, but only Gnome Shell”. Other applications continue to work?
fra81ModeratorHello,
timeout is 15 minutes and there is no setting for changing it.
Regards.
fra81ModeratorSorry for really long delay. I missed your reply.
Surely the difference will be more noticeable in case of multimedia.
fra81ModeratorFinally we managed to reproduce in our labs.
A fix will be released very soon with the next update.
Thanks for all the reports!
fra81ModeratorCan the following TR apply to your case?
https://www.nomachine.com/TR04L04396
If not, please provide the following info.
With frozen you mean that you see the remote screen when connecting but it won’t update? Or that it will update, for example when the clock changes, but input events are not working?
What are your Linux and desktop environment versions?
Logs can be useful. You can gather them as explained in https://www.nomachine.com/AR07K00677 and send to forum[at]nomachine[dot]com.
fra81ModeratorDoes it occur even if there is no activity in the session (like, for example, a video running or animations)?
What is your Mac OS X version and on what hardware?
One option you could try is switching to the MJPEG display encoding, in Server preferences, Performance tab, accessible through the tray icon.
fra81ModeratorAbout point 1, unfortunately that is not configurable, but you can use a alternative way to enable fullscreen mode, like pressing F11 or using the browser’s menu. In that case you can continue using the Escape key in the session.
fra81ModeratorAs for the CPU problem, unfortunately we are still unable to reproduce exactly the same on several machine in our labs, but we are checking a possible issue related to the audio system. Can you try to disable audio from the player GUI and check if it makes any difference?
@tosigus: What do you mean with “When non NoMachine Tray Icon”? Have you changed the “Hide the NoMachine icon in system tray” option?The tray icon should be always visible while somebody connects or disconnects. Does the CPU have spikes while the icon is visible at connection and at disconnection?
fra81ModeratorError Message:
/usr/NX/bin/nxnode.bin
Crash
nxnode.bin crashed with SIGSEGV in nxagentMirrorUpdateCursor()This problem has been fixed in the last release: 4.2.23.
fra81ModeratorLogging can be enabled for the server by enabling this key in the /usr/NX/etc/node.cfg and server.cfg files:
SessionLogLevel 7
However problems with network outage are more likely to be identified by looking in the .nx directories in the user’s home on client and server side (more info in https://www.nomachine.com/AR07K00677 on how retrieving logs). You may notice logs similar to “WARNING! No data received […] since […] ” or any other actual error. Log level cannot be changed there, but default should be enough.
fra81ModeratorWork is in progress, but it is a major change and it will require quite a long period of testing, given the number of different Linux platforms.
So I can’t say exactly. Should be in terms of weeks.
-
AuthorPosts
