-
-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Restart & upgrade fails, then locks out client #3645
Comments
Is there any error in the console? https://joplinapp.org/debugging |
No GUI ever loads, only background processes, i.e. no window ever appears - so I can't get to the console. I only got an interface before I started the 'Restart & upgrade' operation (the one that's triggered by clicking the blue text in the orange banner). |
Still present in 1.0.235. |
Isn't it because the window is somewhere off-screen? What if you try this technique: https://www.howtogeek.com/howto/windows/bring-misplaced-off-screen-windows-back-to-your-desktop-keyboard-trick/ Also to be completely sure, could you maybe try to restart your computer, then start the app again? (just in case there's some process stuck in memory) |
I did this on two separate computers, and I have it configured to use the systray icon. No systray icon appears, including when you press on Show hidden icons. |
How many notes do you have? This new release needs to migrate the search engine index on startup and it can be very slow if you have many notes. What if you let it run all day to be sure? |
I used Process Hacker to check and see if any of the Joplin processes were doing anything whatsoever. It's just idle, doing nothing. I'll let it run all day, sure. |
Okay, it ran all day. No change. |
Hmm, that's not good. I've made a fix to the portable app but I don't think it would change something in your case. Could you stop the process completely (in task manager), then delete the log file, and run the app again? Then if you could upload the log file here so that I can see where it's stopping. Make sure to enable the debugging flags as described there: https://joplinapp.org/debugging/#desktop-application |
I'm assuming flags.txt goes in the JoplinProfile folder for the portable version? Went ahead and did that, here's the logs: log.zip |
I can't see anything abnormal in the log, and there's no error, so I'm not sure what's causing this. What if you reinstall the portable app on a different USB drive, then open the app from a different computer? I'm thinking maybe there's some corrupted state on a temp file somewhere which prevents the app from starting. So if you try from a different computer it might help. |
I have the same issue on Debian Linux .appimage I only have is this and no Joplin on the desktop or on the tray. This obviously happened after letting it try that upgrade thing. It is running because I can see it in the I would be happy to provide logs if you can tell me how to generate it.
|
I already did this on two separate computers and I wasn't using a pen drive on either of them - I simply prefer portable versions of software when they're available because they make OS reinstalls much less painful when they have to happen. Both of them started initially on the new version, and then refused to open after the Restart & upgrade process was clicked on. |
Hello, I can confirm had the same issue with the AppImage on my Ubuntu. I somehow managed to get it started by killing and launching again several times but it looks like it fucked something up, now my windows client can't sync anymore, saying my client must be upgraded even if I have the latest version installed. |
I think it has something to do with Electron restart mechanism, but in way I don't understand. At worst it should fail, and then you can start the app manually, but it seems to be keeping some state around that breaks the app afterwards. |
Could you check using an SQLite database browser, what's the value of "sync.upgradeState" in the "settings" table? |
2 |
After changing the value to 0, the app successfully starts up again, but if I try to synchronize, it will give me the orange banner and want to try to upgrade again. So I think what's happening is that it's being put in the upgrade state but the upgrade just never starts. Maybe it has something to do with using a WebDAV server as my sync target, I don't know. |
I can confirm that setting this back to 0 lets me use Joplin again, with that bothering orange banner up there which I wont click on it for a while.
|
Ok thanks for checking so it seems to be something strange that Electron is doing when restarting the app. I'll see if I can replicate it but it will have to wait for at least a week. If you're stuck, you can always export your notes then delete everything and go back to an earlier version. |
Hello,
Yesterday I read all the change logs since the version I had, did the upgrade and clicked the banner to restart to upgrade the sync target. Joplin closed and did not open again by itself, so I opened it (after some time waiting) and nothing happened, as reported. All I have in the logs is:
Changing Thanks. |
@laurent22 This is still an issue in v1.0.236 |
I have the same issue on 1.0.236, on Ubuntu 18.04.5. I am syncing to OneDrive. I changed the upgrade value to 0 in the DB and Joplin again opens. Does this mean I cannot sync until this is fixed? This is a bit concerning, only because I question the integrity of my notes of which I have a lot. How to proceed? |
For the record this is caused by this bug in electron-builder: electron-userland/electron-builder#4650 |
If you're having a problem with the AppImage, please could you try this release and let me know if it works? |
I'm using the Windows portable, and for me this issue is still ongoing in v1.0.237. |
Using the new version, I see it did ask me to restart the program in a popup. I did this and nothing is changed. It still was stuck on the status 2 requiring me to change to 0. |
Same on Arch Linux. $ /opt/appimages/Joplin.AppImage
(electron) The default value of app.allowRendererProcessReuse is deprecated, it is currently "false". It will change to be "true" in Electron 9. For more information please check https://github.com/electron/electron/issues/18397
log.txt
log-database.txt
After reverting log.txt
log-database.txt
|
Ok it seems it's not even starting the migration process, but I don't get at what point it's getting stuck. I'm going to add more log entries to find out. |
I originally reported this for .appimage on Debian but i am able to repeat this on Windows x64 UThe upgrade fails and it never restarts |
If you're having this issue, please try release 239: https://github.com/laurent22/joplin/releases/tag/v1.0.239 With this release, it should show you whatever is preventing the upgrade to happen - it might be something you can fix, like invalid username or password, or some application error. Either way please give it a try and let me know if you're able to proceed with the upgrade. |
Now a white window appeared saying Joplin is upgrading and might take some minutes; after some time a pop up window appeared, to restart Joplin, and everything seems to be working now. 😃 Logs:
|
It works! Hallelujah! |
I did get this to work, however, I needed to start it via command line. When starting from menu, it would lock up a screen and become unresponsive. Quite strange. Regardless, it did end up working. |
Brilliant, thanks guys for confirming that it works. |
The appimage on Debian worked but autorestarts still failed. It worked after manual restarts. |
Environment
Joplin version: v1.0.234
Platform: Windows (Portable exe)
OS specifics: Windows 10 20H1
Steps to reproduce
Tried this on my other computer too, this time letting Joplin idle in the background (around step 8) for 20 minutes, this didn't help, same result.
log.txt
The text was updated successfully, but these errors were encountered: