Bug 136094

Summary: assigning wallets to applications
Product: [Unmaintained] kdelibs Reporter: Janet <bugzilla>
Component: kwalletAssignee: kdelibs bugs <kdelibs-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: mk.mateng, Thorsten_Reichelt
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Janet 2006-10-21 17:03:08 UTC
Version:            (using KDE KDE 3.5.4)
Installed from:    Debian testing/unstable Packages
OS:                Linux

Please make it possible to assign wallets to applications (or vice-versa). It is possible to create new wallets but you cannot use them in a reasonable way. E.g. I'd love to set up a passwordless wallet for kmail (Bug 97925) and maybe kopete. This is not possible. I created a new wallet and put the entries for those two apps from the original wallet into that one (drag and drop). But the apps expect the entries to be in the original wallet. I even tried to enable the new wallet for storing local passwords - but kmail and kopete passwords are not treated as local (in my eyes they are *somehow* because I enter them locally and not on websites). So for urging kmail to use the second and passwordless wallet I always have to switch wallets in kcontrol before I use kmail. That's as annoying as being asked for the wallet password nearly everytime I check my mail.

I'd expect to be able to maybe rightclick on a new wallet and am able to choose which applications I want to assign to it. Or that the passwords using applications somehow see in which wallet I have copied their passwords and from  then on just use that wallet instead of the standard wallet.
Comment 1 George Staikos 2006-10-21 18:50:44 UTC
There is nothing preventing the application from doing this.
Comment 2 Michael Leupold 2009-03-27 20:21:50 UTC
*** Bug 188278 has been marked as a duplicate of this bug. ***
Comment 3 michaelk83 2022-09-06 15:42:55 UTC
This one is older, but Bug 228308 is more detailed.

*** This bug has been marked as a duplicate of bug 228308 ***