Open slrslr opened 9 months ago
Sounds like it could be some user config issue with different user configs being shared between linked devices and removing you from the group. Do you have any linked devices and which version of Session are they on?
Do you have any linked devices
@KeeJef Before around 5 months, around 1-2 times I have tried to "login" same Session ID with same application data as i am using now and i have tried to do it under different Linux operating system or use recovery key to download my Session profile, i do not remember which way I did it (app data or recovery phrase). But in all such cases, it never loaded conversations list due to insufficient internet speed. Since that time I am using Session on one device only - Linux Debian 11 with KDE, Session AppImage.
I have added a community, shutdown Session, start it to see community disappear from the conversations a few second after start. Then i shutdown session and here are the log lines. Pass-word is the codename of this month Oxen 10.4.0 update (two words), lines containing blinded IDs were removed. File expires in 1 year.
Okay, tracking this one internally as https://optf.atlassian.net/browse/SES-1453
One observation. This issue (removal of certain communities at Session start) does NOT happen to communities that was added to Session long time ago and then removed/added in current release/s, but the bug happens only to these that was first time added recently in recent and a few older releases.
If you need it in another words/detail, then today under v1.12.0 I have added 5 communities.
1 Caliban community that i have possibly never added has this bug. But other 2 from same server that i had in Session for like 1 year and removed these recently in previous release or one before it, these does not have this bug (remains in Session after its restart).
Other servers communities (https://oddch.at/reports?public_key=21319aef2f7ebf5ddda52e8fb440790cb5d5ceb0d1707e9cf512317b7924bc70 and http://157.230.25.186/music?public_key=31e9a433530ac82b0740065c4ab17022162cb2e0315b3857a96de752a5027206) that i have found recently and have added these in current release or the one before it has this bug (are being removed on next session start).
Code of conduct
Self-training on how to write a bug report
Is there an existing issue for this?
Current Behavior
Any community like "Report Abuse Here" found at https://sessioncommunities.online/#reports+21317dc3 when added/joined and Session exit/start, i can see that after a start it gets removed within a few seconds from the Conversations list and i need to join it again (with success), yet it again disappear after restart.
Expected Behavior
No response
Steps To Reproduce
No response
Desktop Version
v1.11.5
Anything else?
Linux Derbian 11 with KDE, Session AppImage.