https://bugs.kde.org/show_bug.cgi?id=510126
Bug ID: 510126
Summary: Can't login any more - "Access token not found: Maybe
it was deleted?"
Classification: Applications
Product: NeoChat
Version First 25.08.1
Reported In:
Platform: Debian stable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: General
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected]
Target Milestone: ---
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
--
You are receiving this mail because:
You are watching all bug changes.
