Joplin version: 1.0.233 (prod,linux)
Platform: Arch 5.7.12-arch1-1 x86_64
OS specifics:
I was one of the ones that initially submitted the Linux freezing bug https://github.com/laurent22/joplin/issues/3114... I don't know why I'm having so many problems with this app???
I just put it off and decided to try joplin again today after all this time since the above closed bug, and again I'm having this issue. I don't know if it could possibly be related to issue 3114 or something else?
I looked at 3114 again and it was closed and said to fix, you just turn off web-clipper? My web-clipper was disabled by default already...
I don't really see anything in the console when the app does open..
Here's a tailed log of the failed app opening. In this log, the app failed to open all together, and I tailed the /home/fred/.config/joplin-desktop/log.txt and this was all the output: https://pastebin.com/V6ksbAMn
Is this the debug log?
Thank you!
I have the same problem here. I'm running the exact same version, but on Debian (kernel 4.19).
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.
No, this is still an issue!
found the following useful https://github.com/laurent22/joplin/issues/29 i swapped my install directory to the C:/program files and it worked
I'm also having this issue with 1.2.6 version on Ubuntu 20.04.
I do not have this issue on Ubuntu 20.04 but on a Debian 10 system. This is quite strange because Joplin worked for at least two days and then, all of the sudden, showed this strange behaviour.
Is there a good way to get some logging output from the application?
For logging https://joplinapp.org/debugging/
I found what caused the problem on my machine: https://github.com/RocketChat/Rocket.Chat.Electron/issues/676#issuecomment-418194978
@JackGruber thanks for the tip.
I do not think that this is the problem in my case since my /tmp is executable (bad enough) and I still do not understand why it worked for two days and then stopped.
Suprisingly I can run the application with npm start from its project directory. I will give the logging a try.
Ok. It is working again. The solution was to not only delete the ~/.config/Joplin directory but also the ~/.config/joplin-desktop directory. I suspect that due to whatever error the configuration data got corrupted causing the application to refuse to start.
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.
Most helpful comment
No, this is still an issue!