PureOS 10.0, Gnome 3.38.5, wayland
How do I get the computer running PureOS to share its desktop to remote clients (Ubuntu 22.04/wayland using Remmina) on the same LAN via VNC? I have gnome-remote-desktop installed and configured via Settings, but that still won’t work. (Another computer in the LAN running Ubuntu 22.04/wayland can share its desktop via VNC just fine.) All I see in Remmina on the client machine is a black window.
I found the homepage from apt-cache show gnome-remote-desktop apparently it’s RDP but for VNC you can enable it with grdctl according to the website. Or you could try vino
Another cheesy way would be to set up a Zoom meeting. Then share the desktop from there. (The free unpaid account meeting would get you 40 minutes.)
You can’t do that over LAN.
Zoom is probably not a good choice for anyone:
I suppose you’re right, that would imply WAN not LAN.
(Unless your LAN is connected to the outside world, then it might fly.)
Wayland… I will never move to this as long as X still runs. If X ever disappears than I will be forced to wayland (this excludes L5 of course).
Install X and use x2go.
Also Ubuntu has eveolved to be so sloooow…
Security!!
(1) Didn’t now that ssh is insecure… Does Secure Shell have a misleading name?
(2) We have seen the security of systems that do not do that. Such as MS-Windows.
(3) So the whole reason for wayland was to make us secure by disallowing network capabilities? I got this logic… Hand hurts, hand removed.
I thinki it was Harvey Corman and Tim Conway that did a skit (one of them in German uniform and faux German accent, during a WWII interrogation):
“You Vill Sign Zee Papers.”
“I can’t sign zee Papers.”
“You VILL Sign Zee Papers!”
“But I CAN’T sign zee papers!”
(Repeat above with different threats and inflection several times.)
“Vhy won’t you sign zee papers?”
“Because you have cut off both my hands!” (Holds up empty coat cuffs.)
Thanks @Jors, but your answer confuses me.
After I had installed gnome-remote-desktop - without knowingly doing anything with grdctl - in the computer settings under sharing, the option to share the screen appeared. I selected the options, and then it told me that a remote device could now access this computer by connecting to vnc://devicename.local. So, that makes me think that simply installing gnome-remote-desktop is for VNC? Or, what am I - a non-tech layman - misunderstanding?
(Anyway, even with gnome-remote-desktop installed and configured, I still cannot access the computer’s desktop from a remote device on the same LAN.)
On other machines running Ubuntu and Wayland and serving their desktops via VNC I am able to remotely connect to their desktops just fine. I have this problem only with the PureOS machine that I want to reach from a remote client.
(I should clarify, my question pertained to that computer running “out-of-the-box” PureOS Byzantium 10.0. I’m trying to learn how to serve its desktop without major changes like changing the defualt windowing system. I am sorry about not making that clear upfront for everyone.)
Still not clear on what the answer to my original question is. If the true answer is something like, “It cannot be done at this time”, well, at least then I will know the truth.
I looked a bit into your problem and found that if you change the firewall zone in PureOS to ‘trusted’ under Advanced Network Configurations, then Remmina or Boxes will find your VNC server with the correct IP address.
Yeah, I stumbled across that idea very shortly before your post talking about firewall zones.
I thought I had the VNC service allowed when I posted my original question. As a quickie shortcut I had relied on the gufw tool to open up everything just while testing this VNC thing, I thought that would do the trick. I guess though that PureOS has some firewall rules that gufw can’t “undo”??? Anyway, when I used the Firewall tool in the PureOS store I saw that the VNC service was not allowed, and when I allowed it in that tool the VNC desktop access worked.
True. But it is not this. The security problem of X will be maybe exposed if you open a direct X connection. In old days and @tracy surely remembers this, a terminal running X would use xdm to connect to a server and pull the full desktop from there. This method has its security issues.
But going through ssh, all X traffic is encrypted and tunneled through ssh. I do not see any security problem with this. This is the difference. And x2go can be trivially configured to pass everything through ssh. NX does a similar thing in the commercial world. There are no real security issues here (except for ssh itself).
Wayland restricts this by removing all network capabilities just like …MS-Windows.
@dln949 Good that you have success with VNC. My only reaction to this is that some problems were easily solved in the past. And people want to re-invent the problem so that they re-invent a “solution”. Only this time it looks very complicated and less efficient.
I believe that people should build on the past. Not demolish good constructions just for rebuilding something worse.
In the distant past we had CDE on the desktop (even olvm @tracy). These desktops had for example actions based on filetype. So you could click on a pdf file and some program would open the file. Imagine how you would feel if Gnome/KDE did not have this capability. Just because. Wayland does this with X (although it tries to solve other issues) and Gnome3 did that with Gnome2.
Another feature I miss from the modern desktop is to minimize apps on the desktop. CDE had this, olvm too, XFCE has this hidden. No modern desktop does this. People just forgot this capability or never saw it. Same goes for network capabilities of the X. People will forget in a few years.
Nah, I remember typing on paper with an Orator font then photocopying them to clear sheets and taking the results to overhead projectors.