How should I proceed to restore my latest backup safely?

I’ve been trying to open my RemNote (local only knowledge base) for some time now and it keeps “loading”. I also get a bunch of different messages:

  • “Saving to disk. Please pause editing until this message disappears”
  • “Still saving”
  • “Sorry - You Need to Refresh”

This doesn’t seem like it’s going to change. What are my options?

How should I proceed to restore my latest backup safely?

Do I need to reinstall RemNote? (I have no access to Settings or anything, as RemNote is eternally “loading”).

In my experience as a user, if you’ve given up on it fixing itself, there’s a folder somewhere (on Linux it’s ~/.config/RemNote) that, if deleted/renamed, then remnote opens from scratch and you get to log back in, add a clean local kbs and restore from a backup, etc.

Also in my experience as a user, it’s very hard to know when to give up on remnote magically fixing itself or not.

This is one of those questions where REALLY the team should come and give an official answer. What’s the point of making backups without a clear official way of restoring them properly?

Thanks. Yeah, things are unstable. I manage to see my content sometimes (after a few restarts), but it goes away.

It’s worrying that after such a huge update an issue as crucial as this continues happening, and without being properly addressed by the team.

My KB isn’t even big yet, since I avoid using RN for crucial stuff due to things like this.

It seems like this was not a RemNote bug after all.

For anyone running into a similar issue, I recently noticed my laptop had been running slow in general and eventually found out my Windows was having trouble with some drivers. Once that was fixed, my laptop started working normally again, and so did RemNote.

The reason I assumed it was a bug on RemNote is because none of my other apps had serious issues or slowed down as much as RemNote did. It took a while for me to notice they were also slowing down. The fact that this post and others similar to this one has been mostly ignored by the team also didn’t help. Regardless, I’m happy that the issue seems to be gone.