Bug 342148

Summary: Failed to sync wallet kdewallet to disk: RC-3
Product: [Applications] kwalletmanager Reporter: Antonio Trindade <toze>
Component: generalAssignee: Valentin Rusu <valir>
Status: REPORTED ---    
Severity: grave CC: arjunak234, pcchou, rdieter
Priority: NOR    
Version: 2.0   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:

Description Antonio Trindade 2014-12-23 10:46:40 UTC
When i create a wallet, KDE opens the existent one or any application writes something on it it returns:
"Failed to sync wallet kdewallet to disk. Error codes are: RC -3 SF Unknown error. Please file a BUG report using this information to bugs.kde.org"

Reproducible: Always

Steps to Reproduce:
1. Delete KDE wallet
2. Create a new wallet



The changes on my system was the upgrade from FC20 to FC21
Comment 1 pcchou 2014-12-23 14:24:33 UTC
I'm a google code-in who is trying to do bug triaging task.
Can you provide which version that you're using?
Comment 2 Antonio Trindade 2014-12-23 14:34:47 UTC
Hello,

$ kwalletmanager -v
Qt: 4.8.6
KDE Development Platform: 4.14.3
KDE Wallet Manager: 2.0

something that i notice, is that file ~/.kde/share/apps/kwallet/kdewallet.kwl is a 0 bytes file
Comment 3 Arjun AK 2014-12-28 11:38:37 UTC
Thanks for the report, but unfortunately i can't reproduce it.

>1. Delete KDE wallet

Was it the wallet named "kdewallet" that you deleted?

>2. Create a new wallet

What was the new wallet's name?
Comment 4 Antonio Trindade 2014-12-30 11:18:59 UTC
Hello,

yes, i deleted the kdewallet.

The new one i call it mywallet and that works fine

After that i delete "mywallet" and create a new one, and the error raised again. I did the same and created 2 wallets, "mywallet" and kdewallet and things look OK now, but if i recreate only the kdewallet the error reaises again.
Comment 5 Christoph Feck 2015-01-15 01:56:00 UTC
Thanks for the update, changing status.
Comment 6 Justin Zobel 2021-03-10 00:32:48 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.