[Bug]: The desktop client log times are not refreshed upon resuming Windows after hibernation
- Dominant language
- C++
- Stars
- 3.9k
- Forks
- 1k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 123
Description
### ⚠️ Before submitting, please verify the following: ⚠️
- [x] This is a **bug**, not a question or a configuration issue.
- [x] This issue is **not** already reported on Github (I've searched it).
- [x] Nextcloud Server and Desktop Client are **up to date**. See [Server Maintenance and Release Schedule](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) and [Desktop Releases](https://nextcloud.com/install/#install-clients) for supported versions.
- [x] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/)
### Bug description
Example screenshot 1:
Example screenshot 2:
If I shut down my computer by way of Start menu > ‘Power’ > Hibernate and go away for a few hours and then I come back, start the computer (resume), and look at this same view (attached) it will look the same way as when I shut down (hibernated) the computer. The update times (1m, 2m, 6m, 36m, 23m, 25m in the picture) will still have those numbers, instead of showing the actual duration. I can only get the correct durations by restarting the NextCloud client.
What also happens is that updates due to others, or myself, updating, uploading or deleting files, will show up in various places in that log view, instead of at the top. To see if a file I'm waiting for to be synced by another has indeed arrived on my end, I need to scroll up and down the log to find it in the list, again instead of seeing it at the top. An alternative means to find out is of course to keep an eye on my folders in Windows, looking at the "Last Modified" timestamp. To get the events right again, I need to restart the client.
I have two different computers that shows the same behaviour.
I've been using NextCloud since around the beginning of this year (or so I think), and though I might not have noticed it at first, this issue has been around for many months if not from the start of me using NextCloud. I'm just now getting around to filing a bug report, sorry!
See discussion at https://help.nextcloud.com/t/the-desktop-client-log-times-are-not-refreshed-upon-resuming-windows-after-hibernation/234058
### Steps to reproduce
1. Take a screenshot of the NextCloud app in Windows, capturing the same view as provided in the Bug Description provided above, with some events in there.
2. Deep-hibernate the computer and be away for a while, perhaps have someone else cause some further activity on NextCloud
3. Start up again, cause it to sync with the Sync Now button if it's not already done it.
4. Browse the log view in the client (the thing on the screenshot provided), take note of oddities in the ordering (should be newest at the top, older and older as you go down, not mixed)
5. Create a new file in some subfolder, or cause other activity.
6. Repeat step 4.
### Expected behavior
The newest activity should always show at the top of the log view in the client, and the duration since the event should always be correct.
### Which files are affected by this bug
Bridge House.blend (more example filenames in the screenshot)
### Operating system
Windows
### Which version of the operating system you are running.
Windows 11 (10.0.26100.6584)
### Package
Official Windows MSI
### Nextcloud Server version
32.0.0
### Nextcloud Desktop Client version
3.17.3
### Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 3.16.1 to 3.16.2)
### Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
### Are you using an external user-backend?
- [x] Default internal user-backend
- [ ] LDAP/ Active Directory
- [ ] SSO - SAML
- [ ] Other
### Nextcloud Server logs
```shell
See attached log in the next section.
```
### Additional info
[client.zip](https://github.com/user-attachments/files/22933423/client.zip) this is a from a different computer than the one I have shared screenshots from before. But you can see the same thing happening on this one, on this screenshot (2 days, 2 minutes, 'now', 14 minutes).
Log file:
[nextcloud.log](https://github.com/user-attachments/files/22933494/nextcloud.log)
Contributor guide
Assessment
This issue has not been assessed yet.