Submission Flathub

[ebbez]

Hi Michael,

I am submitting a standalone Flatpak manifest to Flathub:
flathub/flathub#6428

This submission will work separately from the PRs, but it is preferred by Flathub for some of the metadata (like logo, MetaInfo, .desktop files) to be managed on and retrieved from the upstream Git repository, and for the upstream to help maintain the app on Flathub (not required/necessary, but preferred/appreciated, so don't feel the need/pressured to do this if you don't want to).

I also included the files mentioned above in #676

[ebbez]

@berry120 Just got confirmation by Flathub that they accepted the submission today.

It'll be available at https://flathub.org/apps/details/org.quelea.Quelea and for all users that use GNOME Software or KDE Discover (GUI app store applications) and have Flatpak installed.

[ebbez]

And the Flatpak repo is on GitHub: flathub/org.quelea.Quelea

[ebbez]

(This is how Linux users can now find it on Fedora KDE for example:)

[DeeTigIT]

First of all: congrats for enabling this! Quelea is listed under New in Flathub:

I am testing it in a Debian running VM.
My observation: sound seems not working, both in videos as wel as audio files.

For comparison I also installed the Strawberry Music Player (SMP) using Flathub and played the same audio file.

With SMP:

• I can hear the sound
• SMP icon on the taskbar has a speaker symbol in the top right corner (ginving access to sound adjustment)

With Quelea:

• I don't hear sound
• the Quelea icon on the tasksbar misses a speaker symbol in the top right corner

Could you please verify this missing audio?

SMP:

Quelea:

[ebbez]

Haha the audio issues just also came to my attention as well, and I had just opened up a PR: #684

The bug is caused by missing audio permissions in the Flatpak manifest (--socket=pulseaudio). I have also just sent in an update to Flathub but it'll probably take an hour to propagate.

For now you can also fix the issue by editing the Flatpak permissions through Flatseal or flatpak-kcm.

[ebbez]

But thanks for reporting it in! I could have missed it for a few more weeks because our church doesn't use video files that much.

[DeeTigIT]

The sound issue has been solved!

Another question arises. The new Quelea Flatpak version was shown as an update in KDE Discover app. I always install all updates shown in Discover (on the assumption they are thoroughly tested).

But how will this work when Quelea CI has been released as official 2025.0 releas.
The Flatpak in 2025.0 is the stable one to use for productio, not a CI Flatpak that is build afterwards.
"CI releases are automatically built from the latest code in this repository, and thus are not fully tested. They should not be used in production settings."

Will there be a separate CI Flatpak version or does the Flatpak version remains the same until a new stable release?

[ebbez]

The current Flathub release is actually a Quelea CI. This is because the Flatpak requires the quelea-VERSION-java-app.tar.gz archive file and this has only been added to the build process since the Quelea Flatpak Prototype PR got merged.

If there are no issues with the current Flathub release I'll just hold back on updating it until the new stable version of Quelea has been released. In the meantime, Flathub also has a 'Beta Repository' where I'll push the CI-releases to.

So, for this period until a new Quelea Stable has come out, I'll keep the current Flathub release on this current CI-release. If any bugs arise from the Flathub release I'll try to fix them either upstream or locally on the Flathub Git repo (https://github.com/flathub/org.quelea.Quelea), which can cause the Flathub release to follow CI. If there are no bugs with the Flathub release, only Flathub Beta will contain the new CI updates.

[ebbez]

Regarding this way of releasing, @berry120 would you also like to get invited to the https://github.com/flathub/org.quelea.Quelea repository? I'll make an issue to the https://github.com/flathub/flathub repository to request them to invite you to that Github repository. You don't necessarily need to maintain it actively (I'm happy to do that), but it'd give you some more control if needed.

I could also revert the Flathub version back to the stable 2024.0 (or 2024.1? I see that version in the changelogs and version updates but it doesn't seem like it has been released).

[berry120]

Yes please - then we can (hopefully) somehow mark it as verified on flathub, too?

…

On Mon, 12 May 2025, 12:12 Ebbe Zeinstra, ***@***.***> wrote: *ebbez* left a comment (quelea-projection/Quelea#682) <#682 (comment)> Regarding this way of releasing, @berry120 <https://github.com/berry120> would you also like to get invited to the https://github.com/flathub/org.quelea.Quelea repository? I'll make an issue to the flathub/flathub repository to request them to add you to that Github repository. I could also revert the Flathub version back to the stable 2024.0 (or 2024.1? I see that version in the changelogs and version updates but it doesn't seem like it has been released). — Reply to this email directly, view it on GitHub <#682 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABZ6JDNUUFSTRY4GUYXKY6L26B6ZXAVCNFSM6AAAAAB34SLUOCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNZSGEYTQMBZG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ebbez]

Yes please - then we can (hopefully) somehow mark it as verified on
flathub, too?

Yes I think it'll make it easier to do, but I believe there are some extra steps like logging in to the Flathub dev portal, retrieving the app token, and then adding that token to quelea.org/.well-known/org.flathub.VerifiedApps.txt like it describes in the docs here:

https://docs.flathub.org/docs/for-app-authors/verification#im-publishing-an-app-on-flathub-how-do-i-get-it-verified

[berry120]

That should be easy enough when I'm added so I can retrieve the token 👍

[ebbez]

BTW, I stated before in this issue:

This (Flathub) submission will work separately from the PRs,

But eventually I found out it couldn't work due to a Git LFS file missing on Github (I believe the path was tests/newdatabase/...db).

My original submission manifest built Quelea with Gradle separately, and used the Git repository as a source.

My computer didn't have Git LFS installed, so it didn't throw the LFS error when I test-built the flatpak, but the Flathub build servers do, and because they require all Git history be downloaded, it threw an error when it couldn't find the LFS file referenced in a commit from long ago. That's why I changed back to using the compiled .tar.gz file from the CI-release.

(And in the original submission to build separately I used https://github.com/jwharm/flatpak-gradle-generator to generate the list of sources from the dependencies listed in Gradle, since the Flathub build process doesn't allow network connections during the build-commands execution, so any sources used for built need to be statically defined in the flatpak manifest)