-
Notifications
You must be signed in to change notification settings - Fork 669
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
[Linux] Client crashes on sync at startup #6403
Comments
@Goodaan Could you also run: |
@guruz Thanks for the answer,
|
@Goodaan That's extremely useful, thank you for the data! It's a crash we'd seen on the crash reporter but that we've been unable to reproduce or debug so far. While you can reproduce: Could you also produce a logfile with |
This may already be solvable with the baseline log:
This shows that the same job calls done with |
I don't think this is something that has been tested recently.
Yeah, that explains. The server is stone age old, and no longer supported in 2.5 anyway. |
Should fix an assert when "Server does not support X-OC-MTime" (Which only happens with owncloud 5) Issue #6403
I'll adjust how _finished is used further in master. This patch should be picked into 2.4.
If it is still of any use here is the --logdebug output. It is huge and I did not manage to gist it, so I uploaded it on filebin. Sorry for the inconvenience. |
Now, we've made some commit so the crash should be fixed in the next release. Thanks for the bug report. |
Ok thanks. If I could I would, unfortunately this is not in my power. |
tested 242~rc1 against an 10.0.8 server, that returns the status.php info of a 5.0.25 server as seen above. status message Test success. syncs fine. |
When starting up the client it scans the folders, starts syncing, then segfaults and dies. It is on a fresh Fedora 27 install on my home laptop, syncing on a workplace server that is terribly outdated. The first sync did work and download the contents of the server, but after restarting the machine I cannot get it to work again. I don't know much about the servers config where I work. But I do know that the server is outdated.
Expected behaviour
The client should not segfault
Actual behaviour
It does
Steps to reproduce
Server configuration
ownCloud version: 5.0.25
Client configuration
Client version: 2.4.1-9083
Operating system: Fedora 27
OS language: French
Qt version used by client package (Linux only, see also Settings dialog): Qt 5.6.2, built against Qt 5.6.2
Client package (From ownCloud or distro) (Linux only): From owncloud (https://download.opensuse.org/repositories/isv:ownCloud:desktop/Fedora_27/isv:ownCloud:desktop.repo)
Installation path of client: /usr/bin; /usr/lib64
Logs
Client logfile:
https://gist.github.com/Goodaan/d7916277d483048b7e448881573efa48
gdb:
The text was updated successfully, but these errors were encountered: