Bug sur la dernière version de Nextcloud desktop

ljf · Décembre 19, 2022, 10:27

Salut,
Juste pour dire qu’on m’a signalé un bug important sur le client de synchro nextcloud couplé à la limitation de bande passante.

github.com/nextcloud/desktop

[Bug]: setting speed limit causes client hang.

opened 08:21PM - 06 Dec 22 UTC

zBeeble42

0. Needs triage

### ⚠️ 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 Briefly, the client is locking up, repeatably. Locking up includes not responding to an open from the dock, locking up context menus in the windows shell and only responding to a task-manager kill. If the window is open, it locks up showing with "0B of 4.1MB file 1 of 34" or "7B of 4.1MB file 1 of 34" Pertinent points: - I started with an old version of the desktop client (version lost). I upgraded to 3.6.7 (?) and then to a daily release 3.6.50 (grabbed 2022-12-06). All versions exhibit the same behaviour. - Nextcloud is up-to-date. No changes there (is in production). - if I add files to the local store, those files are uploaded, then this bug manifests. - It was stopping on one file in the local root (of the nextcloud) folder. "langs.xml" I didn't need that file, so I removed it. No change (found this with the client logs). - I also found all files renamed with _conflict_ in them. I resolved those conflicts. No change. - The client logs stop mostly on the same file, but sometimes a different file. Extra diagnostic points (not my first bug report): - computer rebooted, disk CHKDSK'd. client restarted multiple times. Behaviour is repeatable - logs created, but an awful lot of non-opaque information in them. Would prefer to share privately _or_ to cut out small sections. - no other users of same nextcloud affected. - no errors in nextcloud server log - I tried removing files the log stopped on. Did not help. - I tried removing all the .db files in the root ... causing a complete resync. Did not help. ### Steps to reproduce Start nextcloud, wait. Obviously, not for you. This is 100% repeatable on my system. Nextcloud is effectively not working until fixed. I'm not sure what's causing it. ### Expected behavior Nextcloud doesn't lock up? ### Which files are affected by this bug langs.xml ### Operating system Windows ### Which version of the operating system you are running. Windows 10 workstation ### Package Appimage ### Nextcloud Server version 25.0.1 ### Nextcloud Desktop Client version 3.6.50 (although also any others I tested) ### Is this bug present after an update or on a fresh install? Fresh desktop client install ### 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 Debug news new parser added : FeedIo\Standard\Rdf 2022-12-06T15:13:42-0500 Debug news new parser added : FeedIo\Standard\Rss 2022-12-06T15:13:42-0500 Debug news new parser added : FeedIo\Standard\Atom 2022-12-06T15:13:42-0500 Debug news new parser added : FeedIo\Standard\Json 2022-12-06T15:13:42-0500 Debug logreader Could not find resource file "/apps/logreader/css/../js/logreader-main.css" 2022-12-06T15:13:41-0500 Debug spreed Controller OCA\Talk\Controller\SignalingController::pullMessages created 65 QueryBuilder objects, please check if they are created inside a loop by accident. 2022-12-06T15:13:41-0500 Debug spreed Controller OCA\Talk\Controller\SignalingController::pullMessages created 65 QueryBuilder objects, please check if they are created inside a loop by accident. 2022-12-06T15:13:38-0500 ``` ### Additional info [nextcloud-short.log](https://github.com/nextcloud/desktop/files/10170051/nextcloud-short.log)

Je pense que ça peut intéresser du monde de savoir ça.

A+,
ljf