Bug 2330380

Summary:	Missing update of flatpak-spawn causes Evolution to fail on start
Product:	[Fedora] Fedora	Reporter:	nipele.dekisi
Component:	flatpak-xdg-utils	Assignee:	Owen Taylor <otaylor>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	41	CC:	bruce, david.laehnemann, fedhex, gnome-sig, intrep, mark, mcatanza, otaylor
Target Milestone:	---	Keywords:	Upgrades
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-12-14 03:27:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description nipele.dekisi 2024-12-04 16:58:08 UTC

On the Gnome forum I got help about a problem with Evolution after updating the system. The advice there was to Report a bug against flatpak-xdg-utils suggesting two steps:

1. Update flatpak-xdg-utils to 1.0.6
2. Rebuild the F41 Flatpak runtime, which Evolution is using

Quote: "the problem is WebKit is stuck checking the Flatpak portal version but this doesn’t actually reflect the version of flatpak-spawn that is available. Fedora has updated the portal to a new version, but failed to update flatpak-spawn. There’s no easy fix on WebKit’s side."

This leads to my problem with Evolution, where "WebKit is passing --sandbox-a11y-own-name to an older version of flatpak-spawn that doesn’t support it. WebKit is doing a version check in FlatpakLauncher.cpp".

And it would be very great if that could be fixed.

Reproducible: Always

Steps to Reproduce:
1.Check versions:
Evolution 3.54.1 (Flatpak)
Fedora 41
Gnome 47
2.Start Evolution in Terminal via:
flatpak run org.gnome.Evolution
Actual Results:
Evolution is not starting properly, no window appears.

Console output:

~$ flatpak run org.gnome.Evolution

(evolution-alarm-notify:64): Gtk-CRITICAL **: 16:13:03.524: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
flatpak-spawn: Unknown option --sandbox-a11y-own-name=org.gnome.Evolution.Sandboxed.WebProcess-0620af4e-310a-48aa-9d85-9de4c5f1f116
Try "flatpak-spawn --help" for more information.

** (org.gnome.Evolution:57): ERROR **: 16:13:04.354: readPIDFromPeer: Unexpected short read from PID socket
/app/bin/evolution: Line 29: 57 Trace/Breakpoint triggered (Core dump written) /app/bin/evolution.bin "$@"

Expected Results:
There is no error and the Evolution GUI comes up.

Comment 1 Michael Catanzaro 2024-12-05 00:16:19 UTC

Link to discussion: https://discourse.gnome.org/t/how-to-fix-evolution-not-starting-after-update/25389

Comment 2 fedhex 2024-12-05 14:11:34 UTC

The same root cause triggers a crash for the Geary flatpak installed on Silverblue 41; I assume the same would happen for the flatpak installed in the regular workstation edition, but I haven't checked. Also I looked in a Fedora 40 flatpak installation and the same old version of flatpak-spawn is present (1.0.5-6.fc40), the one without the option, so it would seem that Geary or Evolution flatpaks would fail on f40 in the same way.

(I guess that would warrant a bump in this bug's priority/severity now that there are 2 relatively major applications affected across multiple fedora versions/flavors)

Comment 3 david.laehnemann 2024-12-09 12:40:08 UTC

I can confirm, that this bug also affects Fedora 40. I have run the exact same commands as the original poster, and I get the exact same error message, with only timestamps and the WebProcess hash value differing. So I would second the vote for a higher severity.

Comment 4 Fedora Update System 2024-12-09 13:27:56 UTC

FEDORA-2024-6137ee4ecc (flatpak-xdg-utils-1.0.6-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-6137ee4ecc

Comment 5 Fedora Update System 2024-12-09 14:38:19 UTC

FEDORA-FLATPAK-2024-ca717575f5 (flatpak-runtime-f41-16 and flatpak-sdk-f41-13) has been submitted as an update to Fedora 41 Flatpaks.
https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2024-ca717575f5

Comment 6 Fedora Update System 2024-12-10 01:29:04 UTC

FEDORA-FLATPAK-2024-ca717575f5 has been pushed to the Fedora 41 Flatpaks testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2024-ca717575f5

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2024-12-10 02:03:17 UTC

FEDORA-2024-6137ee4ecc has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-6137ee4ecc`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-6137ee4ecc

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2024-12-11 02:47:02 UTC

FEDORA-FLATPAK-2024-947f40556a has been pushed to the Fedora 41 Flatpaks testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2024-947f40556a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2024-12-14 03:27:27 UTC

FEDORA-FLATPAK-2024-947f40556a (flatpak-runtime-f41-17 and flatpak-sdk-f41-14) has been pushed to the Fedora 41 Flatpaks stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2024-12-19 04:06:58 UTC

FEDORA-2024-6137ee4ecc (flatpak-xdg-utils-1.0.6-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Debarshi Ray 2025-11-12 16:41:30 UTC

*** Bug 2330602 has been marked as a duplicate of this bug. ***