Forum / NoMachine for Linux / Can’t connect with KDE Wayland on Arch
- This topic has 8 replies, 2 voices, and was last updated 2 months, 2 weeks ago by Britgirl.
-
AuthorPosts
-
July 22, 2024 at 08:23 #48861jjgalvezParticipant
Good Morning,
I was hoping that version 8.12.12 would solve the 104 error, however I am still having the issue after upgrading. When I try to connect the client cycles through several attempts to connect before finally failing with 104 error. For reference my specs are:
Operating System: EndeavourOS (Arch derivative)
KDE Plasma Version: 6.1.3
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2
Kernel Version: 6.9.10-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LENOVO
Product Name: 20KG0022US
System Version: ThinkPad X1 Carbon 6th
I am also attaching both server and client logs.
July 22, 2024 at 12:06 #48874BritgirlKeymasterSorry for any confusion. I mistakingly inserted in to the old topic that TR05V11141 had been fixed.
Your previous topic highlighted the following TRs:
Attaching to the physical desktop could fail on Rocky Linux 8 with Wayland
https://kb.nomachine.com/TR03U10784 andCapture of the Wayland desktop by EGL doesn’t work with KDE Plasma 6
https://kb.nomachine.com/TR05V11141These are not fixed yet.
July 22, 2024 at 13:20 #48880jjgalvezParticipantThank 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.
July 22, 2024 at 15:01 #48883BritgirlKeymasterThanks for the additional info. I confused https://kb.nomachine.com/TR05V11141 with https://kb.nomachine.com/TR04V11131 (The latter was fixed in the latest update). Our developers are currently working on the somewhat complicated KDE issue (TR05V11141), but we are unable to promise a fix in the next maintenance release.
July 22, 2024 at 18:39 #48899jjgalvezParticipantThank 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.
July 24, 2024 at 08:33 #48905BritgirlKeymasterThanks very much, the message has been passed on 🙂
September 11, 2024 at 15:09 #49619jjgalvezParticipantJust 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.
October 3, 2024 at 19:37 #49919jjgalvezParticipantThank 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.
October 4, 2024 at 08:21 #49930BritgirlKeymasterHi, sorry for not updating you on the situation with the fix after your penultimate post. I thought I had. Good to know that the update has fixed your issue. In the 8.14 release there is the fix for https://kb.nomachine.com/TR03U10784, one of the problems you were encountering. Let us know if you encounter further issues.
-
AuthorPosts
This topic was marked as solved, you can't post.