trnqullea

[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

[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.

[Author]

Posts