- This topic has 4 replies, 2 voices, and was last updated 3 days, 4 hours ago by
.
-
Posts
-
Looking thru the forum there hasn’t been any real recent discussion about this so I am wondering if this has been resolved or not. I just downloaded the Windows and Pi5 packages on (1/21/25)
This machine has 8GB RAM, a ‘uname -a’ shows I am running:
Linux rasp-pi5 6.6.62-rpt-rpi-2712 #1 PREEMPT Debian 1:6.6.62-1-rpt1 (2024-11-25) aarch64 GNU/Linux
This is a fairly new machine with next to no modifications to it. I just stumbled onto NoMachine a couple of days ago and downloaded and installed on this Rasp-Pi5, Windows 10 and Windows 11 to see if it would work for my needs. The Windows to Windows and Rasp-Pi to Windows works great but from either Win 10 or 11 to Pi5 fails on a “Error is 108: Connection reset by peer” condition. I have experienced this while the Pi5 was connected to a HDMI Monitor as well as Headless, actually the HDMI monitor is connected to a 3-way HDMI switcher.
I came across the Error Logs Procedures, in another post, and I can provide both the Server and Client Logs, if needed.
Also upon a reboot I was presented with an option to change from (Wayland) Wayfire to LabWC and do not know if that is a possible solution but on the off chance you would want logs I decided to defer that change until you responded.
Since it has been a long time since I worked on Unix/Linux and I am surely more than a bit rusty I did not want to go messing with things as the first attempt to resolve this issue.
Keith
Hi, can you check whether the workaround in this Trouble Report helps?
BritGirl,
Yes, this allows me to login into the Pi5 machine now, THANX !!
Should I not accept the request to change to LabWC at this time?
Regards,
Keith
The workaround we provided is to disable Wayland, and fall back to X.org. That LabWC requires Wayland if I am not mistaken, so enabling it when you’ve disabled Wayland could cause further issues? I would not switch if I were you.
You must be logged in to reply to this topic. Please login here.