Coffee
1 December 2024 08:33
1
Operating system
Windows
Joplin version
3.1.24
Sync target
Joplin Cloud
What issue do you have?
After the routine JEX export of my main profile, I wanted to switch to the next profile of another user. Since then, Joplin has only ever started with this fatal error message.
What I have tried:
Restart in safe mode
Uninstall Joplin and install Joplin-Setup-3.1.24.exe.
Uninstall Joplin and install Joplin-Setup-3.1.23.exe.
The error keeps occurring.
Workaround:
I will reinstall Joplin on my Linux.
Screenshots
I've opened a related GitHub issue:
opened 03:22PM - 02 Dec 24 UTC
bug
desktop
high
### Operating system
Windows
### Joplin version
3.1.24 and 3.1.23
### Deskto… p version info
_No response_
### Current behaviour
From the forum:
> ```
> An error occurred: Fatal error:
>
> Cannot change or delete a read-only item: e3ce90472d9f4e8b95acff6a437d0cac
> at checkIfItemCanBeChanged
> (C:\Users\Pa\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\lib\....:15)
> at checkIfItemsCanBeChanged
> (C:\Users\Pa\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\lib\....:45)
> at async Note.batchDelete
> (C:\Users\Pa\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\lib\....:17)
> at async permanentlyDeleteOldItems
> (C:\Users\Pa\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\lib\....:5)
> at async setupAutoDeletion
> ...
> ```
### Expected behaviour
Joplin should not crash on startup.
### Logs
_No response_
Edit : I'm linking a related pull request .
Until the issue is fixed , an alternate workaround may be to disable trash autodeletion before starting Joplin. To do this,
Open C:\Users\Pa\.config\joplin-desktop\
.
Open settings.json
in a text editor.
Near the end of the file, add "trash.autoDeletionEnabled": false
.
Update the previous line to end with a comma. For example, the last three lines in the file might now be: "windowContentZoomFactor": 90,
"trash.autoDeletionEnabled": false
}
Start Joplin.
I'm attaching a screen recording that shows the above steps, though on Linux:
1 Like
Coffee
2 December 2024 20:06
4
Thank you – I'll have to wait for the final solution.
This workaround doesn't solve the problem for me.
Coffee
2 December 2024 20:18
5
@laurent wrote
First, a readonly item probably shouldn't have been deleted?
I own several shares that I made available to other JoplinCloud basic accounts when the ‘read only’ option was not yet available. Later, when I discovered that the ‘read only’ option was offered, I changed these shares to ‘read only’.
@personalizedrefriger
@coffee , if you have a GitHub account would you be ok making your comments over there?
That would make it easier for us, so that we don't have to copy and paste each others responses from one place to another.
(also we encourage posting bug reports on GitHub and not here because it's easier for us to keep track of them)
1 Like
Coffee
29 December 2024 13:15
7
This post is to prevent the topic from being automatically closed.
This topic will close a year after the last reply.