If it is a sync issue, please let us know what you are syncing with:
Managed Nextcloud
The operating system you are using:
System: Kernel: 5.4.0-81-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon 5.0.5
wm: muffin dm: LightDM Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal
Machine: Type: Laptop System: Dell product: Latitude E7440 v: 00 serial: Chassis:
type: 9 serial:
Mobo: Dell model: 091TRH v: A00 serial: BIOS: Dell v: A28 date: 06/13/2019
Battery: ID-1: BAT0 charge: 47.0 Wh condition: 47.0/47.0 Wh (100%) volts: 8.4/7.4
model: SMP DELL 909H538 serial: status: Full
CPU: Topology: Dual Core model: Intel Core i5-4300U bits: 64 type: MT MCP arch: Haswell
rev: 1 L2 cache: 3072 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19954
Speed: 2590 MHz min/max: 800/2900 MHz Core speeds (MHz): 1: 2594 2: 2811 3: 2594
4: 2783
Graphics: Device-1: Intel Haswell-ULT Integrated Graphics vendor: Dell driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:0a16
Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa
resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 4400 (HSW GT2) v: 4.5 Mesa 21.0.3
compat-v: 3.0 direct render: Yes
Audio: Device-1: Intel Haswell-ULT HD Audio vendor: Dell driver: snd_hda_intel v: kernel
bus ID: 00:03.0 chip ID: 8086:0a0c
Device-2: Intel 8 Series HD Audio vendor: Dell driver: snd_hda_intel v: kernel
bus ID: 00:1b.0 chip ID: 8086:9c20
Sound Server: ALSA v: k5.4.0-81-generic
Network: Device-1: Intel Ethernet I218-LM vendor: Dell driver: e1000e v: 3.2.6-k port: f080
bus ID: 00:19.0 chip ID: 8086:155a
IF: eno1 state: down mac:
Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel port: f040 bus ID: 02:00.0
chip ID: 8086:08b1
IF: wlp2s0 state: up mac:
Drives: Local Storage: total: 931.51 GiB used: 612.67 GiB (65.8%)
ID-1: /dev/sda vendor: SanDisk model: SSD PLUS 1000GB size: 931.51 GiB speed: 6.0 Gb/s
serial:
RAID: Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0
bus ID: 00:1f.2 chip ID: 8086.282a
Partition: ID-1: / size: 915.40 GiB used: 612.67 GiB (66.9%) fs: ext4 dev: /dev/sda5
Sensors: System Temperatures: cpu: 65.0 C mobo: 44.0 C sodimm: 34.0 C
Fan Speeds (RPM): cpu: 4096
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/nextcloud-devs-client-focal.list
1: deb http: //ppa.launchpad.net/nextcloud-devs/client/ubuntu focal main
2: deb-src http: //ppa.launchpad.net/nextcloud-devs/client/ubuntu focal main
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb https: //mirror.dogado.de/linuxmint uma main upstream import backport
2: deb http: //ftp.uni-mainz.de/ubuntu focal main restricted universe multiverse
3: deb http: //ftp.uni-mainz.de/ubuntu focal-updates main restricted universe multiverse
4: deb http: //ftp.uni-mainz.de/ubuntu focal-backports main restricted universe multiverse
5: deb http: //security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
6: deb http: //archive.canonical.com/ubuntu/ focal partner
Active apt repos in: /etc/apt/sources.list.d/skype-stable.list
1: deb [arch=amd64] https: //repo.skype.com/deb stable main
Active apt repos in: /etc/apt/sources.list.d/spotify.list
1: deb http: //repository.spotify.com stable non-free
Info: Processes: 251 Uptime: 35m Memory: 7.68 GiB used: 3.43 GiB (44.6%) Init: systemd v: 245
runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Client: Unknown python3.8 client inxi: 3.0.38
Normally, the programs from application management are dated directly from Linux Mint. So I don't know (sorry) what to do. There is no update available for Joplin.
When I download the release from Github, I don't even know which one to use. Also ... didn't I have installed Joplin twice after that?
You must have upgraded your sync target using a client running on 2.3.x, maybe a phone if it has automatic upgrades enabled?
There was a change in 2.3 to update the sync target to the new format.
I'm also using mint but not from any inbuilt package manager, its best to just run the recommended script on the downloads page to get the appimage directly from the github latest release.
It might be worth taking a backup of everything (JEX export + profile backup), uninstalling from the mint package manager and re-installing from the script. You can then restore the data in your profile directory and hopefully it should all work again.
Upgrades are then as simple as just running the script again rather than waiting for the packages to be updated.
Thanks for your reply, Yes, I am using a smartphone with Joplin, too. What do you mean with "upgrades enabled"? The Joplin App itself is the latest version 12.3.1. Or do have to enable anything in the Joplin App on iphone?
With "Profile backup" do you mean the folder /home/username/.config/joplin-desktop?
I'm not very familiar with iOS but the google play store for example allows you to prevent application updates being pushed to your phone and installed automatically.
In this case because your phone upgraded to a 2.3.x version and you sync'd with your sync target, it upgraded it from the old sync version 2 to the new sync version 3 which made your mint desktop app non-compatible - once you upgrade to 2.3.5 it should work just fine.
And yes, that is what I mean by the profile backup. The sqlite database and any changes you made to your config are all stored there.
I would actually recommend installing the 'Simple Backup' plugin (just search for simple or backup in config > plugins) and defining a backup path which will perform a backup of your profile and perform an export to JEX at the same time.
Instructions on how to restore if necessary are on the plugin's github page (just click the plugin name on the little square).
Thank you again for your help.
If I do that and restore the Joplin notes from the backup, do I have to delete the notes in Nextcloud beforehand? And can it be that notes that I created or edited with the iphone and which were not synchronized with Joplin Desktop because of the error will then disappear?
Well hopefully if you take a backup of the profile, install from script then re-install and put your profile back, Joplin will just react as if you upgraded it and it will continue from where it left off. The backup and import of the JEX file should hopefully be a last resort as I'm not 100% sure as to what will happen on the sync target if the target is ahead of the JEX archive.
I'm willing to concede ignorance if anyone has a better idea, I'd rather not be responsible for making you lose data because my advice is duff.
On a slightly different note, the version showing as current for me on the mint software manager is 2.3.5, are you seeing different?
It should be, you can see on my screenshot from before (Mint 20.2) that it is showing the correct current version from flathub.
(Incidentally it seems the flathub entry still has the old pictures rather than your swanky new ones) @Steffimania What happens if you press the burger menu on software manager and hit "refresh packages" (or obviously your equivalent of it).
If I open software center and search for "joplin" it first finds that there is a joplin entry but doesn't have any details until it fetches the latest info for the package and updates it, which is when it then shows the latest version of 2.3.5.
Ok I did a bit of googling (I don't use flatpak stuff so its a bit new to me), it seems that software manager will only manage the finding and initial install of flatpaks, you need to do the rest yourself. From terminal try: flatpak list
Find the entry for Joplin and copy the ApplicationID then run sudo flatpak update APPLICATIONID
Wow, thank you for that. Then I would not have searched now. I have just started a request in the Linux Minut Forum. I am assumed that all updates over the package managing are automatically running. Thank you. I'll check that now.
I think it lists all kinds of stuff, flatpaks as well as .deb files. I think the .deb entries update automatically but the flatpaks rely on the application itself to manage updating internally - which is not what Joplin does.
I also use Joplin on Linux Mint 20.2. But I use the AppImage via the command line script on the Joplin help page, it works fine for me (I first installed AppImage "myself", but later changed to the command line script).
Now to some thoughts about the FlatPak version. See this as more general thoughts, not any recommendation of that I know exactly.
I can also see in the Mint Software center that it refer to Flathub version 2.1.8, while Flathub itself has 2.3.5. I do not know why (nor I cannot see a direct explanation above). But what I do understand is that the Mint Update manager nowadays looks for new versions of Flatpaks, I think it may be new from Mint 20.2. This similar to that the Update manager now from 20.2 look for updates of "Cinnamon spices". On the Mint Update manager - Settings - Automation, there is also a setting for FlatPak checks and autoupdate at login, which indicats Flatpaks are checked. So my thery, that even if Software center first install an older version of the Flatpak, the Update manager will find the new one. But, I do not use any Flatpak currently, and have not done a trial.
A second comment on Flatpak in general is a concern that many Flatpaks are maintained by someone else than the developer. It seems to be the case for Joplin, if I understand Flathub information correctly. This means, there is a risk that the Flathub version can be delayed or not maintained compared to versions maintained by the developer. I do not say this is or will be the case for Joplin, it was a general remark of a concern I have.
I do not know if above gives anything useful or just confuse - if confuse, forget my comment...!
