When KWallet opened the first time, I thought I could just use my login password to open it. It rejected the password as "incorrect" even though I never had the chance to set it up in the first place. I read over the documentation saying how this was supposed to work, and the sense that I got was, "In theory, yes, but not in my case." It pops up whenever I open Google and asks for my password, but the supposed setup module that is supposed to guide me through the process apparently is incompatible with my build of Kubuntu (Black Lab). Since I did not purchase any dev support, I will just have to figure out how this is supposed to work on my own, which is how I've happened to get through most of my early stage familiarity issues (I am new to Linux, having grown frustrated with the Windows "architecture." I would like to finally be able to set up my KWallet password for once, so if anyone could help me figure out why this isn't happening in my platform, I would appreciate it.
>When KWallet opened the first time, I thought I could just use my login password to open it. It rejected the password as "incorrect" even though I never had the chance to set it up in the first place Are you sure it was the first time you opened it? If it asks for a password, then it means a wallet was already setup. >but the supposed setup module that is supposed to guide me through the process apparently is incompatible with my build of Kubuntu (Black Lab). That is impossible. The 'setup module' can be found inside kwalletmanager ("File > New Wallet"). >I would like to finally be able to set up my KWallet password for once, so if anyone could help me figure out why this isn't happening in my platform, I would appreciate it. If you have never stored any passwords in kwallet, then you could use kwalletmanager to delete all the currently existing wallets and then create a new one.
There has been no visible activity on this issue for three years. Can this ticket be closed?
This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.