https://bugs.kde.org/show_bug.cgi?id=521267
--- Comment #2 from [email protected] --- I think I more or less understand what is going on. The schema used by qtkeychain in libsecret has the following fields: server: neochat type: base64 user: @user:server.org xdg:schema: org.qt.keychain There is nothing unique here about the device. So both computers do actually use the same entry with the same secret. And I guess that the secret is what determines the device id. In fact, I can see from the debug logs the following: quotient.main: Using server "https://example.org"; by user "@user:example.org" from device "NNNNNNNNNN" However, the $HOME/.config/KDE/neochat.conf contains the following: %40user%3Aexample.org\device_id=OOOOOOOOOO Looks like the originally registered device is ignored and instead the one associated with the secret token is used? Probably a "cheap" way to fix this is to append the device at registration time as part of the the secret schema. Maybe with a @user:server.org-deviceID string or something similar. Ironically this seems to be the mechanism that Quaternion is using in the "legacy mode": https://github.com/quotient-im/Quaternion/blob/dev/client/mainwindow.cpp#L849. I wonder why that behaviour is not the default anymore... -- You are receiving this mail because: You are watching all bug changes.
