FS#73625 - [nextcloud-client] Locks up with 100% CPU usage on run

Attached to Project: Community Packages
Opened by Caleb Maclennan (alerque) - Friday, 04 February 2022, 15:37 GMT
Last edited by Chih-Hsuan Yen (yan12125) - Sunday, 13 March 2022, 16:47 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Antonio Rojas (arojas)
Chih-Hsuan Yen (yan12125)
Architecture All
Severity High
Priority High
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No


As far as I'm concerned the nextcloud client app is completely hosed. I don't know if everybody is running into this, but every Arch system I have the client on on runs into 1 thread at 100% usage and perpetual sync state as soon as I run it.

This did not start with the current client package update, I used 2.4.x builds for a month before this cropped up. As best I can figure it actually started some days after the 23.x server update, which was well after the client update. Even then I think it worked for 2 days before all my clients started having trouble. Now I can't use any of them. I tried downgrading the client a couple patch releases to no avail. Android clients don't seem to have a trouble with the current server version, nor is the web client or davfs mounts having any trouble with the server.

The issue appears to be this one upstream: https://github.com/nextcloud/desktop/issues/4106

Given the BSD guy's hack in that thread, I patched the Arch PKGBUILD and rebuilt. Now I'm able to run the client and sync just fine. My monkey patch it attached. I'm not saying this is the best way forward for the package, it was just an emergency to get me back in production. My build is available in my user repository if anybody needs a similar emergency fix: https://wiki.archlinux.org/title/Unofficial_user_repositories#alerque
This task depends upon

Closed by  Chih-Hsuan Yen (yan12125)
Sunday, 13 March 2022, 16:47 GMT
Reason for closing:  Upstream
Comment by Caleb Maclennan (alerque) - Friday, 04 February 2022, 21:36 GMT
It might be worth looking into this issue: https://bugs.archlinux.org/task/73452#comment205514

My server is running PHP 8.1. I suppose that could be what is sending the client into convulsions.
Comment by Musikolo (Musikolo) - Thursday, 24 February 2022, 03:14 GMT
Nextcloud 23 pegged on CPU in my box when using PHP 8.1. I reverted back to PHP 8.0 and it started working fine. This is the same (boring) story once again. Nextcloud 23 requires PHP 8.0 ( https://github.com/nextcloud/server/blob/v23.0.2/lib/versioncheck.php#L39 ), so it cannot have a line this ( https://github.com/archlinux/svntogit-community/blob/packages/nextcloud/trunk/PKGBUILD#L13) stating that it supports PHP 8.1 when that's not true. Apparently PHP 8.1 should be supported when Nextcloud 23.1 or 24 gets released. More info at https://github.com/nextcloud/server/issues/29287

Would it be possible to honor dependencies as officially supported?
Comment by Chih-Hsuan Yen (yan12125) - Thursday, 24 February 2022, 05:42 GMT
> Would it be possible to honor dependencies as officially supported?

Personally I'm +1 for this, but I'm not a maintainer for server packages and this ticket is for the client package. https://bugs.archlinux.org/task/73452 or general places like mailing lists or forums are better places for suggestions like this.
Comment by Chih-Hsuan Yen (yan12125) - Thursday, 24 February 2022, 05:47 GMT
There are two seemingly related patches from upstream. It will be great if anyone affected can test this.
   PKGBUILD (3.8 KiB)
Comment by Chih-Hsuan Yen (yan12125) - Monday, 28 February 2022, 03:54 GMT
Two patches mentioned above are included in a new version. Please test if community-testing/nextcloud-client 2:3.4.3-1 still has the issue or not, thanks!
Comment by Chih-Hsuan Yen (yan12125) - Sunday, 13 March 2022, 16:46 GMT
Upstream applied a workaround at the server side (https://github.com/nextcloud/desktop/issues/4106#issuecomment-1066038166), which is included in the latest community/nextcloud. Nothing to do for now - closing.