Red Hat Bugzilla – Bug 1024973
[abrt] mirall-1.4.1-1.fc19: __gmpz_clear: Process /usr/bin/owncloud was killed by signal 11 (SIGSEGV)
Last modified: 2013-12-13 22:53:25 EST
Version-Release number of selected component:
runlevel: N 5
var_log_messages: Oct 30 16:42:35 rb11 abrt: Saved core dump of pid 10288 (/usr/bin/owncloud) to /var/tmp/abrt/ccpp-2013-10-30-16:42:34-10288 (83787776 bytes)
Thread no. 1 (10 frames)
#0 __gmpz_clear at ../../mpz/clear.c:28
#1 mp_clear_multi at multi.c:38
#2 ecc_del_point at ecc_points.c:62
#3 _ecc_wmnaf_cache_entry_free at ecc_mulmod_cached.c:55
#4 ecc_wmnaf_cache_free at ecc_mulmod_cached.c:70
#5 gnutls_crypto_deinit at init.c:44
#6 gnutls_global_deinit at gnutls_global.c:304
#7 ne__ssl_exit at ne_gnutls.c:1433
#8 ne_sock_exit at ne_socket.c:372
#9 owncloud_commit at /usr/src/debug/ocsync-0.90.2/modules/csync_owncloud.c:1752
Potential duplicate: bug 1022847
Created attachment 817522 [details]
Created attachment 817523 [details]
Created attachment 817524 [details]
Created attachment 817525 [details]
Created attachment 817526 [details]
Created attachment 817527 [details]
Created attachment 817528 [details]
Created attachment 817529 [details]
Created attachment 817530 [details]
Created attachment 817531 [details]
put new files in the folder synchronised with the desktop sync client, a short while later it crashed
cmdline: /usr/bin/owncloud -session 1028622b2541e2000138040420900000092220007_1383039904_184508
reason: Process /usr/bin/owncloud was killed by signal 11 (SIGSEGV)
runlevel: N 5
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,
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: segfault at 3d ip 000000345268043c sp 00007ff955e014a8 error 4 in libc-2.17.so[3452600000+1b6000]
[ 339.302298] QThread: segfault at 5d ip 000000345268043c sp 00007f7ca37fd4a8 error 4 in libc-2.17.so[3452600000+1b6000]
[ 962.652219] traps: QThread general protection ip:3475c15e20 sp:7f7f92b844a8 error:0 in libgmp.so.10.1.1[3475c00000+6d000]
There's a patch available now:
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:
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.
mirall-1.4.2-3.fc18 has been submitted as an update for Fedora 18.
mirall-1.4.2-3.fc20 has been submitted as an update for Fedora 20.
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
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.
* 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:
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.