https://bugs.kde.org/show_bug.cgi?id=521267
michaelk83 <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #3 from michaelk83 <[email protected]> --- Rather than changing the schema, the device could be encoded as part of the "server" value: "neochat:NNNNNNNNNN". But you will likely find similar issues with nearly any Secret Service client app when trying to use different accounts on different machines. The normal expectation is that the keyring is local to the machine. On KeePassXC's end, it could offer the ability to expose a different group on different devices, similar to its AutoOpen capability. But I often recommend using a separate database for Secret Service, and you can already use separate local databases for your two devices. -- You are receiving this mail because: You are watching all bug changes.
