Fedora 40 + NoMachine not working

[CRCinAU]

Thanks for this info.

I do note though that the session does seem to go between X11 and Wayland depending on the launcher. See the attached screenshots.

The only thing that doesn’t seem to work properly is sizing the desktop in Wayland.

Attachments:

1. 

   Screenshot_20240723_000838.png
   

2. 

   Screenshot_20240723_001045.png
   

[Britgirl]

We don’t know how much of the Wayland protocol is used by KDE internally or in the communication with the other apps, but we do know that the communication with our agent uses the X11 protocol 😉 The resize issue, to be honest, doesn’t look like a NoMachine bug.

[trnqullea]

I’m seeing the same…

Tested with two new KVM guests, both running a “vanilla” Fedora 40 KDE spin (that is Wayland only) I get:

   The session negotiation failed
Error: Cannot create a new display, please contact your system administrator

This is NoMachine 8.13.1. In the connection logs I see, in “session”

   4474 4474 2024-09-07 09:27:14 597.341 ClientSession: Failing reason is ‘The session negotiation failed.
Error: Cannot create a new display, please contact your system administrator’.

and:

  libEGL warning: egl: failed to create dri2 screen

and then in “connection”:

  NX> 105 Listsession –status=”disconnected\054connected” –type=”all” –shadowable=”yes”
NX> 149 Confirmation required for creating new frame buffer on server
Startxserver –option=”yes”
NX> 500 ERROR: Cannot create a new display, please contact your system administrator.

I see there’s a bug https://kb.nomachine.com/TR05V11141, flagged due to be solved in 8.x. I wonder if there’s any hope of progress here as Fedora releases that include X with soon be dropping out of support.

[Britgirl]

Hi, can you both update to the latest version, 8.14 and tell us if you are still encountering issues? We fixed the following TR https://kb.nomachine.com/TR03U10784 related to the the fallback capture method which fails. We would like to eliminate the possibility that this was affecting your NoMachine set-up. If you are still having issues after the update, new logs would be useful. You can extract them from the server machine using the instructions here: https://kb.nomachine.com/DT07S00243
Attach them here or send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

[trnqullea]

… can you both update to the latest version, 8.14 and tell us if you are still encountering issues?

That’s done, to 8.14.2 on both. Also a “dnf update”…

… If you are still having issues after the update

Yes, still there, although maybe I’m testing more options now.

If the server is at the logon prompt (SDDM screen), the client behaviour is the same:

I get the “Error: Cannot create a new display”. Back on Fedora 38, which included “X”, I was able to connect and log on

If I log on the server with the test user (without setting up debug logging)  and connect, It works:

I get “Your desktop is currently viewed” and and “User test from xxx.xxx.xxx.xxx connected” on the server screen. There’s a pause and a white screen on the client but it does connect

It’s possible that this needed the “dnf update” or things that needed to be cached were cached… alas I cannot tell

[Britgirl]

Trnqullea, can you enable debug, reproduce the problem and submit the logs so we can check? If needed, I can spin off your thread if it’s a different problem.

[CRCinAU]

Sorry – got a bit of head fog with the flu at the moment – but are you saying that this should work with Wayland now?

For the record, my setup consists of doing:

# systemctl set-default multi-user.target

Then in server.cfg I change:

DisablePersistentSession “all”
EnableNetworkBroadcast 0
CreateDisplay 1
DisplayOwner “myusername”

In node.cfg I change:

#DefaultDesktopCommand “dbus-launch –exit-with-session /usr/bin/startplasma-wayland”
DefaultDesktopCommand “dbus-launch –exit-with-session /usr/bin/startplasma-x11”
AvailableSessionTypes unix-remote,unix-console,unix-default,unix-application,physical-desktop,shadow,unix-xsession-default,unix-xdm,unix-kde
AudioInterface pipewire
CommandStartPipeWire “/usr/bin/pipewire -c”

For X11 or Wayland – last testing, Wayland worked, but didn’t allow me to change resolution dynamically.

I don’t think I do anything else to make things work.

[Britgirl]

CRCinAU,

sorry for the confusion. I realise now that you fixed the issue for which you opened this topic by changing some configuration keys (https://forum.nomachine.com/topic/fedora-40-nomachine-not-working#post-48741). My bad.

Just to clarify what we had written about another issue you mentioned, related to resolution/resize, there is no change. This is what we wrote last time about Wayland after looking at your logs, “NoMachine handles the resize correctly but then the desktop fails to adapt. You mentioned that you have this problem with startplasma-wayland, but not with startplasma-x11. Even when running the Wayland command, the virtual desktop will fall back to using X11 in any case, because that is the only protocol that NoMachine virtual desktops support at the moment. So the recommended command is startplasma-x11.”

[Author]

Posts