Skip to content
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

Crash on joplin CLI: Unhandled promise rejection Promise ... encryption_applied #1938

Closed
himmelbuerger opened this issue Oct 2, 2019 · 1 comment
Labels
bug It's a bug

Comments

@himmelbuerger
Copy link

Environment

Joplin version: joplin 1.0.149 (prod)
Platform: linux terminal
OS specifcs:Linux penguin 4.19.60-06185-g54aa50936831 #1 SMP PREEMPT Wed Aug 14 01:17:34 PDT 2019 x86_64 GNU/Linux (Chromebook)

Steps To Reproduce

  1. open joplin in terminal
  2. :mknote test
    3 write something
  3. Save it and return to joplin
  4. Joplin crashes and the data is lost
  5. See error message:
    edit: Note has been saved.
    Unhandled promise rejection Promise {
    TypeError: Cannot read property 'encryption_applied' of null
    at ResourceService.indexNoteResources (/home/user/.joplin-bin/lib/node_modules/joplin/lib/services/ResourceService.js:57:15)
    at processTicksAndRejections (internal/process/task_queues.js:85:5)
    at async ResourceService.maintenance (/home/user/.joplin-bin/lib/node_modules/joplin/lib/services/ResourceService.js:135:3)
    } reason: TypeError: Cannot read property 'encryption_applied' of null
    at ResourceService.indexNoteResources (/home/user/.joplin-bin/lib/node_modules/joplin/lib/services/ResourceService.js:57:15)
    at processTicksAndRejections (internal/process/task_queues.js:85:5)
    at async ResourceService.maintenance (/home/user/.joplin-bin/lib/node_modules/joplin/lib/services/ResourceService.js:135:3)

Describe what you expected to happen:

Joplin saves the note or at least it stays somewhere. Joplin does not crash.

Logfile

log.txt

@himmelbuerger himmelbuerger added the bug It's a bug label Oct 2, 2019
@laurent22
Copy link
Owner

This will be fixed in the next release but for now you can run joplin e2ee decrypt to make sure all your notes are decrypted, which will prevent this indexing crash.

@lock lock bot locked and limited conversation to collaborators Oct 14, 2019
scoroi pushed a commit to scoroi/joplin that referenced this issue Nov 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug It's a bug
Projects
None yet
Development

No branches or pull requests

2 participants