SUMMARY This started to happen on Tails 6.19 (debian 12, gnome) and persists in 7.0 (debian 13, gnome) with the neochat stable flatpak. It first occurred in the days prior to the Tails 7.0 release, that is prior to september 18, after an update to either one of the dependencies of neochat or after an update to the neochat flatpak itself. Logging in automatically to an existing matrix account worked flawlessly until said update. First symptom was the message "The login keyring did not get unlocked when you logged into the computer." After typing in the password and unlocking the keyring neochat says "Access token not found: Maybe it was deleted?". I made sure the correct keyring gets unlocked, checked it with seahorse. Unlocked it manually from there before starting neochat, too. In that case only the second error message appears ("Access token not found: Maybe it was deleted?"). The neochat login token is present in the login keychain. Rolling back to a backup complete system image from times prior to the issue occurrence resolves the problem. And after doing a "flatpak update" on the backup image the problem reproducibly reappears. STEPS TO REPRODUCE 1. Start Tails 2. Install neochat flatpak (torsocks flatpak install neochat) and dependencies from a few weeks before sept 18 3. Start neochat, configure for use with tor (set socks5 proxy) and log in to existing matrix account 4. Issue "torsocks flatpak update" 5. Start neochat OBSERVED RESULT Can't login any more - "Access token not found: Maybe it was deleted?" ADDITIONAL INFORMATION I ran into the bug that made neochat 25.08.0 unusable (did not start - saw a bug report on here, too). After you guys released another update it worked again. So that would be the last version I used successfully. Thus the issue seems to have appeared first between Aug 14 and Sep 18. SOFTWARE/OS VERSIONS Tails 6.19, Tails 7.0
Last known working version: $ flatpak info org.kde.neochat NeoChat - Chat on Matrix ID: org.kde.neochat Ref: app/org.kde.neochat/x86_64/stable Arch: x86_64 Branch: stable Version: 25.08.0 License: GPL-3.0 Origin: flathub Collection: org.flathub.Stable Installation: user Installed: 20.1 MB Runtime: org.kde.Platform/x86_64/6.9 Sdk: org.kde.Sdk/x86_64/6.9 Commit: 51790d2353dc70026c5828538c5dfc422ccdf6caeff42c8d809a8dd78dcdabe6 Parent: 6e11cd7d325a98220b1084b6ed759918fc1b206fe07da0930d9cade5b46f66b7 Subject: Revert usage of excessively new Kirigami API (#132) (00013fefb9f6) Date: 2025-08-18 02:22:32 +0000
The last known working version of neochat works on Tails 7.0 and Tails 7.1. Thus, the issue is not caused by a change in Tails. The issue most certainly comes from either neochat or one of its dependencies.
(In reply to Carlos Santana Gutierrez from comment #0) > Logging in automatically to an existing matrix account worked flawlessly > until said update. First symptom was the message "The login keyring did not > get unlocked when you logged into the computer." After typing in the > password and unlocking the keyring neochat says "Access token not found: > Maybe it was deleted?". I've had the same behavior (2nd message, "Access token not found: Maybe it was deleted?") on KDE Neon with Neochat as a system package. > neochat[12696]: Reading access token from the keychain for "@omega16:tchncs.de" > kwalletd6[1995]: kf.wallet.kwalletd: "Item not found" > kwalletd6[1995]: kf.wallet.kwalletd: "Entry not found, key: @omega16:tchncs.de, folder: neochat" Logout of the account and login fresh just solved this for me for now. Unfortunately I did not track, on which version (upgrade) it occured. SOFTWARE/OS VERSIONS NeoChat: 25.08.2 KDE neon User Edition (Wayland) libQuotient: 0.9.5 (built against 0.9.5) KDE Frameworks: 6.19.0 Qt: Using 6.9.2 and built against 6.9.2 Unknown/Default Build ABI: x86_64-little_endian-lp64 Kernel: linux 6.14.0-34-generic
Unfortunately figuring out these keychain problems isn't always easy, due to the many variable parts playing together here. Since it's working for you now, I'm going to mark this as resolved - debugging it now would be practically impossible. Please open a new ticket if you see similar problems again (or comment in this one, if you get the exact same problem again!) BTW: Thanks for the very good bug report and the extensive research! :)