Forum Replies Created
-
Posts
-
Sorry for really long delay. I missed your reply.
Surely the difference will be more noticeable in case of multimedia.
Finally we managed to reproduce in our labs.
A fix will be released very soon with the next update.
Thanks for all the reports!
Can 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.
Does 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.
About 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.
As 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?
Error 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.
Logging 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.
Work 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.
Please send the whole ‘/Library/Application Support/NoMachine/var/log/’. That will be useful also for the first problem.
Are you attaching to the physical display of your home machine? Or are you creating a new virtual desktop?
Please gather client and server side logs as explained here: https://www.nomachine.com/AR07K00677.
Send to: forum[at]nomachine[dot]com.
Sorry for the delay, it looks like I missed your post.
There is no option for decreasing memory usage and those are expected values. Consider anyway that the nxnode.bin process in the new version includes the functionalities of both nxnode and nxagent processes of the old version.
Can you please provide more info:
– What is the nx process with high CPU usage?
– Does the CPU usage remain high when there are no visible updates in the session?
– NoMachine product and version on local and remote machine (free version, Workstation, etc).
– Whether the problem arises connecting to a physical or a virtual display.Please try:
ln -s /usr/lib/i386-linux-gnu/libavcodec.so.54 /usr/lib/i386-linux-gnu/libavcodec.so
ln -s /usr/lib/i386-linux-gnu/libavutil.so.51 /usr/lib/i386-linux-gnu/libavutil.so