Your message dated Wed, 25 Mar 2026 23:05:50 +0100
with message-id <3068071.Icojqenx9y@tuxin>
and subject line Re: Bug#926310: Working again since 2.6.2 version... for some 
time
has caused the Debian Bug report #926310,
regarding nextcloud-desktop: High CPU Usage for several minutes when sync
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
926310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926310
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nextcloud-desktop
Version: 2.5.1-2
Severity: normal

Dear Maintainer,

I switched from the owncloud to the nextcloud client, for synchronizing my data 
with a private nextcloud server (v15.0.5). While the syncronization with the 
owncloud client goes smoothly and is almost instantaneous, it takes several 
minutes with one cpu used at 100%, with a freeze of the nextcloud window until 
completion. This happens at the first syncronization when connecting, but at 
each event (I tried to just add a simple and short textfile on the cloud, the 
nextclooud app freezes for several minutes just for adding it when it is 
detected on the server). Please note that I have several GB of data 
syncronized, if this problem can be related to my case. The syncronization, as 
I said before, goes smoothly with the debian owncloud client, but also with the 
old nextcloud client v2.3.3 from 
http://ppa.launchpad.net/nextcloud-devs/client/ubuntu. As such, the 2.5.1 
version of nextcloud client is practically barely usable.

Thank you,
Raphaƫl



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-4-amd64 (SMP w/24 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nextcloud-desktop depends on:
ii  libc6                     2.28-8
ii  libgcc1                   1:8.3.0-4
ii  libnextcloudsync0         2.5.1-2
ii  libqt5concurrent5         5.11.3+dfsg1-1
ii  libqt5core5a              5.11.3+dfsg1-1
ii  libqt5dbus5               5.11.3+dfsg1-1
ii  libqt5gui5                5.11.3+dfsg1-1
ii  libqt5keychain1           0.9.1-2
ii  libqt5network5            5.11.3+dfsg1-1
ii  libqt5positioning5        5.11.3+dfsg-2
ii  libqt5printsupport5       5.11.3+dfsg1-1
ii  libqt5qml5                5.11.3-4
ii  libqt5quick5              5.11.3-4
ii  libqt5sql5-sqlite         5.11.3+dfsg1-1
ii  libqt5webchannel5         5.11.3-2
ii  libqt5webenginecore5      5.11.3+dfsg-2+b1
ii  libqt5webenginewidgets5   5.11.3+dfsg-2+b1
ii  libqt5webkit5             5.212.0~alpha2-21
ii  libqt5widgets5            5.11.3+dfsg1-1
ii  libqt5xml5                5.11.3+dfsg1-1
ii  libsqlite3-0              3.27.2-2
ii  libssl1.1                 1.1.1b-1
ii  libstdc++6                8.3.0-4
ii  nextcloud-desktop-common  2.5.1-2
ii  nextcloud-desktop-l10n    2.5.1-2
ii  zlib1g                    1:1.2.11.dfsg-1

Versions of packages nextcloud-desktop recommends:
pn  nextcloud-desktop-doc  <none>

nextcloud-desktop suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Hey,

as this one is open for several years with moreinfo needed and not got any 
information, let's just cleanup and close this bug.

It is always possible to still provide information and reopen the bugreport.

Regards,

hefee

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---

Reply via email to