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.

Sign up for GitHub

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

Jump to bottom

Stuck notification case #25513

Closed
Tracked by #24392
turt2live opened this issue Jun 2, 2023 · 2 comments
Closed
Tracked by #24392

Stuck notification case #25513

turt2live opened this issue Jun 2, 2023 · 2 comments
Labels
A-Notifications O-Occasional Affects or can be seen by some users regularly or most users rarely S-Critical Prevents work, causes data loss and/or has no workaround T-Defect

Comments

@turt2live
Copy link
Member

Steps to reproduce

  1. Unclear - clicking through my rooms in the morning (post update restart) yielded a stuck room

Outcome

What did you expect?

Unstuck notifications

What happened instead?

Stuck notifications - see attached rageshake for debugging details

Operating system

Windows 11

Application version

Element Nightly version: 0.0.1-nightly.2023060201 Olm version: 3.2.14

How did you install the app?

The Internet

Homeserver

t2l.io

Will you send logs?

Yes
@Johennes Johennes mentioned this issue Jun 5, 2023
Open
@kittykat kittykat added S-Critical Prevents work, causes data loss and/or has no workaround A-Notifications O-Occasional Affects or can be seen by some users regularly or most users rarely labels Jun 8, 2023
@rda0
Copy link
Contributor

rda0 commented Jul 19, 2023 •
edited
Loading

Similar for me. Yesterday after the update to 1.11.36 (Windows) and clear cache & reload some previously marked read messages (~60) had stuck notification counts. Today on Linux the same, update, clear cache & reload -> 6 stuck in 1 room. Then app crash + restart 9 stuck in 3 DMs. They went away after a manual mark as read. Sending rage shake now.

After another clear cache & reload the 6 stuck in 1 room re-appeared. Sending another rage shake

@t3chguy
Copy link
Member

t3chguy commented Aug 2, 2023 •
edited
Loading

Closing in favour of #24392 as there are no repro steps - this is highly likely to be fixed by the work on develop in the past month. If you continue seeing this please reopen with fresh logs & screenshots of the extended Notifications debug devtool - thanks

@t3chguy t3chguy closed this as completed Aug 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-Notifications O-Occasional Affects or can be seen by some users regularly or most users rarely S-Critical Prevents work, causes data loss and/or has no workaround T-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kittykat @turt2live @t3chguy @rda0