Description of problem: Bad password on first login Version-Release number of selected component: mirall-1.5.3-2.fc20 Additional info: reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: owncloud crash_function: Mirall::Account::state executable: /usr/bin/owncloud kernel: 3.13.8-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 Mirall::Account::state at /usr/src/debug/mirall-1.5.3/src/mirall/account.cpp:302 #1 Mirall::HttpCredentials::queryPassword at /usr/src/debug/mirall-1.5.3/src/creds/httpcredentials.cpp:269 #2 Mirall::HttpCredentials::slotReadJobDone at /usr/src/debug/mirall-1.5.3/src/creds/httpcredentials.cpp:256 #3 QMetaObject::activate at kernel/qobject.cpp:3547 #4 QKeychain::Job::finished at /usr/src/debug/qtkeychain-0.3.0/build/moc_keychain.cxx:102 #5 QKeychain::Job::emitFinished at /usr/src/debug/qtkeychain-0.3.0/keychain.cpp:56 #6 QKeychain::Job::emitFinishedWithError at /usr/src/debug/qtkeychain-0.3.0/keychain.cpp:64 #7 QKeychain::ReadPasswordJobPrivate::gnomeKeyring_cb at /usr/src/debug/qtkeychain-0.3.0/keychain_unix.cpp:123 #8 find_unlocked_1_reply at gnome-keyring.c:5012 #9 on_pending_call_notify at gkr-operation.c:416
Created attachment 885706 [details] File: backtrace
Created attachment 885707 [details] File: cgroup
Created attachment 885708 [details] File: core_backtrace
Created attachment 885709 [details] File: dso_list
Created attachment 885710 [details] File: environ
Created attachment 885711 [details] File: exploitable
Created attachment 885712 [details] File: limits
Created attachment 885713 [details] File: maps
Created attachment 885714 [details] File: open_fds
Created attachment 885715 [details] File: proc_pid_status
Created attachment 885716 [details] File: var_log_messages
*** Bug 1090143 has been marked as a duplicate of this bug. ***
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.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Another user experienced a similar problem: This issue was seen after completing the setup wizard for OwnCloud on Fedora 20 running the 3.17 kernel. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: owncloud crash_function: Mirall::Account::state executable: /usr/bin/owncloud kernel: 3.17.6-200.fc20.i686+PAE package: mirall-1.5.4-2.fc20 reason: owncloud killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
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.