Description of problem: Tried to add a folder sync, folders in the cloud were not listed, so I clicked on the "Sign in" button, then a list of folders appeared and crash happened. Version-Release number of selected component: mirall-1.5.3-2.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: owncloud crash_function: QString::startsWith executable: /usr/bin/owncloud kernel: 3.15.0-0.rc3.git1.2.fc21.i686 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 QString::startsWith at tools/qstring.cpp:3480 #1 Mirall::FolderWizardRemotePath::isComplete at /usr/src/debug/mirall-1.5.3/src/mirall/folderwizard.cpp:382 #2 _q_updateCachedCompleteState at dialogs/qwizard.cpp:508 #3 QWizardPage::qt_static_metacall at .moc/release-shared/moc_qwizard.cpp:306 #4 QMetaObject::activate at kernel/qobject.cpp:3547 #5 QWizardPage::completeChanged at .moc/release-shared/moc_qwizard.cpp:384 #6 QWizardPage::qt_static_metacall at .moc/release-shared/moc_qwizard.cpp:304 #7 QMetaObject::activate at kernel/qobject.cpp:3547 #8 QTreeWidget::itemClicked at .moc/release-shared/moc_qtreewidget.cpp:220 #9 QTreeWidgetPrivate::_q_emitItemClicked at itemviews/qtreewidget.cpp:2241
Created attachment 892386 [details] File: backtrace
Created attachment 892387 [details] File: cgroup
Created attachment 892388 [details] File: core_backtrace
Created attachment 892389 [details] File: dso_list
Created attachment 892390 [details] File: environ
Created attachment 892391 [details] File: exploitable
Created attachment 892392 [details] File: limits
Created attachment 892393 [details] File: maps
Created attachment 892394 [details] File: open_fds
Created attachment 892395 [details] File: proc_pid_status
Created attachment 892396 [details] File: var_log_messages
I can not update any of my packages for the time being, will know If I can continue contributing in about a month. I can pass the ownership to who ever wants to maintain it or I we can share ownerships if I can still contributing. But will not know my status until august 1st is my best guess.
(In reply to Joseph Marrero from comment #12) > I can not update any of my packages for the time being, will know If I can > continue contributing in about a month. I can pass the ownership to who ever > wants to maintain it or I we can share ownerships if I can still > contributing. But will not know my status until august 1st is my best guess. Thanks for letting me know! More than contributing to mirall I'm starting to think about writing some different client that wouldn't take so much CPU and RAM. Example: 55 hours on CPU and 100 MB RAM on my netbook running three days, owncloud being the second biggest process right after firefox. I believe that's not necessary. Also a CLI is missing.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.