Bug #1079
Unread counter counts from old session after /shutdown
| Status: | New | Start: | 08/29/2015 | |
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Complexity: | Found in Version: | |||
| Votes: | 0 |
Description
Kinda a follow-up on #1064 (and I did it recognize it back then, but forgot to add a report)
Starting a new smuxi-server session sets the "Last read"-line into the old session. If someone was talking this also sets the unread counter.
History
Updated by Mirco Bauer 3156 days ago
That the last seen message is remembered even across engine/session restarts is a feature though. What is wrong in this situtation? That you could read the unseen messages while Smuxi wasn't running? :-D
Updated by Lex Black 3155 days ago
Ah, ok.
I suppose I'm kinda "If I didn't read it back then, I don't want to be bothered with it on next start".
But as it is a feature (and after I checked for it explicitly and indeed no issue and behaves like you explained) this can be closed.
Updated by Lex Black 3152 days ago
Now I had a situation, where it didn't work like it expected.
My last message before quiting was on next start presented as an unread message.
Updated by Mirco Bauer 3151 days ago
That can happen when the frontend loses the connection unexpectedly from the engine. Was that the case? It only updates the last seen message when switching away from a chat or on clean disconnect/quit.
Updated by Lex Black 3151 days ago
IIRC I wrote the message and without window switching issued /shutdown
Updated by Mirco Bauer 3151 days ago
Oh /shutdown, yes this is probably a corner-case and with that a bug. The engine is shutting down and the frontend disconnects but doesn't quit. If this is reproducible it should be fixed. Thanks for the intel!
Updated by Mirco Bauer 3151 days ago
- Subject changed from Unread counter counts from old session to Unread counter counts from old session after /shutdown