-
-
Notifications
You must be signed in to change notification settings - Fork 178
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
Message window is empty after reconnect #1556
Comments
https://lists.notraces.net/pipermail/profanity/2021/000047.html :
|
Someone in the MUC suggest that it has to do with: profanity/src/event/server_events.c Line 272 in e31e287
We filter out messages that we already received. So after reconnect MUC history is not displayed again. Still doesn't explain why for some people the window is cleared and for others not. Should check this. |
where are you checking, i mentioned the debug log in my issue, you could check. |
@mdosch Can you comment out the |
Doesn't have an impact.
On 23.02.2022 03:11, Michael Vetter wrote:
***@***.*** Can you comment out the `wins_reestablished_connection()` in `sv_ev_login_account_success()` and see what happens then for your?
…
--
Reply to this email directly or view it on GitHub:
#1556 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
|
Same thing here, version 0.11.1. A couple of twists: sometimes window is empty, sometimes some really old messages are loaded (exactly the same every time it happens), and only the ones that were received, not the ones that were sent. All chatlog files look correct, so it must be a loading issue. Similar thing happens after terminating, starting |
Just an update, that this also happens on another installation where I use a different set up:
|
@moorchegue also using Debian? |
Nope, I'm on Arch. |
I might have captured a trace
This might be the issue |
Sometimes after a reconnect the current window would get cleared. This was a deliberate change to fix the profanity window looking all garbled up after providing the passphrase for a gpg key using pinentry-curses. Fixes profanity-im#1556
@mdosch would be great if you could give feedback here. |
Sometimes after a reconnect the current window would get cleared. This was a deliberate change to fix the profanity window looking all garbled up after providing the passphrase for a gpg key using pinentry-curses. Fixes profanity-im#1556
Seems to be ok now. 🎉 |
If a reconnect happens while a chat window (MUC or 1-1) is open the whole window (top bar, bottom bar, participant list, chat win etc.) is empty (only background color) after the reconnect. Then it gets redrawn but the chat win remains empty.
simplescreenrecorder-2021-06-08_11.41.37.mp4
Expected Behavior
Show the messages in chat window after the reconnect.
Current Behavior
See above.
Steps to Reproduce (for bugs)
Environment
The text was updated successfully, but these errors were encountered: