This bug was fixed in the package gnome-remote-desktop - 42.1.1-2ubuntu1
---------------
gnome-remote-desktop (42.1.1-2ubuntu1) kinetic; urgency=medium
* Merge with Debian. Remaining change:
- Lower gnome-control-center dependency to 41
gnome-remote-desktop (42.1.1-2) unstable; urgency=high
* Don't automatically enable the systemd user service (LP: #1973028)
* Add postinst to remove the automatic enabling of the user service
* debian/control: Lower mutter dependency so that these fixes reach
Testing sooner
gnome-remote-desktop (42.1.1-1) unstable; urgency=medium
* New upstream release (LP: #1970662)
- Fixes black screen with virtio on qemu (LP: #1971195)
* Drop all patches: applied in new release
* Depend on libmutter instead of gnome-shell | budgie-desktop
- This is a more accurate dependency
* Require libmutter 42.1 for Nvidia fixes
* Depend on fuse3 (Closes: #998846) (LP: #1970411)
-- Jeremy Bicha <[email protected]> Thu, 12 May 2022 15:21:47 -0400
** Changed in: gnome-remote-desktop (Ubuntu)
Status: Triaged => Fix Released
--
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/1970662
Title:
Update gnome-remote-desktop to 42.1.1
Status in gnome-remote-desktop package in Ubuntu:
Fix Released
Status in gnome-remote-desktop source package in Jammy:
Triaged
Bug description:
NOTE
====
This adds a dependency on mutter 42.1 so mutter 42.1 needs to reach
jammy-updates (and I assume fully phased) before we let this update in to
jammy-updates.
Impact
------
TODO
Test Case
--------
TODO
What Could Go Wrong
-------------------
TODO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970662/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
