barthalion: > I did not notify you as it had no commits for almost half a year, so I assumed it’s not actively maintained. This kind of behaviour certainly does not make me want to maintain **anything**. Next time, send an e-mail.

Unfortunately, allowing a `.Devel` app set an inconvenient precedent, and it tends to be used as an argument for hosting development releases of apps on Flathub. I did not notify you as it had no commits for almost half a year, so I assumed it’s not actively maintained. I recommend using the `beta` branch of regular Totem or the `gnome-nightly` repo hosted by GNOME.

I was very surprised today when I opened this page to see that the repo had been archived without so much as a warning. Could somebody please unarchive it? Thanks github.com ### GitHub - flathub/org.gnome.Totem.Devel Contribute to flathub/org.gnome.Totem.Devel development by creating an account on GitHub.

It is almost a year since the switch to Vorarbeiter for building and publishing apps. We've made several improvements since then, and it's time to brag about them. ## RunsOn​ In the initial announcement, I mentioned we were using RunsOn, a just-in-time runner provisioning system, to build large apps such as Chromium. Since then, we have fully switched to RunsOn for all builds. Free GitHub runners available to open source projects are heavily overloaded and there are limits on how many concurrent builds can run at a time. With RunsOn, we can request an arbitrary number of threads, memory and disk space, for less than if we were to use paid GitHub runners. We also rely more on spot instances, which are even cheaper than the usual on demand machines. The downside is that jobs sometimes get interrupted. To avoid spending too much time on retry ping-pong, builds retried with the special `bot, retry` command use the on-demand instances from the get-go. The same catch applies to large builds, which are unlikely to finish in time before spot instances are reclaimed. The cost breakdown since May 2025 is as follows: Once again, we are not actually paying for anything thanks to the AWS credits for open source projects program. Thank you RunsOn team and AWS for making this possible! ## Caching​ Vorarbeiter now supports caching downloads and ccache files between builds. Everything is an OCI image if you are feeling brave enough, and so we are storing the per-app cache with ORAS in GitHub Container Registry. This is especially useful for cosmetic rebuilds and minor version bumps, where most of the source code remains the same. Your mileage may vary for anything more complex. ## End-of-life without rebuilding​ One of the Buildbot limitations was that it was difficult to retrofit pull requests marking apps as end-of-life without rebuilding them. Flat-manager itself exposes an API call for this since 2019 but we could not really use it, as apps had to be in a buildable state only to deprecate them. Vorarbeiter will now detect that a PR modifies only the end-of-life keys in the `flathub.json` file, skip test and regular builds, and directly use the flat-manager API to republish the app with the EOL flag set post-merge. ## Web UI​ GitHub's UI isn't really built for a centralized repository building other repositories. My love-hate relationship with Buildbot made me want to have a similar dashboard for Vorarbeiter. The new web UI uses PicoCSS and HTMX to provide a tidy table of recent builds. It is unlikely to be particularly interesting to end users, but kinkshaming is not nice, okay? I like to know what's being built and now you can too here. ## Reproducible builds​ We have started testing binary reproducibility of x86_64 builds targetting the stable repository. This is possible thanks to flathub-repro-checker, a tool doing the necessary legwork to recreate the build environment and compare the result of the rebuild with what is published on Flathub. While these tests have been running for a while now, we have recently restarted them from scratch after enabling S3 storage for diffoscope artifacts. The current status is on the reproducible builds page. Failures are not currently acted on. When we collect more results, we may start to surface them to app maintainers for investigation. We also don't test direct uploads at the moment. * * * This is a companion discussion topic for the original entry at https://docs.flathub.org/blog/vorarbeiter-2026

The change seems unlikely to have affected anything, but please raise this with GitHub · Where software is built

Duplicate of Raindrop Flatpak Request

Following a ‘refresh’ of Octave 10.3, it now crashed when I try to run a script. Running from a terminal produces the error message “octave exited with signal 4”. Operating System: Kubuntu 24.04 KDE Plasma Version: 5.27.12 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Kernel Version: 6.8.0-90-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 27.3 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0

Current Status: January 11, 2025 **22** apps use GNOME **43** or older versions. **29** apps use Freedesktop **21.08** or older versions. **24** apps use KDE **5.15-21.08** or older versions. **6** apps use KDE **6.4** or older versions.

This has been resolved for some days

Project information: Name: Trilium Homepage: https://triliumnotes.org/ License: AGPL-3.0 license Repo : GitHub - TriliumNext/Trilium: Build your personal knowledge base with Trilium Notes Old version: https://flathub.org/en-GB/apps/com.github.zadam.trilium Old Repo : https://github_com/zadam/trilium (Redirect to New) Upstream has been contacted: yes, they failed to do it, most probably lack of skill. The team is doing really great work updating the project, and they have improved it significantly. They also have a very good looking website and docs, but they lack the skills needed for Flatpak and Flathub. they have working .flatpack file build, it took multiple trail and error to make it work with shortcut and icon. Related issues https://github_com/TriliumNext/Trilium/issues/5108 https://github_com/flathub/flathub/issues/6715 https://github_com/TriliumNext/Trilium/issues/4732 Note: new user can only add 4 links so added _

I turned Apparmor back on to see if that causes any problems or not.

I checked and I saw the app icons for the Tor Browser and the Tor Browser Launcher. I was surprised. I clicked on the Tor Browser icon and it started up OK and it’s now working. So it seems the error didn’t prevent the Tor Browser from getting successfully installed.

alamahant: > Please check if temp stopping it resolves the issue. > > > systemctl stop apparmor > I ran the command and then tried to install TBLA and then got the exact same error. Any ideas how to fix this?

hello i am having an issue where i some flatpak applications i want to run are waking up my 5070m from a d3cold state into d0 increasing power consumption, these are basic electron apps that will run more then fine on my igpu, which i think they are doing. but they keep waking up my dgpu and using flatpak overrides and flatseal to hide /dev/dri block gpus and all devices etc and it still wakes the gpu.

Hi there! First of all: This forum is mostly about Flathub as a platform. If you want advice or help specific to an application, you can find links to app-specific help resources on its app page. I will try to give some pointers here, but if you need more in-depth advice, I recommend using the help resources of the application in question. jkgoose: > […], I’m noticing this program only downloads the java edition from the google app store vs the microsoft bedrock edition. […] By “this program”, I assume you’re referring to the Minecraft Bedrock Launcher? First of all, this is not using a “java edition from the google app store”, since this doesn’t exist. The Java edition is separate, bought on Minecrafts website, and only available on desktop platform (though including Linux natively). The Minecraft you find on the Google Play Store is the Bedrock edition, same as the one found on iOS or in the Microsoft Store. Now, the “Minecraft Bedrock Launcher” is just a small wrapper to make the Android version of Minecraft Bedrock run on Linux. Using the Microsoft Store version would require a wrapper for a Windows version. So its not possible with the current launcher to use a version of Minecraft Bedrock bought on the Microsoft Store. I’d assume you could login with your Microsoft Account in the game itself though, and transferring worlds should be possible by manually copying them.

Project information: Name: Oriedita Homepage: https://oriedita.github.io/ License: MIT Upstream has been contacted: Yes, Flathub release · Issue #500 · oriedita/oriedita · GitHub Oriedita is a origami crease pattern makers, one and only maintained software for this. There’s already Linux version as a Debian package.

Greetings, I’m noticing this program only downloads the java edition from the google app store vs the microsoft bedrock edition. is it possible to use my microsoft account instead of my google account to play my micosoft bedrock worlds? thank you

Project information: Name: friction Homepage: https://friction.graphics/ License: GPL v.3 Upstream has been contacted: no Source code: GitHub - friction2d/friction: Friction Graphics Note: Fork of Enve Current version: Friction 1.0.0-rc.3

I’m developing a GTK4/Libadwaita application, and I’ve noticed that in the flatpak packaged version on Flathub that file permissions granted through the portal file picker don’t persist across system restarts. Because of this, the recent files menu I’ve implemented reverts to an empty state after a system restart, which is undesired. Is this expected behavior, or should portal-granted permissions persist across system restarts? Short of granting the app broad filesystem permissions, are there specific manifest permissions or settings needed to enable permission persistence? Any guidance would be greatly appreciated!

I don’t see what exactly is the issue here. What does the business of the company have to do with the app? Do you have anything specific?

**Hello,** I’m facing a problem with the **Heroic Games Launcher (com.heroicgameslauncher.hgl)** and a game (**Horizon Forbidden West**) running via Wine/Proton. The game uses VKD3D-Proton to cache DX12 shaders. **The Problem:** Every time I exit the game, the shader cache merge process (from `vkd3d-proton.cache.write` to `vkd3d-proton.cache`) seems to fail. I suspect this is because the file descriptor limit (`ulimit -n`) inside the Flatpak sandbox is only **1024**. The process likely needs to open thousands of files to merge the cache and hits this limit. * Proof: `flatpak run --command=sh com.heroicgameslauncher.hgl -c "ulimit -n"` returns **1024**. * Result: The `.write` file is left behind, the main `.cache` doesn’t update, and the game recompiles all shaders from scratch on every launch (taking several minutes). **My Question:** Is there an official or recommended way to **increase this`RLIMIT_NOFILE` for a specific Flatpak application**? **What I’ve tried (unsuccessfully):** 1. Creating a systemd user override for the app’s scope (e.g., `app-flatpak-com.heroicgameslauncher.hgl-*.scope`). This didn’t work because the limit seems to be enforced earlier by the sandbox (`bwrap`). 2. Setting the `WINE_FD_LIMIT=1048576` environment variable inside the sandbox. This does not affect the actual OS-level limit. **Is this the right approach?** Would a `flatpak override` command like the one below work? If so, is there a specific parameter that directly controls the file descriptor limit for the sandboxed process? flatpak override --user com.heroicgameslauncher.hgl --env=WINE_FD_LIMIT=1048576 # (plus other necessary permissions) Or is there another mechanism I should use? If possible, could you provide an example of a working configuration? **System Information:** * Distribution: Fedora Linux 42 (Rawhide) * Flatpak version: `flatpak --version` → **1.16.2** * Affected application: `com.heroicgameslauncher.hgl` Any guidance would be greatly appreciated. This issue severely impacts the usability of demanding DX12 games through Flatpak. Thank you for your help!

It seems that TBLA is trying to invoke ldconfig for some reason.Maybe apparmor is blocking it.Please check if temp stopping it resolves the issue. systemctl stop apparmor

Hi Guys, Best Wishes for 2026. For at least 5+ days download stats are not being updated in the Flathub website. They are being update though on https://klausenbusk.github.io/flathub-stats/#ref=ca._0ldsk00l.Nestopia Are we aware of this issue? Thanks a lot.

I’m trying to install the Tor Browser Launcher app (TBLA) in my Ubuntu 24.04 VM. The host is Tumbleweed on my AMD Ryzen laptop. I went to flathub.org to get the TBLA flatpak and install it. After the TBLA installs I press OPEN and get the following error: openSUSE Paste –> ldconfig failed, exit status 256 How to fix this error? I ran “sudo flatpak -v repair“ but it didn’t help I ran “flatpak update“ and it said “nothing to do”. apparmor is installed and running in the Ubuntu VM.

I search and trace a app owner link, the Heshan Aisipai E-commerce Co. Ltd . It have two apps https://flathub.org/zh-Hans/apps/com.iche2.fileshows and the onther .It is a company with doubtful business，the company link https://www.iche2.com/ is a car news web，without company info,trace china https://beian.miit.gov.cn/#/Integrated/recordQuery search 粤ICP备15095388 ， get http://www.zllhq.com/ a company with Red wine