Remote Control under Remote Desktop sharing option only works for VNC

[Marco Trevisan (Treviño)]

[ Impact ]

Toggling "Remote Control" doesn't apply the value to the RDP service

[ Test case 1]
0. Install the updated gnome-control-center packages.
1. Open the Settings app
2. In the left sidebar, choose Sharing.
3. Turn on sharing in the top bar of the app the click Remote Desktop
4. Turn on Remote Desktop
5. Turn on "Enable Legacy VNC Protocol"
6. Turn on Remote Control
7. Open a terminal and run
grdctl status

View-only: No and Status: enabled should show for both RDP and VNC.

[ Test case 2]
Complete Test Case 1. Then
From a second computer, connect to the first computer using Remmina.

The Remote Desktop page on the first computer provides the username and password to use. Just use the first computer's IP address.

So something like:
RDP jeremy@192.168.1.1

Ensure that the RDP connection works and that you can remotely control the first computer from the second computer.

Disconnect.
Then reconnect but switch the protocol in Remmina to VNC

So something like:
VNC jeremy@192.168.1.1

Ensure that the VNC connection works and that you can remotely control the first computer from the second computer.

[ Regression Potential ]

Remote control setting does not work for VNC, changing settings manually from gsettings isn't immediately reflected by the UI.

[ Workaround ]
If you are affected by this issue, you can use this workaround on the machine that you are trying to connect to.

Open a terminal and enter this command:
gsettings set org.gnome.desktop.remote-desktop.rdp view-only false

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-control-center - 1:42.2-1ubuntu1

---------------
gnome-control-center (1:42.2-1ubuntu1) kinetic; urgency=medium

  * debian/patches: Drop applied upstream and update old to use Gtk4 and Adw.
    Some have been dropped as not relevant anymore.
    While usage of AdwLeaf is now too invasive to do a revert as per
     debian/patches/ubuntu/window-Stop-using-HdyLeaflet.patch so it's better
    if we just help fixing the issues upstream.
  * debian/patches: Ensure VNC/RDP remote control setting is honored
    (LP: #1977663)
  * debian/patches: Drop workaround for X-SnapInstanceName.
    It's in snapd for 3 years now, we can safely assume we support it.
  * background: Allow configuring the ubuntu accent color.
    Move the ubuntu colors configuration to a single widget
    (CcUbuntuColorsRow) so that it can be easily included in other widgets
    with minimal changes.
    We keep resources and the widget itself compiled together with the ubuntu
    panel, so that there's no need to change multiple panels build scripts,
    given that these are per-process anyways.
    Helps with LP: #1968213
  * ubuntu-colors-row: Do not change themes on startup (or on user changes)
    Do not override user themes unless an user has explicitly selected a
    color theme. This applies to both the user theme and the icons, as we
    want a consistent experience. But users could still use tweaks to change
    them.
    At the same time, avoid changing the gedit color scheme if an user
    previously set a non-Yaru theme. (LP: #1968213)
  * debian/patches: Ensure both VNC and RDP settings are disabled if requested
    (LP: #1971415)
  * debian/patches: Move the VNC support patch under the ubuntu topic

gnome-control-center (1:42.2-1) unstable; urgency=medium

  * New upstream release
  * Drop the snap & RDP patches: applied in new release

gnome-control-center (1:42.1-3) unstable; urgency=medium

  * Cherry-pick patch to fix snap support
  * Enable snap support in the Applications panel

gnome-control-center (1:42.1-2) unstable; urgency=high

  * Add patch to turn off RDP gsettings key when turning off RDP Sharing
    (LP: #1971415)

gnome-control-center (1:42.1-1) unstable; urgency=medium

  * New upstream release
    - Fix On switch for RDP Sharing
  * Drop 4 patches applied in new release

gnome-control-center (1:42.0-3) unstable; urgency=medium

  * Team upload
  * d/p/appdata-Correct-name-of-launchable.patch:
    Add proposed patch to correct name of .desktop file in appdata
  * d/p/debian/Ignore-result-of-test-network-panel.patch:
    Add patch to work around build-time test failure
  * Reorder patch series so patches from upstream come first

gnome-control-center (1:42.0-2) unstable; urgency=medium

  * Team upload

  [ Jeremy Bicha ]
  * Update build-dependencies
  * Revert "Disable colord panel until colord GTK4 client library is available"
  * debian/control.in: Recommend power-profiles-daemon for power mode feature
  * debian/rules: Disable malcontent on Ubuntu: it's not in main there yet
  * d/p/online-accounts-Fix-goa-helper-on-X11.patch:
    Cherry-pick a patch to fix GNOME Online Accounts in Xorg
  * d/p/network-...

[Steve Langasek (vorlon)]

Wouldn't it be better here to have an end-to-end test case that confirms that RDP *works* after toggling this option?

[Jeremy Bícha (jbicha)]

I have updated the Test Case to be more detailed.

[Łukasz Zemczak (sil2100)]

Hello Marco, or anyone else affected,

Accepted gnome-control-center into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-control-center/1:41.7-0ubuntu0.22.04.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Steve Langasek (vorlon)]

Hello Marco, or anyone else affected,

Accepted gnome-control-center into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-control-center/1:41.7-0ubuntu0.22.04.4 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Nathan Teodosio (nteodosio)]

I reproduced the two test cases with 1:41.7-0ubuntu0.22.04.4, but do note that prepending the username in the Remmina address field fails for me. I.e., "jeremy@192.168.1.1" fails, but "192.168.1.1" succeeds.

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-control-center - 1:41.7-0ubuntu0.22.04.4

---------------
gnome-control-center (1:41.7-0ubuntu0.22.04.4) jammy; urgency=medium

  * debian/patches: Read the user value for gedit setting before changing it.
    This is an oversight while backporting the patch that is already in
    kinetic. (LP: #1968213)
  * debian/gbp.conf: Set upstream branch to upstream/42.x

gnome-control-center (1:41.7-0ubuntu0.22.04.3) jammy; urgency=medium

  * debian/control.in: Depend on gnome-remote-desktop (LP: #1980606)

gnome-control-center (1:41.7-0ubuntu0.22.04.2) jammy; urgency=medium

  * debian/patches: Refresh indexes
  * debian/patches: Ensure VNC/RDP remote control setting is honored
    (LP: #1977663)
  * ubuntu-panel: Do not change themes on startup (or on user changes)
    Do not override user themes unless an user has explicitly selected a
    color theme. This applies to both the user theme and the icons, as we
    want a consistent experience. But users could still use tweaks to change
    them.
    At the same time, avoid changing the gedit color scheme if an user
    previously set a non-Yaru theme. (LP: #1968213)

 -- Marco Trevisan (Treviño) <email address hidden> Thu, 11 Aug 2022 16:10:13 -0400

[Brian Murray (brian-murray)]

The verification of the Stable Release Update for gnome-control-center has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.