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. Is this a bug in the client?
What will happen, if you run the sync again, f.ex. after file creation or modification?
Not entirely sure at this point what will happen to a specific file if you change that particular file, but hitting the âSync Nowâ button is not updating the times for the whole log in the window, and the updates are no longer ordered correctly⊠well, you can see here what I mean.
If you do a âSync nowâ it may happen, that the log will not be updated, if no changes are present.
On the other hand you also can downgrade to the previous version as an alternative.
âŠand If it works in an earlier version, report it on GitHub because that would indicate a regression in the latest version.
1 Like
Itâs not a new issue, itâs been like this for many version updates now, might even have been since I started using NextCloud at about the start of the year. I should have reached out much earlier, but you know how it can be sometimes, the itch need to pester you long and bad enough to go see the doctor.
My use case is often that Iâm having a project file that I and someone else keep shuttling between each other, so I keep an eye on the app to see if the file has synced yet. But because of this happening I need to scroll down and up in the program window to find it, instead of it showing up at the top as expected. Itâs often easier to keep an eye on the file modified time in the folder itself, hitting F5 a bunch of times.
Either way, it would probably be a good idea to bring this to the developersâ attention in an issue on GitHub: GitHub · Where software is built
Unfortunately, I canât reproduce the issue because I donât use hibernate. Perhaps thatâs something you could consider as well. Modern processors consume so little power when idle and in deep C states that hibernation is barely worthwhile in many cases.
I use the âdeep hibernationâ because I want to continue where I was with the stuff I got going, not because it would be âquickerâ to start up the computer to. And some programs can take a good long while to start up from scratch, such as Adobe Photoshop or Substance Painter.
Iâll attempt to file an âissueâ on GitHub. I wanted to see here first if it was a known issue, or something I could fix myself. Like how I learned in responses to the other thing I posted about today, that I could indeed force the client to use English.
Thank you both for your help! =)
Well, thatâs what Iâm achieving by simply donât turn off my computer, which nowadays is a laptop that barely uses any power when idle.
In case someone finds this post, Iâll link the GH issue I created here: [Bug]: The desktop client log times are not refreshed upon resuming Windows after hibernation · Issue #8887 · nextcloud/desktop · GitHub
1 Like