brugi

Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • in reply to: NX won’t work with recent KDE 5.17 #24164
    brugi
    Participant

    I can confirm that patch that you sent by email works for me. Thank you very much!

     

    in reply to: NX won’t work with recent KDE 5.17 #24112
    brugi
    Participant

    I’m using Arch Linux, x64, NoMachine version 6.8.1.

    Thanks! Fingers crossed. 🙂

     

    in reply to: NX won’t work with recent KDE 5.17 #24091
    brugi
    Participant

    OK, sorry for wrong assumption, I tried with this few days ago and it didn’t work. Now I double-checked for typos or something, but no luck. So I envy you. 🙁

    I’m on Arch Linux too and still get “Cannot detect displays” and this:

    ~ sudo /etc/NX/nxserver –restart
    NX> 162 Disabled service: nxserver.
    NX> 162 Service: nxnode already disabled.
    NX> 162 Disabled service: nxd.
    NX> 111 New connections to NoMachine server are enabled.
    NX> 161 Enabled service: nxserver.
    NX> 162 WARNING: Cannot find X servers running on this machine.
    NX> 162 WARNING: A new virtual display will be created on demand.
    NX> 161 Enabled service: nxd.

    Service nxnode remains disabled.

    ~ sudo /etc/NX/nxserver –status
    NX> 111 New connections to NoMachine server are enabled.
    NX> 162 Enabled service: nxserver.
    NX> 162 Disabled service: nxnode.
    NX> 162 Enabled service: nxd.

    in reply to: NX won’t work with recent KDE 5.17 #24082
    brugi
    Participant

    I’m having the same problem (another thread here) and, as jnko said, this doesn’t help.

    It’s because NX does not need to start Plasma, it’s already running and we are trying to connect to physical desktop. From some reason X server with KDE 5.17 is not detected by NX.

     

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