Bug 2050991

Summary:	cannot start flatpaked app with fallback-x11 socket
Product:	Red Hat Enterprise Linux 9	Reporter:	Vladimir Benes <vbenes>
Component:	flatpak	Assignee:	Debarshi Ray <debarshir>
Status:	CLOSED MIGRATED	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	massi.ergosum, 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-15 19:34:09 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 Vladimir Benes 2022-02-05 15:35:02 UTC

Description of problem:
When I switch from Wayland back to X (via gdm menu) I cannot start any app with 
sockets=.*fallback-x11.* 

vbenes@benjoband:~$ flatpak info --show-permissions com.github.tchx84.Flatseal 
[Context]
shared=ipc;
sockets=x11;wayland;fallback-x11;

This is one of those.

Version-Release number of selected component (if applicable):
flatpak-1.10.7-2.el9

How reproducible:
always

Steps to Reproduce:
1. log into GNOME using Wayland session
2. log out into gdm
3. log back in as the same user under X session

Actual results:
cannot run flatpak with fallback-x11 in sockets

Expected results:
should be able to run them anytime

Additional info:

Comment 1 Vladimir Benes 2022-02-05 15:35:42 UTC

The same problem occurs when switching from X to Wayland.

Comment 4 RHEL Program Management 2023-09-15 19:33:09 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 5 RHEL Program Management 2023-09-15 19:34:09 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.