buttercup/buttercup-desktop

SyntaxError: Unexpected end of JSON input

buscon opened this issue · 1 comments

hi,

I am on Linux Mint 21.2 and Buttercup suddenly stopped working.

Here is the output I get when I launch it from the terminal

$ /opt/Buttercup-linux-x86_64.AppImage
[INF] 05:52:44: Application starting
[INF] 05:52:45: Application ready
[INF] 05:52:45: Application session started: 2024-07-23T05:52:45.190Z
[INF] 05:52:45: Logs location: /home/marcello/.local/state/Buttercup-nodejs/buttercup-desktop.log
[INF] 05:52:45: Config location: /home/marcello/.config/Buttercup-nodejs/desktop.config.json
[INF] 05:52:45: Vault config storage location: /home/marcello/.local/share/Buttercup-nodejs/vaults.json
[INF] 05:52:45: Vault-specific settings path: /home/marcello/.config/Buttercup-nodejs/vault-config-<ID>.json
[ERR] 05:52:45: SyntaxError: Unexpected end of JSON input
at undefined                                                                                                                                                  
at parse                                                                                                                                                      
at <anonymous>  …mount_ButterKzspdL/resources/app.asar/build/main/index.js:2  (()=>{var e,t={8597:function(e,t,r){"use strict";var n=this&&this.__awaiter||fu…
at next                                                                                                                                                       
at a            …mount_ButterKzspdL/resources/app.asar/build/main/index.js:2  (()=>{var e,t={8597:function(e,t,r){"use strict";var n=this&&this.__awaiter||fu…

It looks like Buttercup tries to open vault-config-<ID>.json, which does not exist and it crashes.
Any suggestion on what the problem can be?

I deleted the folders:
.config/Buttercup
.config/Buttercup-nodejs
and now Buttercup starts as it should.

Unfortunately I cannot say what was the problem, but my 'solution' might still be helpful for other people running into the same issue.