Forum Replies Created
-
Posts
-
Apologies for replying sooner, the notice ended up in my spam folder. I am using the opensource amd drives which are part of mesa 1:24.2.7. What addition info on the driver can I provide? Also this is not a VM.
Are there any workarounds other than using X11 because none of the other capture methods seem to work either?
Thank 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.
Just 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.
Thank 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.
Thank 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.
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.
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
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:
interesting, are there any workarounds or do i need to set the color depth on my desktop to something less than fullcolor?
