nextcloud / desktop

đź’» Desktop sync client for Nextcloud
https://nextcloud.com/install/#install-clients
GNU General Public License v2.0
2.97k stars 784 forks source link

wake up from suspend - The specified configuration cannot be used. #4331

Open Tealk opened 2 years ago

Tealk commented 2 years ago

How to use GitHub

Actual behaviour

When I suspend the computer and then wake it up again I get the following error message in the sync client: "The server responded with an error while reading the directory "": The specified configuration cannot be used."

when i restart the sync client everything works smoothly

Steps to reproduce

  1. start sync client
  2. suspend coputer
  3. wake up computer

Client configuration

Client version:

Operating system:

OS language: EndeavourOS, 5.16.11-arch1-1, GNOME 41.4

Qt version used by client package (Linux only, see also Settings dialog):

Client package (From Nextcloud or distro) (Linux only): community/nextcloud-client

Installation path of client:

Server configuration

Nextcloud version: 23.0.2

Storage backend (external storage):

Logs

Please use Gist (https://gist.github.com/) or a similar code paster for longer logs.

  1. Client logfile: https://gist.github.com/Tealk/4be122cdcb13a74e3ff7ed723f6da067

  2. Web server error log: No errors in the log

  3. Server logfile: nextcloud log (data/nextcloud.log):

jkhsjdhjs commented 1 year ago

@mgallien Can you re-open this?

github-actions[bot] commented 1 year ago

This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!

futtta commented 1 year ago

Reopen please

On Wed, May 24, 2023, 10:31 github-actions[bot] @.***> wrote:

This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!

— Reply to this email directly, view it on GitHub https://github.com/nextcloud/desktop/issues/4331#issuecomment-1560679447, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABMIMIRRP3FKV4YRLMKU2DXHXBMNANCNFSM5P4XNUPA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

mayonezo commented 1 year ago

@mgallien Can you re-open and approve this?

carolyna commented 1 year ago

I'm running Nextcloud-3.8.2-x86_64.AppImage and syncing to three different servers. Two are on NC 25 and have always worked fine, resuming perfectly after waking up every time. I recently added a third server, a new install on NC26. It consistently fails after waking up with the same error as above "The server responded with an error while reading the directory. The specified configuration cannot be used."

ValdikSS commented 1 year ago

Super hacky workaround:

sudo mv /usr/lib/x86_64-linux-gnu/qt5/plugins/bearer/ /usr/lib/x86_64-linux-gnu/qt5/plugins/bearer.mv

ValdikSS commented 1 year ago

Took some time to debug the issue. https://bugreports.qt.io/browse/QTBUG-114666

Simpliest workaround: start the affected applications without the network, connect to the network later.

digitalcircuit commented 1 year ago

@ValdikSS Thank you for investigating and filing that bug with the Qt project!

I haven't checked in depth, but I think this might impact Quassel IRC's attempted use of QNetworkConfigurationManager to detect network connectivity, too.

sreith1 commented 7 months ago

@mgallien Can you please reopen this? What's even the point of that bot closing unresolved bugs?

grossardt commented 6 months ago

I believe that this bug has also prevented nextcloud from syncing files in my case. I run Nextcloud desktop on Ubuntu with two accounts on two separate servers. One account was experiencing this bug. I noticed that in both accounts there are several files that are present locally but do not get synced to the server. Nextcloud client simply ignores these files, even when they change, I move them out and back in, or rename them. The only fix for me was to manually sync via webdav/rclone. Afterwards, nextcloud started recognizing changes again and has kept in sync since I applied the workaround mentioned by @ValdikSS

Has anyone else experienced this behavior?

If I am right and this is related, this bug is likely to lead to data loss and should get much higher priority.