[GH-ISSUE #3662] [Bug] Unable to launch AppFlowy Flatpak - Missing library #1663

Closed
opened 2026-03-23 21:15:39 +00:00 by mirror · 8 comments
Owner

Originally created by @Sharkitty on GitHub (Oct 10, 2023).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/3662

Bug Description

Since the update that just dropped for the flatpak version (0.3.4), AppFlowy won't launch anymore. Nothing happens, just the wobbling icon to say it's loading and nothing appears. If I launch it from the command line (flatpak run io.appflowy.AppFlowy), all I get is this error:

AppFlowy: error while loading shared libraries: libnotify.so.4: cannot open shared object file: No such file or directory

If I rollback to the previous version it works again.

How to Reproduce

  • Update AppFlowy flatpak to 0.3.4.
  • Launch it, it should fail to launch.

Expected Behavior

AppFlowy should successfully launch.

Operating System

Fedora-KDE 38

AppFlowy Version(s)

0.3.4 (Flatpak)

Screenshots

No response

Additional Context

No response

Originally created by @Sharkitty on GitHub (Oct 10, 2023). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/3662 ### Bug Description Since the update that just dropped for the flatpak version (`0.3.4`), AppFlowy won't launch anymore. Nothing happens, just the wobbling icon to say it's loading and nothing appears. If I launch it from the command line (`flatpak run io.appflowy.AppFlowy`), all I get is this error: ``` AppFlowy: error while loading shared libraries: libnotify.so.4: cannot open shared object file: No such file or directory ``` If I rollback to the previous version it works again. ### How to Reproduce - Update AppFlowy flatpak to `0.3.4`. - Launch it, it should fail to launch. ### Expected Behavior AppFlowy should successfully launch. ### Operating System Fedora-KDE 38 ### AppFlowy Version(s) `0.3.4` (Flatpak) ### Screenshots _No response_ ### Additional Context _No response_
Author
Owner

@ghost commented on GitHub (Oct 10, 2023):

I have the same issue, when attempting to launch the software from the terminal, I get the same error. Fedora 38 Workstation Edition.

<!-- gh-comment-id:1755526885 --> @ghost commented on GitHub (Oct 10, 2023): I have the same issue, when attempting to launch the software from the terminal, I get the same error. Fedora 38 Workstation Edition.
Author
Owner

@LucasXu0 commented on GitHub (Oct 10, 2023):

@HatWearingMann @Sharkitty

Please try to install the libnotify manually.

sudo apt-get install libnotify4

or

sudo dnf install libnotify

And I have updated the version to 0.3.5. It should be available on Flathub tomorrow.

<!-- gh-comment-id:1755540984 --> @LucasXu0 commented on GitHub (Oct 10, 2023): @HatWearingMann @Sharkitty Please try to install the libnotify manually. `sudo apt-get install libnotify4` or `sudo dnf install libnotify` And I have updated the version to 0.3.5. It should be available on Flathub tomorrow.
Author
Owner

@Sharkitty commented on GitHub (Oct 10, 2023):

@HatWearingMann @Sharkitty

Please try to install the libnotify manually.

sudo apt-get install libnotify4

or

sudo dnf install libnotify

And I have updated the version to 0.3.5. It should be available on Flathub tomorrow.

This shouldn't be required to run a flatpak. The whole point of this packaging format is to resolve dependencies separately from the system.

<!-- gh-comment-id:1755603468 --> @Sharkitty commented on GitHub (Oct 10, 2023): > @HatWearingMann @Sharkitty > > Please try to install the libnotify manually. > > `sudo apt-get install libnotify4` > > or > > `sudo dnf install libnotify` > > And I have updated the version to 0.3.5. It should be available on Flathub tomorrow. This shouldn't be required to run a flatpak. The whole point of this packaging format is to resolve dependencies separately from the system.
Author
Owner

@Sharkitty commented on GitHub (Oct 10, 2023):

I checked and libnotify was already installed on my system.

<!-- gh-comment-id:1755608508 --> @Sharkitty commented on GitHub (Oct 10, 2023): I checked and `libnotify` was already installed on my system.
Author
Owner

@shanlalit commented on GitHub (Oct 10, 2023):

Same here running on Pop OS 22. Running version 0.3.4

❯ flatpak run io.appflowy.AppFlowy
AppFlowy: error while loading shared libraries: libnotify.so.4: cannot open shared object file: No such file or directory

❯ sudo apt-get install libnotify4
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
libnotify4 is already the newest version (0.7.9-3ubuntu5.22.04.1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

<!-- gh-comment-id:1755775502 --> @shanlalit commented on GitHub (Oct 10, 2023): Same here running on Pop OS 22. Running version 0.3.4 ❯ flatpak run io.appflowy.AppFlowy AppFlowy: error while loading shared libraries: libnotify.so.4: cannot open shared object file: No such file or directory ❯ sudo apt-get install libnotify4 Reading package lists... Done Building dependency tree... Done Reading state information... Done libnotify4 is already the newest version (0.7.9-3ubuntu5.22.04.1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Author
Owner

@ghost commented on GitHub (Oct 10, 2023):

Works again after update.

<!-- gh-comment-id:1756079732 --> @ghost commented on GitHub (Oct 10, 2023): Works again after update.
Author
Owner

@Sharkitty commented on GitHub (Oct 10, 2023):

Works for me as well with 0.3.5. Thanks a lot for the fast fix 😸

<!-- gh-comment-id:1756101797 --> @Sharkitty commented on GitHub (Oct 10, 2023): Works for me as well with `0.3.5`. Thanks a lot for the fast fix :smile_cat:
Author
Owner

@LucasXu0 commented on GitHub (Oct 11, 2023):

This shouldn't be required to run a flatpak. The whole point of this packaging format is to resolve dependencies separately from the system.

Agreed. So I added libnotify4 as a dependency in flatpak.yml.

<!-- gh-comment-id:1756606498 --> @LucasXu0 commented on GitHub (Oct 11, 2023): > This shouldn't be required to run a flatpak. The whole point of this packaging format is to resolve dependencies separately from the system. Agreed. So I added `libnotify4` as a dependency in flatpak.yml.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AppFlowy-IO/AppFlowy#1663
No description provided.