The bug #2010597 uncovered a problem in the build of the 'evolution' package. The evolution package in the flaptak requires a special build of the evolution-data-server, to have a specific D-Bus prefix used in the container. That's done by: buildopts: rpms: macros: | %_eds_dbus_services_prefix org.gnome.Evolution in the evolution.yaml [1]. The evolution-data-server knows of this variable [2]. I guess, and only guess, that the build re-used a plain build of the evolution-data-server, instead of the one required by the evolution. I do not have a clue where to verify it, I only know that these things work properly. When I enter the container I see the included evolution-source-registry uses D-Bus name `org.gnome.evolution.dataserver.Sources5`, which is wrong, it should use `org.gnome.Evolution.org.gnome.evolution.dataserver.Sources5`. That's causing the trouble in the bug #2010597. This used to work properly in the past. I've no idea when it broke. [1] https://src.fedoraproject.org/flatpaks/evolution//blob/stable/f/evolution.yaml#_27 [2] https://src.fedoraproject.org/rpms/evolution-data-server/blob/f34/f/evolution-data-server.spec#_46
Hm, if I look at the build logs, it looks like the flatpak container build has indeed picked up the evolution-data-server build from flatpak-common. I guess it's because the evolution-data-server build from flatpak-common happened to have a higher release number: evolution-data-server-3.40.4-1.module_f34+12673+4f71ea37 (flatpak-common) evolution-data-server-3.40.4-1.module_f34+12632+5ae7e8f8 (evolution) A quick fix should be to just drop evolution-data-server from flatpak-common to work this around for now. I'm in the process of rebuilding all flatpaks to be based on F35 flatpak runtime and I can take care of this while doing the rebuilds.
https://src.fedoraproject.org/modules/flatpak-common/c/0dda9f95c335dd390f3af4b78179b176461a5d68?branch=f35 I'll update the ticket once the evolution build is done.
> A quick fix should be to just drop evolution-data-server from flatpak-common to work this around for now. Won't that break the other apps, which expect it being available? I think of the GNOME Calendar and such, but I do not know how they build here.
Yeah, we'll have to add it to the manifest for all the other apps that need it -- I'll take care of it.
FEDORA-FLATPAK-2021-c6503004da has been submitted as an update to Fedora 35 Flatpaks. https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2021-c6503004da
FEDORA-FLATPAK-2021-c6503004da has been pushed to the Fedora 35 Flatpaks testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2021-c6503004da See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-FLATPAK-2021-c6503004da has been pushed to the Fedora 35 Flatpaks stable repository. If problem still persists, please make note of it in this bug report.