Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Persistent stuck unread in encrypted room #25984

Closed
Tracked by #24392
andybalaam opened this issue Aug 17, 2023 · 2 comments
Closed
Tracked by #24392

Persistent stuck unread in encrypted room #25984

andybalaam opened this issue Aug 17, 2023 · 2 comments
Labels
A-Notifications O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect

Comments

@andybalaam
Copy link
Contributor

andybalaam commented Aug 17, 2023

Steps to reproduce

Report from an Element employee, who included confidential logs in the rageshake:

I have a room that has 2 unread notifications, with no new events, every time I start Element Nightly. If I click on it the unread counter skyrockets. If I mark it as read and then start pressing page up the unread count skyrockets again.

Version: 2023081601

@dbkr dbkr added S-Major Severely degrades major functionality or product features, with no satisfactory workaround A-Notifications O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience labels Aug 18, 2023
@benjaoming
Copy link

I still experience this, currently with 1 room. "Mark as read" has no effect on the encrypted room, and there is no unread messages, no unread threads, and no encryption errors to explain it.

This has happened many times in the past, but I think that some kind of event has made the "stuck unread" disappear on other rooms. Will have to pay closer attention to that.. but there's been a lot of upgrades and bug fixes in the mix of possible explanations :)

@langleyd
Copy link
Contributor

We believe this is fixed now, I checked in with the reporter and they have not seen it in weeks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Notifications O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect
Projects
None yet
Development

No branches or pull requests

4 participants