Comment 15 for bug 1970139

> 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 addition to the
set of seeded packages on the desktop).

Booting, graphical session starting successfully, login operating, web
browser launching, video and audio playback working, ethernet, wifi,
and bluetooth communication working, USB peripherals functioning.
These are "basic" features. These are the sorts of things on the ISO
test list [1] that get tested on all supported Pis prior to release
and which, should they fail, will either constitute a release blocker
or, at the very least, are added to the release notes.

[1]: http://iso.qa.ubuntu.com/qatracker/milestones/433/builds/250034/testcases

> This is a complete show-stopper for me as remote access to the
> machine, be it through SSH (which works!) or graphically, is sort of
> a necessary feature for this kind of machines.

Are you aware of X-forwarding over SSH, which incidentally works
happily on the Pi desktop images? What remote graphical functionality
do you require that is not supported by this?

> Probably some way of improvement in the QA... like suggesting
> Canonical to buy a Raspberry Pi 4 to the maintainers involved!..
> That's a pretty inexpensive machine. :-)

As I hope is clear from the above, we do have Pi 4s (quite a lot of
them, as we need to cover numerous models and board revisions), and
testing does indeed occur.

Coincidentally, though remote desktop is not on the "mandatory" list
of testing, I was aware of this bug shortly before jammy's release
(and went back and re-verified it after the release, confirming it).
However, I felt it didn't warrant inclusion on the release notes
because it's simply not "basic" functionality, and there were far more
important things that were (and in some cases still are), broken at
release time.

That said, remote desktop is (now) seeded and it would be useful to
add it to an optional list of tests to run through before release. To
that end I've opened LP: #1978113 to remind myself to write an
"optional" set of tests for the desktop images. Please feel free to
make the case (on LP: #1978113) that remote desktop should be on the
"mandatory" list of tests, if you feel it is genuinely critical
functionality (I can just about see the case for X-forwarding over
SSH; I cannot, currently, for full remote desktop).