Unrelated to the current report, anyway I'll stick to my old Raspbian 32
bits (Buster) since Ubuntu 22.04 currently lacks video hardware
acceleration:
https://ubuntuforums.org/showthread.php?t=2478838
... one of the main uses of my RaspbPi being to watch videos without
having run my Desktop PC!
@fprietog
Indeed I regret the open VNC standard is dropped in favour of the
proprietary Microsoft's protocol RDP, itself using H.264 licence ridden
compression. It might be a more efficient standard (I hope so at least),
but it does not go in the direction of freedom!
This issue about RDP would
@Zakhar
Don't waste your time with this application. In kinetic the VNC support
has been dropped because GNOME rules, and Ubuntu, as a GNOME sub-brand,
blindly followed that decission.
You can still use another VNC server if you are using X11 (I don't know
a VNC server that works for Wayland).
Sorry for the incomplete search...
Apparently this is sort of a "known bug", due to the fact that when in
"auto-login" the keyring is not unlocked then VNC server cannot access
the stored password and creates a new random one.
https://askubuntu.com/questions/1403943/22-04-remote-desktop-sharing-
New test on January 14th 2023!
VNC from another Ubuntu machine using Remmina as client is now working
with severe limitations.
Documentation I found after some more research:
- Probably a security feature:
Remote Desktop does NOT work when:
- the session is locked
- even when screen is blanked
Sorry @Dave Jones to have considered Remote Desktop as "basic". It has
been in "settings" for a while now in Ubuntu, so I was taking it for
granted.
And yes I'm aware of X-forwarding... it does NOT provide a full desktop
but only discrete graphical applications, and I have used it in some
Can confirm, both VNC and RDP have started to work with the latest
update.
Many many thanks, I had to postpone Ubuntu upgrades on Raspberry Pi 4
since 20.10 because of remote desktop issues.
Hint that solved inability to connect with the screen locked:
$ flatpak install flathub
> I don't know what you mean when said that remote desktop is a recent
addition to the desktop...
I'll just address this point, but continue the discussion of what should
be included in the mandatory testing over on LP: #1978113.
What I specifically meant by "recent addition" is that, prior to
@waveform
I think that the meaning of "basic" feature in an OS is something that
can't be stated universally because it depends of the usage done by each
set of users. In my opinion remote desktop is a "basic" feature because
I use the Raspberry Pi remotely. And for a Raspberry Pi that's nothing
> It is a pity Canonical is advertising super optimisations on
> Raspberry Pi 4 with 22.04 and this basic feature is totally broken
> as is: was never ever tested...
Graphical remote desktop is far from a "basic" feature, in my opinion
(an opinion bolstered by the fact it is only a recent
fprietog, that's a driver issue. Nothing what g-r-d can do about (nor even
knows about). It should be reported against the RPi gpu driver here.
This is something, that Ubuntus Raspberry Pi team should actually test, before
advertising RPi support.
Possible related issues:
Well, as I stated above the fix is working and now VNC and RDP
connections are working again.
But I've tested gnome-remote-desktop under X11 and Wayland and there is
a real performance problem in Wayland compared to X11 (key presseds are
shown with a lag of seconds because refresh takes too much
The gnome-remote-desktop 42.1.1 release is rolling out in updates over
the next few days.
** Changed in: gnome-remote-desktop (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Just updated to these packages:
- gnome-remote-desktop (42.1.1-0ubuntu1)
- libfreerdp2-2:arm64 (2.6.1+dfsg1-3ubuntu2.1)
- libfreerdp-server2-2:arm64 (2.6.1+dfsg1-3ubuntu2.1)
- libfreerdp-client2-2:arm64 (2.6.1+dfsg1-3ubuntu2.1)
And VNC and RPD sharing are working now in arm64 (Raspberry Pi 4B).
As a temporary (or final) solution just use another VNC or RDP Server.
You can do that only if you use X11 because apart from gnome-remote-
desktop there are no working desktop sharing utilities for Wayland.
You've more info here: https://help.ubuntu.com/community/VNC/Servers
For instance, I'm
hello guys,
This issue is really making ubuntu 22.04 useless on raspberry pi 4,
DOES ANYONE HAVE ANY ALTERNATE OR TEMPORARY SOLUTION TO IT?
we need to use raspberry pi remotely as it is mounted on our robot
without connecting any screen.
:)
It would help us a lot
--
You received this bug
I am experiencing the exact same syndromes plus "Settings" does not seem
to be recording correctly the VNC password, it keeps taking another
value after reboot... strange, I'll have to reproduce it.
I am eagerly waiting for the fix to make its way to the official repos!
It is a pity Canonical is
** Changed in: gnome-remote-desktop (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-remote-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/1970139
Title:
VNC Connection doesn't
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-remote-desktop (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-remote-desktop in Ubuntu.
Thanks Pascal for the details, we will make sure to do a stable update
with the fixes you mentioned (or using 42.1.1)
** Changed in: gnome-remote-desktop (Ubuntu)
Importance: Undecided => High
** Changed in: gnome-remote-desktop (Ubuntu)
Status: Incomplete => New
** Changed in:
As for the RDP connection problem, please provide enough information.
If you have an updated system, then your FreeRDP build should contain the NTLM
fixes. Jeremy afaik backported them to Ubuntu in
https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1968577.
Meanwhile, FreeRDP-2.7.0 was
To be honest, the issue description is insufficient and the crash file useless.
The stacktrace does not contain any debug symbols and for the "sometimes shows
screen garbage before disconnecting" part, a screenshot would be needed,
because the screen content is not just garbage.
It has a
* How did you enable the sharing?
Using the config page: see attached image.
I'm using exactly the same configuration and OS in 3 computers: 2 amd64
and the arm64 Raspberry Pi. In the amd64 ones VNC works. It only fails
in the arm64 Raspberry Pi.
* The default protocol and suggested one is RDP,
Thank you for your bug report. How did you enable the sharing? The
default protocol and suggested one is RDP, did you try if that works
better?
** Changed in: gnome-remote-desktop (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
I managed to get a crash file from apport. It's attached.
** Attachment added: "apport crash file"
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970139/+attachment/5583259/+files/_usr_libexec_gnome-remote-desktop-daemon.1026.crash
--
You received this bug notification
25 matches
Mail list logo
