As originally posted here after spending two weeks working on coming to a conclusion in my spare time:
I have good news:
- I can officially verify with 100% certainty that this specific commit is the culprit behind this entire fiasco: torvalds/linux@339ddb5 . It was suggested earlier here and on reddit, but I had to find out on my own through testing to make sure.
- Node-sqlite3 module just added official Electron 8 support in its master branch, meaning upgrading to Electron 8 in the future should be a fairly safe bet, since this was the one module that Joplin uses that I was scared would break the most on upgrade. mapbox/node-sqlite3@dc30669
- There is a bit of talk about this particular issue being fixed in the next official Electron 8 release (with a partial fix implemented in 8.0.3). I’m having problems finding the source here, though, so I could be terribly mistaken.
The bad news:
- If you use the btrfs filesystem for your harddrives, I’ve found that on the latest 5.5 releases after reverting the epoll commit above, there’s a chance that you won’t be able to boot properly. It’s a bit random when it happens, and I haven’t figured out a set pattern yet, so no bug report ensuing upstream there.
- There is no set release date or timeline that I can find for an official stable release to be deployed for Electron 8.0.4 or Node-Sqlite3 4.1.2 (or whatever they decide to use for versioning for that release).
There are two solutions to this problem that should fix the issue for most users here:
- Revert to the latest Kernel 5.4 release (whether it be the LTS release from your distro’s repos or a custom build if you know what you’re doing with building your own kernel)
- Cloning the official github repo, patching it to the latest kernel.org release, and reverting the above commit and running that kernel with the caveat above and the possibility of other issues arising.
@laurent, if you are able to wait for Node-SQLite3 to release their next release, I don’t really see any other major hurdles for upgrading to Electron 8 for the time being. It would definitely be good to fully test it and I did find one minor UI bug on 5.4 involving creating new ToDo lists breaking the placement of the editor in the app and needing to be restarted.