Pre-release v2.8 is now available (Updated 27 April)

Beta Testing
41

I don't know much about building, but try version 2.8.4 as 2.8.3 seems to be broken either way

42

The build was successful. The problem was macOS removed python2 and started to use python3 as default.
And Joplin uses electron-builder version 22.11.7 which relies on python2, I updated electron-builder to 23.0.3 and it worked as expected.

43

A new release is available:

  • New: Plugins: Add support for file and directory selector in Settings API (fc09598)
  • Improved: Ask to start in safe mode when the application has crashed (d9a4a9c)
  • Improved: More permissive plugin back-off rules (22ae50c)
  • Fixed: Fixed color of links within list in Markdown editor (#6447 by Hieu-Thi Luong)
  • Fixed: Fixed getting geolocation for new notes (86179bd)
7 Likes
44

Hi
After updating to version 2.8.5, and after restarting Joplin, it shows the message with the alternative for starting in safe mode. Is this because something was crushed before the updating, and the new version shows the problem that I was not aware of it before? Or is it a release bug?. It seems Joplin is working well, but If it is not a bug, how can I deal with it to avoid this warning every time I open the app? I am running Joplin in a second laptop with the same result.

Joplin 2.8.5 (prod, linux)

45

You are correct, something isn't right here. I tried it out in dev mode but I guess the feature doesn't kick in when running like that. I updated an install on an Ubuntu 22.04 VM and if you close the app via the close button on the toolbar it brings up the safemode prompt on next launch. Even does it on File > Quit and Ctrl + Q.

What distro are you using?

46

Right I have tested closing app in different way but with same result. Laptop one Ubuntu 20.04, laptop two Ubuntu 22.04.

47

Out of interest I wanted to see if it was an Ubuntu thing in particular or a particular desktop environment but it seems it isn't, also shows the same behaviour on Fedora (Gnome 41) and Manjaro (KDE).

48

Same behavior here, using Joplin Portable, Windows 10 21H2.
Every time I start Joplin :

1 Like
49

Thank you for this update. I was finding myself using Joplin less and less just because it was becoming horribly slow and I dreaded every time I had to retrieve something from my Joplin Notes and was slowly switching to Logseq but with the new update it's blazing fast again.

And profile switching FINALLLLLLY I have been waiting for this I can finally separate my personal and work notes and load them separately :heart:

Thank you this is a HUGE upgrade for me

3 Likes
50

Using Joplin Portable, you can reproduce the "safe mode" problem doing the following.

  1. Start Joplin Portable using JoplinPortable.exe.
  2. Try to run JoplinPortable.exe again without closing the previous instance.
  3. The "start in safe mode" window appears.
  4. Click "Cancel".
  5. A second instance of Joplin has now opened, using the same profile as the first one.

Edit: The same is true with the regular Joplin. If there's another instance already running, the "start in safe mode" window will appear.

51

For those who had an issue with plugins, is this version any better? I suspect the throttle mechanism is quite ineffective now, but I'd rather start from this and slowly increase the restrictions based on feedback.

52

Here it has made the Outline plugin useable, and work as normal, again.

1 Like
53

I think the new version currently looks very good in terms of API throttling.

54

Hi, if it is not possible to fix in a short term, Would it be possible to add an option to make the new feature of version 2.8. disable. I am talking about the alternative to run a safe mode after opening Joplin when something was crashed in the app? Although I select cancel option every time opening Joplin,
this kind of this false warning, for me, is annoying, confusing and does not serve for the purpose that which it was added.I know that there is another alternative going back to last 2.7.15 release, but I'm asking just in case were complicated to find the source of problem for only small users Joplin group.

55

This is obviously a bug, which will be fixed, so no options

1 Like
56

Hmm, that's true I think it's going to conflict with the single instance check, and we definitely don't want that. Looks like the whole thing is more complex than I was expecting so I'm going to drop the feature for now.

57

Crash detection handler is now disabled in 2.8.6:

2 Likes
58

Another release mostly to fix a config issue with the multi profile feature. If this one's ok otherwise it will become the final 2.8 release:

Improved: Sort sync target options (814a5a0)
Fixed: Make undo/redo menu items translatable (#6435)
Fixed: Sync config was lost when switching profiles (#6459)

59

I notice with 2.8.7 on mac I am seeing this warning a lot:

BackOffHandler: Plugin com.github.joplin.kanban: Applying a backoff of 200 milliseconds due to frequent plugin API calls. Consider reducing the number of calls, caching the data, or requesting more data per call. API call was: joplin.data.get

That plugin is also now very slow when you are dragging a note between columns. From what you've said in this thread, it almost seems like this plugin would need to be rearchitected to work with the backoff constraints reliably. Just wanted to mention it in case there is another solution.

1 Like
60

No I probably need to adjust the backoff parameters. Ideally no plugin should have to be rearchitectured at this point