FFe: [MIR] freedp2 -> freerdp3 in main

Bug #2057842 reported by Jeremy Bícha
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
freerdp3 (Ubuntu)
Fix Released
Undecided
Unassigned
gnome-remote-desktop (Ubuntu)
Fix Released
Undecided
Unassigned
remmina (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Feature Freeze Exception Request
--------------
There are only 2 packages in Ubuntu main that use freerdp2: remmina and gnome-remote-desktop. It is requested to switch both to freerdp3. Therefore only one version of freerdp will be in main. freerdp2 will be demoted to universe since many universe packages use it and are not prepared to switch to freerdp3.

This also requests updating gnome-control-center to fully enable the features of gnome-remote-desktop 46.

Impact
------
A headline feature of GNOME 46 is support as a Remote Desktop server without requiring someone to already be logged in locally ("headless" mode). This feature requires gnome-remote-desktop 46. gnome-remote-desktop 46 requires freerdp3.

Impact if this does not happen
------------------------------
- We would need to patch gnome-control-center to use the older Remote Desktop panel (or at least hide the new tab for Remote Login)
- We would need to keep using gnome-remote-desktop 45 instead of 46. The gnome-remote-desktop upstream maintainers would be unhappy with this decision. gnome-remote-desktop 45 was tested against Mutter 45. Changes in Mutter 46 may require changes in gnome-remote-desktop for things to work well although a simple test showed that basic remote desktop seems to work ok with the mismatch. (See comment #1 from upstream developer.)

Why this did not land sooner
---------------------------
It required the packaging of a new source package freerdp3. And we had to do this sooner than Debian. Sorry too many things to do before Feature Freeze and this did not make it.

Affected Packages
-----------------
- gnome-remote-desktop 45 -> 46
- gnome-control-center (to update the Remote Desktop settings page)
- remmina 1.4.34 -> 1.4.35 and swap build-depends. Remmina 1.4.34 did not work with freerdp 3.3 in my testing
- gnome-connections (build-dependency swap): Not required by other changes and not in Main but makes sense to switch it also

Affected Flavors
----------------
Only Ubuntu Desktop and Edubuntu ships gdm3, gnome-control-center, gnome-remote-desktop. (Cinnamon 23.04 and daily 23.10 also ships gnome-control-center but this appears to be a bug since they ship cinnamon-control-center and is likely already fixed in noble-proposed)

Remmina is included in Ubuntu Desktop, Cinnamon, Kylin, and Unity.

gnome-connections has no reverse dependencies or recommends.

Upstream Changes
----------------
https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/blob/46.rc/NEWS

https://gitlab.com/Remmina/Remmina/-/blob/rel/v1.4.35/CHANGELOG.md

gnome-control-center 46~beta was already in Ubuntu 24.04 LTS before Feature Freeze. It will be updated to 46.0. The relevant part here is whether we use the 46~beta version of the Remote Desktop page or the 46.0 version.
https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/46.rc/NEWS

Build Logs
----------
I have backported GNOME Shell 46 RC and GTK4 4.13 to the Ubuntu Desktop PPA. The PPA currently has noble-proposed disabled so that it is easily possible to try this set of packages without dealing with the incomplete 32-bit time transition in noble-proposed. In addition, the PPA has the affected packages from this FFe.

https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+packages

Testing Done
-------
1. From Ubuntu 23.10 client using Remmina, I was successfully able to connect to Ubuntu 24.04 LTS host using GNOME Shell 46 RC and GNOME Remote Desktop 46 RC. Remote control worked.

2. From Ubuntu 24.04 LTS client with Remmina 1.4.35 built with freerdp3, I was able to connect to Ubuntu 23.10 host. Remote control worked.

3. From Ubuntu 24.04 LTS client with GNOME Connections 46 RC built with freerdp3, I was able to connect to Ubuntu 23.10 host. Remote control worked.

4. I added a new Remote Login test case to https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop and verified that remote login worked. Notably, enabling this changes the port for the older service, now called "Desktop Sharing" to 3390. Since 3389 is the default port, users would then need to manually specific port 3390 for Desktop Sharing in their remote connection app (Remmina, GNOME Connections, etc.).

Tags: noble
Jeremy Bícha (jbicha)
Changed in remmina (Ubuntu):
status: New → Incomplete
Changed in gnome-remote-desktop (Ubuntu):
status: New → Incomplete
Jeremy Bícha (jbicha)
description: updated
summary: - [DRAFT] FFe: freedp2 -> freerdp3 in main
+ FFe: freedp2 -> freerdp3 in main
description: updated
Revision history for this message
Pascal Nowack (pnowack) wrote : Re: FFe: freedp2 -> freerdp3 in main

gnome-remote-desktop-45 is not compatible with mutter-46. All you need to do is use a system with the NVIDIA driver, run g-r-d-45 with mutter-46 and you either run into a black screen, or you might see an initial frame but no updates (freezed screen).

Jeremy Bícha (jbicha)
description: updated
Changed in gnome-remote-desktop (Ubuntu):
status: Incomplete → New
Changed in remmina (Ubuntu):
status: Incomplete → New
description: updated
Revision history for this message
Graham Inggs (ginggs) wrote :

FFe approved.

Note that freerdp3 will still need a MIR. Considering this is a straight swap with freerdp2, from the same upstream, it might still be possible for that to be done in time.

Changed in gnome-remote-desktop (Ubuntu):
status: New → Triaged
Changed in remmina (Ubuntu):
status: New → Triaged
Jeremy Bícha (jbicha)
Changed in gnome-remote-desktop (Ubuntu):
status: Triaged → Fix Committed
Changed in remmina (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

MIR Team approval to replace freerdp2 with freerdp3 in main.
Both stay in the archive, only one will be released with noble being in main.

This comes with the discussed requirement of giving this chance a try to add at least some QA.
Right now tests are disabled at build and no autopkgtest is present.

Jbicha said tests are fine but time is scarce.
But Seb was so kind to agree to spend efforts of the Team to add tests before Noble is released.

To unblock things we approve "now" (to get things moved before beta freeze), but want to hold you accountable to get the tests in place.

summary: - FFe: freedp2 -> freerdp3 in main
+ FFe: [MIR] freedp2 -> freerdp3 in main
Revision history for this message
Jeremy Bícha (jbicha) wrote :

I opened https://launchpad.net/bugs/2058401 for the test issue and created a Jira card.

Jeremy Bícha (jbicha)
Changed in freerdp3 (Ubuntu):
status: New → In Progress
Jeremy Bícha (jbicha)
Changed in freerdp3 (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Jeremy Bícha (jbicha) wrote :

The promotion to main is done. This bug will be automatically closed once gnome-remote-desktop and remmina migrate out of noble-proposed.

Changed in freerdp3 (Ubuntu):
status: Fix Committed → Fix Released
Steve Langasek (vorlon)
tags: removed: update-excuse
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package remmina - 1.4.35+dfsg-0ubuntu2

---------------
remmina (1.4.35+dfsg-0ubuntu2) noble; urgency=medium

  * No-change rebuild against libcups2t64

 -- Michael Hudson-Doyle <email address hidden> Wed, 20 Mar 2024 13:56:31 +1300

Changed in remmina (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-remote-desktop - 46~rc-0ubuntu2

---------------
gnome-remote-desktop (46~rc-0ubuntu2) noble; urgency=medium

  * No-change rebuild for mutter ABI changes on armhf.

 -- Matthias Klose <email address hidden> Mon, 25 Mar 2024 19:27:18 +0100

Changed in gnome-remote-desktop (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.