SUSE Slowroll – Can’t connect Error 108 / 104

Forum / NoMachine for Linux / SUSE Slowroll – Can’t connect Error 108 / 104

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #48046
    baf1
    Participant

    After a recent OS version update to SUSE Slowroll (a Tumbleweed derivative), unable to connect from Window 10 machine. Get the Error 108 message at the very last step in physical display connection process.

    Trying to connect from a SUSE Leap 15.5 Linux machine to the same Slowroll server produces the same result, but with error 104. Session log has first mention of error saying

    290.885 ProxySession/ProxySession: ERROR! Session failure in stage ‘StateWaitingProxyVersion’.

    Windows 10 client: NoMachine Enterprise Client 8.11.3

    Linux Server: NoMachine free 8.11.3_4_x86_64 with KDE desktop

    Linux Client: SUSE Leap 15.5 (KDE desktop) NoMachine 8.11.3

    #48066
    Britgirl
    Keymaster

    Are you able to send us client and server-side logs so we can check them? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. For the client-side logs (the Windows’ ones will suffice) see “Fourth step” in that document.

    Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email.

     

    #48076
    baf1
    Participant

    Server and client log files sent as requested. Thanks!

     

    #48133
    Britgirl
    Keymaster

    Hi, from the logs you sent we confirm that you are encountering two issues, both already known, initially reported on different distributions. The main capture method nor the fallback work correctly.

    Capture of the Wayland desktop by EGL doesn’t work with KDE Plasma 6
    https://kb.nomachine.com/TR05V11141

    Attaching to the physical desktop could fail on Rocky Linux 8 with Wayland
    https://kb.nomachine.com/TR03U10784

    Until the fixes are released for those Trouble Reports, you can try disabling Wayland and use X.Org instead, or try with an alternative desktop environment.

    #48137
    baf1
    Participant

    Thanks for investigating this issue. In retrospect, the determination makes sense as the connection problems started when the server was updated to a new OS release where Wayland is used as the default.  I look forward to seeing this problem resolved in a future NM release.

     

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

You must be logged in to reply to this topic.