Plasma 6 wayland connection issue – 104 error

[jjgalvez]

Afternoon,

when I try to connect between two computers both running Arch and Wayland with plasma 6 I get a white screen which then becomes a 104 connection reset by peer error. This looks like the same error in TR07U10921.  I’m attaching the logs hopefully they help. Unfortunately I can’t drop back to xorg as it causes issues on my machine coming out of sleep.

Attachments:

1. p2-2024-03-17-13.04.33.tar.gz

[jjgalvez]

happy to provide any additional information / logs that might be useful

[Britgirl]

Hi, can you submit server side logs so that we can check if it is indeed that TR? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243

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

[jjgalvez]

Thank you I will submit the logs later today

[jjgalvez]

server and client logs sent. Hope they are helpful

[Britgirl]

The logs show that the issue is actually a different one. This https://www.nomachine.com/TR03U10784. Support for 10 bits channels is planned, most likely in one of the minor releases of the v9 tree.

[jjgalvez]

interesting, are there any workarounds or do i need to set the color depth on my desktop to something less than fullcolor?

[Britgirl]

Can you tell us what configuration you have in order to get 30 bit per pixel? We can verify it first in our labs.

[jjgalvez]

Afternoon Britgirl, thanks for the quick reply,

I’m running Arch (EndeavourOS) with KDE Plasma 6 Wayland  (including SDDM on Wayland). I’m attaching a screen shot of the system info for reference.

Nomachine was installed by the AUR

Attachments:

1. 

   Screenshot_20240329_195058.png
   

[Britgirl]

We were more interested in your specific display settings. What’s the monitor model btw?

[jjgalvez]

Monitor MSI Optix Mag321CQR

resolution: 2560×1440 @ 60 Hz
scale: 120%

RGB Range full color

 

[fra81]

@jjgalvez,

please show the content of the ‘/usr/libexec/plasma-dbus-run-session-if-needed’ script. Note that this file could be in a different path, so you can use the ‘locate’ command to find it.

Also show the output of:

ls -l /etc/xdg/plasma-workspace/env

[jjgalvez]

apologies for not replying sooner. On my machine I don’t have a plasma-workspace/env folder other than ~/.config/plasma-workspace/env which is empty

[fra81]

Hi,

did you also check the content of the /usr/libexec/plasma-dbus-run-session-if-needed script?

Besides, you can try the following steps:

1. Create the /etc/xdg/plasma-workspace/env directory

2. Place a nx-surceenv.sh script in it containing only this line: export LD_PRELOAD=/usr/NX/lib/libnxegl.so

3. Reboot

4. Make sure the libnxegl library is preloaded (the output of the sudo netstat -anlp | grep egl command shouldn’t be empty)

 

Let us know the results 😉

[jjgalvez]

the content of /usr/lib/plasma-dbus-run-session-if-needed is:

#!/bin/sh

# Usage: plasma-dbus-run-session-if-needed PROGRAM [ARGUMENTS]

# If the session bus is not available it is spawned and wrapper round our program

# Otherwise we spawn our program directly

drs=

if [ -z “${DBUS_SESSION_BUS_ADDRESS}” ]

then

drs=dbus-run-session

fi

exec /usr/NX/scripts/env/nxpreload.sh  ${drs} “$@”

I also added the nx-surceenv.sh in /etc/xdg/plasma-workspace/env however when I run sudo netstat -anlp | grep egl the output is still empty even after a reboot. I did check that LD_PRELOAD=/usr/NX/lib/libnxegl.so was exported as it’s listed with printenv.

When I try to connect I am still getting a 104 error.

[Author]

Posts