-
Notifications
You must be signed in to change notification settings - Fork 7
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
closes when destination folder has been cleared #109
Comments
Of course, clicking on the "settings" wheel allows to force the updater to download, but I think this should be done automatically. Clicking on that wheel is "not so simple" and normal users could think they need more extreme measures. |
Checking the full installation integrity is not feasible, but I guess we could do a minimal check that the engine binary exists |
It could be possible to check if the daemon executable fails to start, or returns too quickly. It could also be possible to make the updater place a marker that the client would remove if successfully started. If marker is still there when updater is run anew, then show an emergency window or something. |
Step to reproduce on Debian:
unvanquished
folderWhat happens:
A popup saying
Failed to start Unvanquished process.
shows, and the updater ends.What would be expected:
Updater should at least ask to repair (aka: reinstall).
The text was updated successfully, but these errors were encountered: