Open kevquirk opened 3 years ago
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 help@standardnotes.org or standardnotes@protonmail.com?
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).
here are the last n strace lines running sn snap from terminal: same issue with ubuntu mate and kubuntu 20.04
epoll_pwait(4, [{EPOLLOUT, {u32=1882832128, u64=139708579036416}}], 128, 0, NULL, 0) = 1
futex(0xc4203be148, FUTEX_WAKE, 1) = 1
getsockopt(5, SOL_SOCKET, SO_TYPE, [1], [4]) = 0
recvmsg(5, {msg_namelen=112}, 0) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x55b661e09688, FUTEX_WAIT, 0, NULL) = 0
epoll_pwait(4, [{EPOLLIN|EPOLLOUT, {u32=1882832128, u64=139708579036416}}], 128, 0, NULL, 0) = 1
futex(0xc4203be148, FUTEX_WAKE, 1) = 1
openat(AT_FDCWD, "/proc/sys/kernel/random/uuid", O_RDONLY|O_CLOEXEC) = 6
epoll_ctl(4, EPOLL_CTL_ADD, 6, {EPOLLIN|EPOLLOUT|EPOLLRDHUP|EPOLLET, {u32=1882832544, u64=139708579036832}}) = 0
fcntl(6, F_GETFL) = 0x8000 (flags O_RDONLY|O_LARGEFILE)
fcntl(6, F_SETFL, O_RDONLY|O_NONBLOCK|O_LARGEFILE) = 0
fstat(6, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(6, "de8fbd6e-bffb-4e72-a539-e1ef8fcd"..., 512) = 37
read(6, "", 1499) = 0
epoll_ctl(4, EPOLL_CTL_DEL, 6, 0xc420299644) = 0
close(6) = 0
getpid() = 6026
futex(0xc4203be148, FUTEX_WAKE, 1) = 1
futex(0xc420068948, FUTEX_WAKE, 1) = 1
futex(0xc420068948, FUTEX_WAKE, 1) = 1
futex(0xc4203be148, FUTEX_WAKE, 1) = 1
futex(0xc420068948, FUTEX_WAKE, 1) = 1
futex(0xc420068948, FUTEX_WAKE, 1) = 1
futex(0xc420068948, FUTEX_WAKE, 1) = 1
futex(0xc4203be148, FUTEX_WAKE, 1) = 0
futex(0xc420068948, FUTEX_WAKE, 1) = 1
futex(0xc420068948, FUTEX_WAKE, 1) = 1
futex(0xc4203be148, FUTEX_WAKE, 1) = 1
futex(0xc420068948, FUTEX_WAKE, 1) = 1
futex(0x55b661e08c20, FUTEX_WAIT, 0, {tv_sec=0, tv_nsec=100000}) = 0
epoll_pwait(4, [], 128, 0, NULL, 0) = 0
futex(0xc4203be148, FUTEX_WAKE, 1) = 1
mmap(NULL, 65536, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f10701a7000
rt_sigprocmask(SIG_SETMASK, ~[RTMIN RT_1], [], 8) = 0
mmap(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0x7f10687f9000
mprotect(0x7f10687fa000, 8388608, PROT_READ|PROT_WRITE) = 0
clone(child_stack=0x7f1068ff8fb0, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tid=[6047], tls=0x7f1068ff9700, child_tidptr=0x7f1068ff99d0) = 6047
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
mmap(0xc420500000, 1048576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xc420500000
mmap(0xc41ffd0000, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xc41ffd0000
futex(0x55b661e0eae0, FUTEX_WAKE, 1) = 1
mmap(NULL, 262144, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f1070148000
futex(0x55b661e08c48, FUTEX_WAKE, 1) = 1
futex(0x55b661e08b50, FUTEX_WAKE, 1) = 0
futex(0x55b661e08c20, FUTEX_WAKE, 1) = 1
futex(0x55b661e08b50, FUTEX_WAKE, 1) = 0
futex(0x55b661e09688, FUTEX_WAIT, 0, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x55b661e09688, FUTEX_WAIT, 0, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x55b661e09688, FUTEX_WAIT, 0, NULL) = 0
futex(0x55b661e09688, FUTEX_WAIT, 0, NULL) = 0
futex(0x55b661e09688, FUTEX_WAIT, 0, NULL) = ?
+++ exited with 1 +++
Hi @mutable-dan, thank you for providing that; I'll forward it over to our desktop app dev. Are you facing the issues with the password manager service when installing or running the Snap (or anything else)? Have you had the chance to try out the AppImage?
hi @JaspalSuri i have not tried the appimage recently, it had worked in the past though. i do not recall an issue with the password manager. and it is a fresh install of kubuntu.
thanks
Hi @mutable-dan, thank you for letting me know! I'll forward this to dev team for review and will reach out to you if I have any additional questions. 🙂
Hi @mutable-dan, thank you for letting us know and for providing those additional details. I will reach out to you when I hear back from the dev team.
Thank you for reaching out @mutable-dan; at first glance it looks like a system-wide issue more than a SN-specific one 🤔 I don't recognize any of the app's logs in your output… What version of Kubuntu are you running?
hi
i did not send a log. it was an strace. strace
My bad! What about the standard output then? i-e when you run standard-notes
without any additional arguments, what does it print before shutting down?
it does not print anything
Strange… I would expect the app to print something if it ran into an error, so it may very well be something that happens earlier in the process. Are you using other snaps that run without issue? Standard Notes uses Electron to run on multiple platforms. Have you tried installing something like Visual Studio Code, which also runs on Electron?
Just to chime in here - I run the Spotify snap, which I believe is also an Electron app (?) without issue.
I have a few snaps that run fine. vscode runs fine.
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