Workstation: Virtual desktop session crashes with multi-monitor client

Forum / NoMachine Terminal Server Products / Workstation: Virtual desktop session crashes with multi-monitor client

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #13247
    tobi
    Participant

    I recently upgraded my Ubuntu 16.04.1 LTS (unity) server’s nxnode from 5.1.42 to 5.1.62 and now have the following problem:

    On my Windows 10 client (Enterprise client 5.1.62), I have 3 monitors, each with a resolution of 2560×1440. When I arrange these 3 monitors diagonally, I can no longer connect to or create new virtual desktops. The connection is terminated with “input/output error” on the client, and the server logs a kernel error saying that nxnode.bin had a segfault in libc-2.23.so

    This does not happen when I arrange the three monitors horizontally, vertically, or in an “L”-shape.

    On another client (Windows 10, Enterprise client 5.1.62) that has 6 monitors with 2560×1440 resolution each, I have the same issue with a 2-row, 3-column setup of these monitors (worked with this client in 5.1.42). This client does work fine with only 3 monitors enabled in a 1-row, 3-column setup, but adding the other 3 monitors in a second row produces the same error.

     

    #13254
    fra81
    Moderator

    Hi tobi,

    please find the core file on your server (usually /home/<user>/core), and get a backtrace from it following these instructions: https://www.nomachine.com/AR09L00810. Attach it here or send to forum[at]nomachine[dot]com.

    #13327
    fra81
    Moderator

    Thank you for the logs.

    We reproduced the same problem with very high resolutions, and it is now tracked here:

    https://www.nomachine.com/TR12N07455

    Note that you should be able to create a virtual desktop having a lower resolution regardless the current layout of your monitors, by just not maximizing the NoMachine Player window. In fact the virtual desktop’s screen should have the same size of the player’s window. I recommend to create a new connection though, since the resolution could have been saved in the configuration file of the existing connection.

Viewing 3 posts - 1 through 3 (of 3 total)

This topic was marked as solved, you can't post.