Summary: | deskutils/nextcloudclient: segfault on nextcloud because of glib2 | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | lfen <lfen> |
Component: | Individual Port(s) | Assignee: | Michael Reifenberger <mr> |
Status: | Closed Overcome By Events | ||
Severity: | Affects Only Me | CC: | contact, mail, mikael, stephan, tech-lists, w.schwarzenfeld |
Priority: | --- | Flags: | w.schwarzenfeld:
maintainer-feedback?
|
Version: | Latest | ||
Hardware: | amd64 | ||
OS: | Any |
Description
lfen
2019-07-20 17:26:26 UTC
Hi, please retest using the new nectcloudclient version 2.6.1 Hello, I was just about to open an issue regarding this on 13-CURRENT. Ran with gdb and --logdebug as well and have the same stack trace. [OCC::SyncJournalDb::checkConnect sqlite3 version "3.31.1" [OCC::SyncJournalDb::checkConnect sqlite3 journal_mode= "wal" [OCC::ClientProxy::setupQtProxyFromConfig Set proxy configuration to use the prefered system proxy for http tcp connections [OCC::WebFlowCredentials::fetchFromKeychain Fetch from keychain! [unknown static bool LibSecretKeyring::findPassword(const QString &, const QString &, QKeychain::JobPrivate *) This was working with current NextCloud version and then stopped working some weeks ago. > nextcloud --version Nextcloud version 2.6.4git Git revision b45f5fd1a947dc21eb11c69049a99616a2ec950e Using Qt 5.14.2, built against Qt 5.14.2 Using 'OpenSSL 1.1.1g-freebsd 21 Apr 2020' > pkg info glib glib-2.56.3_7,1 > pkg info qtkeychain qtkeychain-0.10.0 Is there something I can help testing? Some new information: I've been told that absence of dbus results in this error as well, so if someone hits this, they should make sure dbus is running (it's needed for communication with the keyring). But that wasn't my issue, for some reason I managed to solve this on my system by nuking NextCloud-client's configuration and the keyring (which I only use for this program). (~/.config/Nextcloud and ~/.local/share/keyrings, nuke at your own risk, beware of dataloss, perform backups, and all that) After that the program has been working flawlessly. Maybe there is some weird edge case that causes the configuration to become invalid and it fails utterly. I've just had this problem and the fix was to remove ~/.config/Nextcloud and ~/.local/share/keyrings and reinstall nextcloudclient. context is: nextcloud --version Nextcloud version 2.6.5git Git revision adada8b2eecd65d7a587b6abe0ae2aabca9a0b75 Using Qt 5.15.0, built against Qt 5.15.0 Using Qt platform plugin 'xcb' Using 'OpenSSL 1.1.1g-freebsd 21 Apr 2020' Running on FreeBSD 12.1-STABLE, x86_64 Because the config was removed, had to re-set-up the client. The port was built in a poudriere that runs every night. I can confirm this problem with the latest 2.6.4 from pkg on 12.1 and to me it looks like the configuration becomes invalid after a certain amount of time. Removing the configuration and starting from scratch makes the client work again for some time, but at some point the problem repeats itself. From looking at https://github.com/nextcloud/desktop/issues?q=is%3Aissue+is%3Aopen+segfault it might seem that the issue is not specific to FreeBSD. I just noticed one more thing: When nextcloud segfaults, synchronising the directory once with nextcloudcmd seems to (at least sometimes) fix the corrupted sync state data so that subsequently nextcloud also works again without the need to start from scratch, I just updated the port to 3.0.2 Could you please test if it behaves differently (hopefully better). Thank you very much Michael, since the upgrade the client is stable again. So to me it seems it was clearly related to the old 2.x version and from my side this bug could be closed. I also haven't observed this issue in a long time :-). Maybe we (someone with permissions) can close this as "Overcome by external events"? |