Bug 2181827 - org.fedoraproject.Platform update breaks org.gnome.Calendar by removing libwebkit2gtk-5.0.so.0
Summary: org.fedoraproject.Platform update breaks org.gnome.Calendar by removing libwe...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-calendar
Version: 37
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kalev Lember
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-26 11:00 UTC by Max Bruckner
Modified: 2023-03-27 03:21 UTC (History)
8 users (show)

Fixed In Version: gnome-calendar-stable-3720230326202254.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-03-27 03:21:50 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Max Bruckner 2023-03-26 11:00:22 UTC
I probably didn't set the "Component" field of the bug properly, but didn't find any relevant component for the org.fedoraproject.Platform runtime.

Description of problem:
On Fedora Silverblue 37, GNOME calendar doesn't start up anymore because org.fedoraproject.Platform is missing libwebkitgtk-5.0.so.0

Version-Release number of selected component (if applicable):

GNOME Calendar:
> $ flatpak info org.gnome.Calendar
> 
> Calendar - Calendar for GNOME
> 
>           ID: org.gnome.Calendar
>          Ref: app/org.gnome.Calendar/x86_64/stable
>         Arch: x86_64
>       Branch: stable
>      Version: 43.1
>      License: GPL-3.0-or-later
>       Origin: fedora
>   Collection: 
> Installation: system
>    Installed: 73.4 MB
>      Runtime: org.fedoraproject.Platform/x86_64/f37
>          Sdk: org.fedoraproject.Sdk/x86_64/f37
> 
>       Commit: 2facc2ac50627d747ab052a756bcf3cf62ce32a845905ae4b1b73bcb657b902a
>      Subject: Export org.gnome.Calendar
>         Date: 2023-02-15 16:35:52 +0000
>       Alt-id: 8f6397fc9c64cf57ca1591ae3a8d99affe7c79e814cc2fb24d5b49b7fe0f20d0

Fedora Platform runtime:
> $ flatpak info org.fedoraproject.Platform
> 
> Fedora Platform - Shared libraries
> 
>           ID: org.fedoraproject.Platform
>          Ref: runtime/org.fedoraproject.Platform/x86_64/f37
>         Arch: x86_64
>       Branch: f37
>      Version: 37
>      License: GPL-2.0-or-later
>       Origin: fedora
> Installation: system
>    Installed: 2.6 GB
> 
>       Commit: b1733e6a3f1bcc24d767f34c8ebe66a1674a8af6e6be73ecd05ddd56ead38c7a
>      Subject: build of runtime/org.fedoraproject.Platform/x86_64/f37
>         Date: 2023-03-22 20:23:48 +0000
>       Alt-id: 1493e3d186a8dfc8a504bcaf54cf6f1a1c1eb96848142799da1f49815d8ae46a


How reproducible:
Happens every time

Steps to Reproduce:
1. flatpak install org.gnome.Calendar
2. flatpak run org.gnome.Calendar

Actual results:
> $ flatpak run org.gnome.Calendar 
> gnome-calendar: error while loading shared libraries: libwebkit2gtk-5.0.so.0: cannot open shared object file: No such file or directory


Expected results:
Should have started GNOME Calendar

Additional info:
This commit is probably the culprit: https://src.fedoraproject.org/flatpaks/flatpak-runtime/c/251ebc4978420b667181891d73f82122cd5b7cdc?branch=f37

Comment 1 Kalev Lember 2023-03-26 17:42:28 UTC
Thanks for filing the issue! I'll get gnome-calendar and the other affected apps (bijiben, evolution, gnome-contacts) rebuilt shorly.

Comment 2 Fedora Update System 2023-03-26 21:10:08 UTC
FEDORA-FLATPAK-2023-b42983e8e6 has been submitted as an update to Fedora 37 Flatpaks. https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2023-b42983e8e6

Comment 3 Kalev Lember 2023-03-26 21:12:48 UTC
OK, that should be fixed with the linked update that rebuilds the affected flatpaks against new webkitgtk 6.0. Would be good if someone could test it and +1 it in the Bodhi system so that it can go to stable as quickly as possible.

Comment 4 Fedora Update System 2023-03-27 03:21:50 UTC
FEDORA-FLATPAK-2023-b42983e8e6 has been pushed to the Fedora 37 Flatpaks stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.