Bug 2174946

Summary:	Backport screen cast & remote desktop persistence
Product:	Red Hat Enterprise Linux 9	Reporter:	Jonas Ådahl <jadahl>
Component:	xdg-desktop-portal-gnome	Assignee:	Jonas Ådahl <jadahl>
Status:	CLOSED MIGRATED	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.2	CC:	jgrulich, mwest, tpelka
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-18 11:00:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jonas Ådahl 2023-03-02 17:30:58 UTC

xdg-desktop-portal-gnome 42 (and the new enough xdg-desktop-portal) added support for persistent screen cast sessions using restore tokens. Persistent remote desktop session support is planned for a future xdg-desktop-portal-gnome version. Both these should be backported to RHEL9, as it not only allows more stream lined screen sharing experience, it also allows improved ability for automated testing by test suites using the portals together with restore tokens.

Comment 1 Jan Grulich 2023-03-23 09:00:15 UTC

I just checked and we have xdg-desktop-portal in version 1.12.4 in RHEL 9. This version should already have support for stream restoration. We just need xdg-desktop-portal-gnome implementation to match that.

Comment 2 RHEL Program Management 2023-09-18 10:58:18 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 3 RHEL Program Management 2023-09-18 11:00:07 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.