Closed mdosch closed 3 years ago
Using 5c5c45321976c9a859694afa781178c68d076ee2, 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?
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: https://github.com/profanity-im/profanity/issues/1488#issuecomment-786769899
I just tried to message myself today. This time with OMEMO enabled. Again didn't segfault.
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.
@StefanKropp do you have an idea reagarding this part?
looking_for_jid = message->to_jid->barejid;
is actually run if its a MAM message.
@StefanKropp nevermind. I think it's not a OMEMO problem but a mistake I made.
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