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.

Sign up for GitHub

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

Jump to bottom

NS_ERROR_NOT_INITIALIZED during LDAP search #146

Open

jdgeenen opened this issue Nov 2, 2019 · 0 comments

Assignees

Labels

bug

Owner

jdgeenen commented Nov 2, 2019 •

edited

Loading

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

Search an LDAP directory
Check the Error Console in TB:
NS_ERROR_NOT_INITIALIZED: Component returned failure code: 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsIAbDirectory.modifyCard] 2 AddressBook.js:256
AddressBook_updateContact chrome://gcontactsync/content/AddressBook.js:256
TBContact_update chrome://gcontactsync/content/TBContact.js:170
AbListener_onItemAdded chrome://gcontactsync/content/AbListener.js:65

Expected behavior
No error is expected

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: Mint
Version:1 18.2

Application (please complete the following information):

Application: Thunderbird
Application Version: 68.2
gContactSync Version: 3.1.7

jdgeenen added the bug label

jdgeenen self-assigned this

jdgeenen changed the title ~~NS_ERROR_NOT_INITIALIZED during bulk add of contacts~~ NS_ERROR_NOT_INITIALIZED during LDAP search

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment