fra81

Forum Replies Created

Viewing 15 posts - 601 through 615 (of 692 total)
  • Author
    Posts
  • in reply to: Blank screen after login on Xubuntu 14.04 #5677
    fra81
    Moderator

    Hi heartbreak,

    your problem seems similar to the one described in https://www.nomachine.com/TR10L04587, though we could not reproduce it in our labs.

    A complete set of logs could be useful. You can gather them by following the instructions in https://www.nomachine.com/AR07K00677. If you prefer, you can send logs to forum[at]nomachine[dot]com.

    in reply to: Best graphics card for NoMachine on linux #5674
    fra81
    Moderator

    Hi Steve,

    in the current version NoMachine for linux is not taking advantage of the graphics card (though work is in progress on this matter).

    Could you explain further why you say that NoMachine doesn’t seem to like your graphics card?

    in reply to: NoMachine server raising CPU usage on Linux Mint 17 #5546
    fra81
    Moderator

    Hi Bart,

    thanks for your answers. As for your old problems with Ubuntu, as far as we know all problems related to the synchronization of toggle keys should be fixed in the last version (BTW, I see you are using a quite old version on client side, various bugs have been fixed since then).

    Regarding the issue with NumLock, here are a couple more links that confirm this has to be considered a bug in Mate:

    https://bugs.launchpad.net/ubuntu-mate/+bug/1364111

    https://github.com/mate-desktop/mate-settings-daemon/issues/57

    in reply to: No image or desktop changes on client screen #5545
    fra81
    Moderator

    Hi Justin.

    1) When interacting with the remote desktop, I get a lot of OS ding sounds (like each time an app is started, new window is created) – known issue, way to resolve?

    This has been reproduced in our labs and it is currently being investigated.

    2) When you logout of the remote desktop (logout of Windows), the image does not update to the login screen, you are stuck at the image just before logout.  Is this by design?  Seems like a bug to me.

    This should be fixed with the next software update.

    3) Do the graphics options in preferences apply only for serving?   In other words, if I make a change on my client !M, will that affect how the server streams the graphics?  (The UI is not clear on this matter.)

    Those settings only apply when the machine where you are doing the changes on acts as a server. If you change preferences (from the NoMachine tray icon) on the client machine, those changes won’t be exported to the server.
    Anyway, there is a different set of settings that affects the way the server streams the display. Those are the ones that can be tweaked from the NoMachine Player toolbar during the session.

    4) In Performance preferences, there are options for framerate and display encoding, and both are unchecked by default.  If these are unchecked (i.e., no specification made), what values are they using?

    Default value for framerate is 25 fps. The encoding method depends also on the decoding capabilities of the client. If the client supports H.264 decoding (by means of the hardware or by codec libraries), then H.264 will be chosen. Otherwise VP8 encoding is always used. MJPEG won’t be used unless it is explicitly requested.

    in reply to: No image or desktop changes on client screen #5530
    fra81
    Moderator

    Hi Justin,

    the logs seems to point to a problem related to the video drivers. Can you specify the version of your graphics card so we can try to replicate this issue in our labs?

    Please try to disable the hardware acceleration from the NoMachine tray icon on the server machine:

    Show the server status -> Server preferences -> Performance

    then uncheck “Use acceleration for display processing”.

    in reply to: NoMachine server raising CPU usage on Linux Mint 17 #5487
    fra81
    Moderator

    Hi Bart,

    it doesn’t appear to be a NoMachine problem since it was reproduced without NoMachine being involved, though it seems not clear what triggers it. Are you attaching to the physical desktop of the Mint machine? Or are you running a virtual desktop session? In the latter case, with a different user than the one logged in physically? And was the NumLock enabled/disabled on the client and the server hosts?

    in reply to: Ubuntu screen blank #5486
    fra81
    Moderator

    Hi jackV,

    indeed this looks like a problem with the video drivers, but I’m not sure I understand what you mean with “visualization”. Is Ubuntu running inside a virtual machine on the Windows 7 host? And in this case visualization has to be intended as “video acceleration” to be enabled in the virtual machine? What is the version of Ubuntu?

    in reply to: Connection ok, video not updating #5465
    fra81
    Moderator

    Hi georgesil,
    this looks like a configuration problem with the proxy, more than with the software. Maybe there is a firewall that starts dropping packets after a while. Are these public proxies that we can try ourselves? If you want to provide further info privately, you can send a email to forum[at]nomachine[dot]com.

    in reply to: NoMachine server raising CPU usage on Linux Mint 17 #5431
    fra81
    Moderator

    Hi Bart,

    this looks very similar to the problem reported here: http://forums.mate-desktop.org/viewtopic.php?f=5&t=2094.

    Can you try the suggested workaround?

    in reply to: Blank screen from Windows to Red Hat Linux #5406
    fra81
    Moderator

    Hi elan,

    unfortunately the logs you sent are not complete and not useful for the investigation. Please send a complete set of logs as explained in details here: https://www.nomachine.com/AR07K00677. If you wish, you can send them to forum[at]nomachine[dot]com by referencing this topic in the subject.

    But before that, can you tell something more? I see you are connecting to a Xvfb display. Is this a headless machine and you followed instructions in https://www.nomachine.com/AR10K00710? Have you launched a desktop environment (or any X application) inside the Xvfb display?

    in reply to: Session unresponsive after long absence #5295
    fra81
    Moderator

    Hi iceback,

    I assume the session was left in disconnected state, and when you reconnected after 2 weeks you found it unresponsive?

    Do you still have logs from that session? More info on how to gather logs here: https://www.nomachine.com/AR07K00677. They can be sent to forum[at]nomachine[dot]com.

    Finally, if the session is still running, please do a test: try to reconnect that session by double-clicking on the icon representing the session but, while doing so, keep Ctrl+Alt pressed. This will make the session is reconnected in “shadowing” mode. Let’s see if user input works with the different protocol.

    in reply to: Error 107 from Win 8.1 to MAC OS X #5243
    fra81
    Moderator

    Hi claus,

    by default NoMachine listens on port 4000. Can you tell us the output of the ‘netstat -an | grep LISTEN’ command on the server?

    Also server side logs could be useful. You can find instructions on how to gather logs in https://www.nomachine.com/AR07K00677. You can send them to forum[at]nomachine[dot]com.

    in reply to: Black screen when connecting to Red Hat #5162
    fra81
    Moderator

    Hi,

    from the logs it looks like the only running instance of Xserver is a Xvfb (virtual framebuffer). Can you confirm?

    Is that a headless machine and you started Xvfb maybe for the purpose of allowing connections through NoMachine?

    Are you sure a desktop environment is actually running inside the Xvfb?

    in reply to: Black screen when connecting to Red Hat #5080
    fra81
    Moderator

    Hi,

    unfortunately the archive seems to be corrupted. Can you please send the logs again to forum[at]nomachine[dot]com?

    in reply to: Logs filling up the Mac Console #5079
    fra81
    Moderator

    Hi BitPerfectRichard,

    we finally managed to reproduce the problem with Console Log and the fix will be included in the upcoming software update.

    The issue was related to the “Resize remote screen” feature and disabling it would have worked as a workaround. The reason why you don’t reproduce it with the just released Yosemite is that remote resize is not yet fully supported there and we are working on it. This should also explain why you don’t get the expected resolution.

Viewing 15 posts - 601 through 615 (of 692 total)