I currently have Joplin 3.3.12 (prod, linux) installed on both of my Linux computers.
Installation and updates are done via the repository of my Linux distribution.
I have the following questions about this:
Is Joplin 3.3.12 (prod, linux) the current productive version?
What could it mean that I have already received ‘Update from version 3.3.12’ twice (2025-07-10 and 2025-11-19) and that ‘Joplin 3.3.12 (prod, linux)’ is displayed both before and after the update – i.e. no change is visible. On my Windows computers, I have Joplin 3.4.12 (prod, win32).
The question is how I can get from where I am now to an officially supported installation.
I think I should first completely uninstall the Joplin Flatpak using the OS’ uninstall function.
But what should I do after that? I have no idea what an ‘appimage’ file is.
I suppose I could run it with a double click – but is that a good idea? I suspect not.
I’m using Tuxedo OS, too. You can use the exact command from the website (without sudo). I can confirm that the script worked for installing and works for updating on my machine.
@Coffee I've used this method for a long time and found it to be stable and reliable; as @Marph said it works fine run as a normal user (and I think that's the way it's intended to be used)
I use an alias for Joplin Update to make life easier.
(I've added the flag to receive the pre-release version, but that's something everyone might not want).
The script pulls in an icon and creates a .desktop file, so you'll find Joplin in your menu
If you find your existing config is located at ~/.config/joplin-desktop then it will be a seamless transition, and when you open it all your data and settings will appear as uusual. But flatpak may have but the files elsewhere, perhaps under ~/.var/app/, you'd have to check.
(I've used the pre-releases for years without any serious issue, well done Joplin devs!)
Uninstall the Flatpak using the software centre. If you see a message about "Joplin is not installed but still has data present" and asking if you wish to delete that data, the answer is no (or just do not press the delete button!). I am not sure that this would actually delete your note data but let's not take chances!
Run the install script to install the Joplin AppImage. It will download Joplin and create a program shortcut. If you see a warning about "sandboxing" do not worry - that is normal. When you run Joplin again it should detect your existing data and look and work exactly as it did before.
Regarding your specific questions:
Should I run this script for
a) the new installation ...
Yes
b) to install new versions as soon as they are available?
Yes
Do I need to run this command with sudo on my Tuxedo OS, which is based on Ubuntu?
No. Everything runs from your home folder, so sudo is not required.
(I know I'm repeating some of what was said above but they ninja'd me as I was testing this on a VM and typing out a reply )
I think this will enable me to get started soon on getting a clean and up-to-date Joplin installation on my Linux computers as well. But I need to sleep on it for at least one night and then take care of a few other urgent matters before I can clear my head enough to do so.
At the moment, this is how I imagine it will work:
a) First, I will perform an additional JEX export from my main computer (virtual Win11 computer on VirtualBox) that uses the same productive data in my NextCloud.
b) I will test the following actions on my virtual Tuxedo OS computer on VirtualBox after creating a backup copy of this virtual computer.
c) Uninstall the Flatpak using the software centre. I think I'll also delete the existing data, because I can then completely resynchronise from my productive data in my NextCloud.
d) Install Joplin with the recommended script
e) Resynchronise my productive data from my NextCloud.
If all that works, I will look into the recommendation ‘alias for Joplin Update to make life easier’....
and if I manage that too, I will also correct the Joplin installations on my two Tuxedo OS computers that I use as hosts for VirtualBox.
Note, if this a Fedora Linux system or OpenSuse Tumbleweed, my RPM packages are an option. I merely repackage the AppImage, and so, what you install is indeed the official version … though, you do rely on a shmuck like me to keep the packaging up to date. And, in the end, I only use Fedora myself. I have been pretty good about keeping the RPMs current over the years, but … not perfect.
Since the latest updates to Tuxedo OS, the Joplin Flatpak no longer started on one of my two hosts.
That's why I decided to take a forward-looking approach and deleted the Joplin Flatpak on this computer via the ‘Discover’ user interface, without being asked whether I wanted to delete the Joplin data or not. I assume that it was also deleted. This is in line with my plan anyway, as I want to completely resynchronise the profiles of the Joplin installed with your script with my NextCloud.
Your script ran without any error messages and Joplin is then listed with its logo as an office application and can be selected. Unfortunately, it does not start on Tuxedo OS, as @Marph had already announced under some AppImage specific workarounds.
$ lsb_release -a
...
Distributor ID: Tuxedo
Description: TUXEDO OS
Release: 24.04
Codename: noble
Would it be possible for you to add a query for TUXEDO OS to a new version of your script in the range from lines 273 to 286 and also set the --no-sandbox parameter for it?
)
).