- Change Summary:
-
Cleaned up some debugging
Fixed the UI name look up stuff
Removed the fast fail from read_password_async as it was causing prompts as we were unlocking the wallet. - Testing Done:
-
~ - connected account, didn't save password, made sure it connected and wasn't stored in kwalletmanager5
~ - connected account, saved password, made sure it connected and verified the password was stored in kwalletmanager5
~ - reconnected account, made sure the account connected without prompting
~ - reopened pidgin, made sure the account connected without prompting.
~ - removed the account and verified the password was removed from kwalletmanager5
~ - connected account with wallet locked, verified that we weren't prompted for a password until the wallet was unlocked.
~ - connected account, didn't save password, made sure it connected and wasn't stored in kwalletmanager5
~ - connected account, saved password, made sure it connected and verified the password was stored in kwalletmanager5
~ - reconnected account, made sure the account connected without prompting
~ - reopened pidgin, made sure the account connected without prompting.
+ - removed the account and verified the password was removed from kwalletmanager5
- Commit:
-
23549e4200f62f7f636c3af5
- Diff:
-
Revision 2 (+687 -500)
Port the KWallet Keyring to the new CredentialProvider API.
Review Request #575 — Created March 19, 2021 and submitted
Port the KWallet Keyring to the new CredentialProvider API.
- connected account with wallet locked, verified that we weren't prompted for a password until the wallet was unlocked.
- connected account, didn't save password, made sure it connected and wasn't stored in kwalletmanager5
- connected account, saved password, made sure it connected and verified the password was stored in kwalletmanager5
- reconnected account, made sure the account connected without prompting
- reopened pidgin, made sure the account connected without prompting.
- disconnected pidgin from kwalletmanager5, re-connected account, verified it reconnected via debug and kwalletmanager5
- force closed the wallet in kwalletmanager5, re-connected account, unlocked wallet, verified no password prompts and that the account connected.
- removed the account and verified the password was removed from kwalletmanager5
Description | From | Last Updated |
---|---|---|
g_task_return_new_error |
QuLogic | |
failed to read |
QuLogic | |
The only place error would be set would be in the above if; why split this in two and not … |
QuLogic | |
g_task_return_new_error |
QuLogic | |
Again, why split this from the if(result != 0)? And then can use g_task_return_new_error. |
QuLogic | |
g_task_return_new_error |
QuLogic | |
Combine with if(result != 0) and use g_task_return_new_error. |
QuLogic | |
g_task_return_new_error |
QuLogic | |
You've been using C++ false/true; is true equal to false, or can you not use if(this->connected) {? |
QuLogic | |
Should the queue be cleared when closing? |
QuLogic | |
Should you only open if there's something in the queue? |
QuLogic | |
Since Request takes a ref, should you unref task at the end of this function? |
QuLogic | |
Since Request takes a ref, should you unref task at the end of this function? |
QuLogic | |
Since Request takes a ref, should you unref task at the end of this function? |
QuLogic | |
Do you need a default if the wrapper checks klass->activate before calling it? |
QuLogic | |
Not changed here, but this should be startup. |
QuLogic | |
Shuts down |
QuLogic |
- Change Summary:
-
Fix a bug where we didn't try to re-open the wallet when it was closed externally.
- Testing Done:
-
- connected account with wallet locked, verified that we weren't prompted for a password until the wallet was unlocked.
- connected account, didn't save password, made sure it connected and wasn't stored in kwalletmanager5
- connected account, saved password, made sure it connected and verified the password was stored in kwalletmanager5
- reconnected account, made sure the account connected without prompting
- reopened pidgin, made sure the account connected without prompting.
~ - removed the account and verified the password was removed from kwalletmanager5
~ - disconnected pidgin from kwalletmanager5, re-connected account, verified it reconnected via debug and kwalletmanager5
+ - force closed the wallet in kwalletmanager5, re-connected account, unlocked wallet, verified no password prompts and that the account connected.
+ - removed the account and verified the password was removed from kwalletmanager5
- Commit:
-
2f7f636c3af5e52ea7a75df3
- Diff:
-
Revision 3 (+686 -500)
- Change Summary:
-
Implemented the cancel functions.
- Commit:
-
e52ea7a75df372213898daa9
- Diff:
-
Revision 4 (+708 -500)
- Change Summary:
-
fixed up issues in review and added some debug output for when we fail to read a password because I got stuck in some tricky debugging situations.
- Commit:
-
72213898daa9d6c171ac8b21
- Diff:
-
Revision 5 (+737 -507)
- Change Summary:
-
remove the unnecessary default implementations
- Commit:
-
d6c171ac8b2148fd16c109c4
- Diff:
-
Revision 6 (+722 -507)