From: Γυψ <gyps@member.fsf.org>
To: 53028@debbugs.gnu.org
Subject: bug#53028: nextcloud client segfaults
Date: Wed, 05 Jan 2022 16:57:15 +0100 [thread overview]
Message-ID: <87wnje9nua.fsf@member.fsf.org> (raw)
Dear all,
after updating my system today nextcloud client segfaults. No helpful error message is output.
The call of
#+begin_src sh
nextcloud --logdebug --logfile -
#+end_src
after removing all configuration of nextcloud produces the following output
#+begin_example
2022-01-05 16:50:20:506 [ info nextcloud.gui.application ]: "################## Nextcloud locale:[en_US] ui_lang:[] version:[3.2.0git] os:[Guix System]"
2022-01-05 16:50:20:506 [ info nextcloud.gui.application ]: Using "en_US" translation
2022-01-05 16:50:20:507 [ info nextcloud.gui.application ]: VFS suffix plugin is available
2022-01-05 16:50:20:507 [ info nextcloud.gui.socketapi ]: server started, listening at "/run/user/1000/Nextcloud/socket"
2022-01-05 16:50:20:507 [ info nextcloud.gui.folder.manager ]: setting remote poll timer interval to 30000 msec
2022-01-05 16:50:20:507 [ info nextcloud.gui.account.manager ]: Migrate: restoreFromLegacySettings, checking settings group "Nextcloud"
2022-01-05 16:50:20:507 [ info nextcloud.gui.account.manager ]: Migrate: checking old config "$HOME/.config/ownCloud/owncloud.cfg"
2022-01-05 16:50:20:513 [ info nextcloud.gui.folder.manager ]: Setup folders from "$HOME/.config/Nextcloud/folders" (migration)
2022-01-05 16:50:20:513 [ info nextcloud.sync.clientproxy ]: Set proxy configuration to use the preferred system proxy for http tcp connections
Segmentation fault
#+end_example
Any idea what could have caused this error?
Cheers,
Alex
next reply other threads:[~2022-01-05 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 15:57 Γυψ [this message]
[not found] ` <handler.53028.B.16413996909178.ack@debbugs.gnu.org>
2022-01-06 10:03 ` bug#53028: Acknowledgement (nextcloud client segfaults) Γυψ
2022-01-06 11:15 ` bug#53028: " Γυψ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wnje9nua.fsf@member.fsf.org \
--to=gyps@member.fsf.org \
--cc=53028@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).