Yes, I ran 'killall gnome-software' before testing
Even when running gnome-software from a terminal which has the http proxy environment variables set, gnome-software still does not work.
Using netstat shows that the problem child is /usr/libexec/flatpak-system-helper
This was testing with Gnome-software 44.5
I'd be quite happy with auto-login storing the password in plain-text somewhere, and unlocking the keyring at boot.
As soon as a person enables auto-logon, they have effectively given up on passwords anyway.
This means that the keyctl_set_timeout function has a bug, because it should expire the keys based on elapsed monotonic time, not wallclock time. Something in it's code is using the wrong kind of clock or the wrong kind of timer.
As an open-source maintainer myself, I have some sympathy.
But the thing is, all of these problems are ones Gnome has created for itself.
The most common case (single user connecting to a single account on a box) used to "just work".
Then people started pretending that anything outside of Gnome was unsupported (i.e. other VNC clients).
Then Wayland decided that remote desktop should go via PipeWire (which broke all kinds of stuff for quite some time, and introduced massive extra latency).
And now it has been decided that instead of solving the simple case, things will just stay broken until solved the most complex case possible (this is known as the Boiling The Ocean approach).
See discussion here: gnome-remote-desktop#140 (comment 1654425)
Basically, after auto-logon happens, VNC/RDP/Gnome-Remote-Desktop starts.
Then when I attempt to access RDP/VNC (from another machine), GRD tries to authenticate but receives an error message from gdm. Manually unlocking the keyring solves this.
There is no disk encryption in play here (i.e. this does not appear to be issue #701)
On Fedora32, it appears to be logging into the Wayland desktop, even though I have selected the X11 desktop.
As of Ubuntu22.10 (i.e. GNOME 43.1), this does not appear to be an issue for me anymore (might have been fixed in an earlier version actually)
For the benefit of anyone else who runs across similar issues:
This appears to be related to my use of "auto-logon" i.e. when the machine boots it automatically logs into my desktop.
If I restart the machine I cannot connect.
However, after restarting, if I then explicitly log out and then log back in again, it works again.
Much better! Thanks!
Jan 31 13:16:53 librebuild3 gnome-remote-de[560185]: [RDP.RDPGFX] CapsAdvertise: Accepting capability set with version RDPGFX_CAPVERSION_106, Client cap flags: H264 (A>
Jan 31 13:16:53 librebuild3 gnome-remote-de[560185]: [RDP.AUDIO_PLAYBACK] Client Formats: [AAC: false, PCM: true]
Jan 31 13:16:53 librebuild3 gnome-remote-de[560185]: [RDP.CLIPRDR] Client capabilities: long format names, stream file clip, file clip no file paths, can lock clip dat>
Jan 31 13:16:52 librebuild3 gnome-remote-desktop-daemon[560185]: [13:16:52:180] [560185:560242] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_COMPLE>
Jan 31 13:16:52 librebuild3 gnome-remote-desktop-daemon[560185]: [13:16:52:179] [560185:560242] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_CONTIN>
Jan 31 13:16:50 librebuild3 gnome-remote-de[560185]: Unable to check file descriptor, closing connection
Jan 31 13:16:50 librebuild3 gnome-remote-desktop-daemon[560185]: [13:16:50:877] [560185:560185] [ERROR][com.freerdp.core.transport] - BIO_should_retry returned a syste>
Jan 31 13:16:50 librebuild3 gnome-remote-desktop-daemon[560185]: [13:16:50:877] [560185:560216] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->R>
Jan 31 13:16:50 librebuild3 gnome-remote-desktop-daemon[560185]: [13:16:50:877] [560185:560216] [ERROR][com.freerdp.core.peer] - peer_recv_callback: CONNECTION_STATE_I>
Jan 31 13:16:50 librebuild3 gnome-remote-desktop-daemon[560185]: [13:16:50:877] [560185:560216] [ERROR][com.freerdp.core.transport] - client authentication failure
Jan 31 13:16:50 librebuild3 gnome-remote-desktop-daemon[560185]: [13:16:50:877] [560185:560216] [ERROR][com.freerdp.core.nla] - [nla_recv] error: -1
Jan 31 13:16:50 librebuild3 gnome-remote-desktop-daemon[560185]: [13:16:50:877] [560185:560216] [ERROR][com.freerdp.core] - transport_read_layer:freerdp_set_last_error>
Jan 31 13:16:50 librebuild3 gnome-remote-desktop-daemon[560185]: [13:16:50:877] [560185:560216] [ERROR][com.freerdp.core.transport] - BIO_read returned a system error >
Jan 31 13:16:50 librebuild3 gnome-remote-desktop-daemon[560185]: [13:16:50:876] [560185:560216] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_COMPLE>
Jan 31 13:16:50 librebuild3 gnome-remote-desktop-daemon[560185]: [13:16:50:871] [560185:560216] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_CONTIN>
Jan 31 13:16:13 librebuild3 gnome-remote-de[560185]: RDP server started
Jan 31 13:16:13 librebuild3 systemd[1305]: Started GNOME Remote Desktop.
Jan 31 13:16:13 librebuild3 systemd[1305]: Starting GNOME Remote Desktop...
Jan 31 13:16:13 librebuild3 systemd[1305]: Stopped GNOME Remote Desktop.
Jan 31 13:16:13 librebuild3 unknown[1596]: RDP server stopped
Jan 31 13:16:13 librebuild3 systemd[1305]: Stopping GNOME Remote Desktop...
noel@librebuild3:~/libo$ grdctl status --show-credentials
RDP:
Status: enabled
TLS certificate: /home/noel/.local/share/gnome-remote-desktop/rdp-tls.crt
TLS key: /home/noel/.local/share/gnome-remote-desktop/rdp-tls.key
View-only: no
Username: noel
Password: noel
I am logged in (with gnome on X11 if that makes any difference)
I tried running
echo -n "<password>" | gnome-keyring-daemon --unlock --replace
does not seem to make any difference, still see same error message in logs.
Mine (on Windows10) just says "an internal error has occurred"
and on the server side, I see in the logs:
Jan 31 12:31:26 librebuild3 gnome-remote-de[1596]: [RDP] Couldn't retrieve RDP credentials: The name :1.3 was not provided by any .service files Jan
I can no longer VNC into my Ubuntu box
Sharing, etc, is enabled
Thanks for you help, looks like this an Ubuntu problem.
Sigh.
Can't even use RDP, Windows Remote Desktop client still doesn't like the gnome-remote-desktop RDP server.
noel@librebuild3:~/libo$ grdctl status
RDP:
Status: enabled
TLS certificate: /home/noel/.local/share/gnome-remote-desktop/rdp-tls.crt
TLS key: /home/noel/.local/share/gnome-remote-desktop/rdp-tls.key
View-only: no
Username: (hidden)
Password: (hidden)
noel@librebuild3:~/libo$
So
() I was running Ubuntu 22.04 () I had a working VNC connection (*) I ran the upgrade process (the GUI one) to update to Ubuntu 22.10
And now I no longer have any kind of VNC connection.
Hmmm, possibly this is an Ubuntu bug, possibly they have removed VNC?
It is rather hard to tell, there are various bits of information floating around the internet, none of which are definitive.
I can say for certain that nothing is listening on the VNC port on that machine.
I can no longer VNC into my Ubuntu box
Sharing, etc, is enabled
But this is a situation, where g-r-d has no control about: Basically, g-s or mutter close the PipeWire stream here.
g-r-d just reacts to the client side here by closing the connection.
The root of the problem IMNSHO, is that we are working around Wayland here. This is a case where gnome-r-d really needs a direct API to Wayland to get accurate and timely information. Using DBUS and PipeWire is strapping an engine to a bicycle tire instead of building it into the frame properly.