Version-Release number of selected component: owncloud-client-1.0.5-5.fc17 Additional info: libreport version: 2.0.13 abrt_version: 2.0.12 backtrace_rating: 4 cmdline: owncloud crash_function: __gconv kernel: 3.5.3-1.fc17.x86_64 truncated backtrace: :Thread no. 1 (8 frames) : #0 __gconv at gconv.c : #1 iconv at iconv.c : #2 QIconvCodec::convertFromUnicode at codecs/qiconvcodec.cpp : #3 QTextCodec::fromUnicode at codecs/qtextcodec.cpp : #4 QString::toLocal8Bit at tools/qstring.cpp : #5 ~QDebug at /usr/include/QtCore/qdebug.h : #6 Mirall::CSyncThread::run at /usr/src/debug/mirall-1.0.5/src/mirall/csyncthread.cpp : #7 QThreadPrivate::start at thread/qthread_unix.cpp
Created attachment 616509 [details] File: core_backtrace
Created attachment 616510 [details] File: environ
Created attachment 616511 [details] File: backtrace
Created attachment 616512 [details] File: limits
Created attachment 616513 [details] File: cgroup
Created attachment 616514 [details] File: maps
Created attachment 616515 [details] File: dso_list
Created attachment 616516 [details] File: var_log_messages
Created attachment 616517 [details] File: open_fds
New Version of mirall/owncloudclient and owncloud-csync has been released, currently I am testing it in my machine, In a about two days it should be in the testing repositories. SO far all sagfault errors have been corrected, the bad news is that the new sync client only works with owncloud server 4.5 and up. So if you are in a owncloud server < 4.5 you should stick with the current owncloud client until the 1.1 version works with the older servers or you upgrade to 4.5 owncloud.
mirall-1.1.0-1.fc17,owncloud-csync-0.60.0-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/mirall-1.1.0-1.fc17,owncloud-csync-0.60.0-1.fc17
mirall-1.1.0-1.fc18,owncloud-csync-0.60.0-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/mirall-1.1.0-1.fc18,owncloud-csync-0.60.0-1.fc18
Package mirall-1.1.0-1.fc18, owncloud-csync-0.60.0-1.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.1.0-1.fc18 owncloud-csync-0.60.0-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-16122/mirall-1.1.0-1.fc18,owncloud-csync-0.60.0-1.fc18 then log in and leave karma (feedback).
New version released upstream you should have it by Sunday/monday in the testing repos. > The most important changes: > > * [GUI] Allow changing folder name in single folder mode > * [GUI] Windows: Add license to installer > * [GUI] owncloud ?logwindow will bring up the log window in an already running instance > * [Fixes] Make sure SSL errors are always handled > * [Fixes] Allow special characters in folder alias > * [Fixes] Proper workaround for Menu bug in Ubuntu > * [Fixes] csync: Fix improper memory cleanup which could cause memory leaks and crashes > * [Fixes] csync: Fix memory leak > * [Fixes] csync: Allow single quote (?) in file names > * [Fixes] csync: Remove stray temporary files I hope this fixes the new crashes
owncloud-csync-0.60.1-1.fc17,mirall-1.1.1-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/owncloud-csync-0.60.1-1.fc17,mirall-1.1.1-1.fc17
owncloud-csync-0.60.1-1.fc18,mirall-1.1.1-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/owncloud-csync-0.60.1-1.fc18,mirall-1.1.1-1.fc18
owncloud-csync-0.60.3-1.fc18,mirall-1.1.3-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/owncloud-csync-0.60.3-1.fc18,mirall-1.1.3-1.fc18
owncloud-csync-0.60.4-1.fc17,mirall-1.1.4-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/owncloud-csync-0.60.4-1.fc17,mirall-1.1.4-1.fc17
owncloud-csync-0.60.4-1.fc17, mirall-1.1.4-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.