https://bugs.kde.org/show_bug.cgi?id=228308
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=228308
--- Comment #14 from michaelk83 ---
That said, and especially assuming most apps would use the default collection
anyway, the backend can choose to ignore the selected collection, and re-route
`CreateItem()` requests as it sees fit. That somewhat breaks
https://bugs.kde.org/show_bug.cgi?id=228308
--- Comment #13 from michaelk83 ---
(In reply to michaelk83 from comment #12)
> Furthermore, the plan is to migrate the KDE apps to QtKeyChain, which AFAIK
> just uses the default collection and doesn't provide an API for specifying
> which collection t
https://bugs.kde.org/show_bug.cgi?id=228308
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=228308
--- Comment #12 from michaelk83 ---
(In reply to michaelk83 from comment #9)
> Related to Bug 451039 comment 2.
On 2nd thought, with the Secret Secret API (KWallet Framework 5.97.0+), it's up
to each application to specify which collection (wallet) it w
https://bugs.kde.org/show_bug.cgi?id=228308
michaelk83 changed:
What|Removed |Added
CC||bugzi...@kerridis.de
--- Comment #11 from michaelk
https://bugs.kde.org/show_bug.cgi?id=228308
michaelk83 changed:
What|Removed |Added
Summary|Applications only check |Control which application
|defau
