1. Introduction §
I recently wanted to improve Qubes OS accessibility to new users a bit, yesterday I found why GNOME Software wasn't working in the offline templates.
Today, I'll explain how to install programs from Flatpak in a template to provide to other qubes. I really like flatpak as it provides extra security features and a lot of software choice, and all the data created by Flatpak packaged software are compartmentalized into their own tree in
2. Setup §
All the commands in this guide are meant to be run in a Fedora or Debian template as root.
In order to add Flathub repository, you need to define the variable
https_proxy so flatpak can figure how to reach the repository through the proxy:
export https_proxy=http://127.0.0.1:8082/ flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
Make the environment variable persistent for the user
user, this will allow GNOME Software to work with flatpak and all flatpak commands line to automatically pick the proxy.
mkdir -p /home/user/.config/environment.d/ cat <<EOF >/home/user/.config/environment.d/proxy.conf https_proxy=http://127.0.0.1:8082/ EOF
In order to circumvent a GNOME Software bug, if you want to use it to install packages (Flatpak or not), you need to add the following line to
ip route add default via 127.0.0.2
Restart the template, GNOME software is now able to install flatpak programs!
3. Qubes OS integration §
If you install or remove flatpak programs, either from the command line or with the Software application, you certainly want them to be easily available to add in the qubes menus.
Here is a script to automatically keep the applications list in sync every time a change is made to the flatpak applications.
3.1. Inotify-tool §
For the setup to work, you will have to install the package
inotify-tools in the template, this will be used to monitor changes in a flatpak directory.
3.2. Syncing app menu script §
#!/bin/sh # when a desktop file is created/removed # - links flatpak .desktop in /usr/share/applications # - remove outdated entries of programs that were removed # - sync the menu with dom0 inotifywait -m -r \ -e create,delete,close_write \ /var/lib/flatpak/exports/share/applications/ | while IFS=':' read event do find /var/lib/flatpak/exports/share/applications/ -type l -name "*.desktop" | while read line do ln -s "$line" /usr/share/applications/ done find /usr/share/applications/ -xtype l -delete /etc/qubes/post-install.d/10-qubes-core-agent-appmenus.sh done
You have to mark this file as executable with
chmod +x /usr/local/sbin/sync-app.sh.
3.3. Start the file monitoring script at boot §
Finally, you need to activate the script created above when the templates boots, this can be done by adding this snippet to
# start monitoring flatpak changes to reload icons /usr/local/sbin/sync-app.sh &
3.4. Updating §
This solution will look for flatpak programs updates each time the template starts, which should occur regularly to update the template packages, and update them unconditionnaly.
Add this snippet to
# check for update export https_proxy=http://127.0.0.1:8082/ flatpak upgrade -y --noninteractive
This could be enhanced by asking the user if they want to update or skip for later, but I still have to figure how to make
notify-send from the root user, I opened a Qubes OS issue about this.
4. Conclusion §
With this setup, you can finally install programs from flatpak in a template to provide it to other qubes, with bells and whistles to not have to worry about creating desktop files or keeping them up to date.
Please note that while well-made Flatpak programs like Firefox will add extra security, the repository flathub allows anyone to publish programs. You can browse flathub to see who is publishing which software, they may be the official project team (like Mozilla for Firefox) or some random people.