Description of problem: I was stepping though the configuration settings for a second sync folder during the initial connection to a freshly installed ownCloud 5 server (may be beta). The options were a bit confusing as far as folder names and locations are concerned so I may have done something illegal in my conventions. This client app doesn't want to start now so I have to try and reset it. Version-Release number of selected component: owncloud-client-1.2.1-2.fc18 Additional info: backtrace_rating: 4 cmdline: owncloud crash_function: csync_vio_set_property executable: /usr/bin/owncloud kernel: 3.8.2-206.fc18.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 csync_vio_set_property at /usr/src/debug/ocsync-0.70.4/src/vio/csync_vio.c:654 #1 csync_init at /usr/src/debug/ocsync-0.70.4/src/csync.c:333 #2 Mirall::CSyncThread::startSync at /usr/src/debug/mirall-1.2.1/src/mirall/csyncthread.cpp:364 #3 QObject::event at kernel/qobject.cpp:1194 #4 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:4562 #5 QApplication::notify at kernel/qapplication.cpp:4423 #6 QCoreApplication::notifyInternal at kernel/qcoreapplication.cpp:946 #7 sendEvent at kernel/qcoreapplication.h:231 #8 QCoreApplicationPrivate::sendPostedEvents at kernel/qcoreapplication.cpp:1570 #9 sendPostedEvents at kernel/qcoreapplication.h:236
Created attachment 711163 [details] File: backtrace
Created attachment 711164 [details] File: cgroup
Created attachment 711165 [details] File: core_backtrace
Created attachment 711166 [details] File: dso_list
Created attachment 711167 [details] File: environ
Created attachment 711168 [details] File: limits
Created attachment 711169 [details] File: maps
Created attachment 711170 [details] File: open_fds
Created attachment 711171 [details] File: proc_pid_status
Created attachment 711172 [details] File: var_log_messages
I may have ignorantly created a loop by syncing a folder to itself which I didn't try to duplicate. Things seem to be working okay now.
owncloud-csync-0.70.5-1.fc17,mirall-1.2.3-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/owncloud-csync-0.70.5-1.fc17,mirall-1.2.3-1.fc17
owncloud-csync-0.70.5-1.fc18,mirall-1.2.3-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/owncloud-csync-0.70.5-1.fc18,mirall-1.2.3-1.fc18
owncloud-csync-0.70.5-1.fc19,mirall-1.2.3-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/owncloud-csync-0.70.5-1.fc19,mirall-1.2.3-1.fc19
Package owncloud-csync-0.70.5-1.fc19, mirall-1.2.3-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing owncloud-csync-0.70.5-1.fc19 mirall-1.2.3-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-4918/owncloud-csync-0.70.5-1.fc19,mirall-1.2.3-1.fc19 then log in and leave karma (feedback).
owncloud-csync-0.70.6-1.fc18,mirall-1.2.4-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/owncloud-csync-0.70.6-1.fc18,mirall-1.2.4-1.fc18
owncloud-csync-0.70.6-1.fc17,mirall-1.2.4-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/owncloud-csync-0.70.6-1.fc17,mirall-1.2.4-1.fc17
owncloud-csync-0.70.5-1.fc19, mirall-1.2.3-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
owncloud-csync-0.70.6-1.fc17, mirall-1.2.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.
owncloud-csync-0.70.6-1.fc18, mirall-1.2.4-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.