-
Notifications
You must be signed in to change notification settings - Fork 671
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
Client not always stops when requested by Windows #8979
Comments
This issue was marked stale because it has been open for 30 days with no activity. Remove the stale label or comment or this will be closed in 7 days. |
TODO: Test how the client reacts to WM_CLOSE |
The issue still occurs, in order to be able to receive the message, it appears that the window needs to shown at least once. |
Please test with close_window.zip. With older clients the expected behaviour is that the client keeps running, independent if the settings ui was shown or not. Additionally please check whether the client closes cleanly when the user logs off, with an old client and a new client. A clean shutdown with the new change should look similar to:
In a clean shutdown of an old client WM_ENDSESSION would be missing. |
Tested testpilotcloud-2.9.2-rc3 on Windows 10 Version 20H2 (Build 19042.1348) VirtualBox VM:
|
Tested testpilotcloud-2.9.2-rc4.6086.x64 on Windows 10 Version 20H2 (Build 19042.1348) VirtualBox VM:
The logfile ends without "Closing DB..."
20211118_1229_owncloud.log.0_NOT_Closing_DB.gz When starting testpilot on commandline with --logflush the last logline is:
|
Tested update from testpilotcloud-2.9.2-rc4.6086.x64 to testpilotcloud-2.9.2-rc4.6087.x64 on Windows 10 Version 20H2 (Build 19042.1348) VirtualBox VM The testpilot-client is shutdown correctly when requested from msi installer:
|
Confirmed that testpilot is shutdown correctly when updating testpilotcloud-2.9.2-rc4 -> testpilotcloud-2.9.2-rc5.6114.x64.msi
|
Scenario "User logout" tested with testpilotcloud-2.9.2-rc5.6114.x64.msi:
|
In that scenario using --logfile won't work as expected as the console process might get killed before us. |
The internal logfile when the db is closed after user logout/login also doesn't contain the line "Closing DB ..." |
Summary for testscenario "User logout" testpilotcloud-2.9.2-rc5.6114.x64.msi on Windows 10 Version 20H2 (Build 19042.1348) VirtualBox VM:
|
Finally got a logfile with "Closing DB..." (--logflush was missing)
|
@gabi18 Can we close this one? |
Yes, I think so.
|
Seen (again) with 2.9.0-rc2
owncloud
and sometimes alsoexplorer
After a second round it normally succeeds.
The text was updated successfully, but these errors were encountered: