I've installed the Standard Notes snap (3.5.11) and everything works fine until I first run the application, where I get a prompt about the Ubuntu keychain and how the snap can't use it by default.
It says I either need to quit the application, or use local storage. Alternatively I can run the following command to fix the issue:
snap connect standard-notes:password-manager-service
I run this command and quit the snap. However, when I then try to run the snap again nothing happens.
OS: Ubuntu 20.04.1
Standard notes snap version: 3.5.11
Hi @kevquirk,
I apologize for the late reply and I'm sorry to hear that. I'm afraid that I wasn't able to reproduce this issue. Is the app still not launching on your device? Does rebooting your system help? If not, can you send us the logs stored here: ~/.config/<app name>/log.log (it's possible that the Standard Notes Snap doesn't have that path, as my .config folder didn't have a Standard Notes folder) to [email protected] or [email protected]?
Hi,
I've tested this and reboot doesn't resolve the issue. There is no ~/.config/Standard Notes/log.log file, but there is ~/.config/Standard Notes/logs/main.log which is below:
[2020-11-30 21:40:12.270] [info] Checking for update
[2020-11-30 21:40:12.367] [info] Generated new staging user ID: ca04e8bc-a799-567d-878b-7d77a1322e6b
[2020-11-30 21:40:13.041] [info] Checking for update (already in progress)
[2020-11-30 21:40:13.387] [info] Update for version 3.5.11 is not available (latest version: 3.5.11, downgrade is disallowed).
[2020-12-01 10:14:19.605] [info] Checking for update
[2020-12-01 10:14:20.442] [info] Update for version 3.5.11 is not available (latest version: 3.5.11, downgrade is disallowed).
[2020-12-01 20:51:24.373] [info] Checking for update
[2020-12-01 20:51:25.598] [info] Update for version 3.5.11 is not available (latest version: 3.5.11, downgrade is disallowed).
Given the timestamps, I think this log is from the AppImage rather than the snap as I only just re-installed the snap package.
I renamed the ~/.config/Standard Notes folder, reinstalled the snap and the folder wasn't recreated. So I'm confident this is from the AppImage.
I've been able to work around the issue and get the snap working by selecting use local storage instead of running the snap connect command.
Thanks for the continued support and a great product!
Update: I've rebooted my machine, come back and once again the snap won't start. The log directory still doesn't exist.
Hi @kevquirk, I'm sorry to hear that. Please use our AppImage in the meantime, until we find a fix for this. You may want to install it with AppImageLauncher if you'd like for the app's icon to be generated. Future updates will run through AppImageLauncher, so using it is relatively seamless.
Thanks using the AppImage with the launcher worked perfectly - not need for the snap at this point (the integration piece was what I was missing from the AppImage originally).
Most helpful comment
Thanks using the AppImage with the launcher worked perfectly - not need for the snap at this point (the integration piece was what I was missing from the AppImage originally).