https://bugs.kde.org/show_bug.cgi?id=524522
michaelk83 <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #17 from michaelk83 <[email protected]> --- (In reply to decagon82 from comment #13) > One question that may be useful for debugging: could the relevant Secret > Service/D-Bus request made immediately before the crash be logged or > otherwise traced, so that we can identify which client/request (e.g. > Chromium) triggers KWalletFreedesktopService::GetSecrets()? You could run dbus-monitor before the crash (e.g. on startup) and add timestamps so you could compare to the crash time. But I don't think it matters what the client is - once the call is made, the result will be the same. And we can already see from the traces that the crashing call is to either `KWalletFreedesktopService::GetSecrets()` or `KWalletFreedesktopItem::GetSecret()` (they both go through the same code path). Those correspond directly to `Service.GetSecrets` and `Item.GetSecret` API calls. The duplicate reports also had `KWalletFreedesktopCollection::CreateItem()` crashing in the same place (a `Collection.CreateItem` API call). The reports mention a few different clients: Bitwarden Desktop, secret-tool, Chromium (your report). Per comment 11, this is already fixed with the latest QCA, so I think we just need to tag a new version of it until the migration to Botan is finished in https://invent.kde.org/frameworks/kwallet/-/merge_requests/148 . -- You are receiving this mail because: You are watching all bug changes.
