Forum Replies Created
-
AuthorPosts
-
jjgalvezParticipant
Are there any workarounds other than using X11 because none of the other capture methods seem to work either?
jjgalvezParticipantThank you for the 8.14.2 update. After a reboot it appears (at least with initial testing) that this has fixed the issue with Plasma 6. Appreciate all the hard work.
jjgalvezParticipantJust checking in, do we know if there is any headway on this issue? Do we know if it will be able to be addressed in the next release and do we know when that may be?
Thank you for any additional information you can provide.
jjgalvezParticipantThank you and understood. I can only image the pressure your developers feel with so many distros now moving to Wayland, and some like Fedora no longer shipping X by default, given how complicated Wayland is. Please let them know their work, as yours, is greatly appreciated.
jjgalvezParticipantThank you for the clarification. Hopefully these will be resolved soon.
Just to provide another datapoint for you, over the weekend I tried !M with Mint using the Cinnamon desktop using Wayland, and was able to connect, As well as Fedora 40 (via the live ISO) using KDE and was not able to connect with the same error.
jjgalvezParticipantThank you I will keep an eye on those TRs.
jjgalvezParticipantthe 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.
jjgalvezParticipantapologies 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
jjgalvezParticipantMonitor MSI Optix Mag321CQR
resolution: 2560×1440 @ 60 Hz
scale: 120%RGB Range full color
jjgalvezParticipantAfternoon 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:
jjgalvezParticipantinteresting, are there any workarounds or do i need to set the color depth on my desktop to something less than fullcolor?
jjgalvezParticipantserver and client logs sent. Hope they are helpful
jjgalvezParticipantThank you I will submit the logs later today
jjgalvezParticipanthappy to provide any additional information / logs that might be useful
jjgalvezParticipantUGG nevermind, clearing cache and data for the nomachine app fixed the problem. I should have tried that first before posting.
Please consider this resolved
-
AuthorPosts