-
Notifications
You must be signed in to change notification settings - Fork 798
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client Fails with Signal 11 upon start #1007
Comments
I just got the same error:
|
10 tasks
Hi, Could you try to run the most recent desktop client and server to check if you still have this issue? The latest version can be seen by checking https://nextcloud.com/install/#install-clients and https://nextcloud.com/install/#instructions-server respectively. If you still have this problem with the latest desktop client, please re-open the issue. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Nextcloud desktop client crashes after logging back in to my nextcloud server
Expected behaviour
Nextcloud client should log into my server and begin syncing files
Actual behaviour
Client dies, showing stack trace in terminal
Steps to reproduce
Client configuration
Client version: 2.5.1
Operating system: Linux, Opensuse Tumbleweed
OS language: en_US.UTF-8
Qt version used by client package (Linux only, see also Settings dialog): 5.12
Client package (From Nextcloud or distro) (Linux only): Distro
Installation path of client:
Logs
Please use Gist (https://gist.github.com/) or a similar code paster for longer
logs.
Template for output < 10 lines
nextcloud --logwindow
ornextcloud --logfile log.txt
(On Windows using
cmd.exe
, you might need to firstcd
into the Nextcloud directory)(See also https://docs.nextcloud.com/desktop/2.3/troubleshooting.html#log-files)
https://gist.github.com/pupper68k/b80be55c911301efab4e348a8d9f32e7
Crash causes stacktrace, all are different, except in that application is given signal 11, which is sometimes SEGV_MAPPER, sometimes SEGV_ACCERR, and sometimes "unknown"
Here are a few examples:
The text was updated successfully, but these errors were encountered: