Skip to content
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

Turning off OTR for a peer causes bad behavior #43

Open
olabini opened this issue Aug 24, 2018 · 4 comments
Open

Turning off OTR for a peer causes bad behavior #43

olabini opened this issue Aug 24, 2018 · 4 comments
Labels
bug importance high An issue that is absolutely necessary to have done before final release

Comments

@olabini
Copy link
Contributor

olabini commented Aug 24, 2018

If you inside of Pidgin says that OTR is turned off for ONE peer, you get weird behavior, primarily that someone starting an OTR conversation from the other side, still seems able to do it.

@claucece claucece added the bug label Aug 28, 2018
@claucece claucece added the importance high An issue that is absolutely necessary to have done before final release label Sep 9, 2018
@olabini olabini self-assigned this Mar 10, 2019
@olabini
Copy link
Contributor Author

olabini commented Mar 10, 2019

I'll take a look at this one.

@claucece
Copy link
Member

claucece commented Aug 5, 2019

Doing some investigation, it turns out that this happens:

Assertion failed: (client->client_profile != NULL), function otrng_client_get_client_profile, file client.c, line 833.

and, then, pidgin crashes.

@pedropalau
Copy link
Member

Assertion failed: (client->client_profile != NULL), function otrng_client_get_client_profile, file client.c, line 833.

This happens also when the server is not configured well.

I found this bug with @Cris2760 when we was reviewing another issue.

@claucece
Copy link
Member

claucece commented Aug 6, 2019

Yeah, it is caused by this: #107
The publication is not handled in the best way when locally something is not changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug importance high An issue that is absolutely necessary to have done before final release
Projects
None yet
Development

No branches or pull requests

3 participants