Description of problem: 1. started owncloud client from the command line 2. entered my server, https://example.com/owncloud/ 3. provided correct username but wrong password 4. changed window to get the correct password 5. owncloud crashed in the meantime Version-Release number of selected component: mirall-1.5.3-2.fc19 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: owncloud crash_function: Mirall::Account::state executable: /usr/bin/owncloud kernel: 3.13.9-100.fc19.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:5010 #9 on_pending_call_notify at gkr-operation.c:416 Potential duplicate: bug 1086993
Created attachment 888582 [details] File: backtrace
Created attachment 888583 [details] File: cgroup
Created attachment 888584 [details] File: core_backtrace
Created attachment 888585 [details] File: dso_list
Created attachment 888586 [details] File: environ
Created attachment 888587 [details] File: exploitable
Created attachment 888588 [details] File: limits
Created attachment 888589 [details] File: maps
Created attachment 888590 [details] File: open_fds
Created attachment 888591 [details] File: proc_pid_status
Created attachment 888592 [details] File: var_log_messages
*** This bug has been marked as a duplicate of bug 1086993 ***