# Flatpak **URL:** \ **Category:** Uncategorized\ **Created:** [April 15, 2019, 7:25pm UTC](https://quelea.discourse.group/t/flatpak/25 "2019-04-15T19:25:12Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![arakan94](https://yyz2.discourse-cdn.com/free1/user_avatar/quelea.discourse.group/arakan94/32/17_2.png) [@arakan94](https://quelea.discourse.group/u/arakan94)\ **Post date:** [April 15, 2019, 7:25pm UTC](https://quelea.discourse.group/t/flatpak/25/1 "2019-04-15T19:25:12Z")
Hi, I noticed that you now distribute as snap… Are you considering supporting Flatpak as well? It’s a lot more used IMHO and having both Snap and Flatpak would likely cover most Linux distros. ---
**Author:** ![berry120](https://yyz2.discourse-cdn.com/free1/user_avatar/quelea.discourse.group/berry120/32/4_2.png) [@berry120](https://quelea.discourse.group/u/berry120)\ **Post date:** [April 16, 2019, 7:46am UTC](https://quelea.discourse.group/t/flatpak/25/2 "2019-04-16T07:46:34Z")
Hey, thanks for signing up! Flatpak isn’t on our radar at the moment but I’m certainly not against supporting it in the future if it seems viable. Feel free to create a GitHub issue so we don’t lose track of it 🙂 ---
**Author:** ![mikefreeman1972](https://yyz2.discourse-cdn.com/free1/user_avatar/quelea.discourse.group/mikefreeman1972/32/111_2.png) [@mikefreeman1972](https://quelea.discourse.group/u/mikefreeman1972)\ **Post date:** [September 26, 2024, 11:32pm UTC](https://quelea.discourse.group/t/flatpak/25/3 "2024-09-26T23:32:46Z")
Hey there! I’ve been out of the loop with Quelea for quite a while, but I thought I’d come back and see how development has gone since last I used the program. So, I went to install it. I see there are no longer .deb files for Linux. I get that, as I remember you being very Ubuntu-centric back then as well. I see only Snap and crossplatform .jar available. Snap: I’m using Linux Mint, which can technically use Snap, but I avoid that thing like the plague, because when I took the snapd block off of a previous Linux Mint install, it messed with my system and things got really slow. On my current system, I refuse to remove the snapd block. So Snap is a no-go for me. I refuse to use the thing. Cross-platform: Trying out the crossplatform .jar installer, it says that it requires Java 8, and requires it to be the default Java. This messes with another program I have installed that needs a newer Java version to be default. I tried it without Java 8, but obviously it didn’t work. So, I can’t use this installer, either. I see that Flatpak has been requested here and on Github. If my opinion counts for anything (which I admit it probably doesn’t), I also vote for a Flatpak package. Snap, as noted above, is very much Ubuntu-centric, and many more security/FOSS-focused Linux distros either can’t use, disable, or won’t allow snapd because of its proprietary nature on Ubuntu’s Snap servers. Because of this, Flatpak is a much more widely adopted Linux standard than Snap is, and is also available for Ubuntu, so your Ubuntu folks can still be just as well-supported. Using Flatpak would bring many more users to the table. Even AppImage would be more generally usable than Snap. Again, this is just my own opinion. For now, until something more easily usable for my system is made available, I’ll just pass on Quelea this time around, and wish you guys the best of luck and God’s blessings on your project! ---
**Author:** ![DeeTigIT](https://avatars.discourse-cdn.com/v4/letter/d/74df32/32.png) [@DeeTigIT](https://quelea.discourse.group/u/DeeTigIT)\ **Post date:** [September 27, 2024, 8:00pm UTC](https://quelea.discourse.group/t/flatpak/25/4 "2024-09-27T20:00:11Z")
With respect to the crossplatform version: - Quelea-2020.0 : jre-8 - Quelea-2021.0 : jre-8 - Quelea-2022.0 : jre-11, jre-21 - Quelea-2024.0 : jre-11, jre-21 On my debian test system I have installed all these Quelea cross-platform versions and jre versions. I start Quelea, with the required jre, using a .sh with essentialy the following statements (in this case: Quelea 2024.0 running with zulu jre-21): 1. sudo update-alternatives --set java /usr/lib/jvm/zulu-fx-21-amd64/bin/java 2. cd /usr/local/Quelea-2024.0/ 3. java --add-exports=javafx.graphics/com.sun.javafx.css=ALL-UNNAMED --add-exports=javafx.base/com.sun.javafx.runtime=ALL-UNNAMED --add-exports=javafx.base/com.sun.javafx.event=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens javafx.controls/javafx.scene.control=ALL-UNNAMED -Dfile.encoding=UTF-8 -Dprism.dirtyopts=false -jar Quelea.jar 4. sudo update-alternatives --auto java Blessings, DeeTigIT ---
**Author:** ![Ebbez](https://avatars.discourse-cdn.com/v4/letter/e/f07891/32.png) [@Ebbez](https://quelea.discourse.group/u/Ebbez)\ **Post date:** [April 16, 2025, 1:19pm UTC](https://quelea.discourse.group/t/flatpak/25/5 "2025-04-16T13:19:53Z")
I’ve just created a prototype Flatpak and submitted a PR request to change the CI/app build to enable Flatpaks to be submitted to Flathub. > > > Hi everyone, > > I've worked these last couple of days on making a Flatpak versio…n. The Flatpak build scripts needs an archive/tarball of the Quelea application (\`dist/\`) with the Quelea.jar in it, so I had to tweak a couple of things with the build. > > To build the Flatpak you need to have Flatpak installed, and run the following commands: > > \## 1. Retrieve the Flatpak manifest > > \`\`\` > $ wget https://raw.githubusercontent.com/ebbez/Quelea/refs/heads/master/flatpak/org.quelea.Quelea.yml > \`\`\` > or > \`\`\` > $ git clone https://github.com/ebbez/Quelea.git > $ cd flatpak > \`\`\` > > \## 2. Build the Flatpak > > (instructions derived from: https://docs.flatpak.org/en/latest/first-build.html) > > \`\`\` > $ flatpak remote-add --if-not-exists --user flathub https://dl.flathub.org/repo/flathub.flatpakrepo > $ flatpak-builder --force-clean --user --install-deps-from=flathub --repo=repo --install builddir org.quelea.Quelea.yml > \`\`\` > > \## 3. Start the Flatpak > > ~~Ideally it would create a launcher, and I have included the .desktop file, but I still need to figure out how to make Flatpak add it to the menu. For now, you can start it with the command~~ > > It now creates a launcher/add the .desktop file to your launcher, but if you can't see the launcher you can run: > > \`\`\` > $ flatpak run org.quelea.Quelea > \`\`\` > > \# Optimizations > > There were also some issues I noticed, such as: > > \* The Wine in my GitHub Actions wouldn't work, so I switched compilation of the Windows standalone to a Windows GitHub Runner. If this is not good, I can try to change it back so the CI runs on one GH Runner only. (https://github.com/Operese/innosetup-cross-action seems interesting) > \* \[The \`upload-release-action\` is now looking for a new maintainer\](https://github.com/svenstaro/upload-release-action/issues/135) and as such it might be unsupported in the future, so I switched the release action to \[a more actively developed/maintained action\](https://github.com/softprops/action-gh-release). > \* Downloading and installing Java manually might be annoying to maintain, so I switched to a GitHub official \`actions/setup-java\` action. > \* The \`lib/\` contained JavaFX libraries/jars, while the clients already get a version of JavaFX that comes with the bundled JDK. I excluded \`javafx\*\` from the \`libs/\`. For the izpack installer, Gradle build will create a \`libfx\` folder with the javafx libraries included. Should result in reduced standalone sizes. > \* The clients only need to execute, so I guess just a JRE would suffice. Changed the JDKs into JRE's (still with the FX libs included and by Azul) which should result in reduced standalone sizes. > \* JavaFX \<= 23 has an issue where maximized windows will shrink to half the screen's size when opening dialogs on Linux (/Wayland). This is fixed in JavaFX 24, so I used a JRE w/ FX 24 from Azul for the Flatpak, which fixes the issue and seems to run fine. Might need more testing though. I also tested this against version 21 from Azul but the bugfix hasn't been backported. This PR only uses JDK/JFX 24 for the Flatpak. > > \# Does it work? > > I've only tested the Windows and Flatpak versions of Quelea. The applications open, but I haven't tested running a full service/schedule in it. The Flatpak version does project correctly. I haven't changed the existing versions too much so I don't think there'll be an introduction of bugs there, unless the already-existing versions rely on the JavaFX libraries in \`libs/\` You could follow the instructions in my PR if you want to run the Flatpak now, but this isn’t an official method yet, and will require some technical knowledge. If you don’t understand/can’t audit the Flatpak manifest, I wouldn’t recommend building it, and would recommend to wait until it _might_ be published to Flathub. ---
**Author:** ![JessyJP](https://yyz2.discourse-cdn.com/free1/user_avatar/quelea.discourse.group/jessyjp/32/292_2.png) [@JessyJP](https://quelea.discourse.group/u/JessyJP)\ **Post date:** [April 16, 2025, 2:35pm UTC](https://quelea.discourse.group/t/flatpak/25/6 "2025-04-16T14:35:32Z")
Why don’t you have a look at my fork. I would be interestested in a distribution. Realistically don’t expect much from the upstream. There is no response from the main dev anyway. At least i am doing active development at the moment. > [@Checkout this Quelea expansion pack build with Improvements and experimental features!](https://quelea.discourse.group/t/checkout-this-quelea-expansion-pack-build-with-improvements-and-experimental-features/1162/24): > > Well i really went overboard this time. What you are seeing is a service process manager. And in white. I think it looks better in white actually. … anyway So: Essentially, it includes or supersede the original init which is just a single sequence. (main method) Can seed-up startup. Now we can don’t need a predefined sequence but can allowed automatic initialization in parallel based on dependency tree. Cool! Any one that knows anything might think Docker or SystemD … ---
**Author:** ![Ebbez](https://avatars.discourse-cdn.com/v4/letter/e/f07891/32.png) [@Ebbez](https://quelea.discourse.group/u/Ebbez)\ **Post date:** [April 17, 2025, 11:31am UTC](https://quelea.discourse.group/t/flatpak/25/7 "2025-04-17T11:31:28Z")
Hi Jessy, thanks for the offer. Cool features! 😃 I admire how much work you’ve put in and engage in the community, but for now I’ll stick to Quelea since I don’t necessarily need them and wish to get Official Quelea to a more stable place. It’d be cool if the stable release of Quelea had a plugin system where you could plug your additions in. I do agree the development of Quelea has slowed down a lot, but I haven’t found it to be completely abandoned. I did see Berry pulled/merged a PR this/last week, so I’m a little hopeful, and of course, this isn’t his job, so I dont mind waiting a few weeks. I do think maybe the core maintainer team could be expanded a little bit? 2/4 maintainers listed on the quelea-projection Github Team seem to be completely inactive in Github the last couple of years, and Berry is the only one that has continued to work on the project at intervals. Arvid also hasn’t been actively engaged in the project in the last couple of years. ---
**Author:** ![JessyJP](https://yyz2.discourse-cdn.com/free1/user_avatar/quelea.discourse.group/jessyjp/32/292_2.png) [@JessyJP](https://quelea.discourse.group/u/JessyJP)\ **Post date:** [April 17, 2025, 12:47pm UTC](https://quelea.discourse.group/t/flatpak/25/8 "2025-04-17T12:47:13Z")
I understand your intention, but I do have to note that “as slowed down a lot” is a significant understatement given a memory leak size of the Atlantic ocean has been hanging around for more than a year. Regarding “It’d be cool if the stable release of Quelea had a plugin system where you could plug your additions in.” well, I already have that (90% there probably) but don’t have plugins to test with. If you are actually interested in that, it can be discussed. Generally a well defined, convenient API (context) would be needed. The RChandler can sort of be used but it needs to be split into API handler and http handler to make it work properly. As for the merge last week, I am not as optimistic as you. Where I am from we have a saying that one bird doesn’t make it spring. It’s his project with 90% being his code and 1 significant contributor, there is no team. It’s just him and everything it’s up to him. ![GitBlame Stats for current main branch (src & server dirs)](https://global.discourse-cdn.com/free1/uploads/quelea/original/1X/1eb9b51ed87f24d7f79175ace31c3856a784b641.png) Naturally, if as you say, he does an update for this year, great! That’s also good for me, I can merge, it’s fantastic. But … after numerous messages, posts, emails, he remains mostly MIA. Of course no one would blame him if his priorities changed. That’s normal life. What is frustrating though, is that there was no announcement of any kind, or maybe a provision for someone to take over for him, or partner with him. In this situation what the community really needed was a clear statement of what the intentions for the next one year or so are. Then again, I really do hope you are right. Of course that would be ideal. ---
**Author:** ![JessyJP](https://yyz2.discourse-cdn.com/free1/user_avatar/quelea.discourse.group/jessyjp/32/292_2.png) [@JessyJP](https://quelea.discourse.group/u/JessyJP)\ **Post date:** [April 17, 2025, 12:48pm UTC](https://quelea.discourse.group/t/flatpak/25/9 "2025-04-17T12:48:34Z")
P.S. I am pretty much compatible with upstream. Consider making the same MR to my fork as well if nothing happens in a few weeks. ---
**Author:** ![Ebbez](https://avatars.discourse-cdn.com/v4/letter/e/f07891/32.png) [@Ebbez](https://quelea.discourse.group/u/Ebbez)\ **Post date:** [April 17, 2025, 1:01pm UTC](https://quelea.discourse.group/t/flatpak/25/10 "2025-04-17T13:01:59Z")
Yep I’ll definitely keep it in mind! ---
**Author:** ![DeeTigIT](https://avatars.discourse-cdn.com/v4/letter/d/74df32/32.png) [@DeeTigIT](https://quelea.discourse.group/u/DeeTigIT)\ **Post date:** [May 11, 2025, 11:53am UTC](https://quelea.discourse.group/t/flatpak/25/11 "2025-05-11T11:53:56Z")
@Ebbez: is sound already working in the Flatpak Quelea? See also my remarks on this at : > > > Hi Michael, > > I am submitting a standalone Flatpak manifest to Flathub: > https://g…ithub.com/flathub/flathub/pull/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 ---
**Author:** ![Ebbez](https://avatars.discourse-cdn.com/v4/letter/e/f07891/32.png) [@Ebbez](https://quelea.discourse.group/u/Ebbez)\ **Post date:** [May 11, 2025, 2:10pm UTC](https://quelea.discourse.group/t/flatpak/25/13 "2025-05-11T14:10:22Z")
I have submitted an update to fix the audio. The manifest file was missing audio permissions so the Flatpak couldn’t access the audio service (pulseaudio). It might take a little longer to be published because such permission updates are usually held back for manual review. ---
**Author:** ![Ebbez](https://avatars.discourse-cdn.com/v4/letter/e/f07891/32.png) [@Ebbez](https://quelea.discourse.group/u/Ebbez)\ **Post date:** [May 11, 2025, 3:30pm UTC](https://quelea.discourse.group/t/flatpak/25/14 "2025-05-11T15:30:45Z")
Audio fix update is now published on Flathub.