-
-
Notifications
You must be signed in to change notification settings - Fork 179
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
Crash on opening 1:1 chat with history when server returns an empty page during RSM #1868
Comments
Interestingly enough, this only occurs with my account on the |
My terminal is really messed up after as well, scrolling just goes through my command history, using cat on text yields strangely formatted text with % symbols at the end of the file... (maybe control signals are being sent before the crash?) |
It seems like we don't get a liberatedsystems.co.uk seems to use ejabberd 23.04, which is latest. |
Excellent, this stops the crash, but now the history never loads unfortunately. Do you think this is an issue with the server? |
I expected that. Give me a minute to try to find out more. We don't get the first item in the result set. So that's why we can't display anything. We need to find out why is that. |
@jacobeva and you are sure you have a history which we could get from the server? |
Okay, so it looks like that for whatever reason MAM isn't working well on my server, let me investigate. |
Boom, got it! Okay, really weird issue. Basically, my ejabberd server was configured to use SQL as the backend database, but was still storing stuff in mnesia for some reason. So when it came to requesting archives, it would try to retrieve them from the SQL database, see nothing and then return nothing. Hence my server sending no history. To fix it, I just imported the SQL schema, exported my ejabberd server's DB using |
That PR will still be useful of course, since it does fix a crash, even if my server was misconfigured ;) |
Great to know the reason!
Of course :) We shouldn't crash in such cases. |
Whenever opening a chat window with an existing contact with chat history (be that through them messaging me, or through using the
/msg
command), profanity crashes within a couple of seconds.Expected Behavior
Profanity should not crash, and open the chat window with the history.
Current Behavior
Profanity completely crashes.
Possible Solution
No idea.
Crash trace
Context
I am trying to contact people in a 1:1 chat who I have previous chat history with.
Environment
Profanity, version 0.13.1dev.master.48148877
Copyright (C) 2012 - 2019 James Booth boothj5web@gmail.com.
Copyright (C) 2019 - 2023 Michael Vetter jubalh@iodoru.org.
License GPLv3+: GNU GPL version 3 or later https://www.gnu.org/licenses/gpl.html
Build information:
XMPP library: libstrophe
Desktop notification support: Enabled
OTR support: Enabled (libotr 4.1.1)
PGP support: Enabled (libgpgme 1.21.0)
OMEMO support: Enabled
C plugins: Enabled
Python plugins: Enabled (3.11.3)
GTK icons/clipboard: Enabled
GDK Pixbuf: Enabled
The text was updated successfully, but these errors were encountered: