I think it's too late. There's no way to avoid Wayland. On our side we tested it and fixed some bugs. There might be more, it's a big stack of packages :(
On Mon, Dec 22, 2025 at 12:55 PM Rick Troth <[email protected]> wrote: > Marcela outed the likely issue in the list-o-packages ... Wayland. > I've been concerned about this for a long time already, that Wayland > adoption will render certain features/functions unavailable. > > There's no fighting the Wayland wave. X11 is long in the tooth and has > always been too chatty. (Though fears about security are inflated.) > My argument is rather that the Wayland implementers will be more > diligent ... that they would be thorough. > In this case, it's the installer developers, but similar admonition: > don't break stuff! (and RDP seems broken) > > I'm not sure any of this would help VNC because (from all I can tell) > VNC is inherently X11. > But there IS some accommodation for X11 in the Wayland world, and maybe > that just needs to grow. > Back, then, to the installer coders: don't kill off the VNC option! > (until RDP is universal) > > > -- R; <>< > > > > On 12/22/25 5:18 AM, Neale Ferguson wrote: > > My problems were happening during the install process so I was booting > from the KERNEL.IMG/GENERIC.PRM/INITRD.IMG. Therefore, there’s no option > for installing the RDP stuff prior to running the install. So either (a) > there’s a problem with my MacOS RDP program or (b) there’s a problem with > the stuff in the installation materials. > > > > However, I can try installing these packages on the system I installed > using the “text” method. If I am able to connect to the daemon running > there then I know it’s the installation materials at fault. > > > > Thanks... > > > > Neale > > > > > > > > Hi, > > in SUSE we made the same change to RDP. I can give you a list of packages > > you need to install. They might have different names > > on CentOS/RHEL. > > This was working for SLE-16.0. Our desktop team needed to fix some > packages > > to make it work. Good luck! > > On your client, just install Remmia > > On the server: > > # Setting up gnome-remote-desktop > > sudo zypper in -y gdm-systemd gnome-remote-desktop freerdp-server > > gnome-session-wayland > > sudo systemctl enable gdm > > sudo systemctl start gdm > > > > # You probably have to do `su -` here first for this one: > > sudo -u gnome-remote-desktop winpr-makecert -silent -rdp -path > > ~gnome-remote-desktop rdp-tls > > > > # Set RDP_USER and RDP_PASS to whatever you want > > sudo grdctl --system rdp set-credentials "$RDP_USER" "$RDP_PASS" > > sudo grdctl --system rdp set-tls-key > > /var/lib/gnome-remote-desktop/rdp-tls.keysudo grdctl --system rdp > > set-tls-cert /var/lib/gnome-remote-desktop/rdp-tls.crt > > > > sudo grdctl --system rdp enable > > > > sudo systemctl --now enable gnome-remote-desktop.service > > > > # MAYBE for debugging: > > systemctl stop firewall > > > > ---------------------------------------------------------------------- > > For LINUX-390 subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO LINUX-390 > or visit > > http://www2.marist.edu/htbin/wlvindex?LINUX-390 > > > -- > -- R; <>< > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or > visit > http://www2.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
