Triple head freeze-up issue

Forums / NoMachine for Linux / Triple head freeze-up issue

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #13699
    T3tra
    Participant

    Greetings Devs and Users,

    [system info at bottom of post]

    I have a triple head setup at home, and another at work. Connecting from home to work I can expand my work desktop across all 3 local monitors, and the performance is amazing – thanks for that!

    The issue I’m seeing is that if I collapse the fullscreen over multiple monitors, do things locally, then expand it again, it will not fully expand over the local frame (sides fit, but top and bottom are no longer masked, or ‘letterboxed’) into my taller monitors at home. But that’s not the real problem. The problem is I cannot do anything with the expanded session now – it’s locked. ctl-alt-0 is also inop, and the client must be killed outside of !NM from a shell.

    It’s completely reproducible – happens every time, and I’m pretty sure you don’t want it to behave that way 🙂 I know I dont! triple head is probably not tested as rigorously as dual monitor setups. I can do whatever testing you need to help get a handle on this.

    Thanks!

    Christopher

     

    #====================================================================

    !NM: v5.1.62 both places

    #====================================================================
    Monitors
    work: 3x1920x1080
    home 3x1920x1200

    #====================================================================
    $ uname -a
    Linux monolith 4.7.0-1-amd64 #1 SMP Debian 4.7.8-1 (2016-10-19) x86_64 GNU/Linux

    #====================================================================
    $ glxinfo -B
    name of display: :0.0
    display: :0 screen: 0
    direct rendering: Yes
    Extended renderer info (GLX_MESA_query_renderer):
    Vendor: X.Org (0x1002)
    Device: AMD HAWAII (DRM 2.45.0 / 4.7.0-1-amd64, LLVM 3.9.1) (0x67b1)
    Version: 13.0.4
    Accelerated: yes
    Video memory: 8192MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.3
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.1
    OpenGL vendor string: X.Org
    OpenGL renderer string: Gallium 0.4 on AMD HAWAII (DRM 2.45.0 / 4.7.0-1-amd64, LLVM 3.9.1)
    OpenGL core profile version string: 4.3 (Core Profile) Mesa 13.0.4
    OpenGL core profile shading language version string: 4.30
    OpenGL core profile context flags: (none)
    OpenGL core profile profile mask: core profile

    OpenGL version string: 3.0 Mesa 13.0.4
    OpenGL shading language version string: 1.30
    OpenGL context flags: (none)

    OpenGL ES profile version string: OpenGL ES 3.1 Mesa 13.0.4
    OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10

    #————————————————————————————————-
    $ X -version

    X.Org X Server 1.18.4
    Release Date: 2016-07-19
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
    Current Operating System: Linux monolith 4.7.0-1-amd64 #1 SMP Debian 4.7.8-1 (2016-10-19) x86_64
    Kernel command line: BOOT_IMAGE=/vmlinuz-4.7.0-1-amd64 root=/dev/mapper/system_vg-os_lv ro radeon.dpm=0
    Build Date: 06 September 2016 01:32:44PM
    xorg-server 2:1.18.4-2
    Current version of pixman: 0.34.0

    #13715
    Tor
    Contributor

    Hi Christopher, thank you for the report. We agree, it’s not the right behaviour! 🙂 Could you kindly compress the most recent directory $HOME/.nx/R-* while the client is frozen, and send it to forum[at]nomachine[dot]com. We didn’t reproduce the issue in our labs, so your help would be great to speed up the investigation.

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

Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.