-
-
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
Segfault when trying to message myself #1488
Comments
Using 5c5c453, both
Anything special you are using? |
I forgot to mention it here. But I remembered that I restored
Conversations from a backup before this happened. Don't know if this
could play a role in regards to outdated OMEMO keys or something.
…On 26.02.2021 09:01, Michael Vetter wrote:
Both `/msg MY_JID` and `/msg MY_JID hi` result for me in:
```
26/02/21 17:59:00 - me: hi
26/02/21 17:59:00 - me: hi
```
Anything special you are using?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#1488 (comment)
|
I just tried to message myself today. This time with OMEMO enabled. Again didn't segfault.
@StefanKropp do you have an idea reagarding this part? |
|
@StefanKropp nevermind. I think it's not a OMEMO problem but a mistake I made. |
Regards #1488 Actually I would have loved to see the stanza that caused the segfault since I'm not entirely sure whether this actually means that we do something wrong earlier on. Right now I don't know why the to_jid should be empty. Let's prevent the segfault for now and see whether we get further bugreports later. Segfaulting issue got introduced with dd566d8.
If you ever do something similar please check whether it works as expected or whether a wrong window will be opened. |
I tried to message myself (the JID which is also used with profanity).
Expected Behavior
I message myself sometimes to share some info or links between different devices. I expected to be able to message myself.
Current Behavior
After opening the chatwindow
/msg MY_JID
profanity crashes.Environment
The text was updated successfully, but these errors were encountered: