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

Account not found #53

Closed
claucece opened this issue Sep 8, 2018 · 15 comments
Closed

Account not found #53

claucece opened this issue Sep 8, 2018 · 15 comments
Labels
bug importance high An issue that is absolutely necessary to have done before final release

Comments

@claucece
Copy link
Member

claucece commented Sep 8, 2018

Sometimes when the UI actions are too fast (you log in and not wait for the publication, and immediately start an OTR conversation), the account is not found and this happens:

No prekey client.

The printing of the account gives:

THE ACCOUNTz??? `

Sometimes as well, the protocol and account are not found for writing the persistent files and this gets writen:

@<b2><8a><dd><ce>!?:(null)
AAAABAABG4LpCAACABCzsG9HGCbEqD5hSHddu76Mu8Ol9NKhqAkXJyMoTVHFjLczxxcfaqUVRxknERlZK9VLwxlqLLVfoAAABAAAAAMzNAAABQAAAABbpUkLfLmvgcxJ16sRJYAOKWlpIgtLXpBEbFdi/YLAayijC269LAQXpEP23U4YPZdBky9CXDRRNeSwXkmA2SPnbokGoA4xhCiMsQRIoe6jQsxFblCC8vef+sGtzUrYWQC9fPlyIWucTz10QN5usCZhv3kchTUA

Can it be a threading error?

@claucece
Copy link
Member Author

claucece commented Sep 8, 2018

cc. @olabini

@claucece claucece added bug importance high An issue that is absolutely necessary to have done before final release labels Sep 8, 2018
@olabini
Copy link
Contributor

olabini commented Sep 8, 2018

I'll look into this. Did you add any debug-printing to see those statements?

@claucece
Copy link
Member Author

claucece commented Sep 8, 2018

No, I just printed the account->username on several places to see if it was been found.

@olabini
Copy link
Contributor

olabini commented Sep 8, 2018

Any idea where the specific places were printed that you saw?

@claucece
Copy link
Member Author

claucece commented Sep 8, 2018

Yes, immediately as you send the storage status message, and you get back that they are too low, and you try to publish:

https://github.com/otrv4/pidgin-otrng/blob/master/prekey-plugin.c#L98

Then this func does not get a prekey client:

https://github.com/otrv4/pidgin-otrng/blob/master/prekey-plugin.c#L274

And it fails here:

https://github.com/otrv4/pidgin-otrng/blob/master/prekey-plugin.c#L85

Around being incorrectly written in the persistent file, Idk when it happen, it just popped out.

@olabini
Copy link
Contributor

olabini commented Sep 11, 2018

I have not been able to reproduce this - I've added a large amount of printings all over the place to check for it, but it never happens for me...

@claucece
Copy link
Member Author

@olabini I'll recheck this.. maybe it is something solved.

@claucece
Copy link
Member Author

claucece commented Oct 1, 2018

I haven't seen this happening again but as we have some other weird bugs; it is worth keeping it open.

@olabini
Copy link
Contributor

olabini commented Oct 1, 2018

I just got a crash here:

                #4  0x00007fdd49b12654 get_domain_from_jid (pidgin-otrng.so)
                #5  0x00007fdd49b11c17 otrng_plugin_get_prekey_client (pidgin-otrng.so)

My guess is that this is from a missing PurpleAccount, so probably connected.

@olabini
Copy link
Contributor

olabini commented Oct 1, 2018

I've added some assertions to the pidgin-helpers file, to make sure all these invariants are always checked.

@claucece
Copy link
Member Author

claucece commented Oct 1, 2018

I'm quite uncomfortable on all of this refactorings, as it seems like a lot of functionality is getting broken. I'm unsure in which other places it is broken...

@olabini
Copy link
Contributor

olabini commented Oct 1, 2018

Sorry, not sure what you're talking about on this issue. I just added assertions to make it faster to see when something is broken.

@claucece
Copy link
Member Author

claucece commented Oct 1, 2018

Well, I'm talking in general. But let's talk about this on the call.

@olabini
Copy link
Contributor

olabini commented Dec 17, 2018

Have you seen this issue again?

@olabini
Copy link
Contributor

olabini commented Jan 30, 2019

OK, we haven't seen this issue for a long while. I'll close this issue now. In case it comes back we can reopen, but I don't think it will.

@olabini olabini closed this as completed Jan 30, 2019
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

2 participants