-
Notifications
You must be signed in to change notification settings - Fork 685
Description
Pre-submission Checks
- I checked for similar issues, but could not find any. I also checked the closed issues. I could not contribute additional information to any existing issue.
- I will take the time to fill in all the required fields. I know that the bug report may be dismissed otherwise due to lack of information.
Describe the bug
With the Windows client being connected to a live OCIS instance, the client request a new login via OAUTH / Browser whenever the computer awakes from deep sleep.
Here, "deep sleep" is my amateur description of what Windows11 does when you close the laptop lid and leave the computer in the sleep state for a longer time period.
Expected behavior
Credentials should be stored and not need to re-authenticate.
Steps to reproduce the issue
- Have ownCloud running and connected to an account on an OCIS instance on a Win11 laptop.
- Close the laptop lid to have the computer go to sleep.
- Wait until "deep sleep" sets in. (That is, if you open the lid again, you will not directly be prompted with the Win11 login screen, but with a sped-up booting procedure.)
- ownCloud client opens and states that the current account has been logged out.
Screenshots
No response
Logs
Log have been collected and I believe this is the crucial part right after the computer wakes up, leading to "OCC::ConnectionValidator::CredentialsNotReady":
https://gist.github.com/sfadschm/21d18d9306627f951f101d03625d6766
Client version number
ownCloud 5.3.1.14018 f15fd5
Libraries Qt 6.4.3, OpenSSL 3.1.2 1 Aug 2023
Using virtual files plugin: wincfapi
OS: windows-10.0.22631
QPA: windows
Desktop environment (Linux only)
No response
Client package version and origin (Linux only)
No response
Installation path (Windows only)
C:\Program Files\ownCloud
Server information
ownCloud Infinite Scale
Edition Community
Version 5.0.6
Web client version 8.0.4
on
Ubuntu 20.04.6 LTS
installed via
Docker container
Additional context
No response