-
Notifications
You must be signed in to change notification settings - Fork 37
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
v1.0. RC1 Need to show warning if onedrive is already running when starting the GUI #55
Comments
Thanks for reporting the issues @rogercreagh . The GUI will now handle this situation more gracefully. It will automatically stop the failed worker and show the bellow status message. Just note that this message will only appear after you attempt to start sync from the GUI manually or after GUI startup if you have auto-sync enabled. I do not plan to monitor or manage processes which were started outside the GUI scope. I had to remove RC1 due to another critical issue I discovered. Feel free to test updated v1.0.0-RC2 AppImage . |
This is a good fix to the immediate bug of it hanging if another instance of onedrive is running but it leaves the underlying problem. |
Depending on how you have installed OneDrive client, you should be able to stop the systemd service with To prevent OneDrive client from starting on startup, you should be able to disable the systemd service with You can check the official documentation at https://github.com/abraunegg/onedrive/blob/master/docs/USAGE.md#running-onedrive-as-a-system-service |
By default onedrive runs automatically in monitor mode on system login. When the GUI starts it doesn't detect that onedrive is already running and reports "Onedrive is sync not running" (which is also bad English - should be "Onedrive sync is not running") which of course is not true.
If you press the play button it hangs with the message Initializing the Onedrive API"
In the log you find the following lines:
So it looks like it is detecting that onedrive is already running when you manually try to start it from the GUI.
Shouldn't it also run this check when the GUI is initialised so it can report that onedrive --monitor is running?
The text was updated successfully, but these errors were encountered: