Bug 1024973

Created attachment 817522 [details]
File: backtrace

Created attachment 817523 [details]
File: cgroup

Created attachment 817524 [details]
File: core_backtrace

Created attachment 817525 [details]
File: dso_list

Created attachment 817526 [details]
File: environ

Created attachment 817527 [details]
File: exploitable

Created attachment 817528 [details]
File: limits

Created attachment 817529 [details]
File: maps

Created attachment 817530 [details]
File: open_fds

Created attachment 817531 [details]
File: proc_pid_status

put new files in the folder synchronised with the desktop sync client, a short while later it crashed

reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/bin/owncloud -session 1028622b2541e2000138040420900000092220007_1383039904_184508
crash_function: __gmpz_clear
executable:     /usr/bin/owncloud
kernel:         3.11.6-200.fc19.x86_64
package:        mirall-1.4.1-1.fc19
reason:         Process /usr/bin/owncloud was killed by signal 11 (SIGSEGV)
runlevel:       N 5
type:           CCpp
uid:            1000

Crash at startup

Have updated to mirall-1.4.2-1.fc19.x86_64, owncloud-csync-libs-0.90.4-1.fc19.x86_64

Run owncloud. Performed a sync. Stable after 3 mins - usually crahsed after ~30seconds. Copy a file within sync area. It uploads then crashed after completing sync. Another machine then picked up the new sync'd file. owncloud again crashed after updating. Also running fc19 64bit.

Running under KDE.
Note my owncloud server is,
owncloud 5.0.11-028
running on NAS server synology DS213 (ARM processor based not that should matter).
Perhaps this relates to difference between 4.5 and 5.0 own cloud server?

Related bug 1010740, filed by other crashes from me.

[  275.489664] QThread[2720]: segfault at 3d ip 000000345268043c sp 00007ff955e014a8 error 4 in libc-2.17.so[3452600000+1b6000]
[  339.302298] QThread[2893]: segfault at 5d ip 000000345268043c sp 00007f7ca37fd4a8 error 4 in libc-2.17.so[3452600000+1b6000]
[  962.652219] traps: QThread[3156] general protection ip:3475c15e20 sp:7f7f92b844a8 error:0 in libgmp.so.10.1.1[3475c00000+6d000]

There's a patch available now:
https://github.com/owncloud/mirall/issues/1115
https://github.com/owncloud/mirall/commit/14081a197b3f048bc18a68d408f13ecce61638b9

I will create a package this night containing the patch. The system will let you know when you guys can test it. Thank you for all reports.

Created attachment 823910 [details]
Patch to backport commit 14081a1 to 1.4.2

Since the proposed fixing commit 14081a1 depends on some pre-v1.4.2 code, I created a patch to backport the commit to v.1.4.2.

I could not test the outcome of the commit itself very deep, but for me it seems like the segfault does not occur anymore.

(In reply to Manuel Faux from comment #16)
> Since the proposed fixing commit 14081a1 depends on some pre-v1.4.2 code, I
> created a patch to backport the commit to v.1.4.2.

Of cause I meant post-v1.4.2 code.

If someone wants to test it:
http://copr-fe.cloud.fedoraproject.org/coprs/faux/mirall/

I am testing it. It seems stable so far. I can not be sure just yet. After the sync has been completed it used to crash. I will update when the sync is completed.

I have not yet made it kaput. Seems stable.

My client also runs stable since I posted the patch. Synced several times and still up and running.

Hope Joseph can build a package soon, to push it to the official repo asap.

Sorry for my super delay, I am in the middle of a batch of testings and projects from my University(all the professors seem to confabulate and give the assignments at the same time as always).

Thank you very much for creating the package I will do my best to push it to the official repos this afternoon/night when I get home.

Again sorry for the delay.

mirall-1.4.2-3.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/mirall-1.4.2-3.fc19

mirall-1.4.2-3.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/mirall-1.4.2-3.fc18

mirall-1.4.2-3.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/mirall-1.4.2-3.fc20

It hasn't crashed yet.  For some reason it downloaded all the files again the first time I started it up.  However, the icon has disappeared so I have no idea what it is doing now...  I guess I'll kill it and start it again.

Problem still exists in mirall-1.4.2-3.fc19. It segfaults within a minute of starting.

(In reply to Chris from comment #26)
> Problem still exists in mirall-1.4.2-3.fc19. It segfaults within a minute of
> starting.

I apologize; ignore me. I misread my version number. I do not yet have the current update, so my tests are irrelevant.

My last comment must have just been a random issue with my system.  The client has been running all night now with no crashes.

(In reply to Samuel Sieb from comment #28)
> My last comment must have just been a random issue with my system.  The
> client has been running all night now with no crashes.

I concur; after installing the correct packages, I too see stability in the application.

Package mirall-1.4.2-3.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing mirall-1.4.2-3.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-21438/mirall-1.4.2-3.fc18
then log in and leave karma (feedback).

mirall-1.4.2-3.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

mirall-1.4.2-3.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

mirall-1.4.2-3.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.