Search for a command to run...
I define myself as a generalist software developer, focusing mostly on web and linux tech. I am also an engineering student in Turkey.
My main goal on this blog is to share my hard-earned findings to 'problems' I've faced along my journey. It covers anything from new JS framework to fixing DNS issues.
This is a very helpful guide, thank you for writing it 😁
Regarding the custom desktop entry, Flatpak doesn't always put it under ~/.local/share/flatpak/exports/...
For me, it was under var/lib/flatpak/exports/share/applications (just like the first proposed solution in the flatpak repo issue).
BTRFS is a modern filesystem that supports features like COW (Copy-on-Write) and instant snapshots. It is more performant and space efficient than ext4 and others. It's on par with ZFS. There are a couple things you should do and not do after setting...
New Year New Domain 2022 is over, for good. It has been a year of challenges for me. I achieved some things I've wanted to but the feeling of not being enough is always there. What we can do for this is to just take in the feeling and keep growing. I...
A very short review of motherf**king websites and why I want to make the web better
How to get unstuck, solve problems and stay healthy as a developer
On this page
In this guide you will learn how to launch flatpak applications with custom arguments and environment variables.
First, you need to find the application id of the app you want. To do that run the command below in the terminal.
$ flatpak list
Find the Application ID and save it somewhere, it's going to be important later on.
If you want to test the env variables or arguments you can use the temporary solution below. Otherwise, use the permanent solution.
Run the command below in a terminal. Make sure replace Application ID with the id you saved in the earlier section and remove the brackets <>.
Note: Angled brackets <> in command references means that the argument is mandatory, while square brackets [] means that the argument is optional. you will see this a lot in manual pages (man command).
$ flatpak run [--env=VARIABLE=VALUE] <Application ID> [--custom-argument-here]
Example
Recently I had a problem with Discord lagging when mouse hovered over the server list. On my system discord is installed as a flatpak. I solved this issue by adding--enable-gpu-rasterization argument as below
$ flatpak run --command discord com.discordapp.Discord --enable-gpu-rasterization
discord needs the --command flag. Your app probably doesn't need it but if you have any problems you can reach out to me in the comments.
However, this is a one-off solution. To make it permanent follow the section below.
If you only want to add some custom env variables there is an easy method. We use the override command of flatpak for it. This method doesn't work for custom arguments (See issue #2913 on flatpak repo) so if you want to add custom arguments please follow create custom desktop entry section.
$ flatpak override --user < --env=VARIABLE_NAME=VARIABLE_VALUE > <Application ID>
This will make your env variable permanent.
Note: you can remove the --user flag if you want the override to be applied system-wide. I only wanted it applied for my user so I'm using the flag here.
To make custom arguments permanent we just have to get a little more involved.
By default installed flatpak application with desktop entries export their .desktop files in ~/.local/share/flatpak/exports/share/applications. What do these .desktop files do? Well, these files contain information about the application's desktop icon, what kind of a program it is and the command used to launch the app. Which is just what we need.
We will first copy this desktop file so that the original file is intact
$ cp ~/.local/share/flatpak/exports/share/applications/<Application id>.desktop \
~/.local/share/applications
After this open the <Application ID>.desktop file at ~/.local/share/applications in your editor.
Example
Some lines in your file might be different.
As you can already see in my edited file, we are going to directly modify the flatpak run command in the Exec field. This is similar to what we did in the [temporary solution](#heading-temporary solution) but this time it will run every time the app is launched.
You just need to modify the Exec field. Here is a reference, you can also use the screenshot above.
Exec=/usr/bin/flatpak run [--env=VARIABLE=VALUE] com.discordapp.Discord [--custom-argument]
References
That's it for now! Please reach out if you face any issues. If this helped you please consider supporting me. Thank you!