Pre-release v2.5 is now available (Updated 28 Oct)

If any of you is trying v2.5.4 with E2EE enabled, please could you check the Encryption screen? There's a huge yet almost invisible update to the E2EE system in this release and I'd be curious to know if it's working well for everybody. If it does, on the Encryption screen, you should see a line that says:

Public-Private Key Pair: Generated

If you don't have this or notice anything off please let me know.

v2.5.6 is available now. Since we haven't heard of any bug so far in the pre-releases, I'll make this one an official release later if everything goes well.

This version also better handles the session expiration logic in Joplin Server/Cloud so I'd like to release it as soon as possible.


https://github.com/laurent22/joplin/releases/tag/v2.5.6

  • New: Added mechanism to migrate default settings to new values (72db8e4)
  • Improved: Improved Joplin Server configuration check to better handle disabled accounts (72c1235)
  • Improved: Improved handling of expired sessions when using Joplin Server (ace1118)
  • Improved: Improved master password state handling in Encryption screen (7d62df8)
  • Fixed: Fixed Goto Anything scrolling for long lists (22e5c3a)

I'm running into an issue on 2.5.6, on Linux, where when attempting to open the options in file > import and selecting an option is causing crashes. The terminal displays:

[58158:1029/024702.571594:ERROR:browser_main_loop.cc(269)] Gtk: gtk_native_dialog_run: assertion '!priv->visible' failed

While this is in a Snap environment (effectively running Gnome 3.38 libs), it seems to be occuring in a lot of other places, take a look here which links to here, so I'd be reasonably suspicious that this would effect AppImage users. I couldn't get it to occur in the AppImage on Ubuntu 20.04, maybe some other people on Linux might be able to check if it happens for them. Edit: Found one, since I haven't published any of the 2.5 releases :wink:

This presumably effects any file open / file save UI. It's extremely late now and I've not had time to look into it properly, but I thought I'd bring it up as early as possible just incase. Naively, I'd assume that maybe Electron just needs to be bumped up a few patch releases but I'm no Electron dev so...

I'll try to upgrade to 15.1.3 to see if it helps.

I have a few Linux VMs already set up so I tested the 2.5.6 AppImage and the import dialog with:

  • Linux Mint 20.2
  • Ubuntu 20.04 Desktop
  • Ubuntu 21.10 Desktop
  • Kubuntu 21.10

No problems encountered.

So, on this limited test, it seems that the dialog issue reported is likely not affecting an AppImage on current Debian/Ubuntu based systems.

2 Likes

One more data point:

  • Manjaro
  • Custom built Joplin:
Joplin 2.5.1 (prod, linux)

Client ID: 934e50ae74a941f587912680f6d54c43
Sync Version: 3
Profile Version: 39
Keychain Supported: No

Revision: 382efa231 (callback-url)

Selecting an option under File - Import does not crash the app but doesn't do anything else either.

Same for 2.5.6 AppImage on Manjaro.

If you could try 2.5.7 it might work as I've upgraded Electron:

I've just tried 2.5.7 in a snap. Firstly, it's probably worth giving some context that in Electron 14 the GTK dialogs were improved to have xdg-desktop-portal support. When this is active, Snaps and Flatpaks can access nearly anywhere on the filesystem (via the GUI at least) and KDE users amongst others can use the KDE file picker instead of GTK's file picker. This is opt in with the environment variable GTK_USE_PORTAL=1. While it'd be nice for this to be turned on I'm not averse to keeping it disabled and it's actually likely I will at the moment anyway.

With this both enabled and disabled, the GTK dialog's still aren't working for me in the snap. Joplin itself doesn't crash when this environment variable isn't there though, it still just prints the assertion and doesn't show any file picker UI.

I'd love to try it on Manjaro but my host environment is Windows 11 with HyperV and HyperV struggles with a lot of distributions for me. The 2.5.7 AppImage on Ubuntu 20.04 works just fine still.

No difference on Manjaro.

Ok thanks for checking. There's a chance we're going to release this as it is, and just patch when the bug is fixed upstream, as it doesn't look like we have many options.

1 Like

No problem for me with Fedora (AppImage), Gnome 40.4.

1 Like

Appimage 2.5.7 all okay here.

Linux (Solus with Budgie)

1 Like

Thought I'd post here rather than the release thread to conclude the above issue; the linked issue shows a few people trying to solve the problem by swapping from synchronous to asynchronous GTK dialog calls. This does appear to fix the problem for me and so I'm running this patch downstream. Electron/JS isn't my strong point so I don't know what side effects this is having, but the testing appears to work fine for imports/exports/plugin installation which I suppose is the main requirement until it's fixed properly in Electron and this can be dropped. Perhaps upstream would be willing to try something similar if it persists as an issue.

Thanks for the fix, I've applied it to master and it will be part of the next patch release.