Did you open one of the Joplin .md file on Nextcloud recently? Because it changes and breaks the file as soon as you open it, and that would cause this error.
Also please share the log as that should hopefully tell you what file is corrupted so that you can delete it on Nextcloud
No, I haven't opened any files, except with Joplin. I use Joplin on several other devices, where it works perfectly (those running Windows still use version 3.4.12).
I'm not sure which log file is relevant. Can you tell me?
Sorry it's not a sync issue, it seems to be something else during initialization. Please see if you can get more information from the console in particular, as described here:
I forgot to mention that when I launch Joplin, the only window that appears is the one shown in the post. I created the flags.txt file anyway, but it doesn't change anything.
Unfortunately the log doesn't tell us enough. Would you mind trying this new version 3.6?
I made a change so that it shows clearly what is happening when the app cannot start. That won't immediately fix the crash, but at least we'll know where it comes from and then I can create another fixed version. Please give it a try and let me know how it goes
No, I did not process the database outside of Joplin's standard usage. But since the problem appeared when I first opened it after the update, perhaps it was the update that process it ???
This table is only created when running the ANALYZE command on the database, which we don't do, so something somewhere on your system must have ran this command. Maybe some external Joplin-related app? Or a plugin? But the fact that nobody else reported this means it's probably something unusual rather than a plugin.
Regardless we'll add a fix to handle this particular case.
I'm experiencing the exact same error.
This happened after updating this afternoon from version 3.4.12 to 3.5.11.
I downloaded the software from the official repository, the one provided by the application.
I also tried version 3.5.12 with the same result.
No, nothing seems to be calling OPTIMIZE in the app. A few things to note:
Just because it happened on the upgrade, doesn't mean it's a problem with this version. Version 3.5 upgrades the database which is what is triggering the bug. So if the database had been analyzed at any point during 3.4 or even before, the issue would only show up now.
The fact that the two of you have this same problem is a bit worrying.
Do you use any Joplin plugin or external application? I'm wondering if one of them run analyze on the db. Or some system-wide tool that does this on Windows, but that would be surprising and ChatGPT gives me nothing for this
I use Joplin practically every day without any apparent problems.
I had missed the version update and ignored it until this afternoon; I closed the application and ran the update, but the application wouldn't start again.
I only use 5 plugins.
I've reverted to version 3.5.12, which is now working correctly.