-
-
Notifications
You must be signed in to change notification settings - Fork 521
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Serious Problem - Notesnook only showing black screen on every Device on different Operating Systems #5695
Comments
i am not a pro subscriber yet, but i would like to be one |
One of the few issues I've found with Notesnook is that occasionally, it doesn't know who you are or forgets half way through. It is usually at a time like this when you are logged in and either you get a blank screen or a partial screen. My recommendation is to try to sign out (if the interface has gotten to that point) or clear your browser cache (at least for Notesnook.com) and then sign in again fresh. I was just getting the Notesnook icon in the middle of the screen and nothing else. Cleared by cache for Notesnook.com, got to the main log in page, logged in and everything is fine. I had to re-enable dark mode, but all my data was there, et c. |
@PricacyPro0 Can you leave it there for a couple of minutes? I think it is trying to migrate your database or something like that. If nothing works, try clearing the data directory here: |
Problem: Loggin in the first time works. All notes are there. After closing the application (web app or installed version) it can't load the notes. It only shows a blank page. It seems like it can't load the database. Clearing the cache,reinstalling, and wiping the database didn't work. Uninstalling and reinstalling also don't solve the solution. Always if you close it and reopen it also on chrome it doesn*t load the notes. I now have tried everything. I rebooted, reinstalled, used different Formats like Appimage, flatpack, snap .... Problem: Notesnook can't open/read the database for notes after logging in, closing the application and then reopening it. I got very got advise from chatgpt to delete all files and check everything. I tried everything so that no cache or any files were still there before reinstalling it. Here is a short summary of chatgpt: Problem Summary: Technical Steps Taken: Identified the graphics card using lspci and glxinfo. No specific error messages were provided by Notesnook or the system during the troubleshooting process. Despite updating the graphic drivers and restarting the system, Notesnook still failed to open the database and display notes. Compatibility issues between Notesnook and the system environment, unrelated to graphic drivers. I also encountered this errror message in every browser when i tried notesnook web, which has the same Problem: Error: out of memory (query: with recursive "subNotebooks"("id") as (select * from (VALUES (?)) as "notebookIds" union all select "relations"."toId" as "id" from "relations", "subNotebooks", "notebooks" where "toType" == ? and "fromType" == ? and "fromId" == "subNotebooks"."id" and (select "deletedBy" from "notebooks" where "notebooks"."id" == "relations"."toId" and "notebooks"."type" == ? limit ?) != ?) select "id" from "subNotebooks") Navigate to the Notesnook Directory: Navigate to the directory where Notesnook stores its data: Remove the IndexedDB directory to reset the database: If you want to ensure a complete reset, you can remove other files in the Notesnook directory: just an example My whole error messages and command line commands can be found here: https://chatgpt.com/share/c0e0a4e2-e09d-4106-a639-165c9bd11a8b It's extremely detailled. |
after the latest notesnook update on android the problem is gone, but on Fedora Linux, it still exists |
for some reason this time, altough there wasn't a new update on Fedora Desktop which could have changed anything, after logging in again it could load the database. And suddenly it worked after a few times trying also in the browser. That's pretty weird. |
maybe this will be an issue soon again. Lets see how long it works |
What happened?
Hi,
The Problem: When opening, Notesnook only shows completely blank screen. There is no option to click on anything, or to see any notes or literally anything.
Image here: https://github-production-user-asset-6210df.s3.amazonaws.com/170201651/331826432-db63eb26-f933-4040-811d-b5b2a74d1f83.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20240518%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20240518T185238Z&X-Amz-Expires=300&X-Amz-Signature=4718328ff744788ccf517d499225ba115d68d21ba1d0dca71eedd4dc38e081af&X-Amz-SignedHeaders=host&actor_id=170201651&key_id=0&repo_id=353775942
It looks the same on Android.
I can still acces my Notes with the Notesnook web app, but then i have to log in with my TOTP 2FA Codes every time i open the web app. This is not an option.
I tried to reinstall the Software on Android and on Fedora several times.
When i reinstalled it, after logging in succesfully, it worked. But after i closed the app once and tried to reopen it again, every time it looked like this:
I rebooted my Fedora system and so on.
My software of Fedora and Notesnook is up to date.
I tried to install notesnook from different sources.
I tried Flathub, snapstore,Github, official webiste, AppImage, and always the same result.
On Graphenos (Android) it also doesn't work.
There i tried the Notesnook version 3.0.7 and others.
On Fedora I also had problems with uninstalling Notesnook.
It would sometimes tell me that Notesnook already was uninstalled, but it still showed the Logo.
When i tried to open it, it would always crash
I previously made an automated report here with the same issue: #5611
I would appreciate it to just create a comment or something, so I can see, that someone of the devellopper has seen this.
I really like notesnook, I tried everything.
If this doesn*t get fixxed, I will have to use Standardnotes again.
Steps to reproduce the problem
s
Version
3.0.7
Platform/OS
Linux, Android
Relevant log output
The text was updated successfully, but these errors were encountered: