Forum / NoMachine for Linux / Plasma 6 wayland connection issue – 104 error
- This topic has 18 replies, 5 voices, and was last updated 6 months ago by jjgalvez.
-
AuthorPosts
-
March 17, 2024 at 18:46 #47459jjgalvezParticipant
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:
March 20, 2024 at 23:00 #47479jjgalvezParticipanthappy to provide any additional information / logs that might be useful
March 25, 2024 at 12:53 #47515BritgirlKeymasterHi, 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!
March 28, 2024 at 15:00 #47560jjgalvezParticipantThank you I will submit the logs later today
March 29, 2024 at 01:45 #47569jjgalvezParticipantserver and client logs sent. Hope they are helpful
March 29, 2024 at 16:18 #47585BritgirlKeymasterThe 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.
March 29, 2024 at 17:43 #47587jjgalvezParticipantinteresting, are there any workarounds or do i need to set the color depth on my desktop to something less than fullcolor?
March 29, 2024 at 19:09 #47591BritgirlKeymasterCan you tell us what configuration you have in order to get 30 bit per pixel? We can verify it first in our labs.
March 30, 2024 at 00:52 #47592jjgalvezParticipantAfternoon 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:
April 2, 2024 at 14:59 #47620BritgirlKeymasterWe were more interested in your specific display settings. What’s the monitor model btw?
April 6, 2024 at 14:08 #47658jjgalvezParticipantMonitor MSI Optix Mag321CQR
resolution: 2560×1440 @ 60 Hz
scale: 120%RGB Range full color
April 11, 2024 at 15:22 #47700fra81Moderatorplease 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
April 21, 2024 at 15:40 #47885jjgalvezParticipantapologies 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
April 26, 2024 at 12:17 #47969fra81ModeratorHi,
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
directory2. 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 😉
April 28, 2024 at 21:41 #47976jjgalvezParticipantthe 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.
-
AuthorPosts
This topic was marked as solved, you can't post.